Swiggy Orders Reconciliation for Restaurants
Restaurants that sell through Swiggy often need to reconcile multiple records for the same order cycle: internal POS or sales data, Swiggy order and settlement reports, and the bank statement where payouts are received. The challenge is not just matching order values. Finance teams also need to review commissions, taxes, coupon discounts, packing charges, cancellation charges, and settlement differences.
Cointab helps restaurant finance teams structure this process as a reusable reconciliation workflow. You can upload the relevant files, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in a clear report.
What Swiggy orders reconciliation covers
Swiggy reconciliation is usually a combination of transaction reconciliation and settlement reconciliation. It helps answer questions such as:
- Which Swiggy orders were fulfilled and settled correctly?
- Which orders were paid short or paid in excess?
- Were commissions, taxes, and other deductions applied as expected?
- Do the Swiggy settlement reports match the bank credits?
- Are there missing payouts, delayed settlements, or unexplained differences?
For finance teams, this creates a controlled way to validate restaurant revenue and partner deductions without relying on manual Excel checks.
Typical data sources used in the workflow
A Swiggy reconciliation workflow often compares Side A, your internal records, with Side B, external partner records.
Side A: your records
This side usually includes the restaurant's source-of-truth data, such as:
- POS orders
- Internal sales reports
- ERP exports
- Store-level order summaries
- Accounting or ledger data
Side B: external records
This side usually includes records received from Swiggy and the bank, such as:
- Swiggy order or annexure reports
- Swiggy settlement reports
- Payout details
- Bank statements
- Supporting files for fees, coupons, or adjustments
Cointab allows you to map the required fields across these files, including date, amount, and order or settlement identifiers.
Common items reviewed during reconciliation
Swiggy order reconciliation usually goes beyond order-level matching. Finance teams often need to check the full settlement picture.
Order-level checks
- Order ID matching between internal records and Swiggy reports
- Paid, unpaid, underpaid, or overpaid orders
- Canceled, refunded, or returned orders
- Orders missing from one side of the reconciliation
Settlement and deduction checks
- Commission charged by the platform
- Tax deductions or tax-related adjustments
- Coupon or discount treatment
- Packing charges collected from the customer
- Cancellation fees
- Final settlement amount credited to the bank
Exception checks
- Orders present in POS but missing in Swiggy
- Swiggy entries missing in POS
- Settlement amounts that do not match the expected net value
- Bank credits that do not align with the settlement report
How Cointab handles Swiggy reconciliation
Cointab gives finance teams a structured workflow instead of a manual spreadsheet process.
1. Upload and map files
Users upload CSV, XLS, or XLSX files for the relevant reports. The system then maps the required fields, such as:
- Transaction date
- Amount
- Order ID or other reference number
- Settlement reference
- Bank reference where needed
2. Add supporting data if needed
Supporting data can help enrich the main reports before reconciliation. For a restaurant workflow, this may include store master data or any internal mapping file used to standardize identifiers or calculate expected values.
3. Create derived columns where useful
If a report needs cleanup or normalization, users can create derived columns. For example, they may standardize order references, calculate net values, or prepare fields for matching.
4. Run reconciliation
Cointab applies structured matching logic to compare the files. It can identify fully matched, partially matched, unmatched, and skipped records, so finance teams can focus on the exceptions that need review.
5. Review the report
Once the run is complete, users can review the reconciliation dashboard and inspect transaction-level results. Filters make it easier to focus on specific stores, periods, or exception types.
6. Download the report
The final reconciliation can be exported as an Excel report for internal review, month-end close, follow-up, or audit support.
Why this matters for restaurant finance teams
Swiggy reconciliation is repetitive, but it is also financially sensitive. Small mismatches in commission, coupon treatment, packing charges, or settlement deductions can accumulate across many orders and stores.
Cointab helps teams:
- reduce manual spreadsheet work
- keep reconciliation logic consistent across periods
- isolate exceptions faster
- review settlement differences with better traceability
- maintain audit-ready records for internal and external review
This is especially useful for restaurants and multi-outlet businesses that reconcile Swiggy on a daily, weekly, or monthly basis.
Reusable workflow for recurring periods
Once the reconciliation setup is defined, the same workflow can be reused for future periods. Finance teams do not need to rebuild the process every month.
Typical recurring use:
- Select the Swiggy reconciliation setup
- Choose the period
- Upload the latest files
- Run reconciliation
- Review the report and exceptions
This helps standardize reporting across locations, periods, and team members.
Manual review for unresolved items
Not every difference can be matched automatically. Some items may require human review because of incomplete references, missing data, or partner-side variations.
Cointab supports manual matching for open transactions that the system cannot resolve confidently. This helps finance teams close exceptions while keeping the decision auditable.
Useful outputs for reporting and close
The reconciliation output can support several finance workflows, including:
- daily settlement tracking
- outlet-level revenue review
- commission and deduction verification
- bank-to-settlement matching
- period-end close
- audit preparation
- partner discrepancy follow-up
The dashboard keeps reconciliation history available for future reference, so teams can revisit prior runs without rebuilding the workflow.
Swiggy reconciliation as part of broader finance operations
For many restaurant businesses, Swiggy is only one part of a larger reconciliation process. The same reconciliation approach can also be used for bank statements, marketplace settlements, vendor statements, and other partner data.
That makes Cointab useful not only for a single report comparison, but as a repeatable reconciliation layer for finance operations where accuracy, transparency, and reviewability matter.
Frequently asked questions
What files are typically used for Swiggy reconciliation?
Most teams use internal POS or sales data on one side and Swiggy order, settlement, and bank statement data on the other side. Supporting files may also be added if they help with mapping or calculations.
Can Cointab help with commission and deduction checks?
Yes. Swiggy reconciliation can include review of commission, taxes, coupon discounts, packing charges, cancellation charges, and settlement differences, depending on the files and logic configured for the workflow.
What happens if an order is found in one report but not the other?
Those transactions appear as unmatched records in the reconciliation report. Finance teams can review them separately and investigate whether the missing record is due to timing, reporting differences, or a data issue.
Can the same reconciliation setup be reused every month?
Yes. Once configured, the workflow can be reused for future periods by uploading the new files and running reconciliation again.
Does the platform support manual review of open items?
Yes. Users can manually match items that require business context or additional review, while keeping the reconciliation outcome visible in the report.
