Categories

A category is how a posting is classified. It is the single choice on a staged row that decides where the entry lands in your books, and two of the things you configure here quietly govern what happens elsewhere: which VAT codes you are allowed to pick, and whether the transaction counts as an acquisition or a disposal for cost basis.

Open Posting → Categories.

Standard and custom categories

SimplyLedger ships a set of standard categories, and they are the same in every entity. You cannot archive them, but you can change how they behave. The settings below apply to standard categories exactly as they do to your own.

Anything else in the list is a category this entity added.

Adding one

Use the Add category card. Names are uppercase letters and underscores only; the field enforces it as you type, so Staking Reward becomes STAKINGREWARD and you want STAKING_REWARD. A name that already exists is rejected.

Set the two options below at the same time, or leave them and set them from the table later.

Tax applicable on

None, Sales or Purchase. This controls which VAT codes are offered when posting with the category.

Leave it as None and only the No VAT code is selectable for that category. This is deliberate rather than a fault, and the posting screen marks it with an info icon reading other VAT codes are hidden because this category has no tax applicability configured.

So if a colleague reports that the VAT dropdown has almost nothing in it, this setting is the reason. Set the category to Sales or Purchase and the full list returns.

Cost basis side

None, Buy or Sell. This tells cost basis reporting whether activity in the category is an acquisition or a disposal.

A category with no side leaves its transactions showing as uncategorised in cost basis, which means they are absent from gain and loss calculations rather than counted as zero. If you run cost basis at all, every category that moves tokens in or out wants a side.

Changing a category

Both settings are dropdowns in the table and save as soon as you change them; there is no separate save step. The change applies to postings made from that point, so it is worth getting them right before a period's posting rather than during it.

Archiving

Custom categories have an archive action at the end of their row. Standard categories do not.

Archive rather than expecting a delete: postings already made against the category keep their classification.

Who can edit

Adding, changing and archiving categories all need write access to the entity. Viewers and guests see the list with the values as plain text. See roles and permissions.

Where categories are used

Used by	How
Posting	The category set on each staged row.
Posting rules	The category a rule fills in automatically.
Hold matches	A hold account can be restricted to matching only certain categories.
Cost basis	Through the cost basis side above.

Next

Posting rules applies categories automatically to transactions that keep recurring.