Budget - Releases

Added

• The Bills page now flags payments without a recorded transaction. A warning card lists bills that were marked paid in the last 60 days without a transaction being created or linked — the situation where the app balance silently detaches from the bank. Each entry has a one-click Record transaction repair that books the missing payment (dated the day it was marked paid, both legs for transfers, splits applied). Deliberate skips via the Skip button are not flagged (#274)
• QAR (Qatari Riyal) and JOD (Jordanian Dinar) are now available as account currencies. JOD amounts use the currency's native 3 decimal places. Automatic exchange rates cover both. Requested in #321

Fixed

• Editing a monthly recurring income never saved the changes — the app showed "Income saved successfully" but the Expected Day (and every other field) kept its old value. Any update whose payload contained an empty field (a monthly income always sends its yearly-only "expected month" as empty) reloaded the entity mid-save and threw away the edits. Thanks to @redsteadz for the fix (#324, #325)
• The "Exclude from forecast" checkbox on a transaction appeared unticked whenever the edit dialog was reopened, and saving the transaction again then really did reset the flag. The flag was stored correctly (including when set by an import rule) but the transaction list never sent it back to the browser, so the dialog always showed — and re-saved — it as off (#326)
• Income/Expenses This Month (and the other report summary totals) deducted transactions in "Exclude from reports" categories without converting them to the base currency, so on multi-currency setups the deduction was applied at the wrong rate — and for a single selected account the deduction wrongly included every other account's excluded transactions too (#326)
• Imports no longer bring in flagged duplicates by default. The preview's "Show duplicates" checkbox — on by default — secretly doubled as the skip-duplicates switch, so every import ran with duplicate-skipping off and rows flagged Duplicate were imported anyway. It is now purely a display filter; a new explicit "Import flagged duplicates too" option (off by default, resets each import) covers the deliberate re-import case. The preview's per-row checkboxes, which were never actually read by the import, are gone, and the New Transactions count no longer includes flagged duplicates (#327)
• Marking a bill paid no longer suggests unrelated transactions as "existing" matches. The Existing Transaction Found dialog offered any unlinked same-day debit as a candidate — cigarettes could be presented as a "match" for a mortgage — steering people into marking bills paid without recording the payment, the classic source of app-vs-bank balance drift. Candidates now must match the bill by amount or name, a weak match is never pre-selected (the safe default is creating the transaction), and the "Don't create any transaction" option now states — and warns after — that the account balance will not reflect the payment (#274)
• Overdue bills no longer double-book when marked paid. The scheduled placeholder pre-created for the next occurrence was written as an ordinary cleared transaction whenever the advanced due date was not in the future, so it counted toward the balance immediately — alongside the actual payment. Next-occurrence placeholders are now always scheduled, regardless of date
• Restoring a backup preserves every bill setting. The data import dropped most bill fields: custom recurrence patterns (restored bills then advanced one day at a time instead of quarterly/etc.), transfer destination and description pattern, auto-pay, reminder days, tags, split templates, start/end dates, remaining payments, forecast exclusion and the future-transaction opt-out

Changed

• The Match transfer dialog now also lists candidates from accounts in a different currency (any amount, within the date window), so cross-currency transfer pairs — e.g. imported from CSV — can finally be linked by hand. Automatic matching after imports is unchanged and still only links exact same-currency amounts (#326)

Fixed

• The account selector saved in the gear settings of insight tiles (Monthly Comparison, Large Transactions, Weekly Spending, Year-over-Year) was silently ignored — the tiles always showed all-accounts data. The saved account now actually scopes the tile's numbers
• Importing transactions that trigger the Auto-Link as Transfer rule action no longer shows "Cannot use object of type Transaction as array" on the import screen. The import itself always completed — the error came from the transfer-linking step afterwards, which also means those transfers were never actually linked (#314)
• The Recent Transactions dashboard tile now honors its "Rows to show" setting above 8 — the display respected the setting but the data fetch was hardcoded to 8 rows, so values of 9–20 silently showed only 8

Added

• Edit auto-categorization rules as JSON. The rule editor gains a Builder / JSON toggle. The JSON view shows the raw rule structure — editable and paste-friendly — checked when you save, and switching back to Builder repopulates the visual widgets. A Copy JSON button makes it easy to move a rule between instances (category/account IDs are instance-specific, as noted in the view). Requested in #318

• Hide shared categories from your own reports. Categories shared with you gain a per-viewer "Hide from my reports" toggle on the Categories page. Unlike the owner's "Exclude from reports" flag — which stays owner-only because it changes every viewer's reports at once — this only affects your own reports and dashboards; the owner and other viewers see no difference. Applied at the SQL layer through the same choke points as the owner flag, so every report and insight tile honors it consistently

• "Exclude shared accounts" on the remaining dashboard tiles. The per-tile toggle added in v2.37 now also covers Budget Progress, Monthly Comparison, Large Transactions, Weekly Spending, Category Trends, Cash Flow Forecast and Year-over-Year (shown in the gear menu when you have shared accounts). Bills, income and pension tiles are deliberately not included — they show entity data, not account aggregates

• Clickable spending charts. Clicking a slice (or bar) on the Spending by Category dashboard tile or the Reports page pie chart jumps to the transaction list filtered to that category, scoped to the chart's date range and account. Tiles set to "top-level only" include the subcategories in the filter so the listed transactions match the clicked amount (#317)

• Per-bill opt-out of pre-created transactions. The "Create future transaction for this bill" checkbox is now a persistent bill setting instead of a one-shot option at creation. Bills with it unticked never get a scheduled placeholder — not at creation, not after marking paid, not after skipping — and toggling it on an existing bill adds or removes the pending placeholder immediately. Previously the checkbox only affected the moment a bill was created, while every payment re-enabled pre-booking unconditionally, so unticking it never actually opted a bill out (#311)

• Convert a transaction into a transfer. The Match transfer dialog gains a "No match? Create the other side" section: pick one of your accounts and the app creates the opposite transaction there and links the pair as a transfer. Until now the dialog could only link two existing transactions, which left no way to correctly book payments to accounts that have nothing to import — e.g. a loan tracked as its own account (#313)

Changed

• Scheduled (future-dated) transactions now show a Scheduled badge in the main transaction list, with a tooltip explaining they are not counted until they occur. Previously only the account detail view had the badge and the main list showed scheduled rows in italics alone, which made a bill's pre-created next occurrence easy to mistake for a duplicate booking (#311)
• The transaction list Total no longer includes scheduled transactions — they are placeholders for money that has not moved yet (#311)

Added

• Exclude shared accounts from reports. When other people have shared accounts with you, the Reports page gains an "Exclude shared accounts" toggle so you can see just your own accounts' figures. The same option is available per-tile (in the gear menu) on the account-based dashboard cards — Income vs Expenses, Spending by Category, Top Spending Categories and Recent Transactions. It's off by default (shared accounts are included, as before) and only appears when you actually have shared accounts. Note: a transfer between one of your accounts and a shared account can only be partly seen when shared accounts are excluded, so income/expense totals may be slightly overstated in that case.

Fixed

• Saving share settings failed with "Some entities do not belong to you" (HTTP 400) when the "Auto-share new" toggle was enabled for a type, or after using Select All — the auto-share toggle (which shares the same data-type as the entity checkboxes) was being collected as a phantom entity and sent as a null id. Entity selection is now scoped precisely, so share settings save correctly with auto-share on (#306)

Changed

• The Categories page now also lists categories that have been shared with you, shown read-only with a "Shared · <owner>" badge. Previously it showed only your own categories, so anyone using a budget made up entirely of shared categories saw an empty page even though the categories worked everywhere else (#306)
• Categories shared with you at Edit permission are now editable — rename them and change their colour straight from the Categories page (they carry a "Shared (editable) · <owner>" badge). Read-only shares stay read-only, and a category's type, parent, budget, report visibility and deletion all remain owner-only (#306)

Added

• Auto-share new entities. Each person you share with now has an "Auto-share new" toggle per entity type (accounts, categories, bills, recurring income, savings goals) in their sharing settings. Turn it on and anything you create from then on is shared with them automatically, at the permission you choose — no more sharing each new bill or category by hand (#306)

Fixed

• Code-integrity "Some files have not passed the integrity check" errors reporting FILE_MISSING for js/.htaccess and vendor/tecnickcom/tcpdf/tools/.htaccess. The app no longer ships any .htaccess files — the Nextcloud App Store strips them from the published archive, which left the signature expecting files that were no longer present. Neither file was needed (the JS one only set a redundant cache header) (#307)
• Deprecation warning in the Nextcloud log — the notifier now throws UnknownNotificationException instead of InvalidArgumentException for unrecognised notifications, as required by Nextcloud 30+ (#308)
• Reports and the dashboard summary were empty when a single account flagged "Exclude from reports" was the only account selected. Accounts flagged out of reports are now only dropped from the all-accounts views; explicitly selecting one shows its data as normal (#309)

Fixed

• Categories marked "Exclude from reports" are now consistently excluded everywhere, including the Income vs Expenses trend, Category Trends, Top Spending Categories and the monthly spending chart — not just the dashboard summary. Exclusion is now applied in the database query itself, so reports and dashboard insight tiles can no longer disagree about which categories count (#219)

Added

• Pensions revamp. You can now record a contribution as a transfer from a bank account — the matching withdrawal is created automatically and kept out of your spending — and record withdrawals/drawdown back into an account (#304). Scheduled (recurring) contributions (monthly/quarterly/yearly) can post automatically or on demand (#251). DC pensions gained a configurable projection target with a progress indicator and a "today's money" (inflation-adjusted) view on the growth chart, plus an optional Pension Projection dashboard card. Bank legs that fund a pension show a Pension badge in the transaction list.

Fixed

• Background-job "class does not exist" log spam that could appear after updating PHP/Nextcloud/the app: the app's autoloader is no longer "authoritative", so it falls back to PSR-4 and self-heals if PHP's cached class map is stale after an update (#305)
• Newly-added dashboard widgets now load their data immediately instead of staying empty until the page is refreshed.
• The pension detail panel's balance history and activity are no longer broken — those views called endpoints that didn't exist; they now show a proper balance chart and a merged timeline of contributions, withdrawals and balance updates, each removable (#251)
• Editing a split transaction with three or more parts no longer zeroes or overwrites the other splits. The last split row is now a read-only "remaining" amount (transaction total minus the other parts), and the dialog blocks saving until the parts add up (#303)
• Spending-anomaly notifications no longer crash with "The arguments array must contain 1 items, 0 given" — a stray % in the notification text made Nextcloud's translation layer fail, spamming the log every time notifications were rendered (#305)

Added

• The transaction list filters now include a Reconciled filter (All / Reconciled / Not reconciled), so you can quickly see which transactions still need reconciling (#301)
• A Budget alert threshold setting controls when a category appears on the Budget Alerts tile (default 80% of budget). Set it to 100% to be alerted only when a category actually goes over budget, rather than when it's merely approaching or fully used (#293)

Fixed

• Creating a category (or account) no longer fails with "Unknown column 'excluded_from_reports'" on instances where an earlier upgrade was interrupted or restored from a mid-upgrade backup. A self-healing migration re-adds the affected columns automatically on update (#302)

Fixed

• On some installs an earlier update was recorded as applied but didn't fully run (an interrupted upgrade, or a database restored from a backup taken mid-upgrade), leaving the excluded_from_forecast column missing — so every new transaction failed with "Unknown column 'excluded_from_forecast'". A migration now re-adds the column automatically on update. (Also surfaced by the new database-error detail field added in 2.32.0.) (#289)

Added

• Run reports on multiple accounts at once: the report Account filter is now a checklist — pick any set of accounts (e.g. all your credit cards, or all your checking accounts) or "All Accounts". Applies across the summary, spending, income, cash-flow, category-by-month and year-over-year reports and their CSV/PDF exports (#299)
• Saved reports: save a report's settings (type, period, selected accounts, tags and options) under a name and re-run it later from the "Saved Reports" picker in the Reports view. The period is stored as the chosen preset (e.g. "Last 3 months") so a saved report always shows up-to-date data (#299)
• Dashboard tiles that can be scoped to a specific account (Spending by Category, Income vs Expenses, Net Worth History, Recent Transactions, and the other account-aware widgets) now show a small label in their header naming the account they're analyzing — the account you picked in the tile's settings, or "All accounts" (#296)

Fixed

• The Reports period selector didn't drive the report on reopen: the dropdown kept your last choice (e.g. "Last Year") but the report always reverted to "Last 3 Months", and clicking "Generate Report" used the reverted range instead of the shown period — you had to switch the dropdown away and back. The report now always matches the period shown in the selector (custom ranges are preserved) (#300)
• The Quick Add Transaction dashboard widget couldn't be used on mobile — the lower fields and the "Add Transaction" button were clipped off the bottom of the tile, so a transaction could never be submitted. Its form is now condensed (each label sits beside its field with tighter spacing) so the whole form fits the tile, and it falls back to scrolling within the tile if it's resized very small (#298)
• Editing a split transaction's amount (e.g. inline in the transaction list) left its splits at the old amounts, so they no longer summed to the transaction total. The splits are now rescaled proportionally to the new amount (the last split absorbs any rounding remainder)
• In the edit-transaction dialog, changing one split amount now adjusts another split so the parts keep summing to the transaction total, instead of silently drifting out of balance
• Split transactions weren't counted toward category budgets or spending. When a single transaction was split across categories (e.g. one $1,000 payment split into rent, parking and a deposit), each of those categories showed $0 spent. Split allocations now count toward category spending everywhere it's shown — the Budget view, the Spending by Category chart, and reports (#297)
• Large amounts (e.g. values over 100,000) on the dashboard hero tiles (Net Worth, Income/Expenses This Month, Net Savings, Cash Flow) wrapped onto a second line, splitting the number mid-digits. The amount now stays on one line and its font scales down to fit narrow tiles instead of wrapping (#295)
• The "Asset Value History" dashboard tile (and "Net Worth History") showed its empty-state message anchored near the bottom of the tile instead of vertically centered. When there's no data the message now fills and centers within the chart area (#294)

Added

• Category by Month report: a new report (Reports → Category by Month) showing income and expenses per category broken down by month, with a column per month and an overall total. Categories are listed alphabetically with sub-categories grouped under their parents, and parent rows include the totals of their sub-categories; a toggle switches to sorting by total instead. Defaults to year-to-date, follows the report date-range and account filters, and exports to CSV and PDF (#288)

Changed

• API errors caused by the database now include the underlying driver message (e.g. a missing column) in a separate detail field of the error response, visible in the browser's network tab. The user-facing message is unchanged; this makes problems diagnosable on managed Nextcloud instances where admins can't read the server log. The executed SQL and any bound values are stripped from the detail (#289)

Fixed

• The dashboard "Budget Alerts" tile showed a red "exceeded" alert (with "0% over") for a category whose spending exactly equalled its budget. Spending that fully uses the budget without going over is now treated as a "100% used" warning, not an over-budget alert; only spending that actually exceeds the budget shows as exceeded (#293)
• PDF reports rendered non-Latin characters (Polish, Cyrillic, etc.) in account/category names as "?". The PDF exports used a built-in font limited to Western European characters; they now use an embedded Unicode font (DejaVu Sans), so names display correctly. Applies to the budget report, bills-calendar and year-over-year PDFs (#292)
• Marking a recurring transfer as paid showed a success message but created no account entries. The Transfers screen was only updating the transfer's "last paid" date instead of calling the mark-paid action, so no transactions were recorded; it now creates the paired transfer transactions like the Bills screen does (#291)

Added

• Exclude an account from totals: a per-account "Exclude from reports, dashboard & forecast" option (in the account's edit dialog) keeps the account fully tracked but leaves its transactions and balance out of every "all accounts" aggregation — reports, the dashboard, forecast, net worth, total balance and category budgets. The account still appears in your accounts list (with an "Excluded" badge) and on its own detail page, and selecting it explicitly in a report still works (#286)

Fixed

• The account detail page's overview tiles only counted the transactions on the visible page (e.g. "50" for an account with 1,603). "Total Transactions", "This Month Income", "This Month Expenses" and "Avg. Transaction" are now aggregated server-side over the whole account, so they're correct regardless of paging (#285)
• The dashboard spending chart's "Total Spending" figure (and each category's percentage) only summed the top 10 categories shown in the chart. It now reflects spending across all categories
• The CSV import preview's "Auto-categorized" count was estimated from a 50-row sample and could be wrong for larger imports; it's now counted over the full file on the server
• Editing an existing bill failed with "Failed to update bill" — saving the edit dialog (whether or not anything changed) returned a 400 error. The bill's start-date column, added with the limited-term bills feature, was missing from the list of updatable columns, so the always-sent start date was rejected before the save could run. Bills now save correctly, with a test guarding every persisted column (#284)
• Opening an account's detail page returned a 500 error (the reconciliation-history request failed). The reconciliation controller was missing a trait it relied on, so it couldn't be constructed and every reconciliation endpoint failed; the account page surfaced it via the history sidebar. Now fixed and covered by tests (#283)
• Starting an account reconciliation failed with a confusing "The string did not match the expected pattern" message (most visibly on Safari). The root cause was the reconciliation controller failing to construct (the #283 fix above resolves it); on top of that, the reconciliation screens now read error responses defensively, so any failure shows a clear message with the HTTP status instead of an opaque JSON-parsing error (#287)
• The Budget Overview dashboard widget (and the digest, spending-anomaly and bill-reminder notifications) always showed amounts in US dollars regardless of your configured currency. The server-side amount formatter was reading the wrong settings key and falling back to USD; it now uses your default currency
• The Budget Overview dashboard widget's "Total balance" now converts multi-currency accounts to your base currency instead of summing different currencies under one symbol (currencies without an exchange rate are excluded from the total and named)

Fixed

• Dropdowns in the transaction list (the column-configuration gear menu and the in-cell category/tag/account editors) were cut off when the table had only a few rows, because the table area was shorter than the dropdowns. The transaction table now fills the available height, so every dropdown has room to open in full (#280)
• The Tags column couldn't be shown/hidden — the Show/Hide Columns menu was missing a Tags entry, and the column wasn't wired into the visibility logic. Tags can now be toggled like the other columns (#281)

Security

• The recurring-income update endpoint no longer passes the raw request body through to the entity layer — a crafted payload could previously set internal fields such as the owning user (mass assignment, integrity only — no data disclosure). Update keys are now allowlisted like the other endpoints

Fixed

• Auto-derived recurring budgets (#269) are now consistent across all surfaces: the dashboard "Budget Remaining" hero, Budget Progress/Breakdown widgets, Budget Health score, and budget alerts now apply the same recurring fallback as the Budget view — a category funded only by recurring bills can now trigger alerts and is counted in headline totals
• Auto-derived budgets now respect bill start/end dates: a bill that hasn't started (or has ended) no longer counts toward today's budget, avoiding double-counting during a planned cost change (#268)
• Recurring income summaries (Income view header, dashboard Income Tracking widget): semi-monthly income was counted at half its value, and a one-time income at full value every month until received
• Transfers page monthly total: semi-monthly and semi-annual transfers were converted incorrectly
• Live forecast cache: cache invalidation never matched the stored key (changes such as toggling "exclude from forecast" appeared to do nothing for up to 5 minutes), and the cache key ignored shared-account visibility, letting a share-restricted viewer briefly see the owner's totals
• Editing a bill's amount without updating its split template is now rejected when the stored splits no longer match (the payment would have silently imported unsplit and uncategorized); setting a split template via the API now clears the bill-level category, matching creation
• Multi-account import partial failures (e.g. a deleted destination account) are now reported in the UI instead of masquerading as a full success
• Import preview now also flags repeated bank transaction IDs for accounts that will be created by the import
• Long OFX FITID hashing threshold raised so every previously-imported FITID keeps its exact ID (re-import dedup continuity)
• Auto-derived category budgets (#269) now handle every supported frequency correctly: semi-annual bills were over-counted 6×, semi-monthly halved, custom-schedule bills counted every month, and one-time bills inflated the budget monthly until marked paid (now excluded). Frequency math is delegated to the shared calculator, which also gained the missing semi-monthly conversion
• Auto-derived budgets no longer apply to past months — they reflect today's recurring bills/income and were rewriting history (including overriding explicitly-zeroed snapshot budgets)
• Multi-account import: an invalid destination account mid-import no longer aborts the batch, and deferred balance recomputes now always run for already-imported rows
• Bank sync: the post-import balance recompute now keys on transaction creation, not the import counter, so a row persisted just before a non-fatal error still gets its balance update
• The scheduled-transactions background job now recomputes balances from the ledger (it was the last remaining hand-computed balance delta, and could race concurrent imports)
• Import preview now flags a repeated bank transaction ID (OFX FITID) within one file as the duplicate it is, matching what import actually does; per-account preview counts include rows that will import with skip-duplicates off
• Marking a bill paid by linking an existing transaction now warns if the link silently failed (no money movement recorded)
• Extremely long OFX FITIDs are hashed to stay within the import-ID column

Fixed

• Dashboard could render half-empty (hero tiles only, widget grid invisible): a Chart.js resize on a hidden tile's detached canvas threw during initialization, and the widget grid was never revealed. Chart resizing now skips detached canvases and the grid is revealed before the resize pass. Likely also behind "nothing happens" reports after certain actions (#273)
• Dashboard tiles with a saved account selection pointing at a deleted account (e.g. after factory reset + import re-numbered accounts) no longer error with 404s and stay empty — stale selections fall back to all accounts
• Account balances are now derived from the ledger instead of running deltas — the root cause behind every historical balance-discrepancy report (#3, #89, #124, #163, #187, #194, #274). The stored balance was a running total that each transaction code path adjusted by hand; any missed or mis-signed delta corrupted it permanently. Every transaction create/update/delete (and retroactive rule run, repair action, import and bank sync) now recomputes balance = opening balance + net of non-scheduled transactions, making drift impossible and self-healing past inconsistencies on the next write. A one-time migration backfills the opening balance so displayed balances do not change on upgrade (#274)
• Marking a bill as paid now warns loudly when no transaction was recorded (bill without an account, or transaction creation failed) — previously the bill was advanced silently and the account balance never reflected the payment, drifting from the real bank balance every cycle (#89, #274)
• The app's own export→import now preserves transaction status (scheduled transactions no longer silently become balance-affecting after a migration) and restores the opening-balance invariant for imported accounts
• "Skip Duplicate Transactions" off is now honored: previously rows whose import ID already existed were still rejected deeper in the stack (duplicate-ID guard + unique index), so parts of the batch silently failed to import. Intentional duplicates now get a uniquified import ID and the entire batch imports (#275)
• Import duplicate detection no longer gives false positives for legitimately identical rows — e.g. two same-priced purchases on the same day with the same description. Identical rows within one file now import as distinct transactions (occurrence-aware import IDs), while re-importing the same statement still skips everything it already imported. Re-importing an older statement also recovers transactions the previous logic wrongly skipped (#276)

Fixed

• Install/upgrade aborted on Nextcloud 32 and earlier with "Primary index name on oc_budget_import_templates is too long". The budget_import_templates migration created its primary key without an explicit name, so Nextcloud derived a default name and hit the Oracle-compatibility identifier limit (the unprefixed table name is exactly 23 characters). The primary key now has an explicit short name. Thanks to @TheUnderdev for the report and fix (#272)

Added

• Shared savings goals — share a savings goal with another Nextcloud user. Recipients see a "Shared" badge and can view progress; with write permission they can edit the goal and add money, while only the owner can delete it (#255)
• Auto-derived budgets from recurring items — a (sub-)category with no manually-set budget now shows its committed recurring total (active recurring bills + recurring income, normalized to the budget period) as an automatic budget limit, marked "auto". Typing a value always overrides it (#269)
• Exclude extraordinary/one-time items from the forecast — a per-transaction "exclude from forecast" flag (with a "No forecast" list badge), the same flag on recurring bills/income (propagated to generated transactions), and a matching import-rule action. Flagged amounts still affect your balance but are kept out of the projection averages (#270)
• Reusable CSV import templates — save column mappings and import options and reapply them to future imports (#247)
• OFX/QIF import account routing — route multi-account OFX/QIF files to the right Budget accounts, remembered across subsequent imports
• Bank sync: pending transactions — option to import not-yet-posted (pending) transactions, automatically reconciled when they clear (#257)
• Bill start dates — a bill only occurs on or after its start date, making it easy to change a recurring cost mid-year by ending one bill and starting another (#268)
• "Shared with me" expenses view — recipients can now see expenses that have been shared with them (#248)
• Dashboard period indicator — chart tiles now show a read-only indicator of the period they cover (#250)

Fixed

• Dashboard now collapses to a single full-width column on phones, independent of your configured desktop column count (#249)
• "Excluded from reports" categories no longer appear in the Budget view (#266, #267)
• Category spending chart shows income as positive with the correct label (#265)
• Tag-linked savings goals now sum net realized contributions (credits minus debits, excluding scheduled) (#264)
• Recurring income description is now persisted on create (#263)
• Transfers are now excluded from dashboard income/expense totals (#262)
• Account Breakdown report now uses each account's own currency instead of a single assumed one (#256)
• Fixed a PageController crash (TypeError) on unauthenticated requests (#259)
• Quick Add date field normalization on iOS (#235)

Docs

• Documented the standalone Quick Add page and the iOS home-screen workaround
• Noted that GoCardless no longer accepts new bank-sync sign-ups; EU/UK self-hosters without an existing account are pointed to manual import (#271)

Added

• The Bills page now flags payments without a recorded transaction. A warning card lists bills that were marked paid in the last 60 days without a transaction being created or linked — the situation where the app balance silently detaches from the bank. Each entry has a one-click Record transaction repair that books the missing payment (dated the day it was marked paid, both legs for transfers, splits applied). Deliberate skips via the Skip button are not flagged (#274)
• QAR (Qatari Riyal) and JOD (Jordanian Dinar) are now available as account currencies. JOD amounts use the currency's native 3 decimal places. Automatic exchange rates cover both. Requested in #321

Fixed

• Editing a monthly recurring income never saved the changes — the app showed "Income saved successfully" but the Expected Day (and every other field) kept its old value. Any update whose payload contained an empty field (a monthly income always sends its yearly-only "expected month" as empty) reloaded the entity mid-save and threw away the edits. Thanks to @redsteadz for the fix (#324, #325)
• The "Exclude from forecast" checkbox on a transaction appeared unticked whenever the edit dialog was reopened, and saving the transaction again then really did reset the flag. The flag was stored correctly (including when set by an import rule) but the transaction list never sent it back to the browser, so the dialog always showed — and re-saved — it as off (#326)
• Income/Expenses This Month (and the other report summary totals) deducted transactions in "Exclude from reports" categories without converting them to the base currency, so on multi-currency setups the deduction was applied at the wrong rate — and for a single selected account the deduction wrongly included every other account's excluded transactions too (#326)
• Imports no longer bring in flagged duplicates by default. The preview's "Show duplicates" checkbox — on by default — secretly doubled as the skip-duplicates switch, so every import ran with duplicate-skipping off and rows flagged Duplicate were imported anyway. It is now purely a display filter; a new explicit "Import flagged duplicates too" option (off by default, resets each import) covers the deliberate re-import case. The preview's per-row checkboxes, which were never actually read by the import, are gone, and the New Transactions count no longer includes flagged duplicates (#327)
• Marking a bill paid no longer suggests unrelated transactions as "existing" matches. The Existing Transaction Found dialog offered any unlinked same-day debit as a candidate — cigarettes could be presented as a "match" for a mortgage — steering people into marking bills paid without recording the payment, the classic source of app-vs-bank balance drift. Candidates now must match the bill by amount or name, a weak match is never pre-selected (the safe default is creating the transaction), and the "Don't create any transaction" option now states — and warns after — that the account balance will not reflect the payment (#274)
• Overdue bills no longer double-book when marked paid. The scheduled placeholder pre-created for the next occurrence was written as an ordinary cleared transaction whenever the advanced due date was not in the future, so it counted toward the balance immediately — alongside the actual payment. Next-occurrence placeholders are now always scheduled, regardless of date
• Restoring a backup preserves every bill setting. The data import dropped most bill fields: custom recurrence patterns (restored bills then advanced one day at a time instead of quarterly/etc.), transfer destination and description pattern, auto-pay, reminder days, tags, split templates, start/end dates, remaining payments, forecast exclusion and the future-transaction opt-out

Changed

• The Match transfer dialog now also lists candidates from accounts in a different currency (any amount, within the date window), so cross-currency transfer pairs — e.g. imported from CSV — can finally be linked by hand. Automatic matching after imports is unchanged and still only links exact same-currency amounts (#326)

Fixed

• The account selector saved in the gear settings of insight tiles (Monthly Comparison, Large Transactions, Weekly Spending, Year-over-Year) was silently ignored — the tiles always showed all-accounts data. The saved account now actually scopes the tile's numbers
• Importing transactions that trigger the Auto-Link as Transfer rule action no longer shows "Cannot use object of type Transaction as array" on the import screen. The import itself always completed — the error came from the transfer-linking step afterwards, which also means those transfers were never actually linked (#314)
• The Recent Transactions dashboard tile now honors its "Rows to show" setting above 8 — the display respected the setting but the data fetch was hardcoded to 8 rows, so values of 9–20 silently showed only 8

Added

• Edit auto-categorization rules as JSON. The rule editor gains a Builder / JSON toggle. The JSON view shows the raw rule structure — editable and paste-friendly — checked when you save, and switching back to Builder repopulates the visual widgets. A Copy JSON button makes it easy to move a rule between instances (category/account IDs are instance-specific, as noted in the view). Requested in #318

• Hide shared categories from your own reports. Categories shared with you gain a per-viewer "Hide from my reports" toggle on the Categories page. Unlike the owner's "Exclude from reports" flag — which stays owner-only because it changes every viewer's reports at once — this only affects your own reports and dashboards; the owner and other viewers see no difference. Applied at the SQL layer through the same choke points as the owner flag, so every report and insight tile honors it consistently

• "Exclude shared accounts" on the remaining dashboard tiles. The per-tile toggle added in v2.37 now also covers Budget Progress, Monthly Comparison, Large Transactions, Weekly Spending, Category Trends, Cash Flow Forecast and Year-over-Year (shown in the gear menu when you have shared accounts). Bills, income and pension tiles are deliberately not included — they show entity data, not account aggregates

• Clickable spending charts. Clicking a slice (or bar) on the Spending by Category dashboard tile or the Reports page pie chart jumps to the transaction list filtered to that category, scoped to the chart's date range and account. Tiles set to "top-level only" include the subcategories in the filter so the listed transactions match the clicked amount (#317)

• Per-bill opt-out of pre-created transactions. The "Create future transaction for this bill" checkbox is now a persistent bill setting instead of a one-shot option at creation. Bills with it unticked never get a scheduled placeholder — not at creation, not after marking paid, not after skipping — and toggling it on an existing bill adds or removes the pending placeholder immediately. Previously the checkbox only affected the moment a bill was created, while every payment re-enabled pre-booking unconditionally, so unticking it never actually opted a bill out (#311)

• Convert a transaction into a transfer. The Match transfer dialog gains a "No match? Create the other side" section: pick one of your accounts and the app creates the opposite transaction there and links the pair as a transfer. Until now the dialog could only link two existing transactions, which left no way to correctly book payments to accounts that have nothing to import — e.g. a loan tracked as its own account (#313)

Changed

• Scheduled (future-dated) transactions now show a Scheduled badge in the main transaction list, with a tooltip explaining they are not counted until they occur. Previously only the account detail view had the badge and the main list showed scheduled rows in italics alone, which made a bill's pre-created next occurrence easy to mistake for a duplicate booking (#311)
• The transaction list Total no longer includes scheduled transactions — they are placeholders for money that has not moved yet (#311)

Added

• Exclude shared accounts from reports. When other people have shared accounts with you, the Reports page gains an "Exclude shared accounts" toggle so you can see just your own accounts' figures. The same option is available per-tile (in the gear menu) on the account-based dashboard cards — Income vs Expenses, Spending by Category, Top Spending Categories and Recent Transactions. It's off by default (shared accounts are included, as before) and only appears when you actually have shared accounts. Note: a transfer between one of your accounts and a shared account can only be partly seen when shared accounts are excluded, so income/expense totals may be slightly overstated in that case.

Fixed

• Saving share settings failed with "Some entities do not belong to you" (HTTP 400) when the "Auto-share new" toggle was enabled for a type, or after using Select All — the auto-share toggle (which shares the same data-type as the entity checkboxes) was being collected as a phantom entity and sent as a null id. Entity selection is now scoped precisely, so share settings save correctly with auto-share on (#306)

Changed

• The Categories page now also lists categories that have been shared with you, shown read-only with a "Shared · <owner>" badge. Previously it showed only your own categories, so anyone using a budget made up entirely of shared categories saw an empty page even though the categories worked everywhere else (#306)
• Categories shared with you at Edit permission are now editable — rename them and change their colour straight from the Categories page (they carry a "Shared (editable) · <owner>" badge). Read-only shares stay read-only, and a category's type, parent, budget, report visibility and deletion all remain owner-only (#306)

Added

• Auto-share new entities. Each person you share with now has an "Auto-share new" toggle per entity type (accounts, categories, bills, recurring income, savings goals) in their sharing settings. Turn it on and anything you create from then on is shared with them automatically, at the permission you choose — no more sharing each new bill or category by hand (#306)

Fixed

• Code-integrity "Some files have not passed the integrity check" errors reporting FILE_MISSING for js/.htaccess and vendor/tecnickcom/tcpdf/tools/.htaccess. The app no longer ships any .htaccess files — the Nextcloud App Store strips them from the published archive, which left the signature expecting files that were no longer present. Neither file was needed (the JS one only set a redundant cache header) (#307)
• Deprecation warning in the Nextcloud log — the notifier now throws UnknownNotificationException instead of InvalidArgumentException for unrecognised notifications, as required by Nextcloud 30+ (#308)
• Reports and the dashboard summary were empty when a single account flagged "Exclude from reports" was the only account selected. Accounts flagged out of reports are now only dropped from the all-accounts views; explicitly selecting one shows its data as normal (#309)

Fixed

• Categories marked "Exclude from reports" are now consistently excluded everywhere, including the Income vs Expenses trend, Category Trends, Top Spending Categories and the monthly spending chart — not just the dashboard summary. Exclusion is now applied in the database query itself, so reports and dashboard insight tiles can no longer disagree about which categories count (#219)

Added

• Pensions revamp. You can now record a contribution as a transfer from a bank account — the matching withdrawal is created automatically and kept out of your spending — and record withdrawals/drawdown back into an account (#304). Scheduled (recurring) contributions (monthly/quarterly/yearly) can post automatically or on demand (#251). DC pensions gained a configurable projection target with a progress indicator and a "today's money" (inflation-adjusted) view on the growth chart, plus an optional Pension Projection dashboard card. Bank legs that fund a pension show a Pension badge in the transaction list.

Fixed

• Background-job "class does not exist" log spam that could appear after updating PHP/Nextcloud/the app: the app's autoloader is no longer "authoritative", so it falls back to PSR-4 and self-heals if PHP's cached class map is stale after an update (#305)
• Newly-added dashboard widgets now load their data immediately instead of staying empty until the page is refreshed.
• The pension detail panel's balance history and activity are no longer broken — those views called endpoints that didn't exist; they now show a proper balance chart and a merged timeline of contributions, withdrawals and balance updates, each removable (#251)
• Editing a split transaction with three or more parts no longer zeroes or overwrites the other splits. The last split row is now a read-only "remaining" amount (transaction total minus the other parts), and the dialog blocks saving until the parts add up (#303)
• Spending-anomaly notifications no longer crash with "The arguments array must contain 1 items, 0 given" — a stray % in the notification text made Nextcloud's translation layer fail, spamming the log every time notifications were rendered (#305)

Added

• The transaction list filters now include a Reconciled filter (All / Reconciled / Not reconciled), so you can quickly see which transactions still need reconciling (#301)
• A Budget alert threshold setting controls when a category appears on the Budget Alerts tile (default 80% of budget). Set it to 100% to be alerted only when a category actually goes over budget, rather than when it's merely approaching or fully used (#293)

Fixed

• Creating a category (or account) no longer fails with "Unknown column 'excluded_from_reports'" on instances where an earlier upgrade was interrupted or restored from a mid-upgrade backup. A self-healing migration re-adds the affected columns automatically on update (#302)

Fixed

• On some installs an earlier update was recorded as applied but didn't fully run (an interrupted upgrade, or a database restored from a backup taken mid-upgrade), leaving the excluded_from_forecast column missing — so every new transaction failed with "Unknown column 'excluded_from_forecast'". A migration now re-adds the column automatically on update. (Also surfaced by the new database-error detail field added in 2.32.0.) (#289)

Added

• Run reports on multiple accounts at once: the report Account filter is now a checklist — pick any set of accounts (e.g. all your credit cards, or all your checking accounts) or "All Accounts". Applies across the summary, spending, income, cash-flow, category-by-month and year-over-year reports and their CSV/PDF exports (#299)
• Saved reports: save a report's settings (type, period, selected accounts, tags and options) under a name and re-run it later from the "Saved Reports" picker in the Reports view. The period is stored as the chosen preset (e.g. "Last 3 months") so a saved report always shows up-to-date data (#299)
• Dashboard tiles that can be scoped to a specific account (Spending by Category, Income vs Expenses, Net Worth History, Recent Transactions, and the other account-aware widgets) now show a small label in their header naming the account they're analyzing — the account you picked in the tile's settings, or "All accounts" (#296)

Fixed

• The Reports period selector didn't drive the report on reopen: the dropdown kept your last choice (e.g. "Last Year") but the report always reverted to "Last 3 Months", and clicking "Generate Report" used the reverted range instead of the shown period — you had to switch the dropdown away and back. The report now always matches the period shown in the selector (custom ranges are preserved) (#300)
• The Quick Add Transaction dashboard widget couldn't be used on mobile — the lower fields and the "Add Transaction" button were clipped off the bottom of the tile, so a transaction could never be submitted. Its form is now condensed (each label sits beside its field with tighter spacing) so the whole form fits the tile, and it falls back to scrolling within the tile if it's resized very small (#298)
• Editing a split transaction's amount (e.g. inline in the transaction list) left its splits at the old amounts, so they no longer summed to the transaction total. The splits are now rescaled proportionally to the new amount (the last split absorbs any rounding remainder)
• In the edit-transaction dialog, changing one split amount now adjusts another split so the parts keep summing to the transaction total, instead of silently drifting out of balance
• Split transactions weren't counted toward category budgets or spending. When a single transaction was split across categories (e.g. one $1,000 payment split into rent, parking and a deposit), each of those categories showed $0 spent. Split allocations now count toward category spending everywhere it's shown — the Budget view, the Spending by Category chart, and reports (#297)
• Large amounts (e.g. values over 100,000) on the dashboard hero tiles (Net Worth, Income/Expenses This Month, Net Savings, Cash Flow) wrapped onto a second line, splitting the number mid-digits. The amount now stays on one line and its font scales down to fit narrow tiles instead of wrapping (#295)
• The "Asset Value History" dashboard tile (and "Net Worth History") showed its empty-state message anchored near the bottom of the tile instead of vertically centered. When there's no data the message now fills and centers within the chart area (#294)

Added

• Category by Month report: a new report (Reports → Category by Month) showing income and expenses per category broken down by month, with a column per month and an overall total. Categories are listed alphabetically with sub-categories grouped under their parents, and parent rows include the totals of their sub-categories; a toggle switches to sorting by total instead. Defaults to year-to-date, follows the report date-range and account filters, and exports to CSV and PDF (#288)

Changed

• API errors caused by the database now include the underlying driver message (e.g. a missing column) in a separate detail field of the error response, visible in the browser's network tab. The user-facing message is unchanged; this makes problems diagnosable on managed Nextcloud instances where admins can't read the server log. The executed SQL and any bound values are stripped from the detail (#289)

Fixed

• The dashboard "Budget Alerts" tile showed a red "exceeded" alert (with "0% over") for a category whose spending exactly equalled its budget. Spending that fully uses the budget without going over is now treated as a "100% used" warning, not an over-budget alert; only spending that actually exceeds the budget shows as exceeded (#293)
• PDF reports rendered non-Latin characters (Polish, Cyrillic, etc.) in account/category names as "?". The PDF exports used a built-in font limited to Western European characters; they now use an embedded Unicode font (DejaVu Sans), so names display correctly. Applies to the budget report, bills-calendar and year-over-year PDFs (#292)
• Marking a recurring transfer as paid showed a success message but created no account entries. The Transfers screen was only updating the transfer's "last paid" date instead of calling the mark-paid action, so no transactions were recorded; it now creates the paired transfer transactions like the Bills screen does (#291)

Added

• Exclude an account from totals: a per-account "Exclude from reports, dashboard & forecast" option (in the account's edit dialog) keeps the account fully tracked but leaves its transactions and balance out of every "all accounts" aggregation — reports, the dashboard, forecast, net worth, total balance and category budgets. The account still appears in your accounts list (with an "Excluded" badge) and on its own detail page, and selecting it explicitly in a report still works (#286)

Fixed

• The account detail page's overview tiles only counted the transactions on the visible page (e.g. "50" for an account with 1,603). "Total Transactions", "This Month Income", "This Month Expenses" and "Avg. Transaction" are now aggregated server-side over the whole account, so they're correct regardless of paging (#285)
• The dashboard spending chart's "Total Spending" figure (and each category's percentage) only summed the top 10 categories shown in the chart. It now reflects spending across all categories
• The CSV import preview's "Auto-categorized" count was estimated from a 50-row sample and could be wrong for larger imports; it's now counted over the full file on the server
• Editing an existing bill failed with "Failed to update bill" — saving the edit dialog (whether or not anything changed) returned a 400 error. The bill's start-date column, added with the limited-term bills feature, was missing from the list of updatable columns, so the always-sent start date was rejected before the save could run. Bills now save correctly, with a test guarding every persisted column (#284)
• Opening an account's detail page returned a 500 error (the reconciliation-history request failed). The reconciliation controller was missing a trait it relied on, so it couldn't be constructed and every reconciliation endpoint failed; the account page surfaced it via the history sidebar. Now fixed and covered by tests (#283)
• Starting an account reconciliation failed with a confusing "The string did not match the expected pattern" message (most visibly on Safari). The root cause was the reconciliation controller failing to construct (the #283 fix above resolves it); on top of that, the reconciliation screens now read error responses defensively, so any failure shows a clear message with the HTTP status instead of an opaque JSON-parsing error (#287)
• The Budget Overview dashboard widget (and the digest, spending-anomaly and bill-reminder notifications) always showed amounts in US dollars regardless of your configured currency. The server-side amount formatter was reading the wrong settings key and falling back to USD; it now uses your default currency
• The Budget Overview dashboard widget's "Total balance" now converts multi-currency accounts to your base currency instead of summing different currencies under one symbol (currencies without an exchange rate are excluded from the total and named)

Fixed

• Dropdowns in the transaction list (the column-configuration gear menu and the in-cell category/tag/account editors) were cut off when the table had only a few rows, because the table area was shorter than the dropdowns. The transaction table now fills the available height, so every dropdown has room to open in full (#280)
• The Tags column couldn't be shown/hidden — the Show/Hide Columns menu was missing a Tags entry, and the column wasn't wired into the visibility logic. Tags can now be toggled like the other columns (#281)

Security

• The recurring-income update endpoint no longer passes the raw request body through to the entity layer — a crafted payload could previously set internal fields such as the owning user (mass assignment, integrity only — no data disclosure). Update keys are now allowlisted like the other endpoints

Fixed

• Auto-derived recurring budgets (#269) are now consistent across all surfaces: the dashboard "Budget Remaining" hero, Budget Progress/Breakdown widgets, Budget Health score, and budget alerts now apply the same recurring fallback as the Budget view — a category funded only by recurring bills can now trigger alerts and is counted in headline totals
• Auto-derived budgets now respect bill start/end dates: a bill that hasn't started (or has ended) no longer counts toward today's budget, avoiding double-counting during a planned cost change (#268)
• Recurring income summaries (Income view header, dashboard Income Tracking widget): semi-monthly income was counted at half its value, and a one-time income at full value every month until received
• Transfers page monthly total: semi-monthly and semi-annual transfers were converted incorrectly
• Live forecast cache: cache invalidation never matched the stored key (changes such as toggling "exclude from forecast" appeared to do nothing for up to 5 minutes), and the cache key ignored shared-account visibility, letting a share-restricted viewer briefly see the owner's totals
• Editing a bill's amount without updating its split template is now rejected when the stored splits no longer match (the payment would have silently imported unsplit and uncategorized); setting a split template via the API now clears the bill-level category, matching creation
• Multi-account import partial failures (e.g. a deleted destination account) are now reported in the UI instead of masquerading as a full success
• Import preview now also flags repeated bank transaction IDs for accounts that will be created by the import
• Long OFX FITID hashing threshold raised so every previously-imported FITID keeps its exact ID (re-import dedup continuity)
• Auto-derived category budgets (#269) now handle every supported frequency correctly: semi-annual bills were over-counted 6×, semi-monthly halved, custom-schedule bills counted every month, and one-time bills inflated the budget monthly until marked paid (now excluded). Frequency math is delegated to the shared calculator, which also gained the missing semi-monthly conversion
• Auto-derived budgets no longer apply to past months — they reflect today's recurring bills/income and were rewriting history (including overriding explicitly-zeroed snapshot budgets)
• Multi-account import: an invalid destination account mid-import no longer aborts the batch, and deferred balance recomputes now always run for already-imported rows
• Bank sync: the post-import balance recompute now keys on transaction creation, not the import counter, so a row persisted just before a non-fatal error still gets its balance update
• The scheduled-transactions background job now recomputes balances from the ledger (it was the last remaining hand-computed balance delta, and could race concurrent imports)
• Import preview now flags a repeated bank transaction ID (OFX FITID) within one file as the duplicate it is, matching what import actually does; per-account preview counts include rows that will import with skip-duplicates off
• Marking a bill paid by linking an existing transaction now warns if the link silently failed (no money movement recorded)
• Extremely long OFX FITIDs are hashed to stay within the import-ID column

Fixed

• Dashboard could render half-empty (hero tiles only, widget grid invisible): a Chart.js resize on a hidden tile's detached canvas threw during initialization, and the widget grid was never revealed. Chart resizing now skips detached canvases and the grid is revealed before the resize pass. Likely also behind "nothing happens" reports after certain actions (#273)
• Dashboard tiles with a saved account selection pointing at a deleted account (e.g. after factory reset + import re-numbered accounts) no longer error with 404s and stay empty — stale selections fall back to all accounts
• Account balances are now derived from the ledger instead of running deltas — the root cause behind every historical balance-discrepancy report (#3, #89, #124, #163, #187, #194, #274). The stored balance was a running total that each transaction code path adjusted by hand; any missed or mis-signed delta corrupted it permanently. Every transaction create/update/delete (and retroactive rule run, repair action, import and bank sync) now recomputes balance = opening balance + net of non-scheduled transactions, making drift impossible and self-healing past inconsistencies on the next write. A one-time migration backfills the opening balance so displayed balances do not change on upgrade (#274)
• Marking a bill as paid now warns loudly when no transaction was recorded (bill without an account, or transaction creation failed) — previously the bill was advanced silently and the account balance never reflected the payment, drifting from the real bank balance every cycle (#89, #274)
• The app's own export→import now preserves transaction status (scheduled transactions no longer silently become balance-affecting after a migration) and restores the opening-balance invariant for imported accounts
• "Skip Duplicate Transactions" off is now honored: previously rows whose import ID already existed were still rejected deeper in the stack (duplicate-ID guard + unique index), so parts of the batch silently failed to import. Intentional duplicates now get a uniquified import ID and the entire batch imports (#275)
• Import duplicate detection no longer gives false positives for legitimately identical rows — e.g. two same-priced purchases on the same day with the same description. Identical rows within one file now import as distinct transactions (occurrence-aware import IDs), while re-importing the same statement still skips everything it already imported. Re-importing an older statement also recovers transactions the previous logic wrongly skipped (#276)

Fixed

• Install/upgrade aborted on Nextcloud 32 and earlier with "Primary index name on oc_budget_import_templates is too long". The budget_import_templates migration created its primary key without an explicit name, so Nextcloud derived a default name and hit the Oracle-compatibility identifier limit (the unprefixed table name is exactly 23 characters). The primary key now has an explicit short name. Thanks to @TheUnderdev for the report and fix (#272)

Added

• Shared savings goals — share a savings goal with another Nextcloud user. Recipients see a "Shared" badge and can view progress; with write permission they can edit the goal and add money, while only the owner can delete it (#255)
• Auto-derived budgets from recurring items — a (sub-)category with no manually-set budget now shows its committed recurring total (active recurring bills + recurring income, normalized to the budget period) as an automatic budget limit, marked "auto". Typing a value always overrides it (#269)
• Exclude extraordinary/one-time items from the forecast — a per-transaction "exclude from forecast" flag (with a "No forecast" list badge), the same flag on recurring bills/income (propagated to generated transactions), and a matching import-rule action. Flagged amounts still affect your balance but are kept out of the projection averages (#270)
• Reusable CSV import templates — save column mappings and import options and reapply them to future imports (#247)
• OFX/QIF import account routing — route multi-account OFX/QIF files to the right Budget accounts, remembered across subsequent imports
• Bank sync: pending transactions — option to import not-yet-posted (pending) transactions, automatically reconciled when they clear (#257)
• Bill start dates — a bill only occurs on or after its start date, making it easy to change a recurring cost mid-year by ending one bill and starting another (#268)
• "Shared with me" expenses view — recipients can now see expenses that have been shared with them (#248)
• Dashboard period indicator — chart tiles now show a read-only indicator of the period they cover (#250)

Fixed

• Dashboard now collapses to a single full-width column on phones, independent of your configured desktop column count (#249)
• "Excluded from reports" categories no longer appear in the Budget view (#266, #267)
• Category spending chart shows income as positive with the correct label (#265)
• Tag-linked savings goals now sum net realized contributions (credits minus debits, excluding scheduled) (#264)
• Recurring income description is now persisted on create (#263)
• Transfers are now excluded from dashboard income/expense totals (#262)
• Account Breakdown report now uses each account's own currency instead of a single assumed one (#256)
• Fixed a PageController crash (TypeError) on unauthenticated requests (#259)
• Quick Add date field normalization on iOS (#235)

Docs

• Documented the standalone Quick Add page and the iOS home-screen workaround
• Noted that GoCardless no longer accepts new bank-sync sign-ups; EU/UK self-hosters without an existing account are pointed to manual import (#271)

Added

• The Bills page now flags payments without a recorded transaction. A warning card lists bills that were marked paid in the last 60 days without a transaction being created or linked — the situation where the app balance silently detaches from the bank. Each entry has a one-click Record transaction repair that books the missing payment (dated the day it was marked paid, both legs for transfers, splits applied). Deliberate skips via the Skip button are not flagged (#274)
• QAR (Qatari Riyal) and JOD (Jordanian Dinar) are now available as account currencies. JOD amounts use the currency's native 3 decimal places. Automatic exchange rates cover both. Requested in #321

Fixed

• Editing a monthly recurring income never saved the changes — the app showed "Income saved successfully" but the Expected Day (and every other field) kept its old value. Any update whose payload contained an empty field (a monthly income always sends its yearly-only "expected month" as empty) reloaded the entity mid-save and threw away the edits. Thanks to @redsteadz for the fix (#324, #325)
• The "Exclude from forecast" checkbox on a transaction appeared unticked whenever the edit dialog was reopened, and saving the transaction again then really did reset the flag. The flag was stored correctly (including when set by an import rule) but the transaction list never sent it back to the browser, so the dialog always showed — and re-saved — it as off (#326)
• Income/Expenses This Month (and the other report summary totals) deducted transactions in "Exclude from reports" categories without converting them to the base currency, so on multi-currency setups the deduction was applied at the wrong rate — and for a single selected account the deduction wrongly included every other account's excluded transactions too (#326)
• Imports no longer bring in flagged duplicates by default. The preview's "Show duplicates" checkbox — on by default — secretly doubled as the skip-duplicates switch, so every import ran with duplicate-skipping off and rows flagged Duplicate were imported anyway. It is now purely a display filter; a new explicit "Import flagged duplicates too" option (off by default, resets each import) covers the deliberate re-import case. The preview's per-row checkboxes, which were never actually read by the import, are gone, and the New Transactions count no longer includes flagged duplicates (#327)
• Marking a bill paid no longer suggests unrelated transactions as "existing" matches. The Existing Transaction Found dialog offered any unlinked same-day debit as a candidate — cigarettes could be presented as a "match" for a mortgage — steering people into marking bills paid without recording the payment, the classic source of app-vs-bank balance drift. Candidates now must match the bill by amount or name, a weak match is never pre-selected (the safe default is creating the transaction), and the "Don't create any transaction" option now states — and warns after — that the account balance will not reflect the payment (#274)
• Overdue bills no longer double-book when marked paid. The scheduled placeholder pre-created for the next occurrence was written as an ordinary cleared transaction whenever the advanced due date was not in the future, so it counted toward the balance immediately — alongside the actual payment. Next-occurrence placeholders are now always scheduled, regardless of date
• Restoring a backup preserves every bill setting. The data import dropped most bill fields: custom recurrence patterns (restored bills then advanced one day at a time instead of quarterly/etc.), transfer destination and description pattern, auto-pay, reminder days, tags, split templates, start/end dates, remaining payments, forecast exclusion and the future-transaction opt-out

Changed

• The Match transfer dialog now also lists candidates from accounts in a different currency (any amount, within the date window), so cross-currency transfer pairs — e.g. imported from CSV — can finally be linked by hand. Automatic matching after imports is unchanged and still only links exact same-currency amounts (#326)

Fixed

• The account selector saved in the gear settings of insight tiles (Monthly Comparison, Large Transactions, Weekly Spending, Year-over-Year) was silently ignored — the tiles always showed all-accounts data. The saved account now actually scopes the tile's numbers
• Importing transactions that trigger the Auto-Link as Transfer rule action no longer shows "Cannot use object of type Transaction as array" on the import screen. The import itself always completed — the error came from the transfer-linking step afterwards, which also means those transfers were never actually linked (#314)
• The Recent Transactions dashboard tile now honors its "Rows to show" setting above 8 — the display respected the setting but the data fetch was hardcoded to 8 rows, so values of 9–20 silently showed only 8

Added

• Edit auto-categorization rules as JSON. The rule editor gains a Builder / JSON toggle. The JSON view shows the raw rule structure — editable and paste-friendly — checked when you save, and switching back to Builder repopulates the visual widgets. A Copy JSON button makes it easy to move a rule between instances (category/account IDs are instance-specific, as noted in the view). Requested in #318

• Hide shared categories from your own reports. Categories shared with you gain a per-viewer "Hide from my reports" toggle on the Categories page. Unlike the owner's "Exclude from reports" flag — which stays owner-only because it changes every viewer's reports at once — this only affects your own reports and dashboards; the owner and other viewers see no difference. Applied at the SQL layer through the same choke points as the owner flag, so every report and insight tile honors it consistently

• "Exclude shared accounts" on the remaining dashboard tiles. The per-tile toggle added in v2.37 now also covers Budget Progress, Monthly Comparison, Large Transactions, Weekly Spending, Category Trends, Cash Flow Forecast and Year-over-Year (shown in the gear menu when you have shared accounts). Bills, income and pension tiles are deliberately not included — they show entity data, not account aggregates

• Clickable spending charts. Clicking a slice (or bar) on the Spending by Category dashboard tile or the Reports page pie chart jumps to the transaction list filtered to that category, scoped to the chart's date range and account. Tiles set to "top-level only" include the subcategories in the filter so the listed transactions match the clicked amount (#317)

• Per-bill opt-out of pre-created transactions. The "Create future transaction for this bill" checkbox is now a persistent bill setting instead of a one-shot option at creation. Bills with it unticked never get a scheduled placeholder — not at creation, not after marking paid, not after skipping — and toggling it on an existing bill adds or removes the pending placeholder immediately. Previously the checkbox only affected the moment a bill was created, while every payment re-enabled pre-booking unconditionally, so unticking it never actually opted a bill out (#311)

• Convert a transaction into a transfer. The Match transfer dialog gains a "No match? Create the other side" section: pick one of your accounts and the app creates the opposite transaction there and links the pair as a transfer. Until now the dialog could only link two existing transactions, which left no way to correctly book payments to accounts that have nothing to import — e.g. a loan tracked as its own account (#313)

Changed

• Scheduled (future-dated) transactions now show a Scheduled badge in the main transaction list, with a tooltip explaining they are not counted until they occur. Previously only the account detail view had the badge and the main list showed scheduled rows in italics alone, which made a bill's pre-created next occurrence easy to mistake for a duplicate booking (#311)
• The transaction list Total no longer includes scheduled transactions — they are placeholders for money that has not moved yet (#311)

Added

• Exclude shared accounts from reports. When other people have shared accounts with you, the Reports page gains an "Exclude shared accounts" toggle so you can see just your own accounts' figures. The same option is available per-tile (in the gear menu) on the account-based dashboard cards — Income vs Expenses, Spending by Category, Top Spending Categories and Recent Transactions. It's off by default (shared accounts are included, as before) and only appears when you actually have shared accounts. Note: a transfer between one of your accounts and a shared account can only be partly seen when shared accounts are excluded, so income/expense totals may be slightly overstated in that case.

Fixed

• Saving share settings failed with "Some entities do not belong to you" (HTTP 400) when the "Auto-share new" toggle was enabled for a type, or after using Select All — the auto-share toggle (which shares the same data-type as the entity checkboxes) was being collected as a phantom entity and sent as a null id. Entity selection is now scoped precisely, so share settings save correctly with auto-share on (#306)

Changed

• The Categories page now also lists categories that have been shared with you, shown read-only with a "Shared · <owner>" badge. Previously it showed only your own categories, so anyone using a budget made up entirely of shared categories saw an empty page even though the categories worked everywhere else (#306)
• Categories shared with you at Edit permission are now editable — rename them and change their colour straight from the Categories page (they carry a "Shared (editable) · <owner>" badge). Read-only shares stay read-only, and a category's type, parent, budget, report visibility and deletion all remain owner-only (#306)

Added

• Auto-share new entities. Each person you share with now has an "Auto-share new" toggle per entity type (accounts, categories, bills, recurring income, savings goals) in their sharing settings. Turn it on and anything you create from then on is shared with them automatically, at the permission you choose — no more sharing each new bill or category by hand (#306)

Fixed

• Code-integrity "Some files have not passed the integrity check" errors reporting FILE_MISSING for js/.htaccess and vendor/tecnickcom/tcpdf/tools/.htaccess. The app no longer ships any .htaccess files — the Nextcloud App Store strips them from the published archive, which left the signature expecting files that were no longer present. Neither file was needed (the JS one only set a redundant cache header) (#307)
• Deprecation warning in the Nextcloud log — the notifier now throws UnknownNotificationException instead of InvalidArgumentException for unrecognised notifications, as required by Nextcloud 30+ (#308)
• Reports and the dashboard summary were empty when a single account flagged "Exclude from reports" was the only account selected. Accounts flagged out of reports are now only dropped from the all-accounts views; explicitly selecting one shows its data as normal (#309)

Fixed

• Categories marked "Exclude from reports" are now consistently excluded everywhere, including the Income vs Expenses trend, Category Trends, Top Spending Categories and the monthly spending chart — not just the dashboard summary. Exclusion is now applied in the database query itself, so reports and dashboard insight tiles can no longer disagree about which categories count (#219)

Added

• Pensions revamp. You can now record a contribution as a transfer from a bank account — the matching withdrawal is created automatically and kept out of your spending — and record withdrawals/drawdown back into an account (#304). Scheduled (recurring) contributions (monthly/quarterly/yearly) can post automatically or on demand (#251). DC pensions gained a configurable projection target with a progress indicator and a "today's money" (inflation-adjusted) view on the growth chart, plus an optional Pension Projection dashboard card. Bank legs that fund a pension show a Pension badge in the transaction list.

Fixed

• Background-job "class does not exist" log spam that could appear after updating PHP/Nextcloud/the app: the app's autoloader is no longer "authoritative", so it falls back to PSR-4 and self-heals if PHP's cached class map is stale after an update (#305)
• Newly-added dashboard widgets now load their data immediately instead of staying empty until the page is refreshed.
• The pension detail panel's balance history and activity are no longer broken — those views called endpoints that didn't exist; they now show a proper balance chart and a merged timeline of contributions, withdrawals and balance updates, each removable (#251)
• Editing a split transaction with three or more parts no longer zeroes or overwrites the other splits. The last split row is now a read-only "remaining" amount (transaction total minus the other parts), and the dialog blocks saving until the parts add up (#303)
• Spending-anomaly notifications no longer crash with "The arguments array must contain 1 items, 0 given" — a stray % in the notification text made Nextcloud's translation layer fail, spamming the log every time notifications were rendered (#305)

Added

• The transaction list filters now include a Reconciled filter (All / Reconciled / Not reconciled), so you can quickly see which transactions still need reconciling (#301)
• A Budget alert threshold setting controls when a category appears on the Budget Alerts tile (default 80% of budget). Set it to 100% to be alerted only when a category actually goes over budget, rather than when it's merely approaching or fully used (#293)

Fixed

• Creating a category (or account) no longer fails with "Unknown column 'excluded_from_reports'" on instances where an earlier upgrade was interrupted or restored from a mid-upgrade backup. A self-healing migration re-adds the affected columns automatically on update (#302)

Fixed

• On some installs an earlier update was recorded as applied but didn't fully run (an interrupted upgrade, or a database restored from a backup taken mid-upgrade), leaving the excluded_from_forecast column missing — so every new transaction failed with "Unknown column 'excluded_from_forecast'". A migration now re-adds the column automatically on update. (Also surfaced by the new database-error detail field added in 2.32.0.) (#289)

Added

• Run reports on multiple accounts at once: the report Account filter is now a checklist — pick any set of accounts (e.g. all your credit cards, or all your checking accounts) or "All Accounts". Applies across the summary, spending, income, cash-flow, category-by-month and year-over-year reports and their CSV/PDF exports (#299)
• Saved reports: save a report's settings (type, period, selected accounts, tags and options) under a name and re-run it later from the "Saved Reports" picker in the Reports view. The period is stored as the chosen preset (e.g. "Last 3 months") so a saved report always shows up-to-date data (#299)
• Dashboard tiles that can be scoped to a specific account (Spending by Category, Income vs Expenses, Net Worth History, Recent Transactions, and the other account-aware widgets) now show a small label in their header naming the account they're analyzing — the account you picked in the tile's settings, or "All accounts" (#296)

Fixed

• The Reports period selector didn't drive the report on reopen: the dropdown kept your last choice (e.g. "Last Year") but the report always reverted to "Last 3 Months", and clicking "Generate Report" used the reverted range instead of the shown period — you had to switch the dropdown away and back. The report now always matches the period shown in the selector (custom ranges are preserved) (#300)
• The Quick Add Transaction dashboard widget couldn't be used on mobile — the lower fields and the "Add Transaction" button were clipped off the bottom of the tile, so a transaction could never be submitted. Its form is now condensed (each label sits beside its field with tighter spacing) so the whole form fits the tile, and it falls back to scrolling within the tile if it's resized very small (#298)
• Editing a split transaction's amount (e.g. inline in the transaction list) left its splits at the old amounts, so they no longer summed to the transaction total. The splits are now rescaled proportionally to the new amount (the last split absorbs any rounding remainder)
• In the edit-transaction dialog, changing one split amount now adjusts another split so the parts keep summing to the transaction total, instead of silently drifting out of balance
• Split transactions weren't counted toward category budgets or spending. When a single transaction was split across categories (e.g. one $1,000 payment split into rent, parking and a deposit), each of those categories showed $0 spent. Split allocations now count toward category spending everywhere it's shown — the Budget view, the Spending by Category chart, and reports (#297)
• Large amounts (e.g. values over 100,000) on the dashboard hero tiles (Net Worth, Income/Expenses This Month, Net Savings, Cash Flow) wrapped onto a second line, splitting the number mid-digits. The amount now stays on one line and its font scales down to fit narrow tiles instead of wrapping (#295)
• The "Asset Value History" dashboard tile (and "Net Worth History") showed its empty-state message anchored near the bottom of the tile instead of vertically centered. When there's no data the message now fills and centers within the chart area (#294)

Added

• Category by Month report: a new report (Reports → Category by Month) showing income and expenses per category broken down by month, with a column per month and an overall total. Categories are listed alphabetically with sub-categories grouped under their parents, and parent rows include the totals of their sub-categories; a toggle switches to sorting by total instead. Defaults to year-to-date, follows the report date-range and account filters, and exports to CSV and PDF (#288)

Changed

• API errors caused by the database now include the underlying driver message (e.g. a missing column) in a separate detail field of the error response, visible in the browser's network tab. The user-facing message is unchanged; this makes problems diagnosable on managed Nextcloud instances where admins can't read the server log. The executed SQL and any bound values are stripped from the detail (#289)

Fixed

• The dashboard "Budget Alerts" tile showed a red "exceeded" alert (with "0% over") for a category whose spending exactly equalled its budget. Spending that fully uses the budget without going over is now treated as a "100% used" warning, not an over-budget alert; only spending that actually exceeds the budget shows as exceeded (#293)
• PDF reports rendered non-Latin characters (Polish, Cyrillic, etc.) in account/category names as "?". The PDF exports used a built-in font limited to Western European characters; they now use an embedded Unicode font (DejaVu Sans), so names display correctly. Applies to the budget report, bills-calendar and year-over-year PDFs (#292)
• Marking a recurring transfer as paid showed a success message but created no account entries. The Transfers screen was only updating the transfer's "last paid" date instead of calling the mark-paid action, so no transactions were recorded; it now creates the paired transfer transactions like the Bills screen does (#291)

Added

• Exclude an account from totals: a per-account "Exclude from reports, dashboard & forecast" option (in the account's edit dialog) keeps the account fully tracked but leaves its transactions and balance out of every "all accounts" aggregation — reports, the dashboard, forecast, net worth, total balance and category budgets. The account still appears in your accounts list (with an "Excluded" badge) and on its own detail page, and selecting it explicitly in a report still works (#286)

Fixed

• The account detail page's overview tiles only counted the transactions on the visible page (e.g. "50" for an account with 1,603). "Total Transactions", "This Month Income", "This Month Expenses" and "Avg. Transaction" are now aggregated server-side over the whole account, so they're correct regardless of paging (#285)
• The dashboard spending chart's "Total Spending" figure (and each category's percentage) only summed the top 10 categories shown in the chart. It now reflects spending across all categories
• The CSV import preview's "Auto-categorized" count was estimated from a 50-row sample and could be wrong for larger imports; it's now counted over the full file on the server
• Editing an existing bill failed with "Failed to update bill" — saving the edit dialog (whether or not anything changed) returned a 400 error. The bill's start-date column, added with the limited-term bills feature, was missing from the list of updatable columns, so the always-sent start date was rejected before the save could run. Bills now save correctly, with a test guarding every persisted column (#284)
• Opening an account's detail page returned a 500 error (the reconciliation-history request failed). The reconciliation controller was missing a trait it relied on, so it couldn't be constructed and every reconciliation endpoint failed; the account page surfaced it via the history sidebar. Now fixed and covered by tests (#283)
• Starting an account reconciliation failed with a confusing "The string did not match the expected pattern" message (most visibly on Safari). The root cause was the reconciliation controller failing to construct (the #283 fix above resolves it); on top of that, the reconciliation screens now read error responses defensively, so any failure shows a clear message with the HTTP status instead of an opaque JSON-parsing error (#287)
• The Budget Overview dashboard widget (and the digest, spending-anomaly and bill-reminder notifications) always showed amounts in US dollars regardless of your configured currency. The server-side amount formatter was reading the wrong settings key and falling back to USD; it now uses your default currency
• The Budget Overview dashboard widget's "Total balance" now converts multi-currency accounts to your base currency instead of summing different currencies under one symbol (currencies without an exchange rate are excluded from the total and named)

Fixed

• Dropdowns in the transaction list (the column-configuration gear menu and the in-cell category/tag/account editors) were cut off when the table had only a few rows, because the table area was shorter than the dropdowns. The transaction table now fills the available height, so every dropdown has room to open in full (#280)
• The Tags column couldn't be shown/hidden — the Show/Hide Columns menu was missing a Tags entry, and the column wasn't wired into the visibility logic. Tags can now be toggled like the other columns (#281)

Security

• The recurring-income update endpoint no longer passes the raw request body through to the entity layer — a crafted payload could previously set internal fields such as the owning user (mass assignment, integrity only — no data disclosure). Update keys are now allowlisted like the other endpoints

Fixed

• Auto-derived recurring budgets (#269) are now consistent across all surfaces: the dashboard "Budget Remaining" hero, Budget Progress/Breakdown widgets, Budget Health score, and budget alerts now apply the same recurring fallback as the Budget view — a category funded only by recurring bills can now trigger alerts and is counted in headline totals
• Auto-derived budgets now respect bill start/end dates: a bill that hasn't started (or has ended) no longer counts toward today's budget, avoiding double-counting during a planned cost change (#268)
• Recurring income summaries (Income view header, dashboard Income Tracking widget): semi-monthly income was counted at half its value, and a one-time income at full value every month until received
• Transfers page monthly total: semi-monthly and semi-annual transfers were converted incorrectly
• Live forecast cache: cache invalidation never matched the stored key (changes such as toggling "exclude from forecast" appeared to do nothing for up to 5 minutes), and the cache key ignored shared-account visibility, letting a share-restricted viewer briefly see the owner's totals
• Editing a bill's amount without updating its split template is now rejected when the stored splits no longer match (the payment would have silently imported unsplit and uncategorized); setting a split template via the API now clears the bill-level category, matching creation
• Multi-account import partial failures (e.g. a deleted destination account) are now reported in the UI instead of masquerading as a full success
• Import preview now also flags repeated bank transaction IDs for accounts that will be created by the import
• Long OFX FITID hashing threshold raised so every previously-imported FITID keeps its exact ID (re-import dedup continuity)
• Auto-derived category budgets (#269) now handle every supported frequency correctly: semi-annual bills were over-counted 6×, semi-monthly halved, custom-schedule bills counted every month, and one-time bills inflated the budget monthly until marked paid (now excluded). Frequency math is delegated to the shared calculator, which also gained the missing semi-monthly conversion
• Auto-derived budgets no longer apply to past months — they reflect today's recurring bills/income and were rewriting history (including overriding explicitly-zeroed snapshot budgets)
• Multi-account import: an invalid destination account mid-import no longer aborts the batch, and deferred balance recomputes now always run for already-imported rows
• Bank sync: the post-import balance recompute now keys on transaction creation, not the import counter, so a row persisted just before a non-fatal error still gets its balance update
• The scheduled-transactions background job now recomputes balances from the ledger (it was the last remaining hand-computed balance delta, and could race concurrent imports)
• Import preview now flags a repeated bank transaction ID (OFX FITID) within one file as the duplicate it is, matching what import actually does; per-account preview counts include rows that will import with skip-duplicates off
• Marking a bill paid by linking an existing transaction now warns if the link silently failed (no money movement recorded)
• Extremely long OFX FITIDs are hashed to stay within the import-ID column

Fixed

• Dashboard could render half-empty (hero tiles only, widget grid invisible): a Chart.js resize on a hidden tile's detached canvas threw during initialization, and the widget grid was never revealed. Chart resizing now skips detached canvases and the grid is revealed before the resize pass. Likely also behind "nothing happens" reports after certain actions (#273)
• Dashboard tiles with a saved account selection pointing at a deleted account (e.g. after factory reset + import re-numbered accounts) no longer error with 404s and stay empty — stale selections fall back to all accounts
• Account balances are now derived from the ledger instead of running deltas — the root cause behind every historical balance-discrepancy report (#3, #89, #124, #163, #187, #194, #274). The stored balance was a running total that each transaction code path adjusted by hand; any missed or mis-signed delta corrupted it permanently. Every transaction create/update/delete (and retroactive rule run, repair action, import and bank sync) now recomputes balance = opening balance + net of non-scheduled transactions, making drift impossible and self-healing past inconsistencies on the next write. A one-time migration backfills the opening balance so displayed balances do not change on upgrade (#274)
• Marking a bill as paid now warns loudly when no transaction was recorded (bill without an account, or transaction creation failed) — previously the bill was advanced silently and the account balance never reflected the payment, drifting from the real bank balance every cycle (#89, #274)
• The app's own export→import now preserves transaction status (scheduled transactions no longer silently become balance-affecting after a migration) and restores the opening-balance invariant for imported accounts
• "Skip Duplicate Transactions" off is now honored: previously rows whose import ID already existed were still rejected deeper in the stack (duplicate-ID guard + unique index), so parts of the batch silently failed to import. Intentional duplicates now get a uniquified import ID and the entire batch imports (#275)
• Import duplicate detection no longer gives false positives for legitimately identical rows — e.g. two same-priced purchases on the same day with the same description. Identical rows within one file now import as distinct transactions (occurrence-aware import IDs), while re-importing the same statement still skips everything it already imported. Re-importing an older statement also recovers transactions the previous logic wrongly skipped (#276)

Fixed

• Install/upgrade aborted on Nextcloud 32 and earlier with "Primary index name on oc_budget_import_templates is too long". The budget_import_templates migration created its primary key without an explicit name, so Nextcloud derived a default name and hit the Oracle-compatibility identifier limit (the unprefixed table name is exactly 23 characters). The primary key now has an explicit short name. Thanks to @TheUnderdev for the report and fix (#272)

Added

• Shared savings goals — share a savings goal with another Nextcloud user. Recipients see a "Shared" badge and can view progress; with write permission they can edit the goal and add money, while only the owner can delete it (#255)
• Auto-derived budgets from recurring items — a (sub-)category with no manually-set budget now shows its committed recurring total (active recurring bills + recurring income, normalized to the budget period) as an automatic budget limit, marked "auto". Typing a value always overrides it (#269)
• Exclude extraordinary/one-time items from the forecast — a per-transaction "exclude from forecast" flag (with a "No forecast" list badge), the same flag on recurring bills/income (propagated to generated transactions), and a matching import-rule action. Flagged amounts still affect your balance but are kept out of the projection averages (#270)
• Reusable CSV import templates — save column mappings and import options and reapply them to future imports (#247)
• OFX/QIF import account routing — route multi-account OFX/QIF files to the right Budget accounts, remembered across subsequent imports
• Bank sync: pending transactions — option to import not-yet-posted (pending) transactions, automatically reconciled when they clear (#257)
• Bill start dates — a bill only occurs on or after its start date, making it easy to change a recurring cost mid-year by ending one bill and starting another (#268)
• "Shared with me" expenses view — recipients can now see expenses that have been shared with them (#248)
• Dashboard period indicator — chart tiles now show a read-only indicator of the period they cover (#250)

Fixed

• Dashboard now collapses to a single full-width column on phones, independent of your configured desktop column count (#249)
• "Excluded from reports" categories no longer appear in the Budget view (#266, #267)
• Category spending chart shows income as positive with the correct label (#265)
• Tag-linked savings goals now sum net realized contributions (credits minus debits, excluding scheduled) (#264)
• Recurring income description is now persisted on create (#263)
• Transfers are now excluded from dashboard income/expense totals (#262)
• Account Breakdown report now uses each account's own currency instead of a single assumed one (#256)
• Fixed a PageController crash (TypeError) on unauthenticated requests (#259)
• Quick Add date field normalization on iOS (#235)

Docs

• Documented the standalone Quick Add page and the iOS home-screen workaround
• Noted that GoCardless no longer accepts new bank-sync sign-ups; EU/UK self-hosters without an existing account are pointed to manual import (#271)

Added

• The Bills page now flags payments without a recorded transaction. A warning card lists bills that were marked paid in the last 60 days without a transaction being created or linked — the situation where the app balance silently detaches from the bank. Each entry has a one-click Record transaction repair that books the missing payment (dated the day it was marked paid, both legs for transfers, splits applied). Deliberate skips via the Skip button are not flagged (#274)
• QAR (Qatari Riyal) and JOD (Jordanian Dinar) are now available as account currencies. JOD amounts use the currency's native 3 decimal places. Automatic exchange rates cover both. Requested in #321

Fixed

• Editing a monthly recurring income never saved the changes — the app showed "Income saved successfully" but the Expected Day (and every other field) kept its old value. Any update whose payload contained an empty field (a monthly income always sends its yearly-only "expected month" as empty) reloaded the entity mid-save and threw away the edits. Thanks to @redsteadz for the fix (#324, #325)
• The "Exclude from forecast" checkbox on a transaction appeared unticked whenever the edit dialog was reopened, and saving the transaction again then really did reset the flag. The flag was stored correctly (including when set by an import rule) but the transaction list never sent it back to the browser, so the dialog always showed — and re-saved — it as off (#326)
• Income/Expenses This Month (and the other report summary totals) deducted transactions in "Exclude from reports" categories without converting them to the base currency, so on multi-currency setups the deduction was applied at the wrong rate — and for a single selected account the deduction wrongly included every other account's excluded transactions too (#326)
• Imports no longer bring in flagged duplicates by default. The preview's "Show duplicates" checkbox — on by default — secretly doubled as the skip-duplicates switch, so every import ran with duplicate-skipping off and rows flagged Duplicate were imported anyway. It is now purely a display filter; a new explicit "Import flagged duplicates too" option (off by default, resets each import) covers the deliberate re-import case. The preview's per-row checkboxes, which were never actually read by the import, are gone, and the New Transactions count no longer includes flagged duplicates (#327)
• Marking a bill paid no longer suggests unrelated transactions as "existing" matches. The Existing Transaction Found dialog offered any unlinked same-day debit as a candidate — cigarettes could be presented as a "match" for a mortgage — steering people into marking bills paid without recording the payment, the classic source of app-vs-bank balance drift. Candidates now must match the bill by amount or name, a weak match is never pre-selected (the safe default is creating the transaction), and the "Don't create any transaction" option now states — and warns after — that the account balance will not reflect the payment (#274)
• Overdue bills no longer double-book when marked paid. The scheduled placeholder pre-created for the next occurrence was written as an ordinary cleared transaction whenever the advanced due date was not in the future, so it counted toward the balance immediately — alongside the actual payment. Next-occurrence placeholders are now always scheduled, regardless of date
• Restoring a backup preserves every bill setting. The data import dropped most bill fields: custom recurrence patterns (restored bills then advanced one day at a time instead of quarterly/etc.), transfer destination and description pattern, auto-pay, reminder days, tags, split templates, start/end dates, remaining payments, forecast exclusion and the future-transaction opt-out

Changed

• The Match transfer dialog now also lists candidates from accounts in a different currency (any amount, within the date window), so cross-currency transfer pairs — e.g. imported from CSV — can finally be linked by hand. Automatic matching after imports is unchanged and still only links exact same-currency amounts (#326)

Fixed

• The account selector saved in the gear settings of insight tiles (Monthly Comparison, Large Transactions, Weekly Spending, Year-over-Year) was silently ignored — the tiles always showed all-accounts data. The saved account now actually scopes the tile's numbers
• Importing transactions that trigger the Auto-Link as Transfer rule action no longer shows "Cannot use object of type Transaction as array" on the import screen. The import itself always completed — the error came from the transfer-linking step afterwards, which also means those transfers were never actually linked (#314)
• The Recent Transactions dashboard tile now honors its "Rows to show" setting above 8 — the display respected the setting but the data fetch was hardcoded to 8 rows, so values of 9–20 silently showed only 8

Added

• Edit auto-categorization rules as JSON. The rule editor gains a Builder / JSON toggle. The JSON view shows the raw rule structure — editable and paste-friendly — checked when you save, and switching back to Builder repopulates the visual widgets. A Copy JSON button makes it easy to move a rule between instances (category/account IDs are instance-specific, as noted in the view). Requested in #318

• Hide shared categories from your own reports. Categories shared with you gain a per-viewer "Hide from my reports" toggle on the Categories page. Unlike the owner's "Exclude from reports" flag — which stays owner-only because it changes every viewer's reports at once — this only affects your own reports and dashboards; the owner and other viewers see no difference. Applied at the SQL layer through the same choke points as the owner flag, so every report and insight tile honors it consistently

• "Exclude shared accounts" on the remaining dashboard tiles. The per-tile toggle added in v2.37 now also covers Budget Progress, Monthly Comparison, Large Transactions, Weekly Spending, Category Trends, Cash Flow Forecast and Year-over-Year (shown in the gear menu when you have shared accounts). Bills, income and pension tiles are deliberately not included — they show entity data, not account aggregates

• Clickable spending charts. Clicking a slice (or bar) on the Spending by Category dashboard tile or the Reports page pie chart jumps to the transaction list filtered to that category, scoped to the chart's date range and account. Tiles set to "top-level only" include the subcategories in the filter so the listed transactions match the clicked amount (#317)

• Per-bill opt-out of pre-created transactions. The "Create future transaction for this bill" checkbox is now a persistent bill setting instead of a one-shot option at creation. Bills with it unticked never get a scheduled placeholder — not at creation, not after marking paid, not after skipping — and toggling it on an existing bill adds or removes the pending placeholder immediately. Previously the checkbox only affected the moment a bill was created, while every payment re-enabled pre-booking unconditionally, so unticking it never actually opted a bill out (#311)

• Convert a transaction into a transfer. The Match transfer dialog gains a "No match? Create the other side" section: pick one of your accounts and the app creates the opposite transaction there and links the pair as a transfer. Until now the dialog could only link two existing transactions, which left no way to correctly book payments to accounts that have nothing to import — e.g. a loan tracked as its own account (#313)

Changed

• Scheduled (future-dated) transactions now show a Scheduled badge in the main transaction list, with a tooltip explaining they are not counted until they occur. Previously only the account detail view had the badge and the main list showed scheduled rows in italics alone, which made a bill's pre-created next occurrence easy to mistake for a duplicate booking (#311)
• The transaction list Total no longer includes scheduled transactions — they are placeholders for money that has not moved yet (#311)

Added

• Exclude shared accounts from reports. When other people have shared accounts with you, the Reports page gains an "Exclude shared accounts" toggle so you can see just your own accounts' figures. The same option is available per-tile (in the gear menu) on the account-based dashboard cards — Income vs Expenses, Spending by Category, Top Spending Categories and Recent Transactions. It's off by default (shared accounts are included, as before) and only appears when you actually have shared accounts. Note: a transfer between one of your accounts and a shared account can only be partly seen when shared accounts are excluded, so income/expense totals may be slightly overstated in that case.

Fixed

• Saving share settings failed with "Some entities do not belong to you" (HTTP 400) when the "Auto-share new" toggle was enabled for a type, or after using Select All — the auto-share toggle (which shares the same data-type as the entity checkboxes) was being collected as a phantom entity and sent as a null id. Entity selection is now scoped precisely, so share settings save correctly with auto-share on (#306)

Changed

• The Categories page now also lists categories that have been shared with you, shown read-only with a "Shared · <owner>" badge. Previously it showed only your own categories, so anyone using a budget made up entirely of shared categories saw an empty page even though the categories worked everywhere else (#306)
• Categories shared with you at Edit permission are now editable — rename them and change their colour straight from the Categories page (they carry a "Shared (editable) · <owner>" badge). Read-only shares stay read-only, and a category's type, parent, budget, report visibility and deletion all remain owner-only (#306)

Added

• Auto-share new entities. Each person you share with now has an "Auto-share new" toggle per entity type (accounts, categories, bills, recurring income, savings goals) in their sharing settings. Turn it on and anything you create from then on is shared with them automatically, at the permission you choose — no more sharing each new bill or category by hand (#306)

Fixed

• Code-integrity "Some files have not passed the integrity check" errors reporting FILE_MISSING for js/.htaccess and vendor/tecnickcom/tcpdf/tools/.htaccess. The app no longer ships any .htaccess files — the Nextcloud App Store strips them from the published archive, which left the signature expecting files that were no longer present. Neither file was needed (the JS one only set a redundant cache header) (#307)
• Deprecation warning in the Nextcloud log — the notifier now throws UnknownNotificationException instead of InvalidArgumentException for unrecognised notifications, as required by Nextcloud 30+ (#308)
• Reports and the dashboard summary were empty when a single account flagged "Exclude from reports" was the only account selected. Accounts flagged out of reports are now only dropped from the all-accounts views; explicitly selecting one shows its data as normal (#309)

Fixed

• Categories marked "Exclude from reports" are now consistently excluded everywhere, including the Income vs Expenses trend, Category Trends, Top Spending Categories and the monthly spending chart — not just the dashboard summary. Exclusion is now applied in the database query itself, so reports and dashboard insight tiles can no longer disagree about which categories count (#219)

Added

• Pensions revamp. You can now record a contribution as a transfer from a bank account — the matching withdrawal is created automatically and kept out of your spending — and record withdrawals/drawdown back into an account (#304). Scheduled (recurring) contributions (monthly/quarterly/yearly) can post automatically or on demand (#251). DC pensions gained a configurable projection target with a progress indicator and a "today's money" (inflation-adjusted) view on the growth chart, plus an optional Pension Projection dashboard card. Bank legs that fund a pension show a Pension badge in the transaction list.

Fixed

• Background-job "class does not exist" log spam that could appear after updating PHP/Nextcloud/the app: the app's autoloader is no longer "authoritative", so it falls back to PSR-4 and self-heals if PHP's cached class map is stale after an update (#305)
• Newly-added dashboard widgets now load their data immediately instead of staying empty until the page is refreshed.
• The pension detail panel's balance history and activity are no longer broken — those views called endpoints that didn't exist; they now show a proper balance chart and a merged timeline of contributions, withdrawals and balance updates, each removable (#251)
• Editing a split transaction with three or more parts no longer zeroes or overwrites the other splits. The last split row is now a read-only "remaining" amount (transaction total minus the other parts), and the dialog blocks saving until the parts add up (#303)
• Spending-anomaly notifications no longer crash with "The arguments array must contain 1 items, 0 given" — a stray % in the notification text made Nextcloud's translation layer fail, spamming the log every time notifications were rendered (#305)

Added

• The transaction list filters now include a Reconciled filter (All / Reconciled / Not reconciled), so you can quickly see which transactions still need reconciling (#301)
• A Budget alert threshold setting controls when a category appears on the Budget Alerts tile (default 80% of budget). Set it to 100% to be alerted only when a category actually goes over budget, rather than when it's merely approaching or fully used (#293)

Fixed

• Creating a category (or account) no longer fails with "Unknown column 'excluded_from_reports'" on instances where an earlier upgrade was interrupted or restored from a mid-upgrade backup. A self-healing migration re-adds the affected columns automatically on update (#302)

Fixed

• On some installs an earlier update was recorded as applied but didn't fully run (an interrupted upgrade, or a database restored from a backup taken mid-upgrade), leaving the excluded_from_forecast column missing — so every new transaction failed with "Unknown column 'excluded_from_forecast'". A migration now re-adds the column automatically on update. (Also surfaced by the new database-error detail field added in 2.32.0.) (#289)

Added

• Run reports on multiple accounts at once: the report Account filter is now a checklist — pick any set of accounts (e.g. all your credit cards, or all your checking accounts) or "All Accounts". Applies across the summary, spending, income, cash-flow, category-by-month and year-over-year reports and their CSV/PDF exports (#299)
• Saved reports: save a report's settings (type, period, selected accounts, tags and options) under a name and re-run it later from the "Saved Reports" picker in the Reports view. The period is stored as the chosen preset (e.g. "Last 3 months") so a saved report always shows up-to-date data (#299)
• Dashboard tiles that can be scoped to a specific account (Spending by Category, Income vs Expenses, Net Worth History, Recent Transactions, and the other account-aware widgets) now show a small label in their header naming the account they're analyzing — the account you picked in the tile's settings, or "All accounts" (#296)

Fixed

• The Reports period selector didn't drive the report on reopen: the dropdown kept your last choice (e.g. "Last Year") but the report always reverted to "Last 3 Months", and clicking "Generate Report" used the reverted range instead of the shown period — you had to switch the dropdown away and back. The report now always matches the period shown in the selector (custom ranges are preserved) (#300)
• The Quick Add Transaction dashboard widget couldn't be used on mobile — the lower fields and the "Add Transaction" button were clipped off the bottom of the tile, so a transaction could never be submitted. Its form is now condensed (each label sits beside its field with tighter spacing) so the whole form fits the tile, and it falls back to scrolling within the tile if it's resized very small (#298)
• Editing a split transaction's amount (e.g. inline in the transaction list) left its splits at the old amounts, so they no longer summed to the transaction total. The splits are now rescaled proportionally to the new amount (the last split absorbs any rounding remainder)
• In the edit-transaction dialog, changing one split amount now adjusts another split so the parts keep summing to the transaction total, instead of silently drifting out of balance
• Split transactions weren't counted toward category budgets or spending. When a single transaction was split across categories (e.g. one $1,000 payment split into rent, parking and a deposit), each of those categories showed $0 spent. Split allocations now count toward category spending everywhere it's shown — the Budget view, the Spending by Category chart, and reports (#297)
• Large amounts (e.g. values over 100,000) on the dashboard hero tiles (Net Worth, Income/Expenses This Month, Net Savings, Cash Flow) wrapped onto a second line, splitting the number mid-digits. The amount now stays on one line and its font scales down to fit narrow tiles instead of wrapping (#295)
• The "Asset Value History" dashboard tile (and "Net Worth History") showed its empty-state message anchored near the bottom of the tile instead of vertically centered. When there's no data the message now fills and centers within the chart area (#294)

Added

• Category by Month report: a new report (Reports → Category by Month) showing income and expenses per category broken down by month, with a column per month and an overall total. Categories are listed alphabetically with sub-categories grouped under their parents, and parent rows include the totals of their sub-categories; a toggle switches to sorting by total instead. Defaults to year-to-date, follows the report date-range and account filters, and exports to CSV and PDF (#288)

Changed

• API errors caused by the database now include the underlying driver message (e.g. a missing column) in a separate detail field of the error response, visible in the browser's network tab. The user-facing message is unchanged; this makes problems diagnosable on managed Nextcloud instances where admins can't read the server log. The executed SQL and any bound values are stripped from the detail (#289)

Fixed

• The dashboard "Budget Alerts" tile showed a red "exceeded" alert (with "0% over") for a category whose spending exactly equalled its budget. Spending that fully uses the budget without going over is now treated as a "100% used" warning, not an over-budget alert; only spending that actually exceeds the budget shows as exceeded (#293)
• PDF reports rendered non-Latin characters (Polish, Cyrillic, etc.) in account/category names as "?". The PDF exports used a built-in font limited to Western European characters; they now use an embedded Unicode font (DejaVu Sans), so names display correctly. Applies to the budget report, bills-calendar and year-over-year PDFs (#292)
• Marking a recurring transfer as paid showed a success message but created no account entries. The Transfers screen was only updating the transfer's "last paid" date instead of calling the mark-paid action, so no transactions were recorded; it now creates the paired transfer transactions like the Bills screen does (#291)

Added

• Exclude an account from totals: a per-account "Exclude from reports, dashboard & forecast" option (in the account's edit dialog) keeps the account fully tracked but leaves its transactions and balance out of every "all accounts" aggregation — reports, the dashboard, forecast, net worth, total balance and category budgets. The account still appears in your accounts list (with an "Excluded" badge) and on its own detail page, and selecting it explicitly in a report still works (#286)

Fixed

• The account detail page's overview tiles only counted the transactions on the visible page (e.g. "50" for an account with 1,603). "Total Transactions", "This Month Income", "This Month Expenses" and "Avg. Transaction" are now aggregated server-side over the whole account, so they're correct regardless of paging (#285)
• The dashboard spending chart's "Total Spending" figure (and each category's percentage) only summed the top 10 categories shown in the chart. It now reflects spending across all categories
• The CSV import preview's "Auto-categorized" count was estimated from a 50-row sample and could be wrong for larger imports; it's now counted over the full file on the server
• Editing an existing bill failed with "Failed to update bill" — saving the edit dialog (whether or not anything changed) returned a 400 error. The bill's start-date column, added with the limited-term bills feature, was missing from the list of updatable columns, so the always-sent start date was rejected before the save could run. Bills now save correctly, with a test guarding every persisted column (#284)
• Opening an account's detail page returned a 500 error (the reconciliation-history request failed). The reconciliation controller was missing a trait it relied on, so it couldn't be constructed and every reconciliation endpoint failed; the account page surfaced it via the history sidebar. Now fixed and covered by tests (#283)
• Starting an account reconciliation failed with a confusing "The string did not match the expected pattern" message (most visibly on Safari). The root cause was the reconciliation controller failing to construct (the #283 fix above resolves it); on top of that, the reconciliation screens now read error responses defensively, so any failure shows a clear message with the HTTP status instead of an opaque JSON-parsing error (#287)
• The Budget Overview dashboard widget (and the digest, spending-anomaly and bill-reminder notifications) always showed amounts in US dollars regardless of your configured currency. The server-side amount formatter was reading the wrong settings key and falling back to USD; it now uses your default currency
• The Budget Overview dashboard widget's "Total balance" now converts multi-currency accounts to your base currency instead of summing different currencies under one symbol (currencies without an exchange rate are excluded from the total and named)

Fixed

• Dropdowns in the transaction list (the column-configuration gear menu and the in-cell category/tag/account editors) were cut off when the table had only a few rows, because the table area was shorter than the dropdowns. The transaction table now fills the available height, so every dropdown has room to open in full (#280)
• The Tags column couldn't be shown/hidden — the Show/Hide Columns menu was missing a Tags entry, and the column wasn't wired into the visibility logic. Tags can now be toggled like the other columns (#281)

Security

• The recurring-income update endpoint no longer passes the raw request body through to the entity layer — a crafted payload could previously set internal fields such as the owning user (mass assignment, integrity only — no data disclosure). Update keys are now allowlisted like the other endpoints

Fixed

• Auto-derived recurring budgets (#269) are now consistent across all surfaces: the dashboard "Budget Remaining" hero, Budget Progress/Breakdown widgets, Budget Health score, and budget alerts now apply the same recurring fallback as the Budget view — a category funded only by recurring bills can now trigger alerts and is counted in headline totals
• Auto-derived budgets now respect bill start/end dates: a bill that hasn't started (or has ended) no longer counts toward today's budget, avoiding double-counting during a planned cost change (#268)
• Recurring income summaries (Income view header, dashboard Income Tracking widget): semi-monthly income was counted at half its value, and a one-time income at full value every month until received
• Transfers page monthly total: semi-monthly and semi-annual transfers were converted incorrectly
• Live forecast cache: cache invalidation never matched the stored key (changes such as toggling "exclude from forecast" appeared to do nothing for up to 5 minutes), and the cache key ignored shared-account visibility, letting a share-restricted viewer briefly see the owner's totals
• Editing a bill's amount without updating its split template is now rejected when the stored splits no longer match (the payment would have silently imported unsplit and uncategorized); setting a split template via the API now clears the bill-level category, matching creation
• Multi-account import partial failures (e.g. a deleted destination account) are now reported in the UI instead of masquerading as a full success
• Import preview now also flags repeated bank transaction IDs for accounts that will be created by the import
• Long OFX FITID hashing threshold raised so every previously-imported FITID keeps its exact ID (re-import dedup continuity)
• Auto-derived category budgets (#269) now handle every supported frequency correctly: semi-annual bills were over-counted 6×, semi-monthly halved, custom-schedule bills counted every month, and one-time bills inflated the budget monthly until marked paid (now excluded). Frequency math is delegated to the shared calculator, which also gained the missing semi-monthly conversion
• Auto-derived budgets no longer apply to past months — they reflect today's recurring bills/income and were rewriting history (including overriding explicitly-zeroed snapshot budgets)
• Multi-account import: an invalid destination account mid-import no longer aborts the batch, and deferred balance recomputes now always run for already-imported rows
• Bank sync: the post-import balance recompute now keys on transaction creation, not the import counter, so a row persisted just before a non-fatal error still gets its balance update
• The scheduled-transactions background job now recomputes balances from the ledger (it was the last remaining hand-computed balance delta, and could race concurrent imports)
• Import preview now flags a repeated bank transaction ID (OFX FITID) within one file as the duplicate it is, matching what import actually does; per-account preview counts include rows that will import with skip-duplicates off
• Marking a bill paid by linking an existing transaction now warns if the link silently failed (no money movement recorded)
• Extremely long OFX FITIDs are hashed to stay within the import-ID column

Fixed

• Dashboard could render half-empty (hero tiles only, widget grid invisible): a Chart.js resize on a hidden tile's detached canvas threw during initialization, and the widget grid was never revealed. Chart resizing now skips detached canvases and the grid is revealed before the resize pass. Likely also behind "nothing happens" reports after certain actions (#273)
• Dashboard tiles with a saved account selection pointing at a deleted account (e.g. after factory reset + import re-numbered accounts) no longer error with 404s and stay empty — stale selections fall back to all accounts
• Account balances are now derived from the ledger instead of running deltas — the root cause behind every historical balance-discrepancy report (#3, #89, #124, #163, #187, #194, #274). The stored balance was a running total that each transaction code path adjusted by hand; any missed or mis-signed delta corrupted it permanently. Every transaction create/update/delete (and retroactive rule run, repair action, import and bank sync) now recomputes balance = opening balance + net of non-scheduled transactions, making drift impossible and self-healing past inconsistencies on the next write. A one-time migration backfills the opening balance so displayed balances do not change on upgrade (#274)
• Marking a bill as paid now warns loudly when no transaction was recorded (bill without an account, or transaction creation failed) — previously the bill was advanced silently and the account balance never reflected the payment, drifting from the real bank balance every cycle (#89, #274)
• The app's own export→import now preserves transaction status (scheduled transactions no longer silently become balance-affecting after a migration) and restores the opening-balance invariant for imported accounts
• "Skip Duplicate Transactions" off is now honored: previously rows whose import ID already existed were still rejected deeper in the stack (duplicate-ID guard + unique index), so parts of the batch silently failed to import. Intentional duplicates now get a uniquified import ID and the entire batch imports (#275)
• Import duplicate detection no longer gives false positives for legitimately identical rows — e.g. two same-priced purchases on the same day with the same description. Identical rows within one file now import as distinct transactions (occurrence-aware import IDs), while re-importing the same statement still skips everything it already imported. Re-importing an older statement also recovers transactions the previous logic wrongly skipped (#276)

Fixed

• Install/upgrade aborted on Nextcloud 32 and earlier with "Primary index name on oc_budget_import_templates is too long". The budget_import_templates migration created its primary key without an explicit name, so Nextcloud derived a default name and hit the Oracle-compatibility identifier limit (the unprefixed table name is exactly 23 characters). The primary key now has an explicit short name. Thanks to @TheUnderdev for the report and fix (#272)

Added

• Shared savings goals — share a savings goal with another Nextcloud user. Recipients see a "Shared" badge and can view progress; with write permission they can edit the goal and add money, while only the owner can delete it (#255)
• Auto-derived budgets from recurring items — a (sub-)category with no manually-set budget now shows its committed recurring total (active recurring bills + recurring income, normalized to the budget period) as an automatic budget limit, marked "auto". Typing a value always overrides it (#269)
• Exclude extraordinary/one-time items from the forecast — a per-transaction "exclude from forecast" flag (with a "No forecast" list badge), the same flag on recurring bills/income (propagated to generated transactions), and a matching import-rule action. Flagged amounts still affect your balance but are kept out of the projection averages (#270)
• Reusable CSV import templates — save column mappings and import options and reapply them to future imports (#247)
• OFX/QIF import account routing — route multi-account OFX/QIF files to the right Budget accounts, remembered across subsequent imports
• Bank sync: pending transactions — option to import not-yet-posted (pending) transactions, automatically reconciled when they clear (#257)
• Bill start dates — a bill only occurs on or after its start date, making it easy to change a recurring cost mid-year by ending one bill and starting another (#268)
• "Shared with me" expenses view — recipients can now see expenses that have been shared with them (#248)
• Dashboard period indicator — chart tiles now show a read-only indicator of the period they cover (#250)