What Is Business Process Automation?

How does business process automation differ from the other kinds?

The difference is scope. Task automation does one step. Workflow automation chains steps. Business process automation covers an entire process from the event that starts it to the outcome that ends it, including the people and approvals in between.

Our guide to workflow automation covers the middle layer in detail. Anthropic's engineering guidance separates workflows, where models and tools follow paths written in code, from agents, where the model directs its own steps. Most business processes want the first.

Why map the process before you automate anything?

Because automating a muddled process gives you a faster muddle. A process map shows where the time actually goes, and usually shows steps that should be deleted rather than automated.

Draw a table with one row per step and five columns: what happens, who does it, which system, how many minutes, and what goes wrong. Fill it in by watching the work, not by asking the manager. The gaps between steps, where an invoice waits in someone's inbox, often cost more than the steps themselves.

A worked example: supplier invoices

This is illustrative, with invented numbers. A business receives 120 supplier invoices a month. Today each one is opened, retyped into the accounting system, emailed to a manager for approval, chased, paid and filed. That takes about 8 minutes of handling each.

• Manual handling: 120 x 8 minutes = 960 minutes, which is 16 hours a month.
• After automation: the invoice is read, the amounts are entered, a matching purchase order is checked by rule, the approver receives a one-click request, and the payment and filing steps are prepared. A person spends about 2 minutes reviewing the exceptions and approvals on each. That is 120 x 2 = 240 minutes, or 4 hours.
• Saved: 12 hours a month. At EUR 20 an hour, that is EUR 240.

EUR 240 a month will not pay for an expensive project. It will pay for a small build on a general platform. The larger gain is often elsewhere: fewer typing errors, no lost invoices and an approval that takes hours instead of days. Put a figure on those only if you can measure them.

What are the best practices?

Eight habits separate processes that work from those that quietly decay:

1. Pick one process. Do not start with a company-wide programme.
2. Measure the baseline. Time the current process for two weeks before you change anything.
3. Simplify first. Delete steps that exist only because of old habits.
4. Define the exception path. What happens when the invoice has no purchase order or the amount is wrong? Name a person.
5. Keep approvals with people. Money, contracts and exceptions need a human decision.
6. Log every step. Who or what did what, when and with which data.
7. Test with real, messy cases. Include the worst ten from last month.
8. Name an owner. Someone who reads the logs monthly and answers when it stops.

When does RPA make sense?

Use robotic process automation only when a system has no integration and cannot be replaced. It imitates a person's clicks and typing, so it breaks when a screen changes, and it needs maintenance. Microsoft's Power Automate pricing page, checked in November 2026, lists a Premium plan at USD 15 per user a month paid yearly that includes attended desktop automation, and a Process plan at USD 150 per bot a month for unattended desktop automation. It notes that a bot can run one unattended desktop flow at a time. For most small businesses, a normal integration on a general platform is cheaper and sturdier.

How do you keep a process auditable?

An automated process should leave a record that a person can read, particularly for money. For finance processes in particular:

• Keep an audit trail. Store what came in, what was decided, who approved and when.
• Separate duties. The person who approves a payment should not be the person who sets up the payee.
• Log changes to the automation itself. Who edited the workflow, and when.
• Control access. Use named accounts with the smallest permissions needed, not a shared login.
• Decide how long to keep records, and apply the same rule to personal data they contain.

If the automation platform or a supplier handles personal data for you, GDPR Article 28 requires a contract that limits what they may do with it. Ask for a data processing agreement and for the ability to export your logs.

What does it cost?

Tool costs are small and design and supervision are not. Zapier's Professional plan starts at USD 19.99 a month billed annually, per its pricing page in November 2026, and Power Automate Premium at USD 15 per user. The bigger costs are the hours to map, build, test and maintain, which depend on how many systems the process crosses. If you buy that help, ask for quotes to be split into hours, tool fees and support, as our guide to the AI automation agency market explains.

What goes wrong most often?

• Automating a bad process. The map showed three unnecessary approvals and nobody removed them.
• No exception path. Odd cases pile up in a mailbox nobody checks.
• No owner. The person who built it leaves.
• Over-customizing. A process so tailored that nobody can change it.
• Resistance from the people doing the work. They know where the real problems are. Involve them in the map.

Next steps

Pick one process you run every week, draw the five-column map and time it for two weeks. Then read AI automation for business to decide whether and where AI belongs in it. If you would like help mapping it, see our AI automation service. We are a new studio, and we quote in writing.