# Business process automation: 12 examples and how to pick the first one

Business process automation means a system carries out the steps of a repeatable process, such as collecting a request, routing it for approval, updating records and notifying people, with staff handling only decisions and exceptions. Good first candidates are frequent, rule-based processes with one clear owner, for example leave requests, purchase approvals and employee onboarding. Pick the first one by scoring each candidate on hours saved, error cost, rule clarity and integration effort.

By Shai Goldenberg. Updated: 2026-11-15.

## What business process automation means

A business process is a chain of steps that turns a request into a result. Someone asks for leave, a manager approves, HR records it, payroll is told. Business process automation means software carries the request along that chain. People make the decisions. The system does the routing, the record keeping and the reminders.

Three parts appear in every automated process:

- **A trigger with structured data.** A form, a record in a system or a scheduled time. Never a free-text email.
- **Rules.** Who approves, in what order, above what amount, and what happens when nobody answers.
- **Actions in systems.** A record is created or changed, a document is generated, a message is sent.

A process that cannot be written in those three parts is not ready to automate. That is useful to know before buying workflow automation software.

## 12 examples

These are typical examples by department, not a list of client projects. For each one, the table shows the trigger, what the automation does and the tool that usually fits.

| # | Process | Trigger | What the automation does | Usual tool |
|---|---|---|---|---|
| 1 | Leave request | Employee form | Checks balance, routes to manager, updates the calendar and HR record | Workflow tool |
| 2 | Employee onboarding | HR joiner form | Creates account, licence and groups, opens equipment and access tickets | Workflow tool plus scripts |
| 3 | Employee offboarding | HR leaver form | Blocks sign-in at the agreed time, hands over mailbox and files, removes access | Workflow tool plus scripts |
| 4 | Purchase request | Request form | Routes by amount and cost center, creates the purchase order in the ERP | Workflow tool with ERP connection |
| 5 | Supplier invoice approval | Invoice received | Extracts invoice data, matches to the order, routes exceptions for approval | Custom application or ERP module |
| 6 | Expense report | Receipt upload | Reads receipt data, applies policy, routes for approval, posts to finance | Custom application or product |
| 7 | Travel request | Trip form | Checks policy and budget, routes approvals, records the itinerary | Custom application or product |
| 8 | Document approval | File added to a library | Routes for review, records the outcome, publishes the approved version | Workflow tool |
| 9 | IT ticket intake | Email or form | Categorizes, assigns, sets priority, alerts on overdue tickets | Service desk product with automation |
| 10 | Customer or supplier registration | Web form | Validates data, collects documents, routes for approval, creates the record in the ERP | Portal plus workflow |
| 11 | Scheduled reports | Time | Collects figures from several systems and sends a summary | Workflow tool or script |
| 12 | Contract renewals | Date field | Reminds the owner ahead of expiry, escalates when no action is taken | Workflow tool |

### HR automation: examples 1 to 3

