VAT software that decides line by line
Most tools aggregate your sales and report totals. Nomad VAT takes the tax decision at transaction level, then keeps the reason for that decision.
Aggregating is not qualifying
A sales total by country does not say which regime applies. Two sales to Germany can come under the OSS for one and a local registration for the other, depending on the country the goods leave from and on the customer's status.
As long as the decision is not taken at line level, it is taken implicitly at aggregate level — and what is implicit cannot be justified.
What a transaction-level engine changes
Five concrete differences with a conventional reporting tool.
The decision is taken at the transaction
Every line carries its regime, its country of taxation and its rate. Totals are a consequence, not a starting point.
Every decision keeps its reason
The rule applied and the data used stay attached to the transaction. A disputed figure unfolds back to its source.
The engine flags instead of guessing
An incomplete address or an invalid VAT number produces an alert, not a default value that would travel through the return unnoticed.
Several platforms, a single period
Shopify, Stripe, Amazon and CSV exports are reconciled over the same period, with the same decision engine.
The limit is stated
Whatever falls outside the covered scope is flagged as such. Tax software that answers wrongly with confidence is more of a problem than software that asks for information.
The scope covered
Frequently asked questions
See the decision, not just the total
Upload an export: every transaction comes back with its regime and its justification.