Tell us how we could make the product more useful to you.
Have something to say?
Do not create a payee from MCP
When using Claude connected via MCP, the "payee" field fails to load. The tool accepts the call (and even updates the "updatedAt" timestamp), but the "payeeId" field remains null—it is not applied. There is no way to assign a payee to an existing transaction via MCP.
Investments analytics improvement
I need to compare the cumulative sums of dividends, stock sales, purchases, and other investment-related transactions. I also want to relate my investment earnings to the expenses in my traditional accounts. So, while it's important to keep the different sources separate (traditional accounts vs. wallets), I also need to know whether my stock investments are helping me cover my day-to-day expenses. I think one way to approach this would be to treat wallets and traditional accounts equally in certain graphs. This would allow me to select, for example, two expense categories, such as leisure and shopping, and compare them with my dividend earnings, stock sales, or both. This way, I could easily see whether I'm spending more than I'm earning from my investments. Another important graph would show the historical value of each stock since it was first acquired. This data could be updated once a day, or the user could be allowed to configure the refresh interval. It's also essential to preserve this historical data even after the user has sold all their shares, so they can still look back at how the stock's value has evolved over time. I see that these features would be complementary to this post
Consistently use singular and plural
Plurals can be covered using | but it isn’t used consistently. I’ve noticed some keys where only plurals are used, like “account(s)” for example. Even though the style guide says “never copy it”, in most other cases even the orginal one uses sigular and plural (e.g. in pages.integrations.enableBankingConnector.buttons.sync or settings.accountGroups.row.accountsCount). Why not use both singular and plural everywhere it applies also in original strings? I haven't tested whether | works in translations, even though it isn't used in the original string but I want to stay as close as possible to the orignial string. I’ve found following strings, that currently have only one string (there may be more): Account(s) / Accounts header.sync.syncingAccounts (currently plural only, even with a {count} variable) pages.integrations.monobank.syncButton pages.integrations.monobank.syncSuccess pages.integrations.enableBankingConnector.syncSuccess pages.integrations.lunchflow.accountsPreviewHint pages.integrations.lunchflow.importButton pages.integrations.lunchflow.importSuccess pages.integrations.walutomat.importSuccess pages.importExport.resolveValues.accounts.skippedNote pages.importExport.ynabImport.preview.skippedNote pages.importExport.budgetBakersWalletImport.resolve.accounts.skippedNote pages.importExport.msMoneyImport.resolve.accounts.skippedNote pages.importExport.msMoneyImport.review.warnings.accountTypeUnsupported pages.importExport.msMoneyImport.review.warnings.accountCurrencyMissing pages.importExport.msMoneyImport.review.warnings.accountNameMissing pages.importExport.msMoneyImport.review.warnings.accountNameDuplicated pages.importExport.ofxImport.resolve.accounts.skippedNote Balance(s) settings.currencies.exchangeRate.balancesNotRefreshed Transaction(s) / Transactions transactions.table.plannedRows (currently plural only, even with a {count} variable) dialogs.reassignCategory.description dialogs.reassignCategory.notifications.success venture.events.form.linkedSummary tagReminders.notifications.existenceCheck.message pages.importExport.msMoneyImport.review.warnings.orphanRowSkipped pages.importExport.msMoneyImport.review.warnings.rowLimitReached pages.importExport.msMoneyImport.review.warnings.rowMissingDate pages.importExport.msMoneyImport.review.warnings.rowAmountUnreadable pages.importExport.msMoneyImport.review.includeVoided.label Issue(s) pages.importExport.msMoneyImport.review.warnings.fileSchemaUnexpected pages.importExport.msMoneyImport.done.partialTitle Duplicate(s) pages.importExport.budgetBakersWalletImport.review.duplicatesTitle pages.account.reconcileDuplicates.result pages.importExport.msMoneyImport.review.duplicatesTitle Row(s) pages.importExport.csvImport.review.unpriceableTitle pages.importExport.msMoneyImport.done.errorsTitle Error(s) pages.importExport.budgetBakersWalletImport.done.partialTitle pages.importExport.budgetBakersWalletImport.done.errorsTitle already uses both, but the first section covers zero rows. You don't have to say “0 row(s),” you just say “0 rows”, do you? budgetPlans.trashed.settingsRowHint is already split into sigular and plural, but only for budget/budgets and not for days. But I’m afraid it’s hard to address both.
Naming an UI consistency
I've noticed a few different design choices. Mixed upper and lower case for titles and buttons / mixed background and no background: Everywhere grey scale title icon except FIRE: Sometimes the + sign is in front of the label, sometimes trailing:
Add some more backend strings to translations
I found messages whose strings don't appear in Crowdin. Login: Restore dialog: There’s may be more.
Widget Settings Problems
In at least German, Spanish, Ukrainian the balance trend widget spike marker setting is unusable if the translation for “Restore Defaults” is too long:
Incorrect money flow direction
The displayed money flow direction in the transaction table view is wrong. Income transfers are displayed the same as expense transfers: In list view it is correct, though: PS: In the list view and => could be replaced with unicode characters ← and → or something better, if technically possible.
Exchange Rate Display
The current rate display 2 USD / EUR (meaning "1 USD = 2 EUR") is a bit confusing because putting the number at the front makes it look like "2 US Dollars per Euro": In my opinion, the rate value should sit on the right side of the currency pair, as the base currency is normally always counted as “1”. Could we update the display to one of these standard formats? 1 USD = 2.00 EUR USD/EUR 2.00 In addition, I was surprised to see in English UI values being formatted with a comma as the decimal separator instead of a period. This actually leads to another issue: if you enter an exchange rate using a comma, the foreign currency value cannot be calculated (even though all other numerical fields in MoneyMoney accept commas without any problem): I noticed your feature request - maybe this would be a great opportunity to take another look at it! 😉 Thanks!
Split Payments Descriptions
Being able to put notes to a split. This would be a key feature to recurrent payments like BNPL (Buy Now Pay Later) that aggregates more payment in one periodic solution.
Incorrect calculation of commissions?
I’m not understanding how are the dividends calculated. If the price of dividend per action is 1.51$ and the bank charges me a commission of 0.46$ what I receive in my bank account or wallet should be 1.05$ not 1.97$, am I right? However, in the wallet’s balance it’s added correctly because it only adds 1€. If you do the same computations with euros occurs the same problem, the total is 1.88€ what is similar to 1.97$
Auto-suggest Payees by Aliases when manually creating a transaction
When a user manually creates a transaction, the Payee field should suggest matching payees based on their Aliases, not only on the payee name.
Cadance options need more space in other languages
The cadence options only fit in English. The translations don’t fit in the available space and there are less shorter translation options.
Counting label in FIRE overview
The label “counting” doesn’t stay in front of the icons in FIRE overview for at least German and Ukrainian: Englisch and Spanish are ok, haven’t checked additonal lanuages.
Balance trend changes due to exchange rate fluctuations
I can see a dip in the balance trend widget even though I have no expenses that day. I have multi currency accounts, so if the dip is due to exchange rate changes, I'd prefer not to reflect it in the balance trend although it should still affect net worth. At a minimum, the tooltip should explain the change, e.g. ‘Exchange rate: −6K’. The same should apply to funds to distinguish actual NAV changes from exchange rate fluctuations.
Planned Expenses
Record and plan expenses scheduled for future dates, overcoming the current constraint that limits entries to today's or past dates. This allows users to forecast budgets and cash flow
Text alignment for wrapped lines in info modals
I noticed a minor visual detail in some info dialogs: when bullet points wrap to a new line, the text currently aligns under the bullet symbol rather than the start of the text: Proposal: Same for Change base currency dialog: In this dialogs it even looks like these bullet points are implemented as a paragraph with line breaks rather than a structured list. Proposal: At “How it works” in AI settings it’s already ok: There may be more, but I haven’t found any others so far. It would be awesome if this could be polished in a future updat
Hint for admin users variable
Running a self-host environment I was curious about what more I can do as an admin. Even though the ADMIN_USERS variable is described in general I couldn’t find a hint what exactly to provide and where to find it. I first tried the registered email address, but it is actually the username shown in household without the “@-sign”. It might be worth to add a hint to the .env file and/or docs, although the practical value of being an admin is currently fairly modest.
Pin the sidebar while scrolling
In settings and analytics in windows with less height the left sidebar scrolls together with the main area without need. Imho that doesn’t look/feel ideal: I just noticed and want to report it, but it is actually a minor one.
Improve header in mobile view
Since adding the drop down next to the + Add button there’s no space between add and the feedback button: Additionally, translation of add in other languages isn’t short as the English one, so the settings button moves out of the view: Two ideas are to either ommit the text in mobile view: Or only show support and feedback buttons in if there’s sufficient space available: But I don’t want to push you into going without feedback and support. Perhaps you have better ideas.
Use the base currency for MS Money import
If the MS Money file has no currency, USD is assumed: “{count} account(s) had no currency in the file, so USD was assumed — check the currency on the accounts step before continuing” (pages.importExport.msMoneyImport.review.warnings.accountCurrencyDefaulted) Could be helpful to change USD as fixed currency to the base currency.