Short answer: travel supplier settlement is how the money an agency collects from customers reaches the suppliers who deliver the travel. Air sales by IATA agents settle through the centralised Billing and Settlement Plan on fixed cycles; consolidator and API sales draw down prepaid wallets in real time; bed banks invoice against credit lines; and card or gateway payments settle to whoever was merchant of record. A typical agency runs four or five of these rhythms at once, which is why reconciliation, not selling, is where back offices drown.
The settlement map: who owes whom
Follow one month of bookings through a mid-sized agency and the money fans out along parallel paths:
Nothing about any single path is complicated. The difficulty is the combination: different cycles, different statement formats, different currencies and different dispute processes, all washing through one or two bank accounts.
Centralised settlement: BSP and ARC
For IATA-accredited agents, air ticket money moves through IATA's Billing and Settlement Plan (BSP): the agent reports all sales, refunds and exchanges through the accredited channels, receives a consolidated billing for each cycle, and remits one net amount to the clearing bank, which distributes it to the airlines. IATA documents the mechanics in its BSP manuals; billing cycles and remittance frequencies are set per country, and payment methods include cash settlement, card sales and IATA's prepaid EasyPay wallet. In the United States, ARC performs the equivalent role. The agency's obligations are strict: miss a remittance and default procedures with financial-security consequences follow quickly.
Settlement here is periodic and batch-shaped, so the work is matching: your issued tickets, ADMs, refunds and commission against the BSP billing file, line by line, every cycle. We cover that discipline in detail in BSP reconciliation explained.
Consolidator and API wallets
Agencies without their own plate, and many with one, buy air and other content through consolidators and API suppliers on a prepaid wallet model: top up the wallet by bank transfer, and every issuance draws it down instantly. Suppliers such as TBO and similar aggregators expose the balance through their portals and APIs (see our TBO API integration page for how that works technically). Settlement risk flips direction here: the supplier holds your money before delivery, so top-up sizing becomes a working-capital decision, and an unnoticed low balance becomes failed ticketing at the worst moment. Wallet accounting is prepayment accounting: the balance is your asset, each booking moves value to cost of sale, and each refund should credit the wallet back, which is precisely the kind of per-event tracking spreadsheets lose.
Bed bank and DMC credit lines
Hotel wholesalers, bed banks and DMCs commonly work the opposite way: they extend a credit limit and invoice on a statement cycle, weekly, fortnightly or monthly, often with payment terms tied to check-in dates rather than booking dates. That is genuinely useful financing, but it produces the messiest reconciliation of the lot: statements arrive as spreadsheets or portal downloads in the supplier's own format, amendments and cancellations generate credit notes that must be netted against the right original lines, and currency differences appear when you sell in one currency and are invoiced in another. Credit lines also concentrate counterparty exposure in both directions: you owe them a growing balance, and your customers' stays depend on that supplier's own solvency and hotel payments.
Cards, gateways and merchant of record
The customer-facing side of settlement is the payment gateway. When the agency is merchant of record, card takings settle from the gateway to the agency's account, minus fees, on the gateway's payout schedule, and chargebacks claw money back weeks later. When the airline's or supplier's own payment page is used, the customer's money bypasses the agency entirely and only commission flows back. A third pattern, paying suppliers with virtual cards generated per booking, gives each supplier payment its own card number and thus its own clean audit trail. Which pattern fits which market, and how payouts, fees and disputes differ between Indian and international gateways, is covered in our guide to payment gateways for travel agencies.
| Settlement model | Direction and timing | Main reconciliation task |
|---|---|---|
| BSP / ARC | Agency pays net per fixed cycle after sale | Match billing file lines to tickets, refunds, ADMs and commission |
| Consolidator / API wallet | Agency prepays; drawdown per booking, instant | Match wallet ledger to bookings and refunds; monitor balance |
| Bed bank / DMC credit line | Supplier invoices per statement cycle, terms follow travel dates | Match statement lines and credit notes to bookings across currencies |
| Gateway (agency as merchant) | Gateway pays agency net of fees on payout schedule | Match payouts to receipts; track fees, holds and chargebacks |
| Virtual cards to suppliers | Per-booking card payment at booking or check-in | Match card transactions to bookings; reconcile card programme statement |
The reconciliation pain points
Ask any travel back office where the hours go and the same list appears:
- Format chaos. Every supplier statement has its own columns, references and file format; humans re-key them into spreadsheets to compare.
- Reference mismatch. The supplier's line carries their reference, your system has yours, and the customer paid quoting neither. Matching depends on keys nobody agreed on.
- Timing differences. A booking sold in March, invoiced against April check-in, refunded in May, appears in three different statements. Cut-off differences make honest numbers look wrong.
- Partial events. Amendments, partial refunds, no-show charges and ADMs attach fractional amounts to old bookings, and unmatched fractions accumulate.
- Currency and fees. Gateway fees, FX spreads and bank charges mean almost nothing matches to the paisa; without tolerance rules, everything becomes an exception.
- The suspense account. Unmatched items get parked "to sort out later", and the parking lot only ever grows.
The cost is not only labour. Unreconciled books hide margin leakage (uncredited refunds, double-charged bookings, unclaimed commission), and they blind the owner to the one number that matters daily: how much of the cash is actually ours, a question explored in travel agency accounting basics.
What automation actually fixes
Settlement automation is unglamorous and works. The pattern implemented in a travel ERP is: ingest every statement automatically (BSP files, wallet ledgers via supplier APIs, bed bank statements, gateway payout files); normalise them into one internal format; auto-match against bookings using reference, amount and date rules with sensible tolerances; and queue only true exceptions for a human, with the booking and the statement line side by side. Add live wallet and credit-line balance monitoring with alerts before limits bite, and scheduled supplier-wise payable reports so payment runs come from data rather than memory. Agencies doing this well reconcile daily in minutes instead of monthly in days, and the exceptions queue becomes a profit-recovery tool, because every exception is either an error to fix or money to claim.
This article is general information about travel technology and online marketing. It is not legal, tax or financial advice, and advertising platform policies change often. Check the current policy documents and take professional advice for your own situation.