Home › Blog › Issue a Ticket in Amadeus: Complete TTP Command Guide

Issue a Ticket in Amadeus: Complete TTP Command Guide

Amadeus Ticketing · Complete Guide

Everything you need to issue a ticket in Amadeus — the beginner workflow, the full TTP command options, troubleshooting, and a video walkthrough. One guide, from first PNR check to final e-ticket number.

📅 Updated: November 2026 ⏱ 15 min read ✈️ GDS HUB Editorial

You’ve finally reached the moment every booking has been building towards: issuing the ticket. After searching flights, adding passenger names, arranging ticketing, adding contacts, including frequent flyer cards, pricing, adding passport data, and recording the form of payment — the only remaining step is to convert that PNR into a real, valid e-ticket.

In Amadeus, that moment is handled by a single command: TTP. On its own, it will issue a ticket in Amadeus for every passenger on every segment. But TTP is far more powerful than that. By adding options, you can control exactly which passengers and segments are ticketed, specify a validating carrier, reprice the TST, process exchanges, withhold taxes, generate invoices and boarding passes, and even verify the ticketing information before committing.

This guide walks through every major TTP option with working examples — plus the beginner workflow, common mistakes, troubleshooting, and a full video demonstration at the end.

Looking for the full reference? This article merges both the beginner lesson and the complete command reference into one place. Every TTP variant — from basic issuance to invoice-by-email — is documented below with an example.

Why Issuing a Ticket Is So Important

A PNR without a ticket is not a confirmed booking. Airlines will automatically cancel any PNR that hasn’t been ticketed within the ticketing time limit — usually 24 to 72 hours after reservation. When you issue a ticket in Amadeus, the system locks in the price, guarantees the seat, and generates the passenger’s 13-digit e-ticket number, which is required for check-in. This is the step that officially completes the sale and generates the agency’s revenue.

Step 1: Verify the PNR Is Ticketing-Ready

Before issuing, always check that the PNR has all the required elements:

  • Passenger names (NM) — matching the passport exactly
  • Contact information (AP / APE) — phone and email
  • Stored fare (FXP / FXR) — the pricing must be stored
  • Form of Payment (FP) — cash or credit card
  • Commission (FM) — if applicable
  • Ticketing Arrangement (FV / TKOK) — received from

If any of these are missing, Amadeus will return an error when you try to issue the ticket.

Related reading: For the pricing step before ticketing, see Amadeus FXP Pricing. For form of payment, see Amadeus FP Command.

Step 2: What Does the TTP Command Do?

TTP is the Amadeus GDS command used to issue a ticket in Amadeus for passengers and segments in a PNR.

Category: Ticketing.

The TTP command also supports options for selecting passengers, segments, validating carriers, rebooking, exchanges, taxes, invoices, and other ticketing requirements. By adding different options, you can control which passengers and segments are ticketed and how the ticket is processed.

Step 3: Basic Ticket Issuance

The simplest form of issuing a ticket in Amadeus is a single entry. This is what most agents use when the PNR is clean and ready:

TTP

Issues tickets for all passengers and all segments.

TTP/RT

Issues tickets and retains the PNR in the AAA — useful when you need to continue working on the PNR (invoices, boarding passes, exchange documents) immediately after ticketing.

TTP66A003

Issues tickets to an alternate printer (66A003 is the printer code).

TTP66A003/RT

Issues tickets to an alternate printer and retains the PNR in the AAA.

Step 4: Issue for Specific Passengers & Segments

When you only need to issue a ticket in Amadeus for part of the PNR — a specific passenger or a specific segment — use the passenger or segment reference:

Passenger selection

TTP/P1

Issues a ticket for passenger 1 only.

TTP/P1,3

Issues tickets for passengers 1 and 3 on all segments.

TTP/P1-4

Issues tickets for passengers 1 through 4 on all segments.

Segment selection

TTP/S2,4

Issues tickets for all passengers on individual segments 2 and 4.

TTP/S3-6

Issues tickets for all passengers on segments 3 through 6.

Passenger + segment combined

TTP/P1-2/S7,9,11

Issues tickets for passengers 1–2 on segments 7, 9, and 11.

Step 5: Passenger Type & Open Segments

Different passenger types (infant, child, adult) and open segments require their own options when you issue a ticket in Amadeus:

TTP/INF

