Supplier changes, payment requests and purchase requests followed different approval paths. Email and manual follow-up made it harder to see who needed to act and where a request had stopped.
Approvals that follow the right path.
A Microsoft 365 approval application that directs business requests to the right reviewers and keeps their status visible.
STARBUCKS / Project overviewRequestors and reviewers can work from one process, with a visible record of each decision and fewer manual hand-offs.
request types on one approval process
Supplier information, payment and purchase requests.
approvals chased by email
Routing rules send each request to the right reviewer automatically.
of every approval decision
Status and completed decisions are held in SharePoint Online.
What the work covered.
A Microsoft 365 application for supplier information, payment and purchase approvals, with request records held in SharePoint Online.
The parts that had to work together.
Each request type followed a different route through the organisation. The workflow needed to apply those rules consistently while keeping the next action and current status clear.
- 01
Requestor
Supplier, payment or purchase request
- 02
Approval workflow
Rules, hierarchy and decision history
- 03
Business record
SharePoint status and completed decision
The build.
- 01A Power Apps interface for supplier, payment and purchase requests.
- 02Power Automate approval workflows.
- 03Routing rules based on request type and approval hierarchy.
- 04SharePoint Online records holding status and decision history.
The features.
- Supplier information approvals
- Payment and purchase requests
- Rule-based approval routing
- SharePoint request records
Let’s look at your workflow.
If your team is working through a similar enterprise problem, tell us about your users, existing systems and what needs to change.


