Skip to content

Changelog

github-actions[bot] edited this page Nov 3, 2026 · 8 revisions

This page is copied from CHANGELOG.md whenever it changes. To correct it, open a pull request on that file.

Changelog

All notable changes to CloudBank are documented here. The format is based on Keep a Changelog, and the project follows Semantic Versioning.

3.13.0 — 2026-11-03

A maintenance release: three dependency updates for security, and two tests that began failing in November fixed. Nothing changes in how CloudBank looks or works.

Security

  • go-jose 4.1.6, used to check single sign-on tokens. It fixes a denial of service when reading an identity provider's RSA keys, and panics on malformed JSON and CBC-HMAC input. RSA keys longer than 4096 bits are now refused; identity providers use 2048 to 4096.
  • fast-uri 3.1.9 and serialize-javascript 7.1.4, both used only to build the app; neither ships inside it.

Fixed

  • The AI's log of what was sent is now dated by the same clock that counts the monthly limit and clears entries after 90 days. A test had started failing on every run on 1 November; users saw no difference.

3.12.0 — 2026-10-21

The AI now helps with the chores around the numbers. It proposes rules for the payees you always file alike, fills in Review's uncategorised rows in one go, cleans up the raw names banks give payees, maps the columns of a CSV it has never seen, answers questions about your money from CloudBank's own queries, and reads a receipt's photo into the entry sheet. As before, each job has its own switch and says what it sends, and nothing it proposes is saved until you save it.

