CSV Reconciliation Without a Bank Feed
Compare bank CSV/XLSX files with invoices, orders, payouts or processor activity when a direct bank feed is unavailable or unnecessary.
Try with sample files | View sample report
Problem statement
Not every bank has a reliable connector, and an occasional review may not justify setting one up. The practical requirement is a consistent bank export and a source file that explains the cash rows.
Minimum file set
| Line item | Amount |
|---|
| Bank file | March statement CSV |
| Source file | March invoices XLSX |
| Bank feed | Not used |
| Clear matches | Separated from review rows |
| Unknown deposits | Kept open for follow-up |
When an export is enough
- A monthly or one-off review does not need continuous balance synchronization.
- CSV/XLSX exports work across regional banks and legacy portals.
- The reviewer can limit the file to the account and period in scope.
- A structured review report is less fragile than more lookup formulas.
Files and columns to prepare
- Bank CSV/XLSX with transaction date, signed amount, description, currency, and reference.
- Order or invoice export with ID, expected amount, date, customer, currency, and payment status.
- Payout or activity file when the bank receives a net processor payout.
CSV-to-report workflow
- Export the same period from the bank and source system.
- Check delimiters, decimal signs, dates, currencies, and amount direction.
- Map stable date, amount, and reference columns.
- Review matches separately from duplicates, unknown rows, and amount differences.
- Export the report and carry unresolved items forward explicitly.
Import checks
- Do not mix accounts or currencies without a separation rule.
- Confirm how debit and credit direction is represented.
- Remove non-transaction balance and summary rows.
- Do not match gross orders directly to a net payout deposit.
How Reconcile Locally helps
- Accepts exported files without requiring a supported connector.
- Normalizes common CSV/XLSX structures and keeps mappings visible.
- Separates matched rows from open exceptions in the report.
What still needs manual review
- The review only sees the rows included in the exports.
- Poor references, grouped settlements, and incomplete processor files can require manual confirmation.
Do not want to connect a bank account?
Compare a browser-local exported-file workflow with a typical connected reconciliation tool.
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
Can I reconcile a bank CSV without connecting the bank?
Yes. Export the bank period as CSV/XLSX and compare it with the relevant invoice, order, payout, or activity export.
What if the CSV has separate debit and credit columns?
Normalize those columns into one signed amount before matching so every row keeps the correct direction.
When is a bank feed better?
A bank feed may be better when continuous sync saves more work than periodic export and review.