Unicommerce Order Data vs Settlement Report Reconciliation: A Complete Guide for Finance Teams

Unicommerce order data vs settlement report reconciliation is the process of comparing order-level transaction data from Unicommerce with settlement reports received from payment partners such as PayU, PhonePe, and Snapmint.

For businesses using Unicommerce to manage orders and multiple payment partners to collect money, this reconciliation is an important finance control. Unicommerce may show an order value and payment reference, while the settlement report may show the actual settled amount, transaction amount, settlement value, or merchant reference.

The goal is to confirm whether every order recorded in Unicommerce has been correctly settled by the relevant payment partner.

This reconciliation helps answer questions such as:

• Are all Unicommerce orders present in payment settlement reports?
• Are all settlement transactions linked to valid Unicommerce orders?
• Do order values match the settled values?
• Are PayU, PhonePe, and Snapmint transactions reconciled correctly?
• Are month-wise reports complete?
• Which orders are missing, mismatched, or pending settlement?

For finance teams, this reconciliation supports accurate payment tracking, settlement validation, month-end closing, and audit readiness.

What Is Unicommerce Order Data vs Settlement Report Reconciliation?

Unicommerce order data vs settlement report reconciliation compares internal order records with external settlement records.

In this workflow, the internal side contains Unicommerce order data. The external side contains multiple settlement reports, including:

• PayU April and May settlement reports
• PayU June settlement report
• PhonePe April settlement report
• PhonePe May settlement report
• PhonePe June settlement report
• Snapmint May settlement report

This shows a multi-payment-partner and multi-period reconciliation. The finance team is not comparing Unicommerce with a single settlement file. Instead, it is validating order data against several payment and settlement sources across different months.

The matching is mainly based on:

• Payment gateway ID or order reference
• Transaction or settlement amount
• Invoice date, transaction date, or settlement date

Reports Involved

Side A: Unicommerce Order Data

The Unicommerce report represents the internal order record.

Important fields include:

• Invoice created date
• Total price
• PG ID

The PG ID is the key payment reference from the order data. It helps connect the Unicommerce order with the payment partner transaction.

The total price represents the order value expected to be collected or settled.

Side B: Settlement Reports

The external side includes settlement reports from PayU, PhonePe, and Snapmint.

Each report uses its own field names and reference structure.

PayU reports use fields such as:

• AddedOn date
• Net Amount
• Merchant Txn ID

PhonePe reports use fields such as:

• Transaction Date
• Transaction Amount
• Merchant Reference ID

Snapmint reports use fields such as:

• Merchant Settlement Date
• Settlement Value
• Order No.

Although the field names differ, the business purpose is the same: to confirm whether the payment or settlement partner has recorded and settled the transaction linked to the Unicommerce order.

Why This Reconciliation Matters

When a business uses multiple payment methods or checkout partners, order and settlement data can easily become disconnected.

Unicommerce may confirm that an order exists, but the settlement partner report may show a different amount, a delayed settlement, or no matching transaction. Similarly, a settlement report may contain a transaction that is not found in Unicommerce.

Without reconciliation, finance teams may face issues such as:

• Orders not settled by the payment partner
• Settlement transactions not linked to orders
• Amount differences between order value and settlement value
• Missing monthly settlement files
• Duplicate transactions
• Incorrect partner-wise receivables
• Delayed exception resolution
• Month-end close delays

This reconciliation helps finance teams confirm that payment partner settlements are complete and accurate against order data.

How Matching Typically Works

Unicommerce order data vs settlement report reconciliation usually works by comparing references, amounts, and dates.

A typical matching flow looks like this:

1. Unicommerce order data is uploaded.
2. Settlement reports from PayU, PhonePe, and Snapmint are uploaded.
3. Unicommerce PG ID is compared with partner-side references such as Merchant Txn ID, Merchant Reference ID, or Order No.
4. Unicommerce Total Price is compared with Net Amount, Transaction Amount, or Settlement Value.
5. Invoice created date is compared with transaction or settlement dates.
6. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• Unicommerce shows an order with a total price of ₹2,000 and a PG ID.
• PhonePe shows a transaction amount of ₹2,000 with the same merchant reference ID.
• The transaction is treated as matched.

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

If an order exists in Unicommerce but not in any settlement report, it becomes an Unicommerce-only exception.

If a settlement transaction exists but no matching Unicommerce order is found, it becomes a settlement-only exception.

Why Multi-Partner Settlement Reconciliation Is Complex

This reconciliation involves PayU, PhonePe, and Snapmint. Each partner uses different terminology, date fields, and amount fields.

This creates several challenges:

• PayU uses Net Amount and Merchant Txn ID
• PhonePe uses Transaction Amount and Merchant Reference ID
• Snapmint uses Settlement Value and Order No.
• Settlement dates may differ from invoice dates
• Reports may be split month-wise
• Partner reports may have different formats
• One partner may report settlement while another reports transaction value
• Some orders may be delayed, refunded, or adjusted

Because of these differences, finance teams need a structured process to normalize and compare all partner reports with Unicommerce order data.

Common Exceptions

1. Unicommerce Order Missing in Settlement Reports

This happens when an order is present in Unicommerce but no matching record is found in PayU, PhonePe, or Snapmint reports.

Possible reasons include:

• Settlement report is incomplete
• Wrong month’s report was used
• Payment was delayed
• PG ID is missing or incorrect
• Order was paid through another partner
• Transaction failed after order creation

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

2. Settlement Transaction Missing in Unicommerce

This happens when a settlement report contains a transaction, but no matching Unicommerce order is found.

Possible reasons include:

• Order was not captured in Unicommerce
• PG reference differs between systems
• Transaction belongs to another period
• Settlement file includes historical transactions
• Manual transaction was processed outside the usual order flow
• Duplicate settlement record exists

This can create accounting and operational confusion if not investigated.

3. Amount Mismatch

Amount mismatches occur when the reference matches but the value differs.

Possible reasons include:

• Settlement amount differs from order amount
• Charges or deductions are included in net amount
• Partial settlement
• Refund or adjustment impact
• Rounding difference
• Incorrect order value
• Partner-side reporting difference

Amount mismatches are important because they directly affect collections and receivables.

4. Date Difference

Unicommerce uses invoice created date, while partner reports may use transaction date, added date, or merchant settlement date.

Date differences may occur due to:

• Payment processing delay
• Settlement cycle timing
• Month-end cutoffs
• Report generation dates
• Delayed settlement by partner
• Transactions settled in a later month

Date differences are common in settlement reconciliation and should be visible in the report.

5. Missing Monthly Reports

Because this workflow includes separate reports for April, May, and June, missing files can create false exceptions.

For example, if June PayU data is missing, Unicommerce orders paid through PayU in June may appear unmatched.

A good reconciliation process should make it clear which files were included and which period was reconciled.

6. Duplicate Transactions

Duplicates can appear in Unicommerce or settlement reports.

Examples include:

• Same PG ID appearing twice
• Same settlement file uploaded twice
• Same order appearing across two months
• Duplicate partner transaction
• Overlapping report periods

Duplicates can overstate collections or create false mismatches.

Excel-Based Reconciliation Challenges

Many finance teams reconcile Unicommerce order data and settlement reports manually in Excel.

The process usually involves:

1. Exporting Unicommerce order data.
2. Downloading PayU, PhonePe, and Snapmint reports.
3. Combining month-wise settlement files.
4. Standardizing reference fields.
5. Comparing PG ID with partner references.
6. Matching total price with settlement or transaction amount.
7. Identifying missing and mismatched records.
8. Preparing exception reports.

This becomes difficult because every partner uses different field names and file structures.

Common Excel issues include:

• Wrong reference column selected
• Broken lookup formulas
• Duplicate records missed
• Month-wise files not combined properly
• Net amount compared incorrectly
• Date format issues
• Manual copy-paste errors
• No clear audit trail

A reusable reconciliation workflow reduces these risks.

What a Good Reconciliation Process Should Include

A reliable Unicommerce order data vs settlement report reconciliation should include:

• Correct Unicommerce order data
• Complete PayU, PhonePe, and Snapmint reports
• Partner-wise reference mapping
• Standardized amount comparison
• Period-wise file validation
• Matched and unmatched categorization
• Amount mismatch reporting
• Duplicate detection
• Date difference visibility
• Audit-ready output

The output should clearly show which orders matched, which settlements are missing, and which items need follow-up.

How Cointab Helps

Cointab can help finance teams automate Unicommerce order data vs settlement report reconciliation by comparing internal order data with multiple payment partner settlement reports.

Finance teams can map PG ID, partner reference fields, dates, and amount fields once and reuse the workflow for future periods.

Cointab helps teams:

• Upload Unicommerce, PayU, PhonePe, and Snapmint reports
• Match PG ID with Merchant Txn ID, Merchant Reference ID, or Order No.
• Compare Total Price with Net Amount, Transaction Amount, or Settlement Value
• Identify fully matched transactions
• Highlight amount mismatches
• Show Unicommerce-only and settlement-only records
• Review skipped or invalid records
• Download audit-ready Excel reports

This helps reduce manual effort and improves visibility into payment settlement exceptions.

Business Value

Unicommerce order data vs settlement report reconciliation helps finance teams:

• Validate order-level collections
• Track payment partner settlements
• Identify missing or delayed settlements
• Improve receivables control
• Reduce month-end close effort
• Detect amount mismatches
• Improve audit readiness
• Reduce manual Excel work

It also helps operations and finance teams resolve payment partner issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile Unicommerce and settlement reports regularly
• Ensure all monthly settlement files are included
• Use PG ID as the primary internal reference
• Map each partner’s reference field correctly
• Review amount mismatches separately
• Track delayed settlements by partner
• Check for duplicate transaction references
• Maintain period-wise reconciliation history
• Document manual adjustments clearly

Conclusion

Unicommerce order data vs settlement report reconciliation helps finance teams confirm whether orders recorded in Unicommerce are correctly reflected in PayU, PhonePe, and Snapmint settlement reports.

Because the reconciliation involves multiple payment partners, different reference fields, month-wise reports, transaction dates, settlement dates, and amount formats, manual reconciliation can become slow and error-prone.

With Cointab, finance teams can automate this reconciliation, reduce Excel effort, identify exceptions faster, and generate audit-ready reports for review.

To learn more or get started with automated reconciliation, visit: https://www.cointab.net/