Why a transaction landed in that category
Most transactions are categorized before you ever look at them. When one lands somewhere odd, the useful question is not "why is it wrong" but "who decided it" — because four different things can have, and what you do about it depends on which.
The four things that categorize a transaction
They run in this order, and the first one to answer wins.
1. Your rules. If a rule you wrote matches, it decides, and nothing later gets a say. Rules are deliberate and deterministic, which is why they go first.
2. What SageFin has learned about the merchant. First, if the charge belongs to a recurring bill you have confirmed and that bill has a category, the charge gets the bill's category. Then, if this merchant's last few charges agree on a category, the new one gets it too. Your own choices count for more than SageFin's when it checks whether they agree. After that comes a merchant seen often enough and categorized consistently enough, which is remembered. This is why a monthly bill stays in one category, and why a coffee shop you have never had in SageFin before often arrives already sensible. None of this uses AI.
3. AI. Whatever is left goes to a model with the merchant, the amount, the date and your category list. If this merchant's earlier charges have categories, or the charge belongs to a recurring bill, the model is told which categories those are, so it can stay consistent with them. This is the only one that records a confidence, because it is the only one making a judgment rather than an assertion — a rule that matched, a merchant that was remembered and a category you chose are all simply true.
4. You. Setting a category by hand overrides everything above.
Your choice is never overwritten
Worth stating plainly, because it is the thing people most reasonably fear about an app that categorizes for them.
Automatic categorization only ever looks at transactions that have no category. Once a transaction has one — from a rule, from the merchant memory, from the model, or from you — no background pass touches it again. A later sync does not re-run the model over your corrections, and nothing quietly changes its mind overnight.
One exception, and it never touches your choices: recurring bills. Sometimes the charges of a recurring bill you have confirmed end up in different categories, such as one gym membership filed as Subscriptions one month and Shopping the next. When that happens, SageFin moves the charges it categorized itself into the bill's category. If the bill has no category, it uses the category most of its charges are in, and gives the bill that category too. A charge you categorized yourself or with a rule stays as it is, and so does a split charge.
Apart from that, a category that looks wrong today was decided once, and it will stay wrong until somebody changes it. Which is the other half of the answer.
Changing one, and making it stick
To fix one transaction, open it and set the category. Done — and it now reads as your decision rather than the model's.
To fix it for next time, write a rule. Fixing the same merchant by hand every month is the signal that a rule is missing. Rules live in Settings → Rules; see Rules.
A rule is one condition and what to do about it:
- Match on the merchant or the description
- using contains, equals, or starts with
- optionally also on amount — money in or money out, greater than, less than or equal to a figure
- then set a category, add tags, rename the merchant, flag it for review or mark it reviewed, assign it to a business, fund a goal, or hide it — any of these together
A rule's amount is kept to dollars and cents. If a figure with more decimal places reaches the editor, from a suggestion or from what you type, the editor rounds it to two and says so under the box, naming both figures, so you can see what will be saved before you save it.
The amount half is what separates cases a name cannot. "Amazon" is shopping when it is £14 going out and a refund when it is £14 coming in.
Order matters, and you control it
Rules are tried in order and the first match wins, so a narrow rule has to sit above a broad one. A rule saying anything containing "Uber" → Travel will swallow every Uber Eats order unless the narrower food rule sits above it. Drag them into the order you want.
A rule can also be switched off with its switch, without deleting it, which is the right move when you are not sure whether it is the one causing the surprise.
Applying a rule to what is already there
A new rule applies to transactions arriving from now on. To sweep it over your history too, use Apply to existing on the rule — it changes every matching transaction that does not already carry that category, and running it twice is harmless. When it finishes, a note appears under the rule saying how many transactions it changed. If it changed none, the note says whether that is because nothing matches the rule or because the matches already have the change.
Describing a rule instead of building one
At the top of Settings → Rules is a box: say what you want in a sentence and Sage drafts the rule, then shows it in plain words with how many past transactions it matches before anything is saved. It is a starting point you can save, edit or throw away, not a shortcut past reading it. See Rules.
Asking Sage for a rule
Ask Sage to make a rule — "always put 702 SW 8th under Shopping" — and it drafts one and leaves it as a suggestion, with a name like 702 SW 8th → Shopping. Its answer ends with Open in rule editor, which opens the rule editor already filled in, on the web or in the iPhone app. Change anything you like and save it; until you do, it is not a rule and has changed nothing. Sage cannot save a rule itself. If you close the editor, the suggestion waits at the top of the rules list, marked as suggested by Sage, with the ones below.
Asking Sage to recategorize
Ask Sage to fix categories — "put these Kroger charges under Groceries" — and it proposes the changes as one batch, up to 200 at a time. Nothing changes yet. A card under its answer shows how many changes there are, the first few with where each one moves and why, and buttons:
- Approve all makes every change in the batch.
- Reject turns the batch down; nothing is changed.
- Review on Transactions page opens the batch in full, where you can untick changes before accepting the rest. For a batch of more than 15 changes, or one with changes Sage could not include, this is the main button.
Only these buttons approve a batch. Replying "yes" to Sage approves nothing, and Sage will point you to the card. Skipped on the card lists what was left out and why: a split transaction, one that is pending, one already in that category, or one whose category you chose by hand.
The same batch can carry more than categories. Ask Sage to tag the hotel and flights with Work, hide a reimbursed lunch, or file a charge under one of your businesses, and each of those is one change in the batch, shown in words: Add tag Work, Remove tag Trip, Hide, Show again, Business → ByteFoo LLC, or Business: ByteFoo LLC → Personal. You approve, untick or reject them exactly as you do a category. Sage uses only the tags in Settings → Tags and the businesses in Settings → Businesses: if you name one that is not there, it says so rather than making it. Filing a charge under a business keeps its tax line; making it personal clears the tax line too, and Undo puts both back.
Once applied, the card says Applied, with Undo for the next 30 days. Undo puts each transaction back as it was: its category, its tags, whether it was hidden, and its business. Each changed transaction's history shows the change as made by Sage, and the batch is listed on the Transactions page's Changes from AI apps list as from Sage. The card and that page show the same batch, so deciding in one place shows in the other.
Sage proposes only while What Sage can do in Settings → Preferences is set to Propose changes for you to approve, which is the default. It is your own setting, and it needs no household switch: a proposal changes nothing until you approve it. Set it to Only read your data and Sage proposes neither batches nor rules.
Rules an AI app suggested
If you have connected an AI app and allowed it to make changes, it can suggest a rule. Suggestions sit at the top of the rules list, marked as not being rules yet. Review opens one in the same editor, filled in, for you to change and save; Dismiss removes it. An app cannot create a rule itself. See Connecting an AI app.
The list is the same in the iPhone app, under Settings → Rules. In either place the editor shows how many of your existing transactions the rule matches, and counts again as you change it. The figure on a suggestion is from when the app made it, so the editor's count is the current one.
Merchant names SageFin suggests
Some merchants arrive with statement text instead of a name, like "SQ *ROBLOX 8823" or "Ysi*giles Road Self St". For those, and for your recurring bills, SageFin's AI may suggest a plain name, here Roblox and Giles Road Self Storage. Only the merchant's name is sent, and the names you already use, so it can match them; never an amount, an account or a date.
A suggestion shows as Suggested name under the merchant in Settings → Merchants, and on the bill in the recurring review. While any are waiting, a count of them sits above the merchant list; press it to see only those merchants, and each one leaves the list as you answer it.
- Accept renames the merchant on all of its transactions and on its recurring bill, the same as editing the name yourself. It also adds a rule: when the merchant equals "Ysi*giles Road Self St", set the merchant to Giles Road Self Storage. So later charges get the name too. You will find it in Settings → Rules and can change or delete it like any other.
- Reject leaves the name alone. That suggestion does not come back.
A name you chose always wins: a merchant you have renamed is never given a suggestion, and an Accept that arrives after you renamed it changes nothing. Each merchant is asked about once, whatever the answer was. Suggestions are made only while Let SageFin read my transactions and receipts with AI is on in Settings → Preferences.
Categories themselves
SageFin ships with a set of categories, and you can create your own in Settings → Categories — a household that thinks in terms of Horse or Boat or Kids' clubs should have those. Custom categories work in rules, budgets and reports exactly like the built-in ones.
Categories live inside groups, and you can make your own groups too. The group is what reports and budgets roll up to, so it is worth putting a new category somewhere sensible rather than leaving it beside things it has nothing to do with.
Rename one and it changes everywhere at once — in your history, your rules and your budgets — because they all point at the category rather than at its name.
Deleting a category, and why it sometimes refuses
A category with transactions in it cannot simply be deleted. SageFin asks you where those transactions should go and moves them first, because the alternative is history with a hole in it. The category you move them to has to be a real one you are keeping — not a group, and not another disabled category.
A built-in category is disabled rather than deleted. It stops being offered when you categorize something, and it keeps working everywhere it was already used. That is deliberate: the built-ins are what the automatic categorization writes, so removing one outright would leave a name in your history that nothing could explain.
Still not sure who decided?
Open the transaction. Under the category is a line saying where it came from — Set by one of your rules, From what SageFin has learned about this merchant, Chosen by AI, or Set by hand.
A few transactions say something else, and each is worth reading literally:
-
From your recurring bill — the charge belongs to a recurring bill you confirmed, and it took that bill's category. Change the bill's category and its later charges follow.
-
Matches this merchant's other charges — this merchant's last few charges agreed on a category, so this one got it too. No AI was asked.
-
Every item on the matched order had this category — the category came from a matched Amazon, Walmart or Costco order, not from a guess about the merchant name.
-
Taken from your bank's own category — your bank said what this was, and SageFin used it.
-
AI looked and found no category that fits — this is not waiting to be categorized. It was looked at, and nothing matched. A category of your own is often the answer.
-
Nothing has categorized this yet — nobody and nothing has decided. Different from the line above it.
-
Recorded before SageFin kept track of who decided — an older transaction, from before SageFin stored this. Who chose its category genuinely is not known.
There is no confidence score on the line, and that is deliberate: the model reports its own certainty, which is not the same as being right, and a percentage next to a category invites more trust than it has earned. What is worth acting on is the source. Fixing the same merchant by hand more than once is the signal that a rule is missing — that, rather than a number, is the best argument for writing one.
A split transaction shows no line, because it has no single category and so nothing single decided it. Each line of the split carries its own.