Blueprint

Confidential

Configuration Blueprint Document

Revision History
Version History
1.0

Date of Revision
October 1, 2014

Author

Comments
Initial Draft

Project Team
Title
Project Owner/ Sponsor:
Project Manager:
Implementation Manager:
Business Project Lead:
Technical Project Lead:

Company Name

Coupa

Authorizers for Sign-Of

Role

Name

Approval Type
Peer Review / Sign-of

Signature

Date

Distribution Team (In Addition to Authorizers)

Role

Coupa Software
Business Blueprint: Client Name

Name

Page 1 of 40
Company Confidential

Blueprint
Confidential

Table of Contents
Executive Summary........................................................................................................................ 6
Customer Success Metrics (This should be updated after Success Workshop)...............................7
Definitions....................................................................................................................................... 8
1.

Coupa Overview & System Configuration Options..................................................................10

2.

Global Settings in Coupa......................................................................................................... 11

2.1.

Company Code Configuration........................................................................................ 11

Address - Configuration.............................................................................................................. 11
Accounting - Configuration........................................................................................................ 11
2.2.

Security Controls.............................................................................................................. 11

Security Controls Customer Best Practices.............................................................................. 11

Security Controls - Configuration............................................................................................... 12
Custom Roles - Configuration..................................................................................................... 12
2.3.

Dashboard Controls.......................................................................................................... 13

Dashboard Controls Customer Best Practices.........................................................................13

Dashboard Controls Configuration........................................................................................... 13
2.4.

Content Groups................................................................................................................ 13

Content Groups Customer Best Practices................................................................................ 13

Content Group - Configuration................................................................................................... 13
2.5.

Budgets............................................................................................................................ 13

Budget Customer Best Practices............................................................................................. 13

Budget - Configuration............................................................................................................... 14
2.6.

Commodities Codes.......................................................................................................... 14

Commodities Codes Customer Best Practices.........................................................................14

Commodities Codes Configuration.......................................................................................... 14
2.7.

Commodity Classification Engine..................................................................................... 14

Commodity Classification Engine Customer Best Practices.....................................................14

Commodity Classification Engine - Configuration......................................................................14
2.8.

Contracts.......................................................................................................................... 15

Contracts Customer Best Practices and Configuration............................................................15

2.9.

Ask an Expert................................................................................................................... 16

Ask an Expert Customer Best Practices and Configuration......................................................16

Coupa Software
Business Blueprint: Client Name

Page 2 of 40
Company Confidential

Blueprint
Confidential
2.10.

Home Page Content....................................................................................................... 16

Home Page Content Customer Best Practices and Configuration............................................16

3.

Sourcing.................................................................................................................................. 16
3.1.

Sourcing - Customer Best Practices.................................................................................. 16

3.2.

Sourcing Settings............................................................................................................. 17

3.3.

Sourcing Events................................................................................................................ 17

3.4.

Price Comparisons............................................................................................................ 17

Price Comparisons Customer Best Practices...........................................................................17

Price Comparisons Configurations........................................................................................... 17
3.5.
4.

Sourcing Approvals........................................................................................................... 17

Procurement........................................................................................................................... 17
4.1.

Procurement Process........................................................................................................ 18

Procurement - Data Process Flows............................................................................................. 18

Procurement Customer Best Practices.................................................................................... 18
Procurement - Configuration...................................................................................................... 18
Requisition to Invoice - Key Performance Indicators..................................................................19
4.2.

Purchase Channels / PO Types.......................................................................................... 19

Purchasing Channels Configuration......................................................................................... 19

4.3.

Procurement Approvals.................................................................................................. 20

Approvals Customer Best Practices......................................................................................... 20

Approvals Configuration.......................................................................................................... 20
Approval Key Performance Indicators...................................................................................... 20
4.4.

Order Lists........................................................................................................................ 21

Order Lists Customer Best Practices....................................................................................... 21

Order Lists - Configuration......................................................................................................... 21
4.5.

Advance Shipping Notices................................................................................................ 21

Advance Ship Notices Customer Best Practices......................................................................21

Advance Ship Notices - Configuration........................................................................................ 21
4.6.

Shipping Terms................................................................................................................. 21

Shipping Terms Customer Best Practices................................................................................. 21

Shipping Terms - Configuration................................................................................................. 21
5.

Invoicing................................................................................................................................. 22
Invoicing - Data Process Flows: Assumes a 3-way match Supplier.............................................22

Coupa Software
Business Blueprint: Client Name

Page 3 of 40
Company Confidential

Blueprint
Confidential
5.1.

Invoicing Global Configuration....................................................................................... 22

Requisition to Invoice - Configuration........................................................................................ 22

Requisition to Invoice - Key Performance Indicators..................................................................23
5.2.

Invoicing Tolerances......................................................................................................... 23

Invoicing Tolerances Customer Best Practices.........................................................................23

Invoicing Tolerances Configuration.......................................................................................... 23
5.3.

Invoicing Approvals........................................................................................................ 23

Invoicing Approvals Customer Best Practice........................................................................... 24

Invoice Approvals Configuration.............................................................................................. 24
Invoice Approvals Key Performance Indicators........................................................................24
5.4.

Payment Terms................................................................................................................. 24

Payment Terms Customer Best Practices................................................................................24

Payment Terms - Configuration.................................................................................................. 24
6.

Inventory................................................................................................................................ 25
6.1.

Inventory Process of Receiving......................................................................................... 25

Inventory - Customer Best Practices.......................................................................................... 25

Inventory Configurations......................................................................................................... 25
6.2.

Receiving Tolerances........................................................................................................ 25

Receiving Tolerances Customer Best Practices........................................................................25

Receiving Tolerances Configuration......................................................................................... 26
7.

8.

Expenses................................................................................................................................ 26
7.1.

Expenses Global Settings................................................................................................. 27

7.2.

Expense Categories.......................................................................................................... 27

7.3.

Expense Classification Engine.......................................................................................... 27

7.4.

Custom Fields................................................................................................................... 28

7.5.

Credit Card Usage and Transaction Mapping....................................................................28

7.6.

Expense Approval Chains................................................................................................. 28

Help Desk Support Process..................................................................................................... 28

8.1.

Coupa Support.................................................................................................................. 28

8.2.

Ask an Expert................................................................................................................... 28

9.

Summation of Risk and Mitigating Control.............................................................................. 29

9.

Appendix................................................................................................................................. 29
9.1.

Purchase Order Layout..................................................................................................... 29

Coupa Software
Business Blueprint: Client Name

Page 4 of 40
Company Confidential

Blueprint
Confidential
9.2.

Chart of Accounts............................................................................................................. 30

9.3.

Coupa Content Groups..................................................................................................... 31

9.4.

Account Security Settings................................................................................................. 31

9.1.

Coupa Custom Fields........................................................................................................ 31

9.1.

User Defaults and Authentication..................................................................................... 32

