Roadmap — what should the Wealth Dashboard get next?

[halvar20000]

This thread is where the order of things gets decided. It is pinned, it stays open, and it is the one place I look before starting the next release.

How it works

• Want something that is already listed below? Add a 👍 to the comment that proposes it. Votes are the sort order.
• Want something that is not listed? Post it as a comment here if it is small, or open its own thread in Ideas if it needs a screenshot or a paragraph. I will link it back here.
• Wrong number, failed sync, broken page? That is an issue, not this thread — bugs skip the queue.
• A bank that will not connect? Start in Q&A with the bank and country. Most of these are on the bank's side; the thread saves the next person with the same bank an evening.

The dashboard is at 0.59 and has run daily against one real household since April 2026. That is the honest limit: one household, a handful of banks and brokers (DKB, Crédit Agricole Suisse, Degiro, Trade Republic, Swissquote, Yuh, Saxo, Kraken). If yours works differently, that is exactly what I cannot see from here.

Where it stands

Accounts by hand, by PSD2 through Enable Banking, by CSV and statement PDF, by broker API. Net worth over time, holdings with market prices, categories with learned rules, budgets, subscriptions, bills, savings goals, cash flow, the Upcoming projection, retirement outlook and plan, people in a household, four languages, an MCP endpoint for an assistant. The full list is in ROADMAP.md; COMPARISON.md sets it beside Portfolio Performance, Wealthfolio and Firefly III.

Things I have thought about, in no order

None of these are promises. They are the candidates I know of; tell me which matter, and what is missing.

1. More importers. Every bank's CSV and every broker's statement PDF is its own parser. If yours is not read, a redacted sample (a few rows or one page, real numbers replaced) is what makes it possible — post it in Q&A or in a thread here.
2. Per-transaction owner — accounts belong to people, transactions do not yet. This unblocks an Expenses per person page.
3. A payslip importer — employer-specific by nature, so probably a template you fill once rather than a parser. This unblocks the Income page.
4. Why it moved — decomposing a day's change in net worth into prices, rates, deposits and withdrawals. Needs daily per-holding snapshots, which only accumulate once the app has been running.
5. Other currencies and rate sources — the ECB covers a lot but not everything. Say which currency you are missing.
6. Mobile layout — it works on a phone, but works is not comfortable.

Deliberately not planned

• A hosted version. A server holding other people's bank consents is a different product with different obligations.
• Write access to a bank. Read-only consent is enough for a dashboard; payment initiation is a different licence and a different class of bug.
• Telemetry, analytics, phone-home. The README promises none, and this thread is what replaces it. If you tell me nothing, I learn nothing — that is the deal.
• Jurisdiction-specific tax or pension rules in the core. If one arrives it goes behind a flag, off by default.

[halvar20000]

Pull statements from Paperless-ngx (or another document archive) by tag — the app fetches every document carrying an account's tag on the daily sync and runs it through the same readers an upload gets; nothing imported twice, unread documents listed by name. Proposed by a user with years of statements in Paperless. Details, and the honest limit (a document is only read if there is a reader for its layout — say which banks are in your archive): #3

👍 here if you would use it.