Amadeus FXI Command: ATC Involuntary Reissue

A complete guide to the FXI command in Amadeus — how to price an itinerary for an ATC involuntary reissue caused by an airline schedule change or flight cancellation.

FXI will only work when the system recognises that the itinerary change is truly involuntary. Before running FXI, verify each of the following:

• Active PNR with an involuntary segment status — the segment status must reflect an airline-driven change: UN, UC, US, NO, HX (flight cancelled), or a schedule change indicator from the airline. Without an involuntary status, FXI will be rejected.
• Airline-initiated disruption documented in the PNR — either the airline’s schedule change advice or the auto-queued schedule change message must be visible in the PNR history.
• New itinerary already updated — the rerouted or rebooked segments must be stored before running FXI so the pricing is applied to the correct routing.
• Issued ticket with valid FA element — the original ticket must be present in the PNR. Without it, there is nothing to reissue involuntarily.
• Active ATC session — the PNR must be open inside the Amadeus Ticket Changer (ATC) workflow, not in a standard booking workspace.
• Office profile permission — your sign-in must be authorised to run ATC involuntary pricing commands.

If any of the above is missing — especially the involuntary segment status — FXI will not produce a valid pricing result. Fix the PNR state first before retrying.

FXI is an Amadeus ATC Involuntary command used for pricing an itinerary when a ticket change is due to an involuntary situation, such as an airline schedule change or flight cancellation.

Category: ATC Involuntary Reissue.

The FXI command initiates the ATC Involuntary pricing process for an eligible involuntary ticket reissue. It tells the system that the itinerary change was caused by the airline, not by the passenger, so the pricing must be handled under involuntary rules.

This is the crucial difference from a standard pricing entry: FXI does not simply search for the best available fare. It applies the involuntary reissue logic that airlines and ATC accept for disruption cases, where no penalty and no additional collection should apply.

Enter the command while the PNR containing the affected itinerary is retrieved:

FXI

This starts the ATC Involuntary pricing process for the eligible itinerary in the PNR. The result is a repriced record prepared for the involuntary reissue.

• Used for ATC Involuntary — it applies the involuntary pricing logic, not standard voluntary pricing rules.
• Handles eligible involuntary itinerary changes — the change must have been caused by the airline, not by the passenger.
• Used during the ticket reissue process — FXI is part of the reissue workflow, not a standalone ticketing command.

💡 Pro-Tip — Always Verify the TST After Running FXI

FXI creates or updates a TST under involuntary conditions. Before moving on to issuance, verify that the TST actually reflects the involuntary treatment — otherwise the airline may reject the reissue or raise an ADM.

1️⃣ TQT     → display the TST created by FXI
2️⃣ check   → fare difference = 0
3️⃣ check   → no penalty collected
4️⃣ check   → fare basis matches the involuntary rule
5️⃣ ER      → save if all correct

If any of these items is wrong, do not continue to issuance. Delete the TST with TTE and re-run FXI after correcting the PNR. For a full review of the TST history, use TTH.

Use FXI when a passenger’s itinerary needs to be changed due to an airline-initiated disruption, such as a cancellation or schedule change, and you need to process an involuntary reissue using ATC. Typical scenarios include:

• A flight cancellation that requires rerouting the passenger on another service.
• A significant schedule change that makes the original connection impossible.
• An itinerary change initiated by the airline for operational reasons.
• Aircraft change or equipment downgrade affecting the booked class.
• Any case where the passenger should not pay extra or incur penalties for the change.

A typical involuntary reissue session using FXI might look like this:

• Retrieve the PNR and confirm the airline-initiated disruption.
• Update the itinerary with the new flights or rerouting.
• Enter FXI to initiate the ATC Involuntary pricing process.
• Review the resulting pricing and confirm it reflects the involuntary conditions.
• Review the created TST with TQT or TQTC.
• Correct any element if needed using TTK or TTI.
• Continue the reissue and issue the new ticket with TTP.

Key takeaway: Use FXI only when the change is airline-caused. For voluntary changes, use FXQ or FXO. Preview with FXF or FXE before confirming.

When FXI fails, the error message usually points to one of the following causes. Match the message to the fix before retrying.

• FXP / FXX / FXB / FXR → standard pricing commands used for normal fares and voluntary changes.
• FXO → Confirmed Best Pricer pricing with TST creation for ATC reissue. Read the FXO guide.
• FXI → ATC Involuntary pricing used when the change was caused by the airline.
• TRF → refund processing, not reissue. Read the TRF guide.
• TTP / TTP/EXCH → ticket issuance and exchange commands used after the pricing step. Read the TTP guide.

Using FXI instead of a standard pricing entry ensures the itinerary is processed under the correct involuntary rules and accepted by ATC.

Explore the related Amadeus ATC reissue and TST commands below to complete your toolkit:

What does FXI do in Amadeus?

FXI initiates the ATC Involuntary pricing process for an eligible involuntary ticket reissue caused by an airline schedule change or cancellation.

Can I use FXI for a voluntary change?

No. FXI is specifically for involuntary situations where the airline caused the change. Voluntary changes use standard pricing commands such as FXQ or FXO.

What is the difference between FXI and FXO?

FXI handles involuntary pricing when the airline caused the change. FXO performs Confirmed Best Pricer pricing with TST creation for standard ATC reissues.

Why did FXI return an error even though the flight was cancelled?

The most common reasons are that the segment status does not show an involuntary code (UN / UC / US / NO / HX), the new itinerary is not yet stored in the PNR, or the PNR is not in an active ATC session. Fix the PNR state first, then re-run FXI.

🔖

Save This FXI Guide for Your Next Disruption

Schedule changes and cancellations never wait for a convenient moment. Bookmark this page so the FXI prerequisites, syntax and troubleshooting steps are always one click away — and explore our other GDS command guides to build your full ATC toolkit.

Press Ctrl + D (Windows) or ⌘ + D (Mac) to add it to your bookmarks.