Issues infant tickets — the infant is linked to the adult PNR.

TTP/PAX

Issues tickets for adult and child passengers only (excludes infants).

TTP/OPEN

Issues tickets for all passengers with a mirror-image open return.

TTP/S2AFCFRACDG

Issues tickets with a specific open segment (AFCFRACDG = carrier and city codes for the open segment).

Step 6: Validating Carrier & TST Selection

When you issue a ticket in Amadeus on a specific airline’s stock, or when the PNR has multiple TSTs, you must specify the validating carrier or TST number:

TTP/VAF

Issues tickets specifying a specific validating airline (in this example, Air France as the validating carrier).

TTP/T3

Issues the ticket for TST 3 — useful in a multi-passenger PNR where several TSTs exist.

TTP/R

Issues tickets and reprices the TST (re-evaluates fare rules before issuing).

TTP/RCH

Issues tickets and reprices the TST with a discount.

Step 7: Fare & Tax Override Options

Some fares require overrides — currency, past-date TST, paper vs. electronic conditions, withholding taxes or surcharges. Use these options when you issue a ticket in Amadeus under special fare conditions:

TTP/FE

Issues tickets and overrides the default currency.

TTP/F

Issues tickets and removes the TST change flag.

TTP/O

Issues tickets and overrides a past-date TST — use only with explicit airline authorization.

TTP/OPT

Issues tickets and overrides the electronic-ticket-only fare condition.

TTP/OET

Issues tickets and overrides the paper-ticket-only fare condition.

TTP/R,WT

Issues tickets while withholding all taxes.

TTP/R,WQ

Issues tickets while withholding all surcharges.

Watch out: Tax and fare overrides bypass the automatic validation. Confirm the airline’s rule first, then issue. Incorrect overrides lead to Agency Debit Memos (ADMs).

Step 8: Documents, Boarding Passes & Invoices

After issuing a ticket, you often need to produce additional documents for the passenger. These options let you issue a ticket in Amadeus and generate the documents in the same entry:

TTP/IBP

Issues both the tickets and itinerary.

TTP/IEP

Issues both the tickets and itinerary (alternate format).

TTP/BP

Issues both the tickets and boarding passes.

TTP/TKA

Issues tickets without boarding passes (US only).

TTP/INV

Issues tickets and the invoice.

TTP/IMP

Issues tickets and prints a mini-itinerary.

Invoice delivery by fax or email

TTP/INV-FAX-FR494960486

Issues tickets and sends the invoice by fax.

Issues tickets and sends the invoice by email.

Step 9: Other Ticketing Options

The remaining TTP variants handle edge cases — revalidation, agent codes, terminal time preference, exchanges, back-office messages. Use them when the standard issue a ticket in Amadeus entry isn’t enough:

TTP/TRV

Revalidates a ticket (ATB2 tickets only).

TTP/IG

Issues tickets and ignores the PNR when in temporary ticketing mode.

TTP/C-U

Overrides the default coupon print for ATB tickets.

TTP/A22AB

Issues tickets with an agent code printed on them.

TTP/TKT

Verifies that the ticketing information entered is correct — run before issuing on complex PNRs.

TTP/T012

Issues tickets and overrides the terminal time preference (12-hour format).

TTP/T024

Issues tickets and overrides the terminal time preference (24-hour format).

TTP/FPCASH

Issues tickets including the form of payment.

TTP/EXCH

Issues tickets for an exchange — used after reissue pricing (FXO, FXQ, or FXI).

TTP/H1

Issues tickets and sends a shadow A.I.R. to the office defined in the office profile.

TTP/BTK

Sends an A.I.R. to the back-office system without issuing tickets.

TTP/R,DO-OBD

Issues tickets and overrides the booking date restriction.

TTP/OD16JUN0X

Issues tickets and overrides the ticketing date.

Step 10: Understanding the E-Ticket Output

After issuing, Amadeus returns a confirmation that contains the essential ticketing data. Read it carefully — this is what you’ll provide to the passenger:

  • 13-digit e-ticket number — starts with the airline’s 3-digit code (e.g., 077 for EgyptAir, 172 for Cathay Pacific)
  • Passenger name and flight details
  • Fare and total amount paid
  • Form of payment used

Record these numbers and provide them to the passenger — this is what they present at check-in. The e-ticket number is required for online check-in, seat selection, and any post-ticketing service request.

