PNR Management

PNR Management

What Is PNR Management?

A passenger name record (PNR) is the electronic file a reservation system creates for every booking. It holds who is traveling, what they booked, how to reach them and when the ticket must be issued. Each PNR is identified by a six-character record locator, the code travelers see on their confirmation. A PNR in travel usually starts with flights, but in a GDS it can also hold hotel, car and rail segments.

PNR management is the work of creating, updating, monitoring and syncing these records across every system that uses them: the airline, the GDS, and the agency’s mid-office, CRM and accounting tools. Done well, it keeps the record accurate from first booking to final refund, so tickets, invoices and traveler messages all match.

How a PNR Is Created and Updated

  1. Booking. An agent or online booking tool sells flight segments in a GDS or airline system, and the seats are held.
  2. Mandatory data. Passenger names, contact details, a ticketing time limit and the name of whoever requested the booking are added.
  3. Saving the record. Ending the transaction generates the record locator. The airline creates its own PNR with a separate locator, linked to the GDS record.
  4. Pricing. The fare is calculated and stored in the record as a fare quote.
  5. Ticketing. Payment is taken, the e-ticket is issued and its number is written back into the PNR.
  6. Import to agency systems. The mid-office reads the PNR and creates the booking file, client invoice and supplier payable. Our article on GDS vs mid-office systems explains how the two divide this work.
  7. Changes. Date changes, airline schedule changes, seat and meal requests and cancellations update the same record. Each change is logged in the PNR history, and a reissued ticket gets a new number linked to the original.
  8. Purge. Some days after the last segment, the GDS removes the PNR from the active system.

Components of a PNR

Five elements are mandatory in most systems, often remembered with the acronym PRINT:

  • Phone. Contact details for the agency and traveler, used for schedule change notices.
  • Received from. Who requested or changed the booking, for accountability.
  • Itinerary. The flight, hotel, car or rail segments, with dates, classes and status codes.
  • Name. Each passenger’s name exactly as on the passport.
  • Ticketing. The ticketing time limit or, once issued, the ticket number.

Most records also carry optional elements:

  • Special service requests (SSRs). Meals, wheelchair assistance, passport data and frequent flyer numbers sent to the airline.
  • Other service information (OSI). Notes for the airline that need no action, such as VIP status.
  • Remarks. Free text and accounting remarks. Back-office remarks pass client codes, cost centers and markups to the mid-office.
  • Fare records. The stored price, fare basis and fare rules.
  • Form of payment. How the ticket was or will be paid.
  • History. A log of every change, who made it and when.

PNR Management Best Practices

  • Use profiles and templates. Pull traveler and company data from stored profiles so names, contacts and remarks are entered the same way every time.
  • Standardize accounting remarks. Agree on one remark format for client codes, markups and cost centers, so the mid-office can read every record without manual fixes.
  • Work queues daily. Schedule changes, ticketing deadlines and waitlist clearances land in GDS queues. Unworked queues mean missed deadlines and stranded travelers.
  • Check names before ticketing. Most airlines do not allow name changes, so a typo can cost a new ticket.
  • Cancel unused segments. Duplicate or inactive segments can trigger airline debit memos and no-show penalties.
  • Keep one source of truth. Every change in the GDS should reach the mid-office automatically, without retyping. Our article on cutting booking errors with mid-office automation shows where manual steps go wrong.
  • Protect personal data. PNRs hold passport and contact details, so limit access and follow GDPR and local privacy rules.

Travel Booster supports this by syncing flight bookings from the GDS directly into its mid-office, validating booking data for completeness before confirmation and flagging inconsistencies early. Tickets, invoices and vouchers are then generated from the same validated record. See how a mid-office connects your GDS, CRS, CRM and accounting system.

FAQ

How long does a PNR stay active after travel?

Most GDSs purge a PNR from the active system a few days after its last segment, though exact timing varies by system and airline. A history copy can usually be retrieved for longer. Agencies keep their own copy in the mid-office for accounting, audits and data retention requirements.

Is a PNR the same as a ticket number?

No. The PNR is the booking, identified by a six-character record locator. The e-ticket number is a 13-digit number, starting with the airline’s three-digit code, that proves payment. One PNR can hold several tickets, one per passenger plus any reissues, and a PNR can exist before any ticket is issued.

Can one PNR hold more than one passenger?

Yes. Families and small parties traveling on the same itinerary often share one PNR, commonly up to nine passengers. Larger parties use a group PNR. If one passenger needs a different itinerary, the agent splits that person into a new PNR linked to the original.

What happens to a PNR when a booking is changed?

The record locator usually stays the same, while the segments, prices and remarks are updated and logged in the history. If the fare changes, the ticket is reissued with a new number linked to the old one. The mid-office must receive the update so invoices and supplier costs stay correct.