Export the bank statement as CSV and the invoice or payment list as CSV. Check that both cover the same dates, and that both use one currency. Dates like 03/04/2026 mean different days in different countries, so confirm the order for each file.
The amount must agree. The date should be close, because a payment usually lands a few days after the invoice. A shared reference such as an invoice number is the strongest sign and can justify a longer gap.
Two payments of the same amount on the same day can swap partners without anyone noticing. Pair them one to one and look at them yourself.
Payment processors often pay out several sales in one deposit. When one bank row equals the sum of a few ledger rows, group them and confirm the grouping.
A payment with the right reference but a different amount is not a match. List it with the difference so you can decide whether it is a part payment, a fee or a mistake.
After matching, the bank total minus the ledger total should equal the unmatched bank total minus the unmatched ledger total, plus any difference left in tolerance matches. If it does not, a row has been counted twice or dropped.
The Bank Reconciliation Matcher pairs a bank CSV with an invoice or ledger CSV, groups batch deposits, lists unmatched rows on each side and downloads an Excel workbook. Files stay on your device. The free version reads the first 150 rows of each file.
Open the free Reconciliation MatcherNo row cap and offline use: the one-time $19 offline pack is here: https://xargaartools.gumroad.com/l/bank-reconciliation-matcher-offline-pack
It pairs rows you give it. A match is a suggestion for you to confirm, not accounting advice.