Product guides

Merchant detail: reading one shop's history at a glance

Each merchant has its own page with recent spend, aliases, a default category and merge tools. Learn what to check and what to change from there.

Editorial illustration for Merchant detail: reading one shop's history at a glance

The merchants directory gives you the whole list. Opening a single merchant gives you its story: how much you have spent there, when you last visited, how its name is recognised and how its transactions are filed. A short visit to one merchant's page often fixes a problem that would otherwise recur in every import.

The top of the page

The page opens with the merchant's name, and its display name if you have set one. Beside these you will find the last seen date and a recent spend figure. A merchant not seen for a long time may belong to a service you have stopped using. A merchant with surprisingly high recent spend may deserve a closer look.

A list of transactions below shows the actual payments. If there are none yet, the page says so.

Display name and aliases

Bank descriptions for one business come in many forms. An alias is a raw descriptor that resolves to this merchant. The page lists them with the highest priority first and notes that an alias wins over the merchant name itself. You can add an alias, and the screen confirms that new transactions carrying it will be recognised. You can also remove an alias after confirming.

If a merchant has no aliases, descriptors still match by name. Add aliases only for variants that fail to match on their own.

Default category and business flag

Here you decide how transactions from this merchant are filed. A default category files them automatically. A business default marks new transactions as business, or personal if you prefer. You can clear a default if it no longer fits. The page shows when nothing is filed automatically, which signals that work remains.

Applying changes to the past

When you set a default, the page offers a choice: apply to new transactions only, or also fill the gaps among existing ones. Choosing to fill the gaps categorises past transactions that have no category yet, which cleans up history. It is the quicker route when you are setting a default for a merchant with many old, unlabelled payments.

Merging duplicates

If the same business appears as two merchants, the page lets you merge a duplicate into this one. The dialog explains that the duplicate's transactions and aliases move across, and the duplicate is deleted. Check the pair before confirming, since merging is a significant change. After merging, spending at that business appears in one place.

Who can change merchants

Merchants are managed by owners, admins and accountants. If you see a no-access message, your role does not include this area, and an administrator can help.

SectionWhat to check
Last seen and recent spendIs the merchant still active?
AliasesDo variants resolve here?
Default categoryDoes it suit most payments?
Business flagShould new payments be marked?
Merge optionIs there a duplicate to combine?

When to leave a merchant alone

Not every merchant needs attention. A shop you visited once has little to configure. Focus on merchants that appear often or hold large amounts. A good threshold is merchants with several transactions in the last quarter. Everything below that line can be handled by the review queue, one payment at a time, as it arises.

A two-minute visit

Pick the merchants you pay most often and visit each once. Check the default, add any aliases that are missing, and merge obvious duplicates. The result is a cleaner directory and a quieter review queue for every month that follows.

SPENDIXAI JOURNAL

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

Explore your reports