Oracle Fusion Cloud ERP and Avalara integration

What moves between them

The main flow runs from Oracle Fusion Cloud ERP into Avalara. When an invoice is posted in Oracle Fusion Cloud ERP, ml-connector polls for the new record, sends it to Avalara with customer address and line item details, receives the calculated tax amount and rate, and posts the tax liability journal into Oracle Fusion Cloud ERP's general ledger mapped to the appropriate GL account and cost center. Purchase invoices and customer invoices both flow through the same pattern. Tax codes and addresses are synced first so every invoice sent to Avalara has valid jurisdictional information, and committed Avalara transactions are reconciled back to Oracle Fusion Cloud ERP for auditability.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Oracle Fusion Cloud ERP side it accepts the customer pod URL and filters new invoices by LastUpdateDate or CreationDate using OData query parameters. On the Avalara side it uses Account ID and License Key authentication and tracks document codes to prevent duplicate submissions, since Avalara returns DocumentCodeConflict if the same document code is posted twice. Because neither system has outbound webhooks, ml-connector polls both on a schedule you define, typically every 5 to 15 minutes. Tax calculations are synchronous from Avalara, returned immediately with rate and jurisdiction detail. Rates are then mapped to the correct GL account and cost center in Oracle Fusion Cloud ERP based on the invoice line item category and customer or supplier. If an Avalara call returns HTTP 429, ml-connector backs off and retries on an exponential schedule. Every record carries a full audit trail linking the original Oracle Fusion Cloud ERP invoice, the Avalara calculation request and response, and the GL posting so tax liability can be audited end-to-end.

A real-world example

A mid-market software company sells subscriptions and professional services to customers across the United States and Canada. Before integrating Oracle Fusion Cloud ERP with Avalara, the finance team manually entered tax rates by jurisdiction into each invoice, then used Avalara offline to validate the liability. Tax rate changes and multi-state customer moves frequently caused GL posting errors. With Oracle Fusion Cloud ERP and Avalara connected, each invoice automatically receives the correct tax calculation on posting, sorted by the customer's destination jurisdiction. Tax liability is posted to GL immediately, the finance team spends no time re-checking rates, and monthly tax reports pull directly from the GL with full confidence in accuracy.

What you can do

• •Send new invoices from Oracle Fusion Cloud ERP to Avalara for real-time tax calculation based on customer or supplier jurisdiction.
• •Automatically post calculated tax amounts into Oracle Fusion Cloud ERP's general ledger, mapped to the correct tax liability and deferred-tax GL accounts.
• •Prevent duplicate Avalara submissions by tracking document codes and handling idempotency safely across retries.
• •Validate customer and supplier addresses with Avalara before calculating tax, and fail fast if an address cannot be resolved.
• •Maintain a complete audit trail linking each Oracle Fusion Cloud ERP invoice to its Avalara calculation to its GL posting.

Questions

Which direction does data move between Oracle Fusion Cloud ERP and Avalara?

The main flow is from Oracle Fusion Cloud ERP into Avalara. When an invoice posts in Oracle Fusion Cloud ERP, ml-connector sends the transaction to Avalara for tax calculation, captures the result, and posts the calculated tax back to Oracle Fusion Cloud ERP's general ledger. Address and tax code reference data are synced in both directions to ensure tax calculations are accurate.

How does ml-connector prevent duplicate tax calculations if a posting fails and retries?

Avalara uses document code as an idempotency key. ml-connector tracks the Oracle Fusion Cloud ERP invoice number as the document code and reuses it on every retry. If the same document code is submitted twice, Avalara returns a DocumentCodeConflict error which ml-connector handles by reading the prior calculation rather than creating a duplicate.

What happens when Oracle Fusion Cloud ERP or Avalara are unreachable or return an error?

ml-connector backs off and retries failed calls on an exponential schedule with jitter to avoid thundering herd. Every transaction carries metadata about which calls succeeded or failed, so you can see in the audit trail where an issue occurred and replay the posting once the system recovers.