Skip to main content

 

 

Coupa Success Portal

Coupa/SAP Integration Playbook

 

EXAMPLE INTEGRATION FLOW: PROCURE TO PAY (P2P)


There are many different integration flows that Coupa customers use to implement Coupa with SAP. A common one is the full Procure to Pay (“P2P”) process. Under this scenario the entire process from purchase requisition through requisition approval, PO, receipt, invoice, and invoice approval is managed through Coupa. Suppliers get many flexible options to connect so that they can receive POs, acknowledge POs and send invoices. Suppliers can upload their information and catalogs and can make comments through the system to ask questions or resolve any issues. Suppliers also receive status updates by email or through the portal. Integration flows with SAP occur at the beginning of the process to bring in master data and at the end to push back process results including approved invoice for payment.

Coupa Integration Design with Flat File.pngCOUPA CUSTOMERS TYPICALLY USE ONE OF TWO APPROACHES FOR INTEGRATING COUPA AND SAP

  • Coupa API – (fully documented at http://integrate.coupa.com) our standard REST-based APIscan be used by customers who would like to implement more sophisticated integrations and isacommon approach for those customers with a middleware platform and resources availabletoorchestrate integration between Coupa and SAP.•Coupa
  • CSV Flat Files - a standard file format is available for all master and transaction data objectstypically integrated between Coupa and SAP and can be leveraged by customers who have theresources available to translate between Coupa’s format and the formats needed for SAP

In many cases, Coupa customers will mix and match various integration methods to provide an optimum model for integration. For example, you may leverage Coupa’s standard flat-file formats for inbound master data and use the Coupa API’s for outbound transactions. The method(s) chosen will vary from customer to customer and Coupa will provide guidance as part of the implementation process

FROM SAP TO COUPA

  • Vendors - vendors with necessary details for completing transactions
  • Accounting Data - company code, account category, general ledger, project, asset, WBS, internal order, cost center
  • Budgets - budgets for each account to inform purchase approval decisions
  • Exchange Rates - rates for international payments
  • Invoice Payments - payments that have been made to suppliers 
  • Custom Status Exports - PO and Invoice status export

FROM COUPA TO SAP

  • Purchase Orders - POs that have been approved
  • PO Revisions - changes to POs that need to be logged in SAP
  • Acknowledgements - POs that have been accepted by suppliers
  • Goods Receipts - end user receipt of goods or services from suppliers
  • Invoices - Invoices from suppliers that are approved as “OK to Pay”

 

 

  • Was this article helpful?