2. Supplier Integration Scenarios

Revised: 24 April 2017

Overview

In many ways, Suppliers are just as important to business as customers. Without the tools we use to deliver our products and services, it would be impossible to be successful. As a Supplier of eProcurement software to you, we take the buyer-vendor relationship very seriously and consider Suppliers a major part of the Coupa procurement foundation. As such, Coupa contains a number of tools that make sending purchase orders to Suppliers and receiving invoices back as fast and transparent as possible. In Coupa, the Supplier record includes information about the Supplier's company, what they sell, how purchase orders are sent, and if applicable, how invoices are received. 

The Supplier object is a flat structure in Coupa as opposed to other ERP systems with parent-child relationships. This flattening task needs to be supported in the ERP Connector product.

To be able to execute business processes in Coupa, you must create and maintain Supplier objects in Coupa. Relevant associated data objects (Enterprise, Content Group, Commodity, Payment Term, Shipping Term, Tax Code) must exist as a prerequisite in Coupa to allow a successful automated integration.

Supplier master data could change in the ERP / Procurement system, so it is important to replicate the changes in Coupa.

Each system can store different levels of Supplier information, so ensure that you can incorporate all Coupa standard fields/tags by default and you have the flexibility in your tool to allow custom fields if required.

Methods

See Using API and Using CSV for an overview of each method. 

Note that if REST API is used to maintain the Supplier object, the Supplier changes must be sent as soon as they are created/updated in ERP as opposed to batch calls.

Scenarios

For certification purposes, we have identified several common Supplier scenarios used by Coupa customers. Each scenario must be executed successfully using CSV and/or API.