Free converter
Bank statement converter for YNAB
Backfill YNAB with months of history from any statement, without hand-typing.
Choose a statement file (PDF, OFX/QFX, CSV, XLSX, TXT — up to 5 MB)
Why YNAB users end up here
YNAB's direct import handles the future; the problem is the past. Starting YNAB mid-year, adding an account YNAB can't link, or reconstructing a stretch where the link was broken all mean file-based import — and YNAB accepts CSV and QIF for exactly this. The catch YNAB users know well: file imports must be shaped right (date, payee, amount) and deduplicated against what direct import already pulled, or your budget double-counts. Converting here gets you a clean, merchant-identified file that maps onto YNAB's importer without spreadsheet surgery.
Importing into YNAB, step by step
- Convert your statement above and download the CSV (QIF also works if you prefer).
- In YNAB: select the account → Import (the file icon next to the account name).
- Choose the file. YNAB detects columns; confirm date format and the amount column when asked.
- Approve the imported transactions — they land as unapproved so nothing enters the budget silently.
The gotchas YNAB users actually hit
Overlap with direct import creates duplicates
If the account is linked, YNAB matches file transactions against imported ones — but near-misses (different payee text, off-by-a-day dates) slip through. Import history from BEFORE the link's start date and let direct import own everything after.
YNAB wants one amount convention
Outflows negative, inflows positive in a single column — which is how our CSV is written. Files with separate debit/credit columns need combining first (or just use ours).
Payee names drive YNAB's automation
YNAB learns category rules per payee. Importing raw descriptors ("SQ *BLU BTL 0412") pollutes that learning; importing identified merchants ("Blue Bottle Coffee") makes the rules stick.
Free converter
Convert your statement — and understand it too
A free account converts a statement page every day to CSV, Excel, QIF or OFX — with every transaction matched to a real merchant name, not a cryptic descriptor. No card required; files deleted after 24 hours.
No bank logins · card numbers redacted before storage · everything deleted after 24 hours
Frequently asked questions
Can YNAB import a PDF statement?
Not directly — YNAB takes CSV, QIF, OFX and QFX files. Convert the PDF here first; scanned PDFs work too, with every date and amount re-validated after extraction.
How far back should I import?
YNAB's own advice is to not drown a new budget in history — a month or two is plenty for budgeting. Import more only if you want the reports, and dedupe carefully around the link date.
Why are my imported transactions unapproved?
By design: YNAB stages file imports for review. Approve them as you categorise — with identified merchant names, that pass is quick.