ERP Records vs Swiggy Marketplace Records Reconciliation: A Complete Guide for Finance Teams

ERP records vs Swiggy marketplace records reconciliation is the process of comparing a company’s internal ERP data with transaction, order, ledger, or settlement records received from Swiggy.

For brands selling through Swiggy or Swiggy-linked commerce channels, the internal ERP may show sales invoices, order values, product-level revenue, taxes, credit notes, returns, refunds, deductions, and receivable balances. Swiggy records may show marketplace orders, accepted values, cancellations, returns, discounts, fees, commissions, taxes, adjustments, and settlement amounts.

This reconciliation helps finance teams answer:

• Are all ERP sales available in Swiggy records?
• Are all Swiggy-side transactions recorded correctly in the ERP?
• Do order values, invoice values, return values, deduction values, and settlement values match?
• Are refunds, credit notes, claims, and adjustments mapped correctly?
• Which records are missing, mismatched, duplicated, or pending review?
• Is the final receivable or settlement balance supported by transaction-level records?

For finance teams, this reconciliation supports marketplace sales accuracy, receivable control, deduction review, settlement validation, month-end close, and audit readiness.

What Is ERP vs Swiggy Reconciliation?

ERP vs Swiggy reconciliation compares the internal business view with the marketplace-side view.

Side A: ERP Records
This represents the company’s internal accounting or sales-side view. It may include orders, invoices, ledger entries, credit notes, refunds, returns, discounts, taxes, and receivable balances.

Side B: Swiggy Records
This represents the Swiggy-side view. It may include order records, accepted sale values, returns, cancellations, refunds, platform deductions, commissions, tax adjustments, settlement entries, and balance details.

The goal is to confirm whether both sides reflect the same commercial activity and whether any differences are explained by refunds, returns, deductions, settlement timing, or valid adjustments.

Matching is usually based on:

• ERP order number
• Invoice number
• Swiggy order ID
• Marketplace transaction ID
• Settlement reference
• Credit note number
• Refund reference
• Product or SKU code
• Order amount
• Tax amount
• Return amount
• Deduction amount
• Net settlement amount
• Order date
• Invoice date
• Settlement date

If the reference and amount match across both systems, the record can usually be treated as matched. If the reference matches but the amount differs, it becomes an amount mismatch. If a record appears only on one side, it becomes an exception.

Why This Reconciliation Matters

Marketplace and quick-commerce sales do not always settle at the same value as the gross sale recorded in the ERP. The final amount may change because of discounts, returns, cancellations, commissions, platform fees, tax adjustments, promotional deductions, claims, penalties, or previous-period corrections.

Without reconciliation, finance teams may face issues such as:

• ERP sales missing from Swiggy records
• Swiggy transactions missing in the ERP
• Incorrect marketplace receivable balances
• Refunds or credit notes not adjusted correctly
• Unsupported Swiggy deductions
• Settlement values not matching expected receivables
• Duplicate order or settlement records
• Timing differences across periods
• Month-end close delays
• Audit queries due to missing marketplace support

A structured reconciliation process helps finance teams validate transaction-level differences before they affect revenue, receivables, and reporting.

Reports Involved

Side A: ERP Report

The ERP report represents the internal business-side view of Swiggy-related transactions.

Common fields may include:

• Order number
• Invoice number
• Customer or channel reference
• Product or SKU code
• Order date
• Invoice date
• Gross sales amount
• Discount amount
• Tax amount
• Net sales amount
• Credit note amount
• Refund amount
• Return amount
• Outstanding amount
• Narration or reference

This report shows what the business has recorded internally as sales, returns, receivables, and adjustments.

Side B: Swiggy Report

The Swiggy report represents the marketplace-side transaction or settlement view.

Common fields may include:

• Swiggy order ID
• Marketplace transaction ID
• Product or SKU reference
• Order date
• Delivery or completion date
• Settlement date
• Gross order value
• Discount amount
• Return value
• Refund value
• Commission or fee deduction
• Tax adjustment
• Promotion or claim adjustment
• Net settlement amount
• Settlement reference

This report shows what Swiggy has recorded, deducted, adjusted, settled, or kept pending.

How Matching Typically Works

ERP records vs Swiggy records reconciliation usually works by comparing order references, invoice references, amount fields, and settlement details.

A typical process looks like this:

1. The ERP report is uploaded.
2. The Swiggy report is uploaded.
3. ERP order numbers, invoice numbers, Swiggy order IDs, and settlement references are compared.
4. ERP sales values are compared with Swiggy order values.
5. Returns, refunds, credit notes, deductions, and adjustments are reviewed separately.
6. Settlement entries are matched against expected receivables.
7. Outstanding differences are categorized for review.
8. Records are marked as matched, partially matched, unmatched, or skipped.

For example:

• The ERP shows a Swiggy order sale of ₹1,200.
• Swiggy shows the same order with a gross value of ₹1,200.
• The order-level value is treated as matched.

Another example:

• The ERP shows a receivable of ₹1,200.
• Swiggy settles ₹1,050 after commission, tax, or promotional adjustment.
• The ₹150 difference should be explained through deduction or adjustment lines.
• If the difference is supported, the transaction can be reconciled. If not, it becomes an exception.

If an ERP record exists but no Swiggy record is found, it becomes an ERP-only exception.

If a Swiggy record exists but no ERP record is found, it becomes a Swiggy-only exception.

Why ERP and Swiggy Records May Differ

ERP and Swiggy records may differ because both systems record transactions at different stages of the order lifecycle.

Common reasons include:

• ERP invoice number and Swiggy order ID are different
• Orders are recorded internally before Swiggy settlement
• Swiggy settlement happens after order completion
• Returns are posted after the original sale
• Refunds are adjusted against later settlements
• Platform deductions are grouped in Swiggy reports
• Discounts are treated differently across systems
• Tax values are calculated or reported differently
• Previous-period adjustments appear in current settlement files
• One settlement may include multiple orders

A good reconciliation process should first match order-level records and then validate returns, refunds, deductions, payments, and balances.

Common Exceptions in ERP vs Swiggy Reconciliation

1. ERP Sale Missing in Swiggy

This happens when an ERP record shows a Swiggy-related sale, but no matching Swiggy record is found.

Possible reasons include:

• Swiggy report period is incomplete
• Order reference is missing or formatted differently
• Order was cancelled before confirmation
• ERP includes non-Swiggy transactions
• Swiggy order was recorded in another period
• Wrong Swiggy file was uploaded

This exception should be reviewed because every valid Swiggy sale recorded internally should have external support.

2. Swiggy Record Missing in ERP

This happens when Swiggy shows a transaction, but no matching ERP record is found.

Possible reasons include:

• ERP report export is incomplete
• Order sync failed
• Swiggy order belongs to another period
• Reference was stored differently internally
• Manual accounting entry is pending
• Swiggy report includes adjustment-only entries

This exception should be reviewed so every Swiggy-side transaction has proper internal accounting support.

3. Amount Mismatch

Amount mismatches occur when the order reference appears related, but the ERP amount and Swiggy amount differ.

Possible causes include:

• Discount treatment difference
• Tax calculation difference
• Platform commission or fee
• Promotional adjustment
• Return or refund impact
• Rounding difference
• Partial settlement
• Wrong amount field selected

Amount mismatches directly affect revenue, receivables, settlement accuracy, and audit reporting.

4. Return or Refund Difference

Returns and refunds reduce the expected receivable amount.

Common issues include:

• Return shown in Swiggy but missing in ERP
• Refund shown in Swiggy but not posted internally
• Credit note posted internally but not reflected in Swiggy
• Partial refund creating amount difference
• Refund posted in a later period
• Return linked to the wrong order

Refund and return differences should be reviewed separately from normal sales mismatches.

5. Deduction or Commission Difference

Swiggy may apply commissions, fees, claims, taxes, penalties, or promotional deductions before settlement.

Possible issues include:

• Commission charged at a different rate
• Platform fee not recorded internally
• Tax deduction not mapped correctly
• Promotional adjustment treated incorrectly
• Prior-period deduction included in current settlement
• Multiple deductions grouped together

These differences should be supported by Swiggy deduction details before they are accepted in the books.

6. Settlement Difference

Settlement mismatch occurs when the amount received or expected does not match the Swiggy settlement value.

Possible reasons include:

• Multiple orders settled together
• Partial settlement
• Refund adjusted before payout
• Deduction adjusted against settlement
• Payment received in a later period
• Previous-period balance carried forward

Settlement differences should be reviewed with order-level and deduction-level support.

