Executive Overview
For thousands of restaurant owners across India, the weekly ritual is almost identical: a digital spreadsheet arrives from Swiggy or Zomato, detailing the financial ecosystem of their delivery business. It outlines gross sales, commissions, logistics fees, taxes, and net payouts. For the vast majority of operators, these dense workbooks are treated as administrative finalities. Past the initial summary tab—where the final net transfer figure sits—the files are rarely opened, let alone audited.
However, a closer, line-by-line technical inspection of real-world payout files reveals a labyrinth of structural quirks, labeling anomalies, and hidden columns that demand granular scrutiny. Following public disclosures by restaurateurs uncovering unauthorized ad charges and unexpected deductions totaling lakhs of rupees, a deeper technical analysis of actual Swiggy payout annexures and Zomato settlement reports exposes critical friction points in platform-merchant accounting.
This investigative report breaks down the structural architecture of these financial documents, identifies systemic data traps that can misrepresent a restaurant’s true liabilities, and examines the broader implications for platform accountability in the digital food-delivery economy.
Detailed Chronology: Unpacking the Anatomy of Platform Settlement Reports
To understand how financial discrepancies go unnoticed, one must examine the internal architecture of the spreadsheets issued by India’s two dominant food-delivery aggregators. By parsing real-world Swiggy annexures and Zomato settlement reports, several structural complexities emerge that challenge manual auditing.
Swiggy: Five Tabs, Hidden Blocks, and Typographical Traps
A standard Swiggy payout annexure is delivered as a comprehensive multi-sheet workbook. While most operators rely exclusively on the primary Summary tab, forensic data parsing shows that financial liabilities are distributed across specific sub-sheets, chief among them being Other charges and deductions and Discount Summary.
The Other charges and deductions tab houses critical adjustments, including advertising expenditures. Yet, it contains a structural quirk: the sheet is divided into two separate blocks—one for the current week and another for adjustments carried over from previous billing cycles. Each block features its own header row. An auditor scanning the sheet visually and halting at the first block will entirely miss the second dataset.
Compounding this visibility issue are literal data entry anomalies within the platform’s automated generation engine. In the files analyzed, the second adjustment block features a misspelled header: while the first block correctly reads Adjustment Type, the second reads Adjusment Type. For developers and automated script-writers, this typo has historically caused data-parsing routines to drop rows, creating invisible discrepancies in automated financial reconciliation tools.
The Discount Summary sheet introduces another analytical challenge via the Restaurant Share (%) column. This single metric dictates whether the cost of a consumer-facing promotion was absorbed entirely by the platform or passed down to the merchant. When the column displays a value of 100, the restaurant funds the entire discount out of its payout; a value of 50 indicates a split cost. Because promotional coupon codes often appear visually identical regardless of funding source, failing to isolate this percentage column can obscure real marketing overhead.
Furthermore, these sheets occasionally feature anomalous rows containing no specific campaign details, displaying instead a remark reading: "Unable to fetch Campaign Details" alongside a financial deduction. In instances reviewed, these unaccounted-for system errors accounted for roughly 3% of a week’s total promotional discounts—money deducted without campaign attribution.
Finally, manual calculations on the Discount Summary sheet face a classic spreadsheet trap: the word TOTAL is placed within the Restaurant Share numerical column rather than the descriptive label column, leaving the label blank. Unwary human auditors or poorly programmed scripts risk double-counting totals if they treat the summary string as a raw data row.
Zomato: Multi-Section Complexity and Reference Errors
Zomato’s settlement reports utilize a fundamentally different layout, centralized primarily within a tab designated as Addition Deductions Details (noting the omission of the forward slash found in PDF renders due to Excel sheet-naming constraints).
This tab is divided into distinct operational sections governed by clear sub-headings:
- Addition Type (cancellation refunds, carry-forward credits)
- Deduction Type
- A) Investments in growth services (primarily advertising fees)
- B) Investments in Hyperpure
- C) Other deductions
- D) Adjustments from previous weeks
Because additions and deductions share a continuous columnar structure, summing the data without accounting for section headers can lead to catastrophic reconciliation errors, treating customer refunds as restaurant liabilities.
Moreover, Zomato’s financial rows incorporate side-by-side columns for Total amount and Adjusted amount. These figures frequently diverge. For instance, onboarding fees may display a full sum under Total amount, a zero under Adjusted amount, and a corresponding balance under Outstanding amount, indicating that no capital left the restaurant’s account during that specific cycle. Auditors reading only the headline total risk overestimating their weekly deductions.
Compounding these complexities, Zomato’s companion Glossary tab exhibits systemic omissions, frequently failing to list active data columns while scrambling the sequence of tax blocks relative to the main data sheets.
Most notably, the grand total row—labeled Total Deductions (A)+(B)+(C)—mathematically aggregates Sections A, B, C, and D. While the financial math is accurate, the label omits Section D ("Adjustments from previous weeks"). Restaurateurs attempting to manually reconcile their accounts against the explicit text of the label will find their figures persistently misaligned. Additionally, the Offers and Discounts Summary tab across tested Zomato reports consistently suffered from broken formula references (#REF!), rendering historical promotional data entirely unreadable.
Supporting Context & Metrics: The Scale of Invisible Overhead
The debate surrounding platform transparency is not merely academic; it strikes at the core unit economics of the Indian restaurant sector, where thin operating margins leave little room for unvoted overhead.
While comprehensive, independent industry-wide loss metrics remain unquantified—partly because public disclosures typically highlight extreme anomalies—documentary evidence points to substantial discrepancies. Cases brought to light by restaurant owners reveal instances where unapproved advertising charges and promotional deductions accumulated quietly across multiple outlets, occasionally amounting to sums upwards of ₹15 to ₹16 lakh before discovery. These funds were often siphoned through micro-deductions across dozens of weekly settlement cycles, remaining entirely invisible until an unusually low net payout triggered a manual investigation.
The opacity of these deductions has historically forced independent operators to choose between two unappealing options: absorbing unknown operational leakage as a cost of doing business, or investing disproportionate administrative hours into cross-referencing thousands of raw data points by hand.
Official Statements and Industry Response
The friction between delivery platforms and merchant partners has not gone unnoticed by the aggregators themselves, signaling tacit acknowledgment of structural transparency challenges within the ecosystem.
Industry shifts began to materialize as regulatory and merchant pressures mounted. Notably, platforms have introduced structural safeguards to curb unauthorized billing and promotional enrollments. Zomato implemented mandatory One-Time Password (OTP) verification steps before specific discount structures can be applied to a restaurant’s menu—a direct acknowledgement of historical friction surrounding unvoted promotional opt-ins. Similarly, marketplace policies have faced increased scrutiny regarding ad-campaign activations, prompting platforms to streamline dispute-resolution mechanisms for merchants contesting automated charges.
Legal and regulatory bodies, while stopping short of sweeping algorithmic audits, have consistently emphasized the necessity of transparent merchant billing practices. Representatives for major aggregators maintain that payout statements are designed to provide comprehensive financial visibility, attributing historical anomalies to software rendering errors, legacy template transitions, or complex multi-city tax compliance requirements. Nevertheless, the persistence of structural errors in exported files underscores the urgent need for standardized, error-free financial reporting protocols across the food-tech sector.
Future Outlook: Moving Toward Algorithmic Transparency
As the Indian online food delivery market matures past its hyper-growth phase, the relationship between aggregators and restaurant partners is shifting from expansion-focused acquisition to long-term operational sustainability.
The technical parsing of payout files highlights an undeniable industry trend: the decentralization of financial auditing. Because traditional accountants and manual spreadsheet reviews are ill-equipped to catch typographical errors, hidden secondary blocks, and formula reference breaks within proprietary platform formats, the market is seeing the rise of specialized, client-side auditing utilities. Tools designed to run entirely locally within browser environments—ensuring data privacy by processing files without server uploads—are beginning to empower merchants to independently verify every rupee of deduction.
Looking ahead, the pressure on Swiggy, Zomato, and emerging Open Network for Digital Commerce (ONDC) participants will likely center on API standardization and radical transparency in financial reporting. Regulators and merchant associations are expected to push for standardized digital ledger formats that eliminate manual parsing traps, incorrect grand-total labels, and unverified promotional charges by default.
For restaurant operators, the lesson is clear: in an era of digital commerce, financial literacy must extend beyond the primary summary tab. Only through rigorous, automated, or systematic line-by-line verification can merchants ensure that their digital ledgers accurately reflect the reality of their kitchen floors.