Step 11: Print or Send the Itinerary Receipt (TWD)

After you issue a ticket in Amadeus, print or email the itinerary receipt for the passenger using the TWD command:

TWD/L9

TWD displays the ticket or document, and /L9 selects line number 9 (adjust according to your PNR).

Pro Tip: Always re-verify the ticket after issuance using the TWD command. Check that the passenger name, flight dates, and ticket number all match. Once the ticket is issued, changes require a reissue (with penalties) or a refund.

Video Lesson

Watch the complete step-by-step walkthrough of issuing a ticket in Amadeus:

Common Mistakes Beginners Make

These are the most frequent errors when issuing a ticket in Amadeus — each one has been seen countless times in real agencies:

  • Trying to issue without a stored fare — TTP will fail because there’s no TST to attach the ticket to.
  • Missing the Form of Payment — the system needs a valid FP entry before issuing.
  • Issuing after the ticketing time limit — the PNR gets cancelled automatically, and the booking is lost.
  • Ignoring the airline’s specific ticketing instructions — some carriers require a specific validating carrier or a specific fare basis.
  • Using the wrong TTP variant — for example, TTP/EXCH for an exchange instead of a new ticket (or vice versa).
  • Issuing with an incorrect passenger name — one of the most expensive errors to fix, often requiring a full reissue or void.
  • Sharing the e-ticket number publicly — it contains personal data; treat it like any other PII.

Troubleshooting Common TTP Errors

When TTP fails, the system returns an error code that tells you exactly what to fix. The most common errors when you issue a ticket in Amadeus are listed below with the correct action:

Combination Not Allowed — TTP

The combination of fares, tour codes or passenger types you’re trying to ticket is not permitted by the airline.

Read: Combination Not Allowed — TTP →

Invalid Fare Basis

The fare basis in the TST does not match any valid fare for the itinerary.

Read: BI-ETKT Invalid Fare Basis →

No Tax Could Be Retrieved

The system could not retrieve the applicable taxes for one or more segments. Taxes must be added manually.

Read: No Tax Could Be Retrieved →

ETKT Function Not Supported for This Carrier

The airline does not support electronic ticketing through Amadeus for this itinerary.

Read: ETKT Function Not Supported →

No Interline Between Carriers

The carriers in the itinerary do not have an interline e-ticketing agreement. Separate tickets may be needed.

Read: No Interline Between Carriers →

Maximum Number of Flights / Passengers / Tickets Exceeded

The PNR contains more segments, passengers, or tickets than the airline allows on a single document.

Read: Maximum Number Exceeded →

Check Date of Birth

The date of birth on the PNR is missing or invalid — common with infant or child fares.

Read: Check Date of Birth →

Check Itinerary

The itinerary has an inconsistency — a date gap, missing segment, or mismatched routing.

Read: Check Itinerary →

Invalid Past Date Segment

One or more segments have a past departure date. Use TTP/O only with airline authorization.

Read: Invalid Past Date Segment →

Commission Not Validated

The commission entered does not match the applicable rule — re-enter before issuing.

Read: Commission Not Validated →

Cancel Seat Item or Split PNR Prior to Name Re-entry

A seat reservation or name change is preventing ticket issuance.

Read: Cancel Seat Item / Split PNR →

EDIFACT Message Size Exceeded

The PNR contains more data than the EDIFACT message can carry — split the PNR.

Read: EDIFACT Message Size Exceeded →

Attn — Issue Separate Tickets

The itinerary requires separate tickets — split the PNR and issue each independently.

Read: Issue Separate Tickets →

Best Practices & Pro-Tips

The TTP command is powerful — and permanent. Once you issue a ticket in Amadeus, it can only be voided (same day) or refunded (with penalties). Follow these practices before pressing Enter:

⚠️ Never use TTP/O unless you are certain. TTP/O forces issuance of a past-date TST. It bypasses airline fare rules and can lead to a rejected ticket at check-in or an ADM. Only use it when the airline has explicitly authorized the override.

⚠️ Verify taxes before using TTP/R,WT. Withholding all taxes removes them from the ticket but does not remove the airline’s obligation to collect them. Some taxes (like YQ) are non-refundable and must still be settled.

