Unicommerce Orders vs Payment, Wallet and COD Settlement Reconciliation: A Complete Guide for Finance Teams

Unicommerce orders vs payment, wallet and COD settlement reconciliation is the process of comparing internal order records from Unicommerce with multiple external payment, wallet, gift card, and COD settlement reports.

For eCommerce and D2C brands, collections do not come from one source. Some orders are paid online through checkout or payment gateway partners, some are collected through COD logistics partners, and some include wallet or gift card payments. The internal order report shows the expected order value, while external reports show the actual payments, settlements, remittances, or adjustments.

This reconciliation helps finance teams answer:

• Are all Unicommerce orders paid, settled, or remitted correctly?
• Are all Gokwik, Razorpay, and Cashfree transactions linked to valid orders?
• Are wallet and gift card payments recorded correctly?
• Are COD remittances matched using AWB, order number, or tracking reference?
• Do final order amounts match external settlement amounts?
• Which orders are missing, mismatched, duplicated, delayed, or pending review?

For finance teams, this reconciliation supports revenue accuracy, settlement tracking, COD control, refund and exchange review, month-end close, and audit readiness.

What Is Unicommerce Orders vs Payment, Wallet and COD Settlement Reconciliation?

Unicommerce orders vs payment, wallet and COD settlement reconciliation compares two sides of data.

Side A: Unicommerce Order Report
This represents the internal order record. It contains order date, final calculated amount, display order code, exchange original order ID, and tracking number.

Side B: External Payment, Wallet, Gift Card and COD Reports
This includes reports from Gokwik, Razorpay, Cashfree, gift card systems, wallet systems, and COD remittance partners such as BlueDart, Ithink, and Delhivery.

The goal is to confirm whether every internal order has the correct external payment, wallet, gift card, or COD settlement support.

Matching is mainly based on:

• Display order code
• Exchange original order ID
• Tracking number
• Platform order ID
• Shopify transaction ID
• Payment notes
• Order notes
• Razorpay notes
• Order name
• Wallet or gift card reference
• AWB number
• COD order number
• Final amount
• Net payment
• Remitted amount
• COD amount
• Transaction, settlement, remittance, pickup, or order date

Why This Reconciliation Matters

A single eCommerce order may pass through multiple systems before it is fully settled. Unicommerce may show the order value, while the payment gateway report, COD partner report, wallet report, or gift card report may show the actual collection or adjustment.

Without reconciliation, finance teams may face issues such as:

• Orders marked paid internally but missing in payment reports
• External payment records not linked to internal orders
• COD remittances not received for delivered orders
• Gift card or wallet payments not captured correctly
• Amount mismatches between internal and external reports
• Exchange orders not linked to original orders
• AWB or tracking references missing
• Duplicate transactions
• Month-end close delays
• Audit queries due to missing order-level support

A structured reconciliation process helps finance teams validate whether every order has been collected, remitted, adjusted, or flagged for review.

Reports Involved

Side A: Unicommerce Order Report

The Unicommerce order report represents the business’s internal order view.

Important fields include:

• Order date
• Final calculated order amount
• Display order code
• Exchange original order ID
• Tracking number

The final calculated amount represents the order value to be reconciled. Display order code helps match prepaid transactions. Tracking number helps match COD remittance records. Exchange original order ID helps identify orders linked to replacements or exchanges.

Side B: Gokwik Settlement Report

The Gokwik report may include:

• Final amount
• Platform order ID
• Shopify transaction ID
• Transaction date

This report is usually matched using order ID, transaction ID, and amount.

Side B: Razorpay and Cashfree Settlement Reports

Payment gateway settlement reports may include:

• Final amount
• Payment notes
• Order notes
• Razorpay notes
• Entity created date
• Settlement date

These reports help validate prepaid collections and gateway-side settlement records.

Side B: Gift Card and Wallet Reports

Gift card and wallet reports may include:

• Net payments
• Final amount
• Order name
• Reference order name
• Title
• Created date

These reports help identify payments made using wallet balances, gift cards, store credits, or similar instruments.

