ERP Sales vs Payment Gateway and COD Reconciliation: A Complete Guide for Finance Teams

ERP sales vs payment gateway and COD reconciliation is the process of comparing internal sales records from an ERP with external payment gateway settlement reports and COD remittance reports.

For eCommerce and D2C businesses, the ERP records the order, sale value, customer payment mode, invoice, refund, cancellation, and receivable amount. However, the actual collection may happen through multiple external partners such as Gokwik, PayU, Worldline, Worldline refund reports, and BlueDart COD remittance reports.

This reconciliation helps finance teams answer:

• Are all ERP prepaid sales available in payment gateway settlement reports?
• Are all COD orders collected and remitted by the courier partner?
• Are all external settlements linked to valid ERP sales?
• Do order values, settlement values, refund values, and COD remittance values match?
• Are failed payments, refunds, cancellations, returns, and RTOs handled correctly?
• Which orders are missing, short-settled, duplicated, delayed, or pending review?

For finance teams, this reconciliation supports sales accuracy, cash collection tracking, refund validation, COD control, month-end close, and audit readiness.

What Is ERP Sales vs Payment Gateway and COD Reconciliation?

ERP sales vs payment gateway and COD reconciliation compares internal order or sales data with external collection records.

Side A: ERP Sales Report
This represents the internal sales-side view. It may include order number, invoice number, customer details, payment mode, order value, tax amount, refund value, order status, and sale date.

Side B: Payment Gateway and COD Reports
This includes external collection records from Gokwik, PayU, Worldline, Worldline refund reports, and BlueDart COD remittance reports. These reports show what was paid, refunded, settled, deducted, remitted, or kept pending by each partner.

The goal is to confirm whether every ERP sale has the correct collection, settlement, refund, or COD remittance support.

Matching is usually based on:

• ERP order number
• Invoice number
• Payment gateway transaction ID
• Payment reference
• Settlement reference
• Refund reference
• AWB number
• COD reference
• Order amount
• Refund amount
• Settlement amount
• COD remittance amount
• Order date
• Transaction date
• Settlement date
• Remittance date

If the order reference and amount match across both sides, 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

ERP sales and actual collections do not always match directly.

A prepaid order may be marked as successful in the ERP, but the payment may settle later through Gokwik, PayU, or Worldline. A refund may appear separately in the Worldline refund report. A COD order may be delivered by BlueDart, but the COD amount may be remitted after the courier’s remittance cycle.

Differences may arise because of:

• Payment gateway settlement cycles
• Gateway fees or deductions
• Refunds and reversals
• Failed or pending payments
• Duplicate payment attempts
• COD collection delays
• COD short remittance
• Returns and RTOs
• Order cancellations
• Settlement timing differences
• Multiple partners handling different payment modes

Without reconciliation, finance teams may face issues such as:

• ERP sales without matching payment settlement
• Settlement records without matching ERP sales
• COD orders delivered but not remitted
• Refunds not posted correctly
• Worldline refund records not mapped to ERP orders
• Short settlements or short COD remittances
• Duplicate payment records
• Delayed settlements across periods
• Incorrect receivable balances
• Audit queries due to missing order-level support

A structured reconciliation process helps finance teams confirm whether sales, settlements, refunds, COD collections, and partner remittances are properly aligned.

Reports Involved

Side A: ERP Sales Report

The ERP sales report represents the internal business view of customer orders and invoices.

Common fields may include:

• Order number
• Invoice number
• Customer name or customer ID
• Order date
• Invoice date
• Payment mode
• Gross order value
• Discount amount
• Tax amount
• Net order value
• Refund amount
• Order status
• Fulfillment status
• AWB or tracking number

This report shows what the business has recorded as sales and receivables.

Side B: Gokwik Settlement Report

The Gokwik settlement report represents payment or checkout-side settlement activity.

Common fields may include:

• Order reference
• Payment reference
• Transaction ID
• Transaction date
• Payment amount
• Refund amount
• Settlement amount
• Settlement date
• Transaction status

This report helps finance teams validate prepaid or checkout-linked collections.

Side B: PayU Settlement Report

The PayU settlement report represents payment gateway collections and settlement activity.

Common fields may include:

• PayU transaction ID
• Merchant order ID
• Payment date
• Gross transaction amount
• Refund amount
• Fee or deduction amount
• Net settlement amount
• Settlement date
• Payment status

This report helps validate PayU collections against ERP sales.

Side B: Worldline Settlement Report

The Worldline settlement report represents payment gateway transactions settled through Worldline.

Common fields may include:

• Transaction ID
• Order reference
• Payment amount
• Transaction date
• Settlement amount
• Settlement date
• Deduction or charge amount
• Transaction status

This report helps validate Worldline payment collections.

Side B: Worldline Refund Report

The Worldline refund report represents refund or reversal transactions.

Common fields may include:

• Original transaction ID
• Refund reference
• Order reference
• Refund date
• Refund amount
• Refund status
• Settlement or adjustment date

This report helps finance teams ensure that refunds are correctly linked to original ERP sales and payment transactions.

Side B: BlueDart COD Report

The BlueDart COD report represents COD collections and remittances from the courier partner.

Common fields may include:

• AWB number
• Order number
• Delivery date
• COD amount
• Remitted amount
• Remittance date
• Deduction or adjustment amount
• Shipment status
• RTO status

This report helps validate whether COD orders have been collected and remitted correctly.

How Matching Typically Works

ERP sales vs payment gateway and COD reconciliation usually works by separating prepaid orders and COD orders.

A typical process looks like this:

1. The ERP sales report is uploaded.
2. Gokwik, PayU, Worldline, Worldline refund, and BlueDart COD reports are uploaded.
3. Prepaid ERP sales are matched with payment gateway settlement records using order ID, transaction ID, or payment reference.
4. Refund records are matched with original ERP orders and payment transactions.
5. COD ERP orders are matched with BlueDart records using AWB, tracking number, or order number.
6. ERP order amount is compared with payment gateway settlement or COD remittance amount.
7. Refunds, cancellations, returns, and RTOs are reviewed separately.
8. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• ERP shows a prepaid order of ₹2,500.
• PayU or Worldline shows a successful payment of ₹2,500 against the same order reference.
• The transaction is treated as matched.

For COD:

• ERP shows a COD order of ₹1,800 with an AWB number.
• BlueDart shows COD remittance of ₹1,800 against the same AWB.
• The transaction is treated as matched.

For refunds:

• ERP shows a refund against an order.
• Worldline refund report shows a matching refund reference and amount.
• The refund is treated as reconciled.

If the reference matches but the amount differs, the difference may be due to gateway charges, refund adjustment, COD short remittance, RTO, deduction, or timing.

Why Multi-Partner Reconciliation Is Complex

This reconciliation is complex because sales, payments, refunds, and COD remittances may come from different systems.

Common challenges include:

• One ERP sales report mapped against multiple external reports
• Different transaction IDs across partners
• Gateway settlement dates differing from order dates
• Refunds appearing separately from settlements
• COD remittance happening after delivery
• AWB missing or incorrect in ERP
• Failed or duplicate payments appearing in gateway reports
• RTO orders reducing COD collections
• One settlement batch covering many orders
• Partner deductions reducing the final amount received

A good reconciliation process should handle prepaid payments, refunds, and COD collections as separate but connected workflows.

Common Exceptions in ERP vs PG-COD Reconciliation

1. ERP Prepaid Sale Missing in Gateway Settlement

This happens when ERP shows a prepaid sale, but no matching Gokwik, PayU, or Worldline settlement record is found.

Possible reasons include:

• Payment failed after order creation
• Settlement report period is incomplete
• Payment reference is missing in ERP
• Payment settled in another period
• Order was cancelled or refunded
• Wrong gateway report was uploaded

This exception should be reviewed because every prepaid ERP sale should have payment support.

2. Gateway Settlement Missing in ERP

This happens when a gateway report shows a successful payment, but no matching ERP sale is found.

Possible reasons include:

• ERP sales report is incomplete
• Order reference was stored differently
• Payment belongs to another period
• Duplicate or retry payment exists
• Payment callback or sync issue occurred
• Manual order entry is pending

This exception should be reviewed so every payment collection has valid sales support.

3. Worldline Refund Missing in ERP

This happens when the Worldline refund report shows a refund, but the ERP does not show the corresponding refund entry.

Possible reasons include:

• Refund has not been posted internally
• Original order reference is missing
• Refund belongs to another period
• Refund was processed directly through the gateway
• ERP refund sync failed
• Partial refund was not mapped correctly

This exception should be reviewed because refunds reduce net sales and receivables.

4. ERP Refund Missing in Gateway Refund Report

This happens when ERP shows a refund, but no matching gateway refund record is found.

Possible reasons include:

• Refund is approved internally but not processed by the gateway
• Refund failed or is pending
• Refund reference was not captured
• Refund was processed through another mode
• Gateway report period is incomplete

This exception should be tracked until the refund is processed or explained.

5. COD Order Missing in BlueDart Remittance

This happens when ERP shows a COD order, but no matching BlueDart COD remittance is found.

Possible reasons include:

• Shipment is not delivered yet
• COD remittance is pending
• AWB number is missing or incorrect
• Order was returned or RTO
• BlueDart report period is incomplete
• Remittance falls in a later cycle

This exception should be tracked until the COD amount is remitted or the shipment status is resolved.

6. BlueDart COD Remittance Missing in ERP

This happens when BlueDart shows a COD remittance, but no matching ERP order is found.

Possible reasons include:

• ERP report is incomplete
• AWB was not captured internally
• Order number was stored differently
• Remittance belongs to another period
• Duplicate courier remittance exists
• Manual mapping is required

This exception should be reviewed so every COD receipt has order-level support.

7. Amount Mismatch

Amount mismatches occur when the order or transaction reference matches, but the ERP amount and external amount differ.

