Bank statements
Old bank statements to Excel
Turn old bank statement PDFs into reviewable Excel rows when CSV exports and bank-feed history do not go back far enough.
Why old statements end up in Excel first
When a bank feed only covers recent months or a closed account no longer offers CSV exports, the practical upstream file is the monthly statement PDF. Excel becomes the easiest place to review transaction rows, catch missing lines, and compare the extracted month against the original statement before doing anything else downstream.
What the spreadsheet should contain
For cleanup work, the useful output is one row per visible transaction with a date, readable description, and signed amount. Some teams also keep a balance or page-reference column during review, but those review columns do not need to go into a later import file.
- Date
- Description
- Amount
- Optional review fields such as balance or page number
Review month by month before importing anywhere
Historical cleanup usually goes wrong when teams merge too much at once. Start with one month, compare the row count and ending balance against the statement, fix sign direction, then move on. That keeps duplicate imports and summary-line mistakes easier to catch.
Trust and file-quality guidance
Original PDFs work best, but clear scans and phone photos can still be tested if the transaction table is readable. DocuRows does not require a bank login, and redacted files are fine as long as transaction dates, descriptions, and amounts remain visible. Review before import still applies even after the spreadsheet looks clean.
Historical statement review sheet
Date,Description,Amount,Balance,Review Note 2024-01-03,OPENING DEPOSIT,1500.00,1500.00,Matches statement opening activity 2024-01-06,ONLINE PAYMENT VENDOR,-349.20,1150.80,Check wrapped description merge 2024-01-31,BANK SERVICE CHARGE,-15.00,1135.80,Confirm fee row is not duplicated
Balance and review-note columns are useful in Excel during cleanup even if the final downstream import later uses only Date, Description, and Amount.
FAQ
Should I upload one huge archive PDF or one month at a time?
One month at a time is easier to review and reconcile. Large archive PDFs can work, but they make row-count checks and duplicate detection harder.
Can I use redacted old statements for testing?
Yes. Redacted files are fine as long as the transaction rows stay visible enough to review.
Does this mean DocuRows exports native QuickBooks files?
No. The safe current claim is reviewable spreadsheet or CSV output. Users should still review before importing into QuickBooks or any other accounting tool.
Turn a statement file into reviewable rows
Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.