Skip to content
Voraal

Services · GDS, NDC & airline

Ticketing automation for the work after the booking

Ticketing is where mistakes cost money: the wrong GDS, a missed time limit, a void after the window closed, a refund that returned a non-refundable tax. Rezencia automates issuance by rule and runs voids, refunds and reissues in one guided flow, with fare-rule and tax handling and ledgers updated as each step completes.

Built for

  • Ticketing desks
  • Consolidators
  • IATA-accredited agencies
  • TMCs
  • Umrah operators in peak season

In brief

What is airline ticketing automation?

Airline ticketing automation issues tickets and handles post-ticketing changes by rule instead of by hand. It decides when a booking is ready to issue, which GDS issues it, and how voids, refunds and reissues are calculated, including penalties, fare difference and refundable taxes. Voraal's Rezencia provides rule-based ticketing and void, refund and reissue automation with a full audit trail.

By the Voraal team · Updated

What gets automated, and what stays a decision

Ticketing automation has two halves. Issuance: deciding that a booking is paid, approved and still priced correctly, choosing the GDS that should issue it for that airline, and issuing before the airline's time limit. Post-ticketing: voids within the permitted window, refunds calculated from the fare's refund rules and the tax breakdown, and reissues that collect the fare difference and change penalty.

Not everything should be automatic. Involuntary changes follow the airline's waiver, some refunds need a supervisor, and large group tickets may need a person to check. Rezencia automates the calculation and the transaction, and lets you decide which actions need approval. A step-by-step explanation is in our guide on how airline ticketing automation works.

How rule-based issuance works

  1. 01

    Booking becomes eligible

    Payment is received or the agent's credit covers it, and any corporate approval is complete.

  2. 02

    Price is checked

    The stored fare is confirmed so a ticket is not issued on a fare that has changed.

  3. 03

    GDS is chosen by airline

    Your rule names the GDS for each airline, as in dynamic multi-GDS ticketing. Staff do not choose.

  4. 04

    Ticket is issued

    Issuance runs through that GDS; ticket numbers are written to the booking and the invoice is raised.

  5. 05

    Exceptions go to a queue

    If issuance fails or a rule needs a person, the booking lands on the desk's work list with the reason.

Void, refund and reissue: what each involves

Each action has its own window, inputs and money effect. ATPCO fare-rule categories such as Category 31 (voluntary changes) and Category 33 (voluntary refunds) define much of the arithmetic, with Category 16 carrying penalty text.

ActionWhen it appliesWhat is calculatedMoney effect
VoidWithin the void window set for the market, typically soon after issueNothing beyond the ticket totalSale reversed as if not issued
RefundUnused or partly used ticket, if the fare allowsPenalty, refundable versus non-refundable taxes, used portionRefund to customer, agent and supplier balances
ReissueChange of date, flight or routingFare difference, tax difference, change penaltyAdditional collection, or residual value per rule
Involuntary changeAirline changed or cancelled the flightPer the airline's waiverOften no penalty; follows waiver terms

Check the void window and refund procedures for your BSP market and each airline. They differ and change.

Key features

  • Per-airline GDS routing

    One rule per airline decides the issuing GDS, changed in one place when a deal changes.

  • Time-limit control

    Bookings close to their ticketing deadline are issued by rule or flagged before the airline cancels.

  • Void, refund, reissue flow

    Penalties, refundable taxes and fare difference are calculated and shown before confirmation. See void, refund and reissue.

  • Ledgers in step

    Customer, agent and supplier balances update with each transaction, ready for BSP and supplier reconciliation.

  • Approval rules

    Choose which actions need a supervisor, by amount, airline or user role.

  • Audit trail

    Every issuance and change is recorded with the user and time against the booking.

BSP, ADMs and why accuracy pays

For IATA-accredited agencies, tickets issued on BSP airlines are reported and settled through the Billing and Settlement Plan, which consolidates sales reporting and remittance between agents and airlines. Airlines can raise Agency Debit Memos (ADMs) when they find a ticket was issued or refunded incorrectly, and these appear in the agent's BSP billing.

Many ADMs come from avoidable errors: a refund that included a non-refundable tax, a reissue priced without the penalty, a ticket issued after a fare changed. Automation reduces these by calculating from the fare rules and stored price and recording each step. It does not remove the need to check a disputed case against the filed rule and the airline's policy.

Implementation process

  1. 01

    Map airlines to GDSs

    List which GDS should issue for each airline you sell.

  2. 02

    Define eligibility

    Decide what makes a booking ready to issue: payment type, credit, approvals.

  3. 03

    Set approval thresholds

    Choose which refunds and reissues need a supervisor.

  4. 04

    Run in parallel first

    For a short period, compare automated calculations with your desk's manual results before relying on them.

Common challenges on a ticketing desk

Manual ticketing

  • Routing learned by heart; new staff cannot ticket alone
  • Void windows missed during peak season
  • Refund amounts worked out on a calculator
  • Ledgers updated later, or not at all

Automated with Rezencia

  • Routing applied by rule; staff ticket from one screen
  • Time limits and void windows tracked on the work list
  • Amounts calculated from fare rules and taxes before confirmation
  • Ledgers update with the transaction

FAQ

Frequently asked questions

Questions buyers ask about airline ticketing automation.

Ask us anything
  • Can tickets be issued automatically the moment payment arrives?

    Yes, if your rules allow it. Eligibility can be based on payment received, available agent credit and completed approvals.

  • How does the system know which GDS should issue a ticket?

    You set one rule per airline naming the issuing GDS. The airline on the booking selects the GDS, using your existing PCC, Office ID or SID credentials.

  • Are non-refundable taxes handled in refund calculations?

    Yes. Refunds are calculated from the fare's refund conditions and the tax breakdown, separating refundable and non-refundable taxes, and shown before confirmation.

  • Will automation stop ADMs completely?

    No system can promise that. Automation removes many common calculation errors, but disputed cases still need checking against the filed rule and the airline.

  • Can some refunds require a supervisor's approval?

    Yes. Approval rules can be set by amount, airline or user role.

  • Does it handle NDC orders and low-cost carrier changes too?

    Changes to NDC orders and LCC bookings are sent to the airline from the same booking, following each airline's supported actions and policy.

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