Watch
AvaTax for SAP Business One in action.
Three short walkthroughs: how AvaTax works inside SAP Business One, how one sale travels from quotation to cancellation, and how exempt customers are handled with ECM.
1. Overview: calculation, validation and posting
How tax is calculated, addresses are validated and documents are posted from SAP Business One to Avalara.
2. The document flow: from quotation to cancellation
One sale followed end to end — quotation, sales order, delivery, A/R invoice, credit memo and cancellation — showing what AvaTax calculates at each step and what it actually records.
3. Exempt customers and ECM
How exempt customers are set up and kept in sync — exemption certificates in Avalara ECM, customer codes, entity use codes and what happens on the invoice when a certificate is on file.
Need a specific scenario covered? Send it to support and we will walk you through it.
What we cover
Everything between SAP Business One and Avalara.
Technical and functional support for the AvaTax add-on, the Avalara account and the business processes that depend on both.
Tax calculation issues
Unexpected tax amounts, zero tax, wrong jurisdiction, origin and destination sourcing, nexus and tax-type mismatches.
Address validation
Ship-to and warehouse addresses that fail validation, bulk validator runs and drop-ship destination handling.
Exemptions and certificates
Exempt customers taxed or taxable customers exempted, entity use codes, CertCapture sync and per-document exemptions.
Reconciliation and posting
Invoices or credit memos missing in Avalara, tax and total mismatches, force re-posting and journal entry handling.
Add-on, AES and WebUI
Add-on upgrades, Service Layer connection, Event Service for third-party documents and WebUI scheduled runs.
Configuration changes
New tax codes, custom rules, additional companies or warehouses, new states and changes in how tax is stored on documents.
How it works
Send us the case, we take it from there.
The faster we can reproduce the issue, the faster it gets solved. Include the SAP document number, the Avalara environment and what you expected to see.
Email info@tax-bridge.ioFAQ
Common AvaTax support questions.
Usually one of four things: no nexus selected for the destination state, an exemption or entity use code applied to the customer, the item mapped to a non-taxable tax code, or the document not carrying the AvaTax trigger tax code on any line. We check them in that order.
The Reconcile tool in the add-on finds documents missing in Avalara and posts them as committed or uncommitted. Because invoices cannot be edited after creation, tax is stored in the AvaTax UDFs or through a journal entry rather than on the document itself.
Documents created through DI-API, DI-Server or Service Layer bypass the add-on. The AvaTax Event Service handles those: it taxes sales orders and posts invoices and credit memos to Avalara. We can install and configure it for you.
We cover configuration inside the AvaTax console (nexus, tax codes, rules, exemptions, locations) and escalate to Avalara Support or your Account Manager when the issue is on their side. Licensing and billing stay with Avalara.
Yes. We recommend keeping an SAP test company connected to your Avalara sandbox so every configuration change is validated there first.
Need help now?
Open an AvaTax support request.
Include the SAP document number, the Avalara environment and what you expected to see, and we will come back with a diagnosis.
Email info@tax-bridge.io