Bugs

The Budget page crashes to "Something went wrong" with this Console error: "TypeError: Cannot read properties of undefined (reading 'properties')" when clearing or changing the Budgeted value of an archived category. This appears to happen specifically when editing a budget period occurring past the 'Archived on' date. For example, if the 'Archived on' date is June 2026, but the budgeted value is edited for the category in July 2026.

On the Trends page, when the savings rate is a negative percentage, is appears green when it should be red.

On the Recurring page, changes made to an existing Recurring Item details (eg. Payee, Category, Amount, Account) are expected to apply to the associated Rule as well. Currently, the Rule remains with the original parameters. If 'End date' is set, and the date passes, the rule should also be deleted to prevent future transactions from getting linked to the recurring item.

When resolving suggested recurring items on the "Suggested Recurring Items" page and choosing "Merge with existing recurring item", that action replaces the existing suggested recurring rule with a new recurring rule, but the rule criteria for "day is between (inclusive)" with the ±2 day range is set according to the current date, as opposed to the expected date of the transactions (the anchor date of the recurring item). If the recurring item's anchor date is the 3nd of the month, then the day range should be set to trigger on transactions with the date between the 1st and the 5th. Currently, it uses the date of when the merge is done, so if today's date is the 23rd of the month, the rule criteria for the day range is set as 21st to 25th.

Previously reported as "Disappearing recurring items" Update (July 11, 2024): Another user reported incorrect totals on the Overview page under the Spending Breakdown. This was associated with a recurring income item, but in this case the recurring item was displaying on the Recurring page for the current month. Simply deleting the recurring rule resolved the issue and the totals then displayed correctly. Update (July 3, 2024): When a recurring item has an end date, it will only display on the Recurring items page up until that end date. With that said, the recurring rule continues to exist on the Rules page past that end date, and therefore will continue linking new transactions that match the recurring item criteria. Since these transactions are linked to a past recurring item, they cause incorrect totals on the Transactions and Overview page, and click to edit the recurring item from the recurring transaction will lead to a blank page (broken link). Two different errors were reported when the blank page occurs (the one in the attached image, and the one below): Uncaught TypeError: Cannot read properties of null (reading 'billing_date') at EditModal.tsx:135:187 at Ll (react-dom.production.min.js:262:359) at t.unstable_runWithPriority (scheduler.production.min.js:18:343) at Ur (react-dom.production.min.js:122:325) at Nl (react-dom.production.min.js:261:308) at Ie (react-dom.production.min.js:292:141) at Kt (react-dom.production.min.js:73:323) at HTMLBodyElement.a (helpers.js:91:17)

If you use the CSV/PDF import tool, and select multiple PDFs to upload at once (PDFs with the same formatting, from the same bank), only transactions from the first PDF are parsed and imported. Expected behavior: the transactions from all PDFs should be parsed and imported. This is only affecting PDFs. Multiple CSVs are successfully recognized and imported at once.

On the Split Transaction screen, the "Amount left to split" total is wrong whenever a split has at least one child amount with the opposite sign from the parent transaction (for example, the parent is a $79.00 expense, and one of the child line items is entered as a positive refund/reimbursement amount rather than another expense). The screen shows a negative "amount left to split" even though the children already add up exactly to the parent amount. I found this while splitting a bank transaction from Venmo that had multiple Venmo transactions represented. The bank transaction was amount -$79.00. The children of the split were: -$9.00 -$15.00 +$5.00 -$15.00 +$5.00 -$15.00 -$35.00 Summing to -$79.00, matching the bank transaction exactly. However the sidebar shows "Original amount: $79.00" and "Amount left to split: -$20.00" even though the split is correctly balanced. The screen appears to sum the absolute value of each child instead of the signed value, rather than netting positive and negative children against each other. In the reproduction above, the absolute values sum to $99.00 (9+15+5+15+5+15+35), and $79.00 - $99.00 = -$20.00, which matches the incorrect figure shown exactly. This appears to be a display-only bug. Re-checking the transaction's data directly (via the API) confirms the parent amount and the children's signed sum are correct and balanced; categorization and totals elsewhere are unaffected. The risk is user-facing confusion: reopening a correctly balanced mixed-sign split shows a misleading "still needs $X" message, and it's unclear whether attempting to "fix" that apparent imbalance through the editor UI (rather than leaving the data alone) could cause an unwanted change to an already-correct split.

I like to attach pdf copies of receipts to their respective transactions. I download the pdfs to my laptop and drag and drop the file, or hit select file and select it that way sometimes. Oftentimes this takes forever. I drop the file, and it will say "Uploading and Processing" for up to a minute, and sometimes it will then load the file and other times it will become blank as if I haven't dropped anything at all. Sometimes if I repeat this process several times, it will finally load, and then several copies of the file will appear at once, one for each time I have attempted to attach the file. Other times I can't get any copies of the file to appear at all. Sometimes after I get it to work once, it then works promptly each time I try after that, sometimes not.

Plaid changed the way synced transactions with the TRANSACTIONS_REMOVED webhook should be handled. This needs to be updated in Lunch Money to ensure removed transactions are also properly removed in the app, to prevent duplicates, as the duplicates have different transaction ids.

The "Fix your connection" email template has two links in the footer: "Customize" links to https://my.lunchmoney.app/settings and works. "unsubscribe" links to https://my.lunchmoney.app/unsubscribe/ and results in a 404 error page.