Payment Reconciliation

Payment reconciliation is the process of matching payments a business receives or sends with the commercial records they relate to, such as invoices, orders, bills and payroll runs, and with the bank and provider records that show the money actually moved. On the receiving side it answers "which customer paid which invoice, and how much is still owed?"; on the paying side it confirms that each approved bill was paid once, in the right amount, to the right party. It is a daily task in finance teams, e-commerce operations and any company that collects money through several channels.

Payment reconciliation sits between accounts receivable and accounts payable on one side and bank reconciliation on the other. The receiving-side step of applying cash to open invoices is known as cash application. When money arrives through card processors or wallets, it also requires settlement reconciliation, because the amount reaching the bank is net of fees and adjustments.

Picture a plumber who sends out twenty invoices a month. Customers pay in different ways: some by bank transfer with the invoice number in the reference, some by card, some in one payment for three jobs, and one who paid a bit less than the bill. At the end of the week the plumber goes through the bank account and marks each invoice "paid", "part paid" or "still open".

That sorting job is payment reconciliation. When references are clear, it is quick. When a payment arrives with no reference, or one transfer covers several bills, it becomes detective work, and until it is done the business cannot be sure who still owes it money.

Matching uses the same techniques as transaction reconciliation, applied to commercial documents:

• Reference match. The invoice number or customer number in the payment's remittance information identifies the invoice.
• Account-based match. Each customer pays into its own virtual account or virtual IBAN, so the receiving account identifies the payer even without a reference.
• Amount and payer match. The amount and the payer's name or account are compared with open invoices.
• Remittance advice. A separate message or email lists which invoices a payment covers, which is common for large business customers paying many invoices at once.

Hard cases include short payments (a customer deducts a disputed amount), overpayments, combined payments, payments net of withholding tax and foreign-currency payments where the amount received differs because of the exchange rate and bank charges. Structured remittance fields in ISO 20022 payment messages, which can carry invoice references in a machine-readable form, are designed to reduce these problems.

Card processors, wallets and marketplaces usually pay merchants one net amount covering many sales. To reconcile, the business rebuilds that figure from the provider's report:

• $P_{\text{net}}$ is the payout deposited in the bank.
• $S$ is gross sales settled in the period, $R$ is refunds and $CB$ is chargebacks.
• $F$ is fees, such as the merchant discount rate or processor charges.
• $H$ is the change in any reserve or hold the provider keeps.

Worked example: 20,000 of sales, 600 of refunds, 200 of chargebacks, 580 of fees and a 1,000 increase in reserve give a payout of 20,000 − 600 − 200 − 580 − 1,000 = 17,620. The business books gross sales as revenue, fees as an expense and the reserve as a receivable, rather than recording only the 17,620 that arrived. Treating the net deposit as revenue understates both sales and costs.

On the paying side, the finance team matches each payment in a bulk payment file or each individual transfer with the approved bill, then with the bank's confirmation or rejection. Rejected and returned payments are reopened; duplicates are recovered. This step is an important defence against payment diversion fraud, where a criminal changes a supplier's bank details, because it checks that the beneficiary account matches the verified supplier record. Payroll teams do the same for salary disbursements.

Businesses import bank statements, processor reports and payment notifications into an ERP or accounts-receivable software that proposes matches and leaves exceptions for staff. Instant payment systems such as FedNow, UPI and Pix send confirmations within seconds, so reconciliation can move from a daily batch to near real time. Faster reconciliation improves cash forecasting, shortens collection follow-up and lowers working capital tied up in receivables. Where money passes through several intermediaries, the full path is traced with multi-step reconciliation.

• ISO 20022 (official site)
• Nacha: Operating Rules