To add passport information in GDS, you need to use a different command in each Global Distribution System — SRDOCS in Amadeus, SI.P1/SSRDOCS in Galileo, and 3DOCS in Sabre. Travel agents and airline ticketing staff must add passport information to the PNR for every international booking, because airlines use this data to comply with Advance Passenger Information System (APIS) regulations. This guide walks through all three GDS commands with real examples, a quick comparison table, and the correct end transaction command for each system.
Whether you’re booking a Cairo-to-London flight in Amadeus or a JFK-to-Dubai trip in Sabre, getting the passport format right at the point of entry prevents failed APIS submissions, denied boarding, and costly reissues. Add passport information in GDS correctly and your bookings will clear ticketing and check-in without friction.
Why Adding Passport Information in GDS Is Mandatory
Adding passport information in GDS is not optional. For any international itinerary, airlines are legally required to collect and transmit passenger passport data to government authorities before departure. This transmission happens through APIS, and it starts from the PNR passport element you enter in the GDS.
If passport information is missing or incorrect:
- The airline may reject the ticketing attempt
- The passenger may face check-in delays at the airport
- The booking may be flagged by immigration authorities
- You may face penalties or ADM (Agency Debit Memo) charges
Adding passport information in GDS proactively — before you issue the ticket — is best practice. Always match the passport data exactly to the document, and always verify the passenger name order (Surname/Given name) against the passport itself, not just the booking.
Amadeus: Add Passport Information in GDS with SRDOCS
The Amadeus command to add passport information in GDS is SRDOCS. It uses hyphens (-) as field separators and ends with /P1 to link the document to a specific passenger.
Amadeus SRDOCS Format
| Field | Meaning |
|---|---|
| SRDOCS | The Amadeus command to add passport information in GDS |
| Two-letter airline code (e.g., UA) | |
| HK1 | Confirmed segment status |
| P | Document type — P = Passport |
| Passport holder’s nationality (ISO code) | |
| Passport number | |
| Date of birth (DDMMMYY) | |
| M = Male, F = Female | |
| Passport expiry date (DDMMMYY) | |
| Passenger surname/given name | |
| /P1 | Link to passenger 1 in the PNR |
Amadeus SRDOCS Example
Passenger JOHN SMITH, US citizen, passport US123456, DOB 01 Jan 1980, expiry 31 Dec 2030, male:
/P1 at the end of the command is what links the passport information to passenger 1. If the booking has multiple passengers, use /P2, /P3, and so on.
Galileo: Add Passport Information in GDS with SI.P1/SSRDOCS
The Galileo (Travelport) command to add passport information in GDS is SI.P1/SSRDOCS. Unlike Amadeus, Galileo uses slashes (/) as field separators, and the passenger link SI.P1 is placed at the beginning of the entry rather than at the end.
Galileo SI.P1/SSRDOCS Format
| Field | Meaning |
|---|---|
| SI.P1 | Select passenger 1 — links the document to the correct passenger |
| /SSRDOCS | The Galileo command to add passport information in GDS |
| Two-letter airline code | |
| HK1 | Confirmed segment status |
| /P | Document type — P = Passport |
| / | Passport holder’s nationality |
| / | Passport number |
| / | Date of birth (DDMMMYY) |
| / | M = Male, F = Female |
| / | Passport expiry date |
| / | Passenger surname/given name |
Galileo SI.P1/SSRDOCS Example
Same passenger (John Smith) — added in Galileo:
/P1 at the end — the SI.P1 at the start already links the document to passenger 1. This is the most common mistake when switching between Amadeus and Galileo.
Sabre: Add Passport Information in GDS with 3DOCS
The Sabre command to add passport information in GDS is 3DOCS. It uses slashes (/) for field separators, requires the place of issue field (unlike Amadeus and Galileo), and ends with a -1.1 suffix that links the document to passenger 1, segment 1.
Sabre 3DOCS Format
| Field | Meaning |
|---|---|
| 3DOCS | The Sabre command to add passport information in GDS |
| /P | Document type — P = Passport |
| / | Passport holder’s nationality |
| / | Passport number |
| / | Country where passport was issued (e.g., USA) — mandatory in Sabre |
| / | Date of birth (DDMMMYY) |
| / | M = Male, F = Female |
| / | Passport expiry date |
| / | Passenger surname/given name |
| -1.1 | Link to passenger 1, segment 1 |
Sabre 3DOCS Example
Same passenger (John Smith), passport issued in the USA:
-1.1 suffix means passenger 1, segment 1 — if the booking has multiple passengers, use -2.1, -3.1 for passenger 2, 3, etc.
Quick Comparison: Add Passport Information in GDS
Side-by-side view of the three GDS passport commands.
| GDS | Command | Passenger Link | Key Difference |
|---|---|---|---|
| Amadeus | SRDOCS | /P1 at the end | Uses hyphens (-) and HK1 |
| Galileo | SI.P1/SSRDOCS | SI.P1 at start | Uses slashes (/), no final /P1 |
| Sabre | 3DOCS | -1.1 at end | Requires place of issue field |
End Transaction Commands After Adding Passport Information in GDS
Once you add passport information in GDS, you must save the PNR with the correct end transaction command for each system:
| GDS | End Transaction Command |
|---|---|
| Amadeus | ER (End and Retrieve) or ET (End Transaction) |
| Galileo | IT (Ignore and Transmit) or ER |
| Sabre | ET (End Transaction) or ER (End and Retrieve) |
RT (Amadeus), *R (Galileo), or *PNR (Sabre) to display the PNR and verify the passport element appears correctly under the passenger.
Common Mistakes When You Add Passport Information in GDS
These are the most frequent errors agents make when adding passport information in GDS:
- Wrong passenger link — using
/P1in Galileo instead ofSI.P1, or forgetting/P1entirely in Amadeus - Missing place of issue in Sabre — the
3DOCSentry will fail - Incorrect date format — must be
DDMMMYY(e.g.,01JAN80), not01/01/80 - Mismatched name order — some GDS require Surname/Given name, others accept Given/Surname — always match your GDS format
- Typo in passport number — one wrong digit can cause APIS rejection
- Saving without verifying — always redisplay the PNR after adding passport information
FAQ: Add Passport Information in GDS
Why is adding passport information to a PNR mandatory?
Airlines require passport details for international flights to comply with APIS regulations. Adding passport information in GDS ensures the PNR is complete before ticketing and prevents check-in issues.
What is the SRDOCS command in Amadeus?
SRDOCS is the Amadeus command to add passport information. Format: SRDOCS HK1-P- – – – – – – /P1. The /P1 suffix links the document to passenger 1.
How do I add passport information in Galileo?
Use SI.P1/SSRDOCS followed by the airline, HK1, and slash-separated fields. The SI.P1 prefix ties the document to passenger 1.
What is the 3DOCS command in Sabre?
3DOCS is the Sabre command to add passport information. Format: 3DOCS/P/ / / / / / / -1.1. The -1.1 suffix links to passenger 1, segment 1.
Which end transaction command should I use after adding passport information?
Use ER in Amadeus, IT in Galileo, and ET in Sabre to save the PNR after adding passport information in GDS.
What is the place of issue field in Sabre 3DOCS?
The place of issue is the country where the passport was issued — for example USA for a US passport. Sabre requires this field, unlike Amadeus and Galileo.
📚 Read Also
Practise Adding Passport Information in GDS — Free Simulator
Create a free GDS HUB account and practise the SRDOCS, SI.P1/SSRDOCS, and 3DOCS commands in a simulated Amadeus, Galileo, or Sabre environment — no live data, no risk.
Start Practising Free →