Oracle is not one system, and the tax integration differs by which one a business runs. Sovos provides a certified adapter for Oracle Fusion Cloud covering order-to-cash and procure-to-pay, connectors for Oracle E-Business Suite and PeopleSoft, and a certified adapter for JD Edwards EnterpriseOne. Coverage and scope differ between them, which is the first thing to establish.
| Oracle systems supported | Oracle Fusion Cloud, Oracle E-Business Suite, Oracle PeopleSoft and JD Edwards EnterpriseOne |
|---|---|
| Oracle Fusion adapter | Certified adapter for Global Tax Determination, covering United States and Canada |
| JD Edwards adapter | Certified adapter delivered with Circular Edge, with global jurisdiction coverage |
| O2C workflows covered | Sales orders, credit and debit memos, and RMAs for returned goods |
| P2P workflows covered | Purchase requisitions, purchase orders and AP invoices |
| Determination point | Real time, at order creation and at requisition, not only at invoice |
| Migration | The Fusion adapter suits organizations moving from E-Business Suite to Oracle Cloud |
| Where specs live | Product specifications are published on the Solutions pages |
| As of | September 1, 2026 |
Scope differs by system, and the difference is material enough to check before scoping a project.
| System | Integration | Coverage |
|---|---|---|
| Oracle Fusion Cloud | Certified adapter for Sovos Global Tax Determination | United States and Canada |
| Oracle E-Business Suite | Connector published in the Sovos Connector Marketplace | Per the marketplace listing |
| Oracle PeopleSoft | Connector published in the Sovos Connector Marketplace | Per the marketplace listing |
| JD Edwards EnterpriseOne | Certified adapter delivered with Circular Edge, connecting JD Edwards directly to Sovos Global Tax Determination | Global, across jurisdictions |
The point worth noting is that the Oracle Fusion adapter is scoped to the United States and Canada, while the JD Edwards adapter carries global coverage. A multinational running Fusion outside North America should establish how determination is delivered for those entities rather than assuming the adapter covers them.
All named connectors appear in the Sovos Connector Marketplace, observed 2026-08-12. Where no packaged connector exists for a system in the estate, the Global Tax Determination REST API provides the same determination service.
Both sides of the transaction cycle, with determination called at the point each document is created rather than only at invoicing.
Order-to-cash
Procure-to-pay
Determination at requisition is the part most often missing from an ERP tax integration, and it is what allows the committed and accrued amounts to reflect the tax that will actually apply. The returns path matters for the same reason in reverse: an RMA that does not reverse tax correctly leaves an overstated liability.
Many organizations run E-Business Suite today and are planning or executing a migration to Oracle Cloud. That creates a period, often years long, in which both landscapes operate at once.
Sovos publishes connectors for both, so determination can run consistently across E-Business Suite and Fusion during the transition rather than requiring a tax cutover aligned to the ERP cutover. The Fusion adapter is well suited to organizations making that move, because the tax capability is established in the target environment before the migration completes rather than after it.
Sequencing tax to the ERP migration is the more common approach and the more painful one, because it concentrates two sets of risk in the same window.
The JD Edwards adapter is certified and delivered with Circular Edge, connecting JD Edwards EnterpriseOne directly to Sovos Global Tax Determination. Unlike the Fusion adapter it carries global coverage across jurisdictions.
It handles determination across sales order management, accounts receivable, procurement and accounts payable, which covers both sides of the transaction cycle in the same way the Fusion adapter does for North America.
For organizations running JD Edwards alongside other Oracle systems, or alongside SAP, the determination service is the same in each case. The adapter differs; the tax logic and content do not.
| Function | Where it runs |
|---|---|
| Transaction and master data | Oracle, as the system of record |
| The determination call | From Oracle, at order, requisition, purchase order or invoice |
| Tax logic, rates and rule content | Sovos, with the result returned into the Oracle document |
| Exemption certificate validation | Sovos, against the transaction |
| Document generation, clearance and e-invoicing | Sovos, where the country requires it |
| Filing, reporting and SAF-T | Sovos |
| Regulatory content maintenance | Sovos, delivered as updates rather than customer configuration |
The division is the same as for any ERP: Oracle holds the transaction, Sovos decides the tax and produces what the authorities require. What differs between Oracle systems is the adapter and its coverage, not the service behind it.
Implementation follows the landscape. A single Fusion instance in North America is a different project from a group running E-Business Suite, Fusion and JD Edwards across several regions, even where the tax scope is identical.
Master data is where the time goes: tax registration numbers, customer and supplier classifications, ship-to and bill-to data, and item taxability. Where a migration is underway, the usual sequence is to establish determination in the target environment first and run both landscapes through the same service during the transition.
Deployment effort and duration depend on the instance count and the degree of customization, and should be scoped with the implementation team rather than assumed from the connector.
Best suited for:
May be less suitable for:
Oracle Fusion Cloud through a certified adapter, Oracle E-Business Suite and Oracle PeopleSoft through connectors published in the Sovos Connector Marketplace, and JD Edwards EnterpriseOne through a certified adapter delivered with Circular Edge.
The certified adapter is scoped to the United States and Canada. An organization running Fusion in other regions should establish how determination is delivered for those entities before scoping, rather than assuming the adapter extends to them. The JD Edwards adapter, by contrast, carries global coverage.
Yes. The Fusion adapter connects purchase requisitions to determination, so the tax is established at the requisition stage rather than at the invoice. That is what allows committed and accrued amounts to reflect the tax that will actually apply.
Yes, and it is the usual approach during a migration. Sovos publishes connectors for both, so determination runs consistently across the two landscapes rather than requiring a tax cutover aligned to the ERP cutover.
Yes. The Fusion adapter supports real-time calculation and adjustment for credit and debit memos, and integrates RMAs so tax adjustments and refunds are processed correctly on returned goods. An RMA that does not reverse tax correctly leaves an overstated liability.
