Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 5 May 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024

Knowledge Card

Problem

Restaurant chain finance leaders deciding how to handle aggregator reconciliation face three structurally different options — build in-house with Excel, SQL, and a data team; buy a per-aggregator reconciliation tool; or deploy reconciliation infrastructure with restaurant industry preset as one vertical — and need a TCO framing, capability checklist, and evaluation rubric that holds across multi-aggregator, multi-outlet, multi-GSTIN, multi-state, and multi-channel scope without confusing the choice with a pricing comparison.

How It's Resolved

Frame TCO across six components (finance time, audit risk, dispute window losses, ITC and cash-ledger leakage, ERP integration cost, scale-out cost); apply a capability checklist covering multi-aggregator coverage, India tax framework (Section 393 TDS at 1% with payment code 1010, Section 52 CGST TCS, Section 9(5)), GSTR-2B and GSTR-8A integration, audit evidence, and ERP write-back; score candidates on a ten-dimension rubric; map the right option to chain scale (build below 10 outlets and single GSTIN, per-aggregator tool below 30 outlets and single aggregator, reconciliation infrastructure at multi-aggregator or 30-plus outlet scale).

Configuration

TCO model with six components and chain-scale parameters; ten-dimension capability scorecard; Section 393 TDS calculator at 1% with payment code 1010; Section 52 CGST TCS calculator with intra-state CGST/SGST and inter-state IGST split; Section 9(5) GST classifier; GSTR-2B commission ITC matcher per GSTIN; GSTR-8A cash-ledger acceptance flow with GSTR-3B utilization; CARO 2020 audit evidence retention rule set; ERP connector inventory; pilot protocol for 30-day three-cycle two-outlet two-aggregator evaluation.

Output

A vendor evaluation conclusion mapped to the chain's actual scope — aggregator count, outlet count, GSTIN spread, ERP stack, audit posture — with a TCO comparison that prices in the components a headline subscription does not, a capability gap analysis against the ten-dimension scorecard, and an implementation timeline aligned to GSTR-3B and quarterly TDS filing windows.

A 100-outlet restaurant chain processes ₹15 crore monthly aggregator GMV across Zomato, Swiggy Food, Swiggy Instamart, ONDC, and a direct-channel order rail. The chain operates under 12 GSTINs across 7 states. At a blended 26 percent commission rate that is roughly ₹3.9 crore monthly commission, ₹70 lakh of monthly 18% GST on commission as input tax credit, ₹15 lakh of monthly Section 393 TDS receivable under payment code 1010, and ₹15 lakh of monthly Section 52 CGST TCS cash-ledger credit. SLA penalty exposure on Swiggy alone runs ₹2 to 5 lakh weekly. Dispute window leakage at this scale is a permanent expense line.

The CFO is choosing between three reconciliation options. This article is the buyer’s evaluation framework for that choice.

The Three Options

Option A — Build in-house. Excel macros for aggregator file ingestion, SQL queries against a POS data warehouse, a data team owning weekly cycle close, and a finance manager owning the tax posting layer. Lower visible cost, higher operating cost, brittle at scale.

Option B — Buy a per-aggregator reconciliation tool. Products in the aggregator-side reconciliation category dedicated to one or two aggregator surfaces. Examples of the per-aggregator tool category cover Zomato or Swiggy individually with strong order-level traces. Adding a second aggregator typically means a second tool.

Option C — Reconciliation infrastructure. A config-driven engine that treats restaurant aggregator reconciliation as one of multiple industry presets, with multi-aggregator, multi-source, multi-statute, multi-outlet, multi-GSTIN scope on a single rule engine. The chain configures rules; the engine closes cycles.

TCO Framing Without Pricing

A common failure mode in vendor evaluation is comparing the headline subscription line of two products and missing the five other TCO components. The framing below is qualitative because the right pricing question is per-chain and not a public number.

Component 1 — Finance team time. A 100-outlet chain on Build typically dedicates 2 to 4 full-time-equivalent finance team members to aggregator reconciliation. Per-aggregator tools cut that to 1 to 2 FTE per aggregator handled. Reconciliation infrastructure typically operates at 0.5 to 1 FTE for the full multi-aggregator scope at this size, with the team focused on exception review rather than data assembly.

Component 2 — Audit risk cost. GST audit findings on commission ITC mismatch, Section 52 cash-ledger leakage, and Section 9(5) misclassification carry expected-value cost in the form of demand notices, interest, and penalties. CARO 2020 qualifications carry reputational and lender-relationship cost. Build approaches and per-aggregator tools that do not close GSTR-2B and GSTR-8A acceptance materially raise this expected value.

Component 3 — Dispute window losses. Swiggy’s 7 to 14 day Partner Portal dispute window and Zomato’s equivalent windows close permanently if missed. At ₹15 crore monthly GMV, even a 0.3 percent dispute-window leakage is ₹4.5 lakh a month or ₹54 lakh a year — exceeding any reasonable reconciliation product cost.

