How to check that converted bank transactions are complete and correct

Updated 2026-10-10

Whatever tool you use to extract transactions from statements, verify the output before it reaches your accounting system. Fixing a missing row now takes seconds; finding it during year-end reconciliation takes hours.

1. Reconcile to the statement balances

Opening balance + sum of all transactions must equal the closing balance (for card statements: previous balance − payments + purchases = new balance). LocalLedger does this automatically for every file and shows ✓ balances reconcile or the exact difference.

2. Compare totals

Most statements print total money in and total money out. Compare them with the Money in and Money out figures above the LocalLedger table.

3. Look at the signs

Rows without a +/− marker in the statement are highlighted. A reversed sign is the most common extraction error and it breaks reconciliation by exactly twice the amount — a useful hint when the difference is not zero.

4. Check the date range and year

Statements that print dates without a year (12/28) and span December–January need the right year on each side. Sort by date and look at the first and last rows.

5. Remove overlaps

If you combine consecutive statements or a statement and a CSV export, use Remove duplicates and make sure you only import periods your accounting system does not already have.

Try it with your own statement. LocalLedger reads the PDF or CSV in your browser, shows every transaction for review and checks the totals against the statement balances.

Convert your statement now — free preview, nothing uploaded