Technology continues to change society at a rapid pace, and accounting and auditing are by no means immune. New technologies are increasingly able to mimic human activity, taking on repetitive tasks more quickly and accurately than people can. The authors provide an overview of the ways in which robotic process automation may change how the profession operates, with a particular focus on the area of revenue audits.
Auditing has historically incorporated many computer-dependent tools and processes, which were often interlinked by many manual steps and keystrokes. A new set of overlay software has emerged, however, that combines these disparate actions into a single smooth automated process. Robotic process automation (RPA) uses these new software tools, such as those offered by Blue Prism or UiPath, to transform a still somewhat handmade audit process into a more assembly-line audit process.
RPA represents a dramatic and disruptive change in current audit practice that promises to allow auditors to operate at a much higher level.
RPA for Reconciliation and Analytical Procedures
In the audit of revenue, RPA can assist auditors by logging into a client’s secure file transfer protocol (FTP) site to retrieve related audit evidence, including the listings for current and prior year sales and the trial balance. RPA can then calculate the total sales per the listing and compare it to the total per the trial balance. Assuming the amounts reconcile, RPA can subsequently calculate whether the total revenue amount from the current and prior year listings is materially different, and generate an alert if the difference exceeds the materiality threshold.
RPA for Dual-Purpose Audit Tests
RPA can be programmed to calculate whether the price and quantity are different across sales invoices, sales orders, and shipping documents, and to generate alerts for sales transactions that contain differences in price and quantity. By automating these procedures, auditors can reallocate their time to more value-added activities, which will inherently increase audit quality. By leveraging RPA software, auditors can obtain a better understanding of the client’s business operations and therefore be able to more precisely assess the risk of material misstatement.
Three-Step Approach to RPA-Based Audits
RPA is a form of process improvement using technology; when applied to auditing, RPA is expected to not only replace manual and mundane audit tasks, but also to motivate the re-engineering of audit processes. When deciding whether RPA is a good fit, public accounting firms can refer to the RPA implementation roadmap RPA implementation consists of three main stages:
1) process understanding
2) audit data standardization (ADS)
3) execution of automated audit tests (i.e., audit apps).
Theoretically, a large number of audit processes may be a good fit for RPA. The audit processes that would benefit the most from RPA are those that contain defined audit tasks that are repetitive and time consuming and that do not require audit judgment. Public accounting firms may identify an audit process where RPA can add value by considering expert knowledge, such as that of revenue audit leaders, and calculating the actual hours spent performing audit tasks. Furthermore, the most important factor to justify automation is the number of times a firm needs to perform a particular function, which is mainly dependent on the number of similar audits being done.
Once a firm determines that a process is a good candidate for RPA implementation, the next step in understanding the process is to divide audit tasks into small audit modules that can be interpreted by software programs. For example, the task of importing or exporting data is intuitive to a human user, but for a software program, the task would have to be divided into a series of small steps:
- Defining the directory from which the file is to be imported
- Importing the file
- Saving the imported file
- Defining the directory into which to export the saved file.
Audit data standardization (ADS)
To run as intended, RPA audit applications need consistency across data fields. Audit-related data may come from different sources, such as the client’s ERP systems or third-party asset managers; thus, data field names in different audit-related reports that contain the same information may be different. If so, RPA software will not be able to execute the intended audit test. Consequently, the second stage in RPA implementation is for public accounting firms to create an audit data standard for each process that will be replaced by RPA.
ADS is becoming more relevant as public accounting firms consider the use of technology in financial statement audits. An ADS template incorporates the audit-related data that is necessary to execute audit tests. Similar data field names and formats can be designed by the firm to ensure the RPA audit application achieves its intended objectives.
Execution of RPA-based audit tests
The final step in the RPA audit implementation framework is to program the software to automatically execute audit tests and deploy it on real-world audit engagements. The advantage of adopting ready-to-use RPA software tools is that they require little to no additional programming. Nevertheless, programming languages such as Python and R can assist in the deployment of RPA-based audit tasks, though they require additional programming skills. Python and R, however, already have libraries that are very useful for RPA functions.
Programming audit tests as rules-based functions would enable the automatic execution of audit tests. Once audit tests are programmed, an auditor can simply click a button for the RPA-based audit tests to import and read data, perform rules-based audit tests, and export the results of audit tests into an audit workpaper.
While RPA has the potential to automate most parts of audit processes, it is preferable for public accounting firms to start small. Targeting low-risk process areas that do not require audit judgment should improve the success rates of RPA projects at firms. Starting small can also increase confidence among RPA software users.
The deployment of RPA audit tests on audit engagements is critical in measuring the success of RPA-based audits. Parallel audit testing consisting of current (manual) audit tests and RPA-based audit tests should also be performed as a way to validate RPA audit tools. Moreover, for RPA to thrive in audit engagements, firms should leverage the support of their IT departments. Establishing an RPA support hotline can help auditors gain more confidence with these tools, and ongoing communication between the audit engagement team and IT support can also help ensure that RPA audit tools are fine-tuned to meet specified audit objectives.
The excitement around RPA is well founded, and the accounting profession is readily embracing this technology. RPA-based audit procedures have the potential to improve audit efficiency and effectiveness. More so than ever, change in the audit profession is slowly but steadily happening, and professionals should be ready to embrace RPA technology and enjoy the fruits of its labor.