If you keep fixing the same merchant every month, the app is treating each correction as a one-off. Turn it into a rule once, such as all rows containing a petrol pump name go to Fuel, and every later statement is sorted for you. For gig workers the same eight or ten names show up all month, so a handful of rules removes most of the chore.
Why does the same merchant keep coming back wrong?
Bank narrations are not tidy. The same fuel pump can appear with a different reference number each time, a payout from a delivery platform may carry a batch code, and a recharge may show the wallet's name in one row and a gateway's name in the next. An app that matches on the exact text will see a new merchant every time.
Even when it does recognise the merchant, it may pick the wrong category the first time. Without a rule, that wrong guess repeats.
Which rows should become rules first?
Count before you create anything. Take last month's statement and tally the corrections you made. A rider might see this:
| Merchant text | Rows a month | Right category |
|---|---|---|
| Petrol pump name | 14 | Fuel and vehicle |
| Platform payout label | 22 | Income, platform payouts |
| Mobile recharge | 2 | Phone and data |
| Bike service shop | 1 | Vehicle maintenance |
| Parking and toll | 9 | Fuel and vehicle |
That is 48 rows from five merchants. Fixing them by hand each month is 48 edits, or 576 over twelve months. Three rules, for the pump, the payout and parking and toll, would have handled 45 of the 48. The service shop can stay a manual fix.
How does SpendixAI avoid the repeat?
Categorisation goes in stages: your own rules first, then merchant defaults and your own history, then AI only if you have it on. A rule matches the text you give it and assigns the category you choose. A correction you make also becomes history, so a similar row finds its category next time without any rule at all. If one merchant appears under two spellings, add an alias so both map to the same name.
Create the rule from a row you have just corrected, not from memory. That way the matching text is exactly what your bank prints.
What if the same merchant should sometimes go elsewhere?
This happens with a general store or a fuel pump with a shop attached. The honest answer is that no rule can tell a litre of petrol from a packet of biscuits on one narration. Keep the rule for the common case, and edit the rare exception by hand. If the rare case is frequent, split by amount: a rule for the usual fill-up range is clearer than a vague catch-all.
What does your income side need?
Gig income arrives as payouts, sometimes in lumps, sometimes weekly. Put the payout label in a rule too, so credits land under platform income and not under uncategorised. Refunds from a shop are different from earnings; keep them separate, or your monthly income will look better than it was.
A twenty-minute routine for next month
- Download the statement and import it, picking the right account first.
- Open the rows left for review and sort them by merchant.
- Create a rule for any merchant that appears three or more times.
- Add an alias where one merchant has two spellings.
- Rerun the review next month and note how many rows were left; the number should fall.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


