Approval flow for purchase requestssample project
Purchase approvals that used to be chased over e-mail move to Teams. They reach the right people based on the amount, and the result is logged in the list and the ERP on its own.
Approval requestPower Automate · Teams
Flow log
- Request opened
- Manager decision
- Finance decision (over 50,000 TL)
- Logged and sent to ERP
- Requester e-mailed
Still doing this by hand?Set this up in your company
- Stack
- Power Automate, Microsoft Teams, SharePoint, Logo ERP
This is a sample flow, not real client work. The model shows how such a system works, and the people and data in it are samples too.
Problem
In many SMEs purchase requests travel by e-mail or word of mouth. Nobody knows whose desk a request is waiting on or who approved what and when. Approved requests are then typed into the ERP by hand.
Solution
- An employee opens a request from a form, and it lands in a SharePoint list as “pending”.
- Power Automate sends it to the line manager as a Teams approval card.
- Above a set threshold (e.g. 50,000 TL) a second approval goes to the finance director.
- The result is logged in the list, and an approved request creates a purchase order in the ERP.
- The requester gets the outcome, with the rejection reason if there is one, by e-mail. Every step is recorded with who and when.
How it would work in your company
- The flow is built in your own Microsoft 365 tenant. Requests live in your SharePoint list and approvals in the Teams your people already use.
- Approvers, amount thresholds, departments and list columns follow your rules. Someone can cover for a manager on leave, and pending approvals can get reminders.
- Whether the ERP purchase order can be created automatically depends on your ERP and its version. We settle that in the first call.
- You get a short walkthrough video at handover, and fixes are free for the first 30 days.
To see how many hours a month chasing approvals costs you: Cost of manual work.