Tell us how we could make the product more useful to you.
Have something to say?
Cash & accounts widget
i have mane accounts, and i would like to see some of them in Cash & accounts widget
Recurring payments
Why are planned transactions included in Balance trend and Spending pace but Recurring payments are not?
Add the number of operation using each category
This would be very useful to tell which category is useful or useless.
Design adjustment in Trackers and Targets
Adjust the design so that, when the window is maximized, the internal boxes occupy the entire space.
Move income category management in settings
“Income categories” option should be under Categories page instead of an option under “General”
Connecting Georgian banks
Are there plans to include Georgian banks, such as Bank of Georgia and TBC?
Completed
Publish version tags (e.g. v0.33.5) on the self-host Docker images
Right now, self-hosters can only pin images to sha- or follow latest. Following latest means database migrations and compose changes land without review. Pinning a SHA is safe, but update tools like Renovate, Diun, and What's Up Docker can't put SHA tags in order. They can't tell that a newer release exists, so every upgrade means checking GitHub releases, mapping the release to its commit, and confirming that the tag exists on Docker Hub. Version tags would also help with #792: those tools can already alert on new semver tags. Proposed solution Have image-to-docker-hub.yml add a version tag next to latest and sha-*, reading the version from packages/frontend/package.json (which release-version-check.yml already checks against the release PR title): frontend: add v${VERSION} to the image-tag list passed to frontend-docker-build backend: add -t "$IMAGE:v${VERSION}" to the imagetools create call in merge-backend Every successful build on main produces images, so a hotfix pushed to main without a version bump would move that version's tag to the new commit. That seems acceptable, since it would still be the latest build of that version, and sha-* stays available for exact pinning.
Completed
Akahu (NZ) account integration
NZ users currently need a paid Lunch Flow account even though Akahu itself is the open-banking layer this adds Akahu the same way Monobank and Lunch Flow work: personal app token + user token, read-only an implementation already exists and I am offering it as a PR
Swipe right on mobile to expand drawer
Would be nice to be able to access the side drawer with a swipe like native apps.
Mark imported transactions for review
I’m missing a feature that YNAB has that I apparently found very useful: the ability to see which imported transactions you haven’t reviewed, and to approve them. Especially with SimpleFIN, which seems to take days to import transactions, I can’t actually remember which ones I’ve seen before. I used this feature to make sure I had eyes on everything I spent, and it helped me stay more accountable. It’s also a good time to clean up and recategorize transactions. Right now in MoneyMatter, I just have to try to remember which transactions I’ve seen, which is especially hard when new ones arrive older in the timeline than the most recent ones.
Tag analysis widget
I use tags like ‘Need’, ‘Want’ and ‘Save’ to categorise transactions including transfers to investment and savings accounts. But, there is no way to see how these tags are distributed over a month. Please add a Tag Analysis widget to the dashboard showing the total amount and percentage for each tag with a selectable date range. This would help users understand their spending and savings distribution and check whether they follow the 50/30/20 rule or similar budgeting methods. Similar functionality is available in apps like budgetbakers. Sample panel:
Payee analysis and top payees widget
It would be useful to see top payees for a selected period, including total spending and transaction count. The current payee view in Settings only shows cumulative totals, while the Tracker shows top payees only for each individual tracker. We could move the Settings payee view to Analysis, add date range filters and introduce a ‘Top Payees dashboard widget’.
Categories or tags in transfers
I need to be able to tag or set a category in a transfer in order to track also what am I doing with money movements. Reason I have a current account, an investment account and wallets. Usually, what I do is to move money from the current account to the investment one and from there to a wallet (is the only way to do it in real life, at least the last step). I want to create a monthly budget including the investments categories so that I can limit myself the amount of money I can invest. The problem is that, although I can create the transfers between my current account and investment account like normal unlinked transactions, when I transfer them to a wallet I cannot set a category. In spite of being able to unliked them as well, then it would useless to have the link transfers feature. Summary I would allow the user to set a category or not in transfers. In case of having a category, consider the transfer as an expense from the account from which the money is withdrawn and as an income in the account where it is received. The same in transfers between accounts and wallets
Pension as a separate asset type
It would be useful to have a separate Pension section in the app to track government pensions, employer funded pensions and private pensions alongside regular investments. These should be treated as assets even when they have long lock-in periods or cannot be withdrawn on demand, while keeping them distinct in networth and retirement calculations. Pension linked investment funds could be categorised under Pension while retaining their existing value and performance tracking. Government and employer funded pensions that cannot be tracked online should be added manually, with an optional expected annual return to estimate future value. Pension contributions could optionally be included in the Sankey chart. Employer funded contributions recorded as income could also be shown as an equivalent expense under Investments → Pension/Retirement Fund. Pension assets should be treated separately from accessible investments in FIRE calculations based on when they can actually be withdrawn.
Add Commodities as an asset type
Allow users to add physical commodities such as gold, silver and platinum to their net worth, enter the quantity they own and track their estimated current value based on market prices. Include these assets in net-worth calculations and asset allocation.
Income vs. Expense Categories for Analytics
In v0.30.6, Tax categories were introduced but it is for Cash Flow analysis only; and in v0.30.9 Income categories were introduced but it is mostly for the transaction form. My recommendation is to continue allowing the users to determine which categories belong to Tax and Income; however to apply such rules across all Analytics functions. One typical example is that, though the Tax categories are treated separately in the Cash Flow, they are still considered as Expenses in the other Analytics modules (like Trend comparison, Pivot, FIRE, etc). This would significantly distort the outcome of financial analysis.
Completed
Make AI endpoint timeouts configurable via environment variables
When using a local Ollama model through an OpenAI-compatible endpoint, MoneyMatter periodically marks the AI connection as invalid with the following error: Your custom AI endpoint did not respond. Check that the server is running and reachable, then reconnect it in AI Settings. The endpoint is reachable, but local LLMs running on CPU can take several minutes to process requests. Currently, the following timeouts are hardcoded: CUSTOM_ENDPOINT_CALL_TIMEOUT_MS — 5 minutes (ai-call-guards.ts) VALIDATION_TIMEOUT_MS — 15 seconds (connection-validation.ts) MODEL_LIST_TIMEOUT_MS — 5 seconds (connection-validation.ts) Requested changes: Please make these timeouts configurable through environment variables, for example: AI_CUSTOM_ENDPOINT_CALL_TIMEOUT_MS=1200000 AI_VALIDATION_TIMEOUT_MS=180000 AI_MODEL_LIST_TIMEOUT_MS=30000 The existing values should remain as defaults for backward compatibility. Additionally, please consider preventing temporary timeouts or connection failures from permanently marking an AI model as invalid and requiring manual reconnection. This would significantly improve compatibility with self-hosted LLMs, especially CPU-based Ollama deployments.
Completed
CSV import fails for files containing non-ASCII characters (UTF-8)
When importing a CSV statement exported from Bank of Georgia containing Georgian characters, MoneyMatter rejects the file with the following error: bog.csv doesn't appear to be a valid CSV file. The file may be binary or renamed. Root cause: In file-validator.ts, the isValidTextContent() function considers only printable ASCII bytes as valid text and requires more than 90% of the file content to match. UTF-8 characters (e.g., Georgian, Cyrillic) fail this validation. Expected behavior: Valid UTF-8 CSV files should be accepted regardless of the language used in headers or transaction descriptions. Suggested fix: Replace the ASCII-based validation with proper UTF-8 text validation while still rejecting binary files.