BSP reconciliation is the process of matching an agency's own ticket, refund, exchange, and memo records against the IATA BSP billing for the same period. This step explains every difference and confirms the amount to remit or receive. It protects cash flow, catches errors before they become debit memos, and keeps the agency ledger aligned with airline settlements.
For IATA-accredited agencies in the UAE, Saudi Arabia, Malaysia, Indonesia, and other BSP markets, reconciliation is essential. The remittance date arrives, whether the numbers match or not. An agency that pays without reconciling either overpays or finds the error months later.
This guide explains the BSP cycle, outlines what each transaction does to the balance, and presents a nine-step BSP reconciliation process any finance team can follow.
What Is IATA BSP?
The IATA Billing and Settlement Plan (BSP) is a standard framework that simplifies sales reporting, remittance, and settlement between airlines and IATA-accredited travel agents. Instead of paying each airline separately, the agency reports sales through BSP and settles one net amount per remittance period.
Agencies view their billing, refunds, and memos in BSPlink, IATA's web platform for BSP. The rules for agents are outlined in the IATA Travel Agent's Handbook and the local procedures of each BSP market.
The BSP Billing Cycle: Reporting, Billing, and Remittance
Three periods drive every reconciliation:
- Reporting period: the days in which tickets, refunds, and exchanges are counted.
- Billing: BSP produces the billing analysis for that period, listing each transaction and the net amount.
- Remittance: the agency pays or receives the net amount by the local remittance date.
Frequencies differ by market. Some BSPs bill weekly or twice a month; others remit monthly. The finance team should finish BSP reconciliation for each billing before its remittance date, not afterwards.
What Each Transaction Does to the Balance
| Transaction | Effect on the amount payable to BSP | What to check |
|---|---|---|
| Ticket sale, cash | Increases | Fare, taxes, commission, form of payment |
| Ticket sale, card paid to carrier | No cash effect for the agency | Card charged by the airline; commission still counts |
| Void | Removes the sale | Voided inside the window; no billing line left |
| Refund | Decreases | Amount and penalty match the approved refund |
| Exchange or reissue | Increases by the add collect | Old and new tickets linked; change fee captured |
| ADM (Agency Debit Memo) | Increases | Reason, ticket reference, dispute deadline |
| ACM (Agency Credit Memo) | Decreases | Credit matches a known claim or correction |
BSP Reconciliation Step by Step
Step 1: Close the Internal Sales Period
Lock the agency's ticket, refund, and exchange records for the same dates as the BSP reporting period. Any late entry should go into the next cycle with a note, ensuring both sides compare the same window.
Step 2: Download the BSP Billing
Download the billing analysis and supporting reports for the period from BSPlink. Keep the original files unchanged for the archive and work on a copy. An agency that sells in more than one BSP market reconciles each market and currency separately; for example, AED billing in the UAE and SAR billing in Saudi Arabia.
Step 3: Match on the Right Keys
Match every BSP line to an internal record using stable keys:
- ticket or document number;
- transaction type (sale, refund, exchange, memo);
- issue date;
- validating carrier;
- gross fare, taxes, and commission.
Ticket number alone is not enough when one ticket has a sale, a refund, and an exchange in the same period.
Step 4: Classify Every Line
| Status | Meaning | Next Action |
|---|---|---|
| Matched | Same on both sides | None |
| Amount Difference | Same document, different value | Check taxes, commission, currency rounding |
| Missing in BSP | In the agency system, not billed | Check void status, report timing, next period |
| Missing Internally | Billed, not in the agency system | Find the booking or raise a query |
| Duplicate | Appears twice on one side | Remove the duplicate or dispute it |
Every line should end the cycle with one of these statuses and have a named owner for anything unresolved.
Step 5: Check Post-Ticket Transactions
Voids, refunds, and exchanges cause most differences. Confirm that each void left no billing line, each refund shows the approved amount and penalty, and each exchange links the old ticket, new ticket, add collect, and fee. Travilo's guide to void vs refund vs reissue explains how each action should appear.
Step 6: Review ADMs and ACMs
ADMs and ACMs adjust the balance after the original sale. Check each memo against the ticket, the stated reason, and the dispute deadline in BSPlink. Dispute wrong ADMs before the deadline, and record accepted ones against the booking that caused them.
When an ADM comes from a sub-agent's booking, recover it through that partner's ledger. This process is described in Travilo's guide to sub-agent management. ADM prevention deserves a separate playbook; at this step, the goal is only to verify, dispute, or accept.
Step 7: Confirm the Remittance Amount
A simple check before payment:
Cash sales − applicable refunds ± BSP adjustments = amount payable or receivable
This is a simplified view. Commission, taxes, card sales, local charges, and market rules all affect the final figure. The BSP billing should remain the reference. The aim is that finance can explain the BSP total line by line before paying it.
Step 8: Post the Accounting Entries
Post the settlement to the ledger. The airline payable falls by the remittance. Refunds receivable are cleared, commission income is recognized, and each ADM cost is charged to the right booking, sub-agent, or supplier.
Step 9: Archive the Reconciliation
Save the BSP files, the matching report, the difference list with explanations, memo decisions, payment proof, and the approver's name. A complete package makes audits and ADM disputes much faster. Keep it for at least the period that local BSP and tax rules require.
Worked Example: A Dubai Agency's Weekly Billing
A Dubai agency's weekly BSP billing shows AED 184,500 payable. The agency's own records indicate AED 181,300. The difference is AED 3,200.
Matching finds two causes:
- A refund of AED 2,700 recorded internally but not yet processed in BSP, so BSP is higher by that amount.
- An ADM of AED 500 billed by BSP but not yet posted internally.
AED 2,700 + AED 500 = AED 3,200. Every dirham is explained. The refund moves to the next period with a note. The ADM is reviewed, accepted, and charged to the sub-agent who made the booking. Finance remits AED 184,500 with a clear record of why it differs from the internal figure.
BSP Reconciliation Checklist
- Internal period closed on the same dates as BSP.
- Every BSP line matched or classified.
- Every void, refund, and exchange checked.
- Every ADM and ACM verified, disputed, or accepted.
- Remittance amount explained and approved.
- Ledger posted and archive saved.
How Travilo Supports BSP Reconciliation
Travilo lists BSP reconciliation among the use cases of its Finance System and Accounting modules. The value comes from keeping the internal side of the match complete and linked.
1. Ticketing and finance in one record. Every issue, void, refund, and reissue in Travilo's Ticket Management module stays attached to the same booking and ledger. This ensures the agency record is ready when the BSP billing arrives.
[Screenshot: Travilo booking record showing ticket actions and ledger entries]
2. Ledger and reconciliation views. Travilo's accounting ledger records airline payables, refunds, commissions, and adjustments. This gives finance one place to compare against BSP.
[Screenshot: Travilo accounting ledger filtered by reporting period]
3. Reports built for finance. Travilo's Reporting Engine includes sales, booking, revenue, and agency balance reports. These allow differences to be traced to a booking, user, or sub-agent.
[Screenshot: Travilo sales report filtered by validating carrier]
Import options for BSP billing files depend on the setup. The product team confirms current options during a demo. For errors that start before ticketing, see Travilo's guide to improving travel booking accuracy. For a full platform comparison, read the best travel booking software guide for agencies.
Want ticketing, finance, and reconciliation in one system? See how Travilo connects ticket management with accounting and book a demo with the product team.
Frequently Asked Questions
What is BSP reconciliation?
BSP reconciliation is the check an IATA-accredited agency runs before each remittance. The finance team matches its own ticket, refund, exchange, and memo records against the BSP billing. They explain every difference and confirm the net amount to pay or receive. This process prevents overpayment and catches errors before they turn into debit memos.
How often should a travel agency reconcile BSP?
Reconcile every billing period, before its remittance date. In markets with weekly or twice-monthly billing, that means weekly or twice-monthly work. Waiting until month-end can let differences pile up, making causes harder to trace, and can leave too little time to dispute an ADM before its deadline.
What causes most BSP differences?
Most differences come from post-ticket transactions. These include voids that still show a billing line, refunds processed on one side only, exchanges without the old ticket linked, and ADMs or ACMs not yet posted internally. Timing gaps between the agency's records and the BSP reporting period cause the rest, along with tax and commission errors.
How long does an agency have to dispute an ADM?
The dispute window depends on the airline's ADM policy and the local BSP rules, so it varies. The deadline for each memo is shown in BSPlink. Agencies should review new ADMs every billing cycle, dispute wrong ones with evidence well before the deadline, and record every decision against the related booking.
Can a small agency reconcile BSP in spreadsheets?
Yes, at low volume. A spreadsheet works when there are few tickets and few post-ticket changes. As volume, sub-agents, and refunds grow, manual matching becomes slow and error-prone. At that stage, a system that links each ticket action to the ledger saves time and reduces missed differences.