Logo

Agency Debit Memos: The Hidden Cost to TMC Margins

Alister Harris
2026-09-03

The Debit Memo Problem, a joint Executive Insight from Lokulus CEO Alister Harris and Agentivity CEO Riaan van Schoor on reducing avoidable Agency Debit Memos in TMC operations

The Debit Memo Problem: Where Travel Management Companies Lose Their Margin

Agency Debit Memos are a familiar frustration for Travel Management Companies. But viewed as an operational and margin problem rather than an administrative one, their impact looks very different.

A joint Executive Insight by Alister Harris, CEO of Lokulus, and Riaan van Schoor, CEO of Agentivity.

Download the complete Executive Insight for the detailed analysis of what ADMs really cost UK TMCs, why current processes fail to catch them in time, and how better monitoring and business orchestration can prevent avoidable charges.

Download the full Executive Insight

Or keep reading for the key findings.

Ask anyone who runs a TMC about Agency Debit Memos (ADMs) and you tend to get the same tired sigh. Everyone knows what they are. An airline decides a fare rule was broken or a ticketing deadline was missed, and a few weeks later a charge lands through the BSP with your agency's name on it.

One memo might be a couple of hundred pounds and a minor irritation. The problem is that they don't arrive alone. They arrive week after week, across consultants, bookings and carriers, creating a steady drain on margin.

What makes that particularly frustrating is how many are potentially preventable. In many cases, the information needed to avoid the charge was already present in the booking data before the deadline.

The problem wasn't knowing.

It was turning that knowledge into action in time.

How much do Agency Debit Memos really cost TMCs?

There is no published UK-wide figure for ADM costs, so the full paper models the potential exposure using UK business travel spend and international memo-intensity benchmarks.

That modelling puts gross ADM exposure across UK TMCs at approximately £14 million to £44 million a year, with a central estimate in the mid-£20 millions.

Against total client travel spend, that may look relatively small. Against TMC economics, it is anything but.

Based on published TMC take-rates and margins, a memo load of that intensity could equate to approximately 1.5–3.3% of gross revenue and 8–13% of EBITDA – before accounting for the staff time spent investigating, disputing, reconciling and reporting on ADMs.

That's why ADMs should be viewed as a margin problem disguised as an administrative overhead.

And the charge itself is only part of the cost.

There is the skilled time spent investigating and challenging memos. There are charges that could have been disputed but age out because nobody reaches them within the dispute window. Then there is the ongoing reconciliation, reporting and airline liaison that gradually becomes accepted as simply another cost of doing business.

Once a loss becomes expected, organisations stop asking whether it was necessary.

Why do avoidable ADMs happen?

The causes of Agency Debit Memos are surprisingly ordinary.

Commission errors. Incorrect fares or taxes. Refund and exchange issues. Missed ticketing deadlines. Schedule changes left unworked. PNR housekeeping. Bookings that disappear from a GDS queue while they still require action.

These aren't usually dramatic failures or difficult judgement calls.

They're everyday tasks competing for attention inside a busy travel operation.

A ticketing time limit comes and goes while a consultant is dealing with an urgent traveller issue. An airline schedule change lands in a queue but isn't picked up quickly enough. A booking that still needs action gets removed from the queue and disappears from view.

The common thread isn't carelessness.

It's time pressure and prioritisation.

Consultants can't spend their days watching every GDS queue. They should be serving travellers. Yet traditional processes often still rely on somebody spotting the right booking, understanding what needs to happen and acting before the deadline.

Working harder doesn't solve that problem at scale.

A better coordinated process does.

The warning was often there all along

This is the part that should make any TMC operations director pay attention.

In many avoidable ADM scenarios, the information needed to prevent the memo already existed hours or days before the charge appeared.

A GDS queue contains a live stream of events that can eventually become ADMs: ticketing deadlines, airline schedule changes, changing segment statuses and supplier housekeeping requirements.

But simply having the signal isn't enough.

Bookings can be removed from queues while they still require action, and even when the warning remains visible, somebody still needs to understand what it means, prioritise it against everything else and ensure the right action happens in time.

The gap is therefore not simply one of information.

It's the gap between knowing and doing.

And that's where monitoring and business orchestration come together.

From monitoring bookings to orchestrating action

Preventing avoidable ADMs requires two things to happen consistently.