Side B: COD Remittance Reports

COD remittance reports from logistics partners may include:

• Remitted amount
• COD amount
• Price
• AWB
• Order number
• Pickup date
• Remittance date
• Transaction date

These reports help confirm whether COD collections from delivered orders have been remitted correctly.

How Matching Typically Works

Unicommerce orders vs payment, wallet and COD settlement reconciliation usually works by comparing reference, amount, and date.

A typical matching process looks like this:

1. The Unicommerce order report is uploaded.
2. Gokwik, Razorpay, Cashfree, gift card, wallet, and COD remittance reports are uploaded.
3. Internal references such as display order code, exchange original order ID, and tracking number are compared with external references.
4. Final calculated order amount is compared with final amount, net payment, remitted amount, price, or COD amount.
5. Order date is compared with transaction date, settlement date, created date, pickup date, or remittance date.
6. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• Unicommerce shows an order value of ₹2,000 with a display order code.
• A payment gateway report shows a final amount of ₹2,000 with the same platform order ID.
• The transaction is treated as matched.

For COD:

• Unicommerce shows an order with tracking number or AWB and a final amount of ₹1,500.
• A COD remittance report shows the same AWB with COD amount of ₹1,500.
• The transaction is treated as matched.

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

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

If an external record exists but no matching internal order is found, it becomes an external-only exception.

Why This Reconciliation Is Complex

This reconciliation is complex because different payment modes use different matching references.

Prepaid transactions may match using:

• Platform order ID
• Shopify transaction ID
• Payment notes
• Order notes
• Gateway notes

COD transactions may match using:

• AWB
• Tracking number
• Order number
• Pickup date
• Remittance date

Wallet and gift card transactions may match using:

• Order name
• Reference order name
• Title
• Net payment value

Because every report uses different fields, finance teams need flexible matching logic instead of relying on one standard order ID.

Common Exceptions in Unicommerce Orders vs Settlement Reconciliation

1. Internal Order Missing in External Reports

This happens when an order exists in Unicommerce but no matching payment, wallet, gift card, or COD record is found.

Possible reasons include:

• Payment failed after order creation
• Settlement is pending
• COD remittance has not been received
• Wrong partner report was uploaded
• Payment reference is missing
• AWB or tracking number is incorrect
• Order was cancelled, returned, or exchanged

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

2. External Transaction Missing in Unicommerce

This happens when an external report shows a payment, settlement, wallet entry, gift card entry, or COD remittance, but no matching Unicommerce order is found.

Possible reasons include:

• Unicommerce order report is incomplete
• Order was stored under another reference
• Payment callback failed
• Transaction belongs to another period
• Duplicate external record exists
• Manual payment or adjustment was processed separately

This can create accounting, customer support, and settlement tracking issues.

3. Amount Mismatch

Amount mismatches occur when the reference matches but the internal final amount and external amount differ.

Possible causes include:

• Partial payment
• Gateway adjustment
• Wallet or gift card split
• COD short remittance
• Refund or reversal impact
• Exchange order adjustment
• Rounding difference
• Incorrect final calculated amount

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

4. COD Remittance Mismatch

COD reconciliation depends heavily on AWB, order number, tracking number, pickup date, remittance date, and COD amount.

Common COD issues include:

• Delivered order not remitted
• Short COD remittance
• AWB not found in Unicommerce
• COD amount mismatch
• Remittance received in a later period
• Duplicate AWB entry
• Partner report missing or incomplete

These issues are important for brands with high COD order volumes.

5. Gift Card or Wallet Mismatch

Gift card and wallet transactions may not behave like normal payment gateway transactions.

Common issues include:

• Gift card redemption not linked to order
• Wallet payment missing internally
• Net payment amount mismatch
• Partial wallet usage not captured
• Duplicate wallet or gift card entry
• Order split across wallet and another payment mode

These transactions should be reviewed separately because they may affect liability and customer balance tracking.

6. Reference Mismatch

Reference mismatches are common because different partners use different identifiers.

Examples include:

