Automate the Boring Stuff: A Guide to Transaction Rules
Use transaction rules to rename noisy merchants, assign categories, and keep recurring imports consistent without manually editing the same rows every month.
Why Transaction Names Get Messy
Imported transactions rarely arrive with clean names. A single merchant can show up as "AMZN Mktp", "Amazon.com Services", "AMAZON RETAIL", or a long payment-processor string. Rideshare, food delivery, utilities, subscriptions, and card payments often have the same problem.
If you manually fix those descriptions every month, you are doing work the app should remember. Transaction rules let BillForecast apply the same cleanup consistently so your reports, budgets, and forecasts stay readable.
What a Rule Can Do
A useful rule usually has two parts: a match condition and one or more actions. The match condition identifies the transaction. The action decides what should happen when BillForecast sees it again.
- Rename a merchant: Turn noisy imported text into a clean payee such as "Amazon" or "Uber".
- Assign a category: Put recurring merchants into groceries, transportation, utilities, income, or another category.
- Standardize notes: Add context for transactions that need review later.
- Support review workflows: Keep rules predictable so automation helps instead of hiding mistakes.
Example: Cleaning Up Amazon
Suppose your card statement includes several versions of Amazon:
- AMZN Mktp US*284-8374
- Amazon.com Services
- AMAZON RETAIL SEATTLE
A rule can match descriptions containing "AMZN" or "Amazon", rename the merchant to "Amazon", and assign the category to "Shopping". That gives your spending reports one clean merchant instead of three slightly different labels.
Use Specific Rules Before Broad Ones
Broad rules are powerful, but they can also be wrong. A payment processor name might represent groceries one week and a restaurant the next. Start with specific patterns that clearly identify a merchant, then add broader patterns only when you are confident they will not misclassify transactions.
A good rule name should explain the intent: "Amazon shopping cleanup" is better than "Rule 12". When you come back months later, you should be able to tell why the rule exists.
When Regex Helps
Regular expressions are useful when a merchant includes changing numbers, dates, or store codes. For example, a pattern can match a fixed prefix while ignoring the variable receipt number at the end. Use regex when a plain text match would require too many duplicate rules.
Keep regex patterns small and test them against a few real examples before trusting them broadly. The goal is consistent cleanup, not cleverness.
A Safer Monthly Workflow
- Import or enter new transactions. Let rules apply to obvious matches.
- Review uncategorized rows. These are candidates for a new rule if they repeat.
- Create the narrowest useful rule. Match the merchant or pattern you actually see.
- Check the result in Activity and budgets. Make sure the category supports your reports and forecast decisions.
Automation Should Make the Ledger Clearer
The best transaction rules are boring. They remove repeated cleanup work without making the ledger mysterious. If a rule makes you less confident in the data, narrow it or delete it. If it makes the same monthly merchant land cleanly every time, it is doing its job.