Source-to-Pay Integration Framework release notes

  • Release version: Store
  • Updated June 11, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Source-to-Pay Integration Framework release notes

    The Source-to-Pay Integration Framework application on the ServiceNow Store provides a standardized integration framework to connect sourcing and procurement workflows across various organizational systems and third-party tools. It enables seamless data exchange and process automation for purchase requisitions (PRs), purchase requisition lines (PRLs), purchase orders (POs), invoice processing, and supplier management with external ERP and procurement systems such as SAP Ariba.

    Show full answer Show less

    Key Features

    • Enhanced outbound staging tables for PR, PRL, PO, and invoices with detailed field mappings including legal entity, buyer group, requested dates, supplier ERP codes, and budget fields to support comprehensive data synchronization.
    • Support for decoupled PR/PO flow allowing independent outbound processing of purchase requisitions separate from purchase orders.
    • Implementation of Access Control Lists (ACLs) to comply with directives such as Non‑Glide Cobalt Raven Brazil.
    • Automatic assignment and backfill of ERP source fields ensuring alignment of procurement data with business owner legal entity configurations.
    • Performance optimizations in transform maps for outbound purchase orders to improve integration efficiency.
    • Supplier qualification before sourcing bid information when sending sourcing requests to third-party solutions.
    • Security fixes and enhanced permissions ensuring proper access and update rights on staging tables to avoid integration blocking issues.
    • Blocking edits and cancellations on POs in target ERP systems like Ariba to maintain data integrity.

    Practical Impact for ServiceNow Customers

    With the latest updates, ServiceNow customers can expect improved integration reliability and richer data exchange capabilities enabling smoother procurement and sourcing workflows. The framework supports complex requisition and order scenarios including service requisitions and complies with regional directives through ACLs. Decoupling PR and PO flows allows greater flexibility in procurement processes. Customers will benefit from optimized performance, enhanced security, and reduced errors during data synchronization with external ERP systems.

    Overall, the framework empowers procurement teams to automate and standardize source-to-pay processes with higher accuracy and compliance, improving operational efficiency and supplier collaboration.

    Version history for the Source-to-Pay Integration Framework application on the ServiceNow Store.

    Important:
    For details on system requirements and family compatibility, view the application listing on the ServiceNow Store website.

    Version history

    Version 11.0.3 - June 2026
    • New:
      • Added the Remit-to party column to the outbound invoice staging table.
      • Added Short Description and Legal Entity field mappings for outbound purchase requisitions (PRs).
      • Added Supplier ERP Code, requested start date, requested end date, and maximum budget field mapping for outbound PRL.
      • Mandated Asset ID field for Ariba at the PRL level and in outbound PRL.
      • Enabled decoupled PR/PO flow to support outbound processing of PRs independently.
      • Added Access Control Lists (ACLs) to support the Non‑Glide Cobalt Raven Brazil directive.
      • Updated PR/PO references to support decoupled PR/PO processing.
      • Mandated fields on Outbound PR for Ariba based on account assignment category selection.
    • Changed:
      • Outbound flows no longer trigger for Closed Canceled and Closed Rejected PRs.
      • Updated PR behavior to use COA field selection instead of CapEx/Expense/Prepaid account fields.
      • Restrict cost allocation type to cost center lines only in the Shopping hub for SAP Ariba PRs.
      • Enabled decoupled PR/PO flow to support outbound processing of PRs.
      • Blocked edit and cancel actions on POs for the target system Ariba.
    • Fixed: Fixed issue with UI Action retry for PR and PO processing.
    Version 12.9.0 - March 2026 (Zurich)
    • New: Added enhancements to the Purchase Requisition Line (PRL) outbound staging table
    • Changed: Performance optimizations applied to the PO transform map
    Version 10.13.0 - January 2026
    • New:
      • Added missing outbound staging fields for Purchase Requisition (PR) and Purchase Requisition Line (PRL), including Buyer Group, Short Description, Requested Delivery Date, Legal Entity, and other required attributes.
      • Added additional outbound fields required to support service requisition scenarios.
      • Introduced the missing Purchase Requisition entity at the integration service record level.
    • Changed:
      • Updated outbound mappings to ensure required fields are mapped between base tables and outbound staging tables for requisitions and orders.
      • Updated PO Header outbound staging to map Purchasing Group from the base table.
      • Updated supplier and supplier contact data source indexing for integration configuration correctness.
    • Fixed:
      • Fixed missing outbound fields that blocked Purchase Requisition creation in ERP.
      • Fixed access issues by enabling required create/update permissions on PR and PRL staging tables.
    Version 12.0.1 - December 2025 (Zurich)
    • New: Created a new integration table for Purchase Requisition Line outbound processing with comprehensive field mapping, including account assignment, state, costs, WBS elements, and cancellation tracking.
    • Changed:
      • Extended the existing Purchase Requisition and Purchase Requisition Line inbound transform maps to support ERP integration scenarios while maintaining backward compatibility with Punchout functionality.
      • Implemented automatic assignment of the ERP Source field on Sourcing Requests and Purchase Requisition Lines upon creation. This update includes:
        • A backfill script for existing records
        • Updated outbound mapping to ensure accurate Target ERP values
      • Ensured consistent ERP Source values are populated on Sourcing Requests and Purchase Requisition Lines to align with the business owner’s legal entity configuration across all SPO entities.
      • Security fixes.
    Version 3.3.4 - December 2023 (Utah)
    Minor fixes.
    Version 4.0.1 - August 2023
    Minor fixes.
    Version 3.3.3 - May 2023
    Minor fixes.
    Version 3.3.1 - August 2022
    Minor fixes.
    Version 3.2.1 - May 2022
    Changed: When sourcing requests are sent out to third party solutions, the procurement team can now qualify suppliers before sourcing bid information from the third party solutions.
    Version 3.1.2 - February 2022
    Standardize the way in which third-party tools and systems integrate with Procurement Service Management. This application provides a standard framework through which a partner or supplier can integrate sourcing and procurement workflows across organization silos and systems.