Overview
Tax on a clean order is a solved problem. Tax becomes interesting when the order stops being clean: a line is cancelled, a delivery splits, an item comes back four months later.
The AvaTax app calculates US sales tax and Canadian GST/HST/PST/QST against current rules and writes the exact amounts onto the order. Not a rate that gets re-derived later — the figures the tax engine returned, which is what makes them hold up where several jurisdictions combine and each rounds in its own way.
When Hantera_ raises an invoice it is recorded for filing, and when a return produces a credit it is recorded against the original sale’s tax treatment. That is the part that is easy to get wrong by hand and expensive to discover at audit.
Rollout is per channel, each with its own ship-from origin, so a market can be switched on without disturbing the others. And if the service cannot be reached, the order still goes through — tagged and logged, so it is an operations task rather than a failed checkout.
What it does
-
Tax calculation on carts and orders
Writes the exact amounts Avalara returns onto order lines, shipping and fees, rather than applying a rate — which matters where state, county, city and district rates combine and round separately.
-
Document recording
Hantera_ invoices are committed to Avalara as sales invoices, and credit invoices from returns are committed at the original sale's tax date.
-
Voiding
Cancelling a Hantera_ invoice voids the corresponding AvaTax document.
-
Tax code and exemption tooling
Look up Avalara tax codes from the portal, assign them per line, fee or shipping line, and set document-level entity and use codes per order.
-
Address validation
Validate and normalise a delivery address against Avalara's address service.
-
Per-channel rollout
Enabled per channel with its own ship-from origin, so a market can go live without affecting the others.
-
Non-blocking failure
If the service cannot be reached the order keeps its existing tax, is tagged for follow-up, and the error is written to the order timeline.
Apps that usually run together.
Most operations install more than one. These are the apps this one is most often paired with, because they share the same order.