Added

  • Rule proposals on Rules and in AI insights: up to eight payees you keep filing under one category by hand (three or more of the last year's transactions no rule decides, four in five in the same category). Create rule opens the rule sheet filled in; saving it offers to fill in the payee's transactions still without a category. The model hears payee and category names and counts, never an amount, a memo or a date.
  • Propose categories on Review's "Needs a category" card: a payee for each row, its own or one named in the bank's text, and a category from the payee's history or else from the model, which is sent the payee, the amount and the date. Every row stays editable; Confirm saves the ticked ones at once.
  • Clean up names on Payees: the model, which sees the payee names only, groups raw bank names (AMZN MKTP IT*2K3) under one clean name, with a "payee contains" rule for the next imports. Everything is editable before Apply, and the last cleanup can be undone.
  • CSV columns. The map step of a generic CSV shows one row per column, with its first value and the field it fills. With the AI on, a file nothing remembers is mapped by the model, which also tells the date order, decimal mark and sign from the column names and the shape of three rows (never their words). The mapping is remembered per wallet by the header row, so the next file from the same bank comes mapped without the AI; Forget drops it.
  • Ask your data at the top of AI insights: a question in your own words. The model picks up to three of CloudBank's read-only queries (a total, by month, by category, the largest expenses, the balances), CloudBank runs them on the wallet, and the answer comes with Numbers used. The model never writes a query or sees a transaction; questions are not kept. Each counts as two requests.
  • Receipts. Scan a receipt in the entry sheet opens the camera. The photo is shrunk in the browser, without the place it was taken, and only Read with AI sends it; the total, date, shop and a short memo fill in. It is never stored unless you tick Attach the photo to the transaction, and What was sent keeps a line about it instead of the photo.
  • Each of these has its own switch in Settings → AI, off at first, except Propose categories, which uses Category suggestion's.
  • Five migrations run at startup, for rule proposals, payee cleanups, CSV mappings and the new switches.

Changed

  • Category suggestion now also sends the date, for Review's proposals; its switch says so.
  • Built with Go 1.27.3, which fixes GO-2026-6809 in crypto/x509.

Fixed

  • Merging payees now moves their templates, the rules that set them and their ignored recurring payments too, instead of leaving those without a payee.
  • AI insights' month picker cut "September 2026"; it now fits the longest month in every language.

3.11.0 — 2026-10-21

The AI does more than fill in fields now. With your own model, it writes a report on each month (and, if you like, each week and year), proposes budgets from what you really spend, points out subscriptions that cost more, categories grown lately, goals falling behind and transactions that look odd. CloudBank works out every number; the model only writes the words, in a box you can tell apart, and nothing it proposes is saved until you save it. Home Assistant can show CloudBank's numbers as sensors, and a phone adds a transaction in two taps.

Added

  • Settings → AI, rebuilt. Your provider (any OpenAI-compatible service, or a model on your own network that an administrator sets), then each job on its own switch, each saying what it sends; the wallets the AI may work on; a monthly request limit with this month's count; and the last 90 days of what was sent, word for word. Off, nothing goes to any model.
  • The AI box. Everything the AI wrote sits in one frame with a slowly changing border (still under reduced motion, or when turned off), with Why? for the numbers it was given and thumbs to say whether it helped.
  • AI insights, a page of reports the AI writes on a wallet's numbers: last month's on the 1st at 07:00 in your time zone, every Monday's and each year's if you tick them, or any month on Generate now. A new AI report ready notification opens it.
  • Budget proposals. Up to five budgets a month from the six complete months before: a category spent on with no budget, or a budget gone over or not reached, gets the median rounded to 5. Apply opens the budget sheet filled in. On Budget, short on the overview and in AI insights.
  • Subscription proposals on Schedules: the last payments over the amount saved, a schedule that looks doubled, one no longer seen in the bank.
  • Savings proposals: up to three categories you spent more on lately, with what going back to before would keep a month; Set budget opens the sheet at the earlier level.
  • Goal proposals on Goals: a goal falling behind gets what to put in a month (Put in opens the money sheet), one asking more than the wallet keeps a later date, one with no date a date. No investment advice.
  • Unusual transactions on Review and the overview: a payee charged far more than usual, a large first payment to a new payee, the same charge twice in a few days. Open in the register, It's fine, and for a double charge See the pair among the possible duplicates. New ones reach the bell.
  • The AI guide: setting it up, what each job does and sends, what stays with you, and the limit.
  • Home Assistant sensors. GET /api/v1/wallets/{walletId}/summary, read with a personal API token: bills overdue and due this week, the next bill, this month's budget and what waits on Review, in plain decimals; balances only with ?balances=true. The guide has the YAML.
  • Quick add from the phone. A long press on the installed app's icon offers New expense and New income (named in your language), opening the entry sheet on your default account with the sign set. On Android, sharing a bank's notification text with CloudBank opens the sheet with it: read at once by the AI's quick entry when it is on, or shown on top to copy from. Nothing is saved until Save (how, and what an iPhone can do).
  • Seven migrations run at startup, for AI reports, schedules, proposals and unusual transactions.

Changed

  • The category suggestion no longer sends the memo, only the payee and the amount.
  • The web-app manifest is now served by the server, so the shortcuts speak your language; it is no longer kept by the offline app shell.

Fixed

  • Quick entry's amount came back as 23.5; it is written in the account's own format, 23,50.

3.10.0 — 2026-10-20

CloudBank can now tell you things where you will see them: in a bell on every page, and by push, email, Matrix, Telegram, Discord, Slack, ntfy, Gotify or a webhook into Home Assistant. You choose which events go where and when. The Schedules page finds the payments that come round with no schedule, shows what each costs in a year, and puts the due dates in your phone's calendar.

Added

  • The bell. The first button of every page header (in the top bar on a phone) lists what CloudBank has to tell you, grouped by Today, This week and Earlier, with unread ones counted on it. A click opens the page it is about, switching wallet if needed, and Mark all as read clears it.

  • Settings › Notifications. An overview of every channel with its state and how many events it gets, and a page per channel: how to connect it, and which events arrive there. Push moved here from Security.

    • Push on this device, as before.
    • Email through the installation's mail server (CB_SMTP_*), once you type back a code mailed to the address.
    • Matrix, to a room, with the installation's shared bot (CB_MATRIX_HOMESERVER, CB_MATRIX_TOKEN) or your own.
    • Telegram, from the installation's shared bot (CB_TELEGRAM_TOKEN, linked with one tap on Connect your chat) or your own, with an optional topic and silent sending.
    • Discord and Slack, through a channel's incoming webhook.
    • ntfy, on ntfy.sh or your own server, and Gotify.
    • A webhook: a JSON POST, signed when you set a secret. The guide has the Home Assistant automation that takes it.

    Send a test checks each one, and its page shows the last delivery or the last error. A channel that cannot be reached is retried for several hours, even across a restart. Tokens and webhook addresses are stored encrypted and never shown again; one on your local network needs an administrator.

  • Events.

    • Bills due, for every member of the wallet.
    • Security: a sign-in from a new device, two-factor sign-in turned off, a new API token. These always reach the bell.
    • Problems: a bank sync that fails, a bank consent about to end, a mailbox that stopped reading, a bank mail nothing could read, and transactions waiting on Review longer than you chose (3 days by default).
    • Money (off until you turn it on): a large expense you did not type yourself, a balance under the account's threshold, a budget at 80% and 100%, a goal reached or falling behind.
    • Summaries (off until you turn it on): a weekly and a monthly one, with money in and out, the period before, the top categories and the week's bills.
    • Administration: a new CloudBank version, for administrators.
  • Timing. Each event goes out at once or in a daily digest at the hour you pick. Quiet hours hold push, email and chat overnight, except problems and security. Thresholds and wallets sets the per-account amounts, which wallets you hear from, and whether amounts appear outside the app. The bell is always immediate.

  • The notifications guide: every channel step by step, Home Assistant, and what an administrator sets up.

  • Found in your transactions. The Schedules page offers the payments that come round with no schedule: the same payee, a similar amount, every week, month, three months or year, still going. Create schedule opens the sheet filled in from it; Ignore stops offering it.

  • What schedules cost in a year. The list's figures lead with what goes out and comes in over twelve months, and each schedule shows its yearly total under its amount.

  • Add to calendar. In the Schedules calendar view, a private address for your phone's calendar app (iPhone, Google Calendar, Outlook): every due date on its day with its name and amount, never a balance. It can be regenerated or turned off, and the same calendar downloads as a .ics file.

  • Ten migrations run at startup, for notifications, their channels, deliveries and timing, known devices, where a transaction came from, ignored recurring payments and calendar addresses.

Changed

  • A schedule needs a payee, except a transfer. The payee sits under the amount in the sheet. Schedules saved without one, such as imported ones, still post: a banner counts them and Complete them one by one opens each in turn, and a new payee can also go to the transactions they registered without one.

Fixed

  • Pages pick up what changed elsewhere. A transaction from bank sync, a bank mail, a scheduled posting or another device showed only after a reload. Pages now refresh when you come back to the tab and every 30 seconds while it is visible.

3.9.0 — 2026-10-17

Bank mails read any mailbox now: Gmail, Libero, iCloud and the others over IMAP with an app password, beside Outlook.com. The AI can read the mails no pattern reads, Review asks about the ones the bank never booked, and one pattern can cover every wording of a bank's notice. A guide walks through all of it.

Added

  • Any mailbox, with an app password. Connect with IMAP asks for the address, the provider (picked from the address, with its server filled in and a link to its guide on app passwords) and the app password, never your main one. CloudBank logs in first and saves nothing unless the server accepts it. The connection is always encrypted, to a server on the public internet. The app password is stored encrypted and never shown again; New app password checks a new one before it replaces the old. A password the server later refuses stops the mailbox until you enter a new one.
  • The AI can read bank mails. Each mailbox chooses How mails are read: patterns only (the default), patterns then the AI, the AI then the patterns, or the AI only. It uses the AI set up in Settings › AI by whoever connected the mailbox. Only authenticated mails from the senders you list ever reach the AI provider, with card numbers, IBANs and other long numbers hidden first. The AI never chooses the account. A mail it wrote carries an AI badge in the history.
  • Review asks about mails the bank never booked. A transaction read from a mail that the bank has not booked five days on shows under Not confirmed by the bank, with the nearest bank rows of its account. Merge keeps the bank's amount, date and reference and the mail's memo, category, payee and tags. A refused payment and its reversal show as one Payment reversed item, deleted together. The register marks transactions from mails with an envelope until the bank confirms them.
  • One pattern for every wording of a notice. The pattern editor lists the mails it was tried on, and shows where a mail it does not read stops matching. Mark the same fields in that mail too and the pattern accepts both wordings. Mails it would newly read are listed as New, to check before saving.
  • Tours of Bank mails and of the pattern editor. The Bank mails page has its tour; the editor offers its own the first time you make a pattern, and its ? plays it again. Review's tour gains a step for unconfirmed rows.
  • The bank mails guide: a mailbox only for the bank, connecting each kind of mailbox, making patterns with an example, the AI, and what happens when the bank's own row arrives.
  • Two migrations run at startup, for IMAP mailboxes and for the AI's settings of each mailbox.

Fixed

  • Escape during a tour closes only the tour. Over a sheet, such as the pattern editor, it also closed the sheet and lost what you had entered. Tours can also be followed with the keyboard: the card's Next button takes the focus.
  • A sheet scrolls what you focus clear of its header and foot, instead of under the sticky Save bar.
  • Review offers the bank row nearest in amount first when merging a transaction read from a mail, so a hotel's 180 meets the hotel's 205.40 before the petrol station's 40 booked the day before.

3.8.1 — 2026-10-16

CloudBank can read your bank's notification mails and write them into the register as cleared transactions. This is a preview. For now it reads Outlook.com, Hotmail and Live mailboxes only; other mailboxes, over IMAP with an app password, come next.

Added

  • Bank mails (Settings › Bank mails, preview). Connect an Outlook.com, Hotmail or Live mailbox by signing in to Microsoft, which can be done from your phone with a QR code. CloudBank only reads: nothing is marked read, moved or deleted. It reads one folder you choose, and only the mails that arrive there from the moment you connect. It needs CB_SECRET_KEY on the server, because the Microsoft credential is stored encrypted. Three migrations run at startup, for the mailboxes, their mails and the patterns.
  • Mails arrive on their own. The server listens to the mailbox (IMAP IDLE), falls back to a check every few minutes where a server cannot listen, and runs a full check every 15 minutes, so a mail is never lost or read twice. The card says whether it is listening, checking or reconnecting. Whoever connected the mailbox gets a push notification when it stops working or the Microsoft sign-in expires, and, at most once a day, when mails arrive that no pattern recognises.
  • Patterns turn a mail into a transaction. Start from a real bank mail, select what to take with the mouse or a finger (amount, memo, payee, card, date…) and choose the account and whether it is money out or money in. CloudBank writes the pattern, tries it on the sender's latest mails and shows the transaction each one becomes. Saving it can also apply it to the mails already waiting. A transaction from a mail is cleared, goes through your assignment rules, and is merged, not duplicated, when bank sync brings the same payment. Advanced shows the pattern's expression, which can also be written by hand.
  • Only authenticated mails write anything by default: a mail whose sender the receiving server did not vouch for (DMARC or DKIM) shows as not authenticated, so a forged notification cannot fill your register.
  • The history of the latest mails names what became of each one. A created transaction links to its row in the register, and a mail no pattern reads offers to make one.

Fixed

  • A new currency follows your language. Every currency added in CloudBank, including the one a new wallet starts with, used a dot for decimals, so a wallet made from scratch in Italian showed "1,234.56 €". A new currency now takes your language's separators: "1.234,56 €" in Italian, Spanish, German and Portuguese, "1 234,56 €" in French. Currencies you already have are left as they are; change them in Currencies.
  • A widened register column keeps its width. It snapped back as soon as you let go. Two quick changes in the Columns menu no longer undo each other, and every preference shows at once instead of after the server answers.

3.8.0 — 2026-10-15

CloudBank speaks four more languages: Spanish, French, German and Brazilian Portuguese, in beta. A privacy mode hides your money across the app, a server can sign in through SSO alone, and the server's errors come in the reader's language.

Added

  • Spanish, French, German and Brazilian Portuguese, marked beta. Each covers the whole interface, the push reminder and the demo, whose wallet, accounts, payees, categories and goals are seeded in the language it is started in. They were translated against a shared glossary (docs/i18n/glossary.md) of what each CloudBank word means and the term chosen for it in every language. The browser's language picks one on a first visit (es-MX → Spanish, pt-PT → Brazilian Portuguese), and a language loads only when it is used, so the app is no heavier for the ones you never pick.
  • A new language selector. Sign-in, setup and the demo have a globe menu listing each language by its own name, with its name in yours under it. Settings › General shows a card per language; while a beta language is chosen, its card links to a form for native speakers to send corrections.
  • README in every language: Italian, Spanish, French, German and Brazilian Portuguese, shorter than the English one, with a row linking them all.
  • Privacy mode. An eye beside the ? of every page (or Shift+H) blurs amounts, balances, totals, memos and payees across the app, sidebar and charts included. Dates, categories, account names and the shape of each page stay readable. It stays on, on that device, until you turn it off, and replaces the register's own switch.
  • Sign in through SSO only. With CB_PASSWORD_LOGIN=false the login page is the provider's button. The first sign-in on a new server becomes the administrator, and CB_OIDC_ADMIN_EMAIL reserves it to one verified email. Ten one-time access recovery codes per person, made in Settings › Security, get you in when the provider is down. docs/sso.md walks through Authelia.
  • The budget's tick says what it means. The big bar names it ("today, 15 October · 48% of the month"), and each line's tick explains on hover, touch or focus how that line stands against the pace. A line paid at most once a month lately, like rent, has no tick.
  • The guides are mirrored to the wiki on every change.

Changed

  • Server errors are in the reader's language, with a sentence of their own for the ones a person meets (a wrong password, a name already taken, an expired bank consent…), and the server's technical detail kept apart under it.
  • Italian follows the glossary: a transfer is a giroconto, a cleared transaction is verificata, a schedule is a programmata, and statuses agree with transazione.
  • Add transaction on the overview opens the entry sheet right there, on the default account, instead of sending you to the register.
  • Large counts read right in Italian, Spanish, French and Portuguese, which have their own plural for round millions.
  • OIDC is sturdier for every setup: a provider that was down when CloudBank started is tried again at the next sign-in, and the email is read from the userinfo endpoint when the ID token leaves it out (Authelia since 4.39). One migration runs at startup, for the recovery codes.
  • The server builds with Go 1.27.2, for ten standard-library security fixes.

Fixed

  • A schedule edited and saved no longer reverts. Opened again, its sheet showed the values from before the save, and a second save wrote them back. A transfer edited from the register did the same.
  • Add transaction on the overview opened the entry sheet and shut it at once when the register had saved filters.
  • An SSO sign-in before setup is refused with the password login on. It used to create an account that was not an administrator, leaving the server with none.
  • The status picker fits its card at 320px, and its icons sit centred in the entry sheet.
  • The bills category says what it filters. Its hint in Settings › Wallet still sent you to the Bills page, gone into Schedules in 3.7.0; it now names the dashboard's Bills widget and the overdue bills reminder.

3.7.0 — 2026-10-06

The secondary pages are rebuilt. Every page outside the register and the overview now answers a question first, lists its entries full width and edits them in a panel beside the list. Bills and Schedules become one calendar, and CloudBank says when a newer version is out.

Added

  • Schedules is a calendar of the month. Bills joins Schedules. Each occurrence sits on its day as not registered, registered, cleared, reconciled or overdue, and occurrences registered months ahead land in their own month. Above it: what is still to pay, what is overdue, and what is coming in. Beside it, Needs you registers or skips in one click, with a sheet to change a bill's amount first. All schedules keeps the list.
  • Told when a newer CloudBank is out. Once a day the server reads the published versions and tells administrators, in a card in the menu and in Settings › About, when a newer release (or a newer nightly, on :latest) is out, with the steps to update. Nothing is sent. Dismissing a release hides it until the next one (a nightly, for a week). An administrator can turn the check off in Settings › About, and CB_UPDATE_CHECK=false turns it off for the whole installation.
  • The wallet's total says what it adds up. The balance beside the wallet and at the head of the dashboard names how many accounts it sums ("4 of 6 accounts" when some are closed or left out of the totals), and opens a breakdown of them.
  • Rules can add tags and match on tags. The rule's sheet previews, as a dry run, what it would match, and a rule's ▶ applies just that rule to the transactions it is the first to match.
  • Add a tag before any transaction carries it.
  • Transactions remember the template they were filled in from, so a template shows how often it is used.

Changed

  • The secondary pages are rebuilt, each in the register's style, with a 396px side sheet (a bottom sheet on a phone) in place of the old dialogs:
    • Categories: each category's transactions, amount and share over the last 12 months, in two sections; Rows or Index view; a subcategory can move to another group or become a group of its own.
    • Payees: the default category and payment, and the category a payee usually gets, made the default in one click.
    • Tags: the categories each tag was mostly in, and its net amount.
    • Currencies: each rate with where it came from and when, which accounts use it, and how its amounts look, with a live preview.
    • Templates: those for quick entry and those behind a schedule, apart.
    • Accounts: reconciled, today and future balances, grouped by type, with the last reconciled date; a row opens its register.
    • Rules: each rule as a sentence with how many transactions it fills in.
    • Budget: one view, the month's (or year's) answer first: spent, left and days to go, then what is in the budget, what is not, and expected income.
    • Goals: what is saved, what to put aside each month, and what is free to spend; reached goals close into a history you can reopen.
    • Vehicles: what each vehicle costs to run over the last year, per kilometre and per 100 km, and its last fill.
  • Review leads back to the register or the overview it was opened from.
  • A new version of the app is offered, not swapped in. An open page shows a notice when a new build is installed, and switches only when you choose Update. A page whose code went missing in an update reloads once instead of breaking.
  • The server builds with Go 1.27.1, the images run on Debian 13, and CI uses Node 26. Two migrations run at startup, in well under a second: one for the settings' revision, one for the instance's own settings.

