Budgie logo
Budgie

Windowed Bank Re-sync

Re-pull just the last N days of bank history without nuking your manual edits or category overrides.

Why a full re-sync is the wrong fix

Sometimes a sync drifts — a transaction reconciles late, a refund posts wrong. The naive fix is a full re-sync, which wipes your edits. Budgie's window picker re-pulls only the slice you ask for.

Pick a window: last 7 days, last 30, last 90, or a custom range. Budgie diffs the bank's response against existing rows; new rows insert, deleted rows soft-delete, edited rows show a conflict picker.

What you get

Five window presets: 7, 30, 90 days, plus custom range

Manual edits in the window are preserved — conflict picker for every edited row

Diff before write — see what changes before anything commits

Soft-delete for rows the bank no longer reports — recoverable from trash

Works on every bank-synced provider — Monobank today, more soon

How it works

Account detail → Re-sync. The window picker opens. Pick a range. The sync engine fetches just that window from the bank API, runs a diff, and presents conflicts before write.

Frequently Asked Questions

Why not just full re-sync?
A full re-sync wipes your manual category overrides and edits. Windowed re-sync diffs only the slice you ask for, so old edits stay safe.
What's the smallest window?
Last 7 days. Larger windows (30, 90, custom) are also one-tap presets. Custom range opens a date picker.
What happens to edited transactions in the window?
A conflict picker appears for every edited row before write. You choose to keep your edit, take the bank's version, or merge fields.
Can I re-sync transactions from before bank-sync was enabled?
Only as far back as the bank's API supports. Monobank has months of history; PrivatBank XLSX is per-export. CSV import is the universal fallback.

Ready to take Budgie for a spin?

Join the waitlist — be first to try the offline-first expense tracker.