A rule didn't categorize a transaction

You created a rule, but a transaction it should catch is still uncategorized or shows a different category. Rules categorize new transactions as they come in, so the most common cause is that the transaction was already there when you made the rule. The other causes are below.

What you'll see

Transactions from a merchant your rule covers still show UNCATEGORIZED or another category. Or applying your rules reports skipped matches, or no matches.

Why it happens

• The transaction was there before the rule. A rule categorizes transactions that come in after it's saved, and leaves existing ones alone unless your AI applies it to them. Changing a rule doesn't recategorize them either. See apply your rules to transactions you already have.
• A category was given when it was added. If you or your AI named a category when adding a transaction by hand, that category is yours, and no rule replaces it. A category that came in with an imported file is different: a matching rule replaces it.
• Rules were turned off for that import or entry. Your AI can import a file or add a transaction without applying rules. Those transactions keep the categories they came with.
• You set that category yourself. Rules never change a category you set, including one your AI set while editing a transaction for you. Applying your rules counts these as skipped. See who wins: you, your rules, or the bank.
• You pinned that merchant. If you pinned a decision about a merchant in your AI's memory, rules skip that merchant's transactions in that ledger. See what your AI remembers.
• The rule is in another ledger. Rules belong to one ledger and only touch that ledger's transactions. A new rule goes into your AI's active ledger unless you name another.
• The rule is turned off. A rule you turned off doesn't categorize new transactions, and applying your rules skips it.
• The pattern doesn't match the merchant name. A rule looks only at the merchant name, ignoring case. If the bank sends a different spelling, or you renamed the merchant, the pattern can miss. See rename a merchant.
• Another rule won. If two active rules match, the rule created first wins, so the transaction gets the other rule's category. To let a later rule win, turn off or delete the earlier one. See when two rules match the same merchant.
• The apply was limited. If your AI applied your rules to a date range or one account, transactions outside it were left alone.

How to fix it

1. Ask your AI to show the rule you expected, in the ledger that holds the transaction. Check its pattern, its category and whether it's on.
2. Ask your AI to test the rule. If it matches none of the transactions you expected, change the pattern to fit the merchant name as it appears. See test, edit, turn off or delete a rule.
3. Ask your AI to apply your rules to the transactions, by account or date range. It runs a preview first, then saves.
4. If the result says transactions were skipped because you set their category, change those yourself. Ask your AI to set the category directly.
5. One pass looks at about 20,000 transactions. If the result says only part of the ledger was covered, ask your AI to apply your rules again by date range or by account.

What you'll see

For the first prompt, your AI saves the rule and adds the charge, which the rule puts in Parking. The six earlier Parking Meter charges stay uncategorized, because they were there before the rule. Your AI then applies your rules to Wallet Cash, and those six move to Parking too. It may ask before saving.

For the second, your AI sets the charge to Dining, saves the rule and applies it to last month. Three Daily Grind Coffee charges move to Coffee. The Dining charge is reported as skipped, because you set its category.

For the third, your AI checks your rules and finds none for Daily Grind Coffee in that ledger. It suggests creating one and applying it. Nothing changes.

Good to know

• New bank transactions arrive at your next session. Pennyweight adds them, and applies your rules to them, when you open the web app or ask your AI something. See how and when bank transactions arrive.
• No rules can look like no matches. When a ledger has no active rules, applying them reports zero matches. Ask your AI to list your rules to tell the two apart.
• Testing counts every match. A test includes transactions whose category you set yourself. Applying leaves those alone.
• Want a one-time fix instead? See rules or a one-time cleanup.