Fixed

  • Saving a split schedule keeps its lines. The Schedules sheet dropped a split template's lines on save, so every posting after it came in uncategorised. The amount and categories of a split are now locked there, as for a transfer.
  • Settings no longer undo each other. Two settings saved at the same moment, or from two tabs or two devices, could silently put one of them back. Saves now queue, and a save built from an older copy is retried over the newer one.
  • Missing files are a 404. A request for a file that does not exist got the app's page instead, so a page left open across an update broke instead of loading the new build.

3.6.1 — 2026-09-29

A round of daily use after the first feedback. The register's filters move into their side panel, the wallet's own lists get a menu group, a large wallet gets faster, and a sweep of the server tightens how requests are checked.

Added

  • A "Wallet data" menu group. Categories, Payees and Currencies become menu pages; until now they were reached only from Settings › wallet › Manage data. They sit with Tags, Rules and Templates in a new group after Insights, and Money keeps Accounts and Transactions. A menu you have customised keeps its shape: the three new pages arrive hidden, and a card at the foot of the menu offers them once, with "Show them" or "Keep hidden".

Changed

  • The register's header is one row. On a desktop, the bank line (the last sync and the Sync button) sits beside the account's name.

  • Filters live in their side panel. The chips no longer crowd the toolbar, and a red × on the Filters button clears them all. The panel is now called "Filters", runs the full height of the register, and on a desktop can be open together with Columns, one above the other.

  • When the filters match nothing, the empty table goes and the message stands beside the panel.

  • Settings › wallet no longer has Manage data: those pages are in the menu.

  • Faster on a large wallet. Measured on 100,000 transactions:

    • the uncleared totals and the cash flow answer in milliseconds instead of a third to half a second;
    • the balance report takes under 200 ms instead of 400;
    • the review behind the register's bank line takes about half the time;
    • the CSV export takes under a second instead of nearly four.

    Responses and the app itself are gzip-compressed, and a full register is seven to nine times smaller on the wire. A migration rebuilds one index at startup, in well under a second on that wallet.

  • The server builds with Go 1.26.6.