HR automation is the most common starting point, because the processes are frequent and the rules are written down. Leave requests are the simplest. Onboarding and offboarding carry more value and more risk, because they create and remove access. Our [IT onboarding and offboarding checklist](https://goldenroz.com/blog/it-onboarding-offboarding-checklist/) lists every step and marks which ones can be automated.

Shai built an onboarding and offboarding automation as a fixed-price project at an industrial company with about 400 users, where he ran IT for four years. One HR form started the account, licence, group and ticket steps, and the leaver form ran the reverse.

### Finance: examples 4 to 7

Purchase requests and invoice approvals are approval chains with money attached. The rules are usually clear: thresholds by amount, cost center owners, a second approver above a limit. The difficulty is the ERP. The automation is only complete when the approved request becomes a purchase order, or the approved invoice is posted, without retyping.

Expense and travel processes add documents. A language model can read a receipt and fill in the amount, date and supplier for the employee to confirm. That removes typing. It does not remove the approval.

### IT and operations: examples 8 to 12

Document approval and scheduled reports are small, low-risk automations that build confidence. Ticket intake is best handled inside a service desk product, as described in [what is ITSM](https://goldenroz.com/blog/what-is-itsm/). Registration of customers or suppliers usually needs a portal, because the person filling in the form is outside the company.

## Choosing the tool

Three kinds of tools cover almost every case.

| Tool type | Fits when | Watch for |
|---|---|---|
| Workflow automation software, such as Power Automate | The process lives in tools you already have: forms, lists, email, chat, documents | Licensing by connector type, flows owned by one person, long flows that are hard to test |
| A product for that process, such as a service desk or an expense tool | The process is standard and the yearly cost is acceptable | Paying for a full product to run one narrow process |
| A custom internal tool | The process has its own data, screens, permissions or volume | Needs an owner and maintenance |

For companies on Microsoft 365, Power Automate is the natural first tool. Microsoft 365 licences include cloud flows with standard connectors, and connectors to many business systems need a paid Power Automate licence. Check each system against Microsoft's connector reference before designing a flow. Our [Power Automate consulting](https://goldenroz.com/power-automate-consulting/) work covers the design, the licence check and the governance: environments, data policies and ownership by a service account so a flow does not stop when its author leaves.

A custom internal tool is the right choice when a workflow tool starts to hold business data in spreadsheets or lists that were never meant to be a database. Signs of this: a list with tens of thousands of rows, permission rules per row, or a flow with hundreds of actions. At that point a small application with a real database, connected to the same sign-in, is easier to test and maintain.

## How to pick the first one

Score each candidate from 1 to 5 on five questions, then add the scores.

| Question | 1 point | 5 points |
|---|---|---|
| How often does it run? | A few times a year | Many times a day |
| How much staff time does each run take? | Minutes | Hours across several people |
| What does an error or delay cost? | An inconvenience | Money, an audit finding or a security gap |
| How clear are the rules? | People disagree on the steps | Written, stable, few exceptions |
| How easy are the integrations? | Systems with no API and no export | One or two systems with supported connectors |

### A worked example

This example is hypothetical. A company compares three candidates.

| Candidate | Frequency | Time per run | Error cost | Rule clarity | Integration | Total |
|---|---|---|---|---|---|---|
| Leave requests | 5 | 2 | 2 | 5 | 5 | 19 |
| Purchase approvals | 4 | 3 | 4 | 4 | 3 | 18 |
| Supplier invoice matching | 5 | 4 | 4 | 2 | 2 | 17 |

Invoice matching looks like the largest saving, but its rules are unclear and its integration is hard. Leave requests score highest and carry little risk, so they are a sound first project. Purchase approvals come second and bring the ERP connection that invoice matching will need later.

The first project should be finished in weeks, used by many people and easy to measure. It also sets the pattern for forms, approvals, ownership and monitoring that later projects reuse.

## What goes wrong

- **Automating a process nobody agreed on.** If two managers describe the approval chain differently, settle that first.
- **No owner.** Every automation needs a named person who receives failure alerts and decides on changes.
- **No handling for silence.** An approval nobody answers needs a reminder, a deputy and a timeout.
- **Hidden manual steps.** If someone still copies the result into another system, the process is only half automated.
- **No measurement.** Record the time and error rate before the change. Without a baseline, nobody can say whether the automation worked.

## From single automations to systems you own

After several automations, a pattern appears. Some processes sit comfortably in a workflow tool. Others have grown into rented products, each with its own yearly fee: a portal, a recruiting system, a travel tool.

At the industrial company mentioned above, Shai presented an estimate to the CEO that replacing rented internal systems with systems the company owns could save about 800,000 NIS a year (about $250,000). That figure is an estimate presented to management, not a measured result. The reasoning behind it is the same scoring exercise applied to subscriptions: list what each system costs per year, what part of it is used, and what a fixed-price replacement would cost. That is the idea behind our [internal systems](https://goldenroz.com/internal-systems/) category.

## What to do next

List ten processes that start with a form or an email and end with a record in a system. Score each with the five questions above. Take the top scorer, write its rules on one page and name its owner.

If you want the mapping, scoring and build done for you, see our [business process automation](https://goldenroz.com/business-process-automation/) page. Projects start at $25,000 at a fixed price per phase, and the first one-hour consultation is free.

## Questions buyers ask

### What is business process automation?

It is the use of software to run a repeatable business process from start to finish: intake, routing, approvals, record updates and notifications. People stay in the process for decisions and exceptions. It differs from task automation, which speeds up one step, because it covers the whole chain and its handoffs.

### What is the difference between business process automation and workflow automation software?

Workflow automation software is a tool, such as Power Automate, that connects triggers and actions. Business process automation is the outcome: a whole process that runs reliably. A simple process may need only a workflow tool. A process with its own data, screens and rules often needs a small application as well.

### Which process should we automate first?

One that runs often, follows written rules, has a single owner and touches few systems. Leave requests, purchase approvals and new employee setup are common first choices. Avoid starting with a process that people disagree about, because automation will fix the disagreement in place.

### Can Power Automate handle business process automation?

For many processes inside Microsoft 365, yes: approvals, document routing, notifications and data moved between SharePoint, Teams, Outlook and Excel. It is a weaker fit for high-volume integration and for processes with complex logic or their own data model. Licensing also depends on which connectors a flow uses.

### How much does business process automation cost?

At Goldenroz, projects start at $25,000 at a fixed price per phase, quoted after a free one-hour scoping call. The price depends on the number of processes, the systems to connect and whether a custom application is needed beside the workflow tool. Software licences are paid by you directly.

---
Page: https://goldenroz.com/blog/business-process-automation-examples/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
