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 platform for sourcing and procurement workflows. It enables seamless integration of procurement processes such as purchase requisitions (PR), purchase requisition lines (PRL), purchase orders (PO), and supplier data across multiple systems and organizational silos. This framework supports integration with ERP and third-party procurement systems, improving automation and data consistency across the source-to-pay lifecycle.

    Show full answer Show less

    Key Features

    • Outbound Staging Enhancements: Multiple releases introduced expanded field mappings for PR, PRL, and PO outbound staging tables, including financial, legal entity, supplier, and account assignment details. This ensures richer data exchange with ERP and third-party systems.
    • Decoupled PR/PO Processing: Recent versions enable independent outbound processing of purchase requisitions and purchase orders, enhancing flexibility in procurement workflows.
    • System Compatibility and Security: Added Access Control Lists (ACLs) to comply with regional directives such as Non-Glide Cobalt Raven Brazil, along with security fixes to safeguard integration processes.
    • Performance Improvements: Optimization of transform maps and indexing ensures efficient data processing and integration reliability.
    • Supplier Qualification: Enables procurement teams to qualify suppliers before sourcing bids are retrieved from third-party solutions.
    • Consistent ERP Source Assignment: Automatic assignment and backfilling of ERP Source values on sourcing requests and PRLs align integration data with legal entity configurations.

    Practical Benefits for ServiceNow Customers

    • Improved data accuracy and completeness in procurement integrations through expanded and mandated field mappings.
    • Increased flexibility by allowing decoupled processing of purchase requisitions and purchase orders.
    • Enhanced security and compliance with updated ACLs and regional directive support.
    • Streamlined supplier qualification processes integrated within sourcing workflows.
    • Better performance and reduced errors in integration processing due to fixes and optimizations.
    • Support for complex procurement scenarios including service requisitions and multi-entity legal configurations.

    Expectations

    By implementing the Source-to-Pay Integration Framework, ServiceNow customers can expect a robust, scalable, and secure integration solution that simplifies procurement data exchange with ERP and third-party systems. The framework’s evolving capabilities reduce manual intervention, improve compliance, and provide enhanced visibility and control over procurement workflows, ultimately accelerating source-to-pay cycle times and improving operational efficiency.

    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.