The tour operator's cash-flow calendar

Your bank balance looks healthiest in October, right after Diwali advances land, and scariest in February, right when you need to pay hill hotels for summer blocks. That's not bad luck. It's the shape of the Indian tour operator's money-year, and if you don't map it on paper, you'll keep mistaking a temporarily full account for profit.

This is the piece most operators skip: a real cash-flow calendar, built around how Indian travellers actually pay, and a simple weekly forecast you can run in the Excel sheet you already have open. It also covers the working-capital options that exist for the months the calendar doesn't close on its own: OD limits, invoice discounting, MUDRA loans. And it explains why the eligibility bar for travel businesses is higher than you'd expect.

None of this is exotic. It's discipline: knowing what money is actually yours, and what money is just passing through your account on its way to a hotel or airline.

The Indian travel money-year, mapped

Outbound and domestic tour operators run on two overlapping seasonal cycles, and both create the same pattern: cash goes out months before the trip, and comes in close to departure.

Hill-station summer travel is the clearest example. Popular hill hotels for the May–June season need to be booked two to three months ahead of travel, which means you're paying supplier advances in February and March against balances your clients won't clear until May or June. Travellers routinely report booking Shimla, Manali and Ladakh properties this far out, and your outflow happens a full quarter before your inflow.

The Puja/Diwali outbound season mirrors it with a different rhythm. You block group rates and hotel allotments for Southeast Asia and Europe packages in July–August, collect the bulk of client payments through September and October as the festival approaches, and the trips actually travel in October–November. December brings its own peak: New Year packages and winter honeymoon travel, with its own advance-then-balance cycle compressed into a shorter window.

Then comes January–February: the famine. Festival trips are done, summer trips haven't been paid for yet, and you're often sitting on the year's biggest single outflow (hill hotel advances) with the year's thinnest inflow. This is exactly the demand backdrop that makes the gap dangerous rather than merely inconvenient. Outbound travel out of India keeps growing (32.7 million Indians travelled abroad in 2025, per Ministry of Tourism data reported in trade press), which means the advance amounts per file are growing too. A bigger business doesn't shrink this gap. It usually widens it, because bigger blocks need bigger advances.

Period	What goes out	What comes in
Feb–Mar	Hill hotel advances (summer)	Festive-season balances trickling in
May–Jun	Final summer supplier payments	Summer trip balances, peak collections
Jul–Aug	Diwali/Puja outbound blocks booked	Early summer-season enquiries
Sep–Oct	Winter block advances	Diwali/Puja client payments peak
Oct–Nov	December peak supplier payments	Puja/Diwali trips travel, final balances
Dec	New Year block costs	December peak collections
Jan–Feb	Summer advances due again	The famine: thinnest inflow of the year

Once this is on paper, the "surprise" cash crunch every February stops being a surprise. It's a known, recurring feature of the business, which means it's plannable.

Client advances are a liability, not income

This is the single costliest mistake in tour operator accounting, and it isn't really an accounting mistake. It's a mental one. When a client pays you ₹1,50,000 as an advance for a December trip, that money sits in your account looking exactly like revenue. It is not revenue. It is a liability: you owe that client a trip, or a refund, until the trip actually happens.

The failure mode is well documented in how tour businesses actually break: operators routinely finance the gap between what they've collected from clients and what they owe suppliers, sometimes for months at a stretch, because large group blocks demand big advance payments long before any client has actually travelled. Spend that advance on something else, even something that feels like "the business" (like a Goa hotel block for a different departure), and you've created a liability with no asset behind it.

Example: An operator collects ₹18 lakh in Diwali advances across 40 pax for a Vietnam departure in October. Instead of holding it, she uses ₹12 lakh of it to lock a Goa New Year block, planning to top it up from November's incoming balances. In late September, a regional flight disruption spooks 10 of the 40 travellers and they cancel, entitled to most of their advance back under her own cancellation terms. She now owes roughly ₹4.5 lakh in refunds she doesn't have, because the cash is sitting in a hotel's account in Goa, not hers.

