Home โ€บ Blog โ€บ EXCHANGE DOC IN FO DOES NOT MATCH ETKT RECORD

EXCHANGE DOC IN FO DOES NOT MATCH ETKT RECORD


A practical guide for travel agents on fixing the FO element ticket number mismatch error in Amadeus when reissuing a ticket with TTP/EXCH or TTP/RT.

When you reissue a ticket in Amadeus, the system does not simply trust what you typed into the PNR. It compares the old ticket number stored in the FO element โ€” the element that holds the exchange document information โ€” against the actual ticket record in the airlineโ€™s database. If there is any discrepancy, the reissue is rejected and the transaction stops. This FO element ticket number mismatch error is one of the most common reasons a reissue fails, and in most cases the fix takes less than a minute. This guide explains why the error happens and how to correct it step by step.

Why the Reissue Is Rejected

This error occurs when you attempt to reissue a ticket using TTP/EXCH or TTP/RT.

The system compares the old ticket number stored in the FO element against the actual ticket record. If there is any discrepancy โ€” a wrong airline code, an incorrect ticket number, or a formatting mistake โ€” the system rejects the transaction.

Common discrepancies include a missing digit, an incorrect airline prefix, a transposed number, or an FO line that was copied from a different passenger or a different ticket entirely.

Step 1: Check the Real Ticket Number

Display the e-ticket record using the TWD command to see the real ticket number stored by the airline.

Display a specific FA line:

TWD/Lx

Or redisplay the current record:

TWDRT

Step 2: Compare TWD with the FO Element

Compare the number shown in TWD with the number inside your FO element.

Look carefully at both the airline prefix (the first three digits, such as 077 or 172) and the numeric part of the ticket number. A single wrong digit anywhere in the sequence will cause the reissue to fail.

Step 3: Correct the FO Element

If the numbers do not match, update the FO line with the exact ticket number that appears in the TWD record.

Always copy the number directly from the TWD display rather than retyping it manually โ€” this avoids introducing a new formatting mistake.

Step 4: Retry the Reissue

After correcting the FO element, run the reissue command again:

TTP/RT

or:

TTP/EXCH

The transaction should now go through without the mismatch error.

Quick Fix Checklist

  1. Confirm the error appeared during a reissue with TTP/RT or TTP/EXCH.
  2. Display the real ticket record using TWD/Lx or TWDRT.
  3. Compare the airline prefix and numeric part with the FO element.
  4. Correct the FO line using the exact number from TWD.
  5. Retry the reissue command.
  6. Confirm the reissue was processed successfully.

Frequently Asked Questions

What causes the FO element ticket mismatch error?

A discrepancy between the old ticket number in the FO element and the actual ticket record โ€” a wrong airline code, an incorrect number, or a formatting mistake.

Which command displays the real ticket number?

Use TWD/Lx for a specific FA line, or TWDRT to redisplay the current record.

Do I need to cancel the PNR if the reissue fails?

No. In most cases, correcting the FO element with the exact ticket number from TWD is enough to complete the reissue successfully.

Conclusion

The FO element ticket number mismatch error is a data accuracy problem, not a system failure. Amadeus simply refuses to reissue a ticket when the exchange document number in the FO element does not match the real ticket record. The fix is straightforward: display the ticket with TWD, compare the airline prefix and numeric part against your FO element, correct any mismatch using the exact number shown, and retry the reissue with TTP/RT or TTP/EXCH. Taking a few seconds to verify the ticket number before reissuing prevents the error entirely and keeps your ticketing workflow smooth.


CT RJT: ETKT RJT โ€“ NO INTERLINE BETWEEN CARRIERS

ETKT FUNCTION NOT SUPPORTED FOR THIS CARRIER

ERROR: NO TAX COULD BE RETRIEVED, PLEASE ADD THEM MANUALLY

Linkedin