finance8 min read

Restaurant working capital calendar: rent, GST, payroll vs T+7–14

Monthly cash calendar for Indian restaurants; when rent, GST, payroll, and statutory payments hit vs when Zomato/Swiggy settle T+7 to T+14, and how to size working capital.

By Forkcast Editorial · HORECA research team

Indian restaurants don't fail because the food cost spreadsheet is wrong. They fail because rent leaves on the 1st, salaries on the 5th, and Zomato money from last fortnight's orders lands on the 12th. P&L profitability and cash solvency are different problems; the gap is timing. Here is the monthly working capital calendar; when money leaves, when it arrives, and how to size the buffer so week one doesn't break you.

The structural mismatch

A Pune casual dining doing ₹18L monthly revenue with 55% from aggregators has roughly ₹10L sitting in settlement lag at any point. Salaries (₹3.2L), rent (₹1.8L), and EMI (₹85k) need ₹5.85L in the bank by the 7th. Aggregator settlements for the last 10 days of the prior month may not have cleared yet. That's the working capital problem; not margin, timing.

Monthly outflow calendar

Date windowOutflowTypical amount (₹5L fixed-cost outlet)Notes
1stSalaries (net pay)₹2,80,000-3,50,000Largest single outflow; non-negotiable timing
1st-5thRent₹1,50,000-2,20,000Often 1st; sometimes 5th-7th per lease
5th-7thEMI (equipment / loan)₹60,000-1,20,000Fixed; missed EMI hits CIBIL
7th-10thEPF + ESI₹35,000-65,000Statutory; late payment attracts interest
10th-15thElectricity + gas₹45,000-90,000BESCOM/MSEDCL cycles vary
11th-13thGSTR-3B (GST)₹40,000-1,20,000Monthly; input credit reduces net
7th-25thTDS / professional tax₹15,000-40,000Depends on headcount and structure
WeeklySupplier payments₹80,000-1,50,000/wkCOD, 7-day, or 30-day credit
WeeklyAggregator ad prepay₹20,000-60,000/wkOften deducted from settlement instead
Ad hocR&M, licences, misc₹25,000-80,000Spikes in summer (AC) and pre-festive
Week 1 outflows for a typical casual dining often exceed ₹6L before a single rupee of current-month aggregator settlement arrives. If your opening bank balance on the 1st is under ₹8L, you are structurally under-capitalised; not temporarily tight.

Monthly inflow calendar (by channel)

ChannelSettlement timing% of revenue (typical)Cash impact
Dine-in cashSame day15-25%Immediate; funds week 1 outflows
Card / UPI (POS)T+1 to T+210-20%Arrives by 3rd-5th
Direct WhatsApp / UPISame day3-8%Best working capital channel
ZomatoT+7 to T+1425-40%Week 2-3 inflows from week 1-2 orders
SwiggyT+7 to T+1420-35%Same lag; batches 2-3× per week
Catering advancesIrregular2-10%High impact when booked; lumpy

The four-week cash rhythm

Week 1 (1st-7th); the trough

Salaries, rent, EMI, and EPF hit. Dine-in cash and T+1 card settlements partially offset, but aggregator money from the prior month's last week is still in flight. This is when owners dip into savings, delay supplier payments, or miss statutory deadlines. Target: enter week 1 with 2× monthly fixed costs in the bank.

Week 2 (8th-14th); aggregator catch-up

T+7 settlements from week 1 orders start landing. GST payment window opens. Supplier payments for the prior week's purchases go out. Bank balance typically recovers 40-60% from the week 1 low if revenue was steady.

Week 3 (15th-21st); the peak

Highest cash week for aggregator-heavy outlets. Settlements from weeks 1-2 orders clear; dine-in revenue from the full month accumulates. Utilities and mid-month supplier cycles hit, but net inflow usually positive. Good week to pay down overdue suppliers and refresh inventory.

Week 4 (22nd-end); the drift

Revenue continues but owners often spend down the week 3 peak on inventory stocking, marketing prepay, or owner draw. Orders placed in the last 7-10 days of the month won't settle until week 1-2 of the next month; creating the next trough. Don't confuse week 3 peak balance with sustainable working capital.

Worked example: aggregator lag vs payroll

DayEventCash in (₹)Cash out (₹)Running balance (₹)
1stOpen + salary3,20,0009,00,000 → 5,80,000
3rdRent1,80,0004,00,000
5thEMI + utilities1,20,000 (POS)1,45,0003,75,000
8thZomato T+7 batch2,10,0005,85,000
10thGST + suppliers1,60,0004,25,000
12thSwiggy T+7 batch1,85,0006,10,000
15thZomato T+7 batch2,30,00090,000 (suppliers)7,50,000

Opening balance ₹9L looks healthy. By the 5th it's ₹3.75L; below one week of fixed costs. Aggregator settlements don't recover the position until mid-month. Without ₹9L opening, this outlet delays salary or statutory payments. For the full 13-week rolling template, see restaurant cash flow forecasting template.

Sizing working capital

  1. Calculate monthly fixed outflows; salaries + rent + EMI + average utilities + statutory. That's your floor.
  2. Calculate aggregator float; monthly aggregator GMV × (average settlement days ÷ 30). At ₹10L aggregator revenue and T+10, float is ~₹3.3L permanently locked.
  3. Add safety margin; 0.5× monthly fixed for bad weeks (rain, festival dip, equipment breakdown).
  4. Target operating cash; fixed outflows + aggregator float + safety margin. For a ₹5L fixed / ₹10L aggregator outlet: ₹5L + ₹3.3L + ₹2.5L ≈ ₹10.8L minimum.

Three levers to shorten the calendar gap

  • Push aggregators to T+7; cuts aggregator float roughly in half. Worth asking at every quarterly account review.
  • Grow direct UPI / WhatsApp to 10-15%; same-day settlement funds week 1 outflows without touching working capital reserves.
  • Negotiate 30-day supplier credit; by month 3, half your suppliers on 30-day terms adds 15 days payable float; effectively ₹1.5-2.5L of free working capital on a mid-size outlet.
Print the outflow calendar and tape it in the accounts area. Every Monday, compare bank balance to the next 14 days of known outflows. If balance < next 14 days outflows, trigger the levers (delay non-critical spend, push supplier terms, skip optional ad prepay) before week 1, not during it.
Compute fixed-cost floor and break-even →

More for you

Restaurant working capital calendar: rent, GST, payroll vs T+7–14 | Forkcast