Demo system
Purchase Approval System
From request to approval to reporting — without chasing emails. This is a demonstration of the architecture, not a client case study.
System architecture
Before
- Employee emails a manager
- Manager asks for missing information
- A spreadsheet is updated
- Approval is chased manually
- Finance receives another email
- Status is unclear
- The weekly report is prepared by hand
After
- Employee submits a structured request
- Rules determine the approver
- Approval arrives in Teams
- Overdue requests escalate
- The record stays current
- The requester is notified
- The management view updates
Architecture
- Employee
- Power App
- Dataverse
- Power Automate
- Approval logic
- Teams
- Decision
- Dataverse
- Power BI
Copilot · optional
Connected to the record and the flow. It does not decide the approval.
Copilot ↔ Dataverse / Power Automate
- “Which requests have been pending for more than three days?”
- “Show me Engineering requests over $10,000.”
- “Remind the approver for PR-102.”
Example approval rules
- Under $5,000
- Manager
- $5,000–$25,000
- Director
- Over $25,000
- VP
- Overdue > 48 hours
- Reminder
- Overdue > 72 hours
- Escalation
- Rejected
- Notify requester
- Approved
- Update record and notify finance
Illustrative thresholds for this demo. A real engagement uses the client’s policy.
What Power BI can show
- Total requests
- Pending value
- Average approval time
- Overdue requests
- Approval rate
- Requests by department
Measure names only. Not results from a client engagement. A demo video can be attached here when it exists.
Your process