20 Power Automate Workflow Examples That Remove Admin from Finance, HR and Operations
Most businesses already pay for Power Automate and barely use it. If you have Microsoft 365, you can build Power Automate workflow examples like the ones below today, often without buying anything new.
The problem is rarely the tool. It is knowing where to start. Teams either automate something trivial and lose interest, or pick their most complex process and stall for months.
This guide gives you 20 practical workflows across finance, HR, operations and reporting. For each one, we show what it does, what triggers it and which licence it needs. Then we explain how to choose your first three.
First, what does your licence cover?
Licensing decides what you can build, so check it before you design anything. Microsoft's rules, as of November 2026, are:
| Tier | What you get | Typical connectors |
|---|---|---|
| Standard (included with most Microsoft 365 business plans) | Cloud flows using standard connectors, up to 6,000 actions per user per day | Outlook, Teams, SharePoint, Forms, Excel Online (Business), Planner, Approvals, OneDrive |
| Premium (Power Automate Premium, per user) | Premium and custom connectors, desktop flows (RPA), process mining | SQL Server, Azure, Dynamics 365, HTTP, Dataverse, most third-party business systems |
| AI (AI Builder features) | Document reading, text extraction, prompts | Invoice and receipt processing, classification |
Four details catch people out:
- SQL Server, Azure and Dynamics 365 connectors are Premium. If your data lives in a SQL database, a Microsoft 365 licence alone will not connect to it (Microsoft Power Platform licensing FAQ).
- Desktop automation on Windows is free for personal use only. Windows users can build attended desktop flows in the default environment, but sharing, scheduling and combining them with cloud flows needs Premium (Power Automate licensing FAQ).
- AI Builder now runs on Copilot Credits. From 1 November 2026, new and renewed licences no longer include seeded AI Builder credits. The features still work, but they consume Copilot Credits (Microsoft Learn: End of AI Builder credits).
- Prices and licensing terms change. Microsoft revises Power Automate pricing and entitlements regularly, so check current figures with Microsoft before you budget.
Each workflow below is tagged Standard, Premium or AI so you can see what is possible with what you already own.
Finance workflows
Finance teams spend a surprising amount of time moving numbers between systems and chasing approvals. These five workflows target that directly.
1. Purchase request approvals
What it does: A staff member submits a request through Microsoft Forms. The flow routes it to the right budget holder based on value and department, sends reminders and records the decision in a SharePoint list. Trigger: New form response Tier: Standard
2. Supplier invoice capture
What it does: Invoices emailed to a shared mailbox are read automatically. Supplier, date, amount and VAT are extracted and passed to finance for checking before entry. Trigger: New email with attachment Tier: AI (plus Premium if posting directly into your finance system)
3. Expense claim routing
What it does: Claims and receipts are submitted from a phone, checked against policy limits, routed to the line manager and then finance, with rejected claims returned with a reason. Trigger: New form response or SharePoint item Tier: Standard
4. Month-end close checklist
What it does: On a set working day each month, the flow creates the close tasks in Planner, assigns owners and posts daily progress to a finance Teams channel. Trigger: Schedule Tier: Standard
5. Credit control reminders
What it does: Overdue invoices are pulled from your finance system each morning. Polite reminder emails go out at set intervals, and the account manager is alerted for anything past 60 days. Trigger: Schedule Tier: Premium (finance system connector)
HR workflows
HR processes are full of handoffs between HR, IT, managers and payroll. Automating the handoffs is often worth more than automating any single task.
6. New starter onboarding
What it does: When a new hire is confirmed, the flow creates IT, facilities and payroll tasks, sends the manager a first-week checklist and emails the starter their welcome pack. Trigger: New item in an HR SharePoint list Tier: Standard
7. Leaver offboarding
What it does: A leaving date triggers equipment return, access removal and final pay tasks, with reminders until each one is closed. This closes a common security gap: accounts left active after someone leaves. Trigger: Leaver form or HR list update Tier: Standard (the Microsoft Entra ID connector is Standard; check permissions with IT before it changes accounts)
8. Holiday requests
What it does: Requests go to the manager in Teams for one-click approval. Approved leave is added to a shared team calendar and the balance tracker is updated. Trigger: New form response Tier: Standard
9. Training and certification renewals
What it does: The flow checks expiry dates weekly and reminds staff and managers 60, 30 and 7 days before a certificate lapses. This is especially useful for regulated roles such as drivers, care staff and engineers. Trigger: Schedule Tier: Standard
10. Policy acknowledgement tracking
What it does: When a policy is updated, the flow sends it to everyone affected, records each acknowledgement and chases anyone who has not responded. Trigger: New file version in SharePoint Tier: Standard
Operations workflows
Operations is where rekeying hurts most, because errors reach customers. These workflows keep data flowing between the systems people already use.
11. Customer order or job intake
What it does: Orders arriving by web form or email are logged in one place, validated and assigned to the right team. A customer acknowledgement goes out automatically. Trigger: New form response or email Tier: Standard (Premium if writing to a CRM, SQL database or line-of-business system)
12. Document generation
What it does: Quotes, contracts, delivery notes or certificates are produced from an approved Word template using live data, converted to PDF and filed against the record. Trigger: Status change on a record Tier: Premium (the Word Online template action is Premium)
13. System-to-system sync
What it does: When a customer or supplier record changes in one system, the change is copied to the others. This ends the "which system is right?" argument. Trigger: Record created or updated Tier: Premium
14. Stock or capacity alerts
What it does: Stock, fleet or room-capacity levels are checked on a schedule, and the right person is alerted in Teams before a shortage becomes a problem. Trigger: Schedule Tier: Standard if the data is in Excel or SharePoint; Premium if it is in SQL Server or another system
15. Legacy system data entry with desktop RPA
What it does: For older applications with no API, a desktop flow copies data from a spreadsheet or email into the system's screens, field by field, with screenshots logged for audit. Trigger: Manual or scheduled Tier: Premium (free on Windows for personal, unshared use only)
Reporting and data workflows
Manual reporting is one of the most expensive habits in mid-sized businesses. Each report is cheap, but they repeat every week. We explain the compounding effect in the compound return on report automation.
16. Scheduled report distribution
What it does: Reports are exported on a schedule and sent to the right people, or posted to Teams, with a short summary of key figures in the message body. Trigger: Schedule Tier: Standard
17. Report templates filled with live data
What it does: Instead of copying figures into a monthly board pack, the flow pulls current data into the template and saves a draft for review. People check the numbers rather than type them. Trigger: Schedule Tier: Premium if the source data is in SQL Server or another business system
18. Data quality alerts
What it does: The flow checks for missing, duplicate or out-of-range values in key records each night and sends a list to the data owner before anyone builds a report on bad data. Trigger: Schedule Tier: Standard or Premium, depending on where the data lives
19. Failed refresh and job alerts
What it does: When a key figure crosses a threshold, or a Power BI refresh or overnight data job fails, the flow alerts the owner straight away with the details, instead of leaving users to find stale numbers at 9am. Trigger: Power BI data-driven alert, or a scheduled check of refresh and job history Tier: Standard for Power BI data-driven alerts; Premium for checking refresh history through the Power BI API or SQL Server Agent jobs
20. Consolidating spreadsheets from multiple sites
What it does: Branches, depots or departments drop their weekly spreadsheets in a SharePoint folder. The flow validates each file and combines the rows into one master dataset for reporting. Trigger: New file in folder Tier: Standard
How to choose your first three
Here is the contrarian part: do not start with your biggest process. Large, cross-department processes are where automation projects stall, because they need agreement from too many people and touch too many systems.
Start with workflows that score well on four questions:
- Is it high volume? Something that happens daily or weekly pays back faster than an annual task.
- Is it rules-based? If two people would make the same decision from the same information, it can be automated.
- Is the data already digital? Paper and phone calls need fixing first.
- Does one team own it? Single-owner processes go live in weeks, not months.
For most organisations, the best first three come from this list: purchase approvals (1), new starter onboarding (6) and scheduled report distribution (16). All three run on Standard licensing, involve one owning team and show visible results quickly.
Fix the process before you automate it
Automating a messy process just makes the mess faster. Before building any of these workflows, map the current steps and remove anything that adds no value. If an approval has three sign-offs, ask whether it needs more than one.
We cover this approach in value stream and process improvement. If the real blocker is the platform underneath, for example data trapped in an old SQL Server, see information and technology modernisation.
Build automation that fails safely
Every workflow will eventually meet something it was not designed for: a missing field, a supplier with a new invoice layout, a system that is down. Good automation plans for that:
- Alert a named person when a run fails, not a shared inbox nobody watches
- Keep a manual fallback so the work can continue
- Log every run so you can see what happened and when
- Review flows quarterly and retire ones nobody uses
As your number of flows grows, treat them like any other part of your workforce. They need an owner, permissions and a review. We explore that idea in managing non-human resources.
Where Cyber Samurai helps
We design, build and support Power Automate workflows for UK organisations, from single approvals to integrations with SQL Server, Azure and line-of-business systems. Our Automation Opportunity Assessment reviews your processes and licences, then gives you a prioritised list of what to automate first and what it will take.
Learn more about our automation expertise, or see how automation fits our wider operational excellence approach.
Keep reading
