Reviewed: 28 October 2026.
The best way to get transactions into YNAB depends on what is getting in your way. If you have a handful of purchases to record, a file upload may be perfectly adequate. If you repeatedly download statements just to keep the same account current, a bank feed may be worth setting up.
For UK, EU and Australian users, the decision starts with coverage. YNAB already connects to selected UK and European banks. Its published Direct Import regions do not include Australia. BankSync offers a separate YNAB destination for supported accounts, subject to early access.
This guide compares the routes so you can keep the budgeting workflow you like and choose a sensible way to supply its transactions.
Compare the three import routes
The table separates how records arrive from what you still do after they arrive. Whichever route you choose, check the account register and review your categories.
File import, Direct Import or BankSync?
| Feature | YNAB file import | YNAB Direct Import | BankSync feed |
|---|---|---|---|
| How records arrive | Download a bank file and upload it to YNAB | Link a supported account within YNAB | Connect your bank in BankSync and match a YNAB account |
| Main eligibility check | Your bank provides a supported export format | Exact bank and account appear in YNAB | Bank account supported; YNAB enabled for your workspace |
| Ongoing work | Repeat exports and uploads, then review | Review imports and maintain the connection | Review imports, feed status and connection access |
| Starting point | Choose the export range and review overlap | Follow YNAB’s linked-account setup | Today by default; optional available history |
| Currency conversion | Prepare records appropriate for the destination plan | Check the account and plan setup in YNAB | None; a different-currency account is Not sent |
When a CSV import is enough
File import suits someone who wants to update a small register occasionally and is comfortable choosing the export dates. It is also useful when a bank has no suitable live connection.
YNAB's file-import guide currently recommends CSV and also accepts OFX, QFX and QIF. On a computer, download the bank export, bring it into YNAB and check the destination account and import options. For CSV, verify the mapped fields and the direction of inflows and outflows.
A sensible review checks one recognisable debit and one credit before trusting a larger batch. If a salary appears as spending or a purchase appears as income, investigate the file mapping rather than trying to compensate by changing categories.
File import is still a recurring task. If it works comfortably for you, there is no need to replace it. If exports keep piling up, the effort of a connected feed may pay off in a simpler routine.
When to use YNAB Direct Import
If YNAB already connects to the account and imports reliably, use that as your starting point. A second service is not necessary simply because another connection route exists.
A missing institution, a missing account within an institution and a temporary outage are different problems. Check YNAB's bank-search guidance and current connection status before deciding there is a coverage gap.
Native Direct Import is not instant. YNAB's explanation of Direct Import describes source refreshes and delays. A newly made purchase is not a good test of whether a connection is working; compare posted records instead.
When a BankSync feed is useful
Consider BankSync when it supports your exact account, YNAB access is enabled and removing repeated file uploads would improve your routine.
The setup is account-based: select YNAB in a feed's Destination tab, authorise access through the popup, choose a plan and match bank accounts in Mapping. There is no spreadsheet field-mapping stage for this destination.
BankSync sends posted entries for you to review in YNAB. It does not choose your budget priorities, convert currencies or automatically link both sides of a transfer. Those boundaries make it easier to decide whether the integration fits your needs.
What changes by region?
Australia: Check the bank through BankSync's Australian institution search and CDR connection flow. When you select YNAB for CDR-connected data, review the recipient disclosure before approving access. An AUD account needs an AUD plan.
United Kingdom: Check YNAB's existing coverage first. If a connection is missing, distinguish personal and business banking entities and confirm the account that BankSync actually returns. Match GBP accounts to a GBP plan.
European Union: Country and local banking entity matter. A bank group operating in several countries may have different connections in each. Account currency also matters: an EU account is not necessarily denominated in euros.
For the bank-connection details, read our Australian YNAB guide, UK bank-sync guide or European coverage guide.
Choose one route for each account
You can make different choices for different YNAB accounts. The mistake is feeding overlapping records into the same account through independent import methods.
BankSync's documentation says not to combine its imports with YNAB Direct Import or File Import on the same destination account. If you move to BankSync, agree a clear handover point, stop the previous route and review the first batch.
For an existing YNAB account, preserve and check the register you already have. Starting a new connection should not become an excuse to recreate accounts or rewrite balances without understanding the difference.
Frequently asked questions
Make the decision with one account
Pick the account that causes the most import work. Check coverage, confirm the plan currency and compare the recurring effort. If BankSync fits, use the switching checklist to make the first import deliberate.
BankSync is independent of YNAB and is not affiliated with or endorsed by YNAB. Setup details follow the BankSync YNAB documentation.