OperationsAug 10, 202613 min readTravel Engine

E-Ticket Management for Travel Agencies: 2026 Playbook

Streamline your e-ticket management with our 2026 playbook. Ensure reliable ticket issuance and avoid costly disputes with a standardized workflow.

A travel agency operations team can reliably issue, store, update, and reconcile airline e-tickets by following one standardized workflow: confirm credentials, validate the booking, select the form of payment, issue the ticket, deliver to the client, retain the record, and reconcile against BSP billing reports. That sequence, done consistently, is the difference between a clean audit and a costly ADM dispute.

Before your next issuance, run through this checklist:

Confirm IATA or ARC accreditation, or verify host-agency credentials and ticketing authority delegation
Log into BSPlink and confirm that the airline has granted Electronic Ticketing Authority for each carrier you plan to ticket
Verify the form of payment (Customer Card, IATA EasyPay, or Alternative Transfer Method) is accepted by that carrier
Run a pre-issue name check: passenger name must match the government-issued ID exactly
Confirm fare rules, ticketing deadline, and wallet or card balance before touching the issue command

Pro Tip: Travelengine centralizes this entire flow, from booking ingestion through BSP reconciliation, so your team works from one source of truth rather than five browser tabs.

Key Takeaways

Reliable e-ticket management requires confirmed ticketing authority, a consistent pre-issue checklist, daily RET-to-BSP matching, and a centralized platform to hold the audit trail together.

Point	Details
Confirm authority before issuing	Verify Electronic Ticketing Authority per carrier in BSPlink before any issuance attempt.
Run the pre-issue checklist every time	Check name, PTC, E indicator, interline eligibility, fare rules, and payment balance before issuing.
Retain ETRs for at least two years	BSP rules require a minimum two-year retention period for all Electronic Ticket Records.
Match daily, not monthly	Ingest RET files daily and match to BSP billing reports to catch ADMs before dispute windows close.
Travelengine centralizes the full cycle	Travelengine connects GDS data, BSP reconciliation, and document retention in one auditable platform.

What does e-ticket management mean for travel agencies and DMCs?
Accreditations, ticketing authority, and compliance you need before issuing
How to issue a ticket step by step inside your GDS
How to store, access, and retain Electronic Ticket Records
Daily reconciliation, BSP billing reports, ADMs/ACMs, and EasyPay flows
How to void, refund, or exchange a ticket correctly
Common issuance errors and how to diagnose them fast
How to automate e-ticket management and choose the right platform
What running e-ticket ops at scale actually looks like
Travelengine covers every step of this workflow
Sources

What does e-ticket management mean for travel agencies and DMCs?

In the travel agency context, e-ticket management covers the full operational lifecycle of an airline or transport electronic ticket: issuing it through a GDS or ticketing service provider, delivering the itinerary receipt to the client, storing the Electronic Ticket Record (ETR), handling voids, refunds, and exchanges, and reconciling issued tickets against BSP or ARC billing reports.

This is not event ticketing or IT help-desk ticketing. The subject here is the flight booking process that runs through IATA's Billing and Settlement Plan or ARC's settlement system, where every issued ticket carries a 13-digit ticket number and a corresponding financial obligation.

Three roles share ownership of the process:

Agent: builds the PNR, runs pre-issue checks, issues the ticket, and delivers the itinerary receipt
Operations: manages ticketing authority in BSPlink, monitors daily RET files, and flags exceptions
Finance: reconciles BSP billing reports, processes ADMs/ACMs, and manages dispute windows

One critical boundary: a PNR is not a ticket. Ticketing is a separate act that generates the ticket number and finalizes the financial record. Some low-cost carriers use light or ticketless models that bypass BSP/ARC reporting entirely, which changes the reconciliation picture for those bookings.

Accreditations, ticketing authority, and compliance you need before issuing

