Swiggy and Zomato reconciliation that catches the short-paid
The payout that lands is never the sum of the orders you served. Commission, charges and adjustments eat the gap, and most restaurants never check whether the gap is right.
CountStand ingests your aggregator orders and reconciles them against the payout, to the paise, flagging every discrepancy, a missing order, an over-charged commission, an adjustment that does not add up. It links to Swiggy and Zomato through an aggregator connection (via UrbanPiper); once that feed is connected, orders flow in and each settlement is checked against what you were actually owed. Three layers of idempotency stop the same order being counted twice. Connect your aggregator account to switch it on.
What honest reconciliation checks
Every order that went out, matched to every rupee that came back.
Orders matched to the payout
Each aggregator order is reconciled against the settlement line for it, so a payout is a set of verified matches rather than a lump sum you accept on faith.
Discrepancies flagged, not buried
Missing orders, over-charged commission and odd adjustments are logged as discrepancies to review, turning "the payout feels low" into a specific list.
Paise-exact, no rounding drift
Reconciliation runs in integer paise, so a hundred small roundings cannot hide a real shortfall inside "close enough".
Double-count protection
Three layers of idempotency on ingest mean a re-sent order or a retried webhook updates the same record instead of inflating your counts.
Why does aggregator revenue need reconciling at all?
Because the money that arrives has been through several hands before it reaches you. An order’s menu price is reduced by commission, then by payment and packaging charges, then by promotional adjustments and the occasional dispute, and the settlement statement compresses all of that into totals. Without matching each order to its settlement line, a short-paid commission or a dropped order simply vanishes into a number too big to eyeball.
Reconciliation restores the check. It reassembles what you were owed from the orders you actually served and compares it, order by order, against what was paid, so the gap is explained rather than accepted.
How does CountStand connect to Swiggy and Zomato?
The order and settlement feed comes through an aggregator connection, integrated via UrbanPiper. Once your account is linked, orders ingest automatically and each payout is reconciled as it arrives; the reconciliation engine, the discrepancy log and the idempotency safeguards are built and fixture-verified against real settlement shapes.
To be plain about the seam: the checking is ready; the live feed lights up when you connect your aggregator account. Until then, nothing is silently pretending to be linked, you switch it on when your partner access is in place.
Asked by owners like you
What does aggregator reconciliation do?
It matches each Swiggy or Zomato order against the payout for it, to the paise, and flags discrepancies, missing orders, over-charged commission, odd adjustments, so a low payout becomes a specific, checkable list.
How does it connect to Swiggy and Zomato?
Through an aggregator feed integrated via UrbanPiper. Once your account is linked, orders ingest and payouts reconcile automatically; the engine and discrepancy log are built and fixture-verified.
Can it double-count orders?
No, three layers of idempotency on ingest ensure a re-sent order or retried webhook updates the same record rather than inflating counts.
Is it available immediately?
The reconciliation engine is ready; the live feed activates when you connect your aggregator account. It is part of CountStand from ₹999/mo per outlet, 30-day free trial.
Stop accepting the payout on faith
Reconcile aggregator orders to the paise, connect your account and start free for 30 days.
30-day free trial · No card · From ₹999/mo per outlet