> For the complete documentation index, see [llms.txt](https://docs.eu-pactum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eu-pactum.com/procurement-product/integration/coupa/configuring-coupa-integration-for-requisitions.md).

# Coupa Requisitions

## Overview

The Pactum Integration with Coupa for Requisitions negotiations is designed to be entirely autonomous and use the flexibility and standard capabilities of Coupa (remote approver, approval chains and Open APIs) to maximise the value of all spend through Pactum negotiation with minimal to zero impact on users or Procurement Teams.

The high level flow is as follows

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2Fgit-blob-3345ca56acbb99cec489dd08daca7a181042070e%2Fcoupa-requisitions-high-level-flow.png?alt=media" alt=""><figcaption></figcaption></figure>

The above flow shows this for a single supplier negotiation. The same integration and flow can be used for multi supplier negotiations.

In the request to order cycle, Pactum acts as an approver in the customer’s approval chain, triggered by appropriate approval conditions. Upon being triggered, Pactum autonomously reaches into Coupa grabbing the details of the request and the proposed supplier and then reaches out to the supplier directly to negotiate the request. Upon conclusion of the negotiation, Pactum reaches back into the request to update the Price and Payment Terms as agreed following the negotiation, then “approves” the request sending it on to complete the approval process in Coupa and Coupa issuing the Purchase Order.

In a scenario where Pactum is not successful, either the supplier does not reach a deal or does not react within the time frame allowed, Pactum will automatically reach back in to Coupa in the same way, posting a comment to say we were unsuccessful and “approving” the request to send it to the next approver.

### Importing requisitions

Pactum integrates to Coupa via the approval flow, using a RemoteApprover. This approver is added to the flow automatically based on configured criteria. Instructions on how to set up the Remote approver and flow can be found in the Configuration section.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2Fgit-blob-f4d752103316f6ac2db722f99254f5abbc54a645%2Fcoupa-requisitions-import-webhook.png?alt=media" alt=""><figcaption></figcaption></figure>

When the approval flow reaches the remote approver, it triggers a call out to Pactum’s API. Based on that signal, the requisition is imported and a negotiation is automatically started.

If the call out does not happen due to any technical issue, Pactum has a fallback mechanism in place. The system polls Coupa’s approvables regularly and imports requisitions that have been assigned to the RemoteApprover.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2Fgit-blob-bd0ade85cab1080523f331bd446102ce993949e8%2Fcoupa-requisitions-import-polling.png?alt=media" alt=""><figcaption></figcaption></figure>

### Updating requisitions with results

When the negotiation has concluded, Pactum will automatically update the following information under the requisition in Coupa:

* Line item prices
* Payment terms

The system will also add a comment, indicating that the requisition has been updated. If the supplier also added an updated quote file, an additional comment is added with the quote attached.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2Fgit-blob-75aacb488728d897437e0dc54ac43948720c2ca8%2Fcoupa-requisitions-update-results.png?alt=media" alt=""><figcaption></figcaption></figure>

### Requisition withdrawals

In case we have imported a requisition and it is not anymore assigned to the Pactum approver, the system will automatically withdraw the negotiation and post a comment in Coupa.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2Fgit-blob-1bfcb028689440856d89af66330edee4d3d90e4e%2Fcoupa-requisitions-withdrawal.png?alt=media" alt=""><figcaption></figcaption></figure>

### Approval Chains (inc. custom fields)

Once the remote approver is set up, the next step is to configure the approval chains to introduce The Pactum Remote Approver.

This can be done using Coupa’s standard approval chains and the logic you wish to use to define where Pactum comes in.

Example could include:

* Total is Less than $
* Contract Name is Blank
* Commodity is x, y or z

Custom Fields

An alternative option here would be to put a Pactum custom field on the request that would be visible to relevant procurement team members who could trigger Pactum as part of their review. Once configured, the Pactum approval chain would then just reference this custom field.

We would recommend any manual steps, such as triggering a custom field would only be an interim measure during the initial phase and that full process automation should be the goal.

Consideration: Escalations

When configuring Pactum, it is important to account for the configuration of approval escalations for Requisitions in Coupa, and ensure that Pactum’s “deadline” for negotiations is less than that.

For Example, if on the Approvals Configuration Page the “Automatically escalates to next approver in chain” for Requisitions is set to 96 hours (4 days) makes sure the Pactum Deadline for requests is set to 3 days, to avoid any conflict.
