Skip to content
Voraal

Case study · Ticketing automation

Void, refund and reissue in one flow.

Post-ticketing changes run in one guided flow with fare-rule and tax handling, instead of manual GDS work and calculator maths.

Problem area
Ticketing automation
Products
Rezencia
Built for
Ticketing desks · Consolidators · Agencies and TMCs

Every ticket that changes after issue — a void, a refund, a reissue — is work done by hand in most agencies: GDS entries, fare-rule reading, tax calculation and a ledger update. Rezencia runs all three in one flow, with an audit trail.

01 · The problem

The problem

Post-ticketing work is where experience is most concentrated and errors are most expensive. Taxes are refunded wrongly, penalties are missed, and the agent's ledger doesn't match what happened in the GDS.

  • Void windows missed
  • Refund amounts calculated by hand
  • Reissues priced without the fare difference and penalty
  • Ledgers updated separately, or not at all

02 · Why it's hard to fix

Why it's hard to fix

  • Every fare is different

    Penalties, refundable taxes and reissue rules vary by fare and airline.

  • Time windows

    Voids are only possible within a short window after issue.

  • Money has to reconcile

    Whatever happens in the GDS must match the customer's refund and the agent's ledger.

03 · What we built

What we built

One post-booking flow in Rezencia. The agent picks the action; Rezencia reads the fare rules and taxes, shows the amounts, runs the GDS transaction and updates the ledgers — every step logged.

  • Void, refund and reissue from the booking
  • Fare-rule and tax handling
  • Ledger and statement updated automatically

04 · How it works

How it works

  1. 1

    Choose the action

    Void, refund or reissue, from the booking.

  2. 2

    See the amounts

    Penalties, refundable taxes and fare difference are calculated and shown.

  3. 3

    Confirm

    The transaction runs on the right GDS.

  4. 4

    Ledgers update

    Customer, agent and supplier balances reflect the change.

05 · What changes for the team

What changes for the team

BeforeWith Voraal
GDS entries and calculator mathsOne guided flow
Refund amounts worked out by handAmounts shown before confirmation
Ledgers updated separatelyLedgers update with the transaction
Knowledge held by a few senior agentsA consistent process for the whole desk

06 · What it does not do

What it does not do

  • Airline rules, waivers and ADM policies still apply; the flow follows them, it doesn't override them.
  • Some complex cases may still need manual GDS work — the built-in terminal is available for those.
  • Refund timing to the traveller depends on the airline and the payment method.

See it on your own bookings.

FAQ

Questions, answered.

Short answers about this solution.

Ask us anything
  • Does it handle partial refunds?

    Yes — refunds are calculated per fare rule, including non-refundable taxes and penalties.

  • What about involuntary changes?

    Involuntary changes follow the airline's waiver; the flow and the audit trail are the same.

  • Is every action logged?

    Yes. Each step is recorded against the booking with the user and time.

WhatsApp