Product guides

Giving every merchant a default category

A default category on each merchant means future payments file themselves. See how to set them, which merchants need care, and when to skip.

Editorial illustration for Giving every merchant a default category

Setting a default category for a merchant is one of the highest-return tasks in the whole app. Once a merchant has a default, new transactions with that merchant can be filed without a decision from you. Done for your twenty most frequent merchants, it can remove most of the manual work from a typical month.

How defaults work

A default category is the category a merchant normally belongs to. When a transaction arrives with that merchant, the app uses the default as its first guess or assignment. If you later recategorise a particular transaction, that is treated as an exception, not as a change to the default.

The merchants screen even tells you when the work is finished: if every merchant already has a default category, it says so. Reaching that message is a reasonable goal for an afternoon.

Choosing defaults well

For most merchants the choice is obvious: a grocery store goes to groceries, a fuel station to fuel. The thinking is needed for merchants that sell a mix of things.

  • **Supermarkets and general stores.** They sell food, cleaning products and sometimes electronics. Pick the category that covers most of your purchases there.
  • **Online marketplaces.** The category varies by purchase, so choose a broad one and adjust exceptions.
  • **Payment apps and wallets.** The merchant name may be the app itself rather than the shop. Treat these carefully.
  • **Pharmacies.** Medical may be correct, though personal care purchases will sometimes appear.

A default only needs to be right most of the time. If a merchant is split half and half, no default will be correct, and a rule with extra conditions, such as an amount range, may do better.

Order of work

Begin with the busiest merchants. Sorting by frequency or by recent activity means that each default you set covers a large share of future transactions. Work down until the remaining merchants are used so rarely that handling them one at a time is perfectly fine.

After setting a batch of defaults, there may be older uncategorised transactions that now have a known answer. Check whether your tools let you apply the new defaults to existing entries, so history improves along with the future.

Where defaults go wrong

Defaults can conceal drift. A merchant that began as a regular coffee shop and then started selling lunches is still labelled as coffee. Reviewing the biggest merchants every few months catches this. Also watch for merchants that change meaning, such as a payment aggregator that serves different businesses over time.

Checking the effect

A week after setting a batch of defaults, look at the uncategorised count. It should have dropped. If some transactions still arrive without a category, note their merchants and handle them next. The measure of success is simply fewer transactions needing your attention.

Why defaults beat repeated manual edits

Setting a default once is a single decision applied many times. Editing each transaction by hand is the same decision repeated, and repetition is where errors and fatigue creep in. Even a ten-minute session on the most frequent merchants usually removes dozens of future edits. Over a year, the time saved is easily measured in hours, which is a strong reason to do this task first and polish everything else afterwards.

A tidy-up checklist

  • Open the merchants screen.
  • Filter or scroll to those without a default.
  • Assign the category that fits at least two-thirds of purchases.
  • Skip rare, one-off names.

Treat defaults as a living setting. They are cheap to change and powerful when right.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports