Skip to content
Blog

How to avoid airline ADMs when sub-agents sell your fares

Tekravel Editorial
Written with the help of AI

The memo shows up in BSPlink for a ticket issued weeks ago. Your ticketing desk issued it, under your IATA number, so it is your memo. But nobody on your desk sold that fare. A sub-agent did — a small agency that took the price from a message you sent on Monday, quoted it to a family on Tuesday, and asked you to issue on Wednesday after the advance-purchase window had already closed. If you want to avoid airline ADMs as a consolidator, that chain is where to look, because the mistake was made two steps before anybody touched the ticket.

That is the argument of this piece: for a consolidator who resells, most agency debit memos are a distribution problem. The ticketing desk is where they surface. It is rarely where they start.

Where the memos actually come from

Airlines word their ADM policies differently, but the reasons memos are raised fall into a handful of groups. What matters for a consolidator is the third column — who, in your chain, created the problem — because that decides where a control has to sit.

GroupTypical triggerUsually created byWhere to stop it
Fare rule breachesAdvance purchase missed, minimum stay ignored, wrong passenger type, a fare used on a route it does not coverThe person who quoted the fare without its conditionsAt the point of sale, before issuance is requested
Booking class mismatchTicket priced in one class while the segment is held in anotherManual repricing, or a rebooking that did not repriceAt issuance, by checking price against segment
Reservation hygieneChurning (repeated cancel and rebook), duplicate bookings, passive or speculative segments, unticketed segments left to expireSub-agents holding seats "just in case"In the reservation, automatically
Pricing and tax errorsTaxes dropped or miscalculated, fare construction wrong after a manual changeYour own desk, most of the timeAt issuance
Commission and incentive claimsCommission claimed on a net fare, a tour code used outside its agreementYour back officeIn settlement
Refunds and exchangesNon-refundable components refunded, penalties not collectedWhoever processed the change in a hurryAt the refund, with the original rules in hand

Read the third column again. Only two of the six groups start on your ticketing desk.

Why fare rules have to travel with the fare

A net fare is a price plus a set of conditions. When a consolidator forwards a fare to sub-agents as a line in a chat or a row in a spreadsheet, the price survives the trip and the conditions do not. The sub-agent sees a number for a route and a month. They do not see that the fare needs ticketing within a set number of days of booking, that it is not valid for a child, or that it only works on the outbound flight the airline filed it for. They sell it in good faith, and the memo is the airline's way of collecting the difference between what was sold and what the rules allowed.

Telling sub-agents to "check the rules" does not fix this. They cannot check what they were never given, and the honest ones will ask you, on the phone, every time — which turns your ticketing desk into a help line and still misses the ones who do not ask.

The fix is structural: the fare and its rules have to reach the sub-agent as one object, at the moment they decide to sell it. In practice that means the sub-agent searches and books in a portal that carries the fare's conditions alongside the price, rather than copying a price out of a message. We wrote about the mechanics of getting net fares out of chat groups in how to distribute net fares to sub agents; the ADM argument is the same argument seen from the other end. A fare sheet that goes stale by lunch is a sales problem. A fare sheet that loses its rules is a liability with your IATA number on it.

There is a second benefit people underrate. When the rules travel with the fare, the sub-agent's acceptance of them is recorded at the moment of sale. That record is half of your defence when a memo arrives.

The audit trail that lets you push a memo back

You will not prevent every memo. Some will be wrong — raised on a fare the airline itself filed badly, on a schedule change it made, on a segment its own system cancelled. Those are disputable, but only inside the dispute window the airline's policy sets, and only with evidence. A consolidator without records pays memos it could have contested, because assembling the story from chat history takes longer than the window allows.

Keep, for every ticket:

  • Who booked it — which sub-agent, which of their staff.
  • The fare and the rules as displayed at the time of booking, not as they read today.
  • The PNR history, including every change and who made it.
  • The issuance record: when, by whom, priced in which class.
  • Any exchange or refund, with the rules used to calculate it.

With that, a memo becomes a question you can answer in minutes: was this the airline's error, ours, or the sub-agent's? The first you dispute. The second you fix in your process. The third you pass on.

What to automate, and what to police

Some ADM causes are mechanical and should never depend on someone remembering. Others need judgement, and automating them just moves the error somewhere less visible. The split we would draw:

  • Automate: cancelling unticketed segments before the ticketing time limit; flagging duplicate bookings for the same passenger and flight; refusing issuance when the priced class does not match the booked class; carrying fare rules into the sub-agent's booking flow; recording who booked and who issued every ticket.
  • Police: name corrections and passenger-type changes; manual repricing; exchanges and refunds on fares with complex penalties; any sub-agent whose bookings keep producing memos.

The last item matters more than it looks. Memos cluster. A small number of sub-agents usually account for most of them, often through one repeated habit — holding seats for clients who have not paid, or rebooking the same flight to keep a fare alive. Reviewing memos by sub-agent, rather than one at a time, turns that pattern into a conversation you can have with a named agency.

And when the conversation does not work, the cost has to land on the account that created it. That is easier when sub-agent credit limits and settlement invoicing are part of the same system that took the booking, so a memo attributable to an agency can be charged back on its next settlement instead of chased by email. We covered how to set those terms in sub agent credit limit management.

What one memo costs you if you get it wrong

The fare difference is only the visible part. Many airlines add an administrative fee per memo on top. Your staff spend time reading it, finding the booking and deciding whether to dispute. You settle through BSP on the airline's timetable, then try to recover the money from a sub-agent on yours — and if that agency has stopped trading with you, or never accepted the rules in writing, the memo is simply yours.

Repetition is worse than any single memo. A pattern of the same violation from the same IATA number is the kind of thing that leads an airline to look harder at everything you issue. For a consolidator whose business is the airline relationship, that is the real exposure.

A distribution problem, solved in distribution

Better ticketing checks catch the two groups that start on your desk. The other four are settled earlier: by giving sub-agents the fare and its rules together, by recording what they saw and accepted, and by tying memos back to the account that caused them. If you run a network of sub-agents and want to see how a consolidator account brings booking, credit and settlement under one roof, the consolidator page sets out what it includes.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.