Business process automation

Does RPA replace people? What software robots take over, and what stays with the team

RPA takes over operations that follow fixed rules: copying data between systems, posting documents, building routine reports. Decisions that need judgement, exceptions and contact with people stay with the team.

The robot takes the fixed-rule operations; the decision stays with the team

IN SHORT

A software robot runs the steps a person performs in an application, by fixed rules. It removes data entry and copying between systems. Exceptions, decisions that need interpretation and work with clients stay with people, who also check the robot's output.

What is RPA?

Robotic Process Automation (RPA) uses software robots to run the operations a person performs in an application’s interface: reading a field, entering data, opening a file, clicking a button. The robot follows fixed rules and does not change the applications it works in. Common platforms are Power Automate Desktop, in the Microsoft ecosystem, and UiPath.

What the robot takes over

  • Copying data between systems: from an email or a PDF into the ERP, from one application into another.
  • Posting documents: invoices, receipts, bank statement lines, in the accounting or ERP system.
  • Routine reports: extracting the same data every day or week and putting it into a fixed format.
  • Checks by rule: comparing two lists, flagging differences, sending a notification.

These are operations with high volume, fixed rules and structured data. The robot runs them the same way every time, logs every run and can work outside office hours.

What stays with the team

  • Exceptions: a document that does not match the rules, missing data, a case the rules did not cover.
  • Decisions that need interpretation: whether to accept a claim, how to treat an unusual transaction.
  • Contact with clients and suppliers: negotiation, explanations, problem solving.
  • Checking the robot’s output: someone owns the process and reviews the reports and the exceptions.

How the work changes after an RPA project

Employees stop typing the same data into two systems and spend that time on the cases the robot flags. Someone in the team becomes the owner of the automated process: they know the rules, read the robot’s reports and ask for changes when the process changes.

The change has to be explained before the project, not after. People who know which tasks the robot takes over, and what they will do instead, help define the rules; people who are surprised by the robot tend to work around it.

An example from accounting

For Aldia, an accounting firm, we delivered a robot built on Power Automate Desktop. For every company in the portfolio, it downloads e-invoices from the Romanian tax authority’s system, posts them in the firm’s accounting software, matches bank statement payments to invoices and sends a report with the alerts. A model in Microsoft Foundry calculates the proposed ledger account; proposals below the confidence threshold are flagged for the accountant’s decision.

The robot handles the repetitive posting work, while the accountant remains the one who decides and is accountable for the books. The accountants spend their time on analysis, on their clients and on the cases that call for professional judgement.

When RPA is not the right tool

  • the application has an API, so a direct integration is more stable than automating the interface;
  • the process changes often, so the robot needs constant changes;
  • most cases are exceptions, so the robot handles little and the team checks a lot.

The return on an RPA project is calculated on the chosen process, before it starts: see how to calculate the ROI of RPA.

Which tasks would you hand to a robot?

We look at your process, measure the volume and the manual time, and separate what a robot can run from what stays with your team.

Denis Stadler

Founder of Stadler & Partners. AI specialist and Agentic AI solution architect on Azure, Azure DevOps, SharePoint, Dynamics 365 and Power Apps. Writes about Microsoft 365 features as they work in production.

About Denis

The first step is a conversation with a senior consultant.

Tell us where the process is stuck. We reply within one business day. We deliver remotely from Brasov, Romania, on CET+1, and come to you for the kickoff.

Denis Stadler
The first call is with Denis Stadler.Founder · AI Architect & Fractional CTO