Bank Statement Reconciliation Hub
Start from the bank row and branch into CSV, invoice, reference-matching, or spreadsheet review workflows.
Start from the bank row and branch into CSV, invoice, reference-matching, or spreadsheet workflows. This hub is for teams that need to explain the bank statement before they post or approve accounting entries.
Bank statement reconciliation is about matching each bank row to supporting source data such as invoices, orders, payouts, or other exported records. The bank statement is the source of truth for cash movement, but not always for business context.
Try with sample files | View sample report
What this hub helps you review
- CSV and XLSX bank exports can use either one signed amount column or separate debit and credit columns.
- Date formats, descriptions, and extracted references often matter as much as the raw amount.
- Invoice and order matching can still leave unpaid items, partial payments, duplicate candidates, and unknown bank rows.
- A lower bank amount may only prove an amount difference until another export confirms the exact cause.
- Review output should keep matched rows, review rows, unpaid rows, and unresolved bank items separate.
Common bank export signals
| Line item | Amount or note |
|---|
| Signed amount column | One field with deposits positive and withdrawals negative. |
| Debit-credit columns | Two fields that need to be normalized before matching. |
| Reference-rich description | Description contains invoice ID, payout ID, or customer note. |
| Unknown deposit | No clear supporting source row found yet. |
What files to export
- Bank statement CSV/XLSX with dates, descriptions, references, signed amounts or debit-credit columns, and the final cash movement.
- Orders or invoices export with expected amounts, dates, customer references, invoice IDs, or order IDs.
- Optional payout or processor export when the bank row is a payout-level deposit rather than a one-to-one customer payment.
Manual workflow
- Normalize the bank export into stable date and amount fields.
- Extract references from descriptions before relying on amount-only comparisons.
- Match exact references first, then use amount and date review rules.
- Keep unknown bank rows, unpaid items, duplicates, and amount differences visible instead of forcing a match.
- Export a final report with matched rows first, review rows next, and unresolved rows clearly separated.
How Reconcile Locally helps
- Works from exported files without requiring a bank connection.
- Separates matched, review, unpaid, duplicate, and unknown bank rows in one report layout.
- Keeps source-row context visible when several references or dates are plausible.
- Supports payout-driven bank rows as well as invoice and order matching workflows.
What still needs manual review
- Truncated bank descriptions can still require a human to confirm the final source row.
- Grouped deposits and amount-only candidates should stay in review until the evidence is stronger.
- Exact accounting classification is outside the scope of bank-row matching and may require another workflow.
Start from the bank export
Use these pages when the bank statement is the source of truth and the supporting file is still unclear.
Spreadsheet and local review workflows
Use these when the bank explanation still lives in exported files and manual review is required.
Related hubs and proof pages
Use these when the bank row is really a payout workflow or when you want the wider guide catalog.