Rules

Use case #1: auto-group credit card payment and transfer transactions (match on the same amount) Use case #2: auto-group credits + debits from the same merchant to denote refunds

I think it would be really cool to have Lunch Money send an email alert if one of my accounts goes below a specified balance. Even cooler would be if the account goes below the value of another account. For example, if my checking account balance drops below my credit card owing balance.

When creating rules, allow an "or" operator. This would be super helpful in consolidating rules with similar purposes for example "if from account A OR account B, do this" or "if payee is this OR that". Additionally it would be super nice to have multiple AND statements for the same field. For example "payee contains xxx AND payee does not contain yyy" This came up when "atm withdrawl" was also including "atm fee" transactions, so I could do "AND payee does not include fee"

Currently, "delete transaction" only works if created from a single existing transaction. This rule effect is not flexible enough to trigger deleting new transactions that are imported.

It's not unusual for Plaid to get transaction signs wrong and mark an expense as income or income as an expense, especially with investment transactions. Sometimes all transactions in an account are wrong, but sometimes only certain ones are, so it would be extremely helpful to be able to create a rule that can just flip the sign when necessary.

Currently you can only select by day of the month (1–31). But I would like the option to select today, tomorrow, yesterday, X # of days or a specific date. For example: If... Matches day... Day is exactly... Today. Then the rule would run on all new transactions.

There is an option to Auto Create rule when updating category but I would prefer it to auto create a suggested rule that I can then approve or reject later

When applying a rule, is it possible to apply it exclusively to transactions that have not been categorized previously? In other words: apply the rule only to transactions with no category set. This approach would be useful in situations where you do not want to affect transactions that, although meeting the rule's conditions, were already categorized or processed in the past.