Glossary

BSP (Billing and Settlement Plan)

IATA’s system for billing and settlement between accredited travel agencies and airlines. BSP consolidates ticket sales and remittances and provides standard financial reporting and controls.

BSP consolidates sales reporting and remittance between accredited agencies and airlines in most markets outside the US. Agencies report transactions, remit on a schedule and receive documents for audit. ARC plays the equivalent role in the US.

Reconciliation matches BSP files to internal orders. High auto‑match rates require capturing ticket numbers, coupons, taxes, commissions and form‑of‑payment fields at the time of sale. Exchanges and refunds must carry the right references so exceptions do not pile up.

Operationally, treat ADMs/ACMs (agency debit/credit memos) as first‑class events. Post them with links to the underlying orders and create workflows for dispute or acceptance. Keep your ledger honest; do not bury adjustments inside generic fees.

A good mid‑office posts as you sell: invoice issuance, payment receipt, ticket issuance, refund completion. By the time the BSP statement arrives, most lines match automatically and finance only reviews deltas.

Design for multiple jurisdictions. Taxes, reporting cadence and file formats vary by region, but the internal order and posting model should not. Keep differences at the import/adapter layer and preserve one set of journals.

Common mistakes

What teams often get wrong

  • Can BSP reconciliation be fully manual at scale?

    Manual matching does not scale and will create ageing and write‑offs. Clean capture of ticket numbers, commissions and taxes at booking enables high auto‑match rates and faster exceptions.

Prefer a walkthrough?

See how the products fit together and discuss your use cases in a live demo.