Internal Books vs Swiggy Ledger Reconciliation: A Complete Guide for Finance Teams

Internal books vs Swiggy ledger reconciliation is the process of comparing a company’s internal accounting ledger with Swiggy ledger records to confirm whether marketplace-related entries are complete, accurate, and properly mapped.

For businesses selling through Swiggy or similar marketplace channels, internal books may contain voucher numbers, against voucher references, supplier invoice numbers, posting dates, and net movement amounts. Swiggy ledger records may contain reference numbers, document numbers, invoice numbers, PO numbers, posting dates, and transaction amounts.

This reconciliation helps finance teams answer:

• Are all Swiggy ledger records posted correctly in internal books?
• Are all internal ledger entries supported by Swiggy records?
• Do internal net movement amounts match Swiggy ledger amounts?
• Are voucher numbers, invoice numbers, document numbers, and PO numbers mapped correctly?
• Are posting dates aligned across both reports?
• Which records are missing, mismatched, duplicated, or pending review?

For finance teams, this reconciliation supports marketplace accounting accuracy, invoice mapping, receivable tracking, month-end close, and audit readiness.

What Is Internal Books vs Swiggy Ledger Reconciliation?

Internal books vs Swiggy ledger reconciliation compares two sides of ledger data.

Side A: Internal Books Ledger
This represents the company’s internal accounting view. It contains posting date, net movement amount, voucher number, against voucher reference, and supplier invoice number.

Side B: Swiggy Ledger
This represents Swiggy-side marketplace ledger data. It contains posting date, amount, reference number, document number, invoice number, and PO number.

The goal is to confirm whether every internal ledger entry has a corresponding Swiggy ledger record, and whether every Swiggy ledger record has been captured correctly in the internal books.

Matching is mainly based on:

• Internal voucher number
• Against voucher reference
• Supplier invoice number
• Swiggy reference number
• Swiggy document number
• Swiggy invoice number
• Swiggy PO number
• Internal net movement amount
• Swiggy amount
• Posting date

If the reference and amount match across both ledgers, the transaction 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 ledger reconciliation is important because marketplace transactions can include sales, deductions, invoices, adjustments, commissions, taxes, credit notes, debit notes, and payouts. These entries may not always appear in internal books in the same format as the Swiggy ledger.

Without reconciliation, finance teams may face issues such as:

• Swiggy ledger entries missing in internal books
• Internal voucher entries not found in Swiggy records
• Amount mismatches between internal net movement and Swiggy amount
• Invoice numbers not mapped correctly
• PO numbers not linked with internal vouchers
• Document numbers missing or duplicated
• Posting date differences
• Unresolved marketplace receivable differences
• Month-end close delays
• Audit queries due to missing ledger support

A structured reconciliation process helps finance teams confirm whether Swiggy-related ledger activity has been properly posted, mapped, and reviewed.

Reports Involved

Side A: Internal Books Ledger

The internal books ledger represents the company’s accounting record.

Important fields include:

• Posting date
• Net movement amount
• Voucher number
• Against voucher reference
• Supplier invoice number

The net movement amount represents the final accounting impact of the ledger entry. Voucher number and against voucher reference help identify the internal transaction. Supplier invoice number helps connect internal postings with marketplace invoice-level records.

This side shows what the company has recorded in its books.

Side B: Swiggy Ledger

The Swiggy ledger represents the marketplace-side record.

Important fields include:

• Posting date
• Amount
• Reference number
• Document number
• Invoice number
• PO number

The amount represents the value reported by Swiggy. Reference number, document number, invoice number, and PO number help connect the marketplace record with internal vouchers and invoice references.

This side shows what Swiggy has reported.

How Matching Typically Works

Internal books vs Swiggy ledger reconciliation usually works by comparing references, amounts, and dates.

A typical matching process looks like this:

1. The internal books ledger is uploaded.
2. The Swiggy ledger is uploaded.
3. Internal voucher numbers, against voucher references, and supplier invoice numbers are compared with Swiggy reference numbers, document numbers, invoice numbers, and PO numbers.
4. Internal net movement amount is compared with Swiggy amount.
5. Internal posting date is compared with Swiggy posting date.
6. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• The internal books ledger shows a net movement of ₹18,000 with a supplier invoice number.
• The Swiggy ledger shows an amount of ₹18,000 with the same invoice number or related reference number.
• The transaction is treated as matched.

If the invoice or voucher reference matches but the amount differs, it becomes an amount mismatch.

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

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

Why Multiple Reference Matching Is Important

This reconciliation depends on more than one reference field because internal books and Swiggy records may store the same business transaction differently.

Internal books may use:

• Voucher number
• Against voucher
• Supplier invoice number

Swiggy may use:

• Reference number
• Document number
• Invoice number
• PO number

A valid transaction may fail to match if finance teams rely on only one field. For example, an internal supplier invoice number may match the Swiggy invoice number, while another transaction may only match through document number or PO number.

A good reconciliation process should compare all available references before marking a record unmatched.

Common Exceptions in Internal Books vs Swiggy Ledger Reconciliation

1. Swiggy Entry Missing in Internal Books

This happens when the Swiggy ledger contains a record, but no matching internal books entry is found.

Possible reasons include:

• Internal posting is pending
• Internal ledger report is incomplete
• Invoice number was not captured internally
• PO number was not mapped correctly
• Entry belongs to another accounting period
• Manual accounting entry is required

This exception should be reviewed because Swiggy activity may not be fully reflected in the books.

