Website Order Payment and COD Remittance Reconciliation: A Complete Guide for Finance Teams

Website order payment and COD remittance reconciliation is the process of comparing internal website order records with external payment and COD remittance reports.

For eCommerce and D2C businesses, customer collections usually happen through multiple channels. Prepaid orders may be paid through Razorpay, while cash-on-delivery orders may be collected and remitted later by logistics partners such as Delhivery and Shiprocket.

The website order report shows what the business expected to collect. Razorpay and COD remittance reports show what was actually paid, collected, or remitted.

This reconciliation helps finance teams answer:

• Are all website orders paid or remitted correctly?
• Are all Razorpay payments linked to valid website orders?
• Are all Delhivery COD remittances mapped to the right orders?
• Are all Shiprocket COD remittances matched with the correct order or AWB?
• Do order amounts match payment and remittance amounts?
• Which orders are unpaid, short-remitted, delayed, duplicated, or pending review?

For finance teams, this reconciliation supports revenue accuracy, COD control, payment validation, receivable tracking, month-end close, and audit readiness.

What Is Website Order Payment and COD Remittance Reconciliation?

Website order payment and COD remittance reconciliation compares two sides of transaction data.

Side A: Website Orders
This represents the company’s internal order records. It may include order ID, order date, payment mode, order amount, payment status, shipment tracking number, AWB number, and delivery status.

Side B: External Payment and COD Remittance Reports
This includes Razorpay payment records and COD remittance reports from logistics partners such as Delhivery and Shiprocket.

The goal is to confirm whether every website order has the correct payment or COD remittance support.

Matching is usually based on:

• Website order ID
• Razorpay payment ID
• Razorpay order ID
• COD order number
• AWB number
• Tracking number
• Shipment reference
• Order amount
• Paid amount
• COD amount
• Remitted amount
• Order date
• Payment 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

A website order being created does not always mean money has been received.

For prepaid orders, Razorpay confirms whether the customer payment was successful. For COD orders, Delhivery or Shiprocket confirms whether cash was collected and remitted after delivery.

Without reconciliation, finance teams may face issues such as:

• Website orders marked paid but missing in Razorpay
• Razorpay payments not linked to website orders
• COD orders delivered but not remitted
• Short COD remittance
• AWB numbers not mapped correctly
• Duplicate payment or remittance entries
• Refunds or cancellations not adjusted correctly
• Delayed COD remittance
• Month-end receivable differences
• Audit queries due to missing payment support

A structured reconciliation process helps finance teams validate prepaid and COD collections in one clear workflow.

Reports Involved

Side A: Website Orders

The website order report represents the internal order view.

Common fields may include:

• Order ID
• Order date
• Customer details
• Payment mode
• Order amount
• Final payable amount
• Payment status
• Shipment tracking number
• AWB number
• Delivery status

This report shows what the business expected to collect from customers.

Side B: Razorpay Report

The Razorpay report represents prepaid payment activity.

Common fields may include:

• Payment ID
• Razorpay order ID
• Website order reference
• Payment amount
• Payment status
• Payment date
• Settlement status
• Refund or reversal details

This report helps finance teams confirm whether prepaid orders were successfully paid.

Side B: Delhivery COD Remittance Report

The Delhivery COD remittance report represents COD collections remitted by Delhivery.

Common fields may include:

• AWB number
• Order number
• COD amount
• Remitted amount
• Remittance date
• Delivery status
• Adjustment details

This report helps finance teams verify whether COD money collected from customers was remitted correctly.

Side B: Shiprocket COD Remittance Report

The Shiprocket COD remittance report represents COD collections processed through Shiprocket.

Common fields may include:

• Order ID
• AWB number
• Courier partner
• COD amount
• Remitted amount
• Remittance date
• Pickup date
• Delivery date
• Adjustment details

This report helps finance teams validate COD collections routed through Shiprocket and its courier network.

How Matching Typically Works

Website order payment and COD remittance reconciliation usually works by separating prepaid and COD orders before matching.

A typical process looks like this:

1. The website order report is uploaded.
2. Razorpay, Delhivery COD, and Shiprocket COD remittance reports are uploaded.
3. Prepaid orders are matched with Razorpay using order ID, payment ID, or Razorpay order reference.
4. COD orders are matched with Delhivery or Shiprocket using AWB number, order number, or tracking reference.
5. Website order amount is compared with payment amount, COD amount, or remitted amount.
6. Order dates are compared with payment dates, delivery dates, and remittance dates.
7. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• The website shows a prepaid order of ₹2,500.
• Razorpay shows a successful payment of ₹2,500 for the same order.
• The order is treated as matched.

For COD:

• The website shows a COD order of ₹1,800 with an AWB number.
• Delhivery or Shiprocket shows a COD remittance of ₹1,800 for the same AWB.
• The order is treated as matched.

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

If a website order exists but no payment or COD remittance is found, it becomes an internal-only exception.

If Razorpay, Delhivery, or Shiprocket contains a transaction with no matching website order, it becomes an external-only exception.

Why Prepaid and COD Matching Should Be Separate

Prepaid and COD collections follow different workflows.

Prepaid orders are usually matched using:

• Website order ID
• Razorpay payment ID
• Razorpay order ID
• Payment amount
• Payment date
• Payment status

COD orders are usually matched using:

• AWB number
• Tracking number
• Courier order number
• COD amount
• Remitted amount
• Delivery date
• Remittance date

If prepaid and COD records are mixed together manually, finance teams may create incorrect matches or miss real exceptions.

A good reconciliation process should separate prepaid payment matching from COD remittance matching while still giving one consolidated order-level view.

Common Exceptions in Website Order Reconciliation

1. Website Order Missing in Razorpay

