YNAB cannot read a PDF, and Direct Import only reaches banks that offer a live connection. Upload your statement PDF and BankXLSX gives you a QFX, OFX, or CSV file built for YNAB File-Based Import, with the Date, Payee, Memo, Outflow and Inflow columns already in the shape YNAB wants. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
YNAB File-Based Import accepts QFX, OFX, QIF, and CSV. A PDF is none of those, and even when your bank exports a raw CSV, it rarely lines up with the exact columns YNAB reads. These are the snags that stop an import.
File-Based Import reads QFX, OFX, QIF, and CSV only. A statement PDF has to be converted into one of those formats before YNAB will touch it.
Direct Import pulls only from banks with a supported connection. Small banks, older periods, and accounts you would rather not link all fall back to a file, which means you need one.
YNAB expects the first row to be Date, Payee, Memo, Outflow, Inflow or Date, Payee, Memo, Amount. A bank CSV with different headers, split rows, or a running balance column will not import cleanly.
In the five column layout the money leaving goes in Outflow and money arriving goes in Inflow, both as positive numbers. A single signed amount column has to use negatives for spending, and banks are inconsistent about which they give you.
Statements print dates as MM/DD/YYYY, DD/MM/YYYY, or a written month. If the order is ambiguous YNAB stops to ask, and a messy file makes that guess wrong.
YNAB suggests not importing entries more than a year old and skips exact date and amount duplicates, so a clean, correctly dated file matters more than people expect.
Upload the statement PDF and the converter reads every transaction, then writes it into the format YNAB imports without a fight.
YNAB names QFX and OFX as its top import formats. Export to either and YNAB reads the payee, date, and amount directly, with the least manual cleanup.
Choose CSV and you get Date, Payee, Memo, Outflow, Inflow as the first row, so the file loads without renaming a single header.
Spending lands in Outflow and deposits land in Inflow as positive numbers, exactly how YNAB reads the five column format.
Every transaction date is normalized so YNAB does not stop to ask which number is the day and which is the month.
Convert several monthly PDFs and combine them into one file so your YNAB budget starts with real history instead of one month.
Statements carry account numbers. Uploads use 256-bit encryption and you can delete your files whenever you want.
Nothing to install and no credit card to start.
Drag your bank or credit card statement PDF into the box above. Multiple monthly statements are fine in one go.
Tip: Scanned PDFs work too.
Choose QFX or OFX for the smoothest import, or CSV if you want to eyeball the rows first. The columns are already YNAB ready.
Tip: QFX is the least fuss.
In the YNAB web app open the account, click the import icon, and upload the file. Review the matched transactions and approve them.
Tip: File import runs on web and iPad.
YNAB is a paid budgeting app with a loyal base of people who track every dollar. The ones reaching for a converter usually bank somewhere Direct Import does not cover, or they are backfilling history.
Your credit union or small bank has no live connection, so every month is a manual file. Convert the PDF once and import it.
Starting YNAB mid year and want prior months in the budget. Convert several statement PDFs and import the full stretch at once.
You would rather not link accounts through a data aggregator, so you download statements and import files by hand.
A business checking account that YNAB will not connect to still needs to sit in the budget, and a converted file gets it there.
No. YNAB File-Based Import accepts four file types, QFX, OFX, QIF, and CSV, and a PDF is not one of them. YNAB Direct Import can bring transactions in automatically, but only from banks that offer a supported connection, so anything outside that list still needs a file. The fix is to convert the statement PDF into a format YNAB reads, and QFX or OFX give the cleanest result because YNAB names them as its top recommendations.
If you go the CSV route, the header row has to match one of two layouts exactly, or YNAB will not map the columns. This is the single most common reason a hand made CSV fails to import.
| Layout | Header row | How amounts work |
|---|---|---|
| Five column | Date, Payee, Memo, Outflow, Inflow | Money spent goes in Outflow, money received in Inflow, both as positive numbers, and the unused column is left blank. |
| Four column | Date, Payee, Memo, Amount | One signed column: outflows are negative like -100.00 and inflows are positive like 500.00. |
Every field except the date can be blank, and the date can be written in different orders as long as it is consistent. YNAB will confirm the day, month, year order during import if it looks ambiguous. BankXLSX writes the five column layout by default, so the file is ready as soon as it downloads.
A QFX or OFX file carries the transaction structure inside it, so YNAB reads the date, payee, and amount without you mapping anything. YNAB says as much, listing QFX and OFX first and suggesting CSV only when those formats are not available. There is one thing no bank file carries reliably, and that is your categories, so YNAB does not assign categories on import regardless of format. You categorize after the transactions land, which is the normal YNAB flow anyway.
File-Based Import runs in the YNAB web app and on iPad in Split View, not on iPhone or Android. Open the account you want, click the file import icon, and choose your converted QFX, OFX, or CSV. YNAB automatically skips any transaction that exactly matches the date and amount of one already there, so re-importing an overlapping month will not create duplicates. As a rule of thumb YNAB suggests not importing transactions more than a year old, so for a big backfill, focus on the window your budget actually needs.
Once the file is in, the transactions behave like any others: assign each to a category, split where needed, and reconcile against the statement balance. If you also keep books in accounting software, the same converted data works there too. Point the export at the Quicken bank statement converter for a QFX Quicken reads, the bank statement OFX converter for a plain OFX, or the bank statement QIF converter if a tool needs QIF. To pull months together first, use combine bank statements in Excel, and the general bank statement converter handles the initial PDF for any of these paths. If you want to see the raw rows before importing, the step by step CSV for YNAB walkthrough covers it.
YNAB is a budget, not a bookkeeping ledger, so many people run both. If the same spending needs to reach QuickBooks Online, convert the file to an importable QBO with a CSV to QBO converter. And if you are watching business spend rather than a personal budget, software that reads receipts and flags every charge through expense management picks up where a budget app stops.
No. YNAB File-Based Import accepts QFX, OFX, QIF, and CSV files, and a PDF is not one of them. Direct Import can pull transactions automatically but only from banks with a supported connection. To get a PDF statement into YNAB you convert it to QFX, OFX, or CSV first, then upload that file.
YNAB reads two layouts. The five column header is Date, Payee, Memo, Outflow, Inflow, with spending in Outflow and deposits in Inflow as positive numbers. The four column header is Date, Payee, Memo, Amount, using one signed column where outflows are negative. The header must be the first row and match exactly.
QFX or OFX give the smoothest import because they carry the transaction structure, and YNAB lists them as its top recommendations. CSV works well when you want to review the rows first. BankXLSX can export all three, so you can pick QFX for speed or CSV for a quick sanity check.
Usually the header row does not match. YNAB needs Date, Payee, Memo, Outflow, Inflow or Date, Payee, Memo, Amount as the exact first line, with no running balance column and no split rows. A converted file uses the right headers from the start, so the import maps every column without editing.
No, and neither does any import into YNAB. Bank files do not carry your budget categories, so YNAB never assigns categories during import regardless of the format. You categorize the transactions in YNAB after they land, which is the standard budgeting workflow.
File-Based Import runs in the YNAB web app and on iPad in Split View. Open the account, click the file import icon, and choose your converted QFX, OFX, or CSV. YNAB matches the transactions and skips any that exactly duplicate a date and amount already in the account.
Yes. Convert each monthly PDF and combine them into a single file, then import that. YNAB suggests keeping to transactions less than about a year old, so for a large backfill focus on the period your budget needs. Duplicate protection means an overlapping month will not double up.
Bank statements contain account numbers, so treat them carefully. BankXLSX encrypts uploads with 256-bit encryption, never resells or shares your financial data, and lets you delete uploaded files at any time. The conversion runs in your browser session rather than being posted publicly.
Import into GnuCash from CSV or OFX.
Export a plain OFX for any budgeting app.
Convert to QIF when a tool needs it.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
