Tax category fields
A tax category is Yessort's description of how something is taxed; the mapping resolves it to a code in your accounting system. Concept background in tax categories.
The category
| Field | What it does |
|---|---|
| Name | What the treatment is called in Yessort |
| Rate | The percentage applied |
A rate alone is not enough to post correctly. Zero-rated and out-of-scope are both zero percent and belong on different lines of a return, so the category carries the treatment and the rate is only part of it.
The mapping
| Field | What it does |
|---|---|
| Provider | Which connected system this mapping is for |
| Tax code | The code in that system |
One mapping per category per provider, so the same category resolves to whatever each system calls it.
When no code is resolved
The entry still posts. The line lands at the account's own default tax treatment.
This does not fail loudly, which is what makes it worth attention. There is no error and nothing appears in a queue — the entry goes through and the treatment is whatever the account defaults to. That may be right, and may quietly not be.
Unmapped tax categories are therefore best cleared early, before volume builds up behind a default nobody chose.
What a post records
Composition per account and tax code pair, not just a total. That is what lets an edit spanning two rates book faithfully instead of netting to a plausible wrong answer. See editing an order after posting.
Accounts are separate
How a line is taxed and which account it lands in are different questions. See accounting category fields.