The best purchase approval workflow depends on where you are today. For Controllers at 100 or more employees still running approvals through email or Slack, design comes first. Thresholds, roles, escalation rules, and policy, then a system that enforces them. For companies under 50 with a single AP person, a simple manager-approves-everything rule works. 

For enterprise teams (1,000+ employees) with a dedicated procurement function, source-to-pay platforms like Coupa or SAP Ariba are the fit. For mid-market finance teams (100 to 1,000 employees) on QuickBooks, Sage Intacct, or NetSuite, ProcureDesk’s purchase approval software enforces the workflow you design, with go-live in 2 to 3 weeks.

TL;DR

• The diagnosis: Most Controllers at 100+ employees don’t have a broken approval workflow. They have no workflow. Email approvals work at 30 employees, collapse at 150.
• The wrong fix: Buying procurement software without designing the workflow underneath just digitizes the same email-based chaos.
• The right sequence: Design first. Thresholds, roles, escalation rules, policy. The system enforces what you designed.
• The operating rule: Auto-approve the routine. Route the meaningful. Escalate the strategic. Set thresholds on 12 months of your actual spend data, not a template.
• The cost of doing nothing: Email-based approvals at 100+ employees consume 30 to 60 hours of avoidable AP work per month. $15K to $30K of annual finance team time on reconstruction.
• The outcome: Mid-market teams that move to system-enforced workflows typically see a 40% reduction in cycle time in the first quarter and recover 7 to 10 hours per week.
• The bottom line: Design the workflow before you automate. Thresholds first, system second. Software is the easy part.

In our onboarding work with hundreds of mid-market finance teams across biotech, logistics, charter schools, and manufacturing, the same pattern shows up. Companies using ProcureDesk’s purchase order approval software typically see a 40% reduction in cycle time within the first quarter. The difference isn’t the software. It’s the workflow design behind it.

This guide walks through how to build a purchase approval workflow from scratch. Thresholds, roles, policy language, escalation rules, and what breaks when you skip the design step.

What Is a Purchase Approval Workflow?

A purchase approval workflow is a defined process that every purchase request must pass through before a purchase order is issued to a vendor. It defines who approves what, at what dollar amounts, and in what sequence.

A complete workflow has four components:

• Trigger: what kicks off the process (any request, or only those above a threshold)
• Approver routing: who approves at each level, based on amount, department, or category
• Escalation rules: what happens when approvals stall or an approver is unavailable
• Documentation: where every decision is recorded for audit purposes

Without these, approvals happen informally. With them, they’re documented, consistent, and auditable.

Why Purchase Approval Workflow Matters at 100+ Employees

At 40 employees, one manager knows who’s buying what. At 200 employees across six departments, informal processes collapse and four things break:

• Budget overruns discovered after invoices hit, because email approvals don’t check live budget
• Audits become reconstruction: Controllers spend 20+ hours rebuilding documentation that should have been captured the first time
• Approval authority dilutes through informal email forwarding
• Month-end close stretches because AP can’t run 3-way match without a PO

Framework: The Spend Visibility Gap. The wider the window between approval and invoice, the harder it is to forecast cash flow or close the books on time.

How does your spend control stack up?

Before you redesign the workflow, find out where you actually stand. The Spend Control Readiness Scorecard is a free 5-minute assessment built for Controllers and CFOs. You’ll see:

• Where your approval workflow is leaking time and money today
• Whether your audit-readiness would hold up under a surprise review
• Which two gaps to fix first for the biggest impact on month-end close

Step 1: Define Your Threshold Framework

The most important design decision is the threshold framework. The goal isn’t to approve everything. It’s to approve the right purchases at the right level, and auto-approve everything else.

The Pareto Method (1 Hour, Grounded in Your Spend Data)

1. Pull 12 months of purchase history from QuickBooks, NetSuite, or Sage Intacct. Include date, amount, vendor, department.
2. Find the 80/20 line. Sort by dollar amount, add a running total column, find the point where 20% of transactions by count account for 80% of total spend. That’s your escalation threshold.
3. Set the auto-approval floor. Find the dollar amount where 70 to 80% of your transactions by count fall. Purchases below this are routine and don’t justify multi-step review.
4. Define the middle band. Everything between the floor and the escalation threshold gets one level of human review.

Practical example: transactions above $15,000 represent 18% of your count but 82% of total spend. Transactions under $750 represent 55% of count and 9% of spend. Framework becomes: under $750 auto-approve, $750 to $15,000 manager approval, over $15,000 Controller or CFO approval. You just eliminated human review from 55% of your transaction volume while keeping oversight on 82% of your spend exposure.

Starting Framework (If You Don’t Have Spend Data Yet)

For a 100 to 300 employee company at $20M to $75M revenue:

Category Overrides That Override Dollar Thresholds

• New vendors: any amount requires at least one human review
• Software and subscriptions: route to IT for security review regardless of cost
• Capital expenditures: Controller review above $2,500
• Recurring commitments: add a contract review step

Step 2: Define the Roles

Vague roles like “management approval required” create the same chaos as no process at all. Define five roles:

• Requestor: creates the request, provides justification, vendor, amount, budget code
• Approver Level 1: department manager. Confirms the purchase is justified and within budget
• Approver Level 2: director or VP. Reviews higher-dollar purchases for budget impact and strategic fit
• Finance Reviewer: Controller or AP manager. Verifies budget code and policy fit before PO issuance
• Final Approver: CFO. Reviews major capital commitments and policy exceptions

Not every purchase hits all five roles. A $300 office supply order needs Level 1 only. A $50,000 equipment purchase goes through all five.

Backup approvers are mandatory. For every role, define a primary, a backup that activates automatically if the primary doesn’t respond, and a maximum hold time before the request escalates. In email-based workflows, this is almost never formalized, which is one of the strongest arguments for a system-enforced workflow.

