Why your food aggregator payouts never match your sales

Every restaurant owner has felt it: you tally up a day's orders, and the amount that hits your bank account a week later is just... off. Not wildly off — a few hundred rupees here, a couple thousand there. Easy to shrug off. Except it happens every single settlement cycle, and it never seems to correct itself.

The gap isn't usually one big mistake. It's five or six small ones stacked on top of each other: a commission slab applied incorrectly on a subset of orders, a cancelled order that still shows as billed in your ERP, a refund deducted twice, a delivery fee miscalculated on a subscription plan, a promotional discount charged to you instead of the food aggregator.

None of these show up clearly on a settlement report. Food aggregators publish payout summaries, not itemized reconciliations — you get a single number covering thousands of orders, with no easy way to check it order-by-order without spending hours in a spreadsheet.

That's the real problem: reconciliation isn't hard because the math is complex. It's hard because doing it manually, order by order, doesn't scale — especially across multiple food aggregators, each with a different report format, different fee structures, and different payout schedules.

The fix isn't better spreadsheets. It's comparing every order in your ERP against every line in every settlement, automatically, so mismatches surface the moment they happen — not three months later when the numbers are impossible to untangle.