CSV Bank Reconciliation - Reconcile Bank Exports with Orders and Invoices
Match bank CSV exports with orders, invoices and payment records. Find discrepancies and export reconciliation reports locally.
Try with sample files | View sample report
Problem statement
Bank CSV reconciliation gets messy when exported rows use inconsistent date formats, unclear references, and mixed deposits that do not line up one-to-one with invoices or payout rows.
Numeric example
| Line item | Amount |
|---|
| Invoice group expected | $2,040.00 |
| Bank CSV deposit | $1,982.50 |
| Open amount difference | -$57.50 |
| Unpaid source rows | $240.00 |
Why the numbers do not match
- Bank exports often hide the useful reference inside a longer free-text description.
- One bank deposit can cover several invoices, orders, or payout rows.
- Date formats and signed amounts vary between banks and source systems.
- Manual spreadsheet filters can hide unresolved rows instead of separating them.
What files to export
- Bank CSV/XLSX with raw descriptions, references, dates, and signed amounts.
- Supporting order, invoice, or payout export with expected amount and reference fields.
- Optional prior-period file when timing gaps or delayed deposits are common.
Manual workflow
- Normalize the bank CSV date and amount columns first.
- Extract likely references from the bank description.
- Match exact references before using amount or date-only rules.
- Keep grouped deposits in review until the related source rows are visible together.
- Export matched rows first, review rows next, and unresolved bank rows separately.
Common mistakes
- Treating bank descriptions as clean references without normalization.
- Using amount-only matches as final support in repeated-value datasets.
- Combining unresolved bank rows with matched rows in one output table.
- Ignoring late deposits that belong to the next or previous file period.
How Reconcile Locally helps
- Highlights matched rows, needs-review rows, unknown bank payments, and unpaid source rows in one review flow.
- Preserves the raw bank description and source-row context for later audit.
- Exports a report that keeps unresolved bank rows visible instead of burying them in formulas.
What still needs manual review
- Grouped deposits and repeated-value bank rows still need reviewer confirmation.
- Weak-reference matches should stay open until another source row proves the explanation.
- Mixed-currency or tax-adjusted deposits may need another export before the difference is final.
Content review and sources
Written and reviewed by the Reconcile Locally product team. Last reviewed June 7, 2026.
Guidance is checked against current product behavior and first-party documentation where available. Reconciliation results still require human review.
Frequently asked questions
What makes CSV bank reconciliation hard?
Exported bank files often mix unclear references, inconsistent date formats, and grouped deposits that do not map one-to-one to source rows.
Should unmatched bank rows stay visible?
Yes. Unknown bank payments should remain visible in the final report until a reviewer confirms their source or classification.