For an IATA-accredited agency, the Billing and Settlement Plan sits at the centre of cash flow, and it is also one of the least understood parts of the operation. Money moves on a fixed schedule whether or not your records are ready, and when your numbers and the airline's numbers disagree, the result is an Agency Debit Memo: a charge against your account that you must either pay or successfully dispute. This article explains what BSP settlement involves, why ADMs arise, and how disciplined reconciliation stops most of them before they are issued.
What the BSP actually does
The BSP is a clearing mechanism that sits between agents and airlines. Rather than every agent settling separately with every airline, sales are reported into the BSP, consolidated, and settled on a regular billing cycle. In the United States the equivalent is the ARC settlement system, which works on similar principles. The agent reports its sales, refunds and adjustments; the BSP totals the amount owed; and on the settlement date the money is collected, typically by direct debit, regardless of whether the agent agrees with the figure.
That last point is the one operators underestimate. Settlement is not a negotiation that waits for you. It runs to a calendar. If a discrepancy exists when the cycle closes, you settle the BSP's number and argue afterwards. This is why reconciliation cannot be a month-end afterthought; it has to keep pace with the billing cycle.
Why ADMs happen
An Agency Debit Memo is the airline's mechanism for recovering money it believes it is owed: an underpaid fare, a missed fare rule, an incorrect commission, a tax applied wrongly, or a ticket issued at a price that does not match the filed fare. ADMs are not inherently punitive; many are legitimate corrections. But a high volume of them is almost always a symptom of weak reconciliation rather than bad luck. The common causes are consistent across agencies.
- Fare and rule errors. A fare is calculated or loaded incorrectly, or a fare rule, such as advance purchase or routing, is breached at the point of ticketing.
- Commission discrepancies. The commission claimed does not match what the airline allows, often because a rate changed and the agency record did not.
- Tax and surcharge mistakes. Taxes are miscalculated, omitted or applied to the wrong portion of the fare.
- Refund and exchange errors. A refund is processed at the wrong value, or an exchange does not account for fare differences and penalties correctly.
- Reporting mismatches. The sale reported into the BSP does not match what was actually collected from the customer.
Notice that nearly all of these are detectable before settlement, if you are comparing your own records against the BSP file as it arrives rather than reacting to a memo weeks later.
What good reconciliation looks like
Reconciliation, properly done, is the continuous matching of three things: what you sold and recorded internally, what you collected from the customer, and what the BSP says you owe. When all three agree, the cycle is clean. When they diverge, the divergence is the early warning of an ADM, and catching it early is the difference between a quiet correction and a dispute after the money has gone.
The discipline rests on a few habits. Reconcile against the BSP billing file every cycle, not only at month-end. Match at the ticket level, so a single mispriced fare is visible rather than buried in a total. Keep fare rules, commission terms and tax treatment current, because most ADMs trace back to a record that drifted out of date. And treat every ADM you do receive as feedback: categorise its cause and fix the process that allowed it, so the same class of error does not recur.
The cost of getting it wrong
The direct cost of an ADM is the amount charged, but the indirect cost is larger. Each ADM consumes staff time to investigate and dispute, the dispute window is short and unforgiving, and a pattern of memos can attract scrutiny of your accreditation. Cash flow suffers too, because settlement collects the disputed amount immediately and you only recover it if the dispute succeeds. Prevention is cheaper than every part of that process.
How automation prevents most ADMs
Manual reconciliation struggles with the BSP for a simple reason: volume and timing. Matching hundreds of tickets against a billing file by hand, every cycle, is slow enough that errors are usually found after settlement rather than before. Automation changes the timing. When your sales, customer collections and supplier costs all live against the same booking record, the system can compare them to the incoming BSP file automatically and flag any ticket where the numbers do not agree, while there is still time to act.
This is where a unified Travel ERP earns its place in finance. Because a platform such as Flightna holds the fare, the taxes, the commission and the collected payment against one booking, reconciling against the BSP becomes a matter of confirming a match the system has already attempted, and reviewing only the exceptions. The fare errors, commission mismatches and reporting differences that become ADMs are surfaced as discrepancies before the cycle closes, which is precisely when they can still be corrected at no cost.
ADMs will never reach zero; some are legitimate and unavoidable. But the majority are preventable, and they are prevented not by working harder at month-end but by reconciling continuously, at ticket level, against the settlement file itself. Get the timing and the granularity right, and the memos that used to arrive as surprises become discrepancies you resolved weeks earlier.