Digital workers inside the stack you already run.

Pactum works inside Coupa or SAP Ariba, reads only the scopes you grant and logs every decision.

Get a demoHow it connects
Illustration: a policy check on one requisition in the P2P. The digital worker corrected a quantity itself, sent the payment terms back to the requester because the quote and the contract disagreed, passed the supplier record and the coding, and the requester corrected and resubmitted nine minutes later
  • 60+global enterprises
  • 1,000,000+requisition checks since March 2026
  • 99%agreement with a customer's own reviewers before it acted alone
  • SOC 2 Type 2compliant, and ISO/IEC 27001:2022 certified

One request through three layers

Requests come in through Teams or the P2P your people already use, digital workers do the work in between, and Coupa or SAP Ariba stays the record.

  • A front door your people already use, with the Intake Agent raising the requisition
  • Digital workers review, source and negotiate with the scopes you grant, listed in your own instance
  • The decision and the audit report write back to your system of record, with nothing built on your side
How it connects
Illustration: one request through three layers. Priya asks for 40 laptops through the front door she already uses, Teams, Coupa or SAP Ariba, and the Intake Agent raises the requisition; digital workers review it against policy, source and negotiate with read scopes only; the requisition, the decision and the audit report are written back to the system of record. A table shows what is read, what is written, and that nothing is built on the customer side

Observer mode before write access

Pactum runs on your live instance with read scopes only, and writes nothing until you have seen it agree with your own reviewers.

  • Reads live requisitions and records what it would have decided
  • You compare its decisions with your reviewers' before anything is switched on
  • Write access is granted per capability, and you can take it back at any time
Alignment Agent
99%agreement with a customer's own reviewers before it acted alone
Illustration: one rule's proof panel before it is switched on: an observer run on live requests with no effect, a backtest against requisitions the customer's own reviewers judged, the agreement rate with those reviewers, and the option to move the rule from advising to acting

The evidence your review board asks for

SOC 2 Type 2, ISO/IEC 27001:2022 and the penetration test report are on the Trust Center before the questionnaire arrives.

  • Every decision logged with the rule that made it
  • No training on your data, by Pactum or by any AI provider
  • Single sign-on through your own identity provider
Security at Pactum
1,000,000+requisition checks since March 2026
Illustration: the policy library with four policies in sync, and the policy assistant asking what policy to create in plain language, with three starting points and one drafted

Digital workers for Coupa and SAP Ariba

Each one runs inside your P2P with the scopes you grant. Procurement chooses which ones run and where.

  • Intake Agent

    Turns a request in plain words, in Teams or your P2P, into a clean, correctly coded requisition and hands it on.

  • Alignment Agent

    Turns your policies and strategy into one rulebook, checks every request against it and gives every digital worker its rules.

  • Single-Source Negotiation Agent

    Negotiates every single-source requisition before the PO exists, for better price, payment terms and working capital.

  • Tactical Sourcing Agent

    Runs the RFQ, drives the competition and negotiates the final terms on buys your team never had time to run.

  • Advanced Sourcing Agent

    Runs the multi-round events your buyers used to carry alone, built on your category strategy.

  • Post-Sourcing Negotiation Agent

    Takes the bids from your closed RFx and negotiates a final offer with every shortlisted supplier before you award.

“Days of manual reviews became minutes. Faster decisions, better compliance, and real efficiency gains.”
Rob Baillie · Head of Procurement · SUEZ UK

What it looks like in production

Customers on Coupa and SAP Ariba, with the system of record untouched.

Frequently asked questions about Pactum for CIOs and procurement technology owners

Does Pactum integrate with Coupa and SAP Ariba, and what access does it need?

Pactum integrates with Coupa and SAP Ariba through two ready-made connectors that your own admin sets up. On Coupa, Pactum runs as a standard approver in your approval chain, with OAuth client credentials and scoped permissions per capability that you can read in your own instance. On SAP Ariba it is a named approver step that reads the requisitions assigned to it over SAP's own APIs. See integrations.

Does Pactum write to our P2P, and what exactly does it write?

Pactum writes only to the requisition it was asked to review. On Coupa that is the approval, escalation or rejection, a comment that tags the requester, corrections to line fields such as quantity and price, and an audit report. It writes only for the capabilities you switch on, and in observer mode it writes nothing at all. Coupa or SAP Ariba stays the system of record.

How does Pactum use AI models, and is our data used to train them?

Pactum uses language models for reading, extraction and classification. Pactum does not train any model on customer data, and its contracts prohibit AI providers from training on it. Rules your procurement team configures decide each outcome, and every model call is logged. The Large Language Models at Pactum document is on the Pactum Trust Center.

How does Pactum stop an AI from hallucinating a purchasing decision?

Pactum keeps decisions rule-based, so a generated sentence cannot become a decision. Where a model evaluates a policy, its verdict is logged and reviewable, and extracted values are checked against the source document. Every rule also runs in observer mode on your live requisitions before it is allowed to act, so you see where it agrees with your own reviewers first.

Where is our data hosted and who can access it?

Pactum hosts your data on Google Cloud in the US or the EU, encrypted at rest and in transit. Access on Pactum's side follows least privilege. Pactum processes your data as your data processor, on your instructions, and keeps it for the duration of the agreement. The SOC 2 Type 2 report, the ISO/IEC 27001:2022 certificate and the penetration test report are on the Pactum Trust Center.

Do we need middleware or custom development to connect Pactum?

No middleware and no custom development are needed for Coupa or SAP Ariba. Both connectors are set up by your own admin inside Pactum Suite, and Pactum is hosted and run by Pactum, so nothing is built or installed on your side. If you run a different procurement system, requisitions reach Pactum through its public API, and your team builds that connection to suit your stack.

How long does it take to implement Pactum?

Pactum goes from approval to value in 2 weeks. Your own admin sets up the Coupa or SAP Ariba connector inside Pactum Suite, with no middleware and no custom development. AI agents then run in observer mode on your live requisitions, so you see their verdicts next to your own reviewers' decisions before they act on anything.

Should we build our own procurement AI agent or buy one?

Buy a procurement AI agent when you need it to act on every request, not only answer questions. A copilot or a general language model answers when someone asks. Pactum's AI agents check every request whether anyone asks or not, apply your rules the same way each time, write the result back to Coupa or SAP Ariba and log every decision. Your team keeps control of the rules.

Can we deploy Pactum while our ERP is fragmented or mid-migration?

Yes, you can deploy Pactum while your ERP is fragmented or mid-migration. Most teams start in Pactum itself, where single-source negotiation, post-sourcing and tactical sourcing run with no integration at all. You connect Coupa or SAP Ariba once your setup is ready. Any other procurement system can send requisitions through the Pactum API, with the connection built on your side to suit your stack.

Can we run Pactum in observer mode before it acts on anything?

Yes, Pactum runs in observer mode on your live instance for as long as you like. It reads every requisition, records the verdict it would have given and writes nothing back, so you can compare it with the decisions your own reviewers made. You switch it on when you are satisfied with the agreement, and off again at any time.

Which spend does Pactum work on?

Pactum works on indirect spend: the goods and services a company buys to run itself, such as IT, facilities, MRO and professional services. AI agents run each request end to end, from intake and the policy check to sourcing, negotiation and the purchase order, inside Coupa or SAP Ariba where each agent is live. That includes the requests outside your catalog and contracts, where no price was agreed in advance.

See the data flow on one page.

Bring your architect and one requisition from your own instance. The demo shows what Pactum reads, writes and keeps.

Get a demo