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").