---
sourceDocument: Yokohama Finance and Supply Chain
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/source-to-pay-operations

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Employee


---

# Report savings when awarding a supplier

# Report savings when awarding a supplier {#ariaid-title1}

* Release version: Yokohama
* 
* Updated November 7, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

When awarding a supplier, enter the spend and savings data for the sourcing event associated with the pipeline project.

## Before you begin

Role required: sn_shop.procurement_specialist

## About this task

The sourcing event that you plan to work on, and all its associated negotiations, sourcing requests, and purchase lines must be in the Requires Decision state. When negotiations are complete for a sourcing event, you can
award one or more suppliers. Awarding suppliers creates purchase requisitions for the selected suppliers and items.

## Procedure

1. Navigate to Source-to-Pay Workspace.
2. Select the list icon (![List icon.]()) and do one of the following:  
   * Navigate to ListsMy workSourcing events.
   * Navigate to ListsAll workSourcing events.
   {#report-savings-pipeline__ul_dwq_tzd_wfc}
3. Open the sourcing event that is in the Requires Decision state.  
4. Select Award.  
   The Award to supplier dialog box is displayed.
5. In the Supplier field, select a supplier, and then select Next.  
6. Enter the spend and savings data in the Final spend, Cost avoidance, Lost savings, and Other savings fields.  
   Note:  
   The Review financials modal is displayed only if the sourcing event is associated with a pipeline project.

   The Hard savings field is auto-populated and displays the
   cumulative savings from all sourcing events associated with the pipeline project. This value is calculated by summing the Negotiated savings from all closed purchase requisition lines (PRLs) within the sourcing
   events.

   You can edit the Hard savings field if you'd like. If you edit the Hard savings field, a warning message appears indicating that the entered value differs
   from the cumulative negotiated savings on PRLs. This warning is shown only if there are negotiated savings on any PRL.
7. Select Submit.
{#report-savings-pipeline__steps_msj_kxf_zfc}

## Result

The sourcing event is moved to Closed Complete, with the individual negotiations under it moved to Closed Decided or Closed Rejected based on your selection. The awarded sourcing request is moved to Closed Complete, with
purchase requisitions automatically created for the purchase lines. In addition, the spend and savings data is updated in the associated pipeline project.

*[\>]: and then