Your dashboard shows successful payments worth ₹50,000, but the bank account receives a different amount. That does not automatically mean money is missing. The payout may reflect fees, refunds, different transaction dates or other documented adjustments.
Settlement moves the amount due into your business bank account under the applicable arrangement. Payment reconciliation checks whether your orders, payment records, settlement reports and bank entries agree. One concerns the movement of money; the other explains and verifies the records around it.
What is Payment Settlement?
Merchant settlement is the transfer of funds due from processed customer payments to the merchant’s account. It follows the relevant provider agreement, payment arrangement and processing conditions.
A successful payment message does not mean the same amount has already arrived in your bank account. Customer payment confirmation and merchant payout are separate records with different purposes.
The timing and composition of a payout can depend on the payment mode, agreed cycle, cut-offs and adjustments. Use your merchant agreement and actual settlement reports to establish what should arrive and when.
Avoid assuming that a label such as T+1 always has the same operational meaning. Confirm what starts the clock, how working days are defined and whether the arrangement applies to every payment mode on your account.
What is payment reconciliation?
Payment reconciliation compares records to confirm that transactions have been recorded correctly and that differences are understood.
A merchant commonly connects four sources:
- Orders or invoices showing what the customer owes.
- Payment records showing attempts and verified outcomes.
- Settlement reports explaining payouts and adjustments.
- Bank statements showing actual credits and debits.
The aim is more precise than matching two totals. Your team should be able to explain an individual order from collection through refund or settlement, including any fees or other applicable deductions.
Reconciliation also identifies process problems. A paid order marked unpaid may delay fulfilment even if the bank payout is correct. A duplicated payment may require action even when the daily total looks healthy.
Key differences at a glance
| Question | Settlement | Reconciliation |
| What does it do? | Transfers the amount due | Compares and explains transaction records |
| Main evidence | Settlement report and bank credit | Orders, payments, adjustments and bank entries |
| Main question | Has the payout arrived? | Does the payout match what should have arrived? |
| Typical issue | A payout has not reached the account | A transaction, fee or refund cannot be matched |
| Operational owner | Finance or treasury, working with the provider | Finance operations with support from product and engineering |
A bank credit can arrive successfully while reconciliation remains incomplete. Conversely, finance can reconcile the expected payout before the bank credit appears and leave it classified as pending settlement.
Both processes are necessary. Tracking settlement protects cash-flow visibility, while reconciliation supports reliable accounting and exception handling.
A worked merchant example
Consider a hypothetical batch containing ₹50,000 in gross successful payments. The settlement report lists ₹1,000 in fees and related taxes and ₹3,000 in refunds deducted from that payout, with no other adjustments.
Expected net settlement = ₹50,000 − ₹1,000 − ₹3,000 = ₹46,000.
These figures illustrate the calculation only. They are not PayU pricing, a tax rate or a promise about how refunds are deducted for every account.
If the bank credit is ₹46,000, the batch may match at the total level. Your team still needs to verify that the underlying payment and refund records belong to the correct orders and settlement period.
If the credit is ₹45,500, investigate the ₹500 difference. It could represent another documented adjustment or a mismatch in the records being compared. Do not create a generic expense entry simply to force the totals to agree.
A practical reconciliation workflow
1. Keep stable identifiers
Store the order or invoice reference alongside the provider’s payment reference. Preserve refund identifiers and the settlement references that connect payments to payouts.
Names and amounts alone are weak matching keys. Two customers may pay the same amount, and one customer may place several orders in a day.
2. Confirm payment outcomes
Distinguish successful, failed and pending attempts. Multiple attempts can belong to one order, so a transaction export should not automatically be treated as a list of completed sales.
Your operational order status should reflect the verified payment outcome. Investigate cases where fulfilment records and payment records disagree.
3. Match payments to settlements
Use the provider’s settlement detail to identify which payments appear in each payout. Check transaction dates, report time zones and the cycle’s cut-off.
Do not compare all of today’s sales to today’s bank credit by default. The credit may relate to an earlier transaction period.
4. Explain every adjustment
Separate fees, applicable taxes, refunds, disputes and other documented entries. Keep their original references so another team member can follow the calculation.
A refund may be connected to a sale from an earlier period. Preserve that relationship while recording the adjustment in the period supported by your reports and accounting process.
5. Match the bank credit
Compare the net settlement amount with the bank entry using the transfer reference where available. A unique transaction reference, often called a UTR, can help connect a payout with the corresponding credit.
If an expected credit is absent, first confirm the destination account and applicable timeline. Then raise the issue with the relevant settlement reference and report details.
6. Maintain an exception queue
Assign each unresolved item an owner, reason, amount and next action. Keep timing differences separate from suspected errors.
Age the queue so old items do not disappear beneath new transactions. A small unmatched value repeated daily can become a significant operational burden.
Common differences and how to investigate
A total that differs is a starting point for investigation, not a conclusion about the cause.
| Difference | First check |
| Successful order absent from payout | Settlement eligibility, cycle and payment reference |
| Bank credit smaller than gross sales | Fees, refunds and other documented adjustments |
| Customer says paid, order says unpaid | Verified transaction outcome and order mapping |
| Two payments against one order | Retry history and duplicate collection handling |
| Refund appears in a later report | Refund reference and actual adjustment date |
Set a consistent reconciliation frequency based on volume and risk. A daily process can help teams act on exceptions promptly, but the design should also include period-end checks and a review of outstanding items.
Restrict who can change reconciled records. Keep a clear audit trail for corrections, including the evidence used and the person who approved the change.
How PayU supports payment visibility
PayU’s settlement API documentation describes settlement information that businesses can use for payment operations. Review the available reports and integration options against your own order and accounting systems.
Ask for a sample showing a payment, a refund and a settlement adjustment. Confirm which identifiers are available and whether your team can export the information it needs.
For implementation, use the current PayU documentation and confirm account-specific access and arrangements. Reporting tools can support reconciliation, but your business still needs matching rules, exception ownership and a controlled accounting process.
Frequently asked questions
Yes. Payment confirmation and merchant settlement are different stages. Check the applicable cycle and settlement report before treating the absence of an immediate bank credit as an error.
Not always. The total can match while individual orders, refunds or adjustment entries remain incorrect. Check the transaction-level relationships as well.
The payout may include documented fees, taxes, refunds or other adjustments, or it may cover a different period. Reconcile against the settlement breakdown to identify the actual reason.
Many matching steps can be automated when reliable identifiers and structured reports are available. Keep a review process for unmatched items, unusual adjustments and changes to the matching rules.
