What a rules engine actually does
A transaction rule is an if-then instruction: if an imported transaction matches some conditions (payee text, amount, account, date), then change something about it (category, display name, tags, review status, or a split). Rules save time only when the condition reliably identifies one kind of spending. A rule for your landlord is safe; a rule that sends every Amazon order to Household is not, because one order can be groceries, a gift and a phone charger.
Accuracy problems come from three places: conditions that are too broad and catch the wrong things, conditions that are too narrow and stop matching (a date or store number embedded in bank text), and rules that run in an order you did not expect. The apps below handle each of these differently.
This is research from official pages read on 29 October 2026, not firsthand testing. We have not opened these accounts or run the features described; disclosures can change, so confirm the live page before you act.
How three apps differ, from their documentation
Lunch Money documents the richest set of conditions and actions of the three pages we could read. PocketSmith runs filters first and then category rules built on merchant keywords. Monarch's help center blocked our reader, so we only report what its official blog describes in a 2022 post; treat blank cells as unverified rather than missing.
| Point | Lunch Money | PocketSmith | Monarch |
|---|---|---|---|
| Match on | Payee (contains, starts with, matches exactly), category, notes, amount range for debits or credits, day range, account | Category rules: merchant keywords. Filters: a separate feature whose criteria the pages we read did not list | Official blog describes if-then rules; full criteria not verified |
| Actions | Rename payee, set notes, set category, add tags, link or unlink recurring item, split, mark reviewed or unreviewed, email you, delete (from transaction panel) | Category rules assign a category; the first matching filter can edit a transaction or assign a category | Blog confirms rules can set review status; other actions not verified |
| Split by rule | Yes, but splitting and editing the original transaction are mutually exclusive | Not covered on pages read | Not verified |
| Past transactions | Create and Apply runs a rule retroactively | Not by default; manual apply overwrites prior categories | Not verified |
| Order when rules overlap | Not stated on the page read | Filters first, then rules; first match wins; drag to reorder | Not verified |
| Auto-created rules | Changing a category creates a match-exactly category rule by default (can be turned off in Settings); renaming a payee creates a suggested rule | Created from the Transactions page or the Categorise items page | Not verified |
A starter rule set for a typical household
This synthetic household has two paychecks, rent, a car, two streaming services and regular big-box shopping. The principle: automate fixed-meaning merchants, use amount or day conditions to separate look-alike payments, and flag ambiguous merchants for a human. Adapt the payee text to exactly how your bank writes it; Lunch Money's own examples show an exact match on Walgreens not matching WALGREENS, and PocketSmith recommends stripping dates and account numbers from merchant keywords.
| Rule | Condition | Action | Why |
|---|---|---|---|
| Payroll | Payee contains employer name, credit | Category Income: Salary; mark reviewed | Same meaning every time |
| Rent | Payee contains landlord or portal name, amount equals rent, day 1 to 5 | Category Housing: Rent; mark reviewed | Amount and day stop a deposit refund from matching |
| Utilities | Payee contains utility name | Category Utilities; rename to a clean name | Bank text is often unreadable |
| Subscriptions | Payee contains each service name | Category Subscriptions; tag subscription | Lets you total recurring costs |
| Fuel | Payee contains station brand, amount under 120 | Category Transport: Fuel | Larger amounts at the same brand may be shop purchases |
| Big-box stores | Payee contains Amazon, Costco, Walmart, Target | Leave uncategorized or mark unreviewed | Mixed baskets need a split by hand |
| Peer payments | Payee contains Venmo, Zelle, Cash App | Mark unreviewed | Could be rent share, a gift or a refund |
| Own transfers | Payee contains your other bank or card name | Category Transfer | Keeps transfers out of spending totals |
Worked example: how one broad rule distorts a month
Suppose the household spends 900 dollars at Amazon in a month: 300 of groceries, 250 of children's clothes, 200 of gifts and 150 of household supplies. A single rule sending Amazon to Household reports 900 in Household and 0 in the other three categories. Groceries look 300 under budget and Gifts look untouched, so the next month's plan is built on wrong numbers.
With the review approach, the same 900 dollars sits in a queue of perhaps six to ten transactions that take a few minutes to split against order history. Monarch's official blog describes this pattern directly: flagging Amazon, Costco and Walmart purchases so they can be split later, and alerting only on transactions rules did not process.
Common rule failures and fixes
- Rule stopped matching: the merchant text includes a date, time or store number. Edit the keyword down to the stable part of the name, as PocketSmith's guide advises.
- Rule catches the wrong things: add an amount range, account or day range condition (Lunch Money supports all three) or move a narrower rule above it where order matters.
- Retroactive apply wiped manual fixes: PocketSmith warns that applying a rule to all matching transactions overwrites earlier categories. Export or note manual splits before applying to history.
- Too many auto-created rules: Lunch Money creates a match-exactly category rule when you change a category unless you turn that off in Settings. Review the rules list monthly and delete one-off rules.
- Split rule silently skips edits: in Lunch Money a rule either splits or updates the original transaction, not both, so build two rules or split first.
Monthly audit checklist
Set aside 15 minutes after the month closes. The goal is to catch errors while you still remember the purchases.
- Filter uncategorized and unreviewed transactions; clear them to zero.
- Sort the month by amount and check the 10 largest outflows by eye.
- Search each big-box and peer-payment merchant and confirm splits.
- Compare each category total with last month; investigate any change above about 25 percent that you cannot explain.
- Pick five random transactions and confirm the category is right; if more than one is wrong, a rule is too broad.
- Open the rules list, delete rules for merchants you no longer use, and check new auto-created rules.
- Confirm transfers between your own accounts are not counted as spending or income.
Questions before you decide
Do new rules change transactions I already have?
It depends on the app. PocketSmith says a new category rule does not run against existing transactions unless you apply it manually, and that doing so overwrites categories already set. Lunch Money offers a Create and Apply option for past transactions.
What happens when two rules match the same transaction?
PocketSmith documents that the first matching filter or rule wins and no later rule runs, so specific rules should sit above broad ones. Lunch Money's rules page we read did not state its ordering, so test overlapping rules on a few transactions first.
Should I automate everything?
No. Automate merchants with one meaning and flag mixed-basket merchants for review. A rule that is wrong 20 percent of the time quietly distorts every monthly total.
Follow the sources
- Lunch Money knowledge base: Rules Checked Oct 29, 2026
- PocketSmith Learn Center: Category rules, how they are ordered Checked Oct 29, 2026
- PocketSmith Learn Center: Editing and deleting category rules Checked Oct 29, 2026
- Monarch official blog: Transaction review Checked Oct 29, 2026
Provider terms can change. Recheck the linked source before applying or subscribing.