Security

  • Saves check what they point at. Transactions, templates, rules, payees and goals refuse an account, category, payee or vehicle of another wallet. Before, such a reference was stored, and names from another wallet could show through it. Upgrading is recommended for every instance with more than one user.
  • Requests to addresses a user gives stay on the public internet.
    • SimpleFIN setup tokens and push subscriptions reach only public https addresses.
    • An AI provider on the local network (Ollama, LM Studio) can be set and used by an administrator only.
    • When an AI provider fails, only its status is shown, never its reply.
  • Idle connections close after two minutes instead of staying open.
  • CI checks the Go modules and the standard library for known vulnerabilities.

Documentation

  • The guides point to the Wallet data group for categories and payees.

3.6.0 — 2026-09-28

The first answers to the first public feedback. A reader found the documentation missing, and writing it turned up three things a new user could not do.

Added

  • A user guide. docs/ gains guides for getting started, importing transactions, every page of the app, and backups, upgrades and restoring, with an index at docs/README.md. Settings › About and the footer link it as "Guide", first among their links.
  • Change your own password. Settings › Security has a Password card: the current password, the new one, and the new one again. Changing it signs out every other session, while this device stays signed in. Until now only an administrator could reset a password.
  • Create a category or a payee from the entry sheet. Typing a name that matches nothing offers "+ Create “Coffee”" (or "+ Add" for a payee). The new one is selected at once, and the rest of the sheet is kept. A category made there is top level, and an expense or an income as the amount's sign says. Split rows offer it too.

Changed

  • Names no longer differ only in case. A second payee "bar centrale" beside "Bar Centrale" is refused, and so is a category that repeats one at its level. The entry sheet shows the existing one instead of offering a new one. The Payees and Categories forms say so before saving, and point at Merge for duplicates already in the data.

Fixed

  • Vehicles survive a wallet backup. A wallet backup left out vehicles and which transactions belonged to them, so a restore lost both. Backups made by 3.5.1 or earlier still restore, without vehicles.
  • The empty Payees page says where payees come from: entering transactions and importing files.

3.5.1 — 2026-09-28

Fixed

  • Importing a file with untagged rows no longer blanks the preview. The preview's tags field could not take an empty list sent as null, and the whole page went white. The API now never sends null where a list belongs.
  • Import counts use the singular for one: "1 row will be imported", not "1 rows", in the review and in the result after it.
  • A page that breaks shows a message, not a blank app. The error stays on that page: the sidebar and the other pages keep working, and moving away clears it.

Documentation

  • The migration guide covers the nginx upload limit, and what to check after importing.

3.5.0 — 2026-09-28

The phone release. CloudBank was designed at 1280px, and it showed on a phone: buttons wrapped, figures took a screen of their own, and pages leaned on controls that no longer fitted. Most of this release is about giving a phone its space back. Alongside it, the bank sync moves into Settings, and syncing and reviewing happen from the register.

Added

  • Sync an account, and see what it needs, from its register. An account linked to a bank shows when it last synced ("2 hours ago") and a Sync button above its balances. Syncing no longer means leaving the ledger. When the account has rows waiting for a look, an amber "3 to review" appears beside them. These are imported rows with no category, or possible duplicates. The button opens Review on that account alone, and "Show all accounts" widens it again. It depends on what there is to review, not on the bank: a file import or two hand-entered rows can need it just as much.
  • Settings › About. A new last section, for everyone: the version, the licence in a sentence, and the links to the source, the API docs, the donation page and HomeBank.
  • The footer can be turned off. Settings › Appearance has a "Show the footer" switch, on every screen. It hides nothing: what the footer carries is also in Settings › About.
  • Skipping one tour can skip them all. Turning down a page tour that was offered asks once whether the other pages should stop offering theirs. The "?" on each page still plays its tour, and resetting the tours in Settings turns the offers back on.

