ERP Ledger vs Swiggy Ledger Reconciliation: A Complete Guide for Finance Teams

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

For brands selling through Swiggy or Swiggy-linked commerce channels, the ERP ledger may show invoices, sales entries, receivables, credit notes, refund entries, deductions, payment receipts, and outstanding balances. The Swiggy ledger may show marketplace orders, accepted values, returns, refunds, platform deductions, commission entries, tax adjustments, settlement entries, and balance details.

This reconciliation helps finance teams answer:

• Are all ERP ledger entries available in the Swiggy ledger?
• Are all Swiggy ledger entries recorded correctly in the ERP?
• Do sales, return, refund, deduction, settlement, and payment values match?
• Are credit notes, claims, promotional adjustments, and platform deductions mapped correctly?
• Which entries 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 Ledger vs Swiggy Ledger Reconciliation?

ERP ledger vs Swiggy ledger reconciliation compares two accounting views of the same marketplace relationship.

Side A: ERP Ledger
This represents the company’s internal accounting view. It may include sales invoices, ledger postings, debit entries, credit entries, credit notes, refund entries, payment receipts, deductions, and outstanding receivables.

Side B: Swiggy Ledger
This represents the Swiggy-side marketplace or partner ledger view. It may include order records, accepted sales values, returns, refunds, platform fees, commissions, promotional adjustments, tax adjustments, settlement entries, and balance details.

The goal is to confirm whether both ledgers reflect the same sales, returns, refunds, deductions, payments, and balances.

Matching is usually based on:

• ERP invoice number
• ERP order number
• Swiggy order ID
• Marketplace transaction ID
• Settlement reference
• Credit note number
• Refund reference
• Payment reference
• Debit amount
• Credit amount
• Gross sales amount
• Return amount
• Refund amount
• Deduction amount
• Net settlement amount
• Transaction date
• Posting date
• Settlement date

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

Why This Reconciliation Matters

Marketplace sales rarely settle at the same value as the gross sales recorded in the ERP. The final amount may change because of returns, refunds, platform commissions, fees, taxes, promotional discounts, claims, penalties, or previous-period corrections.

Without reconciliation, finance teams may face issues such as:

• ERP sales entries missing from Swiggy records
• Swiggy ledger entries 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 ledger entries
• Opening or closing balance differences
• Month-end close delays
• Audit queries due to missing marketplace support

A structured reconciliation process helps finance teams identify transaction-level differences before they become balance-level disputes.

Reports Involved

Side A: ERP Ledger Report

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

Common fields may include:

• Invoice number
• Order number
• Ledger account
• Transaction date
• Posting date
• Debit amount
• Credit amount
• Gross sales amount
• Discount amount
• Tax amount
• Credit note amount
• Refund amount
• Payment amount
• Outstanding balance
• Narration or reference

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

Side B: Swiggy Ledger Report

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

Common fields may include:

• Swiggy order ID
• Marketplace transaction ID
• Invoice or order reference
• Settlement reference
• Order date
• Return date
• Refund date
• Settlement date
• Gross order value
• Discount amount
• Return value
• Refund value
• Commission or fee amount
• Tax adjustment
• Deduction amount
• Net settlement amount
• Closing balance

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

How Matching Typically Works

ERP ledger vs Swiggy ledger reconciliation usually works by comparing references, debit-credit values, settlement values, and dates.

A typical process looks like this:

1. The ERP ledger report is uploaded.
2. The Swiggy ledger report is uploaded.
3. ERP invoice numbers, order numbers, Swiggy order IDs, settlement references, and payment references are compared.
4. ERP debit and credit entries are matched with Swiggy ledger entries.
5. ERP sales or receivable values are compared with Swiggy accepted values.
6. Returns, refunds, credit notes, deductions, and adjustments are reviewed separately.
7. Settlement or payment entries are matched against expected receivables.
8. Outstanding balances are compared after all adjustments.
9. Entries are categorized as matched, partially matched, unmatched, or skipped.

For example:

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

Another example:

• The ERP ledger shows a receivable of ₹1,500.
• The Swiggy ledger shows a settlement of ₹1,280 after commission, promotional adjustment, or tax deduction.
• The difference should be explained through deduction and adjustment lines.
• If the difference is not supported, it becomes an exception.

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

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

Why ERP and Swiggy Ledger Records May Differ

ERP and Swiggy ledger records may not match directly because both systems may record transactions at different stages of the order and settlement lifecycle.

Common reasons include:

• ERP invoice number and Swiggy order ID are different
• Swiggy settlement happens after order completion
• One settlement includes multiple orders
• Returns are posted after the original sale
• Refunds are adjusted against later settlements
• Credit notes are posted separately in the ERP
• Platform deductions are grouped in Swiggy ledger reports
• Discounts are treated differently across systems
• Tax values are reported differently
• Prior-period adjustments appear in the current ledger

