Why the narration looks the way it does
Bank and card statements show the name sent by the payment processor, not the name on the app. A food order might appear as a string of capital letters, a parent company name or a code. Two different restaurants may share the same prefix, while one app appears under several variants. The result is a transaction list that is hard to read and a food report that is incomplete.
Find the messy names
Open the last two months of food-related transactions and sort them by merchant. Note any that look unfamiliar, share a prefix with others or appear in more than one form. Typical patterns include a delivery platform’s name plus a code, a restaurant name with a branch number, and a grocery chain’s name with a store location.
List them in a note. Ten minutes of this scan typically reveals a dozen entries needing attention.
Create aliases
For each messy name, set a clear alias, such as the app’s common name or the restaurant’s. In the merchant settings, link the original strings to the alias and choose a default category. Once set, future transactions from the same string will be renamed and categorised automatically.
| Raw narration | Alias | Default category |
|---|---|---|
| Long coded string for a delivery app | Delivery app | Food delivery |
| Store chain plus location code | Supermarket | Groceries |
| Restaurant plus branch code | Restaurant name | Eating out |
Handle shared strings carefully
Some merchants serve more than one purpose. A supermarket may sell groceries and household items, and a delivery platform may carry groceries as well as restaurant meals. For these, set the default to the most common use and correct exceptions when they appear. The categoriser learns from corrections.
Review the uncategorised list
After setting aliases, check items still without a category. They are typically one-off merchants, such as a roadside stall or a small shop. Assign categories to these manually; if the same merchant is likely to appear again, create an alias too.
Keep the list tidy
When a new app or restaurant appears, make setting an alias part of the monthly review. It takes a minute and keeps the list from rebuilding the mess. If a merchant changes its name or processor, update the alias rather than creating a new one.
The benefit in numbers
With clean names, the monthly food reports become accurate. The household can see exactly how much goes to each app, which restaurant gets the most visits and which grocery chain takes the largest share. Those facts support decisions, such as which membership is worth keeping or which store to shop at. A little tidying makes every later report better.
Handling payments through shared wallets
If food is paid through a shared wallet or a family account, the merchant string may carry the wallet provider’s name rather than the shop’s. In that case the order screen in the wallet app, with its own history, is a better source for naming. Match it against the statement and set the alias accordingly. A few minutes with both screens open settles the question permanently.
Checking the default categories
After setting aliases, test the result with the next few transactions. A wrong default is easy to fix, but only if it is noticed. Open the latest food entries, look for anything in an odd category and correct it. The categoriser learns from each fix, so a few minutes of attention at the start produces a much smoother experience afterwards and reduces the monthly clean-up to a brief scan.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