2. Internal Ledger Entry Missing in Swiggy

This happens when internal books contain a voucher entry, but no matching Swiggy ledger record is found.

Possible reasons include:

• Swiggy ledger report is incomplete
• Internal entry belongs to another channel
• Voucher reference does not match Swiggy reference
• Supplier invoice number was captured differently
• Entry was posted manually in books
• Transaction belongs to another period

This exception should be reviewed because internal accounting entries should have marketplace-side support where applicable.

3. Amount Mismatch

Amount mismatches occur when the reference appears related but the internal net movement amount and Swiggy amount do not match.

Possible causes include:

• Commission or deduction difference
• Tax or fee treatment difference
• Credit note or debit note impact
• Adjustment posted on one side only
• Partial posting in internal books
• Rounding difference
• Wrong amount field selected

Amount mismatches directly affect marketplace receivables, accounting accuracy, and month-end review.

4. Invoice or PO Mapping Issue

Invoice and PO mapping issues happen when Swiggy references are not captured consistently in internal books.

Examples include:

• Supplier invoice number missing internally
• Swiggy PO number not linked to voucher number
• Document number stored in a different format
• Reference number contains extra text
• Partial invoice number captured
• Prefix or suffix differences

A reliable reconciliation process should standardize these references before classifying entries as unmatched.

5. Posting Date Difference

Both reports may use posting date, but the dates can still differ.

Date differences may happen due to:

• Marketplace posting delay
• Internal accounting delay
• Month-end cutoff difference
• Adjustment posted later
• Report generation timing
• Manual journal posted after marketplace reporting

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

6. Duplicate Records

Duplicates may appear in either internal books or Swiggy records.

Examples include:

• Same voucher number posted twice
• Same invoice number repeated
• Same document number appearing more than once
• Duplicate ledger export
• Correction entry not reversed properly

Duplicates can overstate balances and create false mismatches if not identified.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile internal books with Swiggy ledgers manually in Excel.

The usual process includes:

1. Exporting the internal books ledger.
2. Downloading the Swiggy ledger.
3. Cleaning voucher numbers, invoice numbers, document numbers, and PO numbers.
4. Standardizing dates and amounts.
5. Matching records using lookup formulas.
6. Comparing net movement amount with Swiggy amount.
7. Reviewing missing and mismatched entries.
8. Preparing an exception report.

This becomes difficult when transaction volumes increase or when references are spread across multiple fields.

Common Excel challenges include:

• Voucher numbers not matching Swiggy references exactly
• Invoice numbers stored in different fields
• PO numbers not mapped consistently
• Broken lookup formulas
• Wrong amount column selected
• Duplicate records missed
• Date format issues
• Manual copy-paste errors
• No clear audit trail

A structured reconciliation workflow reduces these risks.

What a Good Swiggy Ledger Reconciliation Process Should Include

A reliable process should include:

• Correct internal books ledger
• Correct Swiggy ledger
• Matching using voucher number, against voucher, supplier invoice number, reference number, document number, invoice number, and PO number
• Amount comparison between net movement and Swiggy amount
• Posting date visibility
• Internal-only exception reporting
• Swiggy-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which records matched, which records are missing, and which amount differences need review.

How Cointab Helps

Cointab can help finance teams automate internal books vs Swiggy ledger reconciliation by comparing internal accounting records with Swiggy marketplace ledger records in a structured workflow.

Finance teams can map voucher numbers, invoice numbers, PO numbers, amount fields, and posting dates once and reuse the same setup for future periods.

Cointab helps teams:

• Upload internal books and Swiggy ledger reports
• Match internal voucher, against voucher, and supplier invoice references with Swiggy reference, document, invoice, and PO numbers
• Compare internal net movement amount with Swiggy amount
• Identify fully matched entries
• Highlight amount mismatches
• Show internal-only and Swiggy-only exceptions
• Review skipped or invalid records
• Download audit-ready Excel reports
• Reuse the workflow for recurring reconciliation

This reduces manual Excel work and helps finance teams focus on real marketplace ledger differences.

Business Value

Internal books vs Swiggy ledger reconciliation helps finance teams:

• Validate Swiggy ledger completeness
• Improve marketplace accounting accuracy
• Confirm invoice and PO mapping
• Identify missing internal postings
• Detect unsupported internal entries
• Review amount differences
• Speed up month-end close
• Strengthen audit documentation
• Reduce manual reconciliation work

It also helps finance teams resolve transaction-level marketplace differences faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile internal books and Swiggy ledgers regularly
• Use all available voucher, invoice, document, and PO references
• Compare net movement and Swiggy amount consistently
• Review amount mismatches separately
• Check duplicate voucher numbers, invoice numbers, and document numbers
• Track internal-only and Swiggy-only exceptions
• Maintain period-wise reconciliation history
• Document manual corrections clearly
• Investigate recurring mismatch patterns

Conclusion

Internal books vs Swiggy ledger reconciliation helps finance teams confirm whether internal accounting records match Swiggy marketplace ledger records.

Because this reconciliation depends on voucher numbers, against voucher references, supplier invoice numbers, reference numbers, document numbers, invoice numbers, PO numbers, posting dates, net movement amounts, and Swiggy amounts, manual reconciliation can become slow and error-prone as transaction volumes grow.

With Cointab, finance teams can automate internal books vs Swiggy ledger 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 internal books vs Swiggy ledger reconciliation without relying on manual Excel work. No credit card required.

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