Advanced Cases in Advisory Services

ACCTG 528 · Spring 2026 · Section not recorded in source

Monday, Wednesday · 10:30AM–12:20PM · PACCAR 292

Mar 30, 2026 – Jun 3, 2026

RPA Individual Submission

Software; Short Video Recording · Individual · 30.0%

Overview

Additional Information on the Individual RPA Submissions

Description

An individual project that includes building an RPA software solution that is explained, motivated and demonstrated in a recorded video presentation. Each individual will be asked to develop a desktop-level automation robot of a common repetitive business task. The bot is to be built using either UIPath or the Microsoft Power Apps. The RPA solution is expected to work on a single desktop, and any issues related to the transfer of the bot need to be identified and discussed. The automation solution needs to be motivated in terms of how many human work hours it can save (efficiency) and the value associated with reductions in human errors (effectiveness). Details and further guidance will be provided on Canvas.

Requirements

Components

RPA Video Submission

A short video submission explaining, motivating and demonstrating an individually developed RPA bot using either UIPath or another RPA/Automation software. The individual bot can be based on automating any business process that is repetitive and/or prone to errors. The Individual challenge can also be a major extensions to the Pure Reformed Oils / Skylar RPA Case (see hints below for definitions of major).

Details

  • A discussion of the common repetitive business task being automated at the individual user / desktop-automation level.
  • The discussion of the automation solution needs to be motivated in terms of how many human work hours it can save (efficiency) and the value associated with reductions in human errors (effectiveness).
  • A discussion of the steps performed, input data and outputs automated by the bot.
  • A discussion of whether the automation includes a human-in-the-loop component and if so what and why this element involves human interaction.

Hints

  • Start your video by clearly stating the business task you're automating and its relevance to accounting, finance, administration, internal or external audit (or any other relevant area).
  • Use on-screen visuals to show your bot in action record both input and output steps with narration.
  • Quantify the impact: Estimate time savings and reduction in error rates, using either real data or reasonable assumptions (if unsure, ask).
  • If extending the bot from the Skylar Case, clearly articulate how your extension provides a major improvement of the original bot. This could include adding new features, improving efficiency, or enhancing user experience.
  • A major extension needs to demonstrate a significant improvement over the original bot. This could be in terms of functionality, efficiency, or user experience. For example, if the original bot was a simple data entry automation, a major extension could involve adding error handling, integrating with other software, or automating a more complex process.
  • If you have two ideas for automation, one which is an extension, and one that is a new idea, usually the new idea will be more unique relative to the rest of the class, and be more likely to score higher points.
  • If you are in the situation where you have an idea for both an extension and a new idea, discuss the ideas with the instructor for feedback on which idea will likely do better and on feasibility (usually the new idea will be better but may not be feasible).

RPA Bot Submission

A software deliverable of a desktop-automation level automation bot using UIPath or another automation software.

Details

  • Each individual will be asked to develop a desktop-automation level automation robot of a common repetitive business task. The bot is to be built using either UIPath or the Microsoft Power Apps (or another automation software with approval from your instructor).
  • The RPA solution is expected to work on a single desktop, and any issues related to the transfer of the bot need to be identified and discussed.
  • Any files or other materials required in order to have the bot run (in most cases you will upload a zip file with your input, app, and output folders.

Hints

  • Choose a task that is rule-based, repetitive, and ideally takes at most 5 minutes per execution this helps demonstrate meaningful efficiency gains.
  • As a base case, a loop should include 3 items to loop through each case to demonstrate that the bot could loop through any number of iterations (three is plenty).
  • You can generate the data input into the automation and if you need help generating data, please ask.
  • Keep your folder structure clean and include a brief README file if additional setup is required for your bot to run (note this is uncommon, ask if unsure).
  • If your bot requires specific file paths, applications, or screen resolutions, note these explicitly and suggest how they could be standardized for transferability (again this should be uncommon, ask if unsure).

Submissions

RPA Individual Submission (Individual, 30%, Class 14)

Legacy due date: May 13th, 2025