✓ Use TTP/TKT to verify before committing. On complex PNRs, run TTP/TKT first to confirm all ticketing information is correct. This prevents mistakes that are expensive to reverse.

✓ Always use TTP/RT for multi-step workflows. TTP/RT issues the ticket and retains the PNR in the AAA. This saves you from retrieving the PNR again when you need to process invoices or boarding passes immediately after.

✓ Combine document options in one entry. You can issue tickets, itineraries, boarding passes, and invoices together — for example TTP/IBP/INV. This reduces the number of entries and the risk of inconsistency.

✓ Keep the validating carrier accurate. If you issue a ticket in Amadeus on the wrong validating carrier (via TTP/VXX), the ticket must be voided and reissued. Always confirm against the fare rule.

Comparison of Related Ticketing Commands

TTP is the entry that issues the ticket, but it works alongside a set of commands that prepare, display, delete, or modify the TST before issuance. The table below summarises the most important related commands:

Command Purpose When to Use
TTPIssues tickets for passengers and segmentsFinal step of ticketing
TQTDisplays all TSTs in the PNRBefore issuing — verify fare and TST
TQTCDisplays the TST with full detailsReview all fare, tax and validity elements
TTEDeletes a TST from the PNRWhen repricing is needed
TTKUpdates fare, taxes, validity, baggageManual override before issuance
TTIAdds or modifies itinerary remarksSpecial itinerary wording
TTFRemoves the TST change flagWhen the TST is final and ready to issue
TTCCreates a manual TSTWhen automatic pricing is not suitable
TRFProcesses a refund after issuanceWhen a ticket must be refunded
FXIReprices for reissue of a fully used ticketBefore TTP/EXCH
FXOReprices for reissue without tax re-collectionBefore TTP/EXCH
FXQReprices for reissue with tax re-collectionBefore TTP/EXCH

Frequently Asked Questions

What does TTP do in Amadeus?

TTP is the main ticket issuance command. It lets you issue a ticket in Amadeus for all passengers and segments, or use options to target specific passengers, segments, validating carriers, exchanges, and documents.

What does TTP/RT mean?

It issues tickets and retains the PNR in the AAA — so you can continue working without retrieving it again.

How do I issue a ticket in Amadeus for a specific passenger only?

Use the passenger association: TTP/P1 for passenger 1 only, TTP/P1,3 for passengers 1 and 3, or TTP/P1-4 for a range.

How do I issue an exchanged ticket in Amadeus?

Use TTP/EXCH to issue a ticket in Amadeus for an exchange. This is typically used after reissue pricing with FXO, FXQ, or FXI.

Is it safe to use TTP/O for a past-date TST?

No. TTP/O overrides the system’s past-date check and should only be used when the airline has explicitly authorized it. Using it without authorization can lead to rejected tickets or ADMs.

How do I print the itinerary receipt after issuing?

Use TWD with the ticket line number — for example TWD/L9. This displays or prints the ticket and itinerary for the passenger.

What if TTP fails with an error code?

Common TTP errors include Combination Not Allowed, Invalid Fare Basis, No Tax Could Be Retrieved, ETKT Function Not Supported, and No Interline Between Carriers. Each has a specific fix — see the troubleshooting section above.

How do I send the invoice by email when I issue a ticket in Amadeus?

Use the combined entry: TTP/[email protected]. This issues the ticket and sends the invoice to the passenger’s email in a single step.

Conclusion

Issuing a ticket in Amadeus is the final step that transforms a PNR into a real, valid booking. The Amadeus TTP command is the single most important entry in Amadeus ticketing — on its own it issues tickets for every passenger and segment, and with the right options it becomes a complete ticketing control centre for passenger selection, validating carrier, TST selection, repricing, exchange, fare and tax overrides, document generation, and invoice delivery.

Use TTP for a standard issuance, TTP/RT to keep the PNR open, TTP/P1,3 or TTP/S2,4 for partial issuance, TTP/EXCH for exchanges, and TTP/TKT to verify before issuing. Paired with TQT, TTC, TTK, TTI, TTE, and TTF, it completes the Amadeus ticketing toolkit and ensures every ticket is issued correctly.

Practise TTP in a Safe Amadeus Simulator

Create a free GDS HUB account and practise TTP, TTP/RT, TTP/EXCH, and every other ticketing command in a simulated Amadeus environment — no live data, no risk.

Start Practising Free →