Amadeus PNR Ticketing Mistakes That Trigger ADMs India

The most common Amadeus PNR errors Indian travel agents make — wrong SSR codes, fare-basis mismatches, late voids — and a practical guide to avoiding or

FlightGPT can make mistakes. Confirm flight & fare details before paying.

8 Amadeus PNR ticketing mistakes that trigger ADMs — and how Indian agents can contest or avoid each one (2026)

By Kabir Malhotra (Kabir Malhotra writes about how Indian travel buyers actually pay — UPI vs credit card vs forex card surcharges, reward-point math on the top travel credit cards, RBI tokenisation, EMI-on-flights and the small fees that compound across a year of bookings.) · Published · 13 min read

An ADM (Agency Debit Memo) is essentially the airline billing your agency for a mistake in how you handled a booking — and on Amadeus, a handful of specific errors generate the vast majority of Indian agents' ADMs. Here are the eight most common, and what you can actually do about each one.

TL;DR — what an ADM is and why it matters

An ADM (Agency Debit Memo) is a formal charge raised by an airline against a travel agency for a booking error, policy violation, or revenue discrepancy. Airlines issue ADMs through the BSP (Billing and Settlement Plan) — in India, administered by IATA. When you receive an ADM, the amount is automatically deducted from your BSP remittance in the next settlement cycle unless you formally contest it (raise an ADM dispute through IATA's ADMS tool) and win. ADMs can range from a few hundred rupees to amounts that match the full ticket value, depending on the nature of the error. Getting a grip on which Amadeus actions trigger them is one of the most financially significant skills an Indian agent can develop.

Mistake 1: Issuing a ticket on the wrong fare basis

The classic ADM trigger. In Amadeus, when you use the FXP command (fare quotation) and then issue the ticket with ET or TTP, the system stores the fare basis code alongside the PNR. If the fare basis you quoted does not match the actual fare the passenger travelled on — because the conditions changed, you queued the ticket too long after quoting, or you manually overrode the fare during ticketing — the airline's revenue audit will flag it.

Most common scenario: Agent quotes a fare in the morning (say, an MSAVER fare on IndiGo or a Y-class Air India fare), the client takes a few hours to decide, and by the time the agent re-prices and issues, the original fare class has sold out and the system has auto-repriced to a higher class. The agent does not notice the fare-class change, issues the ticket, and three months later receives an ADM for the fare difference.

How to avoid it: Always re-run FXP immediately before TTP. Never issue a ticket against a fare quotation more than a few minutes old — fare inventory is live. If you are using Amadeus' automatic ticketing queue, set a short re-price interval.

Can you contest it? Rarely successfully, unless you can prove a system error. The airline's audit data is typically conclusive on fare-basis mismatches.

Mistake 2: Missing or incorrect SSR codes

SSR (Special Service Request) codes are how agents communicate passenger requirements to airlines — meal preferences (VGML, HNML, MOML), wheelchair assistance (WCHR, WCHC), unaccompanied minor (UM), infant on lap (INF), and so on. On Amadeus, SSR entries go into the PNR using the SR command.

ADMs from SSR errors come in two flavours:

How to avoid it: Keep an updated reference list of the SSR codes for the airlines you ticket most frequently. For Air India, the SSIM (Standard Schedules Information Manual) and the airline's GDS ticketing guide have the definitive code list. Double-check infant bookings — an INF (infant without seat) entry that is missing or has the wrong date of birth relative to the passenger's travel date is a very common error.

Mistake 3: Late void — missing the ticketing deadline

In Amadeus, a ticket can be voided on the same BSP reporting day it was issued — this is the standard way to cancel a ticket you issued in error before the day ends. After the reporting day closes, voiding is no longer possible; you have to use refund procedures instead, which may attract cancellation penalties.

The ADM scenario: an agent issues a ticket, the client changes their mind, and the agent voids it the next morning thinking it is the same day. The BSP day has already rolled over, the void is rejected, but the agent does not notice — the ticket remains active, the airline settles it through BSP, and later raises a discrepancy notice when the refund that was never processed against the outstanding ticket.

How to avoid it: Know the BSP cut-off time for your country. In India, the BSP reporting day typically closes in the early morning hours. If you issued a ticket in the evening and the client calls the next morning, you may already be past the void window. Verify with your consolidator or BSP administrator the exact cut-off time.

Can you contest it? If you can demonstrate a system error or ambiguous confirmation of the void from Amadeus, you have a case. But straightforward late voids are typically upheld.

Mistake 4: Rebooking without reprice, triggering a fare violation

A passenger changes their travel date. You rebook the segments in Amadeus (cancel old segments, add new segments), but you do not reprice and reissue the ticket — you assume the original ticket covers the new travel and just save the PNR. The passenger travels on the new date. The airline audits the ticket, finds the fare was issued for a specific booking class on specific dates, and the new segments do not match — ADM for the fare difference, often plus an admin fee.

This is especially common with IndiGo, which uses dynamic yield management and where the same flight on a different date can be a completely different fare basis. Air India is somewhat more flexible on fare rules for certain cabin classes, but the principle applies across all carriers.

How to avoid it: Any date or itinerary change on an issued ticket must go through proper reissue (TT/reissue commands in Amadeus). Calculate the reissue penalty and any fare difference upfront, collect it from the client, and complete the reissue before the original travel date. Never just rebook segments without reissuing.

Mistake 5: Incorrect passenger name — NM entry vs passport mismatch

Airlines are increasingly strict on name matching, particularly after e-visa and digitised immigration processing made passport-vs-ticket mismatches easier to audit. In Amadeus, passenger names go in via the NM command. The error: agent enters name as 'SHARMA/RAJESH' but the passport reads 'RAJESH KUMAR SHARMA' — the middle name is dropped. On domestic flights within India, this has historically been forgiven. On international tickets, particularly to the UK, USA, UAE and Saudi Arabia, a significant name discrepancy triggers a check-in problem and potentially an ADM for the reissue cost the airline had to absorb.

How to avoid it: Always enter names exactly as they appear in the passport — no abbreviations, no dropping middle names on international tickets. For domestic bookings, confirm the airline's current name-match policy (IndiGo and Air India have both tightened this).

Contesting this ADM: Difficult if the mismatch is factual. Some ADMs in this category can be waived on first occurrence with a written explanation — worth submitting the dispute with evidence that the error was clerical and did not result in revenue loss.

Mistakes 6, 7 and 8: BSP error, credit card ADMs, and commission clawbacks

Three more patterns worth knowing:

Mistake 6 — BSP settlement errors: If the ticket amount in your BSP settlement file does not match the issued ticket value (due to currency rounding, a manual override you forgot to document, or a form-of-payment discrepancy), the airline raises a BSP error ADM. These are usually small amounts — ₹5–50 — but accumulate. Fix: reconcile your BSP submissions weekly, not monthly.

Mistake 7 — Credit card ADMs: When a passenger pays by credit card through the GDS (using a CC form of payment in Amadeus), some airlines charge a credit-card surcharge that must be collected and remitted. If the agent issues the ticket without collecting the surcharge, or applies an incorrect surcharge rate, an ADM follows. Air India and IndiGo have specific credit-card surcharge rules in their GDS fare filings — check the FCI (Fare Conditions Information) before issuing tickets on card.

Mistake 8 — Commission clawback ADMs: Airlines that have moved to zero commission (most domestic Indian carriers have) occasionally raise ADMs when they find a commission deduction in the BSP that was not authorised. This typically happens when agents use old-format ticketing entries from before commission was removed, or when a fare filing in the GDS has an incorrect commission rate in the CA (commission amount) field. Double-check that your Amadeus agency profile has the correct commission settings for each airline.

For a broader context on how to structure your agent operations to minimise these risks, see our guides on GST and commission income and using FlightGPT Partner for cleaner booking records. Also, FlightGPT's AI search is useful for quick fare benchmarking before committing to a GDS fare.

How to contest an ADM — the IATA dispute process

Every ADM received through BSP can be formally disputed. The process:

  1. Log into IATA's ADMS (Agency Debit Memo System) or your BSP-Link portal within the dispute period — typically 60 days from the ADM issue date. After this window closes, acceptance is automatic and the amount is deducted.
  2. Gather evidence: GDS transaction logs, client communication, the original PNR history (PNH command in Amadeus retrieves the full historical queue), any system error confirmations.
  3. Submit a dispute with a clear written explanation: Briefly state the nature of the error, why the ADM is incorrect or disproportionate, and attach evidence. Airlines review disputes on a rolling basis — response times range from 2 weeks to 2 months.
  4. If rejected, escalate to IATA BSP India or raise it as a formal complaint through your ARC/IATA agent association. Some BSP disputes go to a panel review.

Waiver requests (for ADMs that are technically valid but where the agent requests mercy) are handled separately and directly with the airline's GDS/revenue team — not through IATA. They work better when: the ADM is your first of this type, the amount is small, you have a strong volume relationship with the airline, and you write a clear letter acknowledging the error and explaining what process changes prevent recurrence. Akasa Air and Air India's revenue audit teams in India have historically been receptive to first-offence waiver requests — IndiGo is stricter. There is no guarantee, but it costs nothing to ask.

Frequently asked questions

What is an ADM in travel and why do Indian agents receive them?

ADM stands for Agency Debit Memo — a charge raised by an airline against a travel agency for a ticketing error, fare violation, or policy breach. In India, ADMs flow through the IATA BSP (Billing and Settlement Plan) and are automatically deducted from the agent's next BSP settlement unless disputed within 60 days. Indian agents typically receive ADMs for fare-basis mismatches, late voids, name errors and SSR omissions.

How long do I have to contest an ADM in India through BSP?

The standard dispute window is 60 days from the ADM issue date. After 60 days, the amount is automatically accepted and deducted from your BSP settlement. Log into the IATA ADMS tool or your BSP-Link portal as soon as you receive an ADM, even if you need more time to gather evidence.

Can I get an ADM waived by the airline?

Yes, airlines do waive ADMs, particularly for first-time offences or small amounts where the commercial relationship matters. A waiver request goes directly to the airline's BSP or GDS revenue desk — not through IATA. Write a brief letter acknowledging the error, explain the process change you have made, and attach the relevant PNR history. Air India and Akasa Air have been relatively open to first-offence waivers; IndiGo less so. There is no guaranteed outcome.

What Amadeus command should I run to check PNR history before disputing an ADM?

The PNH command in Amadeus (PNH followed by the record locator) retrieves the full transactional history of a PNR, including every command, queue entry, segment change and ticketing action with timestamps. This is your primary evidence document for any ADM dispute — export and save it as soon as you receive the ADM notice.

Does IndiGo pay commission to agents through the GDS in 2026?

IndiGo, like most Indian low-cost carriers, does not pay net commission through the GDS. Agents earn through service fees charged to clients, or through IndiGo's own travel-agent portal arrangements. Attempting to apply a commission deduction against an IndiGo ticket in the GDS will result in an ADM for the deducted amount — so ensure your agency profile has zero commission set for IndiGo in Amadeus.

What is the best way to avoid fare-basis mismatch ADMs on Amadeus?

Re-run FXP (fare quotation) immediately before every TTP (ticket issuance) — never issue against a quote that is more than a few minutes old. Fare class inventory can change within minutes on busy routes, especially for promotional fares on IndiGo and Akasa. Amadeus' FQBB (fare quote with booking basis) command can also flag whether the booked class still matches the quoted fare before you commit to issuing.