9.2.

Coupa Security Roles........................................................................................................ 32

9.3.

Coupa Custom Roles......................................................................................................... 33

9.4.

Approval Limits and Workflow.......................................................................................... 33

9.5.

Integrations Inbound...................................................................................................... 34

9.6.

Integrations - Outbound................................................................................................... 35

9.7.

Data Volumes................................................................................................................... 35

Coupa Software
Business Blueprint: Client Name

Page 5 of 40
Company Confidential

Blueprint
Confidential

Executive Summary
Purchasing organizations can lose a lot of gains made through strategic sourcing due to a lack of
compliance to preferred supplier contracts and arrangements without robust procure to pay
tools. Automating procure to pay via electronic tool sets is critical to both improving purchasing
performance and efficiency by providing the bedrock for sourcing buyers to drive savings via
strategic sourcing. The addition of procure to pay also adds benefits in spend analysis, added
controls (due to pre as opposed to post purchase approval), supplier relationships and
compliance.
Overall Process
E-Procurement systems exist to automate the Source to pay process. Source to pay is the
transactional flow of data for a user to request and receive goods/services and Suppliers to
receive payment. At Coupa, this transactional process is broken down into two phases with 8
distinct steps:

Source

Requisiti
on

Approve

Order

Receive

Invoice

Verify

Pay

In the PO process, Purchase Orders originate from a Requisition generated by end users and
approved based on a defined approval hierarchy. Receipts and Invoices are then entered against
the corresponding Request and PO. Automated 3-way matching, 2-way matching (also known as
assumed receipt) ensure that invoices that fall outside tolerance do not get paid until any
exceptions are resolved.
The Coupa toolset will allow three basic methods for end users to enter requisitions:

Catalog Relies on a previously setup series of catalogs by the Sourcing function for the
end user to select from
Web Form End users will input necessary information into a prescribed web form
developed by Sourcing. This web form will populate a shopping cart or requisition for
review or submission to a Supplier.
Free Form End user will input necessary information into an appropriate free form
purchase order along with any necessary Supplier information (for example a Supplier
quote).

Project Objective Customer Success Metrics

<COMPANY NAME> has a stated objective of Designing and Deploying a Standardized source to
pay platform. Our ultimate goal is to manage XXX% of Indirect Spend across the organization
using a preferred purchasing method and provide an incremental $XX million annually.
Blueprinting Document Goals
Coupa Software
Business Blueprint: Client Name

Page 6 of 40
Company Confidential

Blueprint
Confidential
The goal of this document is to capture both the business processes governing the Coupa
implementation and the associated integration & configuration decisions. The document contains
various sections which are meant to be guiding principles for configuring & finalizing the system.

Project Guiding Principles

1.
2.
3.
4.
5.
6.
7.

Get the process right before introducing technology

Do not create a legacy system order on day 1
Develop a compelling end user experience
Do not devolve to the status quo by avoiding uphill battles
Our clients & employees must consistently be able to find what they're looking for
More access and greater freedom without compromising control
Maintain a 360 degree view of the process ensuring that all parties afected are taken into
account
8. Take steps to mitigate major failure points common for deployments:
8.1.Low User Adoption
8.2.Low Supplier Enablement
8.3.Poor program management
8.4.Inefectively mapping the process before deploying the tool
9. After deployment, we will continually focus on improving process and system operations

Customer Success Metrics (This should be updated after Success

Workshop)
The Customer Success Metrics as agreed with <COMPANY NAME> are as follows:
-1. End User Adoption of XXX% within XX months of Go-Live
-2. Saving under management of XXX% within XX months of Go-Live
-3. Approval Times for Requisition to achieve a Benchmark of XX Days
-4. Maverick spend reduced from XXX% to XXX%

Coupa Software
Business Blueprint: Client Name

Page 7 of 40
Company Confidential

Blueprint
Confidential

Definitions
Approval Chain
Approval Groups

Assumed Receipt
or Two Way Match
Buyer: Coupa
Catalog
Casual User
COA
Commodity Code
CSN or Coupa
Supplier Network
Draft Supplier
End User or Client
Free Form
FTE
Goods Receipt
(GR)
High Touch
Supplier
IM
Internally Hosted
Catalog
iRequest
Low Touch

These are approval flows that provide business approval to an order,

invoice or expense.
Groups of individuals that simultaneously receive the notification for a
purchase requisition; any one of the individuals within the Approval
Group is able to approve or reject the requisition upon which time the
requisition moves to the next action within the approval chain
A PO process wherein two documents are required in order to process a
payment: the Purchase Order and the Invoice.
Role in the Coupa system that allows for unblocking of requisitions and
other abilities within Coupa; referred to in this documentation as Coupa
Buyer
Group of items available by a supplier. Catalogs can either by internally
hosted or punch out (externally hosted)
Coupa requestor that is only using Coupa between 5 and 10 times per
fiscal year
Chart of Accounts
This is a code similar to the General Ledger code in other systems
Coupa Supplier Network: The CSN is the network that Supplier are
invited to and maintain master data in the system. They can also view
billing and payment details.
The Draft Supplier functionality in Coupa allows an end user to request
a Supplier directly in the system without a web-form. This functionality
is out of scope for this project
Role in Coupa used to perform basic requisitioning.
Purchase requisition or shopping cart where the user provides the
item/service information and supplier rather than selecting an item from
a catalog or punch out
Full Time Employees
A Goods Receipt is a document issued to acknowledge the receipt of the
items listed in it. In other words, it is a document used to register in
Coupa the specifics of items physically received at a dock, desk or
through small parcel
A supplier that will require a lot of time to enable communications. This
moniker is usually reserved for suppliers that will connect using EDI or
cXML.
Coupa Implementation Manager
Items that are uploaded into the Coupa system by a system
administrator. These items are maintained by the customer.
Option in Coupa wherein an end user can punch out to an external site
without a contract.
A supplier that will require little time to enable for communication. This

Coupa Software
Business Blueprint: Client Name

Page 8 of 40
Company Confidential

Blueprint
Confidential
Supplier
OHB
Order lists
PO
Punch Out Catalog
Purchasing
Channels
Preferred Supplier
Requestor
Requisition
Self-Approval
Shopping Cart
Source to Pay
Supplier
Enablement
Tags
Three Way Match
Ultimate Approver
Web-form
WH

