Integration settings on Source-to-Pay side

  • Release version: Zurich
  • Updated March 12, 2026
  • 3 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 Integration settings on Source-to-Pay side

    This guide explains how to configure your Source-to-Pay (S2P) instance to integrate inbound and outbound data flows with your ERP system. The integration allows automatic posting of purchase orders, receipts, invoices, and downloading of primary master data from the ERP, enabling seamless data synchronization for procurement processes.

    Show full answer Show less

    Prerequisites and Initial Setup

    • Assign Roles: Add Importtransformer and Soap roles to the integration user in S2P.
    • Obtain ERP Details: Collect ERP integration user credentials and SOAP or REST API details from your ERP team, depending on the ERP’s web service type.
    • Multiple ERP Instances: Configure separate integrations for each ERP instance if applicable.

    Configuration Steps

    • Define ERP Source: Set up the ERP source in S2P to identify the system for primary data integration and procurement service management.
    • Authentication Profile: Create a basic authentication profile using ERP credentials and associate it with service maps for secure web service communication.
    • Source Configuration: Define ERP source configuration to specify connection parameters for each ERP system integrated with S2P.
    • Configure Service Maps: Set up individual web services for key transactional and master data entities, including:
      • Posting purchase orders, receipts, and invoices to ERP
      • Fetching supplier, cost center, purchasing entity, general ledger account, asset category, and material group updates from ERP
      Each service map requires specifying the endpoint and ERP credentials, with separate web service records for customization.
    • Scheduled Data Synchronization: Configure and schedule the Fetch Spend Primary Data job to regularly update primary data from ERP, ensuring integration accuracy.
    • User Mapping: Load and maintain a mapping table linking S2P users with ERP procurement buyer roles to support requisition assignments.
    • Entity Mappings: Map critical entities between S2P and ERP to align data semantics, including:
      • Purchasing entity to legal entity
      • Asset category to capitalization policy
      • Material group to model category
      • Delivery address location to ERP address code
      • ERP plant ID to ERP location, using the ERP address identifier 1 field

    Benefits for ServiceNow Customers

    By following these integration settings, ServiceNow customers can establish robust, automated data flows between Source-to-Pay and ERP systems. This ensures procurement transactions and master data remain synchronized, reducing manual effort and errors while enabling efficient procurement operations.

    Configure your Source-to-Pay (S2P) instance to support inbound and outbound integration with your ERP system. This integration configuration enables you to automatically post purchase order, receipt, invoice, and download primary data from the ERP.

    Before you start the integration configuration, you must complete the following tasks.
    • Add the following roles to the Integration user:
      • Import_transformer
      • Soap
    • Get the following information from the ERP team:
      • ERP integration user credentials.
      • SOAP or REST API details based on your ERP system and the type of web services you are using for the integration.
    Note:
    If the application needs to support multiple ERP instances, configure S2P to integrate with each ERP instance separately.
    1. Define an ERP source.

      Define the ERP source that you want to integrate with Procurement Service Management. This information is required for any primary data. For more information, see ERP source and Primary data integration.

    2. Set up the authentication profile.

      Create a basic authentication profile that can be used for web service integration with ERP. Register the ERP integration username and password to create the authentication profile and associate it to service maps. For more information, see Set up the authentication profile.

    3. Define source configuration for ERP.

      ERP source configuration determines the ERP source to which your ERP system connects. For more information, see ERP source configuration and Define ERP source configuration for Source-to-Pay.

    4. Configure service maps for the following entities:
      • Post purchase order.

        Set up web services for the source configuration to post purchase orders to ERP.

      • Post receipt.

        Set up web services for the source configuration to post receipts to ERP.

      • Post invoice.

        Set up web services for the source configuration to post invoices to ERP.

      • Fetch supplier.

        Set up web services for the source configuration to fetch supplier updates from ERP.

      • Fetch cost center.

        Set up web services for the source configuration to fetch cost center updates from ERP.

      • Fetch purchasing entity.

        Set up web services for the source configuration to fetch purchasing entity updates from ERP.

      • Fetch general ledger account.

        Set up web services for the source configuration to fetch general ledger account updates from ERP.

      • Fetch asset category.

        Set up web services for the source configuration to fetch asset category updates from ERP.

      • Fetch material group.

        Set up web services for the source configuration to fetch material group updates from ERP.

      Note:
      For configuring each of these service maps, provide the connection end point and the ERP credentials that you set up for your authentication profile. Also, create a separate web service record for each service request that you want to customize.

      For more information, see Configure service maps for Source-to-Pay.

    5. Configure scheduled job to synchronize primary data updates from ERP.

      Set up the interval in the Fetch Spend Primary Data scheduled job to periodically synchronize primary data updates from the ERP, for posting services to work.

    6. Load data to ERP user mapping table.

      Set up S2P and ERP User ID mapping for the integration to work. The mapping is maintained for all active users who have the procurement buyer role in ERP. These users should be used in the requisition assignment rule. For more information, see Load data to ERP user mapping table for Source-to-Pay.

    7. Map the following entities:
      • Purchasing entity.

        Map legal entity to the downloaded purchasing entity in the purchasing entity table.

      • Asset category.

        Map capitalization policy to the downloaded asset category in the asset category mapping table.

      • Material group.

        Map model category to the downloaded material group in the material group mapping table.

      • Delivery address.

        Map location reference in the delivery location table to ERP address code in the address mapping table.

      • ERP plant.

        Map ERP plant id to the corresponding ERP location in the address mapping table. Use the ERP address identifier 1 field for this mapping.