Receipts

How to categorize spending when statements only show merchant names

July 2026

You cannot reliably categorize spending from a bank statement, because a statement line carries a merchant name and a total, nothing more. “POS 4711 SUPERMARKT, 84.20” tells you where you paid. It cannot tell you what you bought, and the category lives in the what. Every tool that categorizes from statements is guessing, and this guide is about when that guess holds, when it breaks, and how to categorize from the source instead.

Why merchant-based categories are a guess

Categorization from statements works by mapping merchants to categories: this merchant is a supermarket, so the transaction is groceries. For single-purpose merchants the guess is fine. A bus ticket machine sells bus tickets. A cinema sells cinema.

The guess breaks at every merchant that sells more than one kind of thing, and those are exactly the merchants where most of your money goes:

The supermarket basket with groceries, shampoo, a phone charger, and cat food becomes one line called “Groceries”, even though a third of it was not food.
The pharmacy run that was half medicine, half cosmetics: one line, one category, half wrong.
The department store, the gas station shop, the everything-store online order: the bigger the merchant, the less its name says about your basket.

Multiply that by a month of shopping and your category chart is not a picture of your spending. It is a picture of where you stood when you paid.

The fixes people try

Manual recategorization. Splitting statement lines by hand into partial amounts. Accurate, and nobody sustains it, because you are reconstructing baskets from memory a week later.

More merchant rules. Mapping tools let you refine rules per merchant. But no rule can split a single line into what the basket actually contained. The information simply is not in the statement.

Accepting the blur. Many people settle for categories that are roughly right. That works until you try to act on them: you cannot trim a “Groceries” number that secretly contains electronics.

Categorizing from the source

The receipt already contains what the statement lost: every line item, named and priced. Categorize from the receipt and the mixed-basket problem disappears, because categories attach to products, not merchants.

That is how Reign works. Snap the receipt and it reads each line item, then sorts every item into its own category. The supermarket basket lands as food, household, and electronics, each with its own number. You review what was read, fix anything you disagree with, and save. No merchant rules to maintain, because there is no guessing step to correct.

Your monthly picture changes character. “Groceries: 640” becomes what it really was: food at 470, household at 110, and 60 of things that deserved their own conversation.

Where statement lines still make sense

Honesty about the trade: item-level categorization needs the receipt in your hand. For history you import from a bank CSV, the line is all there is, so imported transactions carry merchant-level categories, and that is fine for seeing the shape of the past. The receipts you snap from today forward carry the detail. Reign keeps both in one searchable ledger, the history at statement depth and the present at receipt depth.

Start with one basket

Take your next mixed supermarket receipt and snap it. Watching one basket split itself into real categories explains this guide faster than reading it.