---
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


---

# Source-to-Pay integration framework

# Source-to-Pay integration framework {#ariaid-title1}

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

As part of the Source-to-Pay (S2P) integration framework, customers can install an optional third-party ERP integration application that enables primary data, fixed assets, purchase order, receipt, invoice, and tax integration
capabilities between S2P and the third-party ERP application.

Primary data entities include:

* Supplier
* Profit center
* Cost center
* Ledger accounts
* Purchase organizations
* Asset category
* Material mapping
* Unit of measure

{#source-to-pay-integration-framework__ul_syp_tjp_hlb}

While the third-party application is the system of record for primary data, S2P is the system of record for purchase orders and receipts. Invoices are either created manually in S2P or through an external supplier portal (for
example, Ariba). For tax calculation and integration, see [Tax calculations](https://servicenow-prod.fluidtopics.net/3I6PksH_66fXoCkC1ZB2Wg "A framework to integrate tax calculations into Sourcing and Purchasing Automation is implemented such that approvals can be done on the full value of purchases.").

The integration between S2P and the third-party application requires settings on both sides so that these applications function properly together.

* [Integration settings on Source-to-Pay side](https://servicenow-prod.fluidtopics.net/EhsL~8O8Ock0Rjfqqp6XnQ "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.")
* Integration setting on the third-party side.

{#source-to-pay-integration-framework__ul_tly_wqg_3lb}

## Applications required for third-party integration {#source-to-pay-integration-framework__section_xd4_frg_3lb}

The integration requires the Finance -- ERP Integration store application.

## Permissions and roles for third-party integration {#source-to-pay-integration-framework__section_ssj_3rg_3lb}

The following ServiceNow roles are required for integration:

* System administrator (admin) for installation of the integration application.
* Procurement Specialist (sn_shop.procurement_specialist) for defining the ERP source.
* FCA Integration user (sn_fcms_intg.integration_user) for ERP source configurations such as web service authorization, web services for Park and Post, Reverse, and User and Role mapping.Add the following roles to the FCA
  Integration user:

  * Import_transformer
  * Soap
  {#source-to-pay-integration-framework__ul_yq5_zy4_j3b}
{#source-to-pay-integration-framework__ul_mzb_3dn_j3b}

## MID Server required for third-party integration {#source-to-pay-integration-framework__section_fnv_lcn_j3b}

This integration requires an installed and configured MID Server in your ServiceNow instance to connect to the ERP system server. See [Installing the MID Server](https://www.servicenow.com/docs/access?context=mid-server-installation&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) for details.  
Note:  
The MID Server integration is required only for an ERP integration using SOAP services.