Step 3: Write the Policy

A purchase approval policy should be one document, two pages maximum. It needs to answer, without interpretation:

• What is the purpose, and who does it apply to?
• What requires a purchase request before a purchase can be made?
• What are the approval thresholds by dollar amount?
• Who can approve at each level?
• What documentation must accompany a request?
• What happens when the normal approver is unavailable?
• What happens when a purchase is made without following the process?
• How are emergency purchases handled?

If the policy requires interpretation, rewrite it. Ambiguous policies get applied inconsistently, which is the same as not having one. All purchases regardless of payment method (including company credit card) must follow the workflow. Card purchases are not exempt. That’s the most common gap.

Step 4: Design Escalation Rules

Escalation answers one question: what happens when an approver doesn’t respond? Without rules, purchase requests stall, employees follow up manually, and operations slow down. This is the most common failure point in otherwise well-designed workflows.

The key is automatic firing. In email-based workflows, escalation depends on someone noticing the delay and manually forwarding. In a system-enforced workflow, it’s a rule. It runs whether anyone notices or not.

Step 5: Why Email-Based Approvals Break at Scale

A biotech company with 120 employees runs approvals through email. A lab manager emails her director for reagents. The director responds “looks fine” from his phone 6 hours later. Nobody checked budget. The reagents are ordered.

Three weeks later, the invoice arrives in AP. No PO to match. The AP manager spends 45 minutes decoding a 14-message thread to confirm what was approved and by whom. At 80 invoices a month, that’s 60 hours of avoidable work.

Four things specifically break:

• No audit trail that holds up: auditors need a timestamp, an approver name, and a document reference. Email gives you fragments of that. Permanent records need a system.
• No budget check at approval: managers approve from memory, with no live view of committed spend. Departments run over budget with well-intentioned approvals at every step.
• Approval authority dilutes: informal email forwarding to colleagues erodes the framework. Over time, anyone can approve anything with a forwarded thread.
• Reporting requires manual searches: when the CFO asks how much was spent on lab supplies in Q2, someone has to dig through inboxes.

Step 6: Put the Workflow Into a System

A policy in a shared drive doesn’t enforce anything. A purchase requisition system that encodes the rules enforces them automatically, every purchase, every employee, every time.

In ProcureDesk, the workflow runs as eight steps:

1. Request submitted by an employee, manually or via punchout (Amazon Business, Grainger)
2. Workflow engine identifies approvers based on amount, department, vendor status, category
3. Budget check runs in real time. Over-budget requests flag at submission, not at month-end
4. Approvers notified by email, mobile push, or Slack. One-click approve, no login required
5. Escalation fires automatically if the approver doesn’t respond within the configured timeline
6. PO generated and sent to the vendor without a manual creation step
7. Audit trail captured with timestamp and user identity on every action
8. 3-way match completed automatically: PO + receipt + invoice, discrepancies flagged

School in the Square, a charter school with a small finance team, had a two-day average approval cycle before ProcureDesk. After configuring the workflow in the system, it came down to four hours. For Equality Charter School, 87% of PO cycle time was eliminated.

ProcureDesk integrates natively with QuickBooks, Sage Intacct, NetSuite, Microsoft Business Central, and Xero. Approved POs sync automatically. Invoice data syncs after 3-way match. Your chart of accounts, departments, and GL codes populate from your accounting system.

How ProcureDesk Compares to Other Approval Tools

When a Controller looks for software to enforce purchase approvals, the market splits into four buckets. Most articles on this topic skip the comparison entirely.

Coupa, SAP Ariba. Enterprise source-to-pay platforms. Built for 1,000+ employee procurement teams with dedicated IT. Implementation runs 6 to 12 months. Too heavy for the 100 to 1,000 range.

Tradogram, Spendwise. SMB-tier PO tools. Light on approval depth, no automated 3-way matching. Fine at 25 employees. Underbuilt by the time you cross 100.

Ramp, Brex. Corporate card and post-swipe controls. They sit after the purchase commitment, not before. Useful complements to a workflow that enforces purchase requests before money moves. No punchout catalogs, no goods receipt, no 3-way matching.

Bill.com. Sits after the invoice arrives. ProcureDesk sits before. They’re complementary. ProcureDesk integrates with Bill.com so the payment step uses Bill.com’s rails while approval and 3-way matching happen upstream.

ProcureDesk, Procurify, Precoro. The mid-market procurement and AP automation tier. Procurify optimizes for the requester experience across the organization. ProcureDesk optimizes for the Controller’s workflow. ProcureDesk has stronger 3-way matching, deeper QuickBooks support (Desktop and Enterprise, not just Online), and 200+ punchout supplier catalogs.

If you’re at 1,000+ employees with a procurement team, look at Coupa. If you’re under 50 with a single AP person, Tradogram works. If you’re in the 100 to 1,000 employee range, buying physical goods from vendors, and your Controller is responsible for audit-ready documentation, that’s ProcureDesk’s specific job.

Ready to replace your email-based approvals with a workflow that enforces itself?

ProcureDesk is a procurement and AP automation platform built for mid-market finance teams (100 to 1,000 employees). It controls spending before the invoice arrives, with approval routing, real-time budget checks, and automated 3-way matching. Across hundreds of customers, ProcureDesk reduces month-end close from 10 days to 4 days on average. Native integration with QuickBooks, Sage Intacct, NetSuite, Microsoft Business Central, and Xero, with implementation in 2 to 3 weeks.

Resources

• Purchase Order Approval Software
• Purchase Requisition System
• Guide to Purchase Order Approval Process
• Procurement Approval Workflow: From Days to Hours
• How to Automate Purchase Orders