BR
BankStatementReader

Categorizing Bank Transactions: A Practical Workflow

By BankStatementReader Team ·

Categorizing your bank transactions turns a flat list of debits and credits into something you can actually use: a budget, a tax summary, or a clear picture of where the money went. The hard part is rarely the tool you pick — it is the method. This guide lays out a workflow that works whether you are using a spreadsheet, accounting software, or a notebook, so you can apply the same steps no matter where your data ends up.

Step 1: Define a category scheme first

Before you touch a single transaction, decide on your categories. A scheme that you invent row-by-row as you go will drift, overlap, and leave you re-sorting later. Start small and deliberate.

For personal finances, a workable starting set might be: housing, utilities, groceries, dining, transport, healthcare, subscriptions, income, and transfers. For a small business, you will likely mirror the lines on a tax form — see the IRS guidance on business expenses to keep your categories aligned with how you will eventually file.

Two rules keep a scheme usable:

  • Every transaction has exactly one home. If a charge could fit two categories, write down which one wins so the next one like it goes to the same place.
  • Keep the list short enough to remember. Ten to twenty categories is usually plenty. Sub-categories can come later once the top level is stable.

Step 2: Get the transactions into rows

You cannot categorize a PDF. The workflow needs your statement as structured rows — one transaction per line, with date, description, and amount in their own columns.

If your bank lets you download a CSV directly, start there. If you only have a PDF statement, convert it first with the bank statement converter, which detects the transaction table and exports clean rows you can sort and filter. Either way, the goal is the same: a tidy grid where the description column is searchable, because that column is what every rule in the next step depends on.

Once the data is in rows, add one empty column called Category. That column is the whole job — everything from here is about filling it in accurately and consistently.

Step 3: Apply rules and keywords

Most transactions are repeats. The same grocery store, the same streaming service, the same payroll deposit show up month after month with recognizable text in the description. That repetition is what makes categorization scalable: instead of judging each row on its own, you build rules that map a keyword to a category.

A rule is simply: if the description contains X, the category is Y. For example, a description containing "SHELL" or "CHEVRON" maps to transport; one containing "SAFEWAY" or "TRADER JOE" maps to groceries. Work from the merchants you recognize first, because those clear the most rows for the least effort.

How you implement rules depends on your tool. In a spreadsheet you can use formulas and find-and-replace to tag matching rows in bulk — the step-by-step approach is covered in categorizing bank transactions in Excel. In accounting software, rules are usually a built-in feature that runs automatically as transactions import, which is walked through in categorizing transactions in QuickBooks. The principle is identical in both: define the keyword, define the category, let the rule do the repetitive matching.

Step 4: Review what is left uncategorized

No rule set catches everything. After the first pass, filter for blank categories and look at what remains. These leftovers fall into a few buckets:

  • One-off purchases that will not recur — categorize them by hand and move on.
  • Cryptic descriptions where the merchant name is buried in a payment-processor string. Check the amount and date against your memory or receipts to identify them.
  • New recurring merchants you have not seen before. When you categorize one of these, write a new rule for it immediately so the next statement handles it on its own.

That last point is the one people skip, and it is the difference between a system that gets lighter over time and one that stays just as heavy every month. Each new rule you add shrinks the manual pile for every future statement.

Be especially careful with two ambiguous types. Transfers between your own accounts are not income or expenses — give them their own category so they do not inflate your totals. Refunds belong in the same category as the original purchase, entered as a credit, so the net spend in that category stays accurate.

Step 5: Stay consistent over time

A categorization scheme is only as good as its consistency. If "Uber" lands in transport one month and dining the next, your reports become noise. Consistency comes from treating your rules as the source of truth.

A few habits keep things steady:

  • Reuse the same scheme every period. Do not redesign categories mid-year; if you must change one, decide whether to re-tag the prior months or note the break.
  • Categorize on a regular cadence. A short monthly session beats a year-end marathon, because descriptions are fresher in your memory and the volume is smaller.
  • Keep your rule list in one place. Whether it lives in a spreadsheet tab or your software's settings, a single canonical list means you are never guessing how a merchant was handled before.

Putting it together

The workflow is the same regardless of method: define categories, get transactions into rows, apply keyword rules, review the gaps, and stay consistent. Pick the tool that fits how you already work. If you live in spreadsheets, follow the Excel approach; if you run your books in accounting software, follow the QuickBooks approach. And if your starting point is a PDF, convert it to rows with the bank statement converter before you begin — the cleaner the data going in, the less hand-sorting you will do at the end.

Related reading