> 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/approval-flow-positioning.md).

# Approval flow positioning

Pactum's Coupa and Ariba connectors work with Pactum being positioned as an approver in the approval chain

When configuring Pactum's negotiation agent in the approval chain, it commonly goes immediately after a procurement triage process based on the appropriate customer conditions. This allows the triage team to correct any issues and ensure negotiations aren't triggered for requests that are non-compliant.

### Common Approval Chain Conditions

#### Spend Thresholds

We recommend a lower threshold of no less than $1,000 (or equivalent). If an upper limit is required, this is commonly the threshold at which Procurement Teams must ensure a sourcing event is completed (after which the Pactum Post-Sourcing Agent would be best suited).

#### **Contract/Catalogues**

Anything already negotiated on a contract and/or in a catalogue would in most cases not be suitable for a requisition negotiation, as by design they have been proactively negotiated as part of the introduction of the contract or catalogue.

#### **Categories**

There are likely some category areas you know are never applicable to Pactum. Common excluded categories include: Rent, Rates, Utilities, Taxes, Royalties, Legal Services and Patents, and Employee Benefits.

{% hint style="info" %}
Supplier-Based Filters: In some rarer cases, customers have wanted to apply specific supplier-based filters to ensure some suppliers are not triggered. This is done by having a flag on the supplier record that is then copied to the request line and used as a condition. This is not recommended but has been used in some unique cases.
{% endhint %}

\
\
\ <br>

<br>

\ <br>

<br>
