ERP vs PG and COD Settlement Reconciliation: A Complete Guide for Finance Teams

ERP vs PG and COD settlement reconciliation is the process of comparing sales and credit note records from an ERP with settlement and remittance reports received from payment gateways, COD logistics partners, and BNPL providers.

For eCommerce and D2C businesses, collections may come through multiple channels. Prepaid orders may be collected through a payment gateway, COD orders may be collected by logistics partners, and BNPL orders may be settled by affordability partners. Returns and credit notes may reduce the amount that should finally be received.

This reconciliation helps finance teams answer:

• Are all ERP sales settled by the correct payment or COD partner?
• Are all credit notes and returns adjusted properly?
• Are all Cashfree, COD, and BNPL settlement entries linked to valid ERP orders?
• Do ERP grand totals match settlement, remittance, or COD amounts?
• Are AWB numbers, payment IDs, and order references captured correctly?
• Which orders are missing, mismatched, duplicated, delayed, or pending review?

For finance teams, ERP vs PG and COD settlement reconciliation supports revenue accuracy, receivable control, COD tracking, return adjustment, and audit readiness.

What Is ERP vs PG and COD Settlement Reconciliation?

ERP vs PG and COD settlement reconciliation compares two sides of transaction data.

Side A: ERP Sales Reports
This includes the ERP sales report and credit note report. These reports contain posting date, grand total, payment references, order IDs, remarks, and AWB numbers from sales and return-related records.

Side B: PG and COD Settlement Reports
This includes settlement or remittance reports from payment gateways, COD logistics partners, and BNPL providers such as Cashfree, BlueDart, DTDC, Delhivery, Xpressbee, and Snapmint.

The goal is to confirm whether every ERP sale or credit note is correctly reflected in the relevant external settlement report.

Matching is mainly based on:

• Payment reference
• Shopify payment ID
• Extracted order ID
• AWB number
• Merchant reference ID
• COD partner reference
• Grand total
• Settlement, remittance, COD, or order amount
• Posting date, transaction time, delivery date, or settlement date

Reports Involved

Side A: ERP Sales and Credit Note Reports

The ERP side contains two key reports.

Sales Report

The sales report represents revenue-side transactions recorded in the ERP.

Important fields include:

• Posting date
• Grand total
• Remarks or numeric reference
• Payment reference
• Payment ID
• Extracted order ID
• AWB number

This report shows the order value expected to be settled through prepaid, COD, or BNPL channels.

Credit Note Report

The credit note report represents returns, reversals, or adjustments recorded in the ERP.

Important fields include:

• Posting date
• Grand total
• Payment reference
• Payment ID
• Extracted order ID
• Return AWB number

Credit notes are important because they reduce the final receivable or settlement expectation.

Side B: PG, COD, and BNPL Settlement Reports

The external side includes multiple settlement and remittance sources.

Cashfree Report

May include final amount, merchant reference ID, and transaction time.

BlueDart COD Remittance

May include remitted amount, AWB, and remittance date.

DTDC COD Report

May include COD amount, CN number, and delivery date.

Delhivery COD Report

May include COD amount, waybill number, and transaction date.

Xpressbee COD Report

May include order amount, AWB, and delivery date.

Snapmint Report

May include signed order value, Shopify order number, Shopify payment ID, and merchant settlement date.

Each external source uses different references, so the reconciliation must compare multiple identifiers instead of relying on one order number.

How Matching Typically Works

ERP vs PG and COD settlement reconciliation usually depends on reference, amount, and date.

A typical matching flow looks like this:

1. ERP sales and credit note reports are uploaded.
2. Cashfree, COD partner, and Snapmint reports are uploaded.
3. ERP references such as payment ID, payment reference, extracted order ID, remarks, and AWB number are compared with external references.
4. ERP grand total is compared with final amount, remitted amount, COD amount, order amount, or signed order value.
5. ERP posting date is compared with transaction time, delivery date, remittance date, or settlement date.
6. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• ERP sales report shows a grand total of ₹2,500 with a payment reference.
• Cashfree report shows final amount of ₹2,500 with the same merchant reference ID.
• The transaction is treated as matched.

For COD:

• ERP sales report shows an AWB and order value of ₹1,800.
• COD partner report shows the same AWB with COD amount of ₹1,800.
• The transaction is treated as matched.

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

If an ERP order exists but no settlement or COD record is found, it becomes an ERP-only exception.

If a settlement record exists but no ERP order is found, it becomes an external-only exception.

Why This Reconciliation Is Complex

ERP vs PG and COD settlement reconciliation is complex because multiple business flows are involved.

A single reconciliation may include:

• Prepaid payments
• COD collections
• BNPL settlements
• Sales invoices
• Credit notes
• Returns
• AWB-based logistics matching
• Payment ID-based gateway matching
• Settlement date differences
• Delivery date differences

Different partners also use different identifiers. A prepaid payment may match using payment ID or merchant reference ID. A COD order may match using AWB, CN number, or waybill number. A BNPL transaction may match using Shopify order number or payment ID.

This is why flexible matching logic is important.

Common Exceptions in ERP vs PG and COD Settlement Reconciliation

1. ERP Sale Missing in Settlement Report

This happens when an ERP sale is not found in any payment gateway, COD, or BNPL settlement report.

Possible reasons include:

• Payment settlement is delayed
• COD remittance has not been received
• Wrong partner report was uploaded
• Payment reference is missing
• AWB number is incorrect
• Order was cancelled or returned
• Transaction belongs to a later period

This exception should be reviewed because the business may be expecting money that has not been confirmed externally.

2. Settlement Entry Missing in ERP

This happens when Cashfree, COD partner, or Snapmint reports contain a transaction, but no matching ERP sale is found.

Possible reasons include:

• ERP sales report is incomplete
• Order was recorded under another reference
• Payment callback failed
• COD partner report includes an old order
• Duplicate external record exists
• Manual adjustment was included in the settlement file

This can create reporting and accounting issues if not investigated.

3. Amount Mismatch

Amount mismatches occur when the reference matches but the ERP grand total and external amount differ.

Possible causes include:

• Partial payment
• COD short remittance
• Return or credit note impact
• Refund or reversal
• Gateway deduction
• BNPL settlement adjustment
• Rounding difference
• Incorrect ERP amount

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

4. COD Remittance Mismatch

COD reconciliation depends on AWB, CN number, waybill number, delivery date, remittance date, and COD amount.

Common COD exceptions include:

• Delivered order not remitted
• Short COD remittance
• AWB not found in ERP
• Wrong CN or waybill number
• COD amount mismatch
• Remittance posted in a later period
• Duplicate AWB in partner report

These exceptions are important because COD cash collection is often delayed and partner-dependent.

5. Credit Note or Return Mismatch

Credit notes reduce the final amount expected from the order. If credit notes are not reconciled correctly, finance teams may overstate expected settlement.

Common issues include:

• Credit note recorded in ERP but not adjusted externally
• Return reflected externally but not recorded in ERP
• Credit note amount differs from settlement adjustment
• Return AWB does not match partner records
• Credit note appears in a different period
• Duplicate return or credit note entry

Returns and credit notes should be reviewed separately from normal sales matches.

6. Reference Matching Issues

This reconciliation uses multiple references, including payment references, payment IDs, order IDs, remarks, AWB numbers, CN numbers, and waybill numbers.

Matching can fail due to:

• Missing payment reference
• AWB number stored differently
• Order ID hidden inside remarks
• CN number used instead of AWB
• Shopify payment ID not available in all reports
• Manual formatting differences

A reliable reconciliation process should use all available references to improve match accuracy.

7. Date Difference

ERP reports use posting date, while external reports may use transaction time, delivery date, remittance date, or settlement date.

Date differences may happen due to:

• Settlement cycle timing
• COD delivery delay
• Remittance delay
• Month-end cutoffs
• Return processing delay
• Payment gateway reporting timing

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

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile ERP sales, credit notes, PG settlements, and COD remittances manually in Excel.

The typical process includes:

1. Exporting ERP sales and credit note reports.
2. Downloading Cashfree, COD partner, and BNPL settlement reports.
3. Cleaning payment references, order IDs, and AWB numbers.
4. Matching prepaid orders using payment IDs.
5. Matching COD orders using AWB, CN, or waybill numbers.
6. Comparing ERP grand total with settlement or remittance amounts.
7. Adjusting for credit notes and returns.
8. Preparing an exception report.

This becomes difficult when transaction volumes increase.

Common Excel challenges include:

• Too many reference fields
• Broken lookup formulas
• COD partner formats changing
• Credit notes not adjusted correctly
• Duplicate records missed
• Wrong amount column selected
• Date format issues
• No clear audit trail

A structured reconciliation workflow reduces these risks.

What a Good ERP vs PG and COD Settlement Reconciliation Process Should Include

A reliable process should include:

• Correct ERP sales and credit note reports
• Complete PG, COD, and BNPL settlement reports
• Multiple reference matching
• AWB-based COD matching
• Payment ID-based PG matching
• Credit note and return handling
• Amount mismatch reporting
• ERP-only and external-only exception reporting
• Duplicate detection
• Date difference visibility
• Audit-ready output

The output should clearly show which transactions matched and which need follow-up.

How Cointab Helps

Cointab can help finance teams automate ERP vs PG and COD settlement reconciliation by comparing ERP sales and credit note reports with multiple settlement and remittance files.

Finance teams can map payment references, order IDs, AWB numbers, amounts, and dates once and reuse the setup for future reconciliation periods.

Cointab helps teams:

• Upload ERP sales and credit note reports
• Upload Cashfree, BlueDart, DTDC, Delhivery, Xpressbee, and Snapmint reports
• Match prepaid transactions using payment references
• Match COD transactions using AWB, CN number, or waybill number
• Compare ERP grand total with final amount, COD amount, remitted amount, order amount, or signed order value
• Identify fully matched records
• Highlight amount mismatches
• Show ERP-only and external-only exceptions
• Download audit-ready Excel reports

This reduces manual Excel work and gives finance teams a clearer view of settlement exceptions.

Business Value

ERP vs PG and COD settlement reconciliation helps finance teams:

• Validate prepaid and COD collections
• Track partner-wise settlement accuracy
• Identify missing or delayed COD remittances
• Reconcile credit notes and returns
• Detect amount mismatches
• Improve receivable control
• Speed up month-end close
• Strengthen audit documentation
• Reduce manual reconciliation effort

It also helps finance, operations, and logistics teams resolve order-level payment differences faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile ERP, PG, COD, and BNPL reports regularly
• Use payment ID for prepaid orders
• Use AWB, CN number, or waybill number for COD orders
• Review credit notes separately
• Compare amount fields consistently
• Track delayed COD remittances
• Check duplicate order and AWB references
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

ERP vs PG and COD settlement reconciliation helps finance teams confirm whether ERP sales and credit notes match payment gateway, COD, and BNPL settlement reports.

Because this reconciliation depends on payment references, Shopify payment IDs, extracted order IDs, AWB numbers, CN numbers, waybill numbers, grand totals, settlement amounts, COD amounts, remittance dates, and credit notes, manual reconciliation can become slow and error-prone.

With Cointab, finance teams can automate ERP vs PG and COD settlement reconciliation, reduce manual Excel work, identify exceptions faster, and generate audit-ready reports for review.

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

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