Accounting category fields
An accounting category joins a kind of Yessort activity to an account in your accounting system. Concept background in accounting categories.
The category
| Field | What it does |
|---|---|
| Name | What the category is called in Yessort |
| Code | A short identifier for it |
Categories are Yessort's own. They do not change when you change provider.
The mapping
| Field | What it does |
|---|---|
| Provider | Which connected system this mapping is for |
| Account | The account in that system |
One mapping per category per provider. The same category can point at different accounts in different systems, which is what lets the category stay stable while the account code varies.
Accounts are chosen from the provider's real chart of accounts, read from the connection — so you pick rather than type.
Manual accounting exposes no chart of accounts, since there is no external system. Categories still exist and still organise activity; there is nothing external to map onto.
When a mapping is missing
Entries needing that account are not built and not lost. They are held and released once the mapping exists — including the ones already waiting.
So the sequence is: map the account, and the backlog clears itself. There is nothing to replay by hand.
What is not decided here
Sales revenue. Sales posting uses your organisation's default revenue account. Per-variant accounting categories are not yet wired into it, so setting a category on a variant does not currently change where its sales revenue lands.
Categories do decide the account for goods-receipt valuation journals, supplier bills and COGS — which is why those are the entries that appear in Issues when a mapping is missing.
Tax is separate
Which account a line lands in and how it is taxed are two different questions. See tax category fields.