They match every order on their POS against the aggregator’s settlement sheet, once a week, using a fixed five-point checklist: order count, order status, order value, commission percentage, and net payout received. When a mismatch shows up, they document it with the Order ID and raise a dispute within the same payout cycle. The entire process takes under 15 minutes if the POS already tracks online orders.
That is the short answer. The rest of this piece breaks down the exact workflow, what to check at each step, and where most restaurants bleed money without realising it.
Key Takeaways
- Match your POS order data against the aggregator’s weekly payout, line by line
- Verify five things every cycle: order count, delivery status, order value, commission rate, and net deposit
- Status mismatches (delivered vs cancelled) cost the most because the full order value goes unpaid
- A POS with built-in reconciliation cuts this from a 3-hour spreadsheet task to 10 minutes
Why Can’t Reconciliation Wait Until Month-End?
India’s online food delivery market is projected to touch US$61.76 billion in revenue by 2026, according to Statista’s India outlook. Swiggy alone logged 93 million biryani orders across January to November 2025, per their annual How India Swiggy’d report. At that scale, settlement errors are a numbers game.
A restaurant doing 80 Swiggy and Zomato orders a day generates 560 individual settlement calculations every week. Each one involves the base order value, a commission deduction (16-30% depending on your contract and city), GST on that commission, a platform fee, and a payment gateway charge. If even 2% of those carry an error of Rs 15-40, the weekly leak comes to Rs 170-450. By month-end, that is Rs 680-1,800 from one outlet alone.
The problem with waiting until month-end is that aggregator dispute windows close fast. Both platforms enforce specific timelines within which you can raise a query about a transfer. If you flag a missing order from the first week of May on the 28th, the chances of resolution drop sharply because the disbursement cycle has long closed.
The Five-Point Reconciliation Checklist
Every weekly review should cover these five checkpoints, in this order. Skipping any one of them leaves a gap where money can leak through.
| Checkpoint | What you compare | Common error range |
|---|---|---|
| Order count | POS total vs settlement total | 1-5 missing orders/week |
| Delivery status | POS status vs platform status per order | Full order value unpaid (Rs 300-700) |
| Order value | POS amount vs settlement amount per order | Rs 5-40 per order |
| Commission rate | Contracted % vs actual deduction % | 2-6% overcharge on affected orders |
| Net deposit | Settlement figure vs bank credit | Varies by gateway and TDS |
1. Order Count Match
Pull the total number of online orders from your POS for the week. Then pull the total from the aggregator’s settlement report. The two numbers should match exactly.
If your POS shows 412 entries but Swiggy’s settlement lists 407, five went unpaid. Those five could be worth Rs 1,500-3,500 depending on your average ticket size. This is the fastest check and it immediately tells you whether deeper investigation is needed.
2. Delivery Status Verification
For every order, your POS records a status: delivered, cancelled, or rejected. The aggregator’s transfer report records its own status for the same order. When these two disagree, you have a status discrepancy.
Consider this example: a QSR in Jayanagar marks Order #8834 as delivered at 9:17 PM on a Saturday. The rider picked up the food, the customer received it. But Zomato’s backend flagged it as cancelled due to a timeout glitch during a high-traffic window. That Rs 420 never enters the weekly credit. Without a status-level check, you would never spot the gap.
Status discrepancies cost more per incident than any other error type because the entire order value goes unpaid, not just a fraction.
3. Order Value Comparison
Even when both systems agree that an order was delivered, the rupee amount can differ. Your POS might record an order at Rs 540, but the aggregator’s ledger shows Rs 524. The Rs 16 gap typically traces back to one of three places: a rounding difference in GST calculation, a discount code the platform applied that your POS did not register, or a promotional deduction that was auto-applied without your approval.
Individually, these gaps run Rs 5-40 per order. For example, a cloud kitchen in Aundh running two brands on both Swiggy and Zomato might accumulate 20-30 such variances in a single week. Over a month, that is Rs 1,600-4,800 that never showed up as a line item anywhere.
4. Commission Rate Verification
Your contract specifies a commission percentage. For example, 22% across the board. But fee structures have grown more layered over 2025-2026, with per-transaction platform fees, gateway charges, and promotional deductions stacking on top of the base commission.
Pull three or four random line items from the disbursement report each week and manually calculate the effective deduction percentage. If your contract says 22% but the actual cut on a Rs 500 order comes to Rs 145 (29%), something is off. The gap could be a promotional programme auto-applied to your listing, a fee structure revision you were not notified about, or a backend error applying the wrong commission tier.
India’s food services sector is valued at Rs 5.69 lakh crore as of FY24, employing 8.5 million people, per the NRAI India Food Services Report 2024. At that scale, even a 1-2% commission overcharge across thousands of partner restaurants adds up to crores in aggregate overbilling.
5. Net Deposit Verification
After all deductions, cross-check the final amount deposited into your bank account against the net figure on the aggregator’s report. Bank processing fees, TDS deductions, or gateway charges can sometimes create a gap between what the platform says it transferred and what actually landed in your account.
This step catches discrepancies that sit outside the platform’s system entirely. For example, if your bank applies a different processing fee than expected, or if a TDS deduction was applied incorrectly before the transfer reached you.
How Do You Build a Weekly Reconciliation Workflow?
The checklist above works only if someone actually runs it on a fixed day every week. Here is a rhythm that restaurants with 50+ daily online orders have found practical.
Monday morning, before the lunch rush. Download or pull the previous week’s disbursement reports from both Swiggy and Zomato. If your POS generates a consolidated online order report, pull that too.
Run the order count match first. It takes two minutes and tells you immediately whether the week was clean or messy. If counts match across both platforms, you can move through the remaining checks faster.
Flag every discrepancy in a single sheet. Columns: Order ID, platform, date, error type (count/status/amount/commission), your POS value, their reported value, difference in rupees. This becomes your dispute document.
Raise disputes the same day. Do not let flagged entries sit until next Monday. Both Swiggy and Zomato have partner portals where you can file queries. Attach the Order IDs, the amounts, and screenshots from your POS. Restaurants that track their accounting data in a structured way find this step far quicker because the numbers are already organised.
Track dispute resolution in the same sheet. Add columns for “dispute raised on”, “status”, and “resolved amount”. Over three to four weeks, this sheet becomes a pattern tracker. You will start seeing whether errors cluster on specific days, specific platforms, or specific order value ranges.
What Does a Reconciliation Error Cost at Different Scales?
The maths changes depending on how many daily transactions your outlet handles. Here is a rough breakdown assuming a 2% error rate on settlement calculations and an average error value of Rs 25.
A single-outlet cafe in Indiranagar doing 40 orders a day loses roughly Rs 600 per month at this rate. Manageable, but still an unnecessary leak. A multi-brand cloud kitchen in Whitefield processing 300 orders daily across Swiggy and Zomato faces a Rs 4,500 monthly gap from a 2% error rate alone. Over a year, that is Rs 54,000 from one location.
These are conservative estimates. Restaurants that have never reconciled often find the actual error rate closer to 3-5% in the first few weeks, especially if promotional programmes or platform fee changes went unnoticed.
At What Point Do Spreadsheets Stop Working?
Most restaurants start with a downloaded CSV and a spreadsheet. That works at 30-40 transactions a day. Beyond that, the time cost climbs fast.
At 80+ daily orders, a manual CSV comparison takes 2-3 hours per week. You are scanning 560 rows across two platforms, matching Order IDs, and hand-calculating commission percentages. The probability of human error in that process is high, and ironically, you might miss the very gaps you are trying to catch.
A POS system that already ingests aggregator data can run the comparison on its own. It pulls your order records and the platform’s disbursement figures, runs the five-point check across every transaction, and flags discrepancies with Order IDs and rupee differences attached. What took 3 hours in a spreadsheet takes 10 minutes on screen.
Restaurants using analytics and reporting tools inside their POS also spot patterns faster. For example, if Tuesday night deliveries consistently show higher error rates than other days, a POS report surfaces that trend within a couple of weeks. A spreadsheet might take months to reveal the same pattern.
At Petpooja, we have seen this shift play out across our 1,00,000+ restaurant clients. Outlets that move from manual reconciliation to POS-based reconciliation typically recover Rs 2,000-8,000 per month in the first quarter, simply because they are catching errors that were previously invisible. Petpooja POSS includes a built-in reconciliation report that runs this comparison for Swiggy and Zomato payouts at no extra cost.
Conclusion
Reconciliation is not an accounting exercise you can push to your CA at month-end. It is a weekly operational habit, like checking your inventory or reviewing yesterday’s sales. The five-point checklist (order count, status, value, commission, net deposit) covers every layer where money can leak between your kitchen and your bank account. Run it every Monday, document mismatches with Order IDs, and raise disputes the same day. The restaurants that do this consistently are the ones that stop losing Rs 2,000-5,000 a month to errors nobody was looking for.
Frequently Asked Questions
There is no minimum, but the payoff becomes tangible once you cross 30-40 online transactions daily. Below that, errors are infrequent and small. Above 80 per day, cross-checking is not optional because the sheer volume of settlement calculations makes weekly errors almost certain. Our delivery commission calculator can help you estimate what your current deduction rates should look like.
Separately. Each platform has its own commission structure, platform fee, and settlement cycle. Mixing them into one comparison sheet creates confusion when you need to raise disputes, because Swiggy’s partner portal and Zomato’s partner portal handle queries independently. Keep one tab per platform in your tracking sheet.
Status mismatches. An order your POS recorded as delivered but the platform settled as cancelled, or vice versa. These are the costliest because the full order value goes unpaid. Amount variances (Rs 5-40 per order) are more frequent but smaller. Restaurants that also track their P&L weekly tend to spot these gaps sooner.
Yes, but speed and documentation matter. A dispute with specific Order IDs, exact rupee differences, and POS screenshots gets resolved far faster than a vague complaint about low payouts. Restaurants that raise disputes within the same payout cycle see the highest resolution rates. The longer you wait, the harder it gets. Understanding your commission structure also helps you argue your case with specifics rather than approximations.
If your current POS exports online transaction data as a CSV, you can build a basic spreadsheet template that compares it against the aggregator’s settlement CSV. It is manual and time-consuming, but workable at low volumes. For anything above 80 deliveries a day, a POS with built-in aggregator matching (like Petpooja POSS) saves significant time because the comparison runs on its own every disbursement cycle.