moniker is usually reserved for suppliers that will connect using email or
fax.
On Hand Balance is the inventory level in the Inventory system that can
be consumed.
Groups of commonly ordered items available to an end user to be able
to immediately order. These lists are created and maintained by users
with power user access and above.
Purchase Order is an approved Requisition that is communicated to a
Supplier.
Externally hosted catalogs maintained by their associated Supplier. The
items in these catalogs are not maintained by the client.
4 vehicles through which data will flow through the Coupa system. The
4 purchasing channels available in Coupa are 3 way match, Assumed
Receipt, Evaluated Receipt and Service Purchase Order.
List of suppliers designated by Sourcing as preferred suppliers and
flagged as such in Coupa
Synonymous with end user or Client in the Coupa system
Synonymous with Shopping Cart. Indicates the purchase requisition
before it is routed for approval to be a purchase order.
Limit upon which an end client or user can order to without gaining a
supervisor or project managers approval
Synonymous with Requisition. Indicates the purchase requisition before
it is routed for approval
The transactional flow of data for a user to request and receive
goods/services and Suppliers to receive payment
A descriptor for the list of activities that need to occur in order for a
supplier to do business via Coupa; an enabled supplier regardless of
volume will receive POs from Coupa
Descriptive words placed on a material to allow for easier searching by
the end user. These are uploaded to the appropriate material or item
when the item is created or an existing item is maintained.
A PO process wherein three separate documents are required in order to
process a payment: Purchase Order, Goods Receipt and Invoice.
A role used to identify errors in the approval system and adjust approval
settings to repair.
Pre-made forms for end users to fill out if they require anything other
than the standard catalog items. Web forms can be used for free-form
Purchase Order or any other request from the Sourcing organization.
Warehouse is the term used to describe the location for storing
Inventory when the Inventory module is implemented.

Coupa Software
Business Blueprint: Client Name

Page 9 of 40
Company Confidential

Blueprint
Confidential

1. Coupa Overview & System Configuration Options

<COMPANY NAME> purchased the highlighted modules below from Coupa Software. These will
be implemented to work in tandem with our IT infrastructure. The full list of modules is as
follows:
-

Coupa
Coupa
Coupa
Coupa
Coupa
Coupa

Contracts
Sourcing
Procurement
Invoicing
Inventory
Expenses

At contract signature, the following standard applications are available via the Coupa Platform in
addition to the module list above. They are as a standard once you use Coupa:
-

Coupa
Coupa
Coupa
Coupa
Coupa

Budgets
Catalogs
Suppliers (via the Coupa Supplier Network)
Reports
Mobile (including a mobile integration option)

Additional Integration Options:

-

SSO Integration (up to LDAP or SAML 2.0 Integration)

Integration objects with ERP system

Coupa Software
Business Blueprint: Client Name

Page 10 of 40
Company Confidential

Blueprint
Confidential
-

Supplier Enablement option

Environments that are currently available for <COMPANY NAME> are as follows:
-

Test
Production

This Section is meant to be a review of all system configuration options for Admin personnel
configuring the Coupa system for <COMPANY NAME> requirements. It contains the simple yes/no
or checked/unchecked settings that are required for the <COMPANY NAME> configuration with
links to the corresponding business process covered in later sections of this document.

2. Global Settings in Coupa

The purpose of this section is to detail the global level settings that will govern and determine
the use of the Coupa system. These setting are a reflection of the configurations made in your
ERP system and any change to that system will require a change in the Coupa system in order to
maintain system use.

2.1.

Company Code Configuration

Area
Compan
y
Compan
y
Compan
y

Coupa System Option

Company name

Setting
Checked/Unchecked

Company Logo

Checked/Unchecked

Default Time Zone

Checked/Unchecked

Reasoning

Address - Configuration
Area
Compan
y

Coupa System Option

Company Address

Setting
Checked/Unchecked

Reasoning

Accounting - Configuration
- Note: Customer Best Practices
Area
Coupa System
COA
Chart of Accounts
COA

There is support for up to 20 segments but for

optimal performance then look to have 5.

Coupa Software
Business Blueprint: Client Name

Recommendation
One Chart of Accounts Per
Legal Entity
Ensure
fastest
processing
times
Page 11 of 40
Company Confidential

Blueprint
Confidential
Outside of 5 then you should look to default in
values where possible
COA
50 unique or lower is the optimal level for
performance
COA
Ensure users are restricted to the COA that
applies to them
COA
Static Accounting (or lookup) is best to be used
up to 500,000 Accounts and after that then you
should
look
to
use
defined
Dynamic
Accounting.
The configurations in Coupa are as follows:
Area
COA

2.2.

Coupa System Option

Chart of Accounts

Ensure optimal processing

Ensure
times
Ensure
speeds

Setting
Checked/Unchecked

fastest

processing

optimal

processing

Reasoning

Security Controls
Security Controls Customer Best Practices

Area
All

All

All

All

Action
Leverage Coupa's standard roles wherever
possible. These are detailed in Section 10.4.
Use as few custom roles as possible without
compromising your business processes.
For adding additional permissions, add both a
system role and the custom role to assigned
users so that you can leverage Coupa's
updates to the system role.
Set up a non-admin role that has all permission
enabled to help determine which actions are
admin only and cannot be assigned to custom
roles.
Ensure users are restricted to the COA that
applies to them

Reasoning
Reduce testing requirements
for a Go-Live and all future
system upgrades.
Allows you to utilize the
Coupa system roles but also
meet business requirements.
Best practice when dealing
with admin roles.

Ensure
times

fastest

processing

Security Controls - Configuration

Area
Security
Controls
Security
Controls
Security
Controls

Security
Controls

Coupa System Option

Session expiration timeout

Setting
X hours

Reasoning

Log in using SAML

Checked/Unchecked

User
authentication
via SAML

Coupa Credentials: Choose the

minimum password length:
- 5 characters
- 8 characters
Coupa Credentials: Should it be
required that passwords contain a

Coupa Software
Business Blueprint: Client Name

Page 12 of 40
Company Confidential

Blueprint
Confidential

Security
Controls

Security
Controls

Security
Controls

Security
Controls

mix
of
alpha
and
numeric
characters?
Coupa Credentials: When should
users be locked out of the system?
- Never
- After 3 failed password attempts
- After 10 failed password attempts
Coupa Credentials: What should the
lockout period be if a user is locked
out for failed password attempts?
- None
- 15 minutes
- 60 minutes
- Until the Administrator resets the
password
Coupa Credentials: How often
should users be required to choose
a new password?
- Never
- Every 30 days
- Every 60 days
- Every 120 days
Coupa Credentials: When a user
chooses a new password, it:
- must be diferent from the last 3
passwords
- must be diferent from the last 8
passwords
- does not matter if it is the same
as a previous passwords

Custom Roles - Configuration

Area
Security
Controls
Security
Controls

2.3.

Coupa System Option

Session expiration timeout

Setting
X hours

Reasoning

Log in using SAML

Checked/Unchecked

User
authentication
via SAML

Dashboard Controls
Dashboard Controls Customer Best Practices

Area
Process
Savings

Coupa System Option

Your savings per purchase order

Coupa Software
Business Blueprint: Client Name

Setting
X dollars

Reasoning
Look to provide a
value for this setting
that meets company
Page 13 of 40
Company Confidential

Blueprint
Confidential
needs
Process
Savings
Process
Savings
Preferred
Supplier
Savings

