Sourcing and Procurement Operations integration with third-party sourcing solutions

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 4 minutes de lecture

    • ServiceNow can integrate with third-party sourcing solutions to automate the sourcing process within the Sourcing and Procurement Operations product. A generic, easily configurable sourcing integration framework is provided within Source-to-Pay Integration Framework to enable you to specify the business criteria for triggering an integration. This integration framework can also integrate with multiple third-party sourcing solutions based on different criteria.

    Customers can either build the connector to that third-party tool or find one in the ServiceNow store.

    For example, Fairmarkit, a third-party solution, built and certified its own ServiceNow application to the store, which leverages the integration framework to connect with the Fairmarkit system. For more information on this integration, visit store.

    For information on decision configuration, see Decision configuration for third-party sourcing.

    To learn about the integration tables, see Integration tables for third-party sourcing.

    Third-party sourcing integration process

    • If an integration is triggered, considering that applicable business criteria are defined in the decision table, and a request for pricing initiated by a shopper in ShoppingHub meets the criteria, one or more sourcing requests within a single purchase are automatically grouped into a single sourcing event. These are systematically created in the Sourcing and Purchasing Automation application.
    • When the negotiation setup playbook is complete, and the sourcing event is in the Work in Progress state, with the associated negotiations, sourcing requests, purchase lines, cases, and tasks in the Negotiation in Progress state, relevant data is populated in the Sourcing Outbound Queue, Sourcing Line Outbound Queue, and Sourcing Event Outbound Queue tables. This data can then be processed by the third-party solution accordingly, to initiate an RFx in their platform. Sourcing event is also created for the integrated sourcing request.
      Remarque :
      After a sourcing request is created and posted to the Sourcing Outbound Queue table, the third-party tool that is responsible for processing that sourcing request is identified and stored in the Third party tool name field.
    • A system property for the supplier responses close date (sn_spend_intg.u_bids.end.date) sets the Supplier responses close field value on the sourcing event and sourcing requests to after the sourcing event has been created, plus the number of days defined. The default value is three days. The sourcing manager can override this value manually when updating this field on the sourcing event record.
      Remarque :
      A schedule job can be set up in the ServiceNow instance to check if the supplier responses close date has been reached (aka today). When done, ServiceNow stops receiving bids from suppliers and moves all individual supplier negotiations within the sourcing event to the Pricing Obtained state, and then to Requires Decision. The sourcing manager or fulfiller can then award a supplier with the business. The timestamp of the supplier responses close date is 23:59:59 of the day the bids close, in UTC date/time format. As the sourcing manager, you can also decide to close the bids now, with the date and timestamp of now, and proceed with the awarding flow without any wait time.
    • If the supplier responses close date changes on the sourcing request, then this update is sent to the Sourcing Outbound Queue table. The Supplier responses close field is updated. Also, if a sourcing request or purchase line is canceled, this status is also sent back to the sourcing request or purchase line outbound tables respectively.
      Remarque :
      The supplier responses close date is read-only on the sourcing request, but any change of the supplier responses close date on the sourcing event rolls up to the sourcing requests.
    • If there’s an error inserting new or updated records to this table, then the integration status is updated to Failed. The sourcing request at this point is in the Pending Resubmission state. The error details are captured in the Processing Message field and the integration error task is displayed. The procurement specialist must address the error and then resubmit both the sourcing requests and sourcing event by selecting the Resubmit button.
      Remarque :
      Currently, errors are logged only on the Sourcing Outbound Queue table.
    • Suppliers are invited to participate in a bid and engage through the third-party application platform.
    • When quotes are returned, the Sourcing Bid Stage table is populated by the third-party solution and the information is processed internally within ServiceNow using a transform map to populate the purchase lines on the sourcing request.
      Remarque :
      When an RFx is created or awarded in the third-party tool, shoppers and sourcing managers are notified through emails and alerts from Shopping Hub and Source-to-Pay Workspace respectively. Shoppers and sourcing managers are also notified about rejected bids, irrespective of the integration.
    • If additional supplier bids are returned from the third-party solution, an existing logic in ServiceNow determines if a new supplier, supplier product record, or both must be created.
    • After awarding is done in ServiceNow, that information is sent back to the third party using the Awarded Supplier Outbound Queue table. Awarding can also be done in the third-party tool, in which case the data is received by ServiceNow.

    For information on sourcing request, negotiation, and sourcing event flows, see Sourcing request, Negotiations and Sourcing events, respectively. For more information, see Compare quotes and select a supplier.