Changed

  • Bank sync lives in Settings. Settings › Bank sync & AI holds everything the Bank sync page had: providers, connections, schedules, linked accounts and history. The sidebar loses Bank sync, Review and the Banking group they sat in. Old links to /bank-sync land on the section, and the address Enable Banking returns to is unchanged.
  • Filters say how many are on, always. The Filters button carries a count everywhere. On a desktop the chips naming each filter stay beside the search. On a phone, where they took a line or three above the ledger, they move into the filter panel. Reports work the same way. A register emptied by its filters says so, and offers to clear them.
  • Figures that do not fit a phone step through a strip. The register's balances and the overview's figures took two lines, or a screen, on a phone. When they do not fit, they now sit in a strip one figure high, stepping every four seconds. A touch stops it, a swipe scrolls it, and with reduced motion it never moves by itself. The overview's headline balance stays large and still. Whether the figures fit is measured, not guessed: when they fit, and on every wider screen, they stay a plain row.
  • Accounts on a phone are one line each. The desktop table squeezed the name and the amount until "Credit card" wrapped word by word and the € sat on its own line. At 320px the edit and delete buttons fell outside the card. Each account is now its name over its bank and share, its amount, which never wraps, and a ⋯ menu holding Edit, Valuations and Delete. A single tap on the row opens the account.
  • The footer folds on a touch screen. At the end of the page it was three lines of links. It is now one line, the version and licence with a "Links" toggle that opens them one per row.
  • Phone headers fit. A page's "?" sits on its title row, as a small round button, instead of taking the action row. At 320px "Add transaction" reads "Add", so the actions keep to one line.
  • The README points at Buy Me a Coffee first, the easiest way to support the project.

3.2.2 — 2026-09-27

Changed

  • The reports were redesigned. One frame for every tab: a period bar, the register's filters, and a ⋯ for saved views and downloads. Each tab opens with its answer, the figure, before any control. Spending is a ranked list instead of a pie. Every chart has its figures beside it, and a period still running says "so far".
  • Review compares a possible duplicate field by field, with what the two rows share dimmed so the differences stand out, and shows a bank's memo in full wherever a row needs a category.

Fixed

  • The reports now honour the transfer, "no status" and "uncategorised" filters.

3.2.1 — 2026-09-25

Changed

  • Reconciled lines appear only under a status filter. The register draws its "reconciled up to here" lines only while a status filter hides the reconciled rows, one per run of hidden rows, with its dates and count. Unfiltered, each row's status already says what a line would.
  • The demo image is published with every release.

3.2.0 — 2026-09-25

The redesign. Every screen was rebuilt to one measured design — the shell, the register, the overview, settings and the secondary pages — and checked against it by measuring rather than by eye. Around it: an entry sheet beside the ledger that you arrange yourself, page tours, and a public demo to try it all without installing anything.

Changed

  • Entering a transaction happens beside the ledger, not on top of it. The entry form is now a panel that slides in from the right: the rows and the running balance stay visible while you type, and adding several in a row no longer blanks the page between each one.

    Modals are kept for the one thing they are good at — stopping you before something you cannot undo — and those now say what will actually happen ("they are gone for good, and the running balance of every later row changes") with buttons that name the action instead of "OK" and "Cancel". Deleting a transfer says plainly that it removes both entries, which is the part people do not expect. Dismissing one, however you dismiss it, counts as "no".

    The browser's own confirmation box is now gone from the whole app — accounts, payees, tags, templates, schedules, rules, goals, vehicles, API tokens, bank connections, the dashboard layout and the navigation menu. Each of those questions now names its consequence rather than restating itself: deleting a payee says the transactions stay but are left without one, deleting a tag says it comes off every transaction that carries it, removing a bank connection says the transactions already imported are kept. All of it is translated, which the browser's box never was.

  • Every page opens the same way. One header across the whole app: the name of the page, a line saying what the page is actually for, and its actions on the right — instead of the hint floating above the buttons on one page, below them on the next, and missing on a third. On a phone the buttons drop under the title rather than squeezing it.

    A page with nothing on it yet now says what it is for and offers the first step, instead of a grey line reading "No rules yet.": rules explain that they read the text your bank sends so you stop retyping the same thing every month, and there is a button right there to write one.

    Statuses are words again. Mantine sets badges in capitals, which made "OVERDUE" and "PAID" the loudest thing on a row of figures you actually came to read; a status is now a word with a small coloured dot, and the colour still carries the meaning.

  • The ledger got its screen back, and its first line is the way in. Filters and columns open beside the transactions instead of unfolding above them: everything they used to take, they took from the rows, and the rows are the page. On the side they cost width, which a ledger has to spare.

    Adding a transaction starts where the transaction will land — the first line of the register, or the N key — instead of a form sitting above it. The entry sheet opens beside the rows, which is where entering one belongs.

    The notice about rows a filter is hiding is one line now rather than a boxed alert. The register is explaining itself, not raising an alarm.

  • The register says which account it is, and what is hiding rows. The page was called "Transactions" with the account in a dropdown beside the title — the same thing named twice, neither of them the subject. The account is the title now, and switching it is still one click, because the title is the switch. Searching is a field on the page instead of a control inside a panel that starts closed, since narrowing a ledger by text is the commonest thing anyone does to it.

    Active filters are chips you can read. A badge saying "3" told you that three filters were on without saying which, so the only way to find out was to open the panel and inspect every control; each filter now names itself and can be dropped on its own without disturbing the others.

  • The overview answers the question you opened it for. It led with three bordered cards of balances and a donut. It now leads with one figure at forty pixels — what you have — and beside it what the period earned, spent and kept, so the balance has an explanation next to it rather than two more balances. The period is a row of segments (month through all time) instead of a dropdown, because five choices switched constantly deserve one click each.

    The widgets below lost their frames. A dozen bordered rectangles read as a form; as sections separated by air and a hairline, the figures inside go back to being the subject. "Where your money goes" is a list of rows now — name, amount, and a bar scaled against the largest — which survives being a third of the page wide, where a donut and its legend did not.

    Which balances appear is yours: Settings offers today, reconciled and after everything scheduled, and the ones you pick show on the overview and above the register both.

  • The gear is where it was drawn. The style tile put it at the foot of the sidebar, beside your name; it had shipped as an entry at the end of the navigation list, which on a 1280x720 laptop sits 126px below the fold. The foot no longer scrolls with the pages, so the one destination you reach from anywhere is always on screen. Your name and the sign-out moved down there with it, which is also where the tile had them.

    Asking for support moved out of the header and stopped shouting. It was a filled red pill beside the ledger, which is the one place a red pill should never be — it reads as an alarm about your own money. It is now an outlined accent pill at the foot of the sidebar, quiet until you reach for it.

  • The text you were meant to read is now readable. The whole app was measured against WCAG AA in both themes rather than eyeballed, and it was not passing. The "dimmed" grey that carries every page hint and every empty state sat at 3.3:1 in light and 3.5:1 in dark, under the 4.5:1 floor — the text explaining what a page is for was the hardest text on it. Error messages used a red that read at 3.3:1 on a white card, so the one message you must not miss was the faintest. And the donate pill put white on a gradient that fell to 2.7:1 at its brightest point: it was least readable exactly where it was loudest.

    All three are fixed, along with the avatar initials, and e2e/contrast-audit.mjs keeps them fixed — it walks every page in both schemes and fails if anything drops under the floor.

  • The register's columns are yours. Move them into the order you want, drag the edge of a heading to widen one, click a heading to sort by it — both remembered per user, so the register you arranged is the one you get back on another device. Sorting never recomputes the running balance: that figure belongs to its row, and a sorted register is a way of finding a transaction rather than of reading balances down the page.

  • Hide names and amounts for a screenshot. One button in the register blurs payees, memos and figures while leaving dates, categories and the shape of the page legible — so a screenshot still shows how CloudBank works without showing what you earn. It is per-session on purpose: something you switch on for a moment, not a mode to wake up in.

  • The register puts the ledger first. The three balances are a single line in the page header instead of three bordered cards in a block, and the filter panel starts closed — between them they were costing most of the screen above the transactions, which are what the page is for. A filtered register now also says when it is hiding newer rows: ask for everything unreconciled and the top line can be weeks old, which looks like the balance has drifted when it hasn't, so the register explains itself rather than leaving you to work it out.

  • Managing people moved into Settings. Inviting someone or resetting a password is something you do twice a year, so it no longer holds a permanent row in the main menu: it is a People tab inside Settings, shown to admins. Existing /admin/users links still work — they land on that tab. Sidebar group headings also dropped their tracked-out capitals for sentence case, which is easier to scan.

