Skip to content
SageFin

Rules: what happens to a transaction as it arrives

Settings → Rules is where your rules live. Each one looks at a transaction as it arrives and does what it says. For a day the page was a sidebar page called Automations; it is back under Settings.

A rule is the one thing SageFin does to your transactions that you wrote yourself. The jobs it runs on its own after a bank sync, categorizing, finding recurring bills, keeping a bill's charges in one category and matching retail orders, are not rules and are not listed here. Their settings are where they always were: Let SageFin read my transactions and receipts with AI in Settings → Preferences, and Split synced retail orders by category in Settings → Retail sync. What SageFin does on its own describes them, and Why a transaction landed in that category says how your rules and those jobs take turns.

Describing a rule in words

At the top of the page is a box: What should happen when a transaction arrives? Write it in a sentence, like "put Costco Gas in Gas" or "always put Netflix in Streaming", and press Draft a rule.

Sage turns the sentence into an ordinary rule and shows it to you in plain words before anything is saved, with how many of your past transactions it matches:

When the merchant contains "Costco Gas" → set category to Gas · applies to 14 past transactions

The count is made the same way the rule is applied, so it is the real number, and a rule that matches nothing says matches none of your past transactions. Then:

If the rule adds a tag you do not have yet, it says so, and saving creates the tag.

A drafted rule can set a category, set a business, flag transactions for review or mark them reviewed, add tags, rename the merchant, or hide the transactions from spending. A business and a tag are different things: "set the business to Acme" sets your business called Acme, never a tag. The business has to be one you already track under Settings → Businesses; if it is not, the draft says so and leaves the business out, and nothing is created for you. A merchant is renamed only when you ask, as in "call it Anthropic". It looks at one transaction at a time, as it arrives, and it always matches on a merchant or a description. So some requests cannot be rules: anything on a schedule ("every Friday…"), anything that looks over many transactions at once, anything that goes by amount alone ("flag every purchase over $500"), sending a message, and moving money. For those the page says plainly that it cannot be a rule, and why.

Under the box are a few examples to try, like Always put Netflix in Streaming. Choosing one fills in the box, for you to change before drafting. The iPhone app offers the same examples by name, such as Flag big purchases, with the sentence as a hint.

Describing a rule in words uses AI. If AI is off for your household, or nobody has answered the AI question yet, the box is not shown, and New rule opens the rule editor instead. You can always build a rule yourself that way. See Why a transaction landed in that category for how a rule is put together.

Your rules

Below the box are your rules, each in a sentence: what it matches, then what it does. Each one has a switch to turn it off without deleting it. Choose a rule to change it in the editor, and use the menu beside it to Apply to existing transactions or Delete it.

Rules are tried from the top, and the first one that matches wins, so drag a narrow rule above a broad one. A line shows where it will land. To use the keyboard instead, focus the grip at the left of a rule and press the up or down arrow to move it one place. Rules an AI app or Sage suggested wait above the list until you review or dismiss them. A suggestion can set a category, set one of your businesses, give the merchant a cleaner name (say Plaid for "Pst*plaid Inc."), or hide the transactions, and opening it fills the rule editor with all of that. If a business it names has been deactivated since, the editor leaves it off and says so. When the suggestion matched some of your past transactions, Update existing transactions starts ticked, so saving changes them too; untick it to have the rule act only on new ones.

Under each rule, the page says how often it has changed something, like Changed transactions 3 times in the last 90 days, last 2 days ago. That counts the times the rule actually changed a transaction, as new transactions arrived or when you applied it to existing ones, and not how many transactions it matches now. A rule that has not changed anything in that time says so. Each transaction a rule changed also says so, in its own history.

A rule that does nothing

The rule editor will not save a rule that does nothing, but deleting a tag can leave one behind: the tag comes off every rule that added it, and a rule whose only action was that tag has none left. Such a rule says Does nothing — add an action or delete it. under its sentence, on the web and on the iPhone. It still matches transactions, but it changes none of them, and on the web Apply to existing is greyed out for it. Open it to give it an action, or delete it. You can still turn it off or rename it in the meantime.

Deleting a tag offers to delete these rules for you; see Tags. Nothing else empties a rule: a category a rule sets, or a goal it funds, cannot be deleted until the rule is changed, and a business a rule assigns is only ever deactivated.

Recent runs and Undo

At the bottom of the page, Recent runs lists each time one of your rules changed transactions, newest first: which rule, how many transactions it changed, what started it (new transactions arriving, or Apply to existing), and when. Choose a run to see what it changed on each transaction, like Category: Groceries → Dining out.

One thing that is not a rule is listed with them: Keep a bill's category, the clean-up that files a confirmed bill's charges in the bill's category. It keeps the same record of each run, so it can be undone the same way, and its runs say in the background clean-up.

Undo puts back what that run changed, after you confirm. A later change wins: where a transaction no longer holds what the run wrote, because you or someone else changed it since, or a different rule did, it is left as it is now. When that happens, the page says how many transactions were put back and how many were left alone. A run can be undone once, and the undo shows in each transaction's history under your name.

A category put back by Undo counts as your own choice where a rule or the clean-up would otherwise take the transaction straight back: a transaction that had no category before the rule, or a charge Keep a bill's category moved. Rules and the clean-up leave a category you chose alone, so the undo stays undone. If you want the rule to stop for good, turn it off or change it as well.

Runs are kept for 90 days, and at most the newest 500, so the oldest drop off the list and can no longer be undone. A run that changed nothing is not listed.

On the iPhone

The app has it too, as Rules in the menu's Your household group and under Settings → Rules: the same box, the same ideas to start from, and your rules with their switches. Open in rule editor in one of Sage's answers opens it with the editor on that suggestion. Recent runs and Undo are on the web for now.