Ace Budget Auto-Categorization Rules, Set Up Once

Most of the tedium in budgeting is not the thinking. It's typing the same category next to the same coffee shop for the ninth week in a row. Ace Budget auto-categorization rules exist to end that loop: you tell the budget once where a merchant belongs, and it files that merchant for you from then on.

This is a tutorial for setting those rules up well — including the places where a rule is the wrong tool and you're better off doing it by hand.

What Ace Budget auto-categorization rules do (and don't do)

A rule is a match on the payee plus a category. When a transaction's payee matches, the category gets filled in.

Rules run in two places:

• On imported bank spending, automatically, once the charge posts. A pending charge sits and waits; it gets categorized when it posts with its final amount.
• On transactions you type in yourself, where the rule fills in the category as you add it.

Two honest limits. First, rules only ever categorize spending. Deposits are never touched by them — money coming in lands in Ready to Assign and is handled by your income rules instead, which is a separate feature with separate settings. Second, a rule assigns one category. If a purchase needs to be split across several, that's still a decision you make on that transaction.

The one-tap way: teach it while you're already categorizing

You don't need to go hunting for a rules screen to build most of your rules. Just categorize as normal.

When you change a transaction's category, Ace Budget asks whether you want to always categorize that merchant the same way. One tap saves the rule. That's the whole workflow, and it's the one I'd lean on for the first month.

The practical effect: the first time you see a new coffee shop, you spend three seconds; the twentieth time, you spend zero. Your review queue shrinks week by week on its own, without you ever setting aside an evening for "rule maintenance."

If you'd like a nudge to do this regularly, the Android app has a transactions to review notification with its own toggle, plus quiet hours so it doesn't buzz you at 6 a.m.

Writing a rule by hand when the payee text is messy

Bank descriptions are rarely tidy. The same grocery run might import as the store name plus a store number, a city, and a string of digits. For those, write the rule yourself. Ace Budget gives you four ways to match:

1. Contains — the workhorse. A rule matching "KROG" catches every store number and city variant.
2. Starts with — useful when a merchant prefix is stable but everything after it changes.
3. Exact match — for payees that import identically every time, and when you want no collateral damage.
4. Pattern — for the odd case where the text varies in a structured way and the other three are too blunt.

A rule of thumb: start with the shortest fragment that is unmistakably that merchant, and no shorter. "MART" will quietly swallow several merchants you didn't intend. "WALMART" won't.

When a newly imported transaction has one, the memo carries the bank's own description of the purchase, which is often where the useful identifying text lives. Reading a few of those before you write a rule saves guessing.

How to file your backlog with "Apply to past…"

Every rule has an Apply to past… action. Before it changes anything, it shows you how many uncategorized transactions already in your register it will file. You see the number first, then decide.

Two things to know about it.

It touches uncategorized transactions only. If you miscategorized six months of a merchant into the wrong category, a rule will not go back and fix those — you'll edit them yourself. That's a deliberate limit, and a good one: you don't want a rule quietly rewriting decisions you already made.

And because it changes past months, it changes past months' numbers. If you're sitting on a long backlog, apply one rule at a time and glance at the categories it touched rather than firing off ten rules and trying to work out afterward what moved.

When one merchant is really two categories

The big-box store is the classic problem. Half the receipt is groceries, half is a lamp and a pack of socks.

You have three reasonable options, and none of them is automatic:

Pick the dominant category and let the rule handle it, accepting that groceries will run a little high. Simple, slightly inaccurate, and fine for a lot of households.

Skip the rule for that merchant and split the transaction each time across the categories it actually covers. More accurate, more work.

Or set a rule to a catch-all category you check deliberately, so those purchases are never unsorted but always get a second look.

There's one more interaction worth knowing if you enter purchases by hand and also import them from a bank. In Reconcile, Match bank transactions pairs your hand-typed entry with the bank's version. A match keeps the bank's amount and date but takes your entry's category, splits and memo, then removes your duplicate. So a split you built by hand survives the match — the bank's copy doesn't overwrite your work with a plain rule-assigned category.

A first pass you can do this week

Open your register, filter to uncategorized, and work down the list. Categorize each one, and say yes to the rule prompt whenever the merchant is one you'll see again. For anything whose payee looks like a serial number, write a contains rule by hand instead. Then run Apply to past… on the three or four rules that cover your most frequent merchants, checking the count each time before you confirm.

Thirty minutes buys you most of the benefit. The rest accumulates on its own, one tap at a time, as new merchants show up.

If you want to try this before committing, the sign-in screen has a demo that runs entirely on your own device with no account. New customers get a 60-day free trial.