ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
3
Instructions
4
Users need to use the link: https://{YourDomain}.coupahost.com and enter Username and password to login or If a company has SSO enabled, users could login into Coupa via SSO
5
The below mentioned users are for reference purpose only. Admins can change the name as per their requirement
6
Admins can change the test scripts as per their business use case and system configurations.
7
Please log the defects on the last sheet "Defects" and mail the same to quickstartexpenses@coupa.com
8
9
10
11
12
13
NamesUsernameRoles
14
AudreyExpense_AudreyExpense user
15
BenExpense_BenExpense user and Supervisor of Audrey
16
CharlieExpense_CharlieExpense user and Supervisor of Ben
17
DaisyExpense_DaisyExpense Auditor
18
EvaNATeammate of Audrey
19
JohnExpense_JohnExpense user from IT enablement team, who should approve the internet bills when WFH
20
21
22
23
Test Case IDTest Case Description Test case scenarioStatus
24
EE01To test recurring expenses, emailing receipts to coupa wallet, email parsing, adding approver manually functionalities in Coupa expenseAudrey wants to claim internet bills on a monthly basis which he will email to coupa wallet on the day 2 of every month for the financial year.
25
EE02To test On-behalf of report creation, accounting review statuses, delegation functionalities in Coupa expense moduleEva wants to reimburse the cost for year end gifts for clients, but she is on a vacation. She asks Audrey to submit on behalf of her, which goes to the same approval chain as they are colleagues. Audrey submits the expense report on behalf of the Eva without attaching the required receipt. Ben delegates the approval to Charlie as he is on sick leave.
26
EE03To test Coupa mobile app, email approval, attendee tracking, direct picture upload functionalities in Coupa expense moduleAudrey is using coupa mobile app to submit the expense report for the expenses incurred during the team lunch. She directly attaches the receipt by clicking photo of the bill and added attendees. Ben approves the expense report though email notification and Charlie approves the report from coupa mobile app
27
EE04To test Pre-approval form, expense type: mileage expense category in Coupa expense module
Audrey needs to travel to Hyderabad for Business conference. Prior to visiting Hyderabad she needs approval from her direct manager before she starts the booking and after the trip is complete.
28
EE05To test Itemization feature and send back line in Coupa expense moduleAudrey visits to client company for a 3-day workshop, she has to claim air fare, lodging, rental car and other such expenses.
29
T01, T02, T03 T04, T05, T06
Expense user (Submitter)
To test expense report creation via Coupa UI, Mobile app, email parsing, on behalf of and expense report for attendee trackingExpense user submitting expense report via coupa UI, mobile app & email parsing
30
T07, T08, T09, T10, T11
Expense user (Approver)
To test expense report approval via Coupa UI, Mobile app and email. Rejecting expense line and sending line back via Coupa UI
Expense user (Approver) approving expense report via coupa UI, mobile app & emails
31
T12, T13, T14, T15
Expense Auditor
To test expense report approval, rejection, request for info and editing as an auditor via Coupa UIExpense Auditor approving expense report via coupa UI
32
33
34
Note:
35
Management hierarchyManagement hierarchy approvals are used when a request needs the approval of the requester’s manager. Coupa builds a management hierarchy for your organization using the Next Approver value on user records. Coupa also uses the Self Approval Limits and Approval Limits values on the user record to decide when to keep adding approvers with a higher approval limit until the request total is covered.

Hierarchical approvals are typically easiest in terms of configuration and maintenance. It minimizes complexities as the system takes on the burden of building the approval path based on the users’ Next Approver (i.e. reporting manager). This requires manager information and approval limits to be present on the user record.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100