Your savings per invoice (entered

by your company)
Your savings per invoice (entered
by supplier)
Apply current savings level for all
past purchase orders

X dollars
X dollars
Radio button

Look to provide a
value for this setting
that meets company
needs

Dashboard Controls Configuration

Area
Process
Savings
Process
Savings
Process
Savings
Preferred
Supplier
Savings

2.4.

Coupa System Option

Your savings per purchase order

Setting
X dollars

Your savings per invoice (entered

by your company)
Your savings per invoice (entered
by supplier)
Apply current savings level for all
past purchase orders

X dollars

Reasoning

X dollars
Radio button

Content Groups
Content Groups Customer Best Practices

Area
View

Action
In the initial implementation, allow broad
access within the beginning and then look to
narrow it.

Reasoning
No restriction in the initial GoLive so system operate at an
optimal level

Content Group - Configuration

Area
Content
Groups

2.5.

Coupa System Option

Allow users to limit content they
see to one content group at a time

Setting
Checked/Unchecked

Reasoning

Budgets

Creating a mindset of responsible spending starts with end users knowing their budget and how
their individual spend afects that budget. Current industry best practice is to spend 95
100% of the allocated budget.

Budget Customer Best Practices

Area
View

Action
Get accurate budgets integrated
automatically with Coupa to ensure
that users have that visibility

Coupa Software
Business Blueprint: Client Name

Setting

Reasoning
Make people
smarter!

spend

Page 14 of 40
Company Confidential

Blueprint
Confidential

Budget - Configuration
Area
Budget
Periods
Budget
Periods
Budget
Periods

2.6.

Coupa System Option

Allow Users to select budget period
for requisitions
Allow users to select budget period
for expenses
Show detailed budget information
(i.e. exact overrun amount) on
budget overrun/underrun messages

Setting
Checked/Unchecked

Reasoning

Checked/Unchecked
Checked/Unchecked

Commodities Codes
Commodities Codes Customer Best Practices

Area
COA

Action
Extract COA from legacy system
and consolidate it. Determine which
GL will be used by Coupa to narrow
list
Give all Coupa used GLs a name
that is easy to understand

GL

Setting

Reasoning
Reduce
complexity

system

Allow
system
and
actions to be easily
understood by users

Commodities Codes Configuration

Area
Commodi
ties

2.7.

Coupa System Option

Enforce leaf node commodity
selection (only pick base levels in
the tree)

Setting
Checked/Unchecked

Reasoning

Commodity Classification Engine

Commodity Classification Engine Customer Best Practices

The commodity classification engine can be used to map a description keyword to a chosen
commodity mapping so they end user does not have to select a valid option.
Area
Commodi
ty
Classifica
tion
Engine

Action
Map as many description keywords
as possible as will aid user
experience during system usuage

Setting

Reasoning
Aid user adoption

Commodity Classification Engine - Configuration

Area
Commodi

Coupa System Option

Use classification engine as much

Coupa Software
Business Blueprint: Client Name

Setting
Checked/Unchecked

Reasoning
Page 15 of 40
Company Confidential

Blueprint
Confidential
ty
Classifica
tion
Engine

2.8.

as possible

Contracts

Contracts in the Coupa system are not legal documents but rather a title for a container thats
used to list out a series of materials and items tied to a particular supplier. Coupa contracts are
used to setup special settings such as pricing, billing order windows and specific item pricing.
Coupa customer best practice is not to purchase material from a Coupa supplier without a
contract. In order to facilitate this best practice, you can turn on the functionality that requires a
Coupa buyer review for all material that is purchased of of Coupa contract. In order to setup a
contract, an administrator or buyer will populate the contract with the following information:
Supplier
Contract
Name
Contract
Number

Status
Start Date

Expires
Owner
Supplier
Account
Number
Currency

Legal
Agreements
Attachments

Savings %

Must choose a supplier with an active account in Coupa

All contract names must include descriptive and meaningful titles. The basic
naming convention for Coupa contracts will be the Supplier name, ERP Number
and content group able to view the contract or short description of the contract.
Although Contract numbers will not need to be passed over to ERP in an
integration at this time, future use of the contract field may allow for end users
to be able to track spend against a specific contract number (which is auto
assigned)
Contracts can either be in draft status or published. A buyer or administrator
must publish the contract in order for it to be efective
If using the spend options within the contract module, Coupa will track all spend
against the contract starting from this date. Please note that backdating this
start date will not include all previous transactions with the exception of any
transactions that are still pending approval
Contract expiration alerts rely on this field to send out warnings; one the
contract reaches that expiration date, Coupa will deactivate it.
Best practice will be for Contract owners to be set to automatically receive
contract alerts
This field should be left blank

All default currencies for a supplier should come from the Supplier master data.
When setting up a contract, do not change the currency from the standard set
by the supplier record to prevent issues at invoicing.
Although Coupa will allow uploads of any legal agreements, Coupa is not the
official repository. It is only ofered to end users as an option
Any pricing agreements or other attachments can and should be uploaded into
the contract module for reference. This can be in the form of files, URLs or even
plain text.
This field is left at the discretion of the category owner

Coupa Software
Business Blueprint: Client Name

Page 16 of 40
Company Confidential

Blueprint
Confidential
Minimum and
Maximum
Spends

Certain contracts will provide discounts based on the amount of spend made
against that contract. <COMPANY NAME> will use the minimum and maximum
fields to trigger alerts as to the position of spend against a contract in order to
obtain rebates, a renegotiated rate or other Sourcing decisions

Contracts Customer Best Practices and Configuration

-

Note: Customer Best Practices mean having a contract per item bought per
Supplier: This is enabled by having a Start Date and not having an end date.
Note: If a good or service is purchased from a supplier that is not on a Coupa contract
then the requisition must be approved by a buyer before a Purchase Order is released to a
Supplier.

Area
Contract
Contract
Contract

2.9.

Coupa System Option

Default on Unbacked Line
Supplier can Invoice Directly
Coupa Invoice used against
Contract

Setting
Checked/Unchecked
Checked/Unchecked
N/A

Reasoning
Not a configuration
option so just need to
document a decision

Ask an Expert

Coupa has a feature called Ask an Expert which allows users to submit questions to an
assigned expert in that area. For example, you may have a category for RFQ questions and a
category for Buying Policy questions. In order to use this feature, you must set up categories and
assign an expert to answer the questions for each category.

Ask an Expert Customer Best Practices and Configuration

Area
Ask an Expert
Ask an Expert

2.10.

Coupa System
Recommending using this system
Set-up each categories that you will be
using with a user within your organization.

Reasoning
Deal with queries at source
rather than support queries

Home Page Content

Coupa allows some customization of content on the home page. Some customers use this space
for help desk support contact information, company-wide announcements, or other additional
links. Below is an example of a home page with additional links to online Coupa training and
other helpful resources:

Coupa Software
Business Blueprint: Client Name

