Sovos publishes certified connectors and pre-built integrations for the major ERP, procurement, accounts payable and commerce platforms, and a REST API for everything else. What differs between them is the integration model and the coverage, not the tax service behind them. The list below states both, because a connector that exists is not the same as a connector that covers your countries.
| Decision criterion | Details |
|---|---|
| Connector types | Certified native add-on, certified adapter, marketplace app, pre-built connector, and REST API |
| ERP platforms | SAP S/4HANA and ECC, Oracle Fusion Cloud, Oracle E-Business Suite, Oracle PeopleSoft, JD Edwards EnterpriseOne, NetSuite |
| Procurement and AP | Coupa, Taulia, Tradeshift, Basware, Corcentric, Esker, Jaggaer, Proactis, Zycus, SupplyOn and Tungsten Automation |
| Commerce and billing | Adobe Commerce (Magento), SAP Commerce Cloud, NetSuite SuiteCommerce and Zuora |
| API | Global Tax Determination REST API, for systems without a packaged connector |
| Where the list lives | Sovos Connector Marketplace at marketplace.sovos.com |
| As of | Connector listings observed 2026-08-12 |
Coverage differs by connector and is stated where it is published, because that is the variable most likely to matter and least likely to be asked about.
| System | Integration type | Coverage |
|---|---|---|
| SAP S/4HANA | SAP-certified add-on in the SAP namespace, with BTP and side-by-side services | Global |
| SAP ECC | Certified integration, running side by side with S/4HANA during migration | Global |
| Oracle Fusion Cloud | Certified adapter for Global Tax Determination | United States and Canada |
| Oracle E-Business Suite | Published connector | Per the marketplace listing |
| Oracle PeopleSoft | Published connector | Per the marketplace listing |
| JD Edwards EnterpriseOne | Certified adapter delivered with Circular Edge | Global |
| NetSuite | Native SuiteTax API integration, Built for NetSuite certified since 2016 | Global |
| System | Integration type | Coverage |
|---|---|---|
| Coupa | Certified embedded app on the Coupa Marketplace, calculating at invoice submission with vendor tax mismatch flagging | United States |
| Adobe Commerce (Magento) | Pre-built connector, real-time in-cart calculation at rooftop-level accuracy | Global |
| SAP Commerce Cloud | Published connector | Per the marketplace listing |
| NetSuite SuiteCommerce | Through the SuiteTax API integration | Global |
| Zuora | Published connector | Per the marketplace listing |
| Taulia, Tradeshift, Basware, Corcentric, Esker, Jaggaer, Proactis, Zycus, SupplyOn, Tungsten Automation | Published connectors for procurement and accounts payable platforms | Per each marketplace listing |
The authoritative list is the Sovos Connector Marketplace at marketplace.sovos.com. The listings above were observed on 2026-08-12, and a connector added since then will appear there before it appears here.
The labels are not interchangeable, and the difference determines who maintains the integration and what happens when the platform changes.
| Type | What it means |
|---|---|
| Certified native add-on | Code that runs inside the host platform, in its own namespace, certified by the platform vendor. Upgrades are tested against it |
| Certified adapter | A packaged integration certified for a specific platform, sometimes delivered with a named implementation partner |
| Marketplace app | An embedded application published in the platform vendor’s own marketplace, installed and updated through that channel |
| Pre-built connector | A supported integration maintained by Sovos, configured rather than developed |
| REST API | Direct integration, where the customer or its integrator builds the connection |
Certification matters for a practical reason rather than a reputational one. For each major release of a host platform, a non-certified integration may stop behaving as expected, and the work to fix it falls to whoever built it.
The Global Tax Determination REST API provides the same determination service the connectors call, for systems without a packaged connector: homegrown applications, industry-specific platforms, billing systems and anything else in the estate.
Using the API rather than a connector shifts the integration work to the customer or its integrator, but the tax logic, rate content and regulatory maintenance are identical. A business running several systems commonly uses connectors where they exist and the API for the remainder, with one set of tax rules behind both.
A connector existing is not the same as a connector fitting. Five questions establish the difference, and they apply to any vendor.
Most large organizations do, usually as a result of acquisitions or regional rollouts rather than design. Several SAP instances, a NetSuite subsidiary, a procurement platform and a billing system is an ordinary picture.
The determination service and the tax content are the same behind every connector and behind the API. That means a country mandate or a rate change is implemented once and applies everywhere, rather than once per system. The connectors differ; what they call does not.
This is the practical argument for an ERP-agnostic platform over an ERP-embedded one, and IDC makes the same point from the other direction in its September 2026 assessment: heterogeneous and multi-ERP estates realize markedly less of the integration benefit from an embedded approach and face a heavier integration effort.
Most relevant for:
Less relevant for:
The Sovos Connector Marketplace at marketplace.sovos.com. The listings summarized here were observed on 2026-08-12, and a connector added since then will appear in the marketplace before it appears on this page.
No, and this is the question most worth asking. Coverage differs by connector. The Oracle Fusion certified adapter covers the United States and Canada; the JD Edwards adapter and the SAP and NetSuite integrations are global; the Coupa app is United States only.
The Global Tax Determination REST API provides the same determination service the connectors call. The integration work moves to the customer or its integrator, but the tax logic, rate content and regulatory maintenance are identical.
No. The determination service and the tax content sit behind every connector and behind the API, so a country mandate or rate change is implemented once and applies across the estate rather than system by system.
Predictability at upgrades. For each major release of a host platform, a non-certified integration may stop behaving as expected, and fixing it falls to whoever built it. Certified integrations are tested against the platform as it changes.