First, a TMC needs to know the state of every booking, what the supplier requires and when action needs to happen.

This is where Agentivity provides visibility beyond simply reading a GDS queue. Across a TMC's booking channels, Agentivity continuously monitors each booking and identifies the specific supplier requirement attached to it – including bookings that have dropped off a queue.

The second job is making sure something actually happens with that information.

That's where Lokulus provides the business orchestration layer.

Tasks identified by Agentivity can be brought into Lokulus and prioritised alongside work arriving from travellers, suppliers and internal systems. Routine work can be handled automatically, while genuine exceptions are sent to the right consultant with the relevant context attached.

Put simply:

Agentivity knows what needs to be done. Lokulus makes sure it happens.

That means ticketing deadlines can be acted on before they lapse, schedule changes can be processed as they arrive and high-risk routine work doesn't depend on a human having a free moment at exactly the right time.

The aim isn't to ask consultants to work harder.

It's to turn information the operation already has into action more consistently.

The business case for TMCs

Unlike many transformation projects, the starting point for the business case is relatively straightforward.

A TMC already knows what ADMs cost last year: the charges received, the disputes won, the ones paid and, with a little more investigation, the staff time spent managing them.

Improving monitoring and orchestration can attack that cost in several ways at once. Fewer memos should be raised because deadlines and changes are acted on earlier. More incorrect memos can be challenged because the evidence is available and disputes don't age out. And consultants spend less time firefighting queues and managing preventable problems.

Crucially, none of this requires replacing the technology estate.

The GDS, mid-office systems and booking tools remain in place. Monitoring and orchestration sit across them, connecting information to action.

For a TMC wanting to test the approach, the starting point can be one queue that is visibly costing money – often the ticketing time limit queue – rather than a multi-year transformation programme.

Three questions every TMC should ask

As pressure on TMC margins continues, preventable leakage deserves more scrutiny.

Start with three questions:

  1. What did ADMs actually cost us last year – including staff time and the memos we didn't have time to dispute?
  2. Who or what works our GDS queues today, and what happens when those queues become overwhelmed?
  3. How much time passes between a booking being flagged for action and somebody actually doing something about it?

That distance between the signal and the action is where much of the ADM problem lives.

The data is already arriving.

The opportunity is to make sure it becomes the right action, every time.

Frequently Asked Questions

How big is the ADM problem for UK Travel Management Companies?

There is no published UK-wide figure, so the total has to be modelled. The analysis in the full Executive Insight triangulates UK business travel spend against international memo-intensity benchmarks, putting estimated gross ADM exposure across UK TMCs at approximately £14 million to £44 million annually, with a central estimate in the mid-£20 millions.

What causes most avoidable Agency Debit Memos?

Common causes include commission errors, fares and taxes, refunds and exchanges, missed ticketing deadlines, schedule changes left unworked, incorrect repricing, PNR housekeeping issues and bookings that drop off a GDS queue while they still require action.

Can TMCs prevent Agency Debit Memos?

Not every ADM will be preventable, but many common causes can be identified before they become charges. Continuous booking monitoring can identify what suppliers require and by when, while business orchestration can ensure the necessary action is completed or escalated before the deadline.

How is monitoring and orchestration different from simply working GDS queues harder?

Working queues manually still relies on a person spotting the right booking at the right moment. Continuous monitoring identifies the state and requirements of bookings at scale, while orchestration turns those signals into prioritised or automated action and escalates genuine exceptions to consultants.

How do Agentivity and Lokulus work together?

Agentivity monitors bookings across channels and identifies what each booking requires and by when, including when a booking has dropped off the GDS queue. Lokulus provides the orchestration layer that coordinates the systems and people required to act on that information. Agentivity knows what needs to be done; Lokulus makes sure it happens.

Do TMCs need to replace their existing GDS or mid-office technology?

No. The approach described in the paper is designed to work with the existing technology estate. The GDS, mid-office and booking tools remain in place, with monitoring and business orchestration sitting across them to coordinate information and action.

Download the full Executive Insight

The Debit Memo Problem: Where Travel Management Companies Lose Their Margin is a joint paper by Alister Harris, CEO of Lokulus, and Riaan van Schoor, CEO of Agentivity.

Download the complete paper for the detailed financial modelling, ADM benchmarks, common causes of avoidable memos and a deeper look at how TMCs can move from reacting to charges to preventing them.

Download now