Purchase Order Approval Delays — How to Find and Fix Bottlenecks
Published: April 14, 2026
A purchase requisition is raised on Monday. The department head approves it by Wednesday. A purchase order is created on Thursday. Then it sits. The CFO is travelling. The finance controller is reviewing last quarter's numbers. The PO needs two levels of approval and neither approver has looked at it. Two weeks later, someone in procurement follows up with the vendor — who has already increased prices. The organisation either pays more or starts over.
This pattern repeats in every organisation that has multi-level approval workflows without visibility into where things get stuck. The approvals exist for a reason — financial controls, segregation of duties, compliance with internal policies. But the controls create delays, and without measurement, delays become invisible.
This article explains how to make approval bottlenecks visible — through aging reports, SLA tracking, and approver-level analysis — so that governance does not come at the cost of operational speed.
1. The Invisible Queue
In most organisations, the person who raised a purchase requisition has no idea where it is in the approval chain. They know they submitted it. They know it has not been approved. But they cannot see whether it is sitting with the department head, the finance controller, or the CFO. They cannot tell if the delay is 2 days or 12.
This invisibility creates several problems:
- Follow-ups are manual and political. The requester calls the department head, who says "I approved it last week." The requester calls finance, who says "we haven't received it." Nobody can see the actual state.
- Urgent requests get the same treatment as routine ones. A procurement for a production-critical spare part sits in the same queue as a stationery order. The approver sees a list of pending items with no urgency context.
- Patterns are invisible. If one approver consistently takes 10 days while others take 1, nobody notices until the CFO asks why procurement takes six weeks.
- No accountability. When there is no measurement, there is no conversation about approval speed. The delay is accepted as "how things work."
2. Three Layers of Visibility
Solving approval delays requires three distinct types of reporting, each answering a different question:
2.1 Approval Aging — Where Is Each Document Right Now?
Approval aging answers the immediate question: which documents are pending, and for how long? The report shows every document currently in an approval workflow — purchase requisitions, purchase orders, and goods receipt notes — along with:
- Which approval level the document is currently at
- Who the approver is at that level
- How many days the document has been pending at that level
- The total elapsed time since submission
This per-level measurement is critical. A PO that has been pending for 10 days tells you there is a delay. A PO that spent 1 day at Level 1 and has been stuck at Level 2 for 9 days tells you exactly where the delay is.
2.2 SLA Breach Tracking — Which Approvals Have Exceeded Their Time Limit?
Aging tells you how long things have been waiting. SLA breach tracking tells you which ones have exceeded an agreed threshold.
Each level in the approval matrix can carry an SLA — the maximum number of days an approver should take to act. When configured:
| Level | Approver Role | SLA (days) |
|---|---|---|
| 1 | Department Head | 2 |
| 2 | Finance Controller | 3 |
| 3 | CFO | 5 |
A document that has been at Level 2 for 5 days when the SLA is 3 days is flagged as a breach — 2 days overdue. The SLA breach report aggregates these across all pending documents, providing a clear view of which approvals are overdue and by how much.
SLAs transform approval speed from a vague expectation ("approvals should happen promptly") into a measurable commitment. When the CFO reviews a report showing 12 SLA breaches this month, the conversation shifts from "things feel slow" to "Level 2 has a structural capacity problem."
2.3 Bottleneck Approver Analysis — Who Is the Constraint?
The third layer aggregates data by approver rather than by document. For each person who appears in any approval workflow, the system can show:
- How many documents are currently pending with them
- Average aging of their pending items
- Number of SLA breaches attributed to them
- Breakdown by document type (PR, PO, GRN)
This approver-level view reveals structural issues that document-level reports cannot:
- Over-assignment: An approver who appears in 15 different approval matrix codes is spread too thin. The fix is not "approve faster" — it is to redistribute approval responsibility.
- Absence without delegation: An approver on leave with no delegate creates a hard block. Documents cannot progress until they return.
- Awareness gap: Some approvers simply do not check the system regularly. They do not know documents are waiting. Notification delivery is the fix, not a bigger queue.
3. The Notification Layer
Reports identify bottlenecks after the fact. Notifications prevent them in real time. A well-designed approval notification system includes:
- Immediate notification: When a document reaches an approver's level, they receive an in-app notification and an email with a direct link to the document.
- Pending count on dashboard: The approver's landing page shows an unread count of documents awaiting their action. This is updated in real time — not daily or weekly.
- Dedicated queue: A "Pending for Me" view that consolidates all documents awaiting the approver's action across document types — PRs, POs, GRNs, service acceptances. One place to look, not four.
The goal is to make pending approvals impossible to miss. An approver should not need to remember to check the system — the system should actively inform them.
4. Procurement Cycle Time — The Broader Picture
Approval delays are one component of overall procurement cycle time — the duration from requisition submission to goods receipt. A structured system measures each stage independently:
| Stage | Start | End | Typical Range |
|---|---|---|---|
| PR Approval | PR submitted | PR approved | 1-5 days |
| PO Creation | PR approved | PO submitted | 1-3 days |
| PO Approval | PO submitted | PO approved | 2-10 days |
| Vendor Delivery | PO approved | Goods received | 7-30 days |
| GRN Processing | Goods received | GRN approved | 1-5 days |
When cycle time is broken down by stage, the bottleneck is obvious. If PR approval takes 2 days, vendor delivery takes 10 days, but PO approval takes 15 days — the problem is not the vendor. The problem is internal. Cycle time data, segmented by supplier, department, and classification, reveals patterns that aggregate numbers hide.
In many mid-market organisations, internal approval delays exceed vendor delivery times. The organisation blames the vendor for slow procurement while the real constraint is its own approval chain.
5. Structural Fixes — Beyond Reports
Reports make bottlenecks visible. Fixing them requires structural changes:
5.1 Right-Sizing the Approval Chain
Not every purchase needs three levels of approval. A configurable approval matrix can route based on amount, classification, and department — so a stationery order worth Rs 5,000 gets a single-level approval while a capital asset worth Rs 50 lakhs gets three levels. Reducing unnecessary levels is the single most effective way to reduce cycle time.
5.2 Bypass PO for Pre-Approved Items
Some items — annual maintenance contracts, recurring services — are pre-approved in the budget but still go through the full PR-PO cycle. A bypass mode that auto-creates and auto-approves the PO when the PR is approved eliminates an entire stage for these items. This matters most for AMC renewals: they have hard expiry dates, and an approval queue delay turns a routine renewal into an uncovered repair bill. The bypass should require a stated reason and should only be available in combined (all-lines-together) mode to prevent misuse.
5.3 Per-Line Approval
When a requisition has 10 lines and only 1 is contentious, the entire requisition should not wait. Per-line approval allows 9 lines to be approved and proceed to PO while the contentious line is discussed. This granularity prevents one line from blocking an entire procurement batch.
5.4 Approval Topology Choice
Some procurement decisions genuinely need all-or-nothing treatment — approve or reject the entire batch. Others benefit from line-by-line granularity. Offering both topologies (collective and line-level) as a per-requisition configuration lets the submitter choose the appropriate model without requiring a different workflow for each.
6. What to Measure and How Often
| Metric | What It Reveals | Review Frequency |
|---|---|---|
| Average PR approval time | Department-level efficiency | Monthly |
| Average PO approval time | Finance team responsiveness | Monthly |
| SLA breach count | Governance adherence | Weekly |
| Bottleneck approver list | Structural capacity issues | Monthly |
| End-to-end cycle time | Overall procurement efficiency | Quarterly |
| Cycle time by supplier | Vendor performance | Quarterly |
7. Frequently Asked Questions
What is an approval bottleneck?
An approval bottleneck is a stage in a purchase workflow where requisitions or orders stall because the approver is unavailable, the routing is unclear, or no one is tracking aging. Bottlenecks become visible only when the system reports which approver is holding what document and for how many days.
What causes purchase approval delays?
The three most common causes are approvers away from their queue (travel, leave, overload), no SLA tracking so delays stay invisible, and routing rules that send every purchase through the same chain regardless of amount or risk. Measuring time-per-level separates the causes and points to the fix.
How do you measure how long a purchase order has been stuck in approval?
Approval aging is measured from the moment the document enters a specific approval level. When a PO is submitted, it arrives at Level 1. The system records the timestamp. If the Level 1 approver has not acted after 3 days, the aging report shows that PO as "3 days pending at Level 1." When Level 1 approves and it moves to Level 2, the clock resets for that level. This per-level measurement pinpoints exactly where the delay is — it is not enough to know a PO has been pending for 10 days; you need to know it spent 2 days at Level 1 and has been stuck at Level 2 for 8 days.
What is an SLA breach in purchase approval?
An SLA (Service Level Agreement) breach occurs when an approver does not act within the configured time window for their level. Each level in the approval matrix can have an SLA — for example, Level 1 must respond within 2 days, Level 2 within 3 days. When the elapsed time exceeds the SLA, the system flags it as a breach. SLA breach reports show which documents are overdue, by how many days, and which approver is responsible. This transforms approval delays from an invisible problem into a measurable one.
Can you identify which approver causes the most delays?
Yes. Bottleneck analysis aggregates pending approval counts and aging data by approver across all document types — purchase requisitions, purchase orders, and goods receipt notes. If one manager has 15 pending approvals averaging 6 days each while others average 1 day, the data makes the bottleneck visible. This is not about blame — it often reveals structural issues: the approver may be over-assigned, on extended leave without a delegate, or simply unaware that documents are waiting.
How do approval delays affect procurement cycle time?
Procurement cycle time measures the duration from purchase requisition submission to goods receipt. Approval delays directly inflate this metric. A PR that takes 5 days to approve, followed by a PO that takes 7 days to approve, adds 12 days of wait time before a vendor even receives the order. Cycle time reports broken down by stage reveal whether the bottleneck is internal or external. In many mid-market organisations, internal approval delays exceed vendor delivery times.
Do approvers receive notifications when documents are waiting?
Yes. When a document reaches an approver's level, they receive both an in-app notification and an email notification (if their email is verified). The notification includes a direct link to the document. Approvers also have a dedicated "pending for me" view that shows all documents awaiting their action across all document types. Unread notification counts are updated in real time on the dashboard.