> 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/how-procurement-product-works.md).

# How Procurement product works

### Event

The central entity in procurement product is an Event. It is a container that holds information about the demand (line items and other terms) and the participating suppliers. Within the same event, each of the suppliers can either have an initial quote provided or not.

* For the suppliers, for whom an initial quote has not been provided, Pactum will reach out with a request for quote, followed by a negotiation.
* For the suppliers for whom an initial quote has been provided, Pactum will reach out to suppliers to negotiate the provided terms.

In most cases, one event represents a requisition, fixed-price contract or a sourcing event for either of these.

### Negotiable terms

* Total price - Pactum offers will apply a uniform discount across all line items, suppliers can provide their own breakdown on a line item level
* Payment terms - Net days and early payment discounts, also supporting end-of-month and end-of-week options. See [Configuring Payment terms](https://docs.eu-pactum.com/procurement-product/configuring-operational-procurement/configuring-payment-terms.md) for details.

If no payment term options are configured at the workspace level in Procurement product, the system will default to price-only negotiations and quote collection.

### Additional information for suppliers

During the event creation, additional information can be provided. This will be shown to suppliers at the beginning of the chat. Typically, these are either statements of work, or the supplier's own quote so that the supplier can recognise the context more easily. Additional information can be either:

* Attachments (e.g. pdf, xls and other common file types)
* Personalised intro message (free text input)

### Targets

As an additional input, users can provide desired price per item or as a total. These targets give Pactum additional context about what kind of negotiation results are. The desired price can be pricing from previous similar orders or pricing based on market research.

The desired price is used as a price reference in the negotiations. All Pactum offers will be below the desired price and Pactum will not terminate the negotiations earlier than planned if supplier counteroffers are above the desired price.

However, the desired price is not used for savings calculations.

### Disabling reaching out to specific suppliers

Suite users can selectively disable suppliers from being reached out to. When a supplier is disabled, Pactum will not reach out to them.

However, their submitted quotes remain visible and are still used as benchmarks for negotiation strategy and pricing comparisons when negotiating with other suppliers.

These suppliers can also be marked as a winner after the event has concluded.

### Event rejection

In the case of Coupa and Ariba integrated workspaces, Pactum checks whether the PR has any invoices attached. If so, it is a sign of retrospective spend for which the negotiation potential is low and as such Pactum will not reach out to suppliers and will mark the event status as rejected. In the approval flow, Pactum approves it automatically. More details in [Supplier data correction](https://docs.eu-pactum.com/procurement-product/supplier-data-correction.md).

### Interactions with suppliers

#### Emails

After event is started, Pactum will reach out to all suppliers with an email inviting them to Supplier Portal. The content of the email depends on the event context, e.g.

* if there are competing suppliers, emails apply competitive pressure on the suppliers
* if a supplier has not yet provided a quote, they will be invited to participate in the sourcing event

Optionally, the link email can be preceded by an introductory letter that is sent for first-time suppliers and explains the process that is about to happen.

Suppliers are sent reminder emails if they haven't yet entered the supplier portal or if they entered it but didn't finish the discussion.

#### Entering the supplier portal

We provide suppliers with necessary content and confirm there are no reasons it should not take place.

* When no initial quote is available, the process begins with a request for quote (RFQ) in the chat. Once the supplier provides their quote, pricing and relevant terms are negotiated when necessary. Supplier can decline to provide a quote which will be reflected as a status in Suite. Only after quote collection, the supplier will proceed to the negotiation phase.
* When an initial quote is available, the quote is first confirmed with the supplier. If there are no blockers, negotiations begin immediately.

#### Natural language processing

Throughout the chat in the supplier portal, suppliers can share their reasoning and engage in more natural, conversational discussions during the negotiation. Supplier free-text responses are made available in Suite. Guardrails are applied which prevent suppliers from being able to learn acceptance thresholds.

#### Pre-negotiation checks

Different parameters are validated with the supplier before negotiation inside the supplier portal. Some parameters are always validated; some are configurable during implementation.

* Correct person to negotiate with (always applicable):
  * if the supplier claims to be the wrong contact, then we ask for a new contact and automatically launch a new chat with the right contact
* Correct scope of negotiation (always applicable)
  * if the negotiation has wrong items or details then we decline the negotiation
* Items/services haven't yet been delivered (configurable)
  * if the demand has already been fulfilled (i.e. retrospective PR), we decline or continue to negotiate based on workspace configuration
* Confirmation of whether an existing pricing agreement already exists (configurable)
  * If it exists, the supplier is requested to upload supporting evidence. Uploaded attachments are visible in Suite. If the supplier can provide a signed proof, we will not negotiate. If the supplier can’t provide a signed proof, we will still negotiate
* Delivery location confirmation (if a delivery location provided, configurable)
  * Soft enforcement: we’ll continue to negotiate even if the supplier does not agree to the delivery location
  * Hard enforcement: we will not negotiate and decline
  * If no delivery location is provided during event creation, it will not be shared with suppliers
* Delivery date confirmation (if a delivery date is provided, configurable)
  * Soft enforcement: we’ll continue to negotiate even if the supplier is unable to provide it by the delivery date
  * Hard enforcement: we will not negotiate; or feature turned off
* Lead time confirmation (if lead time is provided, configurable)
  * Soft enforcement: if supplier is unable to meet expected delivery date, Pactum asks for supplier's proposal about lead time and applies soft pressure on the supplier to improve the commercial terms instead
  * Disabled: If lead time feature is not turned on or lead time is not provided upon event creation lead time won't be discussed with the supplier.

#### Pause

In competitive events, if certain criteria are met (in particular the deadline being long enough and there are not a sufficient number of suppliers with existing bids), Pactum will pause the supplier chat after the initial quote has been captured. The supplier will be informed that the conversation is on hold until bids from other suppliers are collected. If there are enough bids from other suppliers (or if a timeout is reached), Pactum will reach out again over email to invite the suppliers back who were previously paused. This helps to achieve the following:

* Pactum has a much better price reference for the negotiation and can use stronger arguments in the negotiation
* The supplier feels the competitive pressure and is incentivised to improve their bid further

#### Negotiation

Pactum's aim in a negotiation is to agree on terms that maximise savings, don’t violate constraints that have been provided by the buyer and don’t damage the supplier relationship. The final decision whether to award the supplier and which supplier to award always remains with the buyer.

In the negotiation phase of the chat, Pactum and the supplier are exchanging arguments, counter-arguments, offers and counter-offers. Based on the available context, Pactum determines opening and final targets, determines the optimal number of engagement points, and selects the strongest arguments based on competition, supplier offer evaluations, and available incentives. Arguments are sequenced to balance offers from us and the supplier, ensuring each step moves us closer to our target without unnecessary concessions.

If the supplier provides initial quote in the chat, in some cases it may happen that their first quote is considered very competitive (e.g. compared to other suppliers or the buyer's desired price). In these cases, Pactum skips the negotiation phase as the likelihood of improving the terms even further is low.

#### Offer generation

Pactum's anchor offer is determined by taking into account various features about the demand (e.g. industry, spend amount) and supplier (country, past supplier behaviour). Pactum predicts how different anchors would affect the negotiation outcome and chooses the optimal anchor to maximise the concessions that the supplier is willing to make. If the anchor offer is too aggressive, credibility of the entire negotiation is reduced; if the anchor offer is not aggressive enough, the supplier may concede less compared to more aggressive anchors. This is optimised based on years of negotiation experience with tens of thousands of suppliers across the world and in different industries.

If payment terms are negotiated, Pactum generates MESOs (multiple equivalent simultaneous offers) which are equally acceptable for the buyer based on the WACC provided. This increases the likelihood that there is at least one acceptable offer for the supplier, helping to reach a mutually beneficial agreement.

Subsequent offers will move step by step closer to the final target (the lowest of desired price and existing supplier quotes).

#### Feedback on supplier competitiveness

Pactum gives suppliers feedback on the competitiveness of their bid throughout the negotiation process, utilising both text and visual components. Competitiveness is assessed against other initial bids and the buyer's desired price. Final negotiated bids from the competitors are not taken into account to disincentivise suppliers from engaging at the last minute.

#### Finalization of the discussion

In the final stage of the chat, the supplier is presented with a summary of what was agreed, along with how competitive their final offer is. In this part, we capture any additional information and provide next steps for the supplier. If an agreement was reached, the supplier is requested to upload an updated quote.

At the end of the negotiation, the supplier is also asked to provide feedback. They can give feedback both on how satisfied they are with their final bid and how satisfied they were with the Pactum negotiation process.

### Winner and baseline selection

In case of competitive events, Suite users are able to choose a winner and baseline suppliers for each of the events. These values are not reported to integrated systems (Coupa/Ariba), nor are they reported to suppliers. These choices are used within Pactum for savings calculation purposes.

Winner is the supplier who is awarded with the PO or a contract. The best practice for choosing the baseline is the supplier from whom the business would have bought without the procurement department and Pactum involvement.

### Savings calculation

Savings are calculated as the difference between the winning supplier's final quote and the baseline supplier's initial quote. Note that if winner and baseline supplier are different, savings may not reflect true savings if bids from these suppliers are not directly comparable.

Price savings are calculated as the difference between the total price from the baseline supplier's initial quote and winning supplier's final quote.

As the exact invoice date is not known by the time of the negotiation, then for certain payment terms for which payment days depend on the exact invoice day, Pactum calculates average payment days (e.g. EOM payment terms add additional 15 days on average). Payment days improvement is calculated as the difference between payment days of the winning supplier's final quote and the baseline supplier's initial quote. Finally, the improvement in payment days is calculated as:

<p align="center"><span class="math">\text{capital savings} = \text{baseline price} × \frac{\text{days improved}}{365\text{ days}} × \frac{\text{cost of capital}}{100\%}</span></p>

If initial payment terms are not provided for some suppliers, it is assumed that they are equal to the default baseline payment terms that were provided to Pactum during the implementation phase. Similarly, the cost of capital is assumed to be the value provided to Pactum during implementation. The cost of capital value can be updated, but savings on past events won't be changed retrospectively.

If payment terms have early payment terms option, it is assumed that early payment terms are exercised if and only if the capital savings is higher with early payment term options.

### Deadline extensions

For ongoing events, it is possible to extend deadlines in Suite. This applies to all suppliers who have not yet finalised the discussion. Pactum will send an email notification to the suppliers. It does not have effect on the suppliers who have already concluded their discussions.

As of now, it is only possible to extend deadline for ongoing events.