Page 17 of 40
Company Confidential

Blueprint
Confidential

Home Page
Configuration

Content

Customer

Best

Practices

and

Home page content allows the user to control the information thats available via the home page.
Area
Home
Content

Page

Coupa System
Links to Training Videos, Frequently Asked
Questions and links.

Reasoning
Ease of Access to Users to
Support and Training

3. Sourcing
With Coupa Sourcing, the focus is on self-service to enable you to create sourcing events. Coupa
self-service sourcing makes it easy for others in procurement to host and actively participate in
eBay-like jousting between suppliers competing for your business. You are able to import
information from the winning bid right into Coupa Procurement to create catalogs and contracts
so you can easily turn negotiated savings into realized savings.

3.1.

Sourcing - Customer Best Practices

Area
Sourcing Event
Sourcing Event

3.2.

Sourcing
Sourcing
Sourcing

Coupa System Option

Suppliers need to login to provide
repsonses
Suppliers are allowed multiple
Sourcing responses
Events have sealed response by
default
Sealed bids are editable on an
event level

Setting
Checked/Unchecked

Reasoning

Checked/Unchecked
Checked/Unchecked
Checked/Unchecked

Sourcing Events

Area
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing

3.4.

Reasoning
Ensure optimal processing
Ensure optimal processing

Sourcing Settings

Area
Sourcing

3.3.

Coupa System
Events with up to 20 Suppliers is optimal
Events with up to 450 lines is optimal

Coupa System Option

Requests for Information
Requests for Quotes
Requests for Proposals
Opportunities
Opportunity Triggers

Setting
Checked/Unchecked
Checked/Unchecked
Checked/Unchecked

Reasoning

Price Comparisons
Price Comparisons Customer Best Practices

Area
Price
Comparis

Coupa System Option

Allow online price comparisons

Coupa Software
Business Blueprint: Client Name

Setting
Checked/Unchecked

Reasoning

Page 18 of 40
Company Confidential

Blueprint
Confidential
ons

Price Comparisons Configurations

Area
Price
Comparis
ons

3.5.

Coupa System Option

Allow online price comparisons

Setting
Checked/Unchecked

Reasoning

Sourcing Approvals

All Sourcing events that occur will be approved by the business when a Requisition is used for
the good or services. Coupa best practice involves using the Watcher function to track and
monitor Sourcing events.

4. Procurement
Coupa focuses on driving its customers to industry best practice across the Procurement
function. Part of this drive includes moving the organization towards electronic communication
with its Suppliers. They seek to communicate electronically Purchase Orders to Suppliers.
Industry standards is currently set at 80% for electronic PO communication. This will
help in the reduction in the cost of processing a PO which is set at $10 to $15 dollars
per PO by Industry Standards.

4.1.

Procurement Process
Procurement - Data Process Flows

Procurement Customer Best Practices

Area
Requisition

PO

Coupa System
Average Requisition has three lines but for
optimal performance then do not go above 20
lines
Email communication of Order to Supplier

Receipt

Enable automatic receipts

Coupa Software
Business Blueprint: Client Name

Reasoning
Larger requisition can be
accommodated but keep to
limit for optimal processing
Speed of receipt of order and
supply of goods
Reduces manual intervention
by the team
Page 19 of 40
Company Confidential

Blueprint
Confidential
Custom
Fields

5 fields per object is the optimal level. Anything

over 20 is not supported

Optimize system performance

Procurement - Configuration
Area
Requisiti
on
Requisiti
on

Coupa System Option

Route requisitions to buyer if
supplier is in draft status
Route requisitions to buyer if no
contract is specified

Setting
Checked/Unchecked

Requisiti
on
PO

Enable requisition history

Checked/Unchecked

Emailed purchase orders should

include the order document as an
attachment
Automatically close purchase order
after X days of inactivity
Automatically close a fully invoiced
purchase order after X days
Prevent requesters from making
receipts for suppliers with 2-way
match
Users can request changes to their
POs

Checked/Unchecked

PO

Buyers must review all purchase

order change requests

Checked/Unchecked

PO

Show purchase orders created or

requested by the user in My Spend
History

Checked/Unchecked

Receipt

Only allow quick receiving multiple

PO lines if all lines belong to the
same PO

Checked/Unchecked

Notificati
ons

Send notification back to user if the

system cannot process an approval
notification response via email
Send notifications to requester
when un-received orders are X
days past due
Send notifications to requester to
gather supplier reviews X days

Checked/Unchecked

PO
PO
PO

PO

Notificati
ons
Notificati
ons

Coupa Software
Business Blueprint: Client Name

Checked/Unchecked

Checked/Unchecked
X days
Checked/Unchecked
X days
Checked/Unchecked

Checked/Unchecked

X days

Reasoning
Not enabling draft
suppliers in Coupa
Govern Coupa with
contracts
and
not
directly to supplier.
Want audit history on
requisitions
We are not using a fax
server
Unchecked due to
Blanket POs
No invoicing in Coupa
Needs
to
be
unchecked for Invoice
Pass through to work
Users
have
the
responsibility to make
their own changes
End users will be able
to make their own
changes at project
launch
End users will need to
be able to see or
replicate
past
purchase orders
End users will need to
be able to quickly
place GRs and SRs
against a Purchase
Order

This will not work

unless
doing
full
Invoicing in Coupa

X days
Page 20 of 40
Company Confidential

Blueprint
Confidential
iRequest

after order
Enable iRequest links on the home
page

Online
Help Link

None/Use
Coupas
help/Custom URL

online

Checked/Unchecked

Dont plan on using

iRequest
to
allow
users to order from
anywhere

<- Choose

Requisition to Invoice - Key Performance Indicators

Area
Requisit
ion
PO

Receipt

4.2.
There
-

Goal
Approval of Requisition in two
business days
All Electronic Communication of
Orders to Supplier and no manual
paper
Enable automatic receipts

Measure
48 hours for Approval

Reasoning
Reduces complexity

100%
Electronic
Communciation

Speed of receipt of
order and supply of
goods
Reduces
manual
intervention by the
team

50%
Receipts

Automatic

Purchase Channels / PO Types

are four ways for Coupa to process a purchase. They are:
Three way match,
Assumed Receipt (Two way match)
Evaluated Receipt Settlement (ERS)
Blanket Purchase Order

Purchasing Channels Configuration

Area
Type

4.3.

Action
Review current business processes
and look to replicate in Coupa

Setting

Reasoning
Reduce complexity

Procurement Approvals

Coupa look to process Requisition quicker to enable organization meet Industry benchmarks. The
current benchmark for Requisition approvals in industry are 1 days. Quicker approvals
allows the Procurement department to focus on strategic activities. There are a number of
approval types available in Coupa:
- Management Hierarchy: A requesters manager approves the requisition
- Custom Approval Chain: An element of the requisition (i.e. GL, cost center, supplier, etc.)
drives
- Group Approvals: Only one member of a group of people needs to approve
- Ad-Hoc Approvals: Enable the requester to add ad-hoc approvals to the chain

