Swiggy MIS Reconciliation for Restaurants

Swiggy MIS reconciliation helps restaurant finance teams compare internal MIS or POS records with Swiggy reports, so they can review sales, charges, settlements, and payout differences in one place. Instead of checking spreadsheets line by line, teams can map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in a structured report.

This is especially useful for restaurants that need to understand how Swiggy commissions, cancellations, refunds, GST, and settlement timing affect the final receivable amount. With a reusable workflow, the same setup can be used for future months without rebuilding formulas or reworking the file logic each time.

Why restaurants reconcile Swiggy with MIS data

Swiggy is often one of several channels a restaurant manages, and the finance team needs to confirm that the amount expected in the internal system aligns with the amount reported by the platform. Differences can come from commissions, merchant cancellations, customer refunds, fee deductions, tax treatment, or settlement delays.

A structured reconciliation process helps teams:

• verify sales recorded in the internal MIS or POS system
• compare platform-reported net receivables with internal calculations
• track deductions such as commission, cancellation charges, collection charges, and GST
• identify missing or delayed settlements
• separate genuine exceptions from records that should not be reviewed manually
• keep month-end close and audit preparation more organized

Side A and Side B in this workflow

Cointab uses a Side A and Side B model for reconciliation.

The left side represents the restaurant's records, and the right side represents the external platform records. This makes it easier for finance teams to understand what is being compared and why a difference appears.

Typical reports used for Swiggy MIS reconciliation

A restaurant team may use one or more reports in the reconciliation workflow, depending on how its finance process is set up.

Common inputs include:

• Swiggy invoice or charge details
• Swiggy payment advice or order-level payout information
• Swiggy settlement data
• Internal MIS or POS reports
• Monthly store-level working files

Supporting data can also be added when needed. For example, a store master, mapping file, or fee reference file can help enrich the main reports before reconciliation.

How the reconciliation workflow works

Cointab is designed as a reusable reconciliation engine rather than a one-time spreadsheet check. A typical workflow looks like this:

1. The user starts a new reconciliation in a team workspace.
2. The user selects a popular reconciliation or creates a custom setup.
3. The required files are uploaded for Side A and Side B.
4. The user maps fields such as date, amount, and identifiers like restaurant ID, order ID, or settlement reference.
5. Optional supporting files can be uploaded for lookup, merge, or calculation.
6. Derived columns can be created when a cleaned or calculated field is needed.
7. The reconciliation is run manually or on a schedule.
8. The system applies structured matching logic.
9. Remaining open items are reviewed with AI-assisted analysis where needed.
10. The report is completed and available for review and download.

What the report shows

Once the run is complete, finance teams can review the reconciliation at a summary level and at a transaction level.

The report typically shows:

• total summary
• fully matched records
• partially matched records
• unmatched records
• skipped records
• filters for deeper review
• detailed matched transaction views
• downloadable Excel output for internal review or follow-up

Fully matched

These are the records where the restaurant's internal amount and the Swiggy-reported amount align according to the reconciliation rules.

Partially matched

These records are related, but the amounts do not fully agree. For restaurant teams, partial matches are important because they often point to commission differences, refunds, deductions, or settlement adjustments that need review.

Unmatched

These are records found on one side but not the other. For example, a sale may appear in the MIS but not in the Swiggy report, or a payout may appear in Swiggy data but not yet in the internal file.

Skipped

Skipped records are visible too, so the team can see which rows were excluded because of missing fields, invalid values, duplicates, or file issues.

Common difference areas in Swiggy reconciliation

Restaurant finance teams usually review a few recurring difference types:

• commission and platform fee deductions
• merchant cancellation charges
• buyer cancellation and refund amounts
• GST or other tax-related charges
• settlement timing differences across months
• missing or late files from the platform
• records that need grouping before comparison

Cointab supports structured matching logic for one-to-one, one-to-many, many-to-one, and many-to-many scenarios, so teams can compare transactions more realistically than simple Excel lookups.

How AI helps in this workflow

AI is used as a support layer, not a replacement for finance review.

In this use case, AI can help with:

• creating derived columns using plain-language prompts
• analyzing difficult open items after structured matching is complete
• suggesting possible reasons for unmatched records
• identifying whether a file may be missing
• helping teams review exceptions faster

If evidence is not strong enough, the record should remain unmatched rather than being forced into a weak match.

Why finance teams use a reusable setup

A Swiggy reconciliation setup is usually repeated every month. Rebuilding the same file logic each time creates avoidable work and increases the risk of inconsistency.

A reusable setup helps teams:

• keep the same field mapping and matching logic
• reduce spreadsheet dependency
• standardize reporting across stores or periods
• review exceptions faster at month end
• preserve report history for later reference
• refresh the reconciliation if a missed file arrives later

Automation for recurring restaurant workflows

Once the reconciliation is configured, the data flow can be automated through email, SFTP, or API-based input and output.

This is useful when the restaurant receives platform reports regularly and wants a more consistent process for:

• importing the Swiggy report
• running the reconciliation on a schedule
• reviewing the output in the dashboard
• exporting the result to downstream systems

Automation makes the workflow more suitable for daily, weekly, or monthly finance operations rather than a manual spreadsheet exercise.

Why this matters for restaurant finance teams

Swiggy reconciliation is not only about checking numbers. It is about giving finance teams a clear view of what was sold, what was charged, what was settled, and what still needs attention.

A structured reconciliation process helps teams improve control over:

• payout tracking
• platform deductions
• settlement visibility
• exception handling
• month-end reporting
• audit readiness

For restaurants with multiple stores or high transaction volumes, that visibility is often more valuable than the final summary alone.

FAQ

What data can be used for Swiggy MIS reconciliation?

Restaurants can use internal MIS or POS data on Side A and Swiggy reports on Side B. Supporting files such as store mappings or fee reference files can also be added when needed.

Can the same reconciliation be reused every month?

Yes. Once the file structure and matching logic are configured, the same reconciliation can be reused for future periods by uploading the new files and running the workflow again.

How are differences handled?

The report separates fully matched, partially matched, unmatched, and skipped records so finance teams can focus on open exceptions instead of reviewing every row manually.

Can missing files be added later?

Yes. If a file arrives late, it can be uploaded under the same reconciliation and the report can be refreshed so the comparison reflects the latest data.

Can this workflow be automated?

Yes. Cointab supports automated data input and scheduled reconciliation runs through email, SFTP, and API-based workflows where the setup requires recurring processing.