Section A · Systems of record

Procurement — Coupa, Ariba, Jaggaer, Ivalua

Source-to-pay platforms where procurement teams live day-to-day. For contract intelligence, this is where contract references, supplier risk, and renewal alerts ideally land.

Coupa

What it is

Modern source-to-pay platform. Strong in mid-market and growing enterprises; competitive with Ariba at the high end. Cloud-native; clean APIs.

Who owns it

Procurement Operations team. More accessible than the SAP team is.

How to integrate

REST APIs at /api/.... Well-documented; the customer's Coupa admin can spin up an API user in days, not weeks.

import httpx

resp = httpx.get(
    "https://customer.coupahost.com/api/suppliers",
    params={"limit": 100, "status": "active"},
    headers={"X-COUPA-API-KEY": settings.coupa_api_key, "Accept": "application/json"},
)
suppliers = resp.json()

Auth patterns

API key authentication (X-COUPA-API-KEY header) is the default. OAuth2 available for newer integrations.

Common integration uses

Pull active suppliers, with their categories and risk profiles.
Pull contract metadata (Coupa has a Contracts module).
Pull POs, invoices, three-way-match data for spend reconciliation.
Push renewal alerts, supplier-risk flags, or off-contract-spend warnings back into Coupa's workflow.

Gotchas

Rate limits. Coupa is rate-limited; high-volume backfills need pacing.
Custom fields. Customers extend Coupa with custom fields on suppliers, contracts, POs. Map per customer.
Approval workflows. Writeback to Coupa often hits approval workflows the customer has configured. Test before assuming writes land.

SAP Ariba

What it is

SAP's source-to-pay suite. Dominant at SAP-shop enterprises; tightly integrated with SAP ECC and S/4HANA. Multiple modules: Sourcing, Contracts, Buying, Invoicing, Supplier Risk.

Who owns it

Often the same SAP team that owns the ERP, or a separate Procurement Operations team for the Ariba application.

How to integrate

Ariba APIs: REST endpoints at https://api.ariba.com/.... Documentation is decent but enterprise-y.
cXML: legacy document-based protocol. Used for transactional flows (POs, invoices).
SAP CPI (Cloud Platform Integration): often the middleware between Ariba and other systems.

Auth patterns

OAuth2; SAP's Identity Authentication Service often in the middle.

Gotchas

Module sprawl. Ariba has many modules. "We use Ariba" doesn't tell you which ones. Ask specifically.
cXML legacy. Some integrations still go through cXML rather than REST.
Realm structure. Multi-realm deployments (separate realms per business unit) are common. Per-realm integration setup.
Coordination with SAP ECC/S4 team. Ariba integrations often need ERP-side support too. Two-team coordination.

Jaggaer

What it is

Specialty source-to-pay platform. Strong in higher education, life sciences, complex manufacturing. Often chosen for industry-specific compliance features.

How to integrate

REST APIs; documentation is less polished than Coupa's. Customer-specific configurations vary widely.

Gotchas

Smaller customer community means fewer publicly documented patterns; rely on the customer's Jaggaer admin.
Industry-specific data fields (research grant codes for higher ed, lot-tracking for life sciences) require domain context.

Ivalua

What it is

European source-to-pay platform. Common at European enterprises and in regulated industries (pharma, utilities). Strong in supplier management and risk.

How to integrate

REST APIs. Like Jaggaer, less public documentation than Coupa; customer's Ivalua admin is the source of truth.

Gotchas

Heavy supplier-risk and compliance modules — your integration may need to consume risk scores or contribute to them.
European customer base means data-residency considerations (GDPR) more prominently.

Why this matters for contract intelligence

The procurement suite is often where the customer's procurement team lives day-to-day. Pushing platform output (renewal alerts, off-contract spend warnings, supplier-risk flags) into the procurement suite means the insight lands in their workflow — not in a separate dashboard they have to remember to check.

Integration patterns for contract intelligence:

Pull supplier master + contract refs from the procurement suite. Use as authoritative for entity resolution (chapter 02 of the data model reference).
Pull spend data when ERP integration is incomplete or gated.
Push renewal alerts as tasks or notifications in the procurement workflow.
Push supplier-risk signals into supplier records (e.g., "this supplier has 3 expired DPAs across active agreements").

✓ Check yourself

Answer from memory before opening each one.

A customer says "we use Ariba." What do you ask before you plan any work, and what does each answer change?

Show answer
Ask which modules (Sourcing, Contracts, Buying, Invoicing, Supplier Risk), how many realms, and whether any flows still run on cXML instead of REST. Each answer changes the endpoints, the per-realm setup and which team has to help, since Ariba work often needs the ERP team as well. See SAP Ariba.
You push a renewal alert into Coupa through the API. The call succeeds, but the buyer never sees a task. Where do you look first?

Show answer
Look at the approval workflows the customer configured in Coupa, because write-backs often land inside them instead of straight in the record. Test a write end to end before you promise it, and check the custom fields on that object too. See Coupa.
The SAP team's queue is six weeks long, and you need supplier master and spend data for entity resolution now. What can you start with, and what does it not cover?

Show answer
Pull from the procurement suite. A Coupa admin can often issue an API user in days, and the suite holds supplier profiles, contract references and spend. It will not hold everything in the ERP, such as GL postings, so treat it as a first source and not a replacement. See why this matters and Coupa.
Your sponsor wants renewal alerts shown on a dashboard in your own product. What do you argue instead, and what would make you give way?

Show answer
Argue for pushing the alert into the procurement suite as a task or notification, because the procurement team lives there and will not check a separate dashboard. Give way if the write path is blocked, for example by approval workflows or missing write scope, and ship read-only first. See why this matters.
The customer is on Jaggaer or Ivalua, and there is little public documentation. How do you reduce the risk?

Show answer
Treat the customer's admin as the source of truth and get API access to a tenant early. Ask for the industry-specific fields, such as research grant codes at a university or lot tracking in life sciences. With Ivalua, raise GDPR and data residency from the start. See Jaggaer and Ivalua.

Takeaway

Procurement suites are where the procurement team works every day, so insight pushed into their workflow gets used and a separate dashboard does not.
Coupa is the easiest to reach: REST, an API key, and an admin who can issue an API user in days.
"We use Ariba" says little. Ask for the modules and realms, and expect cXML on older flows and a second team behind the ERP.
Write-backs into a procurement suite often meet the customer's approval workflows, so test that a write lands before you promise it.
For Jaggaer and Ivalua, the customer's admin is the documentation, and industry fields and data residency need domain context.
The suite can stand in for gated ERP data early, but it does not hold the whole ERP.

Procurement tells you who the supplier is, and the CLM holds the signed contract behind that supplier. → CLM platforms

Coupa

What it is

Who owns it

How to integrate

Auth patterns

Common integration uses

Gotchas

SAP Ariba

What it is

Who owns it

How to integrate

Auth patterns

Gotchas

Jaggaer

What it is

How to integrate

Gotchas

Ivalua

What it is

How to integrate

Gotchas

Why this matters for contract intelligence

✓ Check yourself

Takeaway

Further reading