Skip to content
Voraal

Guide · Ticketing

Inside airline ticketing automation: from a held PNR to an issued, serviced and reconciled ticket

Ticketing is where a flight booking becomes a financial obligation. Once a ticket is issued, the agency owes the airline through BSP or the consolidator, whether or not the customer pays. Automating ticketing is therefore less about speed than about making the right decision every time. This guide explains the rules, checks and post-ticketing flows that a ticketing engine runs.

Built for

  • Ticketing managers
  • Consolidators
  • IATA agencies
  • OTAs with ticketing desks
  • Travel product engineers

Short answer

How does airline ticketing automation work?

A ticketing engine watches held PNRs, checks each against rules — payment or credit cleared, fare still valid, passenger data complete, time limit approaching — then chooses the issuing channel and validating carrier and issues the ticket. After issuance it automates same-day voids, reissues under fare-rule change conditions, refunds and schedule-change handling, posting every step to the ledgers. Voraal's Rezencia runs this with rule-based ticketing.

By the Voraal team · Updated · 7 min read

What does a ticketing engine actually decide?

Whether to issue, when, where and on which carrier. A booking held in a GDS or with an airline has a ticketing time limit; if it passes, the airline's system cancels the segments. The fare also carries its own last ticketing date in its rules. Between booking and that deadline, the engine must decide whether the money is secure, whether the fare and passenger data are still valid, and through which GDS office or airline channel to issue, with which validating carrier.

In a manual desk those decisions live in people's heads and email threads. An automated engine makes them explicit rules attached to every PNR, and keeps a record of which rule fired and why — the audit trail that protects you when an airline disputes a ticket.

What happens between booking and issuance?

A typical pre-ticketing pipeline, in the order the engine evaluates it:

  1. 01

    Capture the deadlines

    Read the PNR's ticketing time limit and the fare's last ticketing date. Use the earlier of the two as the working deadline, minus a safety buffer.

  2. 02

    Confirm funds

    Customer payment confirmed, or agent credit or wallet balance sufficient. If not, alert the owner of the booking and, near the deadline, escalate rather than issue on hope.

  3. 03

    Re-validate the fare

    Re-price the PNR to confirm the stored fare is still available and correct. A price difference is routed for approval instead of being absorbed silently.

  4. 04

    Check passenger data

    Names match passports, date of birth and travel documents present where the route requires them, contact details recorded for disruption notices.

  5. 05

    Choose channel and validating carrier

    Apply routing rules: which GDS office or NDC channel issues for this airline and fare, and which plating carrier is permitted under BSP and interline agreements.

  6. 06

    Issue and distribute

    Issue the ticket and any EMDs, store document numbers on the booking, send documents to the customer or agent, and post the sale to agent and supplier ledgers.

Which ticketing rules do agencies typically configure?

Rule typeExampleWhy it exists
Deadline bufferIssue no later than 3 hours before the earlier of TTL and last ticketing dateLeaves time for manual fixes
Funds gateIssue only if payment confirmed or agent credit availablePrevents unpaid tickets
Carrier routingAirline X issues through GDS office A; airline Y through its NDC channelBest fare, incentive or surcharge outcome
Value thresholdTickets above a set amount need supervisor approvalLimits fraud and error exposure
Fare-change gateRe-price difference above a threshold routes for approvalAvoids silent margin loss
Blackout ruleNo auto-issue for flagged agents or routesRisk control
Group handlingGroup PNRs issue by name-list deadline, not individuallyAirline group terms

How are voids automated?

By watching the clock. On BSP, a ticket can be voided only on the same day it was issued, in the system where it was issued; after that, the sale is reported to BSP and the only route back is a refund, if the fare allows it. Airline agency guidance is consistent on this point, and missed voids are among the most expensive avoidable mistakes in a ticketing desk.

An automated engine records each issuance time, shows every ticket still within its void window, processes customer or agent void requests instantly, and reverses ledger entries in the same step. It also catches system-generated voids: a ticket issued in error by a rule can be voided automatically if the funds check later fails within the window.

How do automated reissues and refunds use fare rules?

By reading the airline's filed change and refund conditions rather than relying on staff memory. ATPCO identifies the three most common standards dealing with changes as Category 16 (penalties), Category 31 (voluntary changes) and Category 33 (voluntary refunds). A reissue engine reads Category 31 to calculate the fare difference, change fee and tax difference; a refund engine reads Category 33 to calculate the refundable amount after penalties.

Automation here has limits. Fare rules are not always filed in a form every system can apply, waivers during disruptions are often published as airline notices rather than data, and NDC servicing varies by airline. ATPCO itself noted during the 2020 disruption that existing automation was not built for emergency waivers and that manual changes were very time-consuming. A practical engine automates the clear cases, shows its calculation for the rest and routes them to a person with the rule text attached. AI-generated plain-language fare-rule summaries help agents make that call faster.

