Swiggy MIS Reconciliation for Restaurants

Restaurant finance teams often need to reconcile Swiggy reports with internal MIS or POS records to confirm what was sold, what was settled, and what fees or deductions were applied. Cointab provides a structured reconciliation workflow for this process, so teams can match records, review exceptions, and download audit-ready reports without rebuilding the setup every month.

Why restaurants reconcile Swiggy with MIS

A restaurant may record an order in its internal MIS, but the final amount received from Swiggy can differ because of commissions, cancellations, refunds, delivery-related deductions, taxes, or settlement timing. Without a structured workflow, finance teams end up comparing reports manually in Excel and chasing open items one by one.

Swiggy MIS reconciliation helps teams answer practical questions such as:

• Which orders were fully settled?
• Which orders were partially matched because the amounts differ?
• Which refunds or cancellations explain the difference?
• Which charges were deducted by Swiggy?
• Which amounts are still pending settlement?
• Which stores or periods need follow-up?

Common data used in the reconciliation

Cointab uses a Side A and Side B model.

Side A: Your restaurant records

Side A contains the records your business expects to be correct. For a restaurant, this may include:

• Internal MIS or POS order reports
• Revenue working files
• Store-wise sales summaries
• Receivables or ledger exports
• Other internal finance reports

Side B: Swiggy records

Side B contains the external records received from Swiggy. These may include:

• Swiggy invoice annexure
• Payment advice report
• Settlement or payout details
• Refund and cancellation information
• Charge and deduction breakdowns

File formats and field mapping

Users can upload CSV, XLS, or XLSX files and map the required fields once, such as:

• Order date or transaction date
• Amount
• Order ID or reference number
• Restaurant or store identifier
• Settlement reference or payout reference

If one report uses a different structure, the workflow can still be configured as long as the required fields are available.

How Cointab runs Swiggy MIS reconciliation

The reconciliation workflow is designed to be repeatable for monthly close and ongoing review.

1. Upload the internal MIS file on Side A and the Swiggy report on Side B.
2. Map the date, amount, and identifier columns.
3. Add supporting data if needed, such as store mappings or reference files.
4. Create derived columns when the file needs cleanup or normalization.
5. Run reconciliation manually or on a schedule.
6. Review the matched, partially matched, unmatched, and skipped records.
7. Download the Excel report for finance review or audit support.

Cointab also supports reusable reconciliation setups, so the same Swiggy reconciliation can be used again for the next month or another period with the same logic.

What the reconciliation report shows

After the run is complete, finance teams can review a dashboard-style report with clear transaction status and summary views.

Fully matched records

These are records where the order reference and amount match according to the configured reconciliation logic.

Partially matched records

These are records where the identifiers match, but the amount differs. In a restaurant workflow, this can happen when there is a fee, deduction, refund, cancellation, or settlement difference that needs review.

Unmatched records

These are records that appear on one side but not the other. For example:

• An order exists in MIS but not in the Swiggy report
• A settlement appears in Swiggy but not in the internal books
• A store-level entry is missing in one of the files

Skipped records

These are rows that were not included in reconciliation because of missing data, invalid amounts, duplicate rows, or other file issues. Skipped items remain visible so the finance team understands what was ignored and why.

Typical Swiggy differences restaurant teams review

Swiggy MIS reconciliation is not only about matching order totals. It also helps teams understand the reason behind the final payable or receivable amount.

Common review items include:

• Commission charges
• Merchant cancellation charges
• Refunds to customers
• Settlement timing differences
• Amounts pending settlement
• Missing or delayed reports
• Differences between expected and received amounts

Where needed, Cointab can also use AI-assisted analysis to help review difficult open items and suggest possible reasons for the mismatch. If the evidence is weak, the record stays unmatched so the review remains audit-friendly.

Store-level and period-wise reconciliation

Restaurant finance teams often want the reconciliation summarized by store and by month. Cointab supports flexible period handling, including monthly, quarterly, yearly, lifetime, and custom periods.

This is useful when teams need to:

• Track store-wise settlement performance
• Compare month-end revenue against Swiggy payouts
• Review open items across multiple stores
• Carry forward unresolved differences into the next period
• Maintain a running reconciliation dashboard for reference

Supporting data and derived columns

Swiggy reconciliation often becomes easier when the internal data needs light preparation before matching.

Supporting data can be used to enrich the primary reports, for example:

• Store mapping files
• Product or menu reference files
• Revenue working files
• Internal identifier lookup files

Users can also create derived columns with AI-generated Excel-style formulas. This helps when the team needs to normalize order references, clean text, calculate net amounts, or create match-ready fields without manually writing formulas.

Examples of derived columns can include:

• Clean Order ID
• Net Amount
• Normalized Reference
• Amount after deductions
• Reconciled Settlement Value

Manual review and missed file handling

Not every open item should be forced into an automatic match. Cointab includes manual match support for cases where the finance team has context that the system cannot infer confidently.

If a report is received late or a file was missed, the team can upload the missing file under the same reconciliation and refresh the report. This is helpful for restaurant operations where settlement files or supporting reports may arrive after the main MIS file.

Automation for recurring restaurant finance work

Once the Swiggy reconciliation is configured, it can be reused for recurring monthly or daily workflows. Cointab also supports automated data input and scheduled reconciliation runs through email, SFTP, or API-based workflows.

That means restaurant finance teams can set up the process once and then use the same workflow repeatedly for:

• Daily settlement checks
• Weekly exception review
• Monthly close support
• Store-wise reporting
• Audit preparation

Cointab can also deliver reconciliation output back to downstream systems through email, SFTP, or API when needed.

Why this workflow helps finance teams

A structured Swiggy MIS reconciliation process helps restaurant teams:

• Reduce manual spreadsheet work
• Review exceptions faster
• Keep a clear audit trail
• Standardize monthly reporting
• Separate fully matched, partially matched, unmatched, and skipped records
• Reuse the same workflow for future periods
• Keep finance, accounts, and operations aligned in one workspace

For restaurants managing multiple stores or frequent settlement activity, that visibility is often more useful than a one-time spreadsheet comparison.

What finance teams can expect to see in the dashboard

The reconciliation dashboard keeps past runs available for reference and review. Typical fields include:

• Reconciliation name
• Period
• Run status
• Run date and time
• Files used
• Run by
• View report

This makes it easier to track what was reconciled, when it was run, and how exceptions were handled over time.