Blueprint Confidential
Configuration Blueprint Document
Revision HistoryVersion HistoryDate of RevisionAuthorComments
1.0October 1, 2014 Initial Draft
Project Team
TitleCompany NameCoupa
Project Owner/ Sponsor:
Project Manager:
Implementation Manager:
Business Project Lead:
Technical Project Lead:
Authorizers for Sign-Off
RoleNameApproval TypeSignatureDate
Peer Review / Sign-off
Distribution Team (In Addition to Authorizers)
RoleName
Table of ContentsExecutive Summary6Customer Success Metrics (This should be updated after Success Workshop)7Definitions81.Coupa Overview & System Configuration Options102.Global Settings in Coupa112.1.Company Code Configuration11Address - Configuration11Accounting - Configuration112.2.Security Controls11Security Controls Customer Best Practices11Security Controls - Configuration12Custom Roles - Configuration122.3.Dashboard Controls13Dashboard Controls Customer Best Practices13Dashboard Controls Configuration132.4.Content Groups13Content Groups Customer Best Practices13Content Group - Configuration132.5.Budgets13Budget Customer Best Practices13Budget - Configuration142.6.Commodities Codes14Commodities Codes Customer Best Practices14Commodities Codes Configuration142.7.Commodity Classification Engine14Commodity Classification Engine Customer Best Practices14Commodity Classification Engine - Configuration142.8.Contracts15Contracts Customer Best Practices and Configuration152.9.Ask an Expert16Ask an Expert Customer Best Practices and Configuration162.10.Home Page Content16Home Page Content Customer Best Practices and Configuration163.Sourcing163.1.Sourcing - Customer Best Practices163.2.Sourcing Settings173.3.Sourcing Events173.4.Price Comparisons17Price Comparisons Customer Best Practices17Price Comparisons Configurations173.5.Sourcing Approvals174.Procurement174.1.Procurement Process18Procurement - Data Process Flows18Procurement Customer Best Practices18Procurement - Configuration18Requisition to Invoice - Key Performance Indicators194.2.Purchase Channels / PO Types19Purchasing Channels Configuration194.3.Procurement Approvals20Approvals Customer Best Practices20Approvals Configuration20Approval Key Performance Indicators204.4.Order Lists21Order Lists Customer Best Practices21Order Lists - Configuration214.5.Advance Shipping Notices21Advance Ship Notices Customer Best Practices21Advance Ship Notices - Configuration214.6.Shipping Terms21Shipping Terms Customer Best Practices21Shipping Terms - Configuration215.Invoicing22Invoicing - Data Process Flows: Assumes a 3-way match Supplier225.1.Invoicing Global Configuration22Requisition to Invoice - Configuration22Requisition to Invoice - Key Performance Indicators235.2.Invoicing Tolerances23Invoicing Tolerances Customer Best Practices23Invoicing Tolerances Configuration235.3.Invoicing Approvals23Invoicing Approvals Customer Best Practice24Invoice Approvals Configuration24Invoice Approvals Key Performance Indicators245.4.Payment Terms24Payment Terms Customer Best Practices24Payment Terms - Configuration246.Inventory256.1.Inventory Process of Receiving25Inventory - Customer Best Practices25Inventory Configurations256.2.Receiving Tolerances25Receiving Tolerances Customer Best Practices25Receiving Tolerances Configuration267.Expenses267.1.Expenses Global Settings277.2.Expense Categories277.3.Expense Classification Engine277.4.Custom Fields287.5.Credit Card Usage and Transaction Mapping287.6.Expense Approval Chains288.Help Desk Support Process288.1.Coupa Support288.2.Ask an Expert289.Summation of Risk and Mitigating Control299.Appendix299.1.Purchase Order Layout299.2.Chart of Accounts309.3.Coupa Content Groups319.4.Account Security Settings319.1.Coupa Custom Fields319.1.User Defaults and Authentication329.2.Coupa Security Roles329.3.Coupa Custom Roles339.4.Approval Limits and Workflow339.5.Integrations Inbound349.6.Integrations - Outbound359.7.Data Volumes35
Executive SummaryPurchasing 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 ProcessE-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:Invoice to PaymentRequisition to Receipt
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 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 GoalsThe 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 Principles1. Get the process right before introducing technology2. Do not create a legacy system order on day 13. Develop a compelling end user experience4. Do not devolve to the status quo by avoiding uphill battles5. Our clients & employees must consistently be able to find what they're looking for6. More access and greater freedom without compromising control7. Maintain a 360 degree view of the process ensuring that all parties affected are taken into account8. Take steps to mitigate major failure points common for deployments:8.1. Low User Adoption8.2. Low Supplier Enablement8.3. Poor program management8.4. Ineffectively mapping the process before deploying the tool9. 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 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%
DefinitionsApproval ChainThese are approval flows that provide business approval to an order, invoice or expense.
Approval GroupsGroups 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
Assumed Receipt or Two Way MatchA PO process wherein two documents are required in order to process a payment: the Purchase Order and the Invoice.
Buyer: CoupaRole in the Coupa system that allows for unblocking of requisitions and other abilities within Coupa; referred to in this documentation as Coupa Buyer
CatalogGroup of items available by a supplier. Catalogs can either by internally hosted or punch out (externally hosted)
Casual UserCoupa requestor that is only using Coupa between 5 and 10 times per fiscal year
COAChart of Accounts
Commodity CodeThis is a code similar to the General Ledger code in other systems
CSN or Coupa Supplier NetworkCoupa 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.
Draft SupplierThe 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
End User or ClientRole in Coupa used to perform basic requisitioning.
Free Form 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
FTEFull Time Employees
Goods Receipt (GR)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
High Touch SupplierA 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.
IMCoupa Implementation Manager
Internally Hosted CatalogItems that are uploaded into the Coupa system by a system administrator. These items are maintained by the customer.
iRequestOption in Coupa wherein an end user can punch out to an external site without a contract.
Low Touch SupplierA supplier that will require little time to enable for communication. This moniker is usually reserved for suppliers that will connect using email or fax.
OHBOn Hand Balance is the inventory level in the Inventory system that can be consumed.
Order listsGroups 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.
POPurchase Order is an approved Requisition that is communicated to a Supplier.
Punch Out CatalogExternally hosted catalogs maintained by their associated Supplier. The items in these catalogs are not maintained by the client.
Purchasing Channels4 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.
Preferred Supplier List of suppliers designated by Sourcing as preferred suppliers and flagged as such in Coupa
RequestorSynonymous with end user or Client in the Coupa system
RequisitionSynonymous with Shopping Cart. Indicates the purchase requisition before it is routed for approval to be a purchase order.
Self-ApprovalLimit upon which an end client or user can order to without gaining a supervisor or project managers approval
Shopping CartSynonymous with Requisition. Indicates the purchase requisition before it is routed for approval
Source to PayThe transactional flow of data for a user to request and receive goods/services and Suppliers to receive payment
Supplier EnablementA 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
TagsDescriptive 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.
Three Way MatchA PO process wherein three separate documents are required in order to process a payment: Purchase Order, Goods Receipt and Invoice.
Ultimate ApproverA role used to identify errors in the approval system and adjust approval settings to repair.
Web-formPre-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.
WHWarehouse is the term used to describe the location for storing Inventory when the Inventory module is implemented.
1. Coupa Overview & System Configuration Options 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 Contracts Coupa Sourcing Coupa Procurement Coupa Invoicing Coupa Inventory Coupa ExpensesAt 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 Budgets Coupa Catalogs Coupa Suppliers (via the Coupa Supplier Network) Coupa Reports Coupa Mobile (including a mobile integration option)Additional Integration Options: SSO Integration (up to LDAP or SAML 2.0 Integration) Integration objects with ERP system Supplier Enablement optionEnvironments that are currently available for are as follows: Test ProductionThis Section is meant to be a review of all system configuration options for Admin personnel configuring the Coupa system for requirements. It contains the simple yes/no or checked/unchecked settings that are required for the configuration with links to the corresponding business process covered in later sections of this document.
2. Global Settings in CoupaThe 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. 1. 2. 1. 2. 2.1. Company Code ConfigurationAreaCoupa System OptionSettingReasoning
Company Company nameChecked/Unchecked
CompanyCompany Logo Checked/Unchecked
CompanyDefault Time ZoneChecked/Unchecked
Address - Configuration 1. 2. 1. 2. 2.1. AreaCoupa System OptionSettingReasoning
Company Company AddressChecked/Unchecked
Accounting - Configuration Note: Customer Best Practices AreaCoupa SystemRecommendation
COAChart of AccountsOne Chart of Accounts Per Legal Entity
COAThere is support for up to 20 segments but for optimal performance then look to have 5. Outside of 5 then you should look to default in values where possibleEnsure fastest processing times
COA50 unique or lower is the optimal level for performanceEnsure optimal processing
COAEnsure users are restricted to the COA that applies to themEnsure fastest processing times
COAStatic 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.Ensure optimal processing speeds
The configurations in Coupa are as follows:AreaCoupa System OptionSettingReasoning
COA Chart of AccountsChecked/Unchecked
2.2. Security Controls2.2. Security Controls Customer Best PracticesAreaActionReasoning
AllLeverage 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. Reduce testing requirements for a Go-Live and all future system upgrades.
AllFor 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.Allows you to utilize the Coupa system roles but also meet business requirements.
AllSet 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.Best practice when dealing with admin roles.
AllEnsure users are restricted to the COA that applies to themEnsure fastest processing times
1. 2. 2.1. 2.2. 2.2.1. 3. 4. 4.1. 4.2. 4.2.1. Security Controls - ConfigurationAreaCoupa System OptionSettingReasoning
Security ControlsSession expiration timeoutX hours
Security ControlsLog in using SAMLChecked/UncheckedUser authentication via SAML
Security ControlsCoupa Credentials: Choose the minimum password length:- 5 characters- 8 characters
Security ControlsCoupa Credentials: Should it be required that passwords contain a mix of alpha and numeric characters?
Security ControlsCoupa Credentials: When should users be locked out of the system? - Never- After 3 failed password attempts- After 10 failed password attempts
Security ControlsCoupa 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
Security ControlsCoupa Credentials: How often should users be required to choose a new password?- Never- Every 30 days- Every 60 days- Every 120 days
Security ControlsCoupa Credentials: When a user chooses a new password, it:- must be different from the last 3 passwords- must be different from the last 8 passwords- does not matter if it is the same as a previous passwords
Custom Roles - ConfigurationAreaCoupa System OptionSettingReasoning
Security ControlsSession expiration timeoutX hours
Security ControlsLog in using SAMLChecked/UncheckedUser authentication via SAML
2.3. Dashboard Controls2.3. Dashboard Controls Customer Best PracticesAreaCoupa System OptionSettingReasoning
Process SavingsYour savings per purchase orderX dollarsLook to provide a value for this setting that meets company needs
Process SavingsYour savings per invoice (entered by your company)X dollars
Process SavingsYour savings per invoice (entered by supplier)X dollars
Preferred Supplier SavingsApply current savings level for all past purchase ordersRadio buttonLook to provide a value for this setting that meets company needs
1. 2. 3. 4. 5. 6. 7. 7.1. Dashboard Controls ConfigurationAreaCoupa System OptionSettingReasoning
Process SavingsYour savings per purchase orderX dollars
Process SavingsYour savings per invoice (entered by your company)X dollars
Process SavingsYour savings per invoice (entered by supplier)X dollars
Preferred Supplier SavingsApply current savings level for all past purchase ordersRadio button
2.4. Content Groups2.4. Content Groups Customer Best PracticesAreaActionReasoning
ViewIn the initial implementation, allow broad access within the beginning and then look to narrow it.No restriction in the initial Go-Live so system operate at an optimal level
3. 4. 5. 6. 7. 7.1. Content Group - ConfigurationAreaCoupa System OptionSettingReasoning
Content GroupsAllow users to limit content they see to one content group at a timeChecked/Unchecked
2.5. BudgetsCreating a mindset of responsible spending starts with end users knowing their budget and how their individual spend affects that budget. Current industry best practice is to spend 95 100% of the allocated budget.Budget Customer Best PracticesAreaActionSettingReasoning
ViewGet accurate budgets integrated automatically with Coupa to ensure that users have that visibilityMake people spend smarter!
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 10.1. Budget - Configuration6. 7. 8. 8.7. 8.8. AreaCoupa System OptionSettingReasoning
Budget PeriodsAllow Users to select budget period for requisitionsChecked/Unchecked
Budget PeriodsAllow users to select budget period for expensesChecked/Unchecked
Budget PeriodsShow detailed budget information (i.e. exact overrun amount) on budget overrun/underrun messagesChecked/Unchecked
2.6. Commodities CodesCommodities Codes Customer Best PracticesAreaActionSettingReasoning
COAExtract COA from legacy system and consolidate it. Determine which GL will be used by Coupa to narrow listReduce system complexity
GLGive all Coupa used GLs a name that is easy to understand Allow system and actions to be easily understood by users
Commodities Codes ConfigurationAreaCoupa System OptionSettingReasoning
CommoditiesEnforce leaf node commodity selection (only pick base levels in the tree)Checked/Unchecked
2.7. Commodity Classification EngineCommodity Classification Engine Customer Best PracticesThe 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.AreaActionSettingReasoning
Commodity Classification EngineMap as many description keywords as possible as will aid user experience during system usuageAid user adoption
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 12.1. Commodity Classification Engine - ConfigurationAreaCoupa System OptionSettingReasoning
Commodity Classification EngineUse classification engine as much as possibleChecked/Unchecked
2.8. ContractsContracts 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 off of Coupa contract. In order to setup a contract, an administrator or buyer will populate the contract with the following information:SupplierMust choose a supplier with an active account in Coupa
Contract NameAll 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.
Contract NumberAlthough 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)
StatusContracts can either be in draft status or published. A buyer or administrator must publish the contract in order for it to be effective
Start DateIf 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
ExpiresContract expiration alerts rely on this field to send out warnings; one the contract reaches that expiration date, Coupa will deactivate it.
OwnerBest practice will be for Contract owners to be set to automatically receive contract alerts
Supplier Account NumberThis field should be left blank
CurrencyAll 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.
Legal AgreementsAlthough Coupa will allow uploads of any legal agreements, Coupa is not the official repository. It is only offered to end users as an option
AttachmentsAny 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.
Savings %This field is left at the discretion of the category owner
Minimum and Maximum SpendsCertain contracts will provide discounts based on the amount of spend made against that contract. 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
1. 2. 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. AreaCoupa System OptionSettingReasoning
ContractDefault on Unbacked LineChecked/Unchecked
ContractSupplier can Invoice DirectlyChecked/Unchecked
ContractCoupa Invoice used against a ContractN/ANot a configuration option so just need to document a decision
2.9. Ask an ExpertCoupa 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 ConfigurationAreaCoupa SystemReasoning
Ask an ExpertRecommending using this system
Ask an ExpertSet-up each categories that you will be using with a user within your organization. Deal with queries at source rather than support queries
2.10. Home Page ContentCoupa 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:
Home Page Content Customer Best Practices and ConfigurationHome page content allows the user to control the information thats available via the home page. AreaCoupa SystemReasoning
Home Page ContentLinks to Training Videos, Frequently Asked Questions and links.Ease of Access to Users to Support and Training
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 13.1. 1. 2. 3. 4. 5. 6. 7. 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 PracticesAreaCoupa SystemReasoning
Sourcing EventEvents with up to 20 Suppliers is optimal Ensure optimal processing
Sourcing Event Events with up to 450 lines is optimal Ensure optimal processing
3.2. Sourcing SettingsAreaCoupa System OptionSettingReasoning
SourcingSuppliers need to login to provide repsonsesChecked/Unchecked
SourcingSuppliers are allowed multiple Sourcing responsesChecked/Unchecked
SourcingEvents have sealed response by defaultChecked/Unchecked
SourcingSealed bids are editable on an event levelChecked/Unchecked
3.3. Sourcing EventsAreaCoupa System OptionSettingReasoning
SourcingRequests for InformationChecked/Unchecked
SourcingRequests for QuotesChecked/Unchecked
SourcingRequests for ProposalsChecked/Unchecked
SourcingOpportunities
Sourcing Opportunity Triggers
3.4. Price Comparisons3. 3.1. Price Comparisons Customer Best PracticesAreaCoupa System OptionSettingReasoning
Price ComparisonsAllow online price comparisonsChecked/Unchecked
Price Comparisons ConfigurationsAreaCoupa System OptionSettingReasoning
Price ComparisonsAllow online price comparisonsChecked/Unchecked
3.5. Sourcing Approvals4. 4.1. 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 ProcessProcurement - Data Process Flows
5. 6. Procurement Customer Best PracticesAreaCoupa SystemReasoning
RequisitionAverage Requisition has three lines but for optimal performance then do not go above 20 linesLarger requisition can be accommodated but keep to limit for optimal processing
POEmail communication of Order to Supplier Speed of receipt of order and supply of goods
ReceiptEnable automatic receiptsReduces manual intervention by the team
Custom Fields5 fields per object is the optimal level. Anything over 20 is not supportedOptimize system performance
Procurement - ConfigurationAreaCoupa System OptionSettingReasoning
RequisitionRoute requisitions to buyer if supplier is in draft statusChecked/UncheckedNot enabling draft suppliers in Coupa
RequisitionRoute requisitions to buyer if no contract is specifiedChecked/UncheckedGovern Coupa with contracts and not directly to supplier.
RequisitionEnable requisition historyChecked/UncheckedWant audit history on requisitions
POEmailed purchase orders should include the order document as an attachmentChecked/UncheckedWe are not using a fax server
POAutomatically close purchase order after X days of inactivityChecked/UncheckedX daysUnchecked due to Blanket POs
POAutomatically close a fully invoiced purchase order after X daysChecked/UncheckedX daysNo invoicing in Coupa
POPrevent requesters from making receipts for suppliers with 2-way matchChecked/Unchecked
Needs to be unchecked for Invoice Pass through to work
POUsers can request changes to their POsChecked/UncheckedUsers have the responsibility to make their own changes
POBuyers must review all purchase order change requestsChecked/UncheckedEnd users will be able to make their own changes at project launch
POShow purchase orders created or requested by the user in My Spend HistoryChecked/UncheckedEnd users will need to be able to see or replicate past purchase orders
ReceiptOnly allow quick receiving multiple PO lines if all lines belong to the same POChecked/UncheckedEnd users will need to be able to quickly place GRs and SRs against a Purchase Order
NotificationsSend notification back to user if the system cannot process an approval notification response via emailChecked/Unchecked
NotificationsSend notifications to requester when un-received orders are X days past dueX daysThis will not work unless doing full Invoicing in Coupa
NotificationsSend notifications to requester to gather supplier reviews X days after orderX days
iRequestEnable iRequest links on the home pageChecked/UncheckedDont plan on using iRequest to allow users to order from anywhere
Online Help LinkNone/Use Coupas online help/Custom URL