How are schedule changes handled automatically?

Through queues and notifications. When an airline changes a flight time or cancels a segment, the change arrives on a GDS queue or through the airline's NDC notification. The engine reads it, classifies it (minor time change, significant change, cancellation), notifies the customer or agent on their channel, and proposes options — accept, rebook, refund — according to the airline's involuntary change policy. Involuntary changes typically carry no penalty, but a waiver reference is needed on reissue, so the engine should capture it. See the schedule change alerts case study for how this works in practice.

What are ADMs and how does automation prevent them?

An Agency Debit Memo is a charge an airline raises against an agency, usually through BSP, for a ticketing or servicing error — for example, issuing after the last ticketing date, applying the wrong fare, refunding more than the rule allows, or misusing booking classes. ADMs arrive weeks later and are deducted from the agency's settlement, which makes them hard to trace back to the person responsible.

Automation reduces ADMs by enforcing the checks that cause them: issuing within fare rules, re-pricing before issuance, calculating refunds from Category 33 rather than by hand, and logging every change. When an ADM still arrives, the audit trail shows which booking, which rule and which user, so the agency can dispute it with evidence or charge it back to the responsible agent.

Manual desk vs automated engine: what changes?

ActivityManual deskAutomated engine
Time-limit trackingStaff check queues and spreadsheetsEvery PNR monitored with a working deadline
Funds checkStaff ask finance or check the bank appPayment and credit status read from the booking record
Carrier routingTicketing agent chooses by habitRules choose by airline, fare and channel
VoidsDepends on someone noticing in timeSame-day window shown and enforced
Reissues and refundsCalculated by hand from fare-rule textCalculated from Categories 31 and 33, with review for exceptions
Ledger postingEntered later by accountsPosted at each status change
ADM disputesSearching emails for evidenceAudit trail per booking

How Voraal fits

Rezencia's rule-based ticketing decides which GDS or airline channel issues each booking, tracks PNR queues and time limits, and runs void, refund and reissue in one flow with fare-rule and tax handling and a full audit trail. An integrated GDS terminal sits inside the admin for edge cases, AI fare-rule summaries make conditions readable, and schedule-change alerts notify customers and agents. Explore the airline ticketing automation service, the dynamic multi-GDS ticketing case study, the void, refund and reissue case study and flight fare management for markup and fare rules.

Key takeaways

  • Ticketing creates a financial obligation; automate decisions, not just speed.
  • Work to the earlier of the PNR time limit and the fare's last ticketing date, with a buffer.
  • Gate issuance on confirmed funds, a fresh re-price and complete passenger data.
  • Route issuance by airline and fare to the right GDS office or NDC channel.
  • Enforce the BSP same-day void window automatically.
  • Calculate reissues and refunds from ATPCO Categories 31 and 33; review exceptions.
  • Keep an audit trail per booking to prevent and dispute ADMs.

How Voraal delivers this

The product behind it.

FAQ

Frequently asked questions

Questions buyers ask about how airline ticketing automation works.

Ask us anything
  • What is the difference between a ticketing time limit and a last ticketing date?

    The ticketing time limit is set on the PNR by the airline or GDS, after which unticketed segments may be cancelled. The last ticketing date is a fare-rule condition after which that fare can no longer be issued. A ticketing engine should respect whichever comes first.

  • What is a validating carrier and why does automation need to choose it?

    The validating or plating carrier is the airline whose ticket stock is used and which settles the ticket through BSP. Not every carrier can validate every itinerary, so the engine must apply interline and BSP rules to choose a permitted one.

  • Can a ticket be voided the next day on BSP?

    On BSP, voids are normally only possible on the same day of issuance. After that the sale is reported and you must process a refund if the fare permits. Rules for other settlement systems, such as ARC in the United States, differ.

  • Are EMDs handled by ticketing automation?

    Yes, a full engine issues and tracks EMDs for ancillaries such as seats and bags, and for residual values, alongside tickets. Their refund and exchange rules differ from the ticket's, so they need their own handling.

  • Does automated ticketing work for NDC bookings?

    It can, but servicing support varies by airline and NDC version. The engine needs channel-specific logic for orders, and some changes or refunds may still need offline handling with particular airlines.

  • How do we stop an automated rule issuing a fraudulent booking?

    Combine value thresholds that require approval, credit and payment gates, blacklists for flagged agents or patterns, daily issuance caps per user and alerts on unusual behaviour. The same-day void window gives a final safety net.

Sources and further reading

Regulations, airline programmes and supplier terms change. Confirm requirements with the relevant authority or supplier before acting. Contact [email protected] if you spot something out of date.

Let’s build what comes next.

Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.

WhatsApp