Reviewed: 28 October 2026.
Changing how transactions reach YNAB should not mean rebuilding your plan. The key is to preserve the register you trust, stop the old import route and make the first BankSync import easy to inspect.
A duplicate often starts with overlap: the same real-world purchase arrives from a file, a native bank connection and a separate feed. Choosing a clear handover point is more useful than repeatedly importing and hoping the app will sort it out.
The process below follows the BankSync YNAB setup guide. It applies to supported UK, European and Australian accounts once YNAB is enabled in your BankSync workspace.
Understand what duplicate protection covers
BankSync gives imported transactions stable import IDs. Repeating a BankSync sync therefore does not create another copy of the same BankSync import.
That is different from recognising a transaction imported by another method. BankSync's documented rule is to use one import method per YNAB account: do not combine its feed with Direct Import or File Import on that account.
Two entries with the same amount are not automatically duplicates. They may be separate purchases, or the opposite sides of a transfer in different account registers. Compare the bank record, date, payee, account and origin before changing anything.
Prepare the account you already use
Review your current YNAB register against the bank. Note the most recent records already included and the balance you are expecting. Keep a record of the previous setup so that a later discrepancy has context.
For an existing account, use BankSync's option to map to that account. Creating a second account for the same bank can leave you with two registers representing one real balance.
BankSync does not replace the balance of an existing YNAB account. For an account it creates, the first sync adds a Starting Balance transaction. These are different setup paths, so choose intentionally.
A careful handover, one account at a time
Confirm the new route
Connect the bank in BankSync and confirm the expected account appears. Check that YNAB is available in Destination before changing the old setup.
Review the existing register
Identify transactions already present, including any entered today. Check the balance and note the last completed import.
Stop the previous import method
Unlink YNAB Direct Import on the account if it is in use. Stop overlapping file uploads to that same account.
Authorise the destination
In the BankSync feed, select YNAB, approve access in the popup and choose the plan. For Australian CDR data, review the recipient disclosure.
Map the account and check currency
Select the intended existing YNAB account. Confirm the plan uses the bank account’s currency; choose Don’t send for any account you do not want included.
Start with Today
Use the default starting option unless you deliberately need history. Check the handover day for transactions the previous method already delivered.
Review the first import
Compare known posted entries, the account balance and any transfers. Categorise and approve the records in YNAB before expanding to more accounts.
Work through the handover day
Suppose you import a CSV in the morning and set up BankSync that afternoon. Selecting Today does not mean the morning's records disappear from the bank's transaction history. Inspect that day's entries after the first sync.
The same idea applies when moving from Direct Import. The important question is which records are already in the register, not simply which date you clicked the new connection button.
If you need earlier records, the setup offers 7, 30 or 90 days, subject to bank availability. Do not use a large historical import as the first test of a new connection. Earlier entries can require review in past YNAB months and make a simple handover harder to understand.
Keep each real account mapped deliberately
| Illustrative bank account | Destination | Check before syncing |
|---|---|---|
| Australian everyday account in AUD | Existing account in an AUD plan | Correct CDR account selected |
| UK current account in GBP | Existing account in a GBP plan | Direct Import unlinked on this account |
| European account in EUR | Existing account in a EUR plan | Correct country and banking entity |
| Account you do not want in YNAB | Don’t send | Excluded deliberately rather than left unmapped |
Review transfers and credit cards separately
A transfer between two connected banks arrives as two transactions, one in each YNAB account. BankSync does not link the pair as a YNAB transfer. Review it as a transfer workflow rather than deleting a legitimate side as a duplicate.
If you create a credit card account, check its type before creation. BankSync's guide also calls out the Credit Card Payment category and the existing card balance. Follow the documented setup and your plan's actual circumstances before considering the card ready.
Different-currency accounts need matching-currency plans. Routing a euro account to a pound plan does not produce a converted balance; the account is marked Not sent.
For the bank-connection details, read our Australian YNAB guide, UK bank-sync guide or European coverage guide.
If a number still looks wrong
Start with a narrow sample. Compare one posted bank transaction with the YNAB entry, then examine the handover date and the mapping. Decide whether you have an extra record, a missing record, a transfer issue or a starting-balance issue.
Avoid using an unexplained balance adjustment to hide a known import overlap. Fixing the cause makes the next sync easier to verify. If you cannot determine which record is correct, preserve the evidence and use the documented support route.
For records that never arrived, use the BankSync-to-YNAB troubleshooting guide.
Frequently asked questions
Finish with a repeatable review
After the first batch is correct, use the feed result and YNAB register to check subsequent imports. A good handover ends with a routine you can trust: one real account, one intended destination and one import route.
BankSync is independent of YNAB and is not affiliated with or endorsed by YNAB. Setup details follow the BankSync YNAB documentation.