That scenario isn't a hypothetical edge case. It's the standard way seasonal travel businesses go under. The fix isn't complicated, just uncomfortable to enforce: ring-fence advances against the specific departure they belong to, and don't touch them for anything else until that trip has travelled and the supplier is paid. If your cancellation policy allows meaningful refunds, treat every rupee of advance as refundable until the trip is non-cancellable.

Careful: "But the money's just sitting there, why not use it for two weeks" is how every version of this failure begins. Two weeks becomes six when the next crunch hits, and the departure you borrowed from is the one that gets stranded.

Building a 13-week rolling forecast in the sheet you already use

You don't need new software for this. You need one more tab in the Excel or Google Sheet you already run the business on, with 13 columns (one per week) and the following rows.

1. Opening balance: carried from last week's closing balance.
2. Client balances due this week: pull straight from your booking sheet by departure date minus your standard payment-schedule lead time.
3. Supplier advances due this week: every hotel, DMC and airline advance with a contracted due date.
4. GST payable this week: GST on tour operator services is due on invoicing or on receipt of an advance, whichever comes first, because advances for services attract GST at the time of receipt under the 5%-without-ITC scheme, not at the time of departure. That means the tax outflow can land before the client's balance payment does. Plan the cash for it the moment you issue a receipt voucher, not when the trip travels.
5. TCS deposited this week: TCS collected on overseas tour packages has its own monthly deposit rhythm early in the following month; treat it as a fixed, recurring outflow and confirm the exact due date with your CA (see the TCS playbook for the collection side of this).
6. Salaries and fixed costs: rent, salaries, software, the boring recurring stuff that doesn't pause for the off-season.
7. Closing balance: opening + inflows − outflows. This becomes next week's opening balance.

Fill in weeks 1–4 from actual booking and supplier data. You know these numbers today. Weeks 5–13 will be estimates based on your pipeline and seasonal pattern from the table above. Update it every Friday. The point isn't precision to the rupee; it's seeing, four to six weeks out, which week goes negative, while you still have time to do something about it.

Week	Opening balance	Client balances in	Supplier advances out	GST/TCS out	Salaries/fixed	Closing balance
1	₹8,40,000	₹3,20,000	₹5,00,000	₹95,000	₹2,10,000	₹3,55,000
2	₹3,55,000	₹1,80,000	₹0	₹40,000	₹0	₹4,95,000
3	₹4,95,000	₹0	₹6,50,000	₹0	₹2,10,000	(₹3,65,000)

A negative closing balance in week 3, spotted in week 1, is a solvable problem: delay a discretionary supplier payment, chase an overdue client balance, or draw against a credit line sized for exactly this. The same negative number discovered in week 3 itself is a crisis call to a hotel asking for more time.

When the calendar doesn't close on its own: financing options by problem type

A well-run forecast tells you when you'll be short. It doesn't make the shortfall disappear. For that, match the financing tool to the actual problem. These are not interchangeable, and using the wrong one is expensive.

Seasonal hotel-block advances (the Feb–Mar and Jul–Aug crunches). This is a working-capital timing gap, not a growth need, so the right tool is an overdraft or cash-credit limit against your current account, sized to roughly two months of your typical supplier-advance outflow. Pull that number straight from your 13-week forecast. You draw it down in the advance-heavy months and clear it as client balances arrive. This is the cheapest, most flexible option for a recurring, predictable gap, because you only pay interest on what you actually draw.

B2B receivables from corporates. If a chunk of your revenue is corporate MICE or incentive travel billed on 30–60 day terms, you're financing someone else's payables cycle. Invoice discounting (or TReDS if you're Udyam-registered and dealing with larger corporates) lets you get paid against a raised invoice instead of waiting out the client's payment cycle. This only works cleanly if your invoicing is disciplined; a lender is financing your invoice, not your relationship.

Growth capex: a new branch, a fleet of vehicles, a bigger DMC operation. This isn't a cash-flow timing problem, it's an investment, and it deserves a term loan, not a revolving line. MUDRA (PMMY) loans are explicitly built for this, cover services-sector businesses including small travel agencies, hotels and tour operators, and are collateral-free:

MUDRA category	Loan amount
Shishu	Up to ₹50,000
Kishore	₹50,001 – ₹5 lakh
Tarun	₹5 lakh – ₹10 lakh
Tarun Plus	₹10 lakh – ₹20 lakh (for borrowers who've already repaid a Tarun loan)

The Tarun Plus category, effective from October 2024, extends collateral-free borrowing up to ₹20 lakh, useful headroom if you've already built repayment history on a smaller MUDRA loan.

The eligibility reality lenders won't advertise upfront. Banks classify travel and tourism as a high-risk services category, which means approval hinges less on your revenue story and more on paperwork: Udyam (MSME) registration, two years of clean ITRs, and GST returns filed on time and matching your bank statements. CGTMSE cover, which lets lenders offer collateral-free loans to micro and small enterprises, lowers the approval bar considerably. It's worth asking any lender explicitly whether your loan qualifies for CGTMSE backing before you assume you need collateral. Reports suggest the CGTMSE per-borrower guarantee ceiling was raised as high as ₹5 crore in 2023. Confirm the current ceiling and your eligibility directly on cgtmse.in before you plan around a specific figure.

Do this paperwork in your quiet January–February month, not when you're already short in March. Lenders move slowly; your hill-hotel supplier does not.

Why funding blocks purely from client advances is disguised leverage

Here's the uncomfortable version of the point above: if you're routinely financing supplier advances entirely from other clients' payments (this departure's block paid for by that departure's advances), you are running a leveraged business without calling it one, and without the discipline a real lender would impose.

A bank asks for security, a repayment schedule and proof you can service the debt. A client's advance asks for nothing except a trip that hasn't happened yet. That's not safer borrowing. It's borrowing with worse terms and no visibility, because it's invisible on your P&L until a cancellation wave or a delayed supplier refund exposes it all at once. If your fixed-departure break-even maths already tells you a block needs 70% occupancy to clear cost, funding that block's advance entirely from someone else's deposit means you have zero cushion left if occupancy or timing slips.

The fix is the same ring-fencing discipline from earlier in this post, applied at the level of the whole business: know, every week, which cash in your account is actually yours (earned, delivered, non-refundable) versus which cash is a liability waiting to become either a trip or a refund. A payment schedule that collects appropriately staged advances helps, but it only protects you if you then treat those advances as owed money, not found money.

The short version

• Map your business against the real Indian travel calendar: hill-season advances go out Feb–Mar against May–Jun revenue; Diwali/Puja outbound blocks go out Jul–Aug against Oct–Nov revenue; Jan–Feb is the structural famine every year, not bad luck.
• Client advances are liabilities. Ring-fence each departure's advance until that trip has travelled and its suppliers are paid; never borrow from one departure's deposits to fund another's block.
• Run a 13-week rolling forecast in Excel with rows for client balances, supplier advances, GST on advances, TCS deposits and salaries. GST on a 5%-without-ITC package is often due the moment you receive the advance, not when the trip travels.
• Size an OD/CC limit to roughly two months of your typical seasonal supplier-advance outflow; it's the cheapest fix for a recurring, predictable gap.
• Match financing to the actual problem: OD/CC for seasonal timing, invoice discounting or TReDS for slow-paying B2B corporates, a MUDRA term loan for genuine growth capex.
• Get Udyam-registered, keep two years of clean ITRs and file GST returns on time. That paperwork, not your pitch, is what actually gets a travel business approved for collateral-free lending.
• Do the loan paperwork in your quiet season. Rates and thresholds here are current as of July 2026; confirm specifics with your CA or lender before committing to any figure.