Buckets is a mature desktop budgeting app built around the envelope idea without requiring a self-hosted server. That makes its SimpleFIN support attractive to people who want automatic bank data but do not want to operate Docker, a database or a public web service.
The important distinction is that the budget file remains local, while the provider connection and access URL still need the same care as any financial-data credential.
Choose the right import path
Buckets offers SimpleFIN, bank macros and manual file imports. Use SimpleFIN for ongoing periodic imports when your institution is supported through BankSync. Use a file import for older history when the live feed does not reach far enough. Keep bank macros as a separate fallback rather than running two automated paths against the same account.
Before connecting, back up the Buckets budget file and note each local account’s current reconciled balance. In BankSync, authorize the supported bank, then use the current SimpleFIN destination flow to create the one-time setup token or connection value.
Buckets setup
Back up the budget file
Use Buckets’ local file workflow and keep a recoverable copy.
Connect the bank in BankSync
Authorize the supported institution and select only the needed accounts.
Create the SimpleFIN connection
Use BankSync’s current destination flow and copy the one-time setup token.
Open Buckets bank sync
Choose SimpleFIN in the app’s current account or import settings.
Submit the token once
Allow Buckets to discover source accounts.
Map one account
Match name, type, currency and last four digits before importing.
Reconcile and expand
Verify one statement balance, then link the remaining accounts.
Local does not mean maintenance-free
The SimpleFIN access URL may be stored with the local budget configuration. Protect the device with full-disk encryption, secure backups and an operating-system login. If you sync the budget file through a general cloud drive, understand whether the credential is embedded and whether the file is encrypted.
Backfill without duplicates
SimpleFIN requests are bounded and historical availability varies by bank. Export older transactions from the bank and import them only up to a chosen seam date. Then begin the SimpleFIN feed after that seam. Run a duplicate check on date, amount and source ID, but do not merge legitimate recurring charges merely because their descriptions match.
Why Buckets appeals to hobbyists
There is no server to patch and the budget remains portable. The trade-off is that background sync depends on the desktop application running and platform behavior. If you need multi-user access, remote automation or an API, another app may fit better.
Buckets first-sync checks
| Stage | What to do | Check |
|---|---|---|
| Backup | Copy the budget file before linking | Restore opens successfully |
| Provider | BankSync connection is current | No reauthorisation warning |
| Mapping | One remote account to one local account | Currency and type match |
| Transactions | Newest posted items appear once | No duplicate after second sync |
| Balance | Reconcile to a bank statement date | Opening balance is not doubled |
| History | Document the file/SimpleFIN seam | No overlapping period |
Keep the local file recoverable.
Troubleshooting
If Buckets discovers no accounts, verify the provider connection and generate a fresh setup token; the previous token may have been claimed. If imports stop, determine whether the desktop app has run, whether the provider is stale, and whether the access URL was revoked. If two import methods are active, disable one before deleting data.
For power users, keep a small audit note inside your backup routine: provider, date connected, local-account mapping and backfill seam. That makes later migrations much easier.