7. Date or Period Difference

ERP and Swiggy may show different dates for the same transaction.

Possible reasons include:

• Order date differs from invoice date
• Settlement date differs from sale date
• Refund posted later
• Deduction posted in another period
• Month-end cutoff difference

A date difference is not always an error, but it should be visible during reconciliation.

8. Duplicate Records

Duplicates may appear in either ERP or Swiggy reports.

Examples include:

• Same ERP order repeated
• Same Swiggy order repeated
• Same invoice repeated
• Same refund reference repeated
• Duplicate settlement line
• Duplicate file upload

Duplicates can overstate sales, refunds, deductions, or settlement values if not identified.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile ERP and Swiggy records manually in Excel.

The usual process includes:

1. Exporting ERP sales or ledger data.
2. Downloading Swiggy transaction or settlement data.
3. Cleaning order numbers, invoice numbers, and settlement references.
4. Matching records using lookup formulas.
5. Comparing sales, returns, refunds, deductions, and settlements.
6. Reviewing unmatched and mismatched entries.
7. Preparing an exception report.

This becomes difficult as transaction volumes increase.

Common Excel challenges include:

• Different reference formats
• Multiple transaction types in Swiggy reports
• Returns and refunds posted separately
• One settlement covering multiple orders
• Deductions grouped together
• Duplicate records missed
• Broken lookup formulas
• Wrong amount column selected
• Manual copy-paste errors
• No clear audit trail

A structured reconciliation workflow reduces these risks.

What a Good ERP vs Swiggy Reconciliation Process Should Include

A reliable process should include:

• Complete ERP report
• Complete Swiggy report
• Order-level and invoice-level matching
• Settlement reference mapping
• Gross sales comparison
• Discount comparison
• Tax comparison
• Return and refund visibility
• Deduction and commission review
• ERP-only exception reporting
• Swiggy-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which transactions matched, which deductions need review, and which balances require follow-up.

How Cointab Helps

Cointab can help finance teams automate ERP records vs Swiggy records reconciliation by comparing internal ERP data with Swiggy data in a structured workflow.

Finance teams can map order references, invoice references, settlement references, amount fields, deduction fields, refund fields, and date fields once and reuse the setup for future periods.

Cointab helps teams:

• Upload ERP and Swiggy reports
• Match ERP sales with Swiggy records
• Compare sales, returns, refunds, deductions, settlements, and balances
• Identify fully matched transactions
• Highlight amount mismatches
• Show ERP-only and Swiggy-only exceptions
• Review skipped or invalid records
• Detect duplicate orders and settlement lines
• Download audit-ready Excel reports
• Reuse the workflow for recurring reconciliation

This reduces manual Excel work and gives finance teams better visibility into marketplace sales and settlement differences.

Business Value

ERP records vs Swiggy records reconciliation helps finance teams:

• Validate Swiggy marketplace sales
• Track receivables accurately
• Identify missing orders or entries
• Review refunds and returns
• Detect unsupported deductions
• Improve settlement accuracy
• Reduce marketplace disputes
• Speed up month-end close
• Strengthen audit documentation
• Reduce manual reconciliation work

It also helps finance, marketplace operations, and accounting teams resolve transaction-level issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile ERP and Swiggy reports regularly
• Use order ID, invoice number, settlement reference, and payment reference wherever available
• Review sales, returns, refunds, deductions, and settlements separately
• Track timing differences separately from true mismatches
• Check duplicate order, invoice, refund, and settlement references
• Maintain period-wise reconciliation history
• Document manual corrections clearly
• Review Swiggy deduction and adjustment logic periodically

Conclusion

ERP records vs Swiggy marketplace records reconciliation helps finance teams confirm whether sales, returns, refunds, deductions, settlements, and outstanding receivables are properly aligned.

Because this reconciliation depends on ERP records, Swiggy records, order references, invoice references, settlement references, refund entries, deductions, and timing differences, manual Excel reconciliation can become slow and error-prone as transaction volumes grow.

With Cointab, finance teams can automate ERP vs Swiggy reconciliation, reduce manual Excel work, identify missing or mismatched records faster, and generate audit-ready reports for review.

Start your 14-day free trial with Cointab and automate ERP records vs Swiggy marketplace reconciliation without relying on manual Excel work. No credit card required.

Visit: https://www.cointab.net/