Budgero Changelog

Right after onboarding, a device could save a copy of the new workspace that looked older than it was. Loading or restoring that copy then created the starter category groups and categories a second time, and the starter goal failed to sync. Sync confirmations are now handled strictly in order, and Budgero no longer saves a copy while it is still catching up on changes.

The dry-run preview of an UPDATE or DELETE whose WHERE clause spans several lines now shows only the rows it would change, not the whole table.

On the desktop Planning table, the new Target button adds a column with each category’s goal target for the month and a total per group. The pill fills up as the target gets funded. The choice is remembered on each device.

Reports → Plan vs Reality now lists every category’s goal target for the chosen period next to what you assigned and spent, with group subtotals and how many months each target was met. Groups start folded; click one to open it.

Importing a file into a crypto account stored amounts 100,000 times too small, and amounts under 0.001 BTC became zero. Amounts are now stored at full 8-decimal precision. Imports into regular accounts work exactly as before.

The goal funding list counted a monthly goal’s target for every month in the period, even months before the goal existed. It now uses each month’s actual target and is grouped by category group.

The import dialog now offers a spreadsheet (.xlsx) and a CSV template for bank, cash, credit card or crypto records you keep yourself.

Removed the empty space above the Planning toolbar on desktop and mobile.

On Macs with Safari before version 26 (for example on macOS Ventura), Budgero could not save its local copy of your budget, so it had to rebuild it on every start and sync could stall. It now saves through a method those Safari versions support.

Settings → Earlier versions lists the copies of your workspace the server keeps: the last few and one a day for the past week. Each one shows what it contains (transactions, accounts, categories, budgets), counted on your device. Restoring a copy puts it back on all your devices and then re-applies every change made after it, so no edits are lost.

A device that keeps hitting the same problem now sends one report every ten minutes instead of every minute.

If a browser could not read its stored copy of a workspace, it started again from an empty copy and could upload that to the server before catching up, replacing the full snapshot. The server now refuses any snapshot that is older than the one it holds, and a device only uploads after it has caught up with all changes. Your change history on the server was never affected, so devices that already have your budget keep it.

Budgero Cloud error reports now include the underlying error behind a failure (for example a storage or network error), the state of the app at that moment as fixed values (such as whether sync was connected and the storage type) and a random id for the visit that links a report to the server log of the same requests. Still never your data, amounts or any message text. The privacy policy describes the addition; self-hosted Budgero still sends nothing.

The server no longer writes sign-in tokens into its logs when a sync connection is refused.

If part of Budgero hits an error, that page shows a “Try again” card and the rest of the app keeps working; the assistant and the command palette recover on their own. Before, a crash anywhere meant a blank screen and a reload.

When a sync problem happened, the “Sync needs attention” notice came back every few seconds while Budgero retried. You now see it once per problem, until a sync succeeds.

When the server cannot accept a change, Budgero now hears back with the reason instead of waiting forever, keeps the change on your device and tells you. Sync problems carry a fixed reason code (session expired, update needed, upload failed…).

A key press without a key name, which browsers send during autofill, caused an error in the shortcut handler. It is ignored now.

If the assistant’s reply could not be written to your budget, the chat failed silently. You now get a “Could not save the message” notice.

Budgero Cloud error reports now name the part of the app that failed, our own error code, the request id of a failed server call, and the sequence of screens and internal events before the error (names only, never values). The server reports its own failures the same way. Nothing you type, no amounts and no error message text leave your device; the privacy policy describes the addition. Self-hosted Budgero still sends nothing.

Every server response now carries an X-Request-Id, and a failed request returns it in the error body, so a problem can be traced in the server log without any personal detail.

Transfers between currencies can leave an account a fraction of a cent off, which shows as 0.00 but is not zero. Reconcile used to call that a match and change nothing, so the account could never be zeroed. It now writes the adjustment for any difference, shows it as “< 0.01” with an explanation, and leaves the account at exactly the balance you entered.

Statement imports (CSV, PDF, OFX/QFX, QIF, CAMT) now find a transaction you typed in yourself even when the bank books it a few days later or for a slightly different amount, using the range in Settings → Duplicate transactions (1% and ±7 days by default). Choose Match to keep your transaction, with its category, memo, payee and splits, and mark it cleared. When only one entry fits, the row starts on Match.

SimpleFIN and Enable Banking use the same amount and date range to find entries you already typed in. A Push API transaction that looks like one of yours now waits in the account’s review list instead of being added twice; Add as new adds exactly what was sent.

Rules have a new Set label action, or Clear label to remove one. It works for every rule type, including autofill rules that fill in the label while you add a transaction, and a rule run can be undone.

Select transactions and choose Set Label in the edit menu to label them all, or clear their labels, in one step you can undo.

The day-two and trial-ending emails on Budgero Cloud let you answer with one tap, with an optional note, so telling us what is working takes seconds.

Undoing an edit of an imported transaction could fail with an error, and deleting one could leave its import record behind so the same file row looked imported. Both are fixed.

The account balance and register now update as soon as a file import finishes, instead of after a reload.

A device that reconnected after being offline could stay behind until the next reconnect, and the “Finishing initial sync” message could stay on screen. Both are fixed.

The Imports page lists the supported file formats again instead of “[object Object]”.

The server now refuses oversized sign-in tokens before reading them, which protects it against recently published flaws in a token library used for signing in. Self-host is protected too.

The v1.19.4 Cloud build failed before it shipped. This release completes it, with the same YNAB import and error report improvements.