A good reconciliation process should match transaction-level entries first and then validate deductions, refunds, payments, and balance movement.

Common Exceptions in ERP Ledger vs Swiggy Ledger Reconciliation

1. ERP Ledger Entry Missing in Swiggy Ledger

This happens when the ERP ledger contains a Swiggy-related sale, invoice, or receivable entry, but no matching entry is found in the Swiggy ledger.

Possible reasons include:

• Swiggy ledger period is incomplete
• Order reference is missing in the ERP
• Order was cancelled before confirmation
• ERP ledger includes non-Swiggy transactions
• Swiggy record belongs to another period
• Wrong Swiggy ledger report was uploaded

This exception should be reviewed because ERP marketplace receivables should have external support.

2. Swiggy Ledger Entry Missing in ERP

This happens when the Swiggy ledger contains a transaction, but no matching ERP ledger entry is found.

Possible reasons include:

• ERP ledger export is incomplete
• Order sync failed
• Entry belongs to another period
• Reference was stored differently in the ERP
• Manual accounting entry is pending
• Swiggy ledger includes adjustment-only entries

This exception should be reviewed so every Swiggy-side entry has proper ERP support.

3. Amount Mismatch

Amount mismatches occur when the reference appears related, but the ERP ledger amount and Swiggy ledger 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 debit or credit amount selected

Amount mismatches 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 the ERP
• Refund shown in Swiggy but not posted internally
• Credit note posted in the ERP but not reflected in Swiggy
• Partial refund creating amount difference
• Refund posted in a later period
• Return linked to the wrong order
• Refund reversal not captured correctly

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 in the ERP
• Tax deduction not mapped correctly
• Promotional adjustment treated incorrectly
• Prior-period deduction included in the current settlement
• Multiple deductions grouped together

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

6. Settlement or Payment Difference

Settlement mismatch occurs when the amount paid or expected does not match the Swiggy ledger 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. Opening or Closing Balance Difference

Ledger reconciliation often includes balance validation.

Possible reasons for balance differences include:

• Opening balance mismatch
• Prior-period entries missing on one side
• Previous-period deductions posted later
• Payments posted in one ledger but not the other
• Manual adjustments not captured consistently
• Month-end cutoff differences

Balance differences should be traced back to transaction-level entries.

8. Duplicate Ledger Entries

Duplicates may appear in either the ERP ledger or Swiggy ledger.

Examples include:

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

Duplicates can overstate sales, refunds, deductions, payments, or receivables if not identified.

Why Manual Excel Reconciliation Is Difficult

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

The usual process includes:

1. Exporting the ERP ledger.
2. Downloading the Swiggy ledger.
3. Cleaning order numbers, invoice numbers, settlement references, and payment references.
4. Matching debit and credit entries using lookup formulas.
5. Comparing sales, returns, refunds, deductions, settlements, and balances.
6. Reviewing credit notes, settlement differences, and unmatched entries.
7. Preparing an exception report.

This becomes difficult as transaction volumes increase.

Common Excel challenges include:

• Different reference formats
• Refunds and deductions posted separately
• One settlement covering multiple orders
• Credit notes appearing in different periods
• Opening balance differences
• 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 Ledger vs Swiggy Ledger Reconciliation Process Should Include

A reliable process should include:

• Complete ERP ledger report
• Complete Swiggy ledger report
• Order-level and invoice-level matching
• Debit and credit amount comparison
• Settlement reference mapping
• Refund and credit note visibility
• Deduction and commission review
• Payment and settlement matching
• Opening and closing balance comparison
• ERP-only exception reporting
• Swiggy-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

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

How Cointab Helps

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

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

Cointab helps teams:

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

This reduces manual Excel work and gives finance teams better visibility into Swiggy ledger differences.

Business Value

ERP ledger vs Swiggy ledger reconciliation helps finance teams:

• Validate Swiggy marketplace sales
• Track Swiggy receivables accurately
• Identify missing ledger entries
• Review refunds, returns, and credit notes
• 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 ledger and Swiggy ledger regularly
• Use order ID, invoice number, settlement reference, and payment reference wherever available
• Review sales, returns, refunds, deductions, payments, and balances separately
• Track opening and closing balance differences clearly
• Track timing differences separately from true mismatches
• Check duplicate order, invoice, refund, credit note, and settlement references
• Maintain period-wise reconciliation history
• Document manual corrections clearly
• Review Swiggy deduction and adjustment logic periodically

Conclusion

ERP ledger vs Swiggy ledger reconciliation helps finance teams confirm whether sales, returns, refunds, credit notes, deductions, payments, settlements, and outstanding balances are properly aligned.

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

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

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

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