Approvals Customer Best Practices

Area
Requisition

Coupa System
Enable self-approval limits to an amount that

Coupa Software
Business Blueprint: Client Name

Reasoning
Empowers users and reduces
Page 21 of 40
Company Confidential

Blueprint
Confidential
All
All

fits with business policy

Up to 4 approvers is the optimal level for
performance
Up to 500 approval chains is optimal in a Coupa
deployment

approval time

Ensure
speed

optimal

processing

Approvals Configuration
Area
Approva
l
Prefere
nce
Approva
l
Prefere
nce
Approva
l
Prefere
nce
Approva
l
Prefere
nce
Approva
l
Prefere
nce
Approva
l
Prefere
nce
Approva
l
Prefere
nce
Approva
l
Remind
ers
Approva
l
Remind
ers
Excepti

Coupa System Option

Build approval path based
management hierarchy

on

Setting
Checked/Unchecked

Build approval path based on

original requesters' management
hierarchies

Checked/Unchecked

Build approval
approval chains

Checked/Unchecked

path

based

on

Allow self-approvals

Checked/Unchecked

Notify manager on self-approval

Checked/Unchecked

Add On Behalf Of user as first

approver if requisition is within that
user's self-approval limit

Checked/Unchecked

Enable adding
watchers

and

Checked/Unchecked

Send email reminder to approver

every X hours

Checked/Unchecked
XX Hours

Automatically escalate to the next

approver in chain after X hours of
inaction

Checked/Unchecked
XX Hours

Requisition Ultimate Approver

Person

Coupa Software
Business Blueprint: Client Name

approvers

Reasoning

Page 22 of 40
Company Confidential

Blueprint
Confidential
on
Handlin
g

Approval Key Performance Indicators

Area
Requisit
ion
PO

Receipt

4.4.

Goal
Approval of Requisition in two
business days
All Electronic Communication of
Orders to Supplier and no manual
paper
Enable automatic receipts

Measure
48 hours for Approval

Reasoning
Reduces complexity

100%
Electronic
Communciation

Speed of receipt of
order and supply of
goods
Reduces manual tasks

50%
Receipts

Automatic

Order Lists
Order Lists Customer Best Practices

Area
View

Action
In the initial implementation, allow
broad access within the beginning
and then look to narrow it.

Setting

Reasoning
No restriction in the
initial
Go-Live
so
system operate at an
optimal level

Coupa System Option

Disable setting par levels

Setting
Checked/Unchecked

Reasoning

Disable suggested order amounts

Checked/Unchecked

Disable adjustment sliders

Checked/Unchecked

Order Lists - Configuration

Area
Order
Lists
Order
Lists
Order
Lists
Order
Lists
Order
Lists

4.5.

Minimum value for slider (relative

%)
Maximum value for slider (relative
%)

Advance Shipping Notices

Advance Ship Notices Customer Best Practices

Area
Advanc
ed Ship
Notices

Action
The use of the function is very
useful but need to ensure Supplier
can provide it to the business
requesting it.

Coupa Software
Business Blueprint: Client Name

Setting

Reasoning

Page 23 of 40
Company Confidential

Blueprint
Confidential

Advance Ship Notices - Configuration

Area
Advanc
ed Ship
Notices

4.6.

Coupa System Option

Allow multiple receipts per Advance
Ship Notice

Setting
Checked/Unchecked

Reasoning

Shipping Terms
Shipping Terms Customer Best Practices

Area
Shippin
g Terms

Action
Mapped all Shipping Terms from
ERP system across to Coupa.
Standardize as much as possible
before mapping

Setting

Reasoning
Reduce complexity

Shipping Terms - Configuration

Area
Shippin
g Terms

Coupa System Option

Detail various terms here

Setting
Checked/Unchecked

Reasoning

5. Invoicing
Coupa focuses on driving its customers to lower its processing costs per Invoice. Industry
standards set this cost at 4% of the Invoice value. To lower this cost and meet industry
standards, it requires moving those Invoices to electronic format where less manual intervention
is required. 80% of Invoices are now processed electronically and that is the benchmark
that each organization should aim for.

Coupa Software
Business Blueprint: Client Name

Page 24 of 40
Company Confidential

Blueprint
Confidential

Invoicing - Data Process Flows: Assumes a 3-way match Supplier

5.1.

Invoicing Global Configuration

- Note: Customer Best Practices

Area
Coupa System
Invoice
Auto approval of Invoice
All
All
Custom
Fields

Reasoning
No restriction on the supply of
goods from the Supplier

Up to 4 approvers is the optimal level for

performance
Up to 500 approval chains is optimal in a Coupa
deployment
5 field per object is optimal but anything over
20 is not supported

Ensure optimal processing

speed
Optimize system performance

Requisition to Invoice - Configuration

Area
Invoice
Invoice

Invoice
Invoice
Invoice

Coupa System Option

Show invoices in My Spend History
Require the calculated total to
match a control total for invoices
that AP users create manually
Enable document locking
Enable Booking Hold
Allow
Invoice
Download
with
Authorization

Setting
Checked/Unchecked
Checked/Unchecked

Reasoning
Not doing Invoicing
Not doing Invoicing

Checked/Unchecked
Checked/Unchecked
Checked/Unchecked

Not doing Invoicing

Not doing Invoicing
Not doing Invoicing

Requisition to Invoice - Key Performance Indicators

Area

Goal

Coupa Software
Business Blueprint: Client Name

Measure

Reasoning
Page 25 of 40
Company Confidential

Blueprint
Confidential
Invoice

5.2.

Auto approval of Invoice

100%
Approval

Invoice

No restriction on the
supply of goods from
the Supplier

Invoicing Tolerances
Invoicing Tolerances Customer Best Practices

Area
Invoicing
Tolerances

Action
Review business invoice tolerances that are
currently in place and look to widen them for
the initial Go-Live

Reasoning
Tolerances are easily changed
to
so
remove
potential
bottlenecks at Go-Live.

Invoicing Tolerances Configuration

Area
Request
ers Self
Service
Receivin
g
Request
ers Self
Service
Receivin
g
Request
ers Self
Service
Receivin
g
Request
ers Self
Service
Receivin
g
Centrali
zed
Receivin
g
Centrali
zed
Receivin
g
Centrali
zed
Receivin

Coupa System Option

Quantity
cannot
exceed
the
ordered quantity by more than

Setting
X%

Amount
cannot
exceed
the
ordered amount by more than

X%

Quantity
cannot
exceed
the
currently invoiced quantity by
more than

Blank

Amount
cannot
exceed
the
currently invoiced amount by
more than

Blank

Quantity
cannot
exceed
the
ordered quantity by more than

X%

Amount
cannot
exceed
the
ordered amount by more than