Added

  • Choose how far back the overview looks. A period control in the header — this month, quarter, half-year, year, or all time, which is the default. The widgets that cover a span of time follow it, and any one of them can still pin a period of its own: a dashboard you already arranged keeps exactly the periods you gave it, because a widget you configured is an explicit choice and stays that way. Balances are untouched by it, since a balance is not a period quantity — it is simply what you have now. The register gained a half-year preset along the way.

  • The overview opens with what needs doing. Above the widgets, a short strip lists the handful of things waiting — transactions with no category, overdue bills, budgets gone past, pairs that look like duplicates — each with the one link that fixes it. It disappears entirely when there is nothing to do, so seeing it means something is genuinely waiting. It sits outside the widget grid on purpose: widgets are yours to remove, and an overdue bill is not a preference.

  • Account balances in the sidebar, if you want them. Off by default; pick up to three accounts in Settings and their balances sit at the foot of the sidebar. Only a negative balance is coloured, because colouring the healthy ones too would turn the sidebar into a traffic light.

  • The entry sheet shows what a transaction needs, and you decide the rest. By default: date, account, memo, payment, category and the status as a row of icons; payee and everything else wait under More details. Settings → General moves any field either way. Save and add another gained a toggle that keeps every field for the next entry ("Save and keep"), and each button shows its key: ↵ saves and closes, ⇧↵ saves and starts another.

  • Page tours. Each main page offers a short tour the first time you open it, in a card in the corner that never blocks the page, and the ? in its header replays it. They replace the one first-login tutorial, which explained everything at once to someone who had not yet seen any of it. Settings → General turns the offers off, or resets them.

  • A public demo, and the :demo image it runs. One click makes a throwaway account with a year of made-up data, in English or Italian. It is deleted after two hours without use, every night and on every update; bank sync talks to a pretend bank, and anything that would keep real secrets is switched off. See docs/demo.md.

Fixed

  • Save stays in reach in a long entry sheet. A split of several lines made the sheet taller than the screen, and with its scrollbar hidden nothing said Save was further down. The foot now stays at the bottom, and the scrollbar shows.
  • "Reconciled up to here" shows when it helps. It drew in the unfiltered register, where each row's status already says the same, and vanished under a filter, the one place it helps. It now shows only while a filter hides rows — under "Not reconciled", below the last row.
  • Chart axes show money. The value axes of the dashboard and the reports printed stored minor units — 230,000 for a month of 2.300 €. They show the amount now, and the Balance report's minimum-balance line is labelled inside the chart instead of off its edge.
  • Forms stop overwriting what you type. Forms, modals, dashboard widgets and the bank-sync panels filled themselves in when their data arrived, and a slow response could land after you had started typing and replace it.
  • A confirmation opens above the sheet that asked for it, instead of behind it.
  • The register fits a 1280px screen without sideways scrolling, and the spending pie fits on a phone.
  • Controls are the size the design gives them, and at least 44px on a touch screen.
  • Accessibility, measured. An axe audit (WCAG 2.2 AA, both themes) now finds nothing: every close button, input and progress bar has a name, the column panel's arrows say which column they move, and the ledger shows a focus ring. Sheets, dialogs and collapses no longer move under prefers-reduced-motion, and the register can be driven by keyboard alone, from the ledger to the sheet to a confirmation. The audits stay in e2e/.

3.1.0 – 3.1.5 — 2026-09-04 → 2026-09-17

Smarter bank sync — reconciliation against the entries you already have, a review page, per-connection schedules and a third provider — the Bills redesign, CAMT.053 import, and the first step of the design system.

