GST on booking advances: you owe tax before the trip runs

Your client pays a ₹55,000 advance in January to lock a May departure. You bank it, note it in Excel against the booking, and plan to raise the tax invoice and pay GST once the trip actually runs. That's the habit most agencies carry into every peak season, and it's the wrong sequence.

GST on a booking advance is due the month you receive it, not the month you invoice the balance or the month the client travels. Section 13(2)(a) of the CGST Act fixes the time of supply of a service at the earlier of the invoice date or the date payment is received. Payment arrived first, so payment sets the date. Invoicing only at departure isn't a filing shortcut; it's a gap between what you owe and what you've reported, exactly the kind a GST notice is built to catch.

This post walks through what an advance triggers: the voucher you must issue, which return line it hits and when, how a genuine supplier deposit differs from a taxable advance, and what to do if you've been invoicing at departure all along.

Why the trip date doesn't decide when you owe GST

The rule is simple even though the habit fights it: GST attaches to whichever happens first, the invoice or the payment, not to when the service is delivered. A May departure and a January advance are two different events for tax purposes, and only one of them is happening in January.

Most agencies invoice at departure because that's when the "sale" feels complete: the booking has run, the client has traveled, there's nothing left to argue about. But Section 13(2)(a) taxes the cash the moment it lands in your account. Run every departure this way and you're structurally behind by however many months sit between your advance and your travel date.

The receipt voucher: what Section 31(3)(d) actually makes you issue

Every advance needs a formal receipt voucher, not an internal note in your booking sheet. Section 31(3)(d) requires a registered person to issue a receipt voucher on receiving an advance, and Rule 50 fixes exactly what has to be on it.

Field	What goes here
Supplier details	Your name, address, GSTIN
Serial number	Consecutive, unique for the financial year, max 16 characters
Date, recipient details	Client name/address, GSTIN or UIN if registered
Description, amount	What the advance is against, and the amount received
Tax rate and amount	Rate applied, tax charged on the advance
Place of supply, RCM flag	State code for inter-state, reverse-charge yes/no

Rule 50 also carries a proviso worth knowing: if you can't fix the tax rate at the time the advance lands, tax on it is paid at 18%, and if you can't fix whether the supply is intra-state or inter-state, it's treated as inter-state. That's the default the law falls back to when booking details aren't settled, so lock the itinerary and place of supply before you take the advance, not after.

A real booking, month by month: January advance to May departure

Take a straightforward two-installment booking: 30% advance in January, balance in April, travel in May. Apply Section 13(2)(a) separately to each payment, since each is its own trigger.

1. January: Advance received. Issue the receipt voucher, report the advance in that month's GSTR-1, and pay the tax through GSTR-3B for the January period.
2. April: Balance received, tax invoice raised. Report it in GSTR-1 for that period, in the normal invoice tables, and pay tax on the balance amount.
3. May: Trip runs. Nothing new happens for GST here. Both payments were already taxed in the months you received them.

This is not a "continuous supply of services" arrangement, worth being precise about since the two-installment shape looks similar. Continuous supply under Section 2(33) requires a contract for recurring services over more than three months with periodic payment obligations, a different animal from a single package sold in two installments. The plain time-of-supply rule, applied twice, is the whole answer.

Example: A ₹1,85,000 Kerala package, GST at 5%. Client pays ₹55,000 in January, balance ₹1,30,000 in April. January GST liability: ₹55,000 × 5% = ₹2,750, reported and paid for the January period. April GST liability: ₹1,30,000 × 5% = ₹6,500, reported and paid for the April period. Total tax across the booking is unchanged at ₹9,250; only the timing splits across two return periods instead of landing on one invoice at departure.

Table 11A and Table 11B of GSTR-1, decoded

Table 11A captures the advance and adds its tax to that period's output liability; Table 11B nets that same amount out once the final invoice appears in a later GSTR-1. Between the two, an advance is never double-counted, but it does have to be tracked across two separate filing periods, the same table-by-table discipline that runs through filing GSTR-1 and GSTR-3B as a tour operator.

Concretely, per the GST Council's own FORM GSTR-1 instructions: Table 11A ("Advance amount received in the tax period for which invoice has not been issued") is where you report the January advance, rate-wise and place-of-supply-wise. Table 11B ("Advance amount received in earlier tax period and adjusted against the supplies being shown in this tax period") is where, in April's GSTR-1, you pull that same advance back out, now that it's absorbed into the tax invoice sitting in the normal sales tables. Miss the 11B adjustment and the advance's tax effectively gets counted twice in your own working papers, exactly the kind of mismatch a GST notice is built to flag.

Deposit against a hotel block, or consideration for the package: the line that decides if GST applies at all

A genuine deposit isn't automatically a taxable advance. Section 2(31)'s proviso excludes a deposit from "payment" for GST purposes unless the supplier actually applies it as consideration for the supply. If the money is sitting there as security, refundable and untouched, it hasn't triggered GST yet.