• Display order code not found in partner report
• Tracking number not matching AWB
• Platform order ID formatted differently
• Payment notes missing order reference
• Exchange original order ID not linked correctly
• Order number stored in a different field

A reliable reconciliation process should use all available references before marking a transaction unmatched.

7. Date Difference

Unicommerce uses order date, while external reports may use transaction date, created date, settlement date, pickup date, or remittance date.

Date differences may happen due to:

• Payment gateway settlement cycles
• COD delivery and remittance delays
• Wallet or gift card posting timing
• Month-end cutoffs
• Refund or exchange processing delays
• Report generation 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 Unicommerce orders with payment, wallet, gift card, and COD reports manually in Excel.

The usual process includes:

1. Exporting the Unicommerce order report.
2. Downloading Gokwik, Razorpay, Cashfree, wallet, gift card, and COD reports.
3. Cleaning order IDs, AWB numbers, tracking numbers, and payment references.
4. Matching prepaid transactions using order and payment references.
5. Matching COD transactions using AWB or tracking number.
6. Comparing final order value with external amounts.
7. Separating wallet, gift card, prepaid, and COD transactions.
8. Preparing an exception report.

This becomes difficult because there are many files, formats, and reference fields.

Common Excel challenges include:

• Wrong reference column selected
• Broken lookup formulas
• AWB and order references not standardized
• Wallet and gift card values mixed with prepaid payments
• Duplicate records missed
• Amount fields mapped incorrectly
• Date format issues
• No clear audit trail

A structured reconciliation workflow reduces these risks.

What a Good Unicommerce Settlement Reconciliation Process Should Include

A reliable process should include:

• Correct Unicommerce order report
• Complete payment gateway reports
• Complete wallet and gift card reports
• Complete COD remittance reports
• Multiple reference matching
• AWB-based COD matching
• Payment ID and order ID matching
• Wallet and gift card amount validation
• Amount mismatch reporting
• Internal-only and external-only exception reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders are fully matched and which need follow-up.

How Cointab Helps

Cointab can help finance teams automate Unicommerce orders vs payment, wallet and COD settlement reconciliation by comparing internal order data with multiple external reports in one workflow.

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

Cointab helps teams:

• Upload Unicommerce, Gokwik, Razorpay, Cashfree, wallet, gift card, and COD reports
• Match orders using display order code, exchange order ID, tracking number, platform order ID, transaction ID, order notes, and AWB
• Compare final order amount with final amount, net payment, remitted amount, price, and COD amount
• Identify fully matched transactions
• Highlight amount mismatches
• Show internal-only and external-only exceptions
• Review skipped or invalid records
• Download audit-ready Excel reports

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

Business Value

Unicommerce orders vs payment, wallet and COD settlement reconciliation helps finance teams:

• Validate order-level collections
• Track prepaid settlements
• Reconcile COD remittances
• Control wallet and gift card usage
• Identify missing or delayed partner payments
• Detect amount mismatches
• Improve month-end close
• Strengthen audit documentation
• Reduce manual reconciliation effort

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

Best Practices

Finance teams should follow these best practices:

• Reconcile Unicommerce and partner reports regularly
• Separate prepaid, COD, wallet, and gift card logic
• Use multiple references before marking records unmatched
• Match COD using AWB, tracking number, and order reference
• Review amount mismatches by partner
• Check duplicate payment and AWB references
• Track delayed COD remittances separately
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Unicommerce orders vs payment, wallet and COD settlement reconciliation helps finance teams confirm whether internal order records match external payment, wallet, gift card, and COD settlement reports.

Because this workflow includes multiple payment partners, wallet reports, gift card reports, COD partners, settlement dates, remittance dates, AWB references, order IDs, and exchange references, manual reconciliation can become slow and error-prone.

With Cointab, finance teams can automate Unicommerce orders vs payment, wallet and COD settlement reconciliation, reduce Excel effort, identify exceptions faster, and generate audit-ready reports for review.

Start your 14-day free trial with Cointab and automate Unicommerce orders vs payment, wallet and COD settlement reconciliation without relying on manual Excel work. No credit card required.

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