IATA BSP Airline-Agent Reconciliation for Indian Travel Agencies

A Delhi-headquartered IATA-accredited travel agency operating across 14 branches in metro and tier-2 cities closes May 2026 with ₹85 crore of weekly BSP throughput aggregated across four cycles, 22 participating airlines, three GDS (Amadeus dominant, Sabre and Travelport secondary), 1.84 lakh tickets issued, ₹62 lakh of ADMs raised by airlines and ₹38 lakh of incentive receivables accrued. The CFO walks five reconciliation rails concurrently: BSP-link weekly to bank statement, GDS booking files to BSP-link, ADM/ACM lifecycle with airline dispute response, refund cycle from RA filing to BSP settlement, and Section 393 code 1007 TDS chase against 22 deductor airline TANs through Form 26AS. IATA BSP airline agent reconciliation India at scale is not one reconciliation problem — it is a multi-party, multi-cycle settlement discipline where the audit trail per ticket is the single most important control.

Quick reference

How does the IATA BSP weekly settlement actually work?

The BSP — Billing and Settlement Plan — is the centralised airline-agent settlement system operated by IATA in over 175 countries. In India, BSP-India handles weekly settlement between IATA-accredited travel agencies and participating airlines:

1. Ticket issuance — agent issues a ticket through a GDS (Amadeus, Sabre or Travelport). Each ticket carries an ARN (Airline Reporting Number) and a unique ticket number.
2. Weekly cycle — Monday to Sunday transactions accumulate; the cycle closes Sunday end-of-day.
3. BSP-link weekly report — IATA publishes the per-agent weekly billing report listing per-ticket sales, refunds, ADMs and ACMs per airline, with the net settlement amount.
4. Bank debit — typically on the Friday following the cycle close, the agent’s authorised bank account is direct-debited for the net settlement amount. Where the agent is in net-credit position (refunds exceed sales), the bank is credited.
5. Reconciliation — the agent ties the BSP-link report to the GDS issuance file and to the bank statement debit on settlement day.

Failure to honour the BSP debit triggers escalation through the IATA financial-criteria framework, with potential consequences ranging from increased financial-guarantee requirements to suspension of the agency’s IATA accreditation.

What are the five concurrent reconciliation rails?

Rail 1 — BSP-link to bank statement

The weekly net settlement amount on the BSP-link report must reconcile to the bank statement debit on settlement day. Variances are typically rounding, currency-rate-of-exchange differences on international tickets, or timing differences where the debit lands T+1.

Rail 2 — GDS booking files to BSP-link

Each GDS produces a daily issuance file keyed by PNR and ticket number. Reconciliation ties each GDS-issued ticket to the BSP-link weekly report. Recurring exception patterns:

• Void-rebook timing differences — ticket voided in GDS just before cycle close appearing in BSP because of GDS-to-BSP cut-off timing
• ADM imposition post-issuance — airline raises an ADM for fare-loading error, commission misapplication or unreported issuance after the ticket has cleared
• Refund-application timing — Refund Application (RA) filed in GDS in week 1 settles in week 2 BSP
• Currency conversion variance — international ticket priced in USD with the issued amount converted to INR at GDS rate but settled at BSP day’s rate

With 22 airlines and 3 GDS, the reconciliation is an n-by-m matrix held at ticket-number granularity.

Rail 3 — ADM and ACM lifecycle

Airline Debit Memos (ADMs) are airline-initiated debits to the agent for fare-loading errors, commission disputes, unreported issuances, or compliance breaches. Agency Credit Memos (ACMs) are the reverse — airline credits to the agent for correctable errors. The dispute register holds:

• Airline reference and ADM number
• Error description and amount
• Date raised, dispute filed, response received
• Ageing: 30/60/90 from raise date

The 30-day window to dispute an ADM at the BSP layer matters — beyond it the ADM crystallises and the amount is recovered through the agent’s settlement. Industry-typical ADM incidence is 0.3-0.8 percent of weekly billing — a 0.5 percent rate on ₹85 Cr weekly is ₹42 lakh of ADM activity to manage.

Rail 4 — Refund and RA cycle

A refund originates from a Refund Application (RA) filed in the GDS at cancellation. The refund applies the airline’s fare-rule and computes the net refund — gross fare minus penalty minus commission claw-back where applicable. The RA is queued for BSP settlement in the next available cycle. The reconciliation tracks:

• RA filed date in GDS
• Settlement cycle in which it appeared on BSP-link
• Net refund credited or commission clawed back
• End-customer refund payout from the agent’s wallet

Rail 5 — Section 393 code 1007 TDS on airline incentives

Airline incentive payments to IATA agents — productivity-linked, override commission and segment-incentive structures — fall under Section 393(1)(f) code 1007 at 2 percent (legacy 194H). The agent’s quarterly Form 26AS reconciliation by deductor airline TAN chases this credit. Incentive payments often lag the underlying BSP cycle by 30-90 days because incentive structures are slab-based and reconciled monthly or quarterly. The lagged TDS credit is a working-capital lock.

What is the GST split between 5 percent tour-operator and 18 percent agency commission?

Two distinct treatments apply concurrently:

Pure air-ticket agency on BSP rails — the agent acts as agent for the airline. Principal supply is air travel by the airline. The agent’s revenue is the commission and incentive from the airline (or the service fee charged to the customer separately). Agency commission is taxable at 18 percent under SAC 998551 (services of travel agents) under forward charge.

Tour-operator option — under Notification 11/2017 entry 23, a tour operator can elect:

• 5 percent GST on the gross tour package value (without ITC), or
• 18 percent on the value addition only (with ITC)

The election applies to packaged tour services (air + hotel + ground transport bundled). Mid-tier IATA agencies typically run both — pure air-ticket agency on BSP rails and tour-package operator on direct customer contracts — and the reconciliation must split each so it files in the correct GSTR-3B box.

Worked example — Delhi IATA agency, ₹85 Cr weekly BSP, May 2026

A mid-tier IATA agency operating across 14 metro and tier-2 branches:

The CFO’s month-end close ties:

• Four weekly BSP-link to bank statement reconciliations
• 1.84 lakh tickets across 22 airlines and 3 GDS to BSP-link
• ADM dispute register with 30/60/90 ageing
• Refund register with RA-to-BSP cycle matching
• Section 393 code 1007 TDS chase per airline TAN through Form 26AS

What does the Section 393 / GST overlay look like?

• Section 393(1)(f) code 1007 (legacy 194H) — 2 percent TDS on airline incentives and override commission. See Payment Code 1007 — Commission & Brokerage.
• Section 393(1)(j) code 1010 (legacy 194O) — 1 percent TDS on payouts via OTA aggregators (MakeMyTrip, Yatra, EaseMyTrip).
• Section 52 CGST TCS — 0.5 percent CGST + 0.5 percent SGST on consideration collected by OTA aggregator on agent’s behalf, credit in GSTR-2B.
• GST output on agency commission — 18 percent SAC 998551 forward charge.
• GST output on tour-package revenue — 5 percent without ITC or 18 percent on value-add with ITC, agent election under Notification 11/2017 entry 23.
• FEMA on international ticket settlements — outbound forex remittance to overseas airlines is subject to FEMA reporting; bank-side compliance maintained at BSP-India level.

For the broader payment-code reference see TDS payment codes 1001-1092 India and Section 393 framework explainer.

DGFT authority reference

For the regulatory framework on outbound travel and tour-operator services, foreign-exchange settlement under FEMA for international air-ticket transactions, and the broader trade-services architecture under which IATA-accredited agencies operate see the Directorate General of Foreign Trade (DGFT).

What automated reconciliation changes

Running a ₹340 Cr monthly BSP-throughput reconciliation across 22 airlines, three GDS, 1.84 lakh tickets, dual GST classifications and three Section 393 TDS codes is a multi-party multi-cycle settlement problem that breaks single-counterparty reconciliation tools. Purpose-built reconciliation software India holds the ticket master with ARN-ticket-number granularity, the BSP-link to GDS matching engine with per-airline cut-off rules, the ADM/ACM dispute register with 30/60/90 ageing, the dual-GST classification engine and the multi-code TDS ledger in one frame. Customer outcomes include match rate improvement from 51 percent to 88 percent on revenue-grade ledgers. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the GST split between agency commission and tour-operator filings see GST reconciliation software.

Continue reading in the Logistics cluster

• FASTag toll reconciliation for Indian fleet operators
• 3PL settlement reconciliation for Indian logistics operators
• Freight forwarder multimodal reconciliation for Indian logistics operators
• Logistics reconciliation hub