X%

Quantity
cannot
exceed
the
currently invoiced quantity by
more than

Blank

Coupa Software
Business Blueprint: Client Name

Reasoning

Page 26 of 40
Company Confidential

Blueprint
Confidential
g
Centrali
zed
Receivin
g

5.3.

Amount
cannot
exceed
the
currently invoiced amount by
more than

Blank

Invoicing Approvals

Coupa look to process Invoices quicker to enable organization meet Industry benchmarks. The
current benchmark for Invoice approvals in industry are 3 days. Quicker approvals allows
the AP department to focus on strategic activities and capture early pay discounts. Current
industry standards set that 15 to 20% of your spend should capture these discounts.
- Management Hierarchy: A requesters manager approves the requisition
- Custom Approval Chain: An element of the requisition (i.e. GL, cost center, supplier, etc.)
drives
- Group Approvals: Only one member of a group of people needs to approve
- Ad-Hoc Approvals: Enable the requester to add ad-hoc approvals to the chain

Invoicing Approvals Customer Best Practice

Area
Invoice

Coupa System
Auto approval of Invoice

Reasoning
Obtain
early
discounts

payment

Invoice Approvals Configuration

Area
Approva
l
Prefere
nce
Excepti
on
Handlin
g
Approva
l
Prefere
nce

Coupa System Option

Build approval path based
management hierarchy

on

Setting
Checked/Unchecked

Invoices Ultimate Approver

Person

Route to approval without showing

Invoice Checks Failed

Checked/Unchecked

Reasoning
We
want
to
management
approvals

use

Invoice Approvals Key Performance Indicators

Area
Invoice

Goal
Auto approval of Invoice

Coupa Software
Business Blueprint: Client Name

Measure
100%
Approval

Invoice

Reasoning
No restriction on the
supply of goods from
the Supplier
Page 27 of 40
Company Confidential

Blueprint
Confidential

5.4.

Payment Terms
Payment Terms Customer Best Practices

Area
Shippin
g Terms

Action
Mapped all Payment Terms from
ERP system across to Coupa. Look
to standardize before.

Setting

Reasoning
Reduce complexity

Payment Terms - Configuration

Area
Shippin
g Terms

Coupa System Option

Detail Payment Terms here

Setting
Checked/Unchecked

Reasoning

6. Inventory
6.1.

Inventory Process of Receiving

Inventory - Customer Best Practices

-

Note: Customer Best Practices: Set-up a contract for each Internal Supplier and tie it to
Content Group
Note: Look to use Automatic fulfillment where possible otherwise require Manual Approval

Area
Inventory

Action
5 field per object is optimal but anything over
20 is not supported

Coupa Software
Business Blueprint: Client Name

Reasoning
Optimize
performance

system

Page 28 of 40
Company Confidential

Blueprint
Confidential

Inventory Configurations
Area
Inventor
y
-

6.2.

Coupa System Option

Setting
Checked/Unchecked

Reasoning

Note: Once a Warehouse is in use then you cannot deactivate it.

Note: Only when a Warehouse is deactivated then it cannot receive any stock.
Note: To transfer stock between sites then you need to set-up each party as an
Internal Supplier.

Receiving Tolerances
Receiving Tolerances Customer Best Practices

Area
Receivin
g
Toleranc
es

Action
Review tolerances currently in place
and give a margin of safety to it.

Setting

Reasoning
Reduce potential for
Go-Live bottleneck.

Receiving Tolerances Configuration

Area
Request
ers Self
Service
Receivin
g
Request
ers Self
Service
Receivin
g
Request
ers Self
Service
Receivin
g
Request
ers Self
Service
Receivin
g
Centrali
zed
Receivin
g

Coupa System Option

Quantity
cannot
exceed
the
ordered quantity by more than

Setting
X%

Reasoning
Not
setting
tolerances

Amount
cannot
exceed
the
ordered amount by more than

X%

Not
setting
tolerances

Quantity
cannot
exceed
the
currently invoiced quantity by
more than

Blank

Not using Invoicing at

this time

Amount
cannot
exceed
the
currently invoiced amount by
more than

Blank

Not using Invoicing at

this time

Quantity
cannot
exceed
the
ordered quantity by more than

X%

Not
setting
tolerances

Coupa Software
Business Blueprint: Client Name

any

any

any

Page 29 of 40
Company Confidential

Blueprint
Confidential
Centrali
zed
Receivin
g
Centrali
zed
Receivin
g
Centrali
zed
Receivin
g

Amount
cannot
exceed
the
ordered amount by more than

X%

Not
setting
tolerances

any

Quantity
cannot
exceed
the
currently invoiced quantity by
more than

Blank

Not using Invoicing at

this time

Amount
cannot
exceed
the
currently invoiced amount by
more than

Blank

Not using Invoicing at

this time

7. Advanced Inventory
Advanced Inventory - Customer Best Practices
-

Note: Customer Best Practices: Set-up a contract for each Internal Supplier and tie it to
Content Group
Note: Look to use Automatic fulfillment where possible otherwise require Manual Approval
Note: Internal Supplier is associated to only one Warehouse

Advanced Inventory Configurations

Area
Inventor
y
Settings
Inventor
y
Settings
Inventor
y
Settings
Warehou
se Types
Warehou
ses
Internal
Suppliers
Internal
Suppliers
Fulfillme
nt Type
Cycle
Count
Type
Items

Coupa System Option

Base Currency

Setting

Misc Settings: Cycle counts in the

same warehouse

Checked/Unchecked

Reasoning

Adjustment Reason Codes

Create your warehouse types

Create warehouses with Aisle and
Bins
Create
internal
Supplier
per
warehouse
Warehouse

Warehouse name
Automatic/Manual

Create cycle
needed

count

intervals

if

Set up inventory item number

Coupa Software
Business Blueprint: Client Name

Page 30 of 40
Company Confidential

Blueprint
Confidential
Items
Items
Items
Items
Items

Set up Cycle Count Type if Using

Set Storage UOM per item
Set Consumption UOM per item
Allow Partial Qty with Decimals
Set appropriate internal supplier
per item

Checked/Unchecked

8. Expenses
This area of Coupa is primarily used to process spend that has not been pre-approved by the
organization. It can cover Travel and Entertainment across to company equipment. Coupa
assigns an audit score to every expense report. The score is intended to streamline workflow
and identify expense reports that are of a higher risk. Many factors are used in the audit score
algorithm, including but not limited to:
-User's audit score history of past expense reports
-Any receipts that are missing
-If lines go over the maximum value for the category
-If similar expense lines were found for that user in recent history
-User's audit score history of past expense reports

8.1.

Expenses Global Settings

Area
Expenses
Expenses
Expenses
Expenses
Custom
Fields

8.2.

Setting
Checked/Unchecked

Reasoning

Optimize
performance

system

Expense Categories

Area
Expenses
Expenses

8.3.

Coupa System Option

Show Billing fields (COA Structure)
only to Account Reviewer
Account Reviewers Occurs On
Show Exchange Rate Converter
Flagging of Expenses
5 Custom fields per object is
optimal and anything over 20 is
not supported

Coupa System Option

Detail Complete List of Expense
Categories here
Frugal Meter

Setting
Checked/Unchecked

Reasoning

Really Good function

to implement

Expense Classification Engine

Area
Expenses

Coupa System Option

Use Expense Classification Engine

Expenses

Keyword

Coupa Software
Business Blueprint: Client Name

Setting
Checked/Unchecked

Reasoning
Utilize this option as
much as possible
Utilize as much as
possible

Page 31 of 40
Company Confidential

Blueprint
Confidential

8.4.

Custom Fields

Area
Expenses

8.5.

Coupa System Option

Configurable

Setting
Checked/Unchecked

Reasoning
Restrict this as much
as possible

Credit Card Usage and Transaction Mapping

Within Coupa, Expense Management allows for integration with various Credit Card providers to
allow for a streamlined submission process.
Area
Expenses

8.6.

Coupa System Option

Credit Card Data Source

Setting
Checked/Unchecked

Reasoning
A direct link with a
Credit Card provider
allow
for
faster
expense entry

Expense Approval Chains

Within Coupa, Expense Management approval chains can be configured to match Managerial
Hierarchy (from the user record) or via custom approval chains.
Area
Expenses

Coupa System Option

Managerial
Hierarchy
Chain

Expenses

Custom Approval Chaing

Approval

Setting
Checked/Unchecked

Reasoning
Standard
require
maintenance
Require
maintenance
support

chains
less
more
and

9. Help Desk Support Process

9.1.

Coupa Support

The following users are set-up and registered to work with Coupa support for <COMPANY NAME>.
The ability to create tickets in the Coupa support system is entrusted to only them. Those users
are:
-Procurement Manager: John James
-AP Manager: Lisa Thompson
Then will look to make contact with Coupa at the following email and phone address.
-Email: support@coupa.com
-Phone: 1800-385-7830 (US)
Coupa Software
Business Blueprint: Client Name

Page 32 of 40
Company Confidential

Blueprint
Confidential

9.2.

Ask an Expert

Ask an Expert will be used for end users to be able to reach out and get help immediately for any
issues that they experience within the Coupa interface. The Ask an Expert feature will use the
same triage as the help desk with the initial request extending to the Procurement Shared
Services organization with routing to the ultimate end user using the subsequent business
process notated separately.
The Procurement Shared Services manager will be responsible for providing any updates or
changes to the Ask an Expert field to the Sourcing Operations team who are responsible for
adjusting the content on the home page.

10.
Process

Summation of Risk and Mitigating Control

Risk

Control

9. Appendix
9.1.

Purchase Order Layout

There is an ability to customize the layout of a PO based on the Chart of Accounts

-Chart of Accounts 1:

Coupa Software
Business Blueprint: Client Name

Page 33 of 40
Company Confidential

Blueprint
Confidential

9.2.

Chart of Accounts

The Chart of Accounts will be created and maintained in ERP system and sent to Coupa for user
entry. Chart of Accounts is tied to a billing address and a single Chart of Accounts can only have
a single billing address. It does allow for multiple ship to addresses. The Chart of Accounts will
be:

Segment

Required
(Dynamic
Only)

Coupa Software
Business Blueprint: Client Name

Defaults from
Object

Defaults from
Field

List Defined In
(Dynamic Only)
Page 34 of 40
Company Confidential

Blueprint
Confidential

9.3.

Coupa Content Groups

Custom Fields that were required for the implementation on a per Object basis:

Name

9.4.

Description

Notes

Account Security Settings

Custom Fields that were required for the implementation on a per Object basis:

Name

Description

Notes

9.1. Coupa Custom Fields

Custom Fields that were required for the implementation on a per Object basis:

Field

Field Type

Coupa Software
Business Blueprint: Client Name

Object

Default Field
From

Business
Reason

Page 35 of 40
Company Confidential

Blueprint
Confidential

9.1.

User Defaults and Authentication

Field

Value

Department
Chart of Accounts
Next Approver
Requisition approval limit
Requisition self-approval limit
Authentication Method
Session Expiration Timeout
Minimum Password Length
Lockout Threshold
Lockout Period
Password Expiration
Password History

9.2.

Coupa Security Roles

Security groups will be created for each of the below roles and be brought in as a part of User
integration. The user role will be defaulted for every user so we will not create a group for this
role.

Role

Granted To

Notes / Description

Admin
User
Buyer

Coupa Software
Business Blueprint: Client Name

Page 36 of 40
Company Confidential

Blueprint
Confidential
Accounts Payable
Central Receiving
Accounting Supervisor
Edit Requisition as Approver
Inventory Manager
Edit Expense Report as Auditor
Supplier
Dashboard

9.3.

Coupa Custom Roles

Roles that were created to capture a specific user groups are listed below:

Role

9.4.

Granted To

Notes / Description

Approval Limits and Workflow

The following approval chains are listed below:

Name

Coupa Software
Business Blueprint: Client Name

Priority

Value Range

Type

Page 37 of 40
Company Confidential

Blueprint
Confidential

9.5.

Integrations Inbound

Object

Target

Format

Frequency

Users

Coupa

sFTP / API

Once daily /
Weekly / Monthly

Suppliers

Coupa

Accounts

Coupa

Account Validation
Rules

Coupa

Approval Chains

Coupa

Requisitions

Coupa

Invoices

Coupa

Company Addresses

Coupa

Remit to Addresses

Coupa

Contracts

Coupa

Budget Lines

Coupa

Invoice Payments

Coupa

Lookup Values

Coupa

Items

Coupa

Expense Payment

Coupa

Exchange Rates

Coupa

Other

Coupa

Format

Frequency

9.6.

Source

Integrations - Outbound

Object
Coupa Software
Business Blueprint: Client Name

Source

Target

Page 38 of 40
Company Confidential

Blueprint
Confidential

Approved Invoices

Coupa

sFTP / API

Purchase Orders

Coupa

API

Requisitions

Coupa

API

Purchase Order
Revisions

Coupa

API

9.7.

Once daily /
Weekly / Monthly

Data Volumes

Object

Initial
Volume

Frequency of
Update

Format
(initial/ongoing)

Users

1000

Daily

API

Delta Volume

Suppliers
Accounts
Account Validation
Rules
Approval Chains
Requisitions
POs

Coupa Software
Business Blueprint: Client Name

Page 39 of 40
Company Confidential

Blueprint
Confidential

Invoices
Company Addresses
Remit to Addresses
Contracts
Budget Lines
Invoice Payments
Lookup Values
Items
Expense Payment
Exchange Rates

Coupa Software
Business Blueprint: Client Name

Page 40 of 40
Company Confidential