Runs entirely in your browser — your file is never uploaded to a server.
Drop your file below — runs entirely in your browser, nothing is uploaded.
A QIF file means your bank gave you structured data — which most banks only do for the last few months. Beyond that you get a PDF, and a PDF won't open in Excel. BalanceExtract reads those directly: it works out the column layout from the document itself, handles scanned statements with OCR, checks that every running balance reconciles, and flags any row it isn't confident about before you export.
Same CSV output, same on-device processing, nothing uploaded.
Drag the file onto the box above or click to browse. It is read in your browser — nothing is uploaded to a server, which you can confirm in the Network tab.
Every transaction is read out with its date, payee, description, amount and transaction ID, along with any warnings about rows that need a look.
The CSV file saves straight to your device, ready to open in a spreadsheet or import into your accounting software.
QIF is a plain-text, line-based format where each transaction is a short run of prefixed lines. This guide covers what's actually in the file and a real date-format quirk worth knowing about before it silently breaks a naive parser.
Auditing old Quicken records or moving them into a spreadsheet without retyping every line means reading the QIF file's own real quirks correctly first. QIF files use single-letter field codes (D for date, T for amount, P for payee, M for memo) with each record ending in a bare "^". A real quirk: Quicken's own apostrophe-year date shorthand (1/15'26) trips up parsers that only expect slash-separated dates — this converter handles both.
| Field code | What It Contains |
|---|---|
| D | Transaction date — including the apostrophe-year shorthand (1/15'26) |
| T | Amount |
| P | Payee |
| M | Memo |
Honest side-by-side write-ups, including where each of them is the better choice.