Microsoft SharePoint

Purchase Order Approval Workflows: 6 Common Use Cases

Common Use Cases of Purchase Order Approval Workflows for Procurement Teams

A purchase order approval workflow routes each purchase request to the right approver, applies your spending rules automatically, and keeps a record of every decision. These six patterns are the ones procurement teams usually automate first. Each has a routing rule you can reuse.

A purchase order approval route: the request is raised, the budget is checked automatically, the manager approves, finance approves if the amount is over the limit, and the purchase order is sent to the supplier.

1. Approval by amount

The most common rule. Requests under a set value go to the line manager only. Higher values add finance, and the highest add a director. Keep the limits in a list, so they can change without editing the workflow.

2. Budget check before approval

Before a person sees the request, the workflow compares it with the remaining budget for that cost centre. Requests that exceed the budget are flagged or sent to a different approver. This saves approvers from signing things that finance will reject later.

3. Capital and operating spend

Capital purchases usually need more levels of approval and a business case, while operating purchases can be quick. The request form asks which type it is and the workflow takes the matching route.

4. Urgent purchases

Some purchases cannot wait. Allow an urgent route with a lower approval limit and a mandatory reason, and then report on how often it is used. If urgent becomes the norm, the normal route is too slow.

5. New supplier onboarding

Before the first order, collect the supplier details and run them through checks such as tax registration and bank details, with approval from procurement and finance. Approving the supplier once is easier than reviewing it on every purchase.

6. Three-way match before payment

Before an invoice is paid, the workflow compares the purchase order, the goods receipt and the supplier invoice. When all three agree, it goes forward. When they do not, it goes to a person to resolve.

How to build it on Microsoft 365

  • Request form: a Power Apps or SharePoint form that collects supplier, amount, cost centre and reason.
  • Routing and approvals: Power Automate, with the limits and approvers held in SharePoint lists.
  • Record: each request is a SharePoint item with its approval history, status and attachments.
  • Reporting: a Power BI view of cycle time and spend by department.

For the build details, see approval workflows in Power Automate and procurement with Power Apps. You can also look at our approval workflow product.

Planning a purchase approval workflow?

Tell us your approval levels and limits. We will show you a working design on Microsoft 365.

Talk to us

Frequently asked questions

Do we need an ERP to automate purchase approvals?

No. You can run the request and approval steps on Microsoft 365 and connect to your ERP or accounts system later, if you need to post orders there.

How many approval levels should we have?

As few as your policy allows. Two levels cover most organisations, with a third only for the highest values.

How do we stop people splitting orders to avoid limits?

Report on repeated requests to the same supplier within a short period, and review them. A rule on cumulative spend per supplier helps as well.

Can we keep our current purchase order numbers?

Yes. The workflow can take your numbering from the system you use now, or generate numbers in the same format.

Talk to an expert