Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Outdoor catering revenue in India does not match a dine-in restaurant's POS-and-bank pattern — it is B2B with credit terms, advance receipts, milestone billing, 18%-with-ITC GST, and customer-deducted TDS under Section 393(1)(a) payment code 1002, which makes a standard restaurant close model inapplicable.
Match purchase order against event manifest, milestone invoices, and final tax invoice; reconcile advance receipts to GSTR-1 Table 11 and adjustments via Table 11A; net bank credit against invoice value minus customer-side TDS, then verify the deducted amount appears in Form 26AS within the same quarter.
Per-customer rate card, head-count tolerance band, milestone schedule (booking advance percent, pre-event percent, final reconciliation window), customer GSTIN and PAN map for TDS validation, and 18%-with-ITC routing for inputs against catering revenue.
A daily and per-event close that ties contracted PO value to bank receipts across milestones, surfaces advance-to-invoice gaps as Section 13 exposures, and produces a quarterly 26AS reconciliation pack against TDS deducted by corporate customers.
A Bangalore caterer running a 40-event-per-month operation across corporate offsites, weddings, and institutional canteens closes the books on March and finds that ₹68 lakh of issued invoices does not tie to ₹54 lakh of bank receipts. The gap is not bad debt. Most of it is customer-deducted TDS that has been booked as a receivable but not reconciled against Form 26AS, plus three advance receipts that were treated as bookings instead of taxable supplies under Section 13, plus a final-reconciliation invoice that lost a head-count upgrade because the event manifest never reached finance. Outdoor catering reconciliation in India is not a variant of dine-in restaurant reconciliation — it is a different match shape, a different tax profile, and a different audit trail.
Why outdoor catering reconciles differently from a dine-in restaurant
A dine-in restaurant in India runs a four-rail close — aggregator payouts, POS gateway settlements, UPI, and physical cash — taxed at 5% GST without input tax credit. The match is POS day-end to bank credit, on a daily cycle. Outdoor catering inverts almost every parameter.
The supply is taxed at 18% GST with full input tax credit, under the catering classification rather than the standalone-restaurant 5%-no-ITC notification. Settlements are B2B with credit terms of 30 to 60 days, not card-and-cash on the day of supply. Cash flow runs on advance receipts and milestone invoices, which trigger Section 13 time-of-supply rules independent of when the event happens. And because the customer is typically a corporate, the payment lands net of TDS that the customer has deducted at source — under Section 393(1)(a) payment code 1002 of the Income Tax Act 2025, replacing the legacy Section 194C.
The reconciliation match is therefore PO to event manifest to tax invoice to bank receipt, with 26AS as a parallel quarterly leg. None of the dine-in primitives — POS day-end, cash deposit slip, aggregator settlement file — apply.
The four documents that anchor the close
A clean catering close needs four documents per event, in this order.
Purchase order. The customer’s PO carries the contracted head count, menu, per-head rate, GST treatment, payment terms, customer GSTIN, and customer PAN. Without a customer PAN on the PO, the caterer cannot validate downstream TDS credit in 26AS — and a 1% to 2% receivable becomes irrecoverable.
Event manifest. On the day, the operations team records actual head count served, menu changes, additional courses, extension hours, and damage charges. This is the only document that captures the difference between PO-priced revenue and earned revenue. If the manifest does not reach finance within 24 hours of event close, the final invoice goes out understated and the gap is permanent.
Tax invoice. Priced from the manifest, applies the 18% GST with ITC routing on the catering line. For a multi-day event with milestone billing, this is the third invoice in the chain — preceded by a booking-advance receipt voucher and a pre-event milestone invoice — and it nets prior advances explicitly so that the GSTR-1 outward supply does not double-count.
Bank receipt. Arrives net of customer-deducted TDS. The receipt amount must equal invoice value minus TDS deducted at the prescribed rate. The TDS itself is reconciled against Form 26AS in the quarter the customer files Form 26Q.
How GST rules differ from a dine-in close
The 18%-with-ITC treatment is the structural advantage of catering revenue from a tax-cost standpoint, but it requires a more disciplined working sheet than a flat-5%-no-ITC restaurant.
Inputs — kitchen ingredients, packaging, transport, hired staff, equipment rental, venue rental — carry varied GST rates (5% on most foodstuffs, 12% on packaged goods, 18% on services and equipment). Each input invoice’s ITC can be claimed only against the 18%-catering revenue line, not against any 5%-restaurant revenue line the same legal entity may run. The restaurant GST 5% vs 18% reconciliation guide covers the segregation discipline in detail; for a catering-only entity the discipline simplifies but the documentation rigour does not.
Advance receipts are the second GST trap. Section 13 of the CGST Act fixes the time of supply for services as the earlier of invoice date or payment receipt date. A booking advance received in March for a June wedding triggers GST liability in March. The caterer must issue a receipt voucher, report the advance in GSTR-1 Table 11, and pay 18% in March’s GSTR-3B. When the June final invoice is issued, the prior advance is adjusted through Table 11A. A caterer who treats advances as deposits rather than taxable supplies under-reports outward supply for two quarters and faces a Section 73 demand on assessment.
TDS under Section 393(1)(a) payment code 1002 — the new contractor regime
The Income Tax Act 2025 reorganises TDS into a payment-code structure, replacing the section-based scheme of the 1961 Act. Catering services received by a corporate customer fall under Section 393(1)(a) payment code 1002 — the contractor regime that succeeds the legacy Section 194C. The rate structure carries forward: 1% where the payee is an individual or HUF and 2% otherwise, with the threshold and exemption rules set out in the 2025 Act. A deeper walk-through of the new code system is in the Section 393 TDS new Income Tax Act reconciliation guide.
For the caterer, the operational consequence is unchanged in shape but renamed in form. Each corporate customer deducts the prescribed percentage from each milestone payment, deposits it monthly, and reports it in the quarterly Form 26Q under payment code 1002. The caterer’s Form 26AS reflects the credit roughly six to ten weeks after the deduction. The reconciliation control is a rolling quarterly match: TDS booked as a receivable per ledger versus TDS credit in 26AS per PAN. Mismatches are resolved before income-tax return filing — by then, missing credit is hard to recover.
References to “194C” still appear in older POs, contract templates, and customer ERP screens. Those are legacy labels; the operative provision for deductions on current-year payments is Section 393(1)(a) payment code 1002.
Variance taxonomy — catering close
| Variance | Common root cause | Resolution path |
|---|---|---|
| Bank receipt below invoice value | Customer TDS deducted at source | Match against Form 26AS; book TDS receivable per PAN |
| Bank receipt below invoice net of TDS | Discount, damage charge, or short delivery | Credit note via GSTR-1; reverse output GST in same period |
| Advance not in GSTR-1 Table 11 | Booking treated as deposit | Restate; pay GST with interest; issue receipt voucher |
| Final invoice missing manifest upgrade | Operations did not pass manifest to finance | Tighten 24-hour manifest cut-off; raise supplementary invoice |
| 26AS shows TDS credit but ledger has no receivable | Customer paid net but PO had no PAN | Trace via TAN; book in current quarter; update PO template |
| ITC claimed against 5% revenue line | Mis-routed input on a mixed-revenue entity | Reverse claim in next GSTR-3B; rebuild routing rule |
What automated reconciliation changes for a catering operator
A multi-event catering operation closing books manually typically runs a five-to-seven-day month-end and a quarterly 26AS reconciliation that is two quarters behind. Both gaps cost real money — advance receipts get missed for Section 13, manifest upgrades fall out of the final invoice, and TDS receivables age past the recovery window.
Purpose-built reconciliation software India handles the catering match shape — PO to manifest to invoice to bank receipt — as a four-leg join with explicit milestone and advance handling. TransactIG’s 24+ industry presets include a catering configuration that segregates 18%-with-ITC revenue, applies Section 13 advance routing, and keeps a per-PAN 26AS leg for Section 393(1)(a) credits. Customer outcomes across reconciliation deployments include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022) once the PO, manifest, and invoice exports are structured. The same pattern of rigorous deduction matching that powers payment gateway reconciliation for restaurants applies here, with the deduction stack replaced by the customer-side TDS leg.
The control lift is not in the daily count — a catering business does not run 40-event days. It is in the close discipline: every advance reported in the right month, every manifest upgrade in the final invoice, every TDS receivable reconciled to 26AS in the same quarter. Operative source for the GST notifications referenced above is the GST portal. For the restaurant chain industry surface, see the Restaurant Chains industry guide. For the buying-intent surface covering this rail, see the restaurant reconciliation software for India overview, and for a head-to-head against the aggregator-side reconciliation tool category, see TransactIG vs Cointab.