

        📚 GDS Academy

        
            
                
                    Amadeus GDS Commands & Lessons | GDS Hub
                    35
                

            
                
                    Galileo GDS Commands & Lessons | GDS Hub
                    27
                

            
                
                    Sabre GDS Commands & Lessons | GDS Hub
                    20
                

                    

        
            🛠 Tools
            Airport Taxes Database
            Airports Database
            Farebase Generator
            Tax Checker
            Airline Special Services

Amadeus FS & FZ Commands: Miscellaneous Fare Info

A complete guide to the FS and FZ commands in Amadeus — how to add miscellaneous fare and payment-related information to a PNR.

Not every piece of fare information fits neatly into a tour code or a net remit entry. Sometimes you need to record a reference number from a corporate client, note who paid for the ticket, or attach a short piece of free-flow information that explains the fare arrangement. The FS and FZ commands exist for exactly this purpose. They add miscellaneous fare information to the PNR — short coded references with FS, and free-flow text with FZ. This guide explains what each command does, the correct syntax, and the situations where they should be used.

What Do the FS and FZ Commands Do?

FS and FZ are Amadeus GDS commands used to add miscellaneous fare information to a PNR.

Category: Fare Information.

These commands allow you to record additional fare-related information in the PNR, such as a reference number or details about who paid for the ticket. This information becomes part of the ticket record and is sent with the ticketing data to the airline and the BSP.

They are useful when a fare requires supporting information that does not fit into other fare elements — for example a corporate reference, a purchase order number, or a note that a third party paid for the ticket.

FS — Miscellaneous Fare Information

Use the FS command to add a short coded reference to the PNR:

FS123AC

This adds 123AC as miscellaneous fare information. The FS entry is ideal for short codes, reference numbers, or account identifiers that need to be recorded alongside the fare.

FZ — Free-Flow Miscellaneous Fare Information

Use the FZ command to add free-flow text to the PNR:

FZ TICKET PAID BY IBM

This adds TICKET PAID BY IBM as miscellaneous fare information. The FZ entry is best for readable notes, such as who paid for the ticket, the company that funded it, or any other explanatory text required by the fare agreement.

FS vs FZ — Which One to Use

FS → short coded references, account numbers, or identifiers — for example FS123AC.
FZ → free-flow text with spaces and full words — for example FZ TICKET PAID BY IBM.

Both serve the same purpose — recording fare-related information — but FS is for short codes and FZ is for readable text. Choose the one that matches the format required by the fare condition or the airline.

When to Use FS or FZ

Use FS or FZ when you need to record additional miscellaneous fare or payment-related information in the PNR. Typical scenarios include:

Recording a corporate account number or reference code for the fare.
Noting who paid for the ticket, such as a company or third party.
Adding a purchase order or internal reference number.
Recording free-flow text required by a specific fare rule.
Adding explanatory information requested by the airline or the corporate client.
Supporting a corporate fare with additional identifying information.

How FS and FZ Fit Into the Fare and Ticketing Workflow

A typical fare and ticketing session using FS or FZ might look like this:

Retrieve the PNR and confirm the fare requires supporting information.
Enter FS123AC or FZ TICKET PAID BY IBM as appropriate.
Verify the entry was accepted by the system.
Price the itinerary using FXP or another pricing command if not already priced.
Review the TST with TQT or TQTC to confirm the FS or FZ line appears.
Issue the ticket with TTP once everything is correct.

Tip: Keep FS entries short and coded, and use FZ only when the information genuinely needs to be read as text. Both entries appear in the ticket record, so they should be accurate and relevant to the fare.

If your office or the airline requires the information to be linked to a specific passenger, add the passenger association using /P followed by the passenger number.

Frequently Asked Questions

What does the FS command do in Amadeus?

FS adds miscellaneous fare information to a PNR, typically a short code or reference number such as FS123AC.

What does the FZ command do?

FZ adds free-flow miscellaneous fare information, such as a note about who paid for the ticket. For example FZ TICKET PAID BY IBM.

When should I use FS instead of FZ?

Use FS for short codes and reference numbers, and FZ when the information needs to be written as readable free-flow text with spaces and full words.

Conclusion

The FS and FZ commands are small but practical tools in Amadeus fare management. FS records short coded references such as FS123AC, while FZ records free-flow text such as FZ TICKET PAID BY IBM. Both add miscellaneous fare information to the PNR, supporting corporate fares, third-party payments, and fare rules that require additional identifying details. Use the one that matches the required format, verify the entry appears in the TST before ticketing, and pair them with FT, FXP, TQT, and TTP for a complete and accurate ticketing workflow.