How BudgetSyncer prevents duplicate transactions

Banks often expose the same payment twice: once as pending and again as booked. BudgetSyncer uses stable bank transaction IDs so those versions do not create two YNAB rows when the bank keeps a consistent identity across states.

YNAB also applies its own import ID rules when transactions arrive. BudgetSyncer and YNAB together reduce the duplicate friction that weekly CSV imports create when files include both pending and cleared lines.

When you reconnect a bank after consent expires, BudgetSyncer skips overlaps that already match date, amount, and payee in YNAB. That helps prevent a second full history dump of transactions you already imported.

If you change the YNAB destination for a mapped bank account, import-from-date behaviour follows the new mapping — remapping to a different YNAB account is treated carefully so you do not unintentionally re-import into the wrong place.

Open banking data is only as clean as the bank provides. Odd payee strings, split payments, or cash withdrawals can still need a quick look in YNAB. BudgetSyncer focuses on reliable import — categorization stays in YNAB.

Transactions sync automatically on your chosen schedule (default twice per day; you can add or change sync times on the connections page). Exact local times are shown for your timezone. You can also start a manual sync anytime from BudgetSyncer. With Enable Banking there is no separate daily limit on user-triggered syncs (banks may still delay publishing transactions).