An Agency Debit Memo (ADM) is an invoice from an airline to a travel agency for money the airline believes it should have collected — usually because of a booking error, a fare-rule violation, or a ticketing mistake. It is not a simple warning. It is processed through the Billing and Settlement Plan (BSP) or ARC, and if you ignore it, the amount is settled against your agency.
The good news: almost every ADM is preventable. The causes repeat, the audit rules are known, and the fixes are operational rather than complicated. This guide covers the 14 most common triggers, what an ADM can cost, how the dispute process works, and the checks that keep them out of your BSP statement.
ADM = airline charges the agency. The airline can issue one within 9 months of the final travel date (or 9 months from a refund), and the agency usually has 14–15 days to dispute it through BSPLink or ARC before it is settled. Prevention comes down to five controls: correct fare, correct class, confirmed segments, clean refunds, and a daily queue check.
In this guide
What is an Agency Debit Memo?
An ADM is a debit document issued by an airline to an agency, usually through the BSP or ARC. It tells the agency that a specific transaction was not compliant and that the airline is recovering the difference. The amount might be a fare difference, an under-collected tax, a commission recall, a refund adjustment, or an administrative fee — depending on the carrier’s policy.
It is important to separate an ADM from a penalty in the legal sense. An ADM is a recovery invoice tied to a transaction. That is why the airline must show a reason and a calculation, and why the agency has a limited window to dispute it.
ADM vs ACM
| Document | Direction | Purpose |
|---|---|---|
| ADM — Agency Debit Memo | Airline → agency | Recover money the airline believes the agency owes |
| ACM — Agency Credit Memo | Airline → agency | Credit the agency when the airline owes money |
Most agencies only pay attention to ADMs, but ACMs matter too. If you spot an over-collection or a valid credit, the ACM is the mechanism that gets the money back. A clean reconciliation process catches both directions.
How the ADM process works
- The airline audits a transaction. The trigger can be an automated fare audit, a refund review, a travel audit, a chargeback, or a pattern flagged by the carrier’s revenue integrity team.
- The airline raises the ADM. It is issued electronically, usually through BSPLink or ARC, with a reason code, the ticket or document number, and the amount claimed.
- The agency is notified. The ADM appears in the agency’s BSP/ARC statement or memo queue. This is not a request for information — it is a debit.
- The agency reviews and disputes, or accepts. Under IATA Resolution 850m, the agency has a maximum of 15 days to review and dispute before the ADM is submitted for settlement. Some airlines apply 14 days. Always check the local BSP rule and the carrier’s ADM policy.
- Settlement. If the dispute is rejected or not submitted, the amount is included in the BSP/ARC settlement. If the dispute succeeds, the ADM is reduced or cancelled.
The timing limits are the part agents miss most often. The airline has 9 months from the final travel date to issue an ADM for a sale, and 9 months from the refund date for refund-related ADMs. That means an error from last season can still appear on this month’s statement. The full framework is in IATA Resolution 850m.
Do not ignore an ADM. Missing the dispute window does not make the debit disappear. It simply moves to settlement, and recovering the money afterwards becomes much harder.
The 14 most common ADM causes
The exact list varies by airline. American Airlines, for example, explicitly monitors churning, hidden city, inactive segments, invalid waiver codes, married-segment violations, and O&D manipulation. Air France and KLM focus heavily on passive segments and passenger contact details. Use the list below as a risk map, then read each carrier’s ADM policy for the specific triggers.
Reservation Booking Designator (RBD) violations
An RBD violation happens when the booking class in the reservation does not match the class on the issued ticket. Common triggers: rebooking after a schedule change without repricing, manually overriding the fare, or pricing into a lower class than the one confirmed. The airline released inventory in one class and received revenue from another.
Prevent: reprice after every segment change, compare the segment RBD with the TST, and avoid manual class overrides. The Amadeus pricing guide covers the reprice workflow.
Fare and sales rule violations
Airlines enforce advance purchase, minimum and maximum stay, travel and sale dates, child and infant discounts, routing, airline combinations, taxes, and surcharges. Invalid waiver codes and altered endorsement text also fall here. A common example is using a schedule-change waiver when no schedule change occurred.
Prevent: read the fare rules before ticketing, use automated pricing, and never invent or reuse a waiver code. The FQD penalties guide shows how to check the conditions.
Ticketing without a confirmed booking
Issuing a ticket on a waitlisted, unconfirmed, or holding segment is a violation when the fare requires confirmed space. The agency collects the fare, but the passenger has no confirmed seat — and the airline carries the operational risk.
Prevent: check segment status before issuing, confirm the booking, and never ticket a waitlist to meet a deadline. See the TTP issuance guide for the pre-ticketing checks.
Refund and reissue violations
Duplicate refunds, incorrect refund calculations, refunding a used or no-show ticket, missing passenger consent, wrong form of payment, tax refund errors, and reissues without collecting the fare difference are all recoverable by the airline.
Prevent: use automated refund records, verify the TST and refund calculation, keep passenger consent, and follow the fare rules for the reissue. The manual refund guide and the revalidation vs reissue guide cover both workflows.
Travel audit discrepancies
Airlines compare the ticketed itinerary with the itinerary actually flown. Differences in travel dates, booking class, routing, or partial use can lead to an ADM. Hidden-city travel and no-show segments often surface here, even when the ticket itself looked valid at issuance.
Prevent: advise passengers that unused segments can affect the fare, rebook changes correctly, and keep PNR history evidence. The PNR history guide shows how to reconstruct what happened.
Duplicate or excessive bookings (churning)
Creating multiple bookings for the same passenger on the same flight, or repeatedly cancelling and rebooking the same itinerary to hold inventory, is treated as system abuse. It blocks seats other agencies could sell and distorts the airline’s inventory data.
Prevent: keep one active PNR per passenger per trip, clean duplicates before ticketing, and use waitlist or hold functions correctly. The XE cancel elements guide helps remove duplicates cleanly.
Fictitious or speculative bookings
Bookings with fake passenger names, invented itineraries, or no genuine intent to travel — often used to block inventory or test availability — are strictly prohibited. Group holds without real passenger details fall into the same risk area.
Prevent: use real passenger data, release unused holds before the deadline, and follow the airline’s group deposit and name rules.
Inactive or unticketed bookings
Bookings left active past the ticketing time limit, inactive segments that were never removed, and no-shows that were not cancelled can all trigger an ADM. The airline sees inventory held without revenue, or a segment that does not reflect the passenger’s actual journey.
Prevent: review the TTL queue daily, cancel bookings you cannot ticket, and delete inactive segments. The DL command guide covers inactive segment deletion.
O&D and MCT violations
Origin-and-destination manipulation, married-segment violations, forced availability, point-of-commencement tricks, and bookings that breach minimum connecting time are all ways of bypassing the airline’s inventory logic. They are monitored closely because they can distort revenue and create unsafe connections.
Prevent: book the journey the passenger actually intends to fly, respect MCT, and never split or force segments to obtain a class that was not available for the real O&D.
Passive booking misuse
Passive segments should be used only for ticketing purposes. Using them to hold inventory, meet GDS productivity targets, bypass fare rules, or create a segment that does not exist in the airline’s system is prohibited by many carriers, including Air France and KLM.
Prevent: use passive segments only when the ticketing workflow requires them, ticket immediately, and cancel or remove them if the ticket is not issued.
Cross-border and back-to-back ticketing
Cross-border ticketing (buying in a market to use a lower fare) and back-to-back ticketing (overlapping tickets to bypass a Saturday-night or minimum-stay rule) are fare-rule workarounds. Airlines audit both, and the ADM can recover the full fare difference.
Prevent: follow the fare’s residency and routing conditions, do not split tickets to avoid stay requirements, and document any genuine exception before ticketing.
Excessive ticket voids
A high void ratio can indicate weak ticketing controls, repeated pricing errors, or misuse. Airlines and BSPs monitor void patterns, and a persistent anomaly can trigger a review or an ADM depending on the carrier’s policy.
Prevent: review the PNR and TST before issuing, void only within the permitted window, and monitor each agent’s void report. The void vs refund guide explains the difference.
Use of automation scripts
Robotic macros, screen scrapers, and scripts that manipulate bookings, availability, or queues are prohibited by GDS and airline terms. They can create inventory abuse at scale, so the response is often stronger than a single ADM — including access restrictions.
Prevent: use approved APIs and tools, avoid unauthorized automation, and train staff on what counts as a prohibited script.
Missing passenger information
Incomplete contact details — no phone number, no email, missing APIS or document data — can trigger an ADM with carriers that require complete passenger records. It also creates operational problems when the airline needs to reach the passenger about a schedule change.
Prevent: collect a mobile number and email at booking, add the contact to the PNR, and verify document data before ticketing. The passport data guide covers the document side.
What an ADM can cost
The amount on an ADM is not always just the fare difference. Depending on the carrier and the violation, it can include:
- The under-collected fare — the difference between what was ticketed and what should have been charged.
- Taxes and surcharges that were missed or miscalculated.
- Commission recall when the agency was paid commission on a transaction that is later reversed.
- An administrative or handling fee applied per ADM by some airlines.
- Chargeback amounts where the ADM relates to a card dispute.
- Internal cost — the staff time spent investigating, disputing, and correcting the booking.
Repeated ADMs matter beyond the individual amounts. A pattern of violations can lead to closer airline scrutiny, tighter ticketing permissions, or an agency review. The financial hit is real, but the operational reputation cost is often higher.
How to dispute an ADM
Disputing is not about refusing to pay. It is about checking whether the airline’s calculation and reason are correct. A valid dispute is built on documents, not opinions.
- Log the ADM immediately. Record the ADM number, ticket number, reason code, amount, and deadline in your ADM tracker.
- Read the reason and the calculation. Confirm which transaction is being charged and whether the amount matches the fare rule the airline cited.
- Pull the evidence. PNR history, TST history, the fare rule display, the ticket, the refund record, the waiver code, boarding passes, and any passenger correspondence.
- Check the deadline. Submit through BSPLink or ARC within the airline’s window — usually 14–15 days from issuance. Late disputes are much harder to recover.
- Write a specific dispute. State the fact that is wrong, attach the evidence, and reference the fare rule or waiver. Do not send a generic “please waive” request.
- Track the response. Airlines often take up to 60 days to reply. If the dispute is rejected and the ADM is valid, settle it and fix the root cause.
Chargeback-related ADMs follow separate rules. Under IATA card-sales rules, an ADM issued because of a chargeback may not be eligible for the normal dispute process. Handle those through the card chargeback workflow, not the standard ADM dispute.
The ADM prevention system
Prevention is not a single checklist. It is a rhythm: checks before ticketing, a daily queue review, a weekly reconciliation, and a monthly audit. The agencies with the lowest ADM rates are not the ones with the best dispute writers — they are the ones with the cleanest booking process.
Before every ticketing
- Passenger name matches the travel document and the loyalty card.
- Segment status is confirmed (not waitlisted or holding).
- Booked RBD matches the priced RBD.
- Fare rules, taxes, and surcharges are checked.
- Refund and reissue conditions are understood before the sale.
- Contact details and required documents are in the PNR.
Daily
- Clear the ticketing time-limit queue and cancel bookings you cannot ticket.
- Process schedule-change queues before the airline’s deadline — the QE queue guide covers placement and processing.
- Remove inactive segments and duplicate PNRs.
- Check new ADMs and log the dispute deadlines.
Weekly
- Reconcile voids, refunds, and reissues against the BSP/ARC report.
- Review the ADM inbox and group the causes by type.
- Check agent-level void and refund patterns.
- Confirm that schedule changes were reissued with the correct waiver code.
Monthly
- Audit a sample of PNRs against the tickets issued.
- Review the top three ADM causes and update the training material.
- Re-read the ADM policies of your highest-volume airlines — they change.
- Share the numbers with the team; what gets measured gets fixed.
Pro tip: keep a one-page “fare rule note” for your top 20 routes and fares. Most ADMs come from the same handful of conditions — advance purchase, stay requirements, refundability, and routing. A shared note beats re-reading the same rule under time pressure.
ADM prevention checklist
- Fare rule checked before quoting and before ticketing.
- RBD on the segment matches the RBD in the TST.
- Segment confirmed before issuance.
- Passenger name and contact details complete.
- Waiver code valid for the actual disruption.
- Refund or reissue calculated correctly, with consent.
- No duplicate PNR, inactive segment, or passive misuse.
- No hidden-city, back-to-back, or O&D manipulation.
- Void and refund reports reviewed weekly.
- ADM deadlines tracked and disputes filed on time.
Summary
An Agency Debit Memo is avoidable when the booking process is disciplined. The biggest risks are mismatched booking classes, misapplied fare rules, ticketing unconfirmed segments, refund and reissue errors, duplicate or inactive bookings, and inventory manipulation. Check the fare and the RBD before ticketing, keep the PNR clean, process queues daily, and dispute only with evidence — within the 14–15 day window. The airline has nine months to find the error; your best defence is to catch it before the ticket is issued.
Read Also
How to add contact details in Amadeus, Galileo, Sabre
How to Master Amadeus Encode & Decode Commands
How to Master Galileo Encode & Decode Commands
Frequently asked questions
What is an Agency Debit Memo (ADM)?
An ADM is an invoice from an airline to a travel agency, usually processed through BSP or ARC, to recover money lost through a booking error, fare-rule violation, refund mistake, or ticketing non-compliance.
How long does an airline have to issue an ADM?
Under IATA Resolution 850m, an ADM for a sale must be issued within 9 months of the final travel date. For refunds, the limit is 9 months from the date the refund was processed by the agency.
How long does an agency have to dispute an ADM?
Typically 14–15 days from issuance, before the ADM is submitted for BSP settlement. The exact window depends on the airline and the local BSP, so check both.
What is the difference between an ADM and an ACM?
An ADM debits the agency — the airline is recovering money. An ACM credits the agency — the airline owes money, for example after an over-collection or a valid adjustment.
Can an ADM be waived?
Yes, if the airline made the error or the agency can prove the transaction was compliant. Waivers are based on evidence: PNR history, fare rules, waiver codes, tickets, and correspondence. A valid ADM is rarely waived just because the agency asks.
Do all airlines issue ADMs for the same reasons?
No. The broad categories are similar, but each carrier publishes its own ADM policy and priority areas. Some focus on passive segments, others on O&D manipulation, invalid waivers, or contact details. Read the policy for your top carriers.
How can a travel agency reduce ADMs?
Train agents on fare rules, verify RBD and segment status before ticketing, clean queues daily, reconcile refunds weekly, track ADM deadlines, and audit a sample of PNRs every month. Most ADMs come from a small number of repeat causes.