The test that matters is what you actually do with the money, not what you call it. Say a client pays ₹20,000 to hold a hotel block you've contracted, refundable in full if the group doesn't confirm. That's a deposit: it hasn't been applied against anything yet. The moment you adjust it against the client's booking or their invoice, it stops being a deposit and becomes consideration, and GST applies from that point.

Careful: Labeling every incoming rupee a "deposit" to defer tax is not a safe reading of Section 2(31). If the amount is earmarked against a specific booking and you'd apply it to that booking's price the moment it confirms, it's functioning as an advance, whatever the receipt says. Keep genuine, refundable, unallocated deposits in a separate ledger from package advances so the distinction is visible if it's ever questioned.

The cash-flow trap: you already sent the money to the hotel

An operator billing at 5% GST with no input tax credit has to fund that tax entirely out of cash, often out of an advance that's already been forwarded to a supplier. Tour operator services under Heading 9985 can be billed at 5% GST without input tax credit, or 18% with full input tax credit, the operator's choice, as of August 2026 (rate notifications amend periodically; confirm the current position with your CA before you commit to a slab). Pick 5%, and every rupee of GST on an advance comes straight out of margin or working capital, with no ITC pool to draw against.

Here's where it actually bites. A ₹55,000 January advance against a Kerala booking often goes straight to blocking a hotel or vehicle, before the client's April balance ever arrives. The ₹2,750 GST on that advance still has to be found and paid by the January GSTR-3B due date, from whatever's left in the account, not from the trip's eventual profit. Quoting all-in prices without planning for this is how a well-margined booking still produces a cash squeeze in its first month, three months before a single service has been delivered.

When the booking dies: the refund voucher

If a client cancels after you've already taxed their advance, you don't just delete the entry. Section 31(3)(e) lets you issue a refund voucher when an advance was taxed but no supply follows and no tax invoice is ultimately raised, and Rule 51 fixes what it must contain: your details, a serial number, the recipient's details, the amount refunded, the tax rate and amount, and critically, the number and date of the original receipt voucher it's reversing.

That last requirement is why the receipt voucher discipline from earlier matters even when a booking looks certain to run. Without a traceable original voucher, there's nothing for the refund voucher to reference. It reverses tax already correctly reported; it doesn't retroactively make the original charge wrong. You owed the tax when you received the advance, and cancellation is a separate, later event that unwinds it. What you can actually claw back from the supplier is a separate question, worth matching against your cancellation policy's refund terms.

If you've only ever invoiced at departure, here's the fix and the exposure

Going forward, the fix is procedural: issue a receipt voucher on every advance, report it in that month's Table 11A, pay the tax through that period's GSTR-3B, and adjust it out through Table 11B once the final invoice is raised. Build the advance receipt format into your booking workflow so it's automatic, not something you remember at month-end.

The harder part is the exposure that already exists. If advances have gone untaxed until departure in past periods, that tax was due earlier than it was reported, and it carries interest. Section 50 sets interest on unpaid tax at up to 18% per annum, currently notified at 18%, running from the day after the tax was actually due, calculated against every rupee sitting late, not the total booking value. Working out how many past periods are affected, and what the interest bill comes to, is worth doing with your CA rather than estimating it yourself. It's a bounded, fixable number; leaving it undiscovered is the version that actually costs you.

Common questions

Is GST applicable on advance for services?

Yes. Under Section 13(2)(a), the time of supply for a service is the earlier of the invoice date or the date payment is received, so an advance against a service triggers GST the moment it's received, regardless of when the service is actually delivered.

GST on advance payments: rules for goods vs services

The two aren't treated the same. A relief you may have heard about, exempting small advances from tax, applies only to goods, not services. There's no equivalent for service suppliers, tour operators included, so every taxable service advance is liable from the date of receipt, whatever the amount.

Advance booking GST kab bharna hai?

The tax on an advance is due for the same tax period in which you received it, filed through that period's GSTR-1 (Table 11A) and paid via that period's GSTR-3B. It is not deferred to the month you raise the final invoice or the month the client travels.

What has to be on a receipt voucher?

Your GSTIN and address, a unique serial number for the year, the client's details, a description of the advance, the amount, tax rate and tax charged, the place of supply, and whether reverse charge applies. Rule 50 treats these as mandatory, not optional.

The short version

• GST on a booking advance is due the month you receive it (Section 13(2)(a)), not the month you invoice the balance or the month the client travels.
• Every advance needs a receipt voucher (Section 31(3)(d), Rule 50), with a serial number, tax rate and place of supply, not an internal booking note.
• Report the advance in that month's GSTR-1 Table 11A, pay it via that period's GSTR-3B, and net it back out through Table 11B once the final invoice is raised.
• A genuine, unallocated supplier deposit isn't a taxable advance under Section 2(31), but the moment you apply it against a booking's price, it becomes one.
• On the 5% no-ITC slab, tax on an advance is straight cash out, often before the supplier payment it funded has even been recovered from the client's balance.
• If a booking cancels after the advance was taxed, a refund voucher (Section 31(3)(e), Rule 51) reverses it, referencing the original voucher's number and date.
• If you've been invoicing only at departure, fix the process going forward and get your CA to size the interest exposure (up to 18% p.a.) on past periods separately.