A complete guide to the RTN and RTNR commands in Amadeus โ how to display individual passenger names in a group PNR, either in the current format or exactly as originally entered.
Group PNRs work differently from individual bookings. Instead of a full name list from the start, a group PNR usually begins with a group name element such as NG15EUROPE TOUR, and individual passenger names are added later. Once those names are in the PNR, they can be displayed in two different ways โ in the current standard format, or exactly as the agent originally typed them. The RTN and RTNR commands handle these two views. This guide explains what each command does, when to use them, and why the difference matters when verifying group passenger data.
What Do the RTN and RTNR Commands Do?
RTN and RTNR are Amadeus GDS commands used to display passenger names in a group PNR.
Category: Group Booking.
They allow you to display individual passenger names from a retrieved group PNR, either in the current format or exactly as they were originally entered.
The distinction is important. RTN shows how the names currently appear in the PNR structure โ after any system formatting, name updates, or corrections. RTNR shows the names precisely as the agent typed them, which is essential when verifying original entries against passports, identity documents, or group manifests.
Display Individual Names
To display the individual passenger names in a group PNR:
RTNThis displays the individual passenger names in a group PNR in the current format. Use it when you need a clear list of all named passengers in the booking โ for example, when preparing a rooming list, checking that all expected travellers have been added, or confirming the group is ready for ticketing.
Display Names as Originally Entered
To display the passenger names exactly as they were originally entered:
RTNRThis displays the passenger names as they were originally entered in the PNR. It is the correct command when you need to verify the original name entries โ particularly in cases where a name has since been updated, corrected, or reformatted, and you need to trace exactly what was submitted to the airline.
RTN vs RTNR โ Which One to Use
- RTN โ displays the current individual passenger names in the group PNR.
- RTNR โ displays the passenger names as they were originally entered.
Use RTN when you need the current list โ for manifests, rooming lists, or confirming names before ticketing. Use RTNR when you need the original entries โ for verifying what was submitted to the airline, checking against a name change, or resolving a discrepancy.
When to Use RTN or RTNR
Use RTN or RTNR when working with a group PNR and you need to review the individual passenger names, especially to verify the original name entries. Typical scenarios include:
- Preparing a passenger manifest or rooming list for a group booking.
- Confirming that all expected travellers have been added before ticketing.
- Verifying original name entries against passports or identity documents.
- Investigating a discrepancy after a name correction was applied.
- Checking the group composition before the airlineโs name deadline.
- Confirming how names appeared when they were first submitted to the airline.
How RTN and RTNR Fit Into Your Group Booking Workflow
A typical group booking session using RTN or RTNR might look like this:
- Retrieve the group PNR.
- Enter
RTNto review the current individual passenger names. - Check that every expected traveller is listed correctly.
- Enter
RTNRwhen you need to confirm the original name entries. - Compare the two views if a name was updated or corrected.
- Take any necessary action โ add missing names, correct errors, or proceed with ticketing.
Important: Group PNRs usually carry a strict airline deadline for submitting individual passenger names. Missing that deadline can result in the group space being automatically cancelled without notice.
Always use RTN to verify the current name list before the deadline, and RTNR to confirm the original entries if any changes or disputes arise.
How RTN and RTNR Relate to Other Group Booking Commands
- NG โ creates a group name element.
- AN/RGRP โ displays group availability.
- SS/SG or SS/PG โ sells confirmed or waitlisted group space.
- RTN โ displays the current individual passenger names in a group PNR.
- RTNR โ displays passenger names as originally entered.
- RH โ displays the full PNR history, including name changes.
- TTP โ issues tickets once names are confirmed.
Frequently Asked Questions
What does RTN do in Amadeus?
RTN displays the individual passenger names in a group PNR in the current format.
What does RTNR do?
RTNR displays the passenger names exactly as they were originally entered in the PNR.
When should I use RTNR instead of RTN?
Use RTNR when you need to verify the original name entries โ for example, when checking what was submitted to the airline, or investigating a change made to a name.
Do RTN and RTNR work on individual PNRs?
These commands are specifically designed for group PNRs. For individual bookings, use the standard name display commands.
Conclusion
The RTN and RTNR commands give you two essential views of passenger names in a group PNR. Use RTN to see the current individual name list โ ideal for manifests, rooming lists, and pre-ticketing checks. Use RTNR to see the names exactly as they were originally entered โ essential for verifying original submissions and tracing name changes. Because group bookings carry strict airline deadlines for names and ticketing, checking both views before the deadline helps prevent cancellations and disputes. Used together with NG, AN/RGRP, SS/SG, and TTP, they complete the Amadeus group booking toolkit and ensure every group reservation is accurate from the first entry to final issuance.
