Product guides

Rules that rename messy merchant names

Bank narrations are cluttered. A rule can rename a merchant on arrival, giving you readable lists and one consistent name per business.

Editorial illustration for Rules that rename messy merchant names

Open any transaction list built from bank data and you will see the problem at once: payment descriptions packed with codes, reference numbers and processor prefixes. Even when the category is right, the list is hard to read. One of the actions a rule can perform is renaming the merchant, which gives you clean names without touching the bank data itself.

What the rename action does

The rename action sets a display name for the merchant on transactions that match the rule. So a messy string containing a business name and a stream of digits can become simply the business name. Because the name now matches across transactions, reports that group by merchant combine them properly instead of splitting the same business into several lines.

The rule editor describes the action as renaming the merchant to a name you supply, with an option to leave it empty to keep the original. Leaving it empty is how you use a rule for other purposes, such as filing under a category, without changing names.

When renaming matters

Renaming is worth it for merchants you meet often, because the benefit repeats. Think about payments for fuel, daily groceries, a regular pharmacy, a commute or a recurring utility. For one-off payments, the effort is rarely justified.

It also helps with recognition. Months later, a clean name tells you at a glance what a payment was. A string of codes does not. That can be the difference between spotting an odd charge and scrolling past it.

Building a renaming rule

  • Choose a condition that reliably identifies the payee, such as a distinctive word in the description.
  • Check the preview to make sure only the intended payee is matched.
  • Enter the clean name in the rename field, in the form you want it to appear.
  • Decide whether the rule should also set a category, and whether it applies to existing transactions.

A tip on conditions: pick the part of the description that stays constant. Reference numbers and dates change on every payment, so a condition built on them will never match twice. The business name or processor label is usually stable.

Timing and existing data

The editor explains that renaming is applied as new transactions arrive. That matters if you expect it to rewrite your whole history. Older transactions may keep their old names, so your results depend on what is new. If you want a retrospective tidy, use the merchant tools to rename the directory entry as well, so past and future line up.

Choosing the name

Keep clean names short, consistent and recognisable. Use the name you would say aloud. Decide a convention, such as no suffixes and no capital letters beyond the first, and stick to it. If you track business and personal spending in one workspace, avoid names that mix both worlds.

Be cautious with people. Payments to individuals often show only a name or a handle. Renaming them is helpful, but think about whether you want personal names appearing in shared reports.

BeforeAfter a rename rule
Long description with a processor prefix and digitsPlain business name
Three spellings of one storeOne consistent name
Unlabelled app paymentClear label for what it is

Pairing with categories

The most efficient rules do both jobs at once. A rule that renames a merchant and files it under the right category leaves nothing to do by hand. Once a few of these exist for your most frequent payees, a typical import arrives almost fully tidy.

Review these rules every few months. Businesses change their descriptions, and a rename rule that stopped matching is easy to miss. If a favourite shop suddenly reappears with an ugly name, its rule probably needs a new condition.

SPENDIXAI JOURNAL

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

Explore your reports