Categories are the interface between messy reality and clean reporting.
If categories drift, everything built on top of them drifts too: budgets, taxes, forecasts, and your confidence.
Treat categories as a contract
A category should mean the same thing today as it did six months ago.
That doesn’t mean you never change categories. It means you change them deliberately:
- add a new category when it reduces ambiguity
- rename with care
- keep a record of what changed and why
Use “holding” categories without shame
Sometimes you genuinely do not know. A good system lets you say that.
Use a holding category like:
- “Review: uncategorized”
- “Review: needs receipt”
- “Review: split transaction”
The point is to keep uncertainty visible so it can be resolved.
The FinArctic angle
If TaxTundra and GlacialBooks don’t agree on categories, your workflow becomes translation work.
That’s why we care about stable category primitives and export formats. It’s also why we put design tokens and service contracts behind a single discovery layer: consistency should be enforced by the system, not by memory.