IATA BSP is the industry shorthand agents use for the Billing and Settlement Plan: how accredited travel agencies report airline ticket sales and remit one net amount each billing period instead of settling with every carrier separately. In this guide, BSP means that IATA system — not a bank, a political party or another acronym that shares the same three letters.
Understanding IATA BSP clarifies why remittance calendars matter, what BSPlink is for, how ADMs and ACMs show up in daily ops, and which booking fields finance teams need before remittance week. The sections below cover how the report–bill–remit cycle works, who can use BSP, how it differs from paying airlines one by one, and how booking platforms support clean reporting.
Scope: passenger BSP for IATA-accredited agents. Related systems such as ARC (United States) and CASS (cargo) share the settlement idea but have their own rules; they are noted only where useful, not covered in full.
What IATA BSP Means
BSP stands for Billing and Settlement Plan. In travel agency language, IATA BSP is the standardized framework that lets accredited agents report airline ticket sales, refunds and adjustments through one process and remit one net amount for a billing period, while participating airlines receive consolidated settlement instead of chasing each agency individually.
IATA describes BSP as the trusted backbone of airline distribution between airlines and IATA-accredited travel agents, with tools such as BSPlink for billing, reporting and communication (IATA Billing & Settlement Plan). Published BSP scale figures on that page (re-checked 14 Oct 2026) include:
- 400+ participating airlines
- 59,000+ accredited travel agents
- $242B+ settled annually
- 99.99% on-time settlement rate
Historically, the first BSP launched in Japan in 1971; the model later spread country by country. Wikipedia's overview of the Billing and Settlement Plan matches the same core idea: one intermediary process instead of a mesh of bilateral agency-airline settlements.
So BSP in travel is practical for an agency desk: ticket today against participating airlines using neutral electronic traffic documents, report through the BSP calendar, remit the net, and let the local BSP distribute funds to airlines.
How the Billing and Settlement Plan Works
Think of BSP as a clearing cycle with four stages every agency finance team learns early:
- Sell and document — The agency issues e-tickets (and EMDs where used) under its ticketing authority. Sales, refunds, voids, exchanges, commissions and taxes sit on accountable documents tied to PNRs.
- Report — Document activity flows into the local BSP reporting pipeline (today largely electronic via GDS/ticketing systems and BSPlink), rather than as separate paper packets to each airline.
- Bill — For each billing period, the agent receives a BSP billing that nets sales, refunds, ADMs, ACMs and other adjustments into an amount due (or due to the agent).
- Remit and settle — The agency remits the net to the BSP on the remittance date. The BSP distributes settlement to participating airlines. Agents do not wire each carrier separately for ordinary BSP sales.
That cycle is why ticketing mistakes are expensive. A wrong fare, late void or mismatched name can become an ADM weeks later, long after the passenger has flown. Clean issue data on day one is cheaper than dispute work in the next billing period.
For the document side of the same story, see e-ticket meaning (the paid electronic ticket record) and PNR meaning (the reservation the ticket sits on).
Who Uses BSP (Agents, Airlines and the Local BSP)
Three roles sit inside every BSP market:
- IATA-accredited travel agents — Only accredited passenger agents get BSP access for that market. Accreditation is the gate; software alone does not enrol you.
- BSP airlines — Carriers that elect to participate in a given country's BSP, so agency sales on their stock settle through the plan.
- Local BSP / IATA Settlement Systems — The country or multi-country operation that runs billing calendars, remittance banking and distribution for that market.
IATA's own getting-started note is blunt: to access BSP and its ecosystem, you need to be an IATA-accredited travel agent. If you are still mapping GoLite vs GoStandard, fees and documents, start with how to get IATA accreditation.
Non-IATA agencies still sell flights every day — usually through consolidators, host agencies, airline/LCC APIs or other partners that hold ticketing authority. Those sales may never touch your own BSP account; the partner's settlement arrangements cover them. Knowing what BSP meaning in travel refers to helps you ask the right question in supplier talks: whose ticket stock is this issued on, and through which settlement path?
BSP vs Paying Each Airline Separately
Before BSP-style clearing, an agency's admin load scaled with the number of airlines it sold. Separate reports, separate remittances, separate dispute channels. BSP collapses that into one periodic process per market.
| Aspect | Direct to each airline | Via BSP |
|---|---|---|
| Sales reporting | Per airline process | One BSP reporting pipeline |
| Remittance | Many payments | One net remittance per period |
| Refunds / adjustments | Bilateral | Netting inside the billing |
| Airline cash collection | Airline collects per agent | BSP consolidates then settles airlines |
| Who can use it | Any bilateral deal | IATA-accredited agents + participating airlines |
BSP does not remove commercial risk. Remittance dates still create cash-flow timing: you may have collected from the traveller on Tuesday and remitted on the BSP date later in the cycle. Agencies that grow ticket volume without watching float, bank guarantees and void windows often learn BSP the hard way.
For a wider view of how agencies move money with suppliers and sub-agents outside pure air settlement, see B2B travel payments.
BSPlink, Billing Periods and Remittance Dates
BSPlink is IATA's web platform agents and airlines use to manage billing outputs, reporting views and day-to-day BSP communication. Finance and ticketing supervisors live in it when they download billings, track ADMs or check agent/airline notices.
Each local BSP publishes a calendar: billing period start/end, billing availability and remittance date. Period length is not universal — some markets bill weekly, others in multi-week cycles, and calendars can change (local agent associations usually circulate notices). Always use the calendar for your agency's BSP country in the IATA customer portal rather than memorising another market's dates.
Related ecosystem pieces IATA lists alongside BSP (names only; product fit depends on your accreditation and market) include:
- IATA EasyPay — pay-as-you-go style e-wallet option for ticket settlement where offered
- Travel Agent Service Fees (TASF) — collection/settlement path for agency service fees where supported
- Agent billing data / HOT-style files — detailed sales extracts used for reconciliation and incentive tracking
Ops tip: treat the remittance date like a payroll date. Build an internal checklist (open ADMs, pending refunds, unreported voids, bank balance) 48 hours before remittance, not on the morning funds leave.
ADMs, ACMs and Why Reconciliation Matters
Two memo types dominate BSP dispute work:
- ADM (Agency Debit Memo) — the airline bills the agency for a shortfall (fare difference, tax error, unused ticket misuse, fare-rule breach, and similar).
- ACM (Agency Credit Memo) — the airline credits the agency (over-collection, commission correction, and similar).
ADMs are where weak booking data hurts. If your system cannot show the e-ticket number, fare basis, form of payment, tax breakdown, void timestamp and PNR history, disputing an ADM becomes guesswork. Strong desks reconcile:
- GDS / NDC / API issue logs vs BSP billing lines
- Refund and exchange tickets vs passenger refunds paid out
- EMD numbers for seats, bags and penalties vs ancillary invoices
- Commission expected vs commission in the billing
Keep those identifiers on the same customer and booking record. Spreadsheet hand-offs between ticketing and accounts are how memo deadlines get missed. When BSP statement lines need to sit next to invoices and supplier payments in one back-office view, see travel accounting systems integration for how booking data feeds reconciliation. For teams that want supplier payments, invoices and booking history in one ops view, a CRM that keeps settlement memos next to each booking beats chasing email threads when an ADM lands.
How Booking Software Supports BSP Reporting
Booking software does not replace BSP membership. It should make the data BSP (and your accountant) need impossible to lose:
- Store validating carrier, 13-digit e-ticket numbers, EMD numbers, PNR / airline locators, NDC order IDs, fare basis, taxes, form of payment and issue timestamps on one booking.
- Queue ticketing time limits, failed issues, voids and schedule changes for a human desk before remittance week.
- Export or API-feed sales registers that finance can match to BSP billings and HOT extracts.
- Preserve audit history for ADM disputes (who issued, who voided, which fare was quoted).
When billings list validating carriers by numeric code, desks often decode prefixes beside the ticket mask; IATA.co's airline codes directory is a practical lookup for numeric and two-letter codes during reconciliation.
Where PHPTRAVELS fits
PHPTRAVELS is licensed travel booking software (B2C, B2B or both) with a flights module that connects supplier APIs you already have credentials for. Live flight integrations are listed on phptravels.com/integrations (Amadeus, Sabre, Travelport, Duffel, Mystifly, TBO Holidays, PKFare, Kiwi and others — always re-check that page before promising a supplier). The platform can hold booking references and ticket identifiers your connected suppliers return, and it can feed back-office / accounting workflows such as those described on travel accounting systems integration.
Honest limits: PHPTRAVELS does not grant IATA accreditation, does not enrol you in BSP, does not issue tickets by itself, and does not take a cut of bookings. You bring accreditation (or a ticketing partner), supplier contracts, payment accounts and remittance banking. To see flows end to end, open the live demo; to size modules and APIs, use the pricing configurator.
IATA BSP: Frequently Asked Questions
What does IATA BSP mean in simple terms?
IATA BSP is the Billing and Settlement Plan: IATA's system so accredited agents report and remit airline sales through one periodic process instead of settling separately with every airline.
Is BSP the same as IATA accreditation?
No. Accreditation is membership status. BSP is the settlement framework accredited passenger agents use in markets where it operates. You need accreditation (for that setup) to access BSP.
Do I need BSP to sell flights online?
Not always. Many agencies ticket through consolidators, host agencies or airline/LCC APIs under the partner's authority. You need a commercial path to ticket stock; BSP is one path, not the only one.
What is BSPlink?
BSPlink is IATA's web platform for BSP billing, reporting and airline-agent communication around the settlement cycle.
What is an ADM?
An Agency Debit Memo is an airline charge to the agency for a ticketing or fare-rule shortfall, usually settled through the BSP billing.
Is ARC related to BSP?
ARC performs a similar clearing role for many US agency-airline transactions. It is a separate organisation and rule set from IATA BSP, even though the business problem (consolidate agency air settlement) is related. This guide stays on passenger BSP; choose the system that matches your market and accreditation.
If you are building or upgrading the stack that captures tickets before they hit BSP reports, start with the PHPTRAVELS demo and confirm modules on the pricing page.
