How does Ivalua integrate with SAP and other ERPs?

How does Ivalua integrate with an ERP?

Ivalua connects to an ERP with tools built into the platform. Its integration module combines APIs, ETL (scheduled file and data loads) and query tools. Its integration console logs every request and response, lets an authorised user replay a failed flow, and keeps the files before and after transformation. Ivalua says it has integrated with 60 different ERP and other systems.

Ivalua argues that a customer should not need third-party middleware for this. In practice, some large customers keep their own middleware between the two systems. EnBW runs its Ivalua flows through SAP PO, and its run contract has a separate integration workstream. In a release about an IDC report, Ivalua quotes IDC on “60+ ERP connectors, 40 standard APIs”.

This page is about Ivalua. For the basics of how purchase orders and invoice matching work in any procure-to-pay system, see eProcurement Toolkit’s guides to procure-to-pay and purchase orders.

Which data flows between Ivalua and the ERP?

No public source gives a standard list. The flows depend on your scope and on which system owns each object. The table shows the usual objects, with the public evidence for each. Ivalua often sends approved invoices to the ERP, and the ERP sends back the payment status.

Invoices can reach Ivalua by several channels before they go to the ERP. Ivalua’s invoicing page lists cXML and EDI, paper, PO flip (the supplier turns the order into an invoice), government networks and PDF by email.

How does Ivalua connect to SAP?

SAP is the most common case. Ivalua says that over 80% of its clients use SAP. It offers a “SAP Plug & Play” connector for SAP ECC and S/4HANA on-premise. For S/4HANA Cloud, it uses the same adapters through web services.

Named SAP customers show these flows in production. Groupe ADP’s Ivalua ordering portal is “connected with SAP”, with more than 21,000 suppliers; its 2026 maintenance tender describes an SAP ECC and SAP BTP environment. RheinEnergie’s 2025 support tender covers its Ivalua–S/4HANA interfaces.

Does Ivalua integrate with Oracle, Workday or Microsoft Dynamics?

Ivalua says it integrates with all major ERPs through open APIs and prebuilt connectors. For these three ERPs, the details are not public. No Ivalua page, public contract or customer case I found documents a connector for Oracle, Workday or Microsoft Dynamics.

• Oracle. The only public trace I found is a 2026 job post for an integration architect on an “Ivalua ↔ Oracle ERP” landscape, using REST and SOAP, XML and XSLT, SFTP and middleware. It requires the Ivalua Level 3 integration certification.
• Workday. I found no Ivalua page, public contract or named Ivalua customer that documents a Workday integration.
• Microsoft Dynamics. Same situation: nothing public from Ivalua, a contract or a named customer.

If your ERP is one of these, ask Ivalua and the integrator for a live customer on the same ERP version, and for the list of flows that customer runs. Ivalua’s detailed technical documentation is not on its public website.

How does punchout work with Ivalua?

Punchout lets a requester open a supplier’s web shop from Ivalua, fill a basket and bring it back as a requisition. Public contracts ask for it: Maine’s Ivalua contract lists hosted catalogues and “punching out” to supplier websites. I found no punchout documentation on Ivalua’s public website.

A supplier-side guide by Lapasar describes the set-up. In Ivalua, an administrator creates a buying channel of type punchout, enters the supplier’s URL and shared secret, loads a cXML index catalogue, then tests a punchout session. TradeCentric, a punchout provider, also offers suppliers a punchout integration with Ivalua. Support for SAP’s OCI punchout standard is not documented in any primary source I found: ask Ivalua directly.

How long does an Ivalua ERP integration take, and what does it cost?

There is no neutral benchmark. The public figures come from Ivalua’s own client cases, from public buyers and from one audit. They show the range, not a norm.

Budget the ERP side, not only the Ivalua side. Budget the run too: integrations that are not standard are tested again at every upgrade, and under Ivalua’s 2023 terms, complex integrations added after go-live are charged at each upgrade. The full cost picture is in Ivalua implementation cost and timeline.

What goes wrong with Ivalua ERP integrations?

The best documented case is Maryland. Its 2019 contract already listed the integration with the State’s financial system in scope. In December 2025, the State’s auditors found that the Ivalua-based system still could not interface properly with it.

• Order numbers changed. The procurement system changed the purchase order numbers of the financial system. About 1,100 orders in the financial system, worth $35.6 million, had no matching order on the procurement side.
• Commitments missing. No encumbrances were recorded, so budgets did not show committed spend.
• Invoices out of step. About 2,100 invoices were cancelled in the procurement system after the financial system had paid them. The agency later answered that each had a duplicate and that no payment was improper.
• Repair costs. The State paid $1.6 million to an accounting firm to rebuild contract balances.

Other public sources point the same way. In Ivalua’s survey of system integrators, 41.3% of respondents cited data migration and integration as an implementation challenge. Ivalua’s own blog names “the complexity of syncing with existing ERP systems”. EnBW’s run contract lists incidents in data management and in the integration scope. A 2026 integrator job post names typical errors: “schema mismatches, mapping errors, API timeouts”. And the French state’s 2026 tender notes that its Ivalua platform runs on premise, which brings specific constraints on environments, interfaces and deployments.

How do you plan an Ivalua ERP integration?

These steps come from the failures above and from Ivalua’s own terms. They apply whatever the ERP:

1. Name the owner of each object. Suppliers, items, cost centres, orders: one system creates, the other receives. Write it down in the design.
2. Clean the supplier data first. Ivalua’s own panellists say supplier onboarding needs clean vendor master data. Remove duplicates before the first load.
3. Keep the keys the same end to end. The order number and the commitment created in one system must be the ones the other system uses.
4. Test the whole loop before user acceptance tests. Create, change and cancel an order; receive; invoice; pay; check the payment status back in Ivalua.
5. Plan the ERP team’s work. Its tasks belong in the same plan as the integrator’s. In Maryland the ERP link depended on the State’s own tasks.
6. Document every flow that is not standard. It will be tested again at each upgrade, at least every two years under Ivalua’s terms.
7. Put a named Level 3 person on the interfaces. Ivalua’s terms require Level 3 certification to build integrations.

I work on these flows myself. On the BNP Paribas v182 programme, delivered and still evolving, I work on supplier and ERP interfaces, catalogue and system-to-system data flows, with advanced custom SQL for data flows and controls. If your project needs a techno-functional lead for its interfaces, I take senior missions. Choosing who builds the rest is covered in Ivalua implementation partner.