IntegrationsIndirect procurement

Runs Inside the Systems You Already Use

No new system for your team to learn and no workflow to redesign. Pactum connects to Coupa and SAP Ariba, takes data through your own API, or runs on its own in Pactum with no integration at all.

Get a demoAll digital workers

What runs where

Single-source negotiation runs on every route. Coupa carries the most, from intake to post-sourcing. Post-sourcing and tactical sourcing also run in Pactum with no integration.

Coupa
Intake Agent
Alignment Agent
Single-Source Negotiation Agent
Tactical Sourcing Agent, automated from the requisition
Post-Sourcing Negotiation Agent, embedded
SAP Ariba
Intake Agent
Alignment Agent
Single-Source Negotiation Agent
Pactum API
Single-Source Negotiation Agent
In Pactum, no integration
Single-Source Negotiation Agent
Post-Sourcing Negotiation Agent
Tactical Sourcing Agent
Coupa

From request to award, inside Coupa

Digital workers connect to your Coupa instance over its API. A request comes in, the Intake Agent turns it into a clean requisition and the Alignment Agent checks it against your policy. A digital worker then negotiates it, or takes it to competition. When an RFx closes, the buyer starts a post-sourcing negotiation from the sourcing event and reads the result without leaving Coupa.
  • Turns requests into clean, correctly coded requisitions, checked against your policy
  • Takes tactical buys to competition straight from the requisition
  • Negotiates closed RFx bids in a frame embedded on the sourcing event
  • Writes the outcome back, so approval routing stays where it is
SAP Ariba

Requisitions checked and negotiated, straight from Ariba Buying

Digital workers receive requisition data from Ariba Buying over the API. The Intake Agent turns a request in plain words into a requisition raised in Ariba, the Alignment Agent checks each request against your policy, a digital worker negotiates the terms, and the outcome goes back to the approval flow. Since August 2026 your team sets up the requisition import in Suite settings. No Pactum engineer needed.
  • Checks every requisition against your policy before approval
  • Negotiates single-source requisitions, outcome returned to Ariba
  • Import set up in Suite settings by your own team
  • Field and supplier mapping handled per tenant
API and Pactum

Your own integration, or none at all

Run something other than Coupa or Ariba? Send requisitions through the Pactum API and build the connection to suit your stack. Or skip the integration. Single-source negotiation, post-sourcing and tactical sourcing all run in Pactum on their own, and that is how most teams start.
  • Requisitions through the Pactum API, built on your side
  • Negotiation and tactical sourcing in Pactum, no integration needed
  • Prove the value in Pactum first, then connect your P2P

Live in two to four weeks.

Setup is self-service, and most teams are live in two to four weeks. Start with one workflow, prove it, then widen coverage.

  • SOC 2 Type 2 compliant, data encrypted in transit and at rest
  • Your workflows, approval paths and user experience stay as they are
  • Start with one workflow and expand once it is proven
Get a demo

Frequently asked questions about Pactum integrations

Does Pactum integrate with Coupa?

Yes. Pactum connects to your Coupa instance over its API. Requisitions and sourcing events trigger negotiations automatically, and results post back to the record they came from. Post-sourcing negotiations run embedded on the Coupa sourcing event, so buyers launch them and read the outcome without leaving Coupa.

Does Pactum integrate with SAP Ariba?

Yes. Pactum receives requisition data from Ariba Buying, starts the negotiation over the API and returns the outcome to the approval flow. The Intake Agent can also raise the requisition in Ariba from a request in plain words. Since August 2026 the requisition import is configured in the product, under Suite settings, not by a Pactum engineer. Field and supplier mapping is handled per tenant.

Can we use Pactum without Coupa or SAP Ariba?

Yes. Requisitions can reach Pactum through the Pactum API, with the connection built on your side to suit your stack. Single-source negotiation, post-sourcing and tactical sourcing also run in Pactum with no integration at all, which is how most teams start.

How long does integration take?

Integration setup is self-service, and most customers are running within two to four weeks. Teams usually begin with one focused workflow, prove the value and widen coverage from there.

Do our workflows or approval paths change?

No. Existing workflows, approval paths and the user experience stay in place. Approval routing stays where your team already works, and Pactum writes its outcomes back to the same records.

How is our data protected?

Pactum is SOC 2 Type 2 compliant and ISO/IEC 27001:2022 certified, and data is encrypted in transit and at rest. See the Pactum Trust Center.