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 the Negotiation Suite.
What runs where
Requisitions can reach Pactum four different ways. Post-sourcing runs in Coupa or in the Suite. Tactical sourcing runs in the Suite.
- Coupa
- Requisitions
- Post-sourcing, embedded
- SAP Ariba
- Requisitions
- Pactum API
- Requisitions
- Negotiation Suite
- Requisitions
- Post-sourcing
- Tactical sourcing
Coupa
Requisitions and post-sourcing, without leaving Coupa
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 runs in an embedded frame on the sourcing event, so a buyer launches an autonomous negotiation and reads the outcome inside the Coupa interface.
- Requisition data fetched automatically, outcomes written back
- Post-sourcing negotiations launched and reviewed inside Coupa
- Approval routing stays where your team already works
SAP Ariba
Requisitions straight from Ariba Buying
Pactum receives requisition data from Ariba Buying and starts the negotiation over the API, then returns the outcome to the approval flow. Since August 2026 the requisition import is configured in the product, under Suite settings, rather than by an engineer on our side.
- Requisition data received from Ariba Buying, outcomes returned
- Import configured in Suite settings, not by a Pactum engineer
- Field and supplier mapping handled per tenant
API and Suite
Your own integration, or none at all
If you run something other than Coupa or Ariba, requisitions can reach Pactum through our API and your team builds the connection to suit your stack. And every capability is available in the Negotiation Suite without any integration at all, which is how most teams start and how tactical sourcing runs today.
- Requisitions through the Pactum API, built on your side
- Every capability available in the Suite with no integration
- Most teams prove value in the Suite first, then connect
Live in two to four weeks
Integration setup is self-service, and most customers are running inside two to four weeks. Teams typically begin with one focused workflow, prove the value, and widen coverage from there rather than connecting everything at once.
- SOC 2 Type II certified, with data encrypted in transit and at rest
- Existing workflows, approval paths and user experience stay in place
- Start with one workflow and expand once it is proven