Short answer: an ADM (Agency Debit Memo) is a charge an airline raises against a travel agency through the IATA BSP to recover money it believes the agency owes: usually a fare or commission error, a refund processed incorrectly, or misuse of the booking system. ADMs are governed by IATA Resolution 850m, which requires the airline to explain the charge and gives the agency a defined window to dispute it before it is billed. Most ADMs are preventable, because most of them are triggered by a small set of repeatable mistakes.
What an ADM is (and what an ACM is)
When an IATA-accredited agency issues tickets for an airline, the money flows through the Billing and Settlement Plan rather than through direct invoices. If the airline later finds that it was underpaid on a transaction, it does not send the agency an invoice: it raises an Agency Debit Memo, which flows through BSPlink into a subsequent BSP billing and is collected with the agency's normal remittance. The mirror document is the ACM, the Agency Credit Memo, which returns money to the agency when the correction runs the other way.
The important structural point: an ADM is not a fine handed down by IATA. It is a claim by one airline against one agency, using the BSP as the collection channel. IATA provides the plumbing and the rulebook; the airline decides whether to raise the memo, and the agency decides whether to accept or dispute it. If you are new to how the settlement side works, read our guide to BSP reconciliation first.
The rulebook: IATA Resolution 850m
IATA Resolution 850m sets out when and how ADMs may be used. The points that matter most in practice, phrased generally because the text is amended from time to time:
- ADMs must relate to specific transactions and state a reason the agency can check against the fare rules or its records.
- Airlines are expected to publish an ADM policy so agencies know what they charge for and any minimum amounts or administration fees they apply.
- ADMs must be raised within the time limits in the resolution; for example, debits relating to refunds must be processed through the BSP within nine months of the refund. Older claims are handled directly between airline and agency, outside the BSP.
- Agencies get a defined review window after an ADM is issued, before it is included in a billing, in which they can dispute it through BSPlink.
- Disputed ADMs are suspended from billing while the airline investigates the dispute.
Always check the current text of Resolution 850m and the individual airline's published ADM policy; both are the authoritative sources, and the review and dispute periods are implemented slightly differently from market to market.
The common causes of ADMs
Airlines audit agency sales with automated fare-audit systems, so ADMs cluster around mistakes a machine can detect:
| Cause | What actually happened |
|---|---|
| Fare rule violations | A fare was sold without meeting its conditions: minimum stay, advance purchase, ticketing deadline, routing or booking class did not match the fare basis. |
| Incorrect refunds | A refund calculated without the cancellation penalty, refunding non-refundable taxes, or refunding a partially used ticket at the wrong residual value. |
| Commission errors | Commission taken at a higher rate than the airline files for that fare, market or ticket designator. |
| Churning | Repeatedly booking and cancelling the same itinerary to hold seats or reset ticketing time limits. GDS booking behaviour is audited and billed back. |
| Booking abuse | Duplicate bookings, fictitious or speculative names, hidden-city or back-to-back ticketing practices prohibited by the fare rules. |
| GDS cost recovery | Bookings made in a higher-cost channel than the airline permits for that fare, or segments left unticketed past the deadline. |
| Chargeback pass-through | A cardholder chargeback on a ticket the agency sold, passed back to the agency under the form-of-payment rules. |
The dispute process, step by step
A workable internal process looks like this. First, log every ADM the day it appears in BSPlink and attach it to the original booking, ticket and agent. Second, check the airline's stated reason against the fare rules as they were on the ticketing date, your PNR history and your refund calculation; the GDS fare rules display and ticketing history are your evidence. Third, decide inside the review window: accept memos that are simply right, dispute the ones where your records support you, and dispute with specifics, quoting the fare rule paragraph, the ticket number and the calculation, not a general objection. Fourth, if the airline rejects a dispute you still believe is wrong, escalate through the airline's published ADM contact and, where it applies in your market, the industry disputes process your local IATA office can point you to.
Two practical rules of thumb from agency finance teams: never let a memo sit unread until the billing, and never dispute everything on principle, because an agency that disputes indiscriminately loses credibility on the disputes that matter.
Prevention: engine rules beat human vigilance
Most ADM causes are policy violations a computer can catch at booking time, which is why prevention belongs in the booking flow rather than in training slides. In a flight booking engine or agent desktop, that means hard rules: block ticketing when the booking class does not match the fare basis, enforce ticketing time limits with automatic queue handling instead of letting segments expire, cap rebooking cycles on the same passenger and itinerary so churn never reaches audit thresholds, calculate refunds through the engine with penalties and non-refundable taxes applied automatically, and validate commission against the rate actually filed for the fare.
The same applies on the trade side: a B2B portal that lets sub-agents book raw GDS content without rules is an ADM generator, because the accredited agency carries the memo while the sub-agent keeps the sale. Rules travel with the platform, which is why agencies moving from manual GDS work to a governed engine typically see their ADM exposure fall. Building those controls is part of what we do in travel agency software and travel ERP projects.
Tracking ADMs like a finance metric
Treat ADMs as a measurable cost of sale, not as random weather. The metrics that matter: ADM count and value per thousand tickets, split by airline, by cause and by agent or channel; dispute rate and dispute win rate; and time from ADM issue to resolution. An ERP that links every memo to its booking produces these numbers as a by-product. The pattern they reveal is usually concentrated: a handful of causes, a handful of airlines, sometimes a single office, producing most of the value. Fix those and the curve bends. Refund-related memos deserve their own line, because refund and reissue handling is a discipline of its own; we cover it in our guide to airline refunds and reissues.
This article is general information about travel technology and online marketing. It is not legal, tax or financial advice, and advertising platform policies change often. Check the current policy documents and take professional advice for your own situation.