YNAB Direct Import Not Working? Convert Your Bank Statement and Import Transactions Instead

Last updated August 2026.

If YNAB has stopped pulling transactions from your bank, the fix that works today is File Based Import. Download or convert a statement into a CSV, QFX, OFX or QIF file and drag it into YNAB on the web app. That keeps the account accurate while the connection is repaired, and it is the workaround YNAB itself points to. A broken link is rarely permanent, but waiting for it does not have to mean falling behind in your plan.

Why does YNAB Direct Import stop working?

Direct Import is a chain with three links in it: your bank, an import provider, and YNAB. YNAB works with two providers, MX and Plaid, and uses whichever is currently performing better for your institution. When any part of that chain changes, most often a bank adding a security step or rebuilding its website, the connection can break.

The symptoms YNAB lists are worth memorizing, because they are how you tell a broken connection from a slow one:

• The account shows an error
• Transactions are missing
• The balance in YNAB does not match the balance at your bank

None of this is unique to YNAB. Any service that reaches into a bank account runs into the same wall, and YNAB notes that some institutions, Canadian banks and credit cards especially, are consistently harder to keep connected.

How long should I wait before assuming it is broken?

Give it three days. Direct Import is not a live feed. Most linked accounts refresh once or twice a day, and some banks limit updates further than that. Add the time it takes a transaction to move from pending to posted, and YNAB says it can take up to three days for a posted transaction to appear in your plan. New transactions typically show up within 24 to 72 hours.

So a transaction from this morning that is not in YNAB this afternoon is normal. A transaction from last Tuesday that is still missing, or a balance that is off by a known amount, is a real problem worth acting on.

What YNAB recommends while the connection is down

Two things, and they are not equivalent. Manual entry gets you immediate accuracy on a handful of transactions. File Based Import gets a whole period back in one action, which is what you want if the connection has been down for more than a day or two.

File Based Import lives on the YNAB web app, or on an iPad using Split View. It is not available on iPhone, Android or other mobile devices, so this is a job for a computer. Once you have a file, you drag it anywhere onto the YNAB page and the Import Transactions window opens by itself.

Getting a file your bank will not give you

Here is where most people stall. YNAB reads exactly four file types: CSV, QFX, OFX and QIF. Everything else returns an Invalid File warning. Plenty of banks make it easy to download one of those. Plenty of others, particularly credit unions, business accounts and smaller institutions, hand you a PDF statement and nothing more, or only let you download the last 90 days when the gap you need to fill is older than that.

A PDF statement is still usable, it just needs converting first. Upload the statement to the YNAB CSV converter and export it as CSV, QFX or OFX, then drag that file into YNAB. If you have a run of monthly statements to catch up on, they can be merged into one file before extraction so the whole gap arrives as a single import rather than six.

Which format should you send YNAB?

All four work. They do not all behave the same once a repaired connection starts importing again, which is the situation you are actually in.

The reason OFX and QFX win in this specific scenario is the overlap. When the bank connection is restored, it may deliver some of the days you just imported by hand. A file with a FITID on every transaction lets YNAB recognize what it has already seen. A CSV cannot offer that, so protection falls back to date and amount matching alone.

Will a file import create duplicates?

YNAB is reasonably good at preventing them. It automatically skips imported transactions that carry the exact same date and amount as ones already in the account, and it matches file imports against transactions you typed in yourself when the amounts are identical and the dates are within ten days of each other. That ten day window is generous on purpose, because manual entries are usually dated when you spent the money and bank files are dated when it posted.

Duplicates that do get through are almost always a date mismatch. If your converted file dates a transaction differently from the way the restored connection dates it, the two do not look identical and both stay. YNAB suggests deleting the duplicates and reconciling, because transactions dated more than three days before the last reconciled transaction stop importing altogether after that point.

One thing to be careful about before you start deleting: once you import transactions and delete them, YNAB will not let those same transactions import into that account again. If you clear out a messy import and then want it back, the documented route is to create a new unlinked account, move the surviving transactions over with Move to Account, and delete the old account.

The transactions Direct Import will never bring back

This one catches people who try to fix a broken link by unlinking and relinking the account. When you link an account, YNAB imports that day opening balance, creates a Starting Balance transaction, and does not import anything that cleared before that date. Relinking does not backfill the gap you were trying to close. It just sets a new line in the sand.

If the missing period is older than the day you linked, no amount of reconnecting will produce it. Converting the statements covering that period is the only way in. YNAB does add one caveat worth respecting: it does not recommend importing transactions more than a year old through File Based Import.

Should you keep using Direct Import at all?

For most people, yes. It is genuinely less work when it is healthy, and YNAB monitors connection quality and switches providers when one performs badly for a given bank. Direct Import is also completely optional, and there is a real case for running one or two troublesome accounts on files permanently rather than checking every week whether they synced.

The accounts worth moving to a file routine are the ones that break repeatedly, the ones no provider offers, and business accounts where you want a statement as the record anyway. A once a month conversion is more predictable than a connection that fails quietly, and quiet failure is the expensive kind: you do not notice the balance drifting until reconciliation. If catching overspending early is the point of the exercise, pairing the monthly routine with something that alerts you the moment spending crosses a threshold covers the gap between imports.

A short checklist when imports stop

1. Wait three days before treating missing transactions as a fault, since most accounts refresh only once or twice a day.
2. Compare the YNAB balance against the bank balance. A mismatch confirms it is a connection problem, not a delay.
3. Download a CSV, QFX or OFX from the bank if it offers one. Convert the PDF statement if it does not.
4. Prefer OFX or QFX, so the restored connection cannot double up the period you just imported.
5. Import on the web app, check the account name at the top of the import window, then confirm the transaction count and the first and last dates against the statement.
6. Reconcile only once the period is complete, because reconciling closes the door on anything dated more than three days earlier.

Getting the file right is most of the work. If your bank only gives you PDFs, converting the statement to OFX or to the QFX format takes a minute and leaves you with a file YNAB can check against itself. For the full picture of what YNAB does and does not accept, including the field mapping and the errors it throws, the YNAB import guide covers each case.