This happens when a prepaid website order exists, but no matching Razorpay payment is found.

Possible reasons include:

• Payment failed after order creation
• Payment was initiated but not captured
• Razorpay reference was not stored correctly
• Wrong report period was selected
• Order was cancelled
• Payment belongs to another gateway or method

This exception should be reviewed because the website may show an order without confirmed payment.

2. Razorpay Payment Missing in Website Orders

This happens when Razorpay shows a payment, but no matching website order is found.

Possible reasons include:

• Payment callback failed
• Order creation failed after payment
• Website order report is incomplete
• Payment reference was stored differently
• Duplicate payment attempt exists
• Manual correction is required

This issue can create customer support and accounting challenges.

3. COD Order Missing in Remittance Report

This happens when a COD order exists in the website report, but no matching Delhivery or Shiprocket remittance is found.

Possible reasons include:

• Order has not been delivered yet
• COD remittance is pending
• AWB number is incorrect
• Courier report period is incomplete
• Remittance is delayed
• Shipment was returned or cancelled

This exception should be tracked until the COD amount is received or the order status is resolved.

4. COD Remittance Missing in Website Orders

This happens when Delhivery or Shiprocket shows a COD remittance, but no matching website order is found.

Possible reasons include:

• Website order report is incomplete
• AWB number was not captured internally
• Remittance belongs to another order period
• Courier partner reference is different
• Duplicate remittance record exists
• Manual mapping is required

This exception should be reviewed so every partner remittance has order-level support.

5. Amount Mismatch

Amount mismatches occur when the reference matches but the website order amount and external amount differ.

Possible causes include:

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

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

6. Delayed COD Remittance

COD collections are often remitted after delivery, so date differences are common.

Possible reasons include:

• Courier settlement cycle
• Delivery date and remittance date gap
• Weekend or holiday delay
• Return or RTO processing
• Partner holdback
• Cutoff timing difference

A delayed COD item may not be an error, but it should be visible and tracked.

7. Duplicate Payments or Remittances

Duplicates may appear in internal or external reports.

Examples include:

• Same website order appearing twice
• Duplicate Razorpay payment attempt
• Same AWB repeated in COD report
• Duplicate courier remittance entry
• Duplicate file upload
• Retry payments creating multiple records

Duplicates can overstate collections if not identified.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile website orders, Razorpay payments, and COD remittances manually in Excel.

The usual process includes:

1. Exporting the website order report.
2. Downloading Razorpay payment data.
3. Downloading Delhivery and Shiprocket COD remittance reports.
4. Separating prepaid and COD orders.
5. Cleaning order IDs, payment IDs, AWB numbers, and tracking numbers.
6. Matching prepaid payments using lookup formulas.
7. Matching COD remittances using AWB or order number.
8. Comparing order amount with paid or remitted amount.
9. Preparing an exception report.

This becomes difficult as order volumes increase.

Common Excel challenges include:

• Different formats across Razorpay, Delhivery, and Shiprocket
• AWB numbers not captured consistently
• Payment IDs stored in different fields
• COD remittance delays
• Duplicate entries missed
• Broken lookup formulas
• Manual copy-paste errors
• No clear audit trail
• Repeated effort every close cycle

A structured reconciliation workflow reduces these risks.

What a Good Website Order Reconciliation Process Should Include

A reliable process should include:

• Complete website order report
• Complete Razorpay payment report
• Complete Delhivery COD remittance report
• Complete Shiprocket COD remittance report
• Separate prepaid and COD matching logic
• Matching using order ID, payment ID, AWB, and tracking references
• Amount comparison between order value, payment value, and remitted value
• Date visibility across order, payment, delivery, and remittance stages
• Internal-only exception reporting
• External-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders are fully collected, which are pending, and which require follow-up.

How Cointab Helps

Cointab can help finance teams automate website order payment and COD remittance reconciliation by comparing internal order records with Razorpay, Delhivery COD, and Shiprocket COD remittance reports in one structured workflow.

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

Cointab helps teams:

• Upload website order, Razorpay, Delhivery COD, and Shiprocket COD remittance reports
• Match prepaid orders with Razorpay payment records
• Match COD orders with Delhivery and Shiprocket remittances
• Compare order amounts with paid and remitted amounts
• Identify fully matched transactions
• Highlight amount mismatches and short remittances
• Show internal-only and external-only exceptions
• Review delayed COD remittances
• Review skipped or invalid records
• Download audit-ready Excel reports

This reduces manual Excel work and gives finance teams better visibility into order-level payment and COD exceptions.

Business Value

Website order payment and COD remittance reconciliation helps finance teams:

• Validate prepaid collections
• Track COD remittances
• Identify unpaid or unremitted orders
• Detect unsupported payment records
• Improve revenue accuracy
• Improve receivable control
• Reduce customer support disputes
• Speed up month-end close
• Strengthen audit documentation
• Reduce manual reconciliation work

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

Best Practices

Finance teams should follow these best practices:

• Reconcile website orders with payment and COD reports regularly
• Separate prepaid and COD workflows
• Use payment IDs for prepaid matching
• Use AWB and tracking numbers for COD matching
• Compare order amount with payment and remittance amount consistently
• Review COD delays separately from true mismatches
• Check duplicate order IDs, payment IDs, and AWB numbers
• Track internal-only and external-only exceptions
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Website order payment and COD remittance reconciliation helps finance teams confirm whether internal website orders are properly paid, collected, or remitted by external partners.

Because this reconciliation involves prepaid payments, COD collections, Razorpay transactions, Delhivery remittances, Shiprocket remittances, order IDs, AWB numbers, tracking references, amounts, and date differences, manual reconciliation can become slow and error-prone as order volumes grow.

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

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