Component 4 — ITC and cash-ledger leakage. Unclaimed commission ITC and unaccepted Section 52 cash-ledger credit are the two largest pure-rupee leak heads. At ₹70 lakh monthly commission ITC and ₹15 lakh monthly TCS, even a 5 percent leakage is ₹4.25 lakh a month.

Component 5 — ERP integration. Build approaches re-key data into Tally, SAP, Oracle, NetSuite, or Zoho. Per-aggregator tools require a separate ERP integration per tool. Reconciliation infrastructure typically ships native ERP write-back across major Indian-deployed stacks.

Component 6 — Scale-out cost. Adding a new aggregator (ONDC, Magicpin, a regional aggregator) is a multi-month project on Build, a separate tool selection on per-aggregator approach, and a configuration change on reconciliation infrastructure. Adding a new GSTIN is a parallel concern for build and per-aggregator approaches; on reconciliation infrastructure it is a rollup-dimension addition.

Capability Checklist

A reconciliation product evaluated for a 30-plus outlet chain must score against the following capabilities. This is the minimum set, not an aspirational list.

Capability	Why it matters
Multi-aggregator on one engine	Zomato + Swiggy Food + Swiggy Instamart + ONDC + Magicpin + direct-channel as sources
Multi-outlet, multi-GSTIN rollup	Outlet, GSTIN, state, channel, chain levels
Section 393 TDS at 1% with payment code 1010	India income tax framework on aggregator settlements
Section 52 CGST TCS with split	Intra-state CGST/SGST or inter-state IGST
Section 9(5) GST classifier	Operator-paid output GST vs restaurant’s own outward supply
GSTR-2B commission ITC matching	18% GST on commission as input tax credit per GSTIN
GSTR-8A acceptance flow	Cash-ledger credit with GSTR-3B utilization mapping
SLA penalty parser	Swiggy-specific operational deduction line
Restaurant-borne vs platform-borne classifier	Discount component classification for revenue and TDS base
Dispute-window flagging	Swiggy and Zomato Partner Portal cut-offs
CARO 2020 audit evidence	Pull-on-demand multi-statute trace
ERP write-back	Tally, SAP, Oracle, NetSuite, Zoho without per-aggregator project
Implementation timeline	2 to 4 weeks is the industry-typical config-driven benchmark

Ten-Dimension Evaluation Rubric

Score each candidate on a 0 to 5 scale per dimension.

Aggregator coverage — count of native aggregator connectors on the same engine.
Source rail count — aggregator, POS, bank, GST as four rails; how many close end-to-end.
India tax framework — Section 393, Section 52, Section 9(5), Section 17(5) blocked credits.
GST portal integration — GSTR-2B match and GSTR-8A acceptance per GSTIN.
Multi-outlet, multi-GSTIN rollup — five rollup dimensions, continuous output.
Audit evidence — CARO 2020 pull-on-demand for any cycle, any outlet, any GSTIN.
Dispute and SLA management — Swiggy and Zomato Partner Portal windows, with operational routing.
ERP write-back — native connectors across Indian-deployed stacks.
Implementation timeline — go-live cycle close inside one filing month.
Operating model — exception-led review (target) vs data-assembly (anti-pattern).

A candidate scoring below 3 on any of dimensions 3, 4, or 6 should be ruled out for a 30-plus outlet chain regardless of headline.

When to Choose Each Option

Choose Build (Option A) when the chain is below approximately 10 outlets and ₹50 lakh monthly aggregator GMV, operates within a single GSTIN, has one aggregator only, and has a finance team comfortable with weekly Excel cycle close. Plan the transition before the break point — typically the second aggregator addition or the second GSTIN — not after.

Choose a per-aggregator tool (Option B) when the chain is single-aggregator-heavy (more than 80 percent of GMV on one aggregator), below 30 outlets, with single or limited GSTIN spread, and a finance team willing to own the GST portal interface, the four-rail close, and the ERP write-back manually.

Choose reconciliation infrastructure (Option C) at multi-aggregator scope, 30-plus outlets, 3-plus GSTINs, a CARO 2020 audit posture, and any requirement for native ERP write-back. The break-even shifts down further if the chain is growing — adding a new aggregator or a new GSTIN every quarter exhausts the per-aggregator approach quickly.

For the engine surface, see restaurant reconciliation software India and the broader payment gateway reconciliation money page. For named comparison against the per-aggregator category, see vs Cointab.

Vendor Evaluation Protocol

A clean evaluation has five steps:

Define the four-rail close standard — aggregator, POS, bank, GST — that any candidate must demonstrate end-to-end on the chain’s actual data.
Score on the ten-dimension rubric. Eliminate candidates below 3 on dimensions 3, 4, or 6.
Run a 30-day pilot on three weekly cycles for two outlets across two aggregators. Validate cycle close inside one filing month.
Assess implementation timeline. A config-driven engine typically goes live in 2 to 4 weeks; build approaches and per-aggregator tool stacks can run several months. The benchmark to apply is whether go-live falls inside the chain’s next filing month.
Validate audit posture. Pull CARO 2020 evidence on the pilot data; have the chain’s auditor sign off on the trace before sign-off on the vendor.

For the regulatory walkthroughs underpinning the framework, see Section 393 TDS new Income Tax Act reconciliation, TDS payment codes 1001-1092, and the broader pillar at restaurant reconciliation India. The GST portal hosts the GSTR-2B, GSTR-8A, and electronic cash ledger interfaces that any reconciliation must reconcile against.

For the restaurant chain industry surface, see the Restaurant Chains industry guide.

The questions below address the build vs buy vs vendor evaluation decisions most often raised by finance leaders at multi-outlet restaurant chains in India.

Primary reference: Goods and Services Tax portal — where Section 52 of the CGST Act, Section 9(5) liability rules, GSTR-2B matching, GSTR-8A acceptance, and the electronic cash ledger interface are hosted.

Frequently Asked Questions

How should a restaurant chain frame total cost of ownership for aggregator reconciliation?

TCO has six components, none of them the headline subscription cost. First, finance team time at full-loaded cost — typically the largest line. Second, audit risk cost — the expected value of GST audit findings, CARO 2020 qualifications, and Section 393 TDS receivables that lapse. Third, dispute window losses on Swiggy and Zomato that go unrecovered. Fourth, ITC and cash-ledger leakage on commission GST and Section 52 TCS that is never claimed. Fifth, ERP integration and re-keying labour. Sixth, scale-out cost when adding a new aggregator or a new state GSTIN. A spreadsheet is cheap on line one and expensive on every other line; reconciliation infrastructure inverts that profile.

What is the capability checklist for evaluating restaurant aggregator reconciliation software in India?

The minimum capability set is: multi-aggregator coverage (Zomato, Swiggy Food, Swiggy Instamart, ONDC, Magicpin, direct-channel) on a single engine; multi-outlet and multi-GSTIN rollup at outlet, GSTIN, state, channel, and chain level; India tax framework support — Section 393 TDS at 1% with payment code 1010, Section 52 CGST TCS with intra-state CGST/SGST and inter-state IGST split, Section 9(5) GST classifier, Section 17(5) blocked-credit handling; GSTR-2B commission ITC matching; GSTR-8A cash-ledger acceptance flow; GSTR-3B utilization mapping; CARO 2020 audit evidence retention; ERP write-back to Tally, SAP, Oracle, NetSuite, and Zoho without per-aggregator integration projects; SLA penalty and dispute-window management for Swiggy.

When does building in-house with Excel and SQL still make sense for a restaurant chain?

Build in-house with Excel and SQL is defensible for chains below approximately 10 outlets and ₹50 lakh monthly aggregator GMV, and only if the chain operates within a single GSTIN. The break point is the cycle close that slips past the GSTR-3B and quarterly TDS filing windows. Once cycle close is at risk, the cost of audit findings and lapsed receivables exceeds the cost of any reconciliation product within one quarter. Chains that are growing fast should plan the transition before the break point, not after.

What is the difference between per-aggregator reconciliation tools and reconciliation infrastructure?

Per-aggregator reconciliation tools — the category of products dedicated to a single aggregator surface — own the deduction trace inside that platform's settlement file. They are typically excellent at Zomato or at Swiggy individually. They stop at the platform boundary: GSTR-2B commission ITC matching, GSTR-8A cash-ledger acceptance, multi-aggregator consolidation, four-rail joins (aggregator + POS + bank + tax), and ERP write-back are usually outside the tool's scope. Reconciliation infrastructure treats restaurant aggregator reconciliation as one preset of many verticals on a config-driven engine, with all of those capabilities native and consistent across aggregators.

How should a 100-outlet chain run a vendor evaluation?

Run a five-step evaluation. Step 1, define the four-rail close standard — aggregator, POS, bank, GST — that any candidate must demonstrate end to end. Step 2, score on the ten-dimension rubric (multi-aggregator, multi-outlet, India tax framework, GSTR-2B match, GSTR-8A acceptance, CARO 2020 evidence, ERP integration, dispute-window management, SLA penalty handling, multi-GSTIN rollup). Step 3, run a 30-day pilot on three weekly cycles for two outlets across two aggregators to validate cycle close. Step 4, assess implementation timeline (industry typical is 2 to 4 weeks for a config-driven engine; significantly longer for build-in-house or per-aggregator tool stacks). Step 5, validate audit posture — pull CARO 2020 evidence on the pilot data and have the chain's auditor sign off.

What audit-grade evidence does CARO 2020 require for restaurant aggregator reconciliation?

CARO 2020 reporting requires the auditor to comment on internal financial controls, on undisputed statutory dues paid on time, and on any material discrepancy between physical and book records. For aggregator reconciliation, the evidence set is: order-level trace from gross sale through commission, GST on commission, Section 393 TDS, Section 52 CGST TCS, restaurant-borne discounts, SLA penalties, and refund reversals to the bank credit; reconciled GSTR-2B commission ITC per GSTIN; accepted GSTR-8A entries with cash-ledger utilization mapped to GSTR-3B; new TDS statement validation against book Section 393 receivable. Pull-on-demand for any cycle, any outlet, any GSTIN.