Retail Payable Invoice

Solution Design Document

Retail Payable Invoice

Solution Design Document
Version 1.0
01/02/2020

21
 Retail Payable Invoice
Solution Design Document

SUMMARY

Document Owner(s)
Document Author(s) SkillMust.com
Document Status Draft

SUMMARY

Name Approval Type Date Approved

Business Approval

CHANGE LOG

Version # Implemented By Document Change Description

Submission Date
Original document created and
1 Process Architect 18/01/2020
submitted for approval

CLIENT SME DETAILS

Name Role Email ID

21
 Retail Payable Invoice
Solution Design Document

Table of Contents

1. Objective
2. Scope for Automation
3. Applications
4. Input Requirements
5. Complexity of the To-Be Process
6. Detailed Solution Design
7. Success Criteria
8. Exception Handling
9. Process Maintenance
10. Automation Operational Arrangements
11. Business Continuity Plan/ Disaster Recovery (DR) Plan
12. Key Assumptions
13. Document Review Guidelines
14. Glossary
15. Appendix
Appendix A: Process Map
Appendix B: Process Templates

21
 Retail Payable Invoice
Solution Design Document

1. Objective
This document contains the solution design for the Retail Payable Invoice process. It
lays out the high-level “As-Is” process steps as well as the “To-Be” process steps to be
automated using the selected Robotic Process Automation (RPA) tool. It also elaborates
upon key aspects of the automation that is being implemented for this use case.

 High Level Overview of As-Is Process:

 In this process, Analyst accesses Payable invoice screen in Retail application
to search for the transactions & match the amount & quantity against the
counter party settlement quantity & amount.
 Analyst changes the fin status of the transactions based on the threshold
percentage & the transactions are moved to payments screen
 The transactions in the payments screen are confirmed for creating cash
disbursements
 Volumes Information: <TBD>

2. Scope for Automation

The scope for the automation is to validate the transactions in Payable invoice screen &
approve the Payments to create cash disbursements from RETAIL application.

3. Applications
Application Name& Credentials
External
Version (including any Type required for Read/ Write
/ Internal
upgrade information) BOT ID
Network-hosted
RETAIL Internal Yes Read & Write
Application
Desktop
Excel Internal No Read
Application
Desktop
Outlook Internal Yes Read & Write
Application

4. Input Requirements
The inputs and pre-requisites detailed out below, need to be present for the Bot to
function in the desired manner. 

21
 Retail Payable Invoice
Solution Design Document

N Typ Format Name Description Location Initial Value

o e
1 Cou Xlsx Transacti The excel will contain TBD Counterpart
nter onDetails the counterparty y details
part _MMDDY quantity & amount
y YYY along with payment
deta method. This will be
ils created by analyst
file before starting of the
process

5. Complexity of the To-Be Process

This process has been categorized as a ‘Simple’ process from an RPA Implementation
perspective.

6. Detailed Solution Design

High-Level Design

The following sections capture the business logic necessary to navigate through the
process.

21
 Retail Payable Invoice
Solution Design Document

1. Subprocess A – Login to Retail

Subprocess A – Login to Retail

Step ID Step Description Step Type
A1 On a particular time each day, bot will begin execution. Click

Bot will click on SkillMust application in the browser

window

A2 Enter the below URL in the text box of the SkillMust Click
popup window & click on the Sign In Button

http://SkillMust.com

A3 Uncheck both the checkboxes in the popup & click OK Click

button

2. Subprocess B – Payable Invoice Validation

Subprocess B – Payable Invoice Validation

Step ID Step Description Step Type
B1 Click on Navigation button Click

B2 Navigate to Financials panel & under Payable Invoices click Click

Payable Invoices

B3 Click on Query button Click

B4 Select Company as XYZ & click Select button Click

B5 Repeat steps for all the transactions with Fin status value Click
as New

B6 For the current transaction, go to the row in the bottom Click

panel with value Temp-ACCTPAY in the Account column.
Copy the value under column Gross Quantity & paste it
under Retail Quantity Amount.
21
 Retail Payable Invoice
Solution Design Document

Copy the value under column Credit & paste it under

Retail Invoice Amount

B7 Open the account Team stored in the VM Click

B8 Find the transaction number in column B of the account Click

Team which matches the transaction number of the
current transaction in the Retail application.
Copy the value in column C & paste in the Counterparty
Invoice Amount
Copy the value in column D & paste in the Counterparty
Invoice Quantity

B9 Select the value of the drop down list under Pay Method Click
column for the current transaction in Retail which
matches the value in column E of the account Team

B10 Match the value of Retail Invoice Amount with Click

Counterparty Invoice Amount & Retail Invoice quantity
with Counterparty Invoice quantity with the threshold
percentage value defined in the configuration file.
If the both the values are within the threshold limit,
change the fin status of the transaction to Approved, else
change the status to Discrepancy

3. Subprocess C – Confirm Payments

Subprocess C – Confirm Payments

Step ID Step Description Step Type
C1 Click on Payments under Cash disbursements tab Click

C2 Under Payments tab on top, click Confirm All button Click

C3 Under Payments tab on top, click Create Disbursements Click

button

C4 Go to Create Disbursements screen Click

4. Subprocess D – Sending email

21
 Retail Payable Invoice
Solution Design Document

Subprocess D – Sending Email

Step ID Step Description Step Type
D1 Send email with description<TBD> Send Email

7. Success Criteria
The bot will send out the job completion email notification everyday at <TBD> with the
details <TBD>.

8. Exception Handling

Exceptions handled by robotic process automation can primarily be classified into

system and business exceptions. The automation under discussion handles each error
type in a standardized manner.
In general, if the Bot encounters any unexpected scenario, the Bot will generate an
exception message and inform the same to account team. The Bot will generate
exception email, with mitigating actions specified below.

Business Exceptions
All known business exceptions are accounted for within the solution design. If an
unexpected scenario is found, the Bot will log an exception in UiPath for that record and
inform the same to account Team.
Any unexpected business scenarios that the Bot encounters will cause the Bot to skip
the case, leaving it open and informing to Account team.
For any business exception, then:
i. Action taken by automation: Error captured in the Exception Report for the
business exceptions
ii. Reporting Type: The Exception message for the business scenario will be
preserved within the Exception Report.
iii. Manual Action required:
a. Account Team Supervisor: Manual review recommended if business
exception occurs frequently
b. Bot Controller: None

21
 Retail Payable Invoice
Solution Design Document

Known Business Exceptions:

Exception Scenario Exception Status Message

Counterparty Excel is not found Counterparty Excel is not found

System Exceptions
System Exception such as Retail application not working is considered in the SDD. If an
unexpected scenario is found, the Bot will log an exception in UiPath for that record and
inform the same to Trading Team.

Exception Scenario Exception Status Message

Retail is not accessible Retail is not accessible
Outlook is not accessible Outlook is not accessible

9. Process Maintenance
 The counterparty details excel file should be available before starting of the
process

10. Automation Operational Arrangements

How often will the solution run? <TBD>

How many cases is the solution expected to <TBD>

handle?
Will the solution run outside normal <TBD>
working hours?
What time will the solution start? <TBD>

What part will the Business play within the Review

end-to-end process?
Will the Business re-submit exception cases Possibly
to the solution?

11. Business Continuity Plan/ Disaster Recovery (DR) Plan

In case of complete failure of the Bot, the team will need to revert to manual process. 
 Operations team will perform the “Process” process manually, until notified
 RPA Capability will be responsible for operational tracking, monitoring,
maintenance. In case of any temporary outages or planned downtime, the COE will
communicate to business and expedite restoration of services. 

21
 Retail Payable Invoice
Solution Design Document

 Process owners are expected to systematically review and audit the results to
ensure the functional value is provided.
 Changes to host systems to be proactively communicated to members of the RPA
Capability. 
 The process owner will receive notification emails for all failures. 

12. Key Assumptions

 TBD

13. Document Review Guidelines

This document is to be reviewed every 12 months and updated with relevant process
and system changes to reflect the current process and automation functionality. This
review should be conducted by a nominee of the document owner and signed off by the
document owner.

14.

21
 Retail Payable Invoice
Solution Design Document

14. Glossary

Term Description
RPA Robotics Process Automation
UiPath UiPath
SIT System Integration Testing
SLA Service Level Agreement
SME Subject Matter Expert
UAT User Acceptance Testing

15. Appendix

Appendix A: Process Map

Appendix B: Process Templates

Sr. File Name Type Purpose Attachment
1
2
3

21