Payment reconciliation for ecommerce matches orders and payment records with funds received in the merchant’s bank account. It confirms whether refunds, fees, disputes and settlements were recorded correctly.
For a small store, this may mean comparing a payment dashboard with a bank statement. Larger businesses may reconcile several websites, marketplaces, payment methods and settlement cycles.
TL;DR: Ecommerce Payment Reconciliation
Reconciliation connects each ecommerce order with its payment attempts, refunds, fees, settlement record and final bank credit. Use stable identifiers such as order ID, payment ID, settlement ID and UTR. Reconcile frequently, separate payment status from settlement status, and send unresolved exceptions for review instead of matching by amount alone.
What Is Ecommerce Payment Reconciliation?
Ecommerce payment reconciliation means comparing records from different systems to confirm that the amount collected and adjusted matches the amount received.
Relevant records may come from:
- Ecommerce and order-management platforms
- Payment gateway or processor records
- Marketplaces
- Refund and dispute systems
- Settlement reports
- Bank accounts
- Accounting or ERP software
Reconciliation follows an order through payment, refund or dispute activity, settlement and bank credit. For every completed order, the business should be able to answer:
- Was a successful payment recorded?
- Was the correct amount collected?
- Were fees, taxes and adjustments recorded separately?
- Was the payment included in a settlement?
- Did the expected net settlement reach the bank?
- Was any refund completed and linked to the original payment?
Payment Reconciliation vs Settlement Reconciliation
Payment reconciliation verifies that each ecommerce order has the correct payment status. It identifies successful, failed, pending, duplicate or unmatched payment attempts.
Settlement reconciliation checks whether the payment provider transferred the expected net amount to the merchant’s bank account after fees, refunds, disputes and other adjustments.
The two are connected but not interchangeable. One order may have several payment attempts, while one settlement may contain payments and adjustments from many orders. The settlement and reconciliation guide explains how payment gateway settlements move from transactions to bank credits.
Why Payment Reconciliation Matters for Ecommerce
The order value displayed on an ecommerce platform is not always the amount deposited into the bank. Fees, refunds, chargebacks, currency conversion and other adjustments can change the final value.
Regular reconciliation helps a business:
- Verify that successful payments were settled
- Find orders marked paid without a confirmed payment
- Track refunds until their final status
- Record gateway fees and applicable taxes correctly
- Identify duplicate payments and unmatched credits
- Investigate delayed or missing settlements
- Support accurate revenue and cash-flow reporting
- Answer customer payment questions with transaction-level evidence
Order, Payment and Settlement Records
Each ecommerce transaction creates several related records.
Order Record
The order record comes from the ecommerce platform or order-management system. It normally contains the order ID, items, discounts, shipping, tax, total amount, fulfilment status and return or cancellation status.
Payment Record
The payment record shows each payment attempt and may contain the payment ID, order reference, method, amount, status, capture details, timestamp, network reference and failure reason.
Settlement Record
The settlement record explains the transfer to the merchant’s bank account. It can contain the settlement ID, date, status, gross amount, fees, taxes, refund or dispute adjustments, net settlement and UTR.
A single order may have multiple payment attempts, one successful payment, a partial refund and a later settlement adjustment. Stable identifiers are needed to connect them reliably.
Also read: How payment gateways connect with business systems
How Ecommerce Payment Reconciliation Works
1. Collect Records for the Same Period
Gather order data, payment attempts, refunds, disputes, settlement reports, bank statements and accounting records. If the business uses multiple gateways or marketplaces, collect each source separately before combining the data.
2. Standardise the Data
Systems often use different field names, time zones, currencies and status labels. Before matching:
- Map merchant references to one order ID field
- Use one timestamp format and time zone
- Standardise currency and amount formats
- Separate gross amount, fees, taxes, refunds and net settlement
- Map provider-specific statuses to consistent internal statuses
- Remove duplicate exports
This step is essential for automated matching because fields with different formats or meanings cannot be compared reliably.
3. Match Orders With Payments
Use a unique order ID or merchant reference as the primary key, supported by payment ID and transaction details. Identify:
- Successful, failed and pending attempts
- Orders with several payment attempts
- Duplicate successful payments
- Paid orders without a confirmed payment
- Payments without a recognisable order
Do not match by amount alone. Different customers can place orders for the same value.
4. Match Payments With Settlements
A successful payment may be grouped with other transactions in a later settlement. Match it using payment ID, order ID, settlement ID, settlement date and provider references.
The settlement value can be lower because of fees, refunds or disputes. Every difference should have an identifiable reason. Cashfree’s settlement documentation explains settlement IDs and UTRs.
5. Match Settlements With Bank Credits
Compare the expected net settlement with the bank credit using the settlement ID, date and UTR. Allow for the configured settlement cycle, bank working days, reversals and other documented adjustments.
A bank credit proves that money arrived, but the settlement report explains which payments and adjustments contributed to it. Cashfree’s All Settlements API supports lookup using settlement ID, UTR or date range.
What Is a Payment Settlement Report?
A payment settlement report lists the financial activity included in a transfer from the payment provider to the merchant’s bank account. It typically contains:
- Settlement ID, date and status
- Related payments or transactions
- Gross collected amount
- Processing fees and applicable taxes
- Refund and dispute adjustments
- Net settlement amount
- Bank reference or UTR
A transaction report lists individual payment attempts. A settlement report groups the financial events that contribute to a bank transfer. Both are necessary for end-to-end reconciliation.
How to Reconcile Ecommerce Refunds
Refund reconciliation connects the refund request with the original order, payment, refund event, settlement adjustment and accounting entry.
Each refund record should contain the original order and payment IDs, a unique refund ID, refund amount, reason, initiation date, current status and final reference where available.
Keep the following statuses separate:
- Refund requested
- Refund initiated
- Refund processed or successful
- Refund failed
- Refund reversed
- Refund received by the customer, where confirmation is available
An initiated refund may not yet have reached the customer’s account. Customer communication should reflect the actual status. Event-based updates can be handled through payment webhooks and verified against provider records.
Partial Refund Example
If a customer pays ₹3,000 and receives a ₹1,000 refund, record the original payment of ₹3,000, the refund of ₹1,000 and the retained amount of ₹2,000. Also record the applicable fee treatment and final order status. Do not treat the partial refund as a new sale or full cancellation.
Also read: Set up webhooks for payments, refunds, settlements and disputes
Reconciling Fees, Taxes and Adjustments
The merchant’s bank credit may differ from the customer payment because of processing fees, tax on fees, refunds, chargebacks, currency conversion, settlement fees or marketplace commissions.
| Item | Amount |
|---|---|
| Customer payment | ₹10,000 |
| Processing fee | -₹200 |
| Applicable tax on fee | -₹36 |
| Refund adjustment | -₹1,000 |
| Expected net settlement | ₹8,764 |
This is illustrative. Actual fees, taxes and refund treatment depend on the provider, contract, payment method and applicable tax rules. Indian businesses should confirm their accounting and GST treatment with a qualified professional.
Common Ecommerce Reconciliation Mismatches
| Mismatch | What to check |
|---|---|
| Order marked paid but payment missing | Payment ID, server-side status, webhook event and settlement record |
| Payment received but order missing | Checkout interruption, order-creation error and merchant reference mapping |
| Payment and order amounts differ | Discounts, tax, shipping, currency conversion, split or partial payments |
| Successful payment not settled | Settlement cycle, status, holds, reversals and bank holidays |
| Settlement differs from bank credit | UTR, value date, reversal, period selection and bank adjustment |
| Refund missing from settlement | Refund ID, processing status and later settlement cycles |
| Duplicate successful payment | Customer retry, timeout and duplicate-payment handling rule |
| Currency mismatch | Customer, processing and settlement currencies, exchange rate and fees |
Use order-level settlement lookup when the question begins with a specific order rather than a settlement batch.
Automated Payment Reconciliation
Automated reconciliation imports records, standardises fields, applies matching rules and routes unresolved items for review. It is useful when manual spreadsheet matching becomes slow or error-prone.
A sensible matching hierarchy is:
- Exact order ID and payment ID
- Exact payment ID and amount
- Payment ID and settlement reference
- Validated UTR and settlement date
- Amount and date as a lower-confidence rule
- Manual review for unresolved exceptions
Automation should not silently force a match. Each exception needs a type, related IDs, amount, owner, status, supporting evidence and resolution date. Common exceptions include missing payments, duplicate payments, incorrect fees, delayed settlements, failed refunds and unrecognised bank credits.
Cashfree’s PG Reconciliation API returns reconciliation details for a selected date range. Its payment APIs can support connected order, payment, refund and settlement workflows.
Automation Still Needs Exception Review
Automated rules reduce repetitive matching, but delayed statuses, missing identifiers and adjustments from later settlement cycles can create false exceptions. Keep a clear review path instead of treating every unmatched record as a loss.
How Often Should Ecommerce Payments Be Reconciled?
A practical schedule is:
- Daily: Orders, successful and failed payments, duplicate attempts and high-value transactions
- Every settlement cycle: Settlement reports, fees, refunds and bank credits
- Weekly: Unresolved exceptions, disputes and delayed refunds
- Monthly: Accounting close, revenue, taxes and management reporting
High-volume businesses should not wait until month-end. Earlier review makes it easier to trace payment events and customer communication.
How Cashfree Supports Ecommerce Reconciliation
Cashfree provides dashboard reports, APIs and webhooks that businesses can use to connect orders, payment events, refunds, disputes, settlements and bank credits.
A Cashfree workflow may match the ecommerce order with its successful payment, review fees and adjustments, and connect the settlement ID and UTR with the bank credit. The Payments integration overview describes available integration options.
Businesses that need faster access to eligible funds can review Instant Settlements. Marketplaces that divide collections among vendors may require Easy Split and its line-item reconciliation reports. Availability and settlement cycles depend on the merchant configuration and applicable terms.
Also read: Integrating a payment gateway with Shopify
Ecommerce Payment Reconciliation Checklist
Before closing a reconciliation period, confirm that:
- Every completed order has an appropriate payment status
- Every successful payment is linked to an order
- Pending and failed payments are not recorded as revenue
- Duplicate payments have been investigated
- Refunds are linked to original payments
- Fees, taxes, disputes and chargebacks are recorded separately
- Settlement reports match expected net amounts
- Bank credits match settlements through UTRs or references
- Unmatched items have owners, evidence and due dates
- Accounting reflects gross sales, refunds, fees and adjustments
Conclusion: Connect Every Order to Its Bank Credit
Ecommerce payment reconciliation creates a traceable link between an order, its payment attempts, any refund or dispute, the provider’s settlement report and the final bank credit.
Use stable identifiers, separate payment status from settlement status and explain every adjustment. Automation can reduce repetitive work, but exceptions still require clear ownership and review. A regular process improves financial accuracy, customer support and cash-flow visibility.
Frequently Asked Questions
What is ecommerce payment reconciliation?
It is the process of matching ecommerce orders with payments, refunds, fees, settlements and bank credits to confirm that transaction and accounting records are complete.
What is settlement reconciliation?
Settlement reconciliation compares the transactions and adjustments in a provider’s settlement report with the net amount deposited into the merchant’s bank account.
What is a payment settlement report?
It is a report showing the payments, fees, taxes, refunds, disputes and other adjustments that contributed to a settlement, along with the net amount and bank reference.
What is refund reconciliation?
Refund reconciliation links a refund to its original order and payment, tracks its processing status and confirms the related settlement and accounting adjustments.
How frequently should ecommerce businesses reconcile payments?
Many businesses check orders and payments daily, reconcile each settlement cycle, review exceptions weekly and complete a wider accounting reconciliation monthly. Higher transaction volume may require more frequent checks.
Can payment reconciliation be fully automated?
Most routine matching can be automated when identifiers and data formats are consistent. Human review is still needed for missing IDs, delayed events, disputed adjustments and other exceptions.
Which fields are required for ecommerce reconciliation?
Common fields include order ID, payment ID, amount, currency, payment status, refund ID, refund amount, settlement ID, fees, taxes, net settlement, settlement date and UTR or bank reference.
