How Avalara AvaTax connects to Oracle Fusion Cloud ERP
Avalara connector for Oracle ERP Cloud (web services)
The connector is a web services layer hosted on Oracle Cloud Infrastructure. Oracle Fusion Tax calls out to AvaTax with the transaction lines, ship-from, ship-to and item tax codes, and receives tax amounts back to store on the invoice lines.
Fusion Tax configuration and tax codes
Inside Fusion you set up the tax regime and configuration that route calculation to the external provider, and map Fusion items or product categories to Avalara tax codes. Exemption certificates and customer entity-use codes are carried across so exempt sales calculate to zero.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Oracle Fusion Receivables / Order Management | Avalara AvaTax | Invoice or order lines, ship-from and ship-to addresses, item tax codes, customer exemption data | Transaction is saved or completed, or tax is recalculated |
| Avalara AvaTax | Oracle Fusion Tax | Tax amounts by jurisdiction and line | Response to the calculation call |
| Oracle Fusion Payables | Avalara AvaTax | Supplier invoice lines for use tax determination | AP invoice validation |
| Oracle Fusion | Avalara reporting | Committed transactions for returns and audit | Invoice posted or period close |
Setting it up
- 1Scope the tax footprintList the legal entities, ship-from locations and states or countries you collect in, and decide whether AP use tax and e-invoicing are in scope.
- 2Create the Avalara company and nexusSet up the company, locations and nexus jurisdictions in the Avalara portal, and generate the account credentials used by the connector.
- 3Configure Fusion TaxDefine the tax regime, rates and the configuration that points calculation to the external service, with the integration user holding only the required roles.
- 4Map items to tax codesAssign Avalara tax codes to Fusion items or categories. Freight, installation and miscellaneous charges need their own treatment.
- 5Load exemption certificatesAlign customer records with Avalara exemption handling so resale and manufacturing exemptions flow through.
- 6Test in a non-production podRun taxable, exempt, multi-state, credit memo and rounding cases and compare results to a manual calculation before go-live.
- 7Cut over and monitorEnable in production, watch calculation errors for the first close, and reconcile Fusion tax totals to the Avalara return data.
What usually breaks
- !Items without an Avalara tax code default to taxable, so non-taxable parts and services are over-charged until mapped.
- !Address quality: incomplete or unvalidated ship-to addresses return wrong jurisdictions or calculation errors.
- !Credit memos and partial returns that do not reference the original transaction can leave the tax ledger out of step with Avalara.
- !Rounding differences between Fusion line rounding and Avalara jurisdiction rounding create pennies of drift that fail reconciliations.
- !Expired exemption certificates silently turn exempt customers taxable again.
- !Quarterly Oracle updates can change tax-related setup behavior, so re-run the regression cases after each update.
A private AI layer across both systems
Tax exception triage
A private assistant reading Fusion invoices and the Avalara transaction log can list invoices where calculation failed or fell back, with the likely cause such as a missing address or unmapped item.
Reconciliation in plain language
Ask which invoices differ between Fusion tax totals and Avalara for a period, and get a drill-down by jurisdiction for the tax team to review.
Drafting tax code mappings
For new items, the assistant proposes tax codes from item descriptions and past mappings. A tax professional approves before anything is written back.
Try it here, free
Oracle Fusion Table Names Reference for SCM and Financials
A searchable reference of widely used Oracle Fusion SCM and Financials table names with what each holds and the keys to join on.
When something else fits better
- Oracle Fusion Tax native rates and rules are enough for a single state or a small number of jurisdictions.
- Vertex or Thomson Reuters ONESOURCE are the other mainstream engines for Fusion, and may already be in your Oracle contract.
- For on-prem Oracle (EBS or JD Edwards), look at the Vertex or ONESOURCE connectors rather than a Fusion-specific path.
Frequently asked questions
How long does an Avalara and Oracle Fusion implementation take?
Avalara quotes 30 to 60 days for the Oracle ERP Cloud integration. The real timeline depends on how many legal entities and jurisdictions you cover, how clean item tax codes and addresses are, and how long testing and the first close reconciliation take.
Where does the connector run?
Avalara describes it as a web services connector hosted on Oracle Cloud Infrastructure. Fusion Tax calls it for each calculation, so there is no connector server for you to patch, but outbound calls to Avalara must be allowed by your Oracle tenancy.
Does it handle e-invoicing?
Avalara lists its e-invoicing and live reporting product as also available for Fusion. It is a separate scope from sales tax calculation, with its own country mandates and setup, so plan it as a distinct workstream.
Can this run on-prem?
Fusion Cloud ERP is SaaS, so the ERP side is cloud. If your plants run on-prem Oracle EBS or JD Edwards, a different connector applies, and Netray's private AI layer can still sit on exported or replicated data inside your network.
Pairing documented at www.avalara.com/us/en/products/integrations/oracle/oracle-erp-cloud-fusion-finan . Avalara AvaTax is a product of Avalara; Netray is independent and not affiliated with either vendor.