1

{PROCESS Name & CLIENT Name} – Process Definition Document

Robotic Process
Automation

<Business Process Name>

Process Definition Document (PDD)

2
Process Name - Process Definition Document v 1.0
 Document History

Date Version Role Name Organization Function Comments

dd.mm.yyyy 1.0 Author Name Client org AP-SME Created document v 1.0
Surname

3
Process Name - Process Definition Document v 1.0
Contents

1. Introduction 4
1.1 Purpose of the document 4
1.2 Objectives 4
1.3 Process key contacts 4
1.4 Minimum Pre-requisites for automation 5
2. As IS process description 5
2.1 Process Overview 5
2.2 Applications used in the process 5
2.3 As IS Detailed Process map 6
2.4 Additional sources of process documentation 7
3. To BE Process Description 8
3.1 TO BE Detailed Process Map 8
3.1.1 Change/Improvement details 8
3.1.2 Areas already automated 9
3.2 In Scope for RPA 9
3.3 Out of Scope for RPA 9
3.4 Business Exceptions Handling 9
3.4.1 Known Exceptions 9
3.4.2 Unknown Exceptions 10
3.5 Application Error and Exception Handling 10
3.5.1 Know Errors or Exceptions 11
3.5.2 Unknow Errors and Exceptions 11
4. Other Requirements and Observations 12
5. Document Approval 12

4
Process Name - Process Definition Document v 1.0
 5
Process Name - Process Definition Document v 1.0
 1. Introduction

1.1 Purpose of the document

The Process Definition Document outlines the business process chosen for automation using UiPath
Robotic Process Automation (RPA) technology.

The document describes the sequence of steps performed as part of the business process, the
conditions and rules of the process prior to automation and how they are envisioned to work after
automating it, partly or entirely. This specifications document serves as a base for developers,
providing them the details required for applying robotic automation to the selected business
process.

1.2 Objectives
The business objectives and benefits expected by the Business Process Owner after automation of
the selected business process are:
{replace the below bullet points that serve as example, with the specific, SMART objectives and benefits expected after automation }

➢ Reduce processing time per item by 80 %. The duration to process an invoice in AS IS state is
7 minutes.
➢ Monitoring of xyz sub activities

1.3 Process key contacts

The specifications document includes concise and complete requirements of the business process
and it is built based on the inputs provided by the process Subject Matter Expert (SME)/ Process
Owner.

The Process Owner is expected to review it and provide signoff for accuracy and completion of the
steps, context, impact and complete set of process exceptions.

The names have to be included in the table below.

Role Name Contact details Notes

(email, phone number)

Process SME Name, Surname Name.surname@domain.co Point of contact for

m questions related to
business exceptions
Mobile: 44 0735 325 209
and passwords

Process Name, Surname Name.surname@domain.co Point of Contact for

Reviewer / m process exceptions

Mobile: 44 0735 325 209

Process Owner/ Name, Surname Name.surname@domain.co Escalations, Delays,

Approver for

6
Process Name - Process Definition Document v 1.0
production m

Mobile: 44 0735 325 209

1.4 Minimum Pre-requisites for automation

1. Filled in Process Definition Document

2. Credentials (user ID and password) required to logon to machines and applications
3. Test Data to support development.

2. As IS process description
2.1 Process Overview
General information about the process selected for RPA prior to automation.

# Item Description

1 Process full name NPO invoice posting

2 Process Area Accounts Payable

3 Department Finance and Accounting

4 Process short description PDF invoices sent by email are posted in SAP for later payment.

(operation, activity,
outcome)

5 Role(s) required for AP Process Associate, AP Payment team etc

performing the process

6 Process schedule and Daily, Monday to Friday, 9 am – 6 pm

frequency

7 # of items processes ~4500

/month

8 Average handling time 7 min

per item

9 Peak period (s) End of month, usually from 20th to 28th day of each month

10 Total # of FTEs supporting 10

this activity

11 Level of exception rate ~20% exceptions (incomplete invoice details, unreadable data
on the invoice etc)

12 Input data PDF attachments received by email

7
Process Name - Process Definition Document v 1.0
13 Output data Invoice posted in SAP. Confirmation email. Processed email
moved to process folder.

14 Dependencies n/a

(upstream, downstream)
*Add more table rows if necessary to include relevant data for the automation process. No fields should be left empty. Use “n/a” for the
items that don`t apply to the selected business process.

2.2 Applications used in the process

The table includes a comprehensive list all the applications that are used as part of the process
automated, at various steps in the flow.
# Application System Login Interface Environment/ Comments
name & version Module
Languag Access method (Include URLs)
e

1 Outlook 2011 EN n/a Client Local desktop Single Sign On

2 SAP 740 EN ECE Client Local desktop Test environment for

POC identical with
Patch 11
production system.
*Add more table rows to include the complete list of applications.

2.3 As IS Detailed Process map

This chapter depicts the AS IS business process in detail to enable the developer to build the
automated process.
{Detailed process map to be added here, with input/output flow at each stage. Divide the process into stages if required (for better
readability)}.

Add the AVG TAT (Average Turn Around Time) for each key transaction/ activity. Use the “Short description of key process steps” . More
detailed information can be documented in a separate table and/or documented and embedded in this document/ Section.

Example:

8
Process Name - Process Definition Document v 1.0
{Fill in the table below with a short description of the process steps presented in the AS IS diagram}.

Step Short Description of Key Process Steps AVG

TAT*

1 Check Outlook email, NPO Folder, for new emails to be processed

2 Pick new email, check the email for attachment and available information

3 If the PDF attachment is missing, reply to email requesting for the PDF to
be sent attached

4 Logon to SAP, module ECC, navigate to menu

5 Search for the vendor name listed on the invoice

6 Check if the vendor entry exists in SAP

7 If the vendor doesn`t exist, send email to request for vendor entry to be
created

8 If the vendor exists, proceed to register the invoice in SAP

9 After the invoice is processed, send an email notification that the action is
complete

10 In Outlook, move the email with the processed attachment to the

“Processed” folder
In the AVG TAT ( Average Turn Around Time) please fill in the current TAT of each transaction. More detailed information can be
documented in a separate table and/or documented and embedded below.

2.4 Additional sources of process documentation

If there is additional material created to support the process automation please mention it here,
along with the supported documentation provided.

Additional Process Documentation

Video Recording of the process Insert link to the video Date and time of the

9
Process Name - Process Definition Document v 1.0
[Mandatory] recording and provide recording.
access to the video.
Insert additional relevant
comments

List of supporting documents Embed documents List here all the templates,
mapping tables, list of URLS
that are provided as
supporting info for
automation.

Standard Operating Procedure (s) Insert link to the standard Insert any relevant comments
operating procedure
(Optional)
related to the process in
scope.

Other documentation Insert link to any other Insert any relevant comments
relevant process
(Optional)
documentation (L4, L5
process description, fields
mapping files etc)
*Add more table rows to reflect the complete documentation provided to support the RPA process.

10
Process Name - Process Definition Document v 1.0
 3. To BE Process Description
This chapter highlights the expected design of the business process after automation.

3.1 TO BE Detailed Process Map

{Detailed process map to be added here, with input/output flow at each stage. Divide the process into stages if required (for better
readability)}.

Example:

{Fill in the table below with a legend of the process steps and symbols presented in the TO BE diagram}.

Legend
Step number in the process. Referred in the details or Exceptions and Errors table

This process step is proposed for automation

This process step remains manual (to be performed by human agent)

Change/ Improvement opportunity

Area or Branch Already Automated

3.1.1 Change/Improvement details

Use this section to detail the list the change or improvement opportunity in the To-Be Process.

Important aspects to be mentioned: what is the initiative, expected outcome, expected completion
date, contact person for details, and if will impact the current automation request.

# Initiative name and Process Step(s) Does it impact Expected Contact

Expected where it is the current completion person
Outcome/Benefits identified automation date for
request? How? more
details

11
Process Name - Process Definition Document v 1.0
 1.

2.
3.

3.1.2 Areas already automated

List the areas and branches where the process is already automated. Mention if that has any impact
on the current automation request.

3.2 In Scope for RPA

The activities in scope of RPA, are listed here:

Example:

1. Verify emails for attachments

2. Handle exception if attached PDF is missing
3. Post data in SAP
4. Send confirmation email

3.3 Out of Scope for RPA

The activities OUT of scope of RPA, are listed here. Mention of the changes/ improvement
opportunities identified for automation are out of scope for this automation iteration.

Example:

1. Dispatching the emails into NPO invoices folder

2. E-invoicing
3. Invoices received by Fax

3.4 Business Exceptions Handling

The Business Process Owner and Business Analysts are expected to document below all the business
exceptions identified in the automation process. These can be classified as:

Known Unknown

Previously encountered. A scenario is New situation never encountered before.

defined with clear actions and It can be caused by external factors.
workarounds for each case. Cannot be predicted with precision,
however if it occurs, it must be
communicated to an authorized person
for evaluation.

12
Process Name - Process Definition Document v 1.0
 3.4.1 Known Exceptions
The table below reflects all the business process exceptions captured during the process evaluation
and documentation. These are known exceptions, met in practice before. For each of these
exceptions, define a corresponding expected action that the robot should complete if it encounters
the exception.

BE # Exception Step Parameters Action to be taken

name
send email by using Reply email function
1 Missing Step # 2 If attachment is
attachment missing “Hello,
The current email is missing the invoice in PDF/ XML
format. Please resend the email with the correct file
attached.
Thank you”

Invoice Fields missing send email for additional details: Reply email
2 mandatory Step # 3 or incomplete:
details are “Hello,
missing or Company name The product details mentioned in the invoice are
incomplete incomplete or missing. Please check the invoice details
Invoice date
(unidentifiable) and re-send the correct invoice.
Invoice Thank you”
reference
number

Description

Taxable
amount

Tax Rate

Total amount

Contact
information

3 Vendor does Step # 6 Vendor name Send email to

NOT exist in not found vendormasterdata@sapvmd.domain.com
SAP
“Hello ,

The vendor presented in the attached invoice is

missing from SAP. Please create one entry for it and
confirm when it has been done. Thank you,”
Insert more table rows if necessary to capture all the exceptions in a comprehensive list.

3.4.2 Unknown Exceptions

For all the other unanticipated or unknown business (process) exceptions, the robot should:
{Define a corresponding expected action that the robot should complete if it encounters unknown exception.}

Example:

13
Process Name - Process Definition Document v 1.0
 - send an email notification at XYZ@domain.com [insert full name, function and email
address] with the original email and error message screenshot attached.

3.5 Application Error and Exception Handling

A comprehensive list of all errors, warnings or notifications should be consolidated here with the
description and action to be taken, for each, by the Robot.

Errors identified in the automation process can be classified as:

Area Known Unknown

Technology/ Experienced previously, action plan New situation never encountered before,
or workaround available for it. or may happened independent of the
Applications
applications used in the process.

3.5.1 Know Errors or Exceptions

The table below reflects all the errors identifiable in the process evaluation and documentation.

For each of these errors or exceptions, define a corresponding expected action that the robot
should complete if it is encountered.

AE Error name Step Parameters Action to be taken

#

1 Email stops Any step when Error message Wait for application to respond.
responding working with
outlook. Most Retry.
frequent when
opening Close application and run the
attachments. sequence again.

SAP logon Account deactivated Send email with screenshot to RPA

2 failure Step 4 supervisor.

Insert more table rows if necessary to capture all the exceptions in a comprehensive list.

3.5.2 Unknow Errors and Exceptions

For all the other unanticipated or unknown application exceptions/errors, the robot should:
{Define a corresponding expected action that the robot should complete if it encounters an error or unknown exception.}

Example:
- send an email notification at XYZ@domain.com [insert full name, function and email
address] with the original email and error message screenshot attached.

14
Process Name - Process Definition Document v 1.0
 4. Other Requirements and Observations
Include below any other relevant observations you consider needed to be documented here.

Example: Specific Business monitoring requirements (audit and reporting) etc

5. Document Approval
This document requires serial approval (sign off) from the roles defined in the table below.
Changes to the requirements must be documented in an updated version (i.e v 2.0) and requires a new
signature flow.

Version Flow Role Name Organization Approval Date:

(Dept.)

1.0 Document Technical Name Surname

prepared by Solution
Architect

1.0 Document Process Name Surname

Approved by: Owner

1.0 Document Operations Name Surname

Approved by:

1.0 Document Compliance Name Surname

Approved by:

1.0 Document RPA Name Surname

Approved by: Architect/
Developer

15
Process Name - Process Definition Document v 1.0