Restaurant Reconciliation Software for Indian Chains
An Indian restaurant chain runs on four reconciliation rails simultaneously — aggregator settlements from Zomato, Swiggy, Magicpin, and Dunzo; POS payment gateway feeds across Pine Labs, MSwipe, Razorpay, and PayU; daily cash deposits at the outlet bank; and a GST output split between 5% restaurant service and 18% bundled offerings — across dozens of outlets, multiple GSTINs, and several states. TransactIG is reconciliation software India built for that operating reality, with native ingestion of every aggregator settlement format, MDR-by-instrument validation on the payment gateway side, and Section 393, Section 52 CGST, and Section 9(5) classification baked into the matching engine.
Why Restaurant Chain Reconciliation Is Hard
The four-rail problem
Every order at a restaurant chain lands on one of four rails, and each rail produces its own settlement file with its own commission structure, tax treatment, and reconciliation cadence. An aggregator order from Zomato or Swiggy is a gross GMV minus commission, packaging charge, ad spend, customer cancellation, and Section 393 TDS, settled T+5 or T+7 in a consolidated payout. A dine-in card swipe through Pine Labs is gross amount minus MDR, settled T+1 to the restaurant bank. A cash bill becomes a daily deposit slip that may or may not reconcile to the POS shift close, depending on float adjustments, voids, and refunds. And a 5% GST line on the same restaurant menu is treated differently from an 18% bundled-catering line on the GSTR-1.
A reconciliation tool that treats only the aggregator rail — which is the typical posture of restaurant-tech point solutions — leaves the POS, cash, and GST rails to a finance analyst and a spreadsheet. The chain ends up with three reconciliations stitched together by hand and a fourth (GST) that nobody owns until the auditor asks for it.
Multi-outlet, multi-GSTIN, multi-state consolidation
A 60-outlet QSR chain or cloud kitchen operator typically runs across 8 to 12 states, which means 8 to 12 GSTINs, 8 to 12 state-level GST ledgers, and a separate Section 9(5) liability check per state. The aggregator delivers a single consolidated payout file that has to be split by outlet code, mapped to the correct GSTIN, and reconciled against the right state's POS register and bank account. Section 52 CGST TCS credit lands in the electronic cash ledger of the GSTIN whose name is on the aggregator portal — not necessarily the GSTIN whose outlet served the order.
A franchise model adds another layer: royalty paid to the brand owner is an inward supply with its own GSTR-2B reconciliation and Section 194J / 393 TDS schedule, separate from outbound revenue. A reconciliation system for restaurants has to handle the rollup at outlet, GSTIN, state, brand, and entity level — and produce CARO 2020 evidence at each level — without the finance team having to rebuild the data model in Excel every month.
What TransactIG Restaurant Reconciliation Does
TransactIG ingests order-level data from every aggregator, every POS payment gateway, and every outlet bank account, and matches it against the POS or ERP order register with Section 393, Section 52 CGST, and Section 9(5) classification baked in — taking match rates from the 51% typical of partial, single-rail tools to 88% through end-to-end automation.
Multi-aggregator order-level ingestion
Native parsing of Zomato Restaurant Partner exports, Swiggy Owner App settlement files, Magicpin payout statements, and Dunzo merchant payouts at order level — not just the consolidated payout. Each order carries GMV, commission, packaging charge, ad spend recovery, customer cancellation deduction, TDS withheld, and TCS withheld as separate fields ready for matching.
Section 393 + payment code 1010 TDS
Aggregator TDS deducted under the new Section 393 (replacing the legacy 194O posture) is classified against payment code 1010 and cross-matched against Form 168 — the new annual TDS statement under the Income Tax Act 2025. Cross-era cases that span the transition window are handled with both the new and legacy code references on the same return.
Section 52 CGST TCS reconciliation
1% TCS collected by the aggregator under Section 52 of the CGST Act is reconciled against the GST electronic cash ledger via GSTR-2X — kept on a separate track from income-tax TCS under Section 206C. The two ledgers are never conflated, and each carries its own evidence file for the statutory auditor.
Section 9(5) aggregator GST liability flag
Every aggregator order is flagged for Section 9(5) treatment — where the aggregator, not the restaurant, is liable for the 5% GST. Section 9(5) revenue is separated from regular dine-in revenue in the GSTR-1 and GSTR-3B working, and the split is preserved in the reconciliation register for DRC-01B / DRC-01C scrutiny response.
POS gateway with MDR-by-instrument
Pine Labs, MSwipe, Razorpay, and PayU settlement files are ingested with MDR validated by instrument type — debit card, credit card, RuPay, UPI, BharatPe QR — against the contracted rate card. MDR variances above tolerance route to an exception queue. 18% GST input tax credit on MDR is cross-referenced against the gateway's GSTIN in GSTR-2B.
Daily cash deposit variance taxonomy
Daily cash deposits from each outlet are reconciled against the POS shift close with a named variance taxonomy: CASH_SHORT, CASH_OVER, VOID, REFUND, FLOAT_ADJUST. Each variance carries its outlet, its date, its ageing, and its maker-checker status. The variance taxonomy itself is the subject of a filed patent.
The Six Reconciliation Surfaces
A restaurant chain is not a single reconciliation. It is six concurrent reconciliations on different tax frameworks, different settlement cadences, and different match keys. Each row below is a rail TransactIG reconciles natively.
| Rail | What it covers | Compliance touchpoint | Match key |
|---|---|---|---|
| Aggregator settlement (Zomato, Swiggy, Magicpin, Dunzo) | Order-level GMV, commission (typically 18-30%), packaging charges, customer cancellation deductions, ad spend recovery, net payout to restaurant | Section 393 TDS (code 1010), Section 52 CGST TCS, Section 9(5) GST liability flag | Aggregator order ID + outlet code + payout cycle |
| POS payment gateway (dine-in card and UPI) | Card swipes (Pine Labs, MSwipe), UPI QR (Razorpay, PayU, BharatPe), MDR by instrument, settlement T+1 or T+2 to restaurant bank | 18% GST input tax credit on MDR, GSTR-2B cross-match against gateway GSTIN | Terminal ID + transaction reference + settlement batch |
| Daily cash deposit at bank | Cash-on-delivery for takeaway, dine-in cash bills, float reconciliation, deposit slip versus bank credit, named variance taxonomy | CARO 2020 cash control reporting, Section 269ST cash receipt thresholds, internal financial controls | Outlet code + deposit slip number + date + amount |
| GST output (5% vs 18% split) | 5% on regular restaurant service (no ITC), 18% on outdoor catering and certain bundled services (with ITC), aggregator-routed 9(5) flag | GSTR-1, GSTR-3B reconciliation against POS register; ITC denial check on 5% line items | HSN/SAC code + invoice line + outlet GSTIN + place of supply |
| Franchise royalty inward supply | Royalty paid to brand owner (typically 4-8% of net sales), area development fees, marketing fund contribution | Section 194J + new Section 393 TDS schedule, 18% RCM where applicable, GSTR-2B cross-check | Royalty invoice + monthly net sales certificate + payout reference |
| Liquor and bar sales (state excise, outside GST) | Excise-paid liquor sales captured separately from GST output, state-specific excise reporting, bar POS to bank deposit chain | State excise return reconciliation, separate ledger isolation from GST taxable turnover | Excise category + outlet liquor licence + daily bar settlement |
Rail-specific guides: Zomato · Swiggy · Magicpin / Dunzo · POS gateway · daily cash · GST split
How TransactIG Restaurant Reconciliation Works
Connect the four rails
Aggregator settlement file ingestion (Zomato, Swiggy, Magicpin, Dunzo via portal export or scheduled pull), POS payment gateway feeds (Pine Labs, MSwipe, Razorpay, PayU), and bank statements from each outlet's collection account. Onboarding cadence is configured per rail — daily for aggregators and POS, daily-or-weekly for bank deposits.
Match at order level
Each rail is matched at the order level against the POS or ERP order register — Petpooja, UrbanPiper, Posist, Restroworks, or chain-specific in-house POS, plus Tally Prime, SAP FI, or Zoho Books on the ERP side. Section 393 TDS, Section 52 CGST TCS, and Section 9(5) GST treatment are applied as classification rules during the match — not as a downstream cleanup step.
CARO 2020 ready evidence file
Month-wise reconciliation register at outlet, GSTIN, state, brand, and entity level. Ageing report for unmatched items, maker-checker sign-off timestamps, and the named variance taxonomy across all four rails. The output is the evidence file the statutory auditor examines under CARO 2020 — produced automatically with every close cycle, not rebuilt by the finance team in Excel.
What is Restaurant Reconciliation
Restaurant reconciliation is the process of matching every order served by a restaurant outlet — whether routed through an aggregator, a dine-in card swipe, a UPI QR, or a cash bill — against the corresponding entry in the POS register, the ERP general ledger, the aggregator settlement file, the payment gateway settlement file, and the bank statement. The output is a reconciled revenue register that ties gross GMV through commissions, MDR, TDS, TCS, and GST out to the cash actually received in the restaurant's bank account.
The Indian operating context adds three constraints that generic restaurant accounting tools do not handle. First, the new Income Tax Act 2025 has consolidated aggregator TDS into Section 393 with payment code 1010, and the credit reflects in Form 168 — a shift the finance team has to absorb without losing audit continuity with legacy 194O cases. Second, Section 52 of the CGST Act, 2017 — unchanged GST law — requires aggregators to collect 1% TCS that lands in the restaurant's GST electronic cash ledger via GSTR-2X, on a track entirely separate from income-tax TCS. Third, Section 9(5) of the CGST Act shifts the GST liability for restaurant services routed through aggregators onto the aggregator itself, creating a revenue split that must be carried through GSTR-1 and GSTR-3B every month.
The practical challenge is that this has to work across 30 to 200 outlets, 5 to 15 GSTINs, multiple states, and four concurrent rails — with the statutory auditor under CARO 2020 looking for clean reconciliation evidence at each level. The system that handles this natively, rather than treating restaurant operations as a special case of generic AR reconciliation, is what makes automated reconciliation viable for a multi-outlet chain.
Manual Excel vs Aggregator-Only Tools vs TransactIG
Restaurant chains today use one of three approaches: an Excel-based monthly reconciliation built by the finance team, a single-rail aggregator reconciliation tool that solves only the Zomato or Swiggy side, or an end-to-end platform that covers all four rails with India tax framework awareness.
| Dimension | Manual Excel | Aggregator-only tools | TransactIG |
|---|---|---|---|
| Match rate | Around 51%; balance routed to manual exception handling | Higher on aggregator rail in isolation; POS, cash, and GST untouched | 88% across all four rails through automated matching |
| India tax framework | Manual classification each cycle; high error rate on Section 393 vs 52 CGST | Generic global tax model; no Section 393 / 52 CGST / 9(5) awareness | Section 393 + payment code 1010, Section 52 CGST TCS, Section 9(5) baked into the matching engine |
| Multi-outlet rollup | Pivot tables and VLOOKUPs; breaks at 30+ outlets | Outlet-level dashboard; GSTIN, state, and brand consolidation typically absent | Outlet, GSTIN, state, brand, and entity rollup as the default model |
| Audit evidence file | Rebuilt manually for each statutory audit; ageing and maker-checker often missing | Aggregator side covered; POS, cash, GST evidence still manual | CARO 2020 ready register with ageing, maker-checker, and named variance taxonomy across all rails |
| Implementation / configurability | No implementation; ongoing finance-team load and key-person dependency | Quick on the aggregator rail; new rails require custom development | 2 to 4 weeks, no-code rule configuration, 24+ industry presets including restaurant chain |
Related Guides
Restaurant & F&B Reconciliation
All articles on aggregator, POS, GST, cash, franchise, and liquor reconciliation for Indian restaurants.
Restaurant Reconciliation in India
The full process: aggregator, POS, daily cash, and the 5% vs 18% GST split with ITC.
TransactIG vs Cointab
Architectural and India tax framework comparison for multi-outlet reconciliation.
Frequently Asked Questions
What is restaurant reconciliation software? +
Restaurant reconciliation software automates the matching of revenue and cash movements across the four rails an Indian restaurant chain operates on: aggregator settlements (Zomato, Swiggy, Magicpin, Dunzo), POS payment gateway settlements (Pine Labs, MSwipe, Razorpay, PayU), daily cash deposits at the bank, and the 5% versus 18% GST output split between regular dine-in revenue and aggregator-routed orders. The software ingests order-level data from each rail, matches it against the POS or ERP order register, classifies aggregator commissions, payment gateway MDR, and packaging charges into the correct expense categories, and produces a CARO 2020 ready reconciliation register at outlet, GSTIN, and entity level.
How does Section 393 + payment code 1010 TDS replace Section 194O? +
Under the Income Tax Act 2025, the e-commerce operator TDS provisions previously housed in Section 194O have been consolidated into Section 393 of the new Act, with payment code 1010 used on the TDS return. The substantive rule is unchanged: Zomato, Swiggy, Magicpin, and other aggregators deduct TDS on the gross order value before remitting net payout to the restaurant. The restaurant has to reconcile each payout against the order register, validate the TDS amount deducted, and cross-match it against the credit reflected in Form 168 (the new annual TDS statement that replaces parts of the old Form 26AS view). TransactIG handles the new code 1010 as the primary classification and retains 194O as a legacy reference for cross-era cases that span the transition window.
Does Section 52 CGST TCS reconciliation work the same as Section 206C income-tax TCS? +
No — these are two distinct ledgers and must not be conflated. Section 52 of the CGST Act, 2017 is GST law and remains unchanged by the Income Tax Act 2025. It requires aggregators to collect 1% TCS (0.5% CGST + 0.5% SGST, or 1% IGST for inter-state) on the net taxable value of supplies made through their platform and deposit it against the restaurant's GSTIN. The restaurant claims this credit in its electronic cash ledger via GSTR-2X and uses it to discharge GST liability. Section 206C of the Income Tax Act, by contrast, governs income-tax TCS on specific categories like scrap or motor vehicles — entirely separate, separately reconciled, and credited to the income-tax PAN ledger, not the GST cash ledger. TransactIG keeps these two reconciliations on separate tracks with separate evidence files.
Can the platform handle 50+ outlets across multiple GSTINs? +
Yes. A typical mid-size restaurant chain or QSR operator runs 30 to 200 outlets across 5 to 15 states, which means 5 to 15 GSTINs and a corresponding multiplication of state-level tax positions, aggregator settlement files, and bank accounts. TransactIG ingests the consolidated aggregator payout file, splits it by outlet code and GSTIN, reconciles each outlet to its local POS register, and produces a rollup view at the GSTIN, region, brand, and entity level. Intercompany transfers between outlet operating accounts and a central pooling account are recognised as a single matched pair. Multi-state, multi-GSTIN, multi-brand consolidation is the default mode — not an enterprise add-on.
How does the platform handle Section 9(5) aggregator GST liability? +
Section 9(5) of the CGST Act, 2017 makes the aggregator — not the restaurant — liable for GST on certain notified services, including restaurant services supplied through e-commerce operators. For restaurants below the GST registration threshold, this means Zomato or Swiggy charges and deposits the 5% GST directly, and the restaurant does not raise a tax invoice on those orders. For registered restaurants, the order-level treatment depends on the menu category and the location of the restaurant in the supply chain. TransactIG flags every aggregator order against its Section 9(5) status, separates 9(5) revenue from regular dine-in revenue in the GSTR-1 and GSTR-3B working, and produces a reconciliation showing the GST liability split between the restaurant and the aggregator — the evidence the GST officer asks for during scrutiny under DRC-01B or DRC-01C.
How long does implementation take for a multi-outlet chain? +
Implementation takes 2 to 4 weeks for most multi-outlet restaurant chains. Week one covers aggregator settlement ingestion — Zomato Restaurant Partner portal exports, Swiggy Owner App settlement files, Magicpin payout statements, and Dunzo merchant payouts. Week two maps the POS data — Petpooja, UrbanPiper, Posist, Restroworks, or chain-specific in-house POS — and the ERP order register (Tally Prime, SAP FI for larger chains, Zoho Books for D2C operators) into TransactIG's matching schema. Weeks three and four apply matching rule configuration for outlet codes, GSTIN routing, MDR-by-instrument validation, and the daily cash deposit variance taxonomy. No code development is required. TransactIG is cloud-only, runs from AWS Mumbai, and is ISO 27001:2022 certified.
Stop reconciling four rails in four spreadsheets every month
TransactIG connects to your aggregator portals, POS gateways, and outlet bank accounts in 2 to 4 weeks. Section 393, Section 52 CGST, and Section 9(5) are built in. ISO 27001:2022 certified. Runs from AWS Mumbai.