Purchase Requisition Approval process diagram
This is a worked example. Wavelength built the diagram below from the description on this page. Nobody drew it by hand.
What was said
The requester submits a purchase requisition. The manager reviews it and decides whether to approve. If the manager approves, it goes to procurement. Procurement checks if the budget is available. If the budget is there, procurement creates a PO in the ERP. If the budget is not there, finance reviews it for a reallocation. Once the PO is created, procurement sends it to the vendor and the process is complete.
The diagram
What is in this flow
- Systems: None.
- People and teams: Requester, Manager, Procurement, Finance.
- Decisions: Manager Approves?, Budget Available?.
- Size: 13 steps and 14 connections.
Steps
- Requester
- Submit Requisition (Requester)
- Manager
- Manager Review (Manager)
- Manager Approves?
- Procurement
- Check Budget (Procurement)
- Budget Available?
- Finance
- Review Reallocation (Finance)
- Create PO in ERP (Procurement)
- Send to Vendor (Procurement)
- PO Complete
Mermaid code
Copy this into any Markdown file, GitHub README, or Mermaid Live to render the same flow.
flowchart TD
n1(Requester)
n2([Submit Requisition])
n3(Manager)
n4[Manager Review]
n5{Manager Approves?}
n6(Procurement)
n7[Check Budget]
n8{Budget Available?}
n9(Finance)
n10[Review Reallocation]
n11[Create PO in ERP]
n12[Send to Vendor]
n13([PO Complete])
n1 -->|submits| n2
n2 -->|routes to| n3
n3 -->|reviews| n4
n4 -->|decides| n5
n5 -->|Yes| n6
n5 -->|No, rejected| n13
n6 -->|checks budget| n7
n7 -->|decides| n8
n8 -->|Yes| n11
n8 -->|No| n9
n9 -->|reviews| n10
n10 -->|reallocated| n11
n11 -->|creates PO| n12
n12 -->|sends to vendor| n13
Map your own process
Describe your version out loud, or paste the transcript of a call. Wavelength draws the flow as you talk, and you can edit it by voice, by prompt, or by hand.
Every new account starts with 7 days of Pro. No card needed.
This example is part of our guide for business analysts.