Possible causes include:

• Partial payment
• Gateway fee or deduction
• Refund adjustment
• COD short remittance
• Courier deduction
• Shipping charge difference
• Discount or coupon difference
• RTO adjustment
• Rounding difference
• Wrong amount field selected

Amount mismatches directly affect sales, receivables, and cash reporting.

8. Duplicate Transactions

Duplicates may appear in ERP, gateway, refund, or COD reports.

Examples include:

• Same ERP order repeated
• Same payment reference repeated
• Same refund reference repeated
• Same AWB repeated
• Duplicate settlement entry
• Duplicate file upload

Duplicates can overstate sales, payments, refunds, or COD collections if not identified.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile ERP sales, payment gateway settlements, refund reports, and COD remittance reports manually in Excel.

The usual process includes:

1. Exporting ERP sales data.
2. Downloading Gokwik, PayU, and Worldline settlement reports.
3. Downloading Worldline refund reports.
4. Downloading BlueDart COD remittance reports.
5. Cleaning order IDs, transaction IDs, refund references, AWB numbers, and dates.
6. Separating prepaid, refund, and COD transactions.
7. Matching records using lookup formulas.
8. Comparing ERP values with settlement and remittance values.
9. Reviewing refunds, cancellations, RTOs, and unmatched records.

This becomes difficult as transaction volumes increase.

Common Excel challenges include:

• Multiple external reports
• Different reference formats
• Refunds reported separately
• Missing AWB numbers
• COD remittances delayed across periods
• Duplicate payments or refunds missed
• Broken lookup formulas
• Manual copy-paste errors
• No clear audit trail

A structured reconciliation workflow reduces these risks.

What a Good ERP vs PG-COD Reconciliation Process Should Include

A reliable process should include:

• Complete ERP sales report
• Complete Gokwik settlement report
• Complete PayU settlement report
• Complete Worldline settlement report
• Complete Worldline refund report
• Complete BlueDart COD report
• Separate prepaid, refund, and COD matching logic
• Order ID, transaction ID, refund reference, AWB, and payment reference mapping
• Refund, cancellation, return, and RTO visibility
• Amount mismatch reporting
• ERP-only exception reporting
• External-only exception reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which sales were collected, which refunds were processed, which COD orders were remitted, and which records need follow-up.

How Cointab Helps

Cointab can help finance teams automate ERP sales vs payment gateway and COD reconciliation by comparing ERP sales data with Gokwik, PayU, Worldline, Worldline refund, and BlueDart COD reports in a structured workflow.

Finance teams can map ERP order IDs, payment references, transaction IDs, refund references, AWB numbers, amount fields, and date fields once and reuse the setup for future periods.

Cointab helps teams:

• Upload ERP sales, payment gateway, refund, and COD reports
• Match prepaid ERP sales with Gokwik, PayU, and Worldline settlements
• Match ERP refunds with Worldline refund records
• Match COD ERP orders with BlueDart remittance records
• Compare ERP amounts with settled, refunded, and remitted amounts
• Identify fully matched transactions
• Highlight amount mismatches, short settlements, and short remittances
• Show ERP-only and external-only exceptions
• Review refunds, cancellations, returns, and RTO differences
• Download audit-ready Excel reports

This reduces manual Excel work and gives finance teams better visibility into prepaid collections, refunds, and COD remittance differences.

Business Value

ERP sales vs payment gateway and COD reconciliation helps finance teams:

• Validate prepaid collections
• Track COD remittances
• Reconcile refunds accurately
• Identify unpaid or unremitted orders
• Detect short settlements
• Detect short COD remittances
• Improve receivable accuracy
• Reduce gateway and courier disputes
• Speed up month-end close
• Strengthen audit documentation
• Reduce manual reconciliation work

It also helps finance, operations, and customer support teams resolve order-level collection and refund issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile ERP sales with payment gateway and COD reports regularly
• Separate prepaid, refund, and COD transactions before matching
• Use order ID and transaction ID for gateway matching
• Use refund reference and original transaction ID for refund matching
• Use AWB and tracking numbers for COD matching
• Review refunds, cancellations, returns, and RTOs separately
• Track delayed settlements separately from true mismatches
• Check duplicate order IDs, transaction IDs, refund references, and AWB numbers
• Maintain period-wise reconciliation history
• Document manual adjustments clearly

Conclusion

ERP sales vs payment gateway and COD reconciliation helps finance teams confirm whether ERP sales, prepaid settlements, refunds, COD collections, returns, cancellations, and RTO adjustments are properly aligned.

Because this reconciliation depends on ERP sales, Gokwik settlements, PayU settlements, Worldline settlements, Worldline refunds, BlueDart COD remittances, order IDs, payment references, refund references, AWB numbers, and timing differences, manual Excel work can become slow and error-prone as order volumes grow.

With Cointab, finance teams can automate ERP sales vs payment gateway and COD 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 sales vs payment gateway and COD reconciliation without relying on manual Excel work. No credit card required.

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