Sub-agent wallet and credit limits: let your network book without letting it overdraw
Consolidators and B2B portals give sub-agents the ability to book and ticket on credit. That is how the network grows — and how money is lost when a sub-agent books beyond its deposit, tickets on a limit nobody was watching, or disappears with an unpaid balance. This page sets out where the exposure comes from and how to control it without slowing the network down.
01What goes wrong
Credit losses in B2B travel rarely come from one big default. They come from small gaps in control.
Limits in spreadsheets
Credit limits held in a sheet and checked after ticketing, not before.
Deposits recorded late
Top-ups and deposits entered a day later, so available credit is never accurate at the moment of booking.
Exposure nobody watches
Sub-agents ticketing through their own PCCs with no one tracking how much is outstanding.
Tickets issued on exhausted credit
Auto-ticketing continues after the limit is reached because nothing stops it.
See where it breaks — and how it is fixed
The problem. Sub-agents ticket directly while limits sit in a spreadsheet checked later. One goes over its limit, and the consolidator still owes the settlement.
The fix. TRI checks each sub-agent’s available credit at booking and ticketing, warns near the limit, and holds ticketing when credit runs out.
Explore each problem
Limits in spreadsheets
Why it happensThe limit is reviewed in a report after tickets are already issued.
How the platform fixes itA customised credit limit per sub-agent is enforced at booking and ticketing.
Deposits recorded late
Why it happensAvailable credit is a moving number that is never current.
How the platform fixes itCredit used and available credit are in view, with deposits monitored.
Exposure nobody watches
Why it happensSub-agents ticket through their own PCCs with no one tracking the total owed.
How the platform fixes itTRI manages each sub-PCC individually, with near-limit warnings.
Tickets issued on exhausted credit
Why it happensAuto-ticketing carries on because nothing stops it.
How the platform fixes itTicketing is put on hold when a sub-agent has no credit left.
02Why it matters
For the business
- Unpaid balances that become bad debt
- Tickets issued that the consolidator must settle through BSP regardless
- Credit decisions made under sales pressure
For operations
- Manual reconciliation of deposits against bookings
- Ticketing paused by hand when someone notices
- Disputes with sub-agents over what was available when
For the sub-agent
- Unexpected ticketing holds with no warning
- No self-service view of available credit
03Why it happens
-
The consolidator carries the settlement
When a sub-agent books on the consolidator’s accreditation and credit, the consolidator owes the airline through BSP whether or not the sub-agent pays. The credit risk is structural.
-
Checks happen too late
If the limit is enforced by a person reviewing a report, tickets are already issued by the time the breach is seen.
-
Available credit is a moving number
Deposits, top-ups, refunds and new bookings all change it. Unless they are recorded in the same system at the moment they happen, the number used for decisions is stale.
-
Every sub-agent is different
A long-standing partner and a new agency need different limits and different terms, which spreadsheet-based control cannot apply consistently.
The credit terms, defined
| Term | Meaning |
|---|---|
| Credit limit | The maximum the consolidator allows the sub-agent to owe at any time |
| Deposit / wallet balance | Money the sub-agent has paid in advance |
| Outstanding | Bookings and tickets issued but not yet paid for |
| Available credit | What the sub-agent can still book — commonly the credit limit plus the deposit balance, minus what is outstanding |
| Near-limit warning | A notice when available credit falls close to zero, so the sub-agent can top up before ticketing stops |
Checking at booking and at ticketing
Credit has to be checked at two moments, because a held booking costs nothing while an issued ticket is owed through settlement.
| Moment | What is checked | Why |
|---|---|---|
| Booking (hold) | Whether the sub-agent has enough available credit for the fare | Stops bookings that could never be ticketed |
| Ticketing | Available credit at the moment of issue | The ticket creates a settlement obligation for the consolidator |
| Deposit or top-up | That the payment is recorded straight away | Available credit is only accurate if deposits are current |
04Our approach
Enforce credit where the money moves — at booking and ticketing — not in a weekly report.
A limit per sub-agent
Each sub-agent has its own customised limit, with credit used and available in view.
Enforced automatically
Sales are controlled by available credit; ticketing is put on hold when a sub-agent has no credit left.
Warn before the limit
Near-limit warnings let the sub-agent top up before ticketing stops.
Same control across GDS
The control layer covers sub-PCCs on Sabre and Travelport alike.
05How the Innovate Solution platform solves it
| Problem | Platform capability |
|---|---|
| Booking beyond the deposit | A customised credit limit per sub-agent; sales are controlled by available credit and ticketing is put on hold when a sub-agent has no credit left. |
| Exposure nobody watches | TRI manages each sub-PCC individually: credit used and available credit in view, deposits monitored, near-limit warnings. |
| Different terms per sub-agent | Per-sub-agent branding, markups and credit limits on the B2B portal. |
| ADM exposure from sub-agent errors | Bookings that may carry ADM risk are flagged — see BSP & ADM management. |
How it runs, step by step
- Limit setA credit limit is set for the sub-agent against its deposit and terms.
- Booking checkedAvailable credit is checked when the sub-agent books.
- Warning issuedAs the limit approaches, the sub-agent is warned to top up.
- Ticketing heldIf credit is exhausted, auto-ticketing is held until a deposit is recorded.
Watch TRI’s credit control in action: TRI sub-agent credit control video.
06What changes
| Before | With the platform |
|---|---|
| Limits checked after tickets are issued | Limits enforced at booking and ticketing |
| Available credit worked out from a sheet | Credit used and available in view, live |
| Ticketing stopped by hand when someone notices | Ticketing held automatically at the limit |
| Sub-agent surprised by a hold | Near-limit warnings before it happens |
See it on your own bookings. A live walkthrough of this workflow on the platform — not slides.
Book a demoWho this is for
- Airline consolidators
- Wholesalers with sub-agent networks
- B2B travel portals
- Host agencies
Questions to ask any vendor
- Is the credit limit enforced at booking and ticketing, or reviewed afterwards?
- Can each sub-agent have its own limit and terms?
- Does the system warn the sub-agent before the limit?
- Does credit control cover sub-agents ticketing through their own PCC?
Frequently asked questions
What is a sub-agent wallet?
A prepaid balance a sub-agent holds with a consolidator or B2B portal. Bookings draw it down and deposits or top-ups add to it, so the sub-agent can only book what it has paid for or been granted as credit.
How should credit limits for sub-agents be set?
Per sub-agent, based on its deposit, history and documents, and reviewed as the relationship develops rather than set once for the whole network.
Can credit be controlled when sub-agents ticket through their own PCC?
Yes. TRI manages every sub-PCC individually, with a credit limit per sub-agent, credit used and available in view, and near-limit warnings.
What happens when a sub-agent reaches its limit?
Sales are controlled by available credit, so ticketing is put on hold until a deposit or top-up is recorded. The sub-agent is warned as the limit approaches.
Related pages
- TRI
- TRI credit control video
- BSP & ADM management
- Platform for consolidators
- B2B travel portal software
- Travel software FAQ
Sources and further reading
About this page. The problem described here comes up repeatedly in public traveller and travel-agent forum discussions that our team reviewed in November 2026. Examples are paraphrased; no person, airline or booking site is named, and we do not claim how often it occurs. See all travel software problems and solutions.
Next step
See credit limits, wallets and near-limit warnings across a sub-agent network.