The BSP manual for agents draws a clear line between two things agents often conflate: airline appointment (the commercial relationship) and Electronic Ticketing Authority (the technical permission to issue e-tickets on a carrier's stock). You need both. Ticketing authority is granted per airline via BSPlink and must be requested separately, even when you already have an appointment.

BSP centralizes selling, refunding, reporting, and remitting for IATA-accredited agents, so every ticket you issue flows through a single financial settlement. BSPlink is where your team manages ticketing authority, pulls billing reports, reviews ADMs and ACMs, and handles dispute communications.

Key compliance items:

ETR retention: store all Electronic Ticket Records issued through BSP for a minimum of two years
Passenger notices: deliver the itinerary receipt and mandatory Ticket Notices per IATA Resolution 724 at the time of issuance
Form-of-payment permissions: BSP accepts Customer Card (CC), IATA EasyPay (EP), and approved Alternative Transfer Methods, but individual carriers may restrict which options they accept on their stock

IATA EasyPay blocks funds in real time at issuance, uses the EP form-of-payment code on BSP billing reports, and settles daily through IATA's clearing bank to airlines. It reduces upfront credit exposure for agents, but EP transactions appear as a separate line on billing reports, so your reconciliation process must account for them explicitly. See the IATA EasyPay procedural notes for the full settlement flow.

How to issue a ticket step by step inside your GDS

Every issuance follows the same sequence. Skipping a step is where costly reissues originate.

Build and verify the PNR. Confirm passenger name matches the government-issued ID character for character. Check the Passenger Type Code (PTC), any Special Service Requests (SSRs), and that the itinerary is complete.
Check carrier eligibility. Confirm the E (Electronic Ticketing) indicator is present on each segment. Verify interline agreements if the itinerary spans multiple carriers. Pull carrier-specific fare rules and ticketing deadline from the GDS fare display.
Validate the booking. Run the GDS validation entry (DT/ETE0 in Travelport, or the equivalent in your TSP) as a pre-issue gate. This catches ineligible itineraries before the ticket number is generated.
Select and confirm form of payment. Verify the carrier accepts your chosen payment method. For IATA EasyPay, confirm the wallet balance covers the full fare before proceeding.
Issue the ticket. Enter the ticketing command (TKP in Travelport Smartpoint, or your GDS equivalent). The system returns a 13-digit ticket number and the airline PNR. Confirm both appear in the booking file.
Deliver to the client. Send the itinerary receipt and mandatory Ticket Notices immediately. Document the delivery timestamp.
Flag for reconciliation. Mark the ticket number in your agency system and queue the booking for the next RET ingestion cycle.

Pro Tip: Always check the ticketing deadline in the fare rules before step 3. A booking that auto-cancels overnight because the deadline passed is a reissue at best, a lost sale at worst.

Once issued, the carrier's ticket record is effectively immutable. Name corrections or major itinerary changes require a void or refund and reissue, not a simple GDS edit.

How to store, access, and retain Electronic Ticket Records

ETRs live in two places simultaneously: the airline's reservation system and the GDS ticket fields attached to your PNR. Your agency database is a third layer, and it is the one you control.

To retrieve a ticket record in Travelport Smartpoint, the GDS knowledge base documents three primary commands:

*HTE displays the current ETR attached to the active booking
*TE/[ticket number] retrieves a specific ticket record by number
*TEH pulls the full ticket history, including voids, exchanges, and reissues

Use *TEH whenever you need an audit trail for a dispute or a refund claim. The history entry shows every transaction against that ticket number.

Retention architecture that holds up under audit:

Layer	What it stores	Access method
Airline system	Carrier ticket record	Airline portal or GDS ETR link
GDS ticket fields	ETR at time of issuance	`HTE`, `TE/#`, `*TEH`
Agency database	Copies, delivery proof, change log	Internal search by ticket number or PNR
Secure backup	Archived ETRs and transaction logs	Role-based retrieval

The two-year minimum retention rule applies to all ETRs issued through BSP. Build that window into your document retention policy and confirm your backup system preserves raw source files, not just summaries.

Pro Tip: Link to the Travelengine confirmation management guide for a practical approach to organizing delivery records at scale.

Daily reconciliation, BSP billing reports, ADMs/ACMs, and EasyPay flows

Reconciliation is where financial exposure either gets caught early or compounds into unrecoverable losses. Three-way matching between GDS booking records, contracted rates, and BSP statements flags discrepancies far earlier than a monthly manual review.

Daily tasks (ops role):

Ingest GDS RET (Reporting and Evaluation of Transactions) files
Match issued ticket numbers to the day's PNRs
Compare against BSP Billing Report line items
Route exceptions to a queue for same-day resolution

Weekly tasks (finance role):

Review EP transactions on BSP billing reports separately from card transactions
Check BSPlink for new ADMs or ACMs issued by carriers
Confirm dispute windows are still open on any flagged ADMs

Monthly tasks (finance + ops):

Full BSP statement reconciliation against agency bank records
Close resolved disputes and archive supporting documentation
Review ADM patterns to identify recurring issuance errors

ADMs issued by airlines appear directly in your BSP billing and are payable unless disputed. Carriers frequently impose dispute windows that can be shorter than IATA defaults. Missing that window means the ADM amount is collected automatically in your next BSP billing cycle. Check BSPlink for new ADMs at least weekly, and keep the GDS transaction log and delivery proof ready before you file a dispute.

How to void, refund, or exchange a ticket correctly

The place you perform the transaction determines what gets reported to BSP and what documentation you can produce later.

Voids: process in the GDS on the same calendar day as issuance, before 23:59 local time (confirm the carrier's specific cutoff). A same-day void removes the ticket from BSP billing entirely. After that window closes, you are in refund territory.
Refunds: process through BSPlink or the airline's portal, depending on whether the fare is BSP-reportable. Attach the original ETR, the passenger delivery proof, and the fare rules documentation.
Exchanges: issue a new ticket and apply the exchange value. Electronic Miscellaneous Documents (EMDs) handle ancillary fees and service charges that accompany exchanges or stand-alone ancillary sales.

Required records for every void, refund, or exchange: the original ticket number, the GDS transaction log entry, the passenger delivery confirmation, and the fare rules or carrier waiver that authorizes the action.

Pro Tip: Capture the GDS transaction log and passenger delivery proof at the moment of processing, not after the fact. If a dispute arises, that timestamp is your evidence.

Common issuance errors and how to diagnose them fast

Most failed issuances trace back to one of five root causes:

Passenger name format does not match carrier requirements (middle names, titles, special characters)
PTC is unsupported by the fare or carrier (infant without adult, unaccompanied minor without carrier approval)
E indicator is missing on one or more segments, meaning the carrier has not enabled electronic ticketing for that flight
Interline agreement is absent between carriers on a multi-carrier itinerary
Payment authorization fails (insufficient EasyPay wallet balance, card decline, or carrier does not accept the chosen payment method)

Quick diagnostic sequence:

Check the E indicator on every segment in the GDS fare display
Verify interline agreements through the GDS interline database or carrier KB
Confirm form-of-payment acceptance with the carrier's ticketing rules entry
Pull *TEH to check whether a prior transaction left the ticket in an inconsistent state
Review RET files for any BSP mismatch on the same booking

Escalation decision: raise an ADM dispute in BSPlink when the charge relates to a BSP-reported transaction and you have documentation. Contact the airline directly when the issue is a carrier-side system error, a waiver request, or a ticket number that does not appear in BSPlink at all.

How to automate e-ticket management and choose the right platform

Manual reconciliation at volume is where errors compound. Automated three-way matching between GDS records, contracted rates, and BSP statements catches discrepancies before dispute windows close.

Platform evaluation checklist:

GDS/TSP connectors (Travelport, Amadeus, Sabre) for real-time booking and ticket data
RET and ETR ingestion with automatic ticket number extraction
BSPlink-compatible ADM/ACM workflow with dispute tracking
Form-of-payment mapping, including EP code identification
Role-based access controls (agent, ops, finance) with a full audit trail
Exportable reconciliation reports for BSP billing periods
Exception routing with configurable matching thresholds

Implementation sequence:

Pilot with one high-volume market or airline before full rollout
Map every role to a specific task and SLA (daily RET ingestion = ops; weekly ADM review = finance)
Configure auto-matching thresholds to flag exceptions without blocking clean transactions
Preserve raw source files (RET files, GDS logs, BSP statements) for dispute support
Schedule a monthly review of exception patterns to refine thresholds over time

Travelengine's booking management features cover ticket ingestion, document storage, and supplier invoice matching. The Trevi AI assistant automates routine booking updates and flags anomalies, while the reporting dashboard surfaces reconciliation exceptions without requiring a manual export cycle. See the workflow automation overview for implementation patterns.

What running e-ticket ops at scale actually looks like

The playbook in this guide works. The part most operations managers underestimate is not the GDS commands or the BSP rules — it is the cross-team handoff. Sales creates a booking and considers the job done. Finance wants a clean BSP statement. Operations sits in the middle, responsible for a process that neither team fully owns.

The single most effective change a team can make is establishing one source of truth for ticket status: issued, voided, pending reconciliation, disputed. Without it, the same ADM gets worked by two people or missed by both. The workflow only holds when every role knows exactly where to look and what to do next.

Travelengine covers every step of this workflow

Most agency teams manage e-ticket operations across a GDS, a BSPlink login, a spreadsheet, and an email thread. Travelengine replaces that stack with a single platform built for exactly this workflow.

The Travelengine platform connects to your GDS, ingests RET and ETR data automatically, and maps every ticket number to the corresponding booking and client record. Three features that directly address the pain points in this guide:

Automatic ticket ingestion: ticket numbers are captured at issuance and linked to the booking file, eliminating manual entry and the mismatches that follow
ADM/ACM dispute tracking: new ADMs from BSPlink are surfaced in the ops dashboard with dispute window countdowns, so nothing falls through
Centralized document retention: ETRs, delivery confirmations, and transaction logs are stored in one place with role-based access and a two-year-minimum retention policy built in

The Trevi AI assistant handles routine updates and flags exceptions before they become billing problems. Start a free trial or book a demo to see how the reconciliation dashboard maps to your current BSP billing cycle.