QuickBooks
Import old bank statements into QuickBooks Online
How to turn old bank statement PDFs into QuickBooks-ready CSV rows when bank feeds or CSV exports do not go back far enough.
When bank feeds do not go back far enough
QuickBooks bank feeds and bank portals may only expose a limited history window. Cleanup users often end up with PDF statements for the older months they still need to reconcile.
Start month by month
For historical cleanup, one monthly statement at a time is easier to audit. It helps the user check row counts, date ranges, and duplicates before adding the next month.
- Start with one statement.
- Review transaction rows before import.
- Keep date ranges separate to reduce duplicate risk.
Use a simple QuickBooks CSV shape
The current DocuRows workflow exports reviewable CSV rows, not a native QBO file. For many cleanup jobs, Date, Description, and signed Amount are the useful first target.
Check before importing
Before using the file downstream, compare visible transactions against the CSV, confirm withdrawals are negative, deposits are positive, and remove statement summaries or balance-only rows.
Historical cleanup CSV
Date,Description,Amount 2025-01-03,OPENING DEPOSIT,1500.00 2025-01-06,ONLINE PAYMENT VENDOR,-349.20 2025-01-31,BANK SERVICE CHARGE,-15.00
For multi-month cleanup, keep each month easy to trace back to the original PDF.
FAQ
Can I process several months of statements?
Yes, but start with one month, review the output, then continue. One statement at a time is easier to reconcile and debug.
Should I upload one large PDF or separate monthly PDFs?
Separate monthly PDFs are usually easier to review. A large combined PDF may work, but it makes date-range and duplicate checks harder.
Can DocuRows create a native QBO file?
Not yet. The current product focuses on QuickBooks-ready CSV rows that can be reviewed before import.
Turn a statement file into reviewable rows
Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.