Payment reconciliation process from sale to bank deposit
The payment reconciliation process confirms that every payment you expected was actually received, in the right amount, and recorded correctly. It ties three records together: the invoice or order, the processor or remittance record, and the bank deposit, then explains every fee, refund, partial payment and timing gap between them.
What payment reconciliation covers
Bank reconciliation asks whether the ledger agrees with the bank. Payment reconciliation asks a more detailed question: did each customer pay what they owed, and did that money arrive? For a business that invoices a handful of clients by wire transfer, the two are almost the same task. For a business that sells through card processors, wallets and marketplaces, they are very different, because money arrives in batches, net of fees, days after the sale.
That gap is where revenue leaks. A refund booked twice, a chargeback nobody recorded or a fee booked as negative revenue all distort the numbers quietly. A defined payment reconciliation process catches them every period instead of once a year during the audit.
The three records every payment touches
Every payment passes through three systems, and each one describes it differently.
- The source document: an invoice in your accounting system, or an order in your store. It holds the gross amount the customer owes.
- The payment record: the processor transaction, the remittance advice or the PayPal activity line. It holds the gross charge, the fee and the payout it belongs to.
- The bank deposit: one line on the statement, usually a payout that combines many payments, minus fees and refunds.
Reconciliation means linking all three for every payment, not just matching the bank line to a total. When you can trace a single order from the invoice to the deposit, you can also explain any difference at the deposit level.
Payment reconciliation steps that work every period
Decide the frequency before you decide the method. High volume sellers reconcile payouts daily or weekly, because a problem found on Tuesday is easy to trace and a problem found four weeks later is not. Invoice businesses with a few dozen payments a month can reconcile weekly and do a full review at month end.
The order of work matters, because each step narrows what the next one has to explain.
- Collect the files for the period: open invoices or orders, the processor transaction or payout report, and the bank statement.
- Match payments to invoices or orders first, using reference, invoice number and amount. Flag partial payments and overpayments.
- Group processor transactions by payout. Each payout should equal its charges minus refunds, fees and any adjustments.
- Match each payout total to the deposit on the bank statement, allowing for the settlement delay of your processor.
- Book the fees, refunds, chargebacks and reserves as separate entries, not netted against revenue.
- Review what is left: payments without an invoice, invoices without a payment, and payouts without a deposit.
This sequence is what transaction matching automates. Done by hand, step three is usually the slowest, because one payout can contain hundreds of charges.
Write the process down once, including which reports to pull, which accounts fees and refunds go to and who reviews the result. A documented process survives holidays and staff changes, and it is the first thing an auditor asks for when they test your revenue cycle.
A worked illustration of a batched payout
As an illustration, say your processor deposits $9,640 on Tuesday. The payout report shows 112 charges totaling $10,180, two refunds of $120 and $60, and fees of $360. Charges minus refunds minus fees gives $9,640, so the payout agrees with the deposit.
Now check the other direction. Of the 112 charges, 109 match orders in your store by order ID. Two charges have no order, which usually means a manual invoice was paid by card link. One order shows as paid in your store but has no charge, which may be a payment that failed after checkout. Those three lines are your exceptions. The other 109 are reconciled, and the fees and refunds are ready to book.
Notice that the bank line alone told you nothing about those three exceptions. Reconciling only at the deposit level would have shown a perfect match while a customer went uncharged.
The same check works for invoice businesses. As an illustration, a wire of $7,500 arrives with the reference of one invoice for $5,000. Searching open invoices for the same customer finds a second invoice of $2,500, so the wire pays both. Without that search, the payment would sit as an overpayment on one invoice while the other stayed overdue and triggered a reminder to a customer who already paid.
Where the payment reconciliation process breaks
A few patterns cause most of the trouble, and each one has a fix.
- Net deposits: the bank shows the payout after fees. Fix it by reconciling gross charges and fees separately, then the net.
- Settlement delays: a sale on the 30th lands in the bank on the 2nd. Use a date window, and carry the payout as in transit at month end.
- Partial and combined payments: one wire pays three invoices, or one invoice is paid in two parts. Match one to many and many to one, then record the remaining balance.
- Currency conversion: a payout in a different currency than the order. Record the conversion difference as its own line.
- Chargebacks and reserves: money withheld from a payout. Book it to a receivable or reserve account, not as a reduction of sales.
If these keep producing leftovers every month, our article on reconciliation discrepancies goes through how to trace each type.
Small, recurring differences deserve the same attention as large ones. A few cents per payout across thousands of payouts adds up, and it usually points to a rounding rule or a currency setting that is easy to fix once someone looks at it.
Processor and marketplace specifics
Each source has its own report and its own quirks. Stripe payouts batch charges minus fees and refunds, and the payout reconciliation report lists each transaction per payout; our guide to the Stripe payout reconciliation report walks through it. PayPal keeps its own balance, so the activity report and the transfers to your bank are two separate reconciliations, covered on the PayPal reconciliation page. Amazon settlement reports list orders, fees, refunds and reserves for each settlement period, explained on the Amazon settlement reconciliation page. For Shopify Payments payouts, see Shopify payout reconciliation.
For invoice-based businesses, the same process applies to remittances instead of payouts. The cash application software page shows how incoming payments are applied to open invoices when a remittance covers several of them.
Automating the process without losing control
Automation should do the matching and leave the judgment to people. Reconciles reads the invoice export, the processor report and the bank statement, splits each payout into its charges, refunds and fees, and matches all three layers. Each match carries a plain-language reason and a confidence score. Whatever does not match goes to an exceptions queue sorted into unmatched, partial, duplicate, amount difference and date difference.
Nothing posts to your ledger without review. Once the exceptions are cleared, fees and refunds go back to your books as journal entries in a file your accounting system accepts. You can read more on how automated reconciliation works.