Sub agent credit limit management: credit is the product

It is Thursday afternoon and a sub-agent you have worked with for two years sends a WhatsApp: five tickets to Istanbul for a family, departing Sunday, "settle as usual next week". Their balance with you is already past what you agreed. They have always paid. You issue. Most consolidators recognise that moment, and most can name the one sub-agent who did not pay after it. Sub agent credit limit management is the discipline of deciding that moment in advance, in a system, instead of at four o'clock on a Thursday with the fare about to expire.
The uncomfortable starting point: for a consolidator, credit is not a courtesy wrapped around the product. It is the product. A sub-agent can usually find the same net fare somewhere else. What they cannot easily find is someone who lets them issue today and pay at the end of the cycle. That is why they stay — and it is also how you end up financing a business you do not own.
Deposit, credit or pay-per-booking: three different businesses
The three ways to let a sub-agent buy from you are not positions on one dial. Each puts the cash-flow risk on a different party, and each attracts a different kind of agent.
| Model | Who carries the risk | Good for | Where it goes wrong |
|---|---|---|---|
| Deposit (prepaid balance) | The sub-agent — the money sits with you before they issue | New agents, markets where collection is slow, anyone you do not know yet | Agents dislike tying up cash; a strong agent leaves for a supplier that offers terms |
| Credit limit | You — you issue now, they pay at settlement | Established agents with a payment history you can check | The limit drifts upward on goodwill, and nobody re-reads it after a bad month |
| Pay-per-booking | Nobody, if the payment clears before ticketing | Occasional agents, one-off groups, agents on probation | Slow for the agent; a transfer that "is on its way" quietly becomes credit |
Most consolidators end up running all three at once. That is fine as long as each sub-agent sits on exactly one of them at any time, and moving between them is a decision someone makes rather than something that happens by drift. The usual pattern is a ladder: a new agent starts on deposit or pay-per-booking, earns a small limit after a few clean cycles, and has it raised only on evidence. The ladder also runs downwards. An agent who pays late twice goes back to deposit — and that rule is written down before it is needed, so applying it is not personal.
A mixed model, where a deposit acts as collateral against a limit, works well for agents you want to keep but do not yet trust. The deposit does not have to cover the whole limit to change behaviour. It has to be large enough that walking away from it hurts.
What should block issuance, and what should only warn
This is the part of the policy most consolidators never write down, and it decides whether the limit means anything. A limit that only produces a warning is a suggestion. A limit that blocks everything, including a reissue for a passenger already stranded at the airport, will be overridden by phone within a week and then ignored.
The useful split is between actions that put new money at risk and actions that do not.
- Block a new ticket or hotel voucher that would take the agent past their available limit. Available means the limit minus everything unpaid — issued-but-not-yet-invoiced as well as invoiced-but-not-paid. Most leakage happens because only the second half is counted.
- Block any new issuance on an account that is past its settlement due date, whatever the balance. An overdue invoice is a stronger signal than a high one.
- Warn when a booking would take the agent close to the limit. The agent should see that before your staff do, so the conversation starts on their side.
- Allow changes that add no exposure — a name correction, a seat request, a date change with no fare difference.
- Allow with an audit trail a manual override by a named person on your side, with a reason. If overrides are anonymous, they become the policy.
Two details matter more than they look. The check has to run at the moment of issuance, not at search or hold. A held PNR costs you nothing; a ticket does. An agent who held six bookings while they had room for all six, then tickets them one by one after a payment bounced, should be stopped at the fourth ticket — not waved through because the hold looked fine on Monday. And refunds and voids should release limit only when they actually settle with the airline or the hotel, not when the agent requests them.
Settlement cycles and invoicing
A credit limit without a settlement cycle is a loan with no repayment date. The cycle — weekly, fortnightly, monthly — is what turns the limit into a revolving amount rather than a ceiling the agent reaches once and stays at.
Shorter cycles are safer and more work. Longer cycles are kinder to the agent and fund more of their business with your money. A sensible rule is to line the agent's cycle up with your own obligations. If you settle with the airlines through BSP on a fixed calendar, an agent who pays you after your BSP date is being financed by you for the gap, every cycle, indefinitely. Put their due date before yours, not after.
The invoice itself should be boring and complete: every document issued in the period, every refund and ADM passed through, the opening balance, payments received and the closing amount due — in the currency the agent was sold in. When a sub-agent disputes an invoice, the dispute is almost always about one line nobody can trace to a booking. If every line points at a PNR or a voucher number, the dispute takes minutes.
Pass ADMs through on the next invoice with the airline's memo attached, rather than absorbing them and resenting it later. An agent who never sees an ADM never learns which fare rule they keep breaking.
The failure mode: a ticket issued against an exhausted limit
This is how it usually goes wrong, and no single step looks like a mistake while it happens.
An agent's limit is full. A request arrives for a large group. The ticketing desk sees an urgent booking from a good customer and issues it, meaning to sort out the balance on Monday. On Monday the agent pays part of the old invoice; the new tickets roll onto the next one. Nobody blocked anything, because the limit lived in a spreadsheet the ticketing desk never opens. Two cycles later the agent's real exposure is several times the number anyone approved, and the conversation is no longer about the limit. It is about whether they can pay at all.
What that costs you is more than the unpaid amount. You have already paid the airline for those tickets through your own settlement. You carry the ADMs on anything they sold wrongly. If the agency closes, you are an unsecured creditor of a travel agency, which in most markets means recovering little, slowly. And the loss tends to arrive in the same week as your own BSP payment, so it hits your cash flow at the worst possible moment.
The fix is not a stricter person on the ticketing desk. It is putting the limit where the ticket is issued, so that going past it takes a deliberate override instead of a busy afternoon.
Where the limit has to live
If your sub-agents book through a portal you give them, the limit belongs in that portal, against that agent's account, checked by the same step that issues the ticket. A limit kept in accounting software and reconciled weekly will always be a cycle behind the bookings. That is the real argument for running sub-agents on a B2B portal instead of WhatsApp: not convenience, but that the portal is the only place a limit can actually stop something.
On our platform, sub-agent credit limits and settlement invoicing are first-class concepts in the system rather than spreadsheets beside it, and each tenant runs them from its own admin panel with role-based staff permissions — so the person who can raise a limit does not have to be the person who issues tickets. If you are building the network now, a consolidator account is where that starts, and the order in which you distribute net fares to sub-agents matters as much as the terms you attach to them.
Credit handed out by default is a loan nobody approved. Credit handed out by rule is the thing your sub-agents are actually paying you for.