Added

  • A design system underneath the app. The first step of the restyle: CloudBank now has its own blue as the default accent, two bundled typefaces (Public Sans for the interface, IBM Plex Mono for every figure, so a column of amounts lines up on the decimal), a proper heading scale, and controls that ease between colours instead of snapping. Nothing is fetched from a font CDN — the app is self-hosted and installs offline.

    The change underneath matters more than the paint: colour now means one thing at a time. The accent means "you can act here" and nothing else, because you can change it; income and expense have their own fixed pair that no longer moves when you pick a different accent. Green and red are gone from the accent picker for that reason, and a saved accent of green or red falls back to the new default until you pick another.

  • Bank sync via Pluggy (Latin America), experimental. A third provider joins SimpleFIN and Enable Banking, on the same bring-your-own-credentials footing. Banks are linked in Meu Pluggy — free for personal use — and CloudBank only reads them, so there is no consent redirect to set up: paste your application's client id and secret, add an item id, link the accounts. Credentials are verified when saved rather than at the first sync, and a credit card's inverted sign convention is handled, so card spending lands as an expense rather than income. Marked experimental: it follows Pluggy's published API but has not been exercised against a live bank.

  • Import ISO 20022 CAMT.053 statements. The end-of-day statement most European banks offer as a download is now a first-class import format, alongside HomeBank .xhb, QIF, OFX/QFX and CSV: pick CAMT.053 in the import assistant and the file runs through the same preview, duplicate detection and assignment rules as any other. The bank's own reference for each movement is kept, so re-importing an overlapping statement flags the repeats instead of duplicating them, and statements exported in ISO-8859-1 or windows-1252 are read correctly rather than rejected.

  • Scannable tables — numbers now use tabular figures app-wide, so amounts and balances line up cleanly in columns (the register, every table, the dashboard), and tables share one compact, consistent density with a quiet row-hover highlight.

  • Consistent empty states — list pages (accounts, transactions, schedules, templates, budget, payees, categories, rules) now share one centered icon-and-message placeholder instead of a bare dimmed line.

  • Grouped sidebar navigation — the left nav is now organized into collapsible sections (Money, Planning, Banking, Insights, Settings) with the dashboard on top, so it reads as an ordered, mature menu instead of a long flat list. Collapse the sections you don't use (remembered per device).

  • Bank-sync reconciliation — imported transactions are now matched against your existing manual or scheduled transactions (same amount within a date window) and merged into them instead of duplicated (the bank reference is carried over so future syncs recognise the row), imported with the right status (booked → reconciled, pending → cleared, and a pending row settles up to its booked form when it arrives), and given a default payment mode by account type (IBAN → direct debit, card → credit card). Whatever pending transactions a bank exposes are imported from the same call; many banks' PSD2 interfaces return only booked ones.

  • Bank-sync review — a dedicated page listing imported transactions that still need a category (set it inline) and a duplicate finder for pairs that slipped through, each with merge, edit, delete, or "not a duplicate" (a dismissal that is remembered so the pair isn't surfaced again).

  • Bills, redesigned — the Bills view now shows one row per bill with its last successful payment and its next occurrence, plus a quick "add a bill" form (name, amount, account, day of month) that creates a monthly scheduled outflow in your bills category.

  • Transaction bulk actions — multi-selection bulk edit now covers category, payee, payment mode, status and tags (add or replace), plus bulk delete; reachable from the selection bar and the right-click menu, with shift-click range selection in the register.

  • Dashboard Tidy / Reset — in edit mode, Tidy re-packs the widgets into a clean, gap-free grid and Reset restores the default layout.

  • CI & code review — CodeQL static analysis runs on every pull request, and the end-to-end job builds the app image from a shared layer cache for faster runs.

  • Per-connection sync schedule & cached balances — each bank connection has its own auto-sync schedule: the time of day and the weekdays it runs (in your local timezone), instead of a coarse interval. It syncs at most once per scheduled day. Account balances on the Bank sync page are also cached (refreshed at most every 12h) instead of fetched on every visit. Both keep CloudBank within PSD2's small per-day access budget.

  • Last-sync status — each connection shows when it last synced and the outcome (ok / partial / error) of that attempt, for both manual and background syncs.

  • Sync history — each connection keeps a short, expandable history of its recent runs on the Bank sync page: time, manual vs automatic, status, and a per-linked- account breakdown (fetched / imported / reconciled, or the error) — so anyone can see why a sync did what it did without reading server logs.

  • Bulk "not a duplicate" — the duplicate finder can dismiss every surfaced pair at once, for when a fresh import flags many look-alikes that are all legitimate.

Changed

  • The background bank-sync timer (CB_BANK_SYNC_INTERVAL, now default 1h) only controls how often the job checks for due connections; each connection's own frequency decides when it actually syncs.

Fixed

  • CloudBank can be built on Windows. Two source files whose paths differed only in case (registerFilters.ts and RegisterFilters.tsx) collided on case-insensitive filesystems, so imports resolved to the wrong module and the web build failed before it started — invisible to Linux CI. The filter model is now registerFilterModel.ts, line endings are pinned to LF by a .gitattributes, npm run typecheck actually typechecks (it silently checked nothing), and CONTRIBUTING.md lists the command behind each make target for contributors without a POSIX shell.

  • Dates now follow your own calendar, not UTC. The register's This month / This quarter / This year filters were computed by converting a local date to UTC, so east of UTC every preset covered the wrong window — the last day of the period was excluded and one day of the previous period leaked in. The same conversion decided what "today" meant everywhere else, so a transaction entered in the evening west of UTC was pre-filled with tomorrow's date, and one entered just after midnight east of UTC with yesterday's. Every civil date is now derived from the local calendar, and the register's midnight roll-over waits for your midnight rather than UTC's.

  • PSD2 rate limit (HTTP 429). Bank sync made two transaction calls per account (booked + an explicit pending call), doubling usage and tripping the ASPSP's "consented multiplicity per day" limit so nothing imported. It now makes a single call that already returns whatever pending the bank exposes. A new opt-in CB_BANK_SYNC_DEBUG_PENDING flag logs a booked/pending breakdown (and, on request, the exact provider response) to diagnose banks that return no pending. Using it confirmed that Intesa Sanpaolo exposes only booked transactions over PSD2 — pending charges are unavailable until they book — so the missing rows are a bank limitation, not a sync bug. See docs/bank-sync.md.

Removed

  • The dedicated marketing site. The Astro one-pager under site/ and its GitHub Pages workflow are gone; CloudBank is presented from easly1989.github.io instead. Nothing in the app (server or web) depended on it, so this changes no behaviour — only the donation links now point at the consolidated donation page.

Security

  • Bounded dashboard income/expense window. The ieMonths query parameter was clamped only to non-negative; a large value flowed into a slice allocation, so an authenticated user could request an enormous window and exhaust server memory. It is now capped at the existing 120-month maximum (fixes a CodeQL go/uncontrolled-allocation-size finding).
  • Dependency automation. Added a .github/dependabot.yml (weekly, grouped minor/patch PRs across Go, npm, Docker and GitHub Actions) and documented that CB_SECRET_KEY should be a strong, high-entropy value.

2.0.0 – 3.0.3 — Post-parity releases (2026-07 → 2026-09)

Built on the 1.0 parity base across many point releases: the 2.x line brought deep personalization and HomeBank interop with onboarding polish; the 3.x line brought the post-parity push — automatic bank sync, security (2FA, scoped API tokens, encrypted secrets), the phone (installable PWA + web push), and opt-in AI. (Granular per-tag notes weren't kept; the entries below summarise the line.)

Added

  • Scheduled background bank sync — auto-sync connections are refreshed on a timer (CB_BANK_SYNC_INTERVAL, default 12h), so transactions arrive without clicking "Sync now". A per-connection toggle turns it off, and an Enable Banking connection whose consent has expired is skipped (reconnect it to resume). Enable Banking connections also show their consent expiry and a one-click Reconnect that renews it while keeping the account links.
  • Optional secret encryption at rest — set CB_SECRET_KEY to encrypt CloudBank's reversible server-side secrets (bank credentials, AI API keys, 2FA secrets, the web-push signing key) with AES-256-GCM. Opt-in and backward compatible: without it, secrets are stored in plaintext as before; set it and each secret is encrypted on its next write.
  • Automatic bank sync — import transactions straight from your bank, de-duplicated and run through your assignment rules, via two bring-your-own-credentials providers: SimpleFIN (worldwide; a ~$15/year SimpleFIN Bridge subscription) and Enable Banking (EU/EEA + UK via PSD2 — a free sandbox to test, your own production application for real accounts). Credentials (the SimpleFIN access URL, the Enable Banking application key) are stored server-side and never returned to the client; CloudBank never sees your bank login. See docs/bank-sync.md.
  • Savings goals — manual piggy-bank goals with contribute / withdraw, a progress bar and an optional target date; included in wallet backup/restore.
  • Bills view — a "what's due" surface over scheduled transactions, with upcoming / due / overdue state and one-click posting.
  • Full-text register search — search across memo, payee, category and info from the register.
  • Two-factor authentication (TOTP) — optional per-user 2FA with authenticator apps (QR enrolment + one-time recovery codes) and a two-step login.
  • Personal API tokens — scoped, revocable bearer tokens for programmatic access (a Bearer request bypasses the session CSRF guard); the token secret is shown once at creation.
  • Installable PWA — a web-app manifest, icons and an offline app shell, so CloudBank installs to the home screen / desktop.
  • Web push notifications — opt-in browser push (VAPID; keys stored server-side), used for schedule / bill due reminders.
  • Opt-in AI category suggestions — provider-agnostic, bring-your-own-key; suggests a category for a transaction from its description. The API key is write-only and never returned to the client.
  • Opt-in AI natural-language entry — type "coffee 3.50 yesterday" and get a pre-filled transaction to review before saving (same BYO-key setup).
  • Documented bank-import plugin contract — a stable CSV/OFX/QIF import-plugin contract (docs/import-plugins.md) plus broader debit/credit CSV column mapping.
  • Fully customizable, free-form dashboard — place and resize widgets anywhere on a snap grid (not just reorder); add multiple instances of any widget from an "Add widget" palette, each with its own settings (e.g. two spending donuts over different periods); the layout persists per user and stacks to a single column on phones. New widget types beyond the standard set: a single account balance card, a recent transactions list, a key-figure big-number, and a free-text notes card. Existing dashboards are migrated automatically.
  • Per-account default payment mode — each account can pre-fill the payment mode of new transactions (e.g. Direct Debit for a bank account, Credit Card for a card); a chosen payee's own default still takes precedence.
  • Selected-transactions total — selecting rows in the register now shows the selection's net total (plus an income/expense split for mixed selections) in the bulk bar, HomeBank-style.
  • Scheduled income/expense summary — the Scheduled page shows the recurring income, expense and net normalized per week / month / year at a glance.
  • HomeBank-style dashboard — pick an account and Add opens the full transaction modal; the spending donut shows percentages; the income/expense chart is wider; and the Upcoming panel is split into Recurring / Future / Reminders tabs, each with post / skip / edit actions.
  • Themes — an accent-colour picker alongside light / dark / auto; the light/dark toggle now persists as a user setting (survives a refresh).
  • Collapsible sidebar (icon rail) and pinnable, reorderable navigation with a "More" group for unpinned items.
  • Templates — a dedicated management page (create/edit/delete), and templates are offered when entering a transaction instead of appearing as "upcoming".
  • HomeBank .xhb export — download a wallet back to a HomeBank file (round-trips with the importer); available from the wallet's backup section.
  • Desktop-style income/expense chart on the dashboard (diverging bars around a zero line) with a selectable period.
  • Smart amount entry (HomeBank style) — 12.40 and 12,40 are both read as decimals; a per-user preference, on by default.
  • Double-click any grid row — register, budget, currencies and the other management grids — to open it for editing.
  • A first-login tutorial (coachmark tour) — dismissable, shown once per user, and restartable from Settings.
  • Brand logo/icon beside the app name and as the favicon.
  • A footer donation link (PayPal) and a HomeBank credit link.
  • An animated landing site (Astro) published to GitHub Pages, now featuring real app screenshots and a mouse-reactive background.
  • CI: a weekly HomeBank version watch that opens a compatibility-review issue when a newer HomeBank release appears.
  • The Schedules grid now shows each scheduled transaction's amount.
  • Accounts show both today's balance and a separate projected future balance (initial balance plus all dated transactions, including future ones).
  • A show / hide future transactions toggle in the register's filter bar.
  • A per-wallet setting to pre-register scheduled transactions up to N months ahead (HomeBank style, up to 3 months), used by the auto-posting scheduler.

Changed

  • The wallet switcher now lists only wallets + "Create wallet"; categories, payees, currencies, integrity, backup/restore and .xhb export moved under Settings → Wallet.
  • Import / export moved into Settings → Wallet (it is wallet-scoped) and is no longer a separate sidebar item; the old /import route redirects there.
  • The wallet Settings tab is titled after the active wallet and its sections (general, import, backup, danger zone) are grouped behind a section selector so they no longer overflow the page.
  • Settings, Import and Preferences pages now use the full page width instead of a narrow centred column.
  • Dates are rendered everywhere in the user's configured format.
  • Faster initial load — the app is code-split per route with vendor chunks and imports only the chart pieces it uses, so the first download is much smaller.
  • Modernized the stack (React 19, Mantine 9, Vite 8, React Router 7, current Go dependencies) and internal refactors (per-domain API client, dedicated vehicle/tag packages, a SQLite read pool for read-only queries) with no change in behaviour.
  • Documentation now states parity with HomeBank (no fixed version), so it tracks current and future HomeBank releases.

Fixed

  • Reports: the Statistics pie is larger with a side legend, and the Trend and Balance charts render immediately instead of appearing blank until a control is changed.
  • The theme toggle now switches on the first click (previously the first click was a no-op when the system theme resolved to "auto").
  • Chart legend and axis text stay readable in both light and dark themes and update correctly when toggling the theme (they no longer keep stale colours).
  • Account balances are computed from the account's transactions instead of always showing the initial balance (often zero).
  • The dashboard quick-add row no longer stretches wider when a tag is added.
  • Italian status labels aligned with the HomeBank desktop wording.

1.0.0 - 2026-06-22

The first public release: a self-hosted, web-based personal finance manager with HomeBank feature parity, shipped as a single Docker container.

Added

  • Accounts of every HomeBank type (bank, cash, checking, savings, credit card, liability, asset, investment) with per-account currency and flags.
  • Transactions with 12 payment modes, the cleared/reconciled status lifecycle, category splits, free tags, internal transfers (including cross-currency), bulk edit and duplicate detection.
  • Register view with a server-computed running balance, rich combinable filters, and a statement reconciliation workflow.
  • Scheduled transactions with automatic posting and a startup catch-up, reusable templates, and assignment rules for auto-categorisation.
  • Budgets (same-every-month or twelve monthly values) and a full suite of reports — Statistics, Trend Time, Balance, Budget and Vehicle cost — with charts and CSV/PNG export.
  • Import: native HomeBank .xhb, plus CSV (HomeBank dialect and generic mapped), QIF and OFX/QFX, through a shared import assistant with duplicate flagging, on-import rules and OFX FITID de-duplication. Export: CSV and QIF.
  • Multi-currency with manual rates and online ECB rates via frankfurter.app (no API key), with graceful degradation to manual rates.
  • Preferences (language, theme, date format, start screen, default account), a wallet integrity check with fixes, wallet backup/restore as portable JSON, and an admin VACUUM INTO hot backup of the whole database.
  • Multi-user, admin-managed (no self-registration), with first-run setup, argon2id passwords, CSRF protection and login rate limiting.
  • Responsive UI with light/dark themes and English + Italian translations.
  • Interactive API documentation (Swagger UI) at /api/docs.

Infrastructure

  • Single distroless Docker image (amd64 + arm64), SQLite on a /data volume.
  • CI (lint, race tests, build, Docker smoke, Playwright e2e) and automated GHCR publishing (:latest nightly, :main stable, :vX.Y.Z per release).

Clone this wiki locally