When a passenger cancels a ticket or changes a date, the agency must cancel or reissue it with the airline, work out the refund after airline penalties, and return the right amount to the passenger. Online, every refund and date change is tracked against the booking and the agent's wallet — so no refund is paid twice or forgotten.
That single tracked record is what the ZantaSoft Travel Agency Portal gives every agency. The rest of this post explains what a refund really involves, where the money goes, and how online tracking protects both the agency and the passenger.
Why refunds go wrong on paper
On paper, a refund lives in three places at once: the airline's email, the agent's WhatsApp chat, and a note in a register. The passenger asks for his money, the agent checks the chat, the owner checks the register, and the three rarely agree. Was the ticket refunded by the airline already? Was the amount Rs 45,000 or Rs 48,500? Did the sub-agent already receive it, or is it still sitting with the main agency? Every question needs a phone call, and every phone call costs time the agency does not have during peak season.
The costliest mistake is the double refund: the passenger is paid once by the agent and once by the office, because neither knew about the other payment. The second costliest is the forgotten refund — the airline paid it back months ago, but nobody claimed it or passed it on, and the passenger eventually takes his business to another agency.
What a refund really involves
A refund is not one step; it is a chain. First the ticket is cancelled with the airline, which applies its own penalty — a fixed fee, a percentage of the fare, or no refund at all on the cheapest fares. Then the airline returns the balance, which can take days or weeks. Then the agency deducts its own service charge if one was agreed, and pays the passenger the rest. If a sub-agent sold the ticket, the money passes through his wallet too, and his ledger must show the deduction.
Each step has a number attached: the penalty, the refundable amount, the date the airline paid, the date the passenger was paid. Lose any one of those numbers and the agency cannot answer the simplest question a passenger asks: "Where is my refund?"
Date changes and reissues
A date change is often harder than a cancellation. The old ticket is cancelled, a new ticket is issued on the new date, and the fare difference is charged or refunded. Sometimes the new fare is higher and the passenger must pay the difference before the ticket is issued; sometimes it is lower and money is owed back. In between, the passenger may have already paid a hotel or a visa fee tied to the old date.
Online, the reissue stays linked to the original booking. The portal shows the old ticket, the new ticket, the fare difference, and who paid what — in one place. On paper, the reissue becomes a new line in a register with no link back to the original sale, and the fare difference becomes a number nobody can trace a month later.
Who pays what: airline penalty vs agency service
Passengers often blame the agency for the airline's penalty. The honest answer is to show the split clearly: this much was the airline's cancellation fee, this much was the fare difference, and this much was the agency's service charge. When the split is written on the booking itself, the argument ends before it starts — the passenger can see that the agency kept only its agreed charge.
That clarity also protects the agency's own money. If the airline deducts a penalty of Rs 8,000 from a Rs 60,000 ticket, the agency must never refund the full Rs 60,000 to the passenger by mistake. A portal that holds the airline's penalty figure next to the refund figure makes that mistake almost impossible.
Tracking refunds in the agent wallet
For agencies working with sub-agents, refunds must flow through the agent's wallet and ledger. When a sub-agent's passenger cancels, the refund is deducted from that sub-agent's wallet balance, and his ledger shows the entry with the booking reference. The main agency sees the same entry from its side. Both sides agree, because both sides read the same record.
Without that shared record, the end of the month becomes a dispute: the sub-agent says he is owed Rs 120,000, the agency's register says Rs 95,000, and the difference is a handful of refunds recorded on one side only. A wallet that updates itself on every refund ends that argument for good.
Keeping passengers informed
Most refund complaints are not about the money — they are about silence. A passenger who hears nothing for two weeks assumes the worst. A portal that records each step lets the agent answer in seconds: the airline accepted the cancellation on Tuesday, the refund arrived on Friday, your payment is scheduled for Monday. That one message keeps a customer who would otherwise leave.
Refunds and date changes are part of selling tickets, not an exception to it. Agencies that handle them cleanly keep their passengers; agencies that lose track of them lose both money and trust. The ZantaSoft Travel Agency Portal tracks every refund, reissue and wallet entry against the original booking — setup is Rs 15,000 one-time and Rs 50,000 per year. Try it free for 7 days, or message us on WhatsApp and we will show you how refunds work inside the portal.
Written by the ZantaSoft team
We build custom software for real businesses — and we write about what we learn along the way.