Bugs

On the Budget page in beta, the 'Pad your budget' tooltip for income categories is showing recurring income as a negative value. It should be positive.

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.

During CSV / PDF import, the 'Fix Dates' feature only works correctly when the date format is entered in uppercase letters, eg. 'DD/MM/YYYY'. It doesn't work as expected when entered as 'dd/mm/yyyy'.

On the Transactions page, when splitting a transaction ('Transaction Details' panel > Split Transaction), the tags added to the splits don't show up in the table or in the individual split's 'Transaction Details' panel until the page is refreshed.

On the Overview page, Projected Net Income will only display if there are both income and expense recurring items set up. Currently, if there are only recurring expenses and no recurring income, then the Projected Net Income doesn't display. It should display regardless of whether both income and expense recurring items exist. As long as at least one recurring item exists, regardless of type, Projected Net Income should be displayed.

On the Suggested Recurring page, or when managing the suggest recurring item directly from a transaction, clicking on "This is not a recurring item" initiates an endless spinning loading state on all three buttons. Note that the suggested recurring item does get deleted (the item disappears after refreshing the page and is no longer associated with the transactions). There are also reports of the same behavior with the "merge with existing" action.

On the Transactions page, updating the Payee name of a transaction that is associated with a suggested recurring item, will lead to the Payee name only updating in the 'Transaction Details' panel. The payee name in the Transactions table cell will remain with the original value. If the suggested recurring is marked as "This is not a recurring item", the payee name in the table will then reflect correctly. On the other hand, if the suggested recurring is accepted, it will lock the listing with the two different payee names.

The "Available to Spend" does not seem to be calculating properly like it did in the regular version. For Example, in a specific category, with a budget of $100, there is a projected spend of $80, but it is still saying I have $100 available to spend. It should be saying $20. In some cases, positive values in the 'Available' column of the Budget Breakdown also appear in red, instead of green, and vice-versa.

On the Transactions page, the categories dropdown and the expanded payee name on hover, will be cut off at the bottom of the table when viewed in a narrower screen width. It displays correctly in a fully expanded browser.

When using 'Create from Recurring' on the Transactions page, transactions associated with Recurring Items that have their anchor date set to day 30 or 31st will end up getting created in the following month if the day doesn't exist (February, April, June, September, and November). If the anchor date's day does not exist in the current month, the recurring item should be created on the last day of that month (e.g., February 28th for February 2025, April 30th for April 2025), as per the billing day that displays when viewing the Recurring Items page. Steps to Reproduce: Create a Recurring Item with an anchor date of January 31, 2025. Use the "Create from Recurring" option in February 2025 to create the transaction. The item is incorrectly created on March 3, 2025, instead of February 28, 2025. Similarly, for an anchor date of April 30, 2025, the item gets created on May 1, 2025, instead of April 30, 2025.