Skip to main content

Spending Rules: Automatically Categorize Transactions in Bulk

Written by Taylor Stewart

How do I create a Spending rule?

Advisors create rules in Planning → Spending → Rules; clients use Spending → Manage → Rules. A Spending rule applies repeated category, merchant-name, tag, or hiding choices to matching transactions in that household, including existing history and future entries.

  1. Open Rules using the route for your role, then select New rule. The rule editor opens with Settings and Preview changes tabs.

  2. Under If transaction matches..., enable a condition such as Merchant and enter the matching value.

  3. Under Then apply updates..., enable an action such as Update category and select its category.

  4. Open Preview changes and inspect the matching count and examples.

  5. Select Save, then verify affected entries in Transactions and totals in Cash Flow. New rules go at the end of the list; move a specific category exception before any broader rule that already assigns a category.

Save requires at least one populated match condition and one action. A rule can still be broad, so don't use a common word without checking the matches.

The editor has no name field. The Rules list identifies each rule by its conditions, actions, and match count. To revise an existing rule, use its pencil icon with the Edit tooltip, change its conditions or actions, and select Save.

What conditions can a Spending rule match?

In Spending's rule editor, a transaction must meet every populated condition. Selecting several accounts or category types means any selected value can satisfy that particular condition.

Available conditions are:

  • Merchant or Description, using Contains or Equals. Matching ignores capitalization and treats text literally. Merchant uses the automatically assigned merchant name, or the source description if no automatic name exists. It doesn’t match a name set by Rename merchant; use Description and check Preview changes if the original merchant name is unclear.

  • Amount, using Equals or Range.

  • Categories, selecting an automatically assigned category.

  • Category type, using Income, Spending, or Transfer from the automatically assigned category's group.

  • Accounts, selecting included household accounts. Accounts marked Exclude From Plan don’t appear in this picker, even when their transactions remain in Spending.

  • Date, limiting transaction dates. The first date field sets the start; the second sets the end.

Amount conditions use signed amounts: a $14.99 outflow is -14.99. A range for $100–$200 outflows is Min -200 and Max -100. This differs from Transactions' unsigned Amount range filter.

Category conditions use automated classification, not a manual category or another rule's result. Rules don't chain from each other's changes. The current editor has no Category group condition; use an available category or another supported condition instead.

What can a Spending rule change?

In Spending's rule editor, the available actions are Rename merchant, Update category, Add tags, and Hide. These change how matching transactions appear or count in Spending without editing their original date, amount, or account.

Rename merchant changes the displayed merchant name. Update category selects an active category and can’t create one.

Add missing categories in Planning → Spending → Categories, or Spending → Manage → Categories as a client. Add tags combines rule tags with existing manual tags, and its picker can create a new tag.

Enabling Hide excludes matching entries from Spending summaries. Turning Hide off removes that action from this rule; it doesn't force entries visible if another rule or manual choice hides them.

A rule doesn't disconnect an institution, change an account balance, or set Profile spending. An entry categorized in a Transfer group already stays out of inflows and outflows. Check its category before hiding movement between accounts owned by a single household.

What does Preview changes verify for a Spending rule?

In Spending's rule editor, Preview changes identifies transactions that match your draft rule's conditions. It shows the matching count and up to the first 80 rows, with dates, merchants, categories, accounts, and amounts.

Treat that list as a match check. It doesn't prove that every displayed transaction will receive the proposed category: a manual category or an earlier rule can take precedence. The preview's category column shows the transaction's current category, not a before-and-after result.

Before saving, inspect whether the account and amount signs fit your intent. After Save, open several matching entries in Transactions and check Cash Flow. If a result is wrong, edit the rule and save again, or delete the rule to remove its effects across history.

Which Spending rule wins when several rules match?

Spending applies the earliest matching rule that supplies each particular action. New rules, including suggested rules, go at the end of the Rules list. Move a specific category exception before an older, broader category rule so the exception can apply.

  1. Open Planning → Spending → Rules as an advisor, or Spending → Manage → Rules as a client.

  2. Drag an active rule by its handle to the intended position.

  3. Reopen affected transactions and check the result; the new order saves when dropped.

Category, merchant name, and hidden state are resolved separately, so different rules can supply different actions on the same entry. Tags from matching rules accumulate.

After a reorder, also check older transactions affected by archived rules. Archived rules keep their old ordering values while active rules are renumbered, which can change which rule wins for older dates.

A manual category takes priority over rule categories, which take priority over automatic classification. A manual hiding choice also takes priority. Reordering rules won't undo either manual choice, and the transaction eye control can't override an active hiding rule by itself.

Can a Spending rule hide an entire account without disconnecting it?

A Spending rule can hide transactions in and out of an included account while keeping its connection and planning balance. The Accounts condition lists included assets and liabilities, including bank accounts; accounts marked Exclude From Plan are missing from that picker.

  1. An advisor opens Planning → Spending → Rules → New rule; a client opens Spending → Manage → Rules → New rule.

  2. Enable Accounts and select the intended account. Leave unrelated conditions empty if the entire account is the intended scope.

  3. Enable Hide under Then apply updates....

  4. Open Preview changes and check the account and matching count.

  5. Select Save. In Transactions, use the filter's Visibility → Hidden only choice to check examples, then verify Cash Flow.

This affects matching past and future transactions. Save this rule before turning on Exclude From Plan? if this account's balance should also leave household planning totals; the saved rule continues applying after exclusion. A Hide rule alone doesn't exclude Profile debt payments or change household planning spending.

To reverse a mistaken account-wide rule across history, delete it; archiving retains its effect through the archive date. Other rules or manual hiding can still keep entries hidden.

Why is my business account missing from the Spending rule’s Accounts list?

An account marked Exclude From Plan disappears from Spending's rule Accounts picker and transaction account filter, even though its transactions remain. Advisors can still hide a business checking account's activity with a rule saved before exclusion.

  1. Open this account's drawer in Profile → Accounts and check Exclude From Plan? under Overview → Planning. If it's on, that's why this account is missing from Spending's account choices.

  2. Before excluding an account, open Planning → Spending → Rules → New rule. Enable Accounts, select this account, and enable Hide. Leave unrelated conditions empty, check Preview changes, then select Save.

  3. Return to this account's drawer and turn on Exclude From Plan?. A saved Hide rule keeps applying after exclusion.

If this account is already excluded, turn Exclude From Plan? off, save its Hide rule using step 2, then turn Exclude From Plan? back on; household plan totals include this account while exclusion is off.

For individual hiding, open Planning → Spending → Transactions, search by merchant or description, open an entry, and use its eye control. Excluded accounts' transactions show an internal account ID instead of an account name, so account-name search won't find them. Check Cash flow afterward; hidden entries stay saved.

A Business owner alone neither excludes balances nor hides transactions. See Account Types in Kerdora for ownership and exclusion behavior.

What is the difference between Archive and Delete for Spending rules?

On Spending's Rules page, Archive retains a rule for transaction dates through today; Delete removes that rule's effects from all transaction dates.

  1. Find a rule you want to archive or delete and select the icon with the Archive or Delete tooltip.

  2. Read the confirmation and confirm Archive or Delete.

  3. Review affected transactions. Use Show archived when you need to inspect an archived rule.

Archive uses today's date automatically. A transaction imported later with a date on or before that cutoff can still match; archiving isn't a frozen snapshot of entries already seen. Archived rules can't be reordered, and the page has no unarchive control.

Deleting a rule doesn't delete transactions. Their display is recalculated using remaining rules, manual choices, and automatic classification.

A transaction may therefore keep the same category or hidden state if another source still supplies it. Delete has no undo control; to get a deleted rule back, create it again.

Can I create a Spending rule while categorizing a transaction?

Spending can offer a rule suggestion after you manually change a transaction’s category on Transactions or Cash Flow. The suggestion asks whether to always categorize matching activity that way and displays a matching count.

Select Edit rule in that suggestion to inspect its conditions and Preview changes before saving. Create rule saves the suggested rule directly; dismissing the suggestion leaves your individual category correction in place.

A suggestion isn't proof that every matching entry has the same purpose. Review mixed-use merchants and broad descriptions carefully. A manually categorized transaction keeps that manual category after a rule is created, so use other matching entries to check how the rule applies.

The suggestion closes after about 10 seconds unless you open Edit rule. If it closes, create the rule from Spending’s Rules page.

Did this answer your question?