Reviewed: 28 October 2026.
If a transaction has not appeared in YNAB, first identify the route that should have delivered it. This guide covers a BankSync feed sending to YNAB. If you use YNAB's own Direct Import instead, start with YNAB's linked-account troubleshooting.
For BankSync, a missing entry can have several ordinary explanations: the bank has not posted it, the account is excluded, the plan currency differs, the feed starts after the historical period you want, or one of the connections needs attention.
Work through the evidence in order. Reconnecting everything at once makes it harder to discover which part was responsible.
Find the symptom that matches your situation
The BankSync integration guide describes the following behaviours. Use the message on your own feed to choose the next check.
Symptoms and next checks
| What you see | What to check | Next action |
|---|---|---|
| A recent card payment is absent | Pending or posted status | Wait for the final posted transaction |
| An account says Not sent | Account currency versus plan currency | Choose a matching-currency plan |
| One account sends nothing | Mapping and Don’t send setting | Select the intended YNAB account |
| Feed says YNAB access is unavailable | YNAB authorisation or subscription | Reconnect YNAB from Integrations |
| Rate-limit message | YNAB rate limit — continues on next sync | Let the next scheduled sync continue |
| Destination account was closed | Current mapping target | Choose a valid replacement account |
| A deleted transaction stays absent | Whether it was previously sent and deleted | Do not expect a retry to recreate it |
Check whether the bank has posted the transaction
BankSync's YNAB destination sends posted transactions only. Pending entries are never sent through this destination.
A card purchase can be visible in your banking app before the bank makes a final posted record available through its data connection. General feed settings for pending transactions do not change the YNAB destination's posted-only behaviour.
Compare against a known posted transaction rather than the newest purchase. In Australia, source refresh timing can add a delay; in the UK and EU, posting and provider timing also matter. A successful sync cannot retrieve a final record that the source has not supplied.
Check the account and the plan
Open the feed's Mapping tab and find the source account. It should point to the intended YNAB account, or be deliberately excluded with Don't send.
Check the destination plan's currency too. An Australian-dollar account cannot be treated as pounds merely by choosing a GBP plan. BankSync does not convert currencies and marks a mismatched account Not sent.
If one feed contains accounts in several currencies, organise separate feeds and matching-currency plans for the accounts you want to include. The European guide includes a EUR and PLN example.
A mapping warning also deserves attention. BankSync can warn when a bank account already sends through another feed or a YNAB account receives from a different bank account. A saved configuration is not, by itself, proof that the mapping is the one you intended.
Trace one missing transaction
Confirm the source record
Choose a posted bank transaction and note its date, amount, currency and source account. Avoid using a pending purchase as the test.
Inspect the feed
Check the selected banks, destination plan, account mapping, start choice and latest sync result.
Inspect the destination
Open the exact mapped YNAB account. Check whether the record already exists, was deleted, or is waiting for approval.
Act on the specific message
Renew bank access for a bank-consent problem, reconnect YNAB for a destination-access problem, or let the next scheduled sync continue after a rate limit.
Check dates before requesting more history
A new feed starts from Today by default. If you expected last month's purchases, check whether you deliberately selected Include past transactions.
The historical options are limited by what the bank provides. Choosing 90 days does not make unavailable records appear. BankSync's UK and European bank guides also describe limits on the initial history available from a new connection.
Two other date behaviours are useful when investigating an apparently missing record. Transactions a bank posts late are still sent. Transactions dated after today in UTC wait for a later sync because YNAB rejects future dates. Local time and UTC can be on different calendar dates, which can be particularly noticeable for Australian users.
These are reasons to inspect the dates and sync result before treating an entry as lost.
Reconnect the part that needs attention
Bank authorisation and YNAB authorisation are separate.
For a bank-consent problem, use the bank connection's renewal or reconnection flow. Follow the expiry information shown for that institution. See the Australian connection guide, UK guide or European guide.
For revoked or expired YNAB access, reconnect from Integrations. BankSync's documented flow keeps your account matches and start dates. A closed or deleted YNAB account instead requires a new destination mapping.
If the message is a YNAB rate limit, the next scheduled sync resumes the work. Repeatedly reconnecting is not the documented remedy.
What to include when asking for help
A useful support report identifies the feed, region, affected account, latest sync time and exact error message. Add whether the sample transaction is posted, its date and amount, and whether it was already present or deleted in YNAB.
Share sensitive transaction details only through the appropriate support channel, and never include bank passwords or YNAB access credentials. A narrow example is usually more useful than sending an entire financial history.
Frequently asked questions
Verify one record before changing the whole setup
Once the cause is understood, confirm that a known posted transaction reaches the intended account exactly once. Then review the wider date range and balance.
If you are still setting up the feed, use the switching checklist. If you have not chosen an import route, compare CSV imports and connected bank feeds.
BankSync is independent of YNAB and is not affiliated with or endorsed by YNAB. Setup details follow the BankSync YNAB documentation.