RPA

What RPA means

RPA stands for robotic process automation and means software operating a user interface by fixed rules. The decisive point is the kind of access: instead of using an interface, the program reaches the same fields, buttons and screens as a person. It opens a program, enters values, clicks, reads a table and repeats that as often as needed.

The advantage lies in availability. Where no interface exists, the user surface is the only route. That covers older ERP systems, supplier portals, banking applications and government forms. The disadvantage is fragility: when the layout changes, the process breaks.

How it differs from interfaces and AI

Three techniques are often confused. An interface is the clean route, because it is built for data exchange. It has to exist and be maintained, though. An RPA process needs no interface but a stable surface. An AI application makes decisions that cannot be captured in rules, such as sorting a freely written enquiry.

In practice they interlock. An AI model reads an invoice and recognises amount and date, an RPA process enters the values into the accounting system. The separation is sensible, because the first task needs a different tool than the second.

When RPA makes sense

• No interface available: with a portal that has no open access, the surface is the only route.
• High volume: a process running a hundred times a day justifies the build. Twice a month barely does.
• Fixed rules: the process has to be describable in steps. Where exceptions dominate it becomes unmaintainable.
• No write access without control: processes triggering orders or payments need approvals.

Why it can become expensive over time

The first reason is maintenance. Every layout change in the target system breaks the process, and the effort for that lies with the shop and not with the portal's owner. Anyone running many processes needs someone to maintain them.

The second reason is access management. An RPA process signs in like a user. Anyone using a personal account for it loses traceability. Dedicated technical accounts with clearly limited rights are needed. The third reason is replacement: as soon as the provider offers an interface, the surface process becomes superfluous and should be replaced, otherwise the workaround is paid for permanently.

Frequent questions

• Is RPA outdated? No, it remains the route for systems without access.
• Do I need developers? Simple processes can be recorded, complex ones need someone with experience.
• What is the most common mistake? No log and nobody responsible for maintenance.