Tax is configured once per jurisdiction and applied per line on invoices and expenses.
Jurisdictions come from your hubs
The list of jurisdictions is derived from where your organisation actually trades rather than being a menu of every country.
That keeps the surface short and it means adding a hub in a new country surfaces its tax configuration rather than requiring somebody to remember.
Rates
Each jurisdiction carries its own rates, and how they are shown depends on the country.
Most jurisdictions show a single rate per tax type.
India shows components, because the tax is split: either central and state components together, or the integrated rate for interstate supply. Showing it as one number would be wrong and would make the resulting invoices wrong.
That difference is not cosmetic. It is the reason a generic tax field is not sufficient for a business trading in India, and it is handled here rather than being somebody's spreadsheet.
Seeding
A jurisdiction with no rates offers to seed the standard set for that country.
Worth taking. Entering nine slabs by hand is an afternoon and an opportunity for a typo that will appear on customer invoices.
Seeded rates are a starting point and remain editable, so anything specific to your situation can be adjusted afterwards.
Each rate posts somewhere
A rate carries the accounts it posts to, which is what connects tax to the ledger.
When an invoice is sent, the tax on it credits the account the rate names. When an expense is approved, the tax on it debits the account it names. Neither requires a journal entry.
Getting these accounts right is the part that matters, because tax collected is money you are holding on somebody else's behalf, and it belongs in a liability account rather than mixed into revenue. A rate posting to the wrong account produces a profit and loss that overstates income and a balance sheet that understates what you owe.
Treatment is per line
An invoice applies tax per line rather than to the whole document.
That is necessary rather than elaborate. A single invoice frequently mixes standard-rated work with something zero-rated, exempt, or outside scope entirely, and applying one treatment to all of it is the most common way a compliant business produces a non-compliant invoice.
Reverse charge and cross-border
Where the customer accounts for the tax rather than you, the treatment reflects it and the invoice shows it.
This is worth setting up correctly before the first cross-border invoice rather than after. Getting it wrong means either charging tax you should not have, which the customer will query, or not charging tax you should have, which is your problem rather than theirs.
Zero-rated, exempt and out of scope
Three treatments that all result in no tax charged and mean different things, and conflating them is a common compliance error.
Zero-rated is taxable at nought per cent. It counts as taxable supply.
Exempt is outside the tax entirely, and frequently affects how much input tax you can reclaim.
Out of scope is not a supply the jurisdiction taxes at all.
The invoice looks identical in all three cases. The returns do not, which is why the treatment is recorded per line rather than being inferred from the fact that the tax was zero.
What this does and does not do
It calculates. Correctly, per line, per jurisdiction, with the right components.
It records. Every tax amount posts to a named account, so what you owe is a figure in your books rather than a calculation somebody does at quarter end.
It does not file. No return is submitted anywhere. The platform tells you what you collected and what you paid; lodging it is a separate act.
It does not advise. Whether a particular supply is zero-rated in your jurisdiction is a professional question. The platform applies the treatment you choose.
Expenses have tax too
Tax is not only an invoicing concern. Tax paid on an expense is usually recoverable, and it has to be recorded to be recovered.
That is why expense approval posts tax to its own account rather than lumping it into the cost. A business that records expenses gross is overstating its costs and understating what it can reclaim, and the amount is rarely trivial over a year.
Where tax appears
Two places, and they are different accounts.
Tax you charge on an invoice is money held on behalf of the authority. It belongs in a liability account until it is paid over.
Tax you pay on an expense is usually recoverable, and it belongs in an asset account until it is reclaimed.
Netting the two happens at return time. Recording them as one account from the start makes that impossible to unpick.
Multiple jurisdictions
An organisation trading from more than one hub carries a rate set per jurisdiction, and an invoice uses the one for the entity issuing it.
Worth checking when a second hub is added. The new jurisdiction arrives with no rates, and the first invoice from that entity is the moment somebody discovers it.
What a rate carries
More than a percentage. Each rate names the accounts its tax posts to, so the configuration and the bookkeeping are one thing rather than two that have to agree.
For a jurisdiction with components, each component carries its own, which is what makes a split tax post correctly rather than being recorded as a single lump that somebody has to break down later.
Rounding
Tax rarely divides cleanly, and how the remainder is handled has to be consistent.
It is applied per line and totalled, which is the treatment most jurisdictions expect. The practical consequence is that a total may differ by a unit of currency from the same amount taxed as one lump, and that is correct rather than an error.
Worth knowing before somebody recalculates an invoice by hand and reports a discrepancy.
Two habits
Set it up before the first invoice, not after. Correcting tax on issued invoices means credit notes and awkward conversations, and it is entirely avoidable.
Review rates when a jurisdiction changes them. Nothing here tracks legislation. A rate that changed in April and was not updated produces quietly wrong invoices until somebody notices, and the person who notices is usually a customer.
Did this answer your question?
No, ask a person