What a PNR is, and how it relates to a corporate trip record
A passenger name record, usually shortened to PNR, is the file an airline (or the system that holds the airline booking) keeps for a traveller or a travelling group. It typically contains names, itinerary segments, contact details, and ticketing status. In everyday talk, “the PNR” is often used as a synonym for the booking locator itself — the code on a ticket or an itinerary. In a corporate programme, that airline file is necessary, and it is not the whole story.
GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips. This glossary entry defines PNR travel in that corporate context, and then relates it to the corporate booking record that also holds policy, approvals, hotels, documents, cost and duty of care.
What a PNR usually contains
At minimum it identifies the passengers and the flight segments they hold. It may also hold special requests, contact data, and a ticketing deadline. When a flight is changed, the PNR is the airline-side file that has to be updated. When two people travel on the same locator, they share a PNR; when they are ticketed separately, they may not.
A PNR is not, by itself, a policy check, an approval, a hotel confirmation, an invoice, or a duty-of-care view. Those objects may refer to the same journey, but they live in the corporate record unless the programme has been designed so they share a file.
How this sits next to GDS, NDC and GTOS
Airline bookings are often created or retrieved through distribution paths described, conservatively, in the glossary entries for GDS and NDC, and in the search-to-ticket guide. GTOS is not a GDS terminal, and this page does not claim a GDS or NDC certification. How a given distribution path is used is an implementation and demo topic; we do not publish a certified connector list. See also GDS integrations, written with the same restraint.
In GTOS, the traveller requests a flight in My Mobility, policy and approvals sit on the trip, and the desk works the file in Control Tower. A locator or PNR that results from ticketing belongs in that trip context. If the only current itinerary is a PNR in a separate tool, the corporate programme has already lost the rest of the file.
USD is the main currency on this site. Pricing is in USD and available on request. Each company sees only its own data. Access is by role. We do not claim certifications we do not hold.
What this entry will not claim
We will not invent a field-level PNR map, a locator format, or a live certification against a distribution standard. We will not treat a PNR as a substitute for documents, hotels, ground transport or invoices. A demo can show a flight request becoming a ticketed trip on the GTOS record, and can be explicit about how a locator appears on that file, without presenting GTOS as an airline system of record.
Frequently asked questions
Is a PNR the same as a GTOS trip record?
No. A PNR is the airline-side booking file. The GTOS record is the corporate file that can also hold policy, approvals, hotels, documents, cost and duty of care, with the flight booking in context.
Does GTOS replace a GDS terminal?
No. GTOS is a travel operating system. We do not claim GDS or NDC certification on this page. Distribution paths are a demo and implementation topic.
Why do travel teams still talk about the PNR?
Because it is the airline file and the locator people use at the airport. In a corporate programme it still has to sit inside a wider trip record, or the rest of the journey will fragment.
Related
See GTOS in a demo
We are now taking early-access requests. Demo accounts are available now.
- A walkthrough of the Client Portal, My Mobility and Control Tower
- Your travel policy, set up in a demo account
- USD pricing discussed on request, with PKR quotes available
Prefer email or WhatsApp? insights@goglobal.pk · +92 320 4111222