Approval Workflow in Purchasing: Multi-Stage Without Delays

Multi-step approval processes are intended to provide oversight but usually result in delays. The problem rarely lies with the system itself, but rather with the rule behind it: If every order must be approved, every order becomes slow. This article outlines the architecture that makes approval the exception—including a ready-to-use approval matrix and a system comparison.

Multi-level approvals only slow down procurement if every order goes through the workflow. The faster approach involves setting budget limits for each cost center: Orders within the limit are processed without approval; only orders that exceed the limit are routed through tiered thresholds. Approval thus becomes the exception rather than the rule.

Key points at a glance:

• Four levels of control apply before approval: product range, budget, value threshold, and cost center. Each level that applies control in advance saves one approval step.
• An approval matrix with three to four value levels is sufficient for most medium-sized companies.
• Procurement suites can map hierarchies of any depth—this is their strength and, at the same time, the reason for long processing times.
• Real-time budgets prevent overspends before they occur. Our customers report a 20 to 35 percent reduction in budget overspends.
• The approval logic must also apply to external ordering systems and requests for quotes; otherwise, that is precisely where compliance gaps arise.

The best approval is the one that doesn’t have to happen

Introducing approval levels doesn’t solve a control problem—it just pushes it further down the queue. Every approval involves two steps: one for the requester, who has to wait, and one for the approver, who reviews an order to which they usually can’t contribute anything.

Definition: An approval workflow in purchasing is the chain of rules that determines which purchase orders, starting at a certain value, must be approved by which authority before they are sent to the supplier.

The crucial question, therefore, is not “How many levels do we need?” but “How many orders actually need to go through the workflow?” In practice, this number is significantly lower than what most purchasing guidelines stipulate. An order for screws totaling 40 euros from the catalog associated with a cost center that has a budget limit does not require a signature.

This is precisely where the connection to the actual problem lies: The more cumbersome the official route, the more attractive the unofficial one becomes. An overly strict approval process is one of the most reliable drivers of maverick buying.

Four levels of rules determine the outcome before anyone has to approve it

Set the rules as early in the process as possible. Every level that takes effect in advance removes a decision from the workflow.

On our platform, these levels are handled by two modules: product range restrictions and approval workflows come from the Marketplace Package, while budgets and cost centers come from the Controlling Package. Budgets can be assigned to cost centers, users, or product groups and combined in any way—for example, a personal budget for personal protective equipment within a department’s budget.

Tip: Synchronize the cost center structure automatically from the ERP system instead of maintaining it twice in the procurement platform—otherwise, approvals will be processed against outdated cost centers.

Here’s how to set up the approval matrix: four rows are enough

An approval matrix assigns exactly one instance to each purchase order value. Three to four levels are sufficient for most medium-sized companies—each additional level extends the turnaround time without measurably reducing risk.

The following example is intentionally kept simple. Adjust the value thresholds to match your purchasing policy, but keep the first row: it’s the reason the process remains fast.

Three factors determine whether this matrix works in practice:

• Substitution policy: Each level must have a designated substitute. Without one, purchasing comes to a standstill as soon as someone goes on vacation.
• Time-based escalation: Define what happens after 48 hours without a response—automatic escalation to the next level is better than making follow-up calls.
• Value threshold per order, not per line item: Otherwise, requesters will split orders until they fall below the threshold.

Real-time budgets eliminate half the approval chain

A budget that only becomes visible at month-end is not a control tool, but merely a notification. That’s why a budget with real-time consumption data provides more control than any additional approval level ever could.

The mechanism behind it is simple: The spending status updates with every order. If a cost center reaches a critical threshold—say, 85 percent—those in charge see it on the dashboard. If the threshold is exceeded, orders are automatically halted and can only be placed again with special approval.

Key Fact: Our customers report 20 to 35 percent fewer budget overruns and 15 percent more accurate financial planning. For an indirect procurement budget of two million euros, this translates to approximately 300,000 euros in better-allocated funds—as detailed in the Budget Control in Procurement.

The case study on the Overview of Departmental Budgets. For companies with multiple plants, the case study on decentralized ordering with centralized approval provides a more detailed comparison.

Which systems support multi-level approvals?

All reputable procurement systems can handle multi-level approvals based on order value and cost center. The difference lies not in whether this is possible, but in the effort required to set up the rules—and in how much configuration you’ll be responsible for afterward.

The honest assessment: If you need to map approvals across group companies, direct materials, and service contracts within a single set of rules, there’s really no getting around using a suite. For indirect materials and C-parts in medium-sized businesses, this scope of functionality is the reason why implementation projects fail—not the solution to the problem.

Those who want to keep approvals within the ERP system can combine both: via OCI Punchout and the SAP integration, the purchase requisition is created in SAP, the approval process takes place there, and the purchase order is then sent to the supplier via the platform.

The gap arises where the workflow ends

An approval process is only as robust as its weakest link. In most companies, this isn’t catalog ordering, but rather the side channels: vending machines on the production floor, direct orders from small suppliers, and requests for quotes sent via email.

To prevent a compliance gap from arising there, the same rules must apply. External ordering systems are therefore integrated into the existing approval processes, and requests for quotes follow the same workflow from the initial request through to the order.

The fact that cost transparency in the indirect procurement sector remains one of the greatest untapped opportunities is also confirmed by the Deloitte’s global CPO survey. Anyone wishing to quantify the effort behind individual ordering processes more precisely can find the measurement framework at HTWK Leipzig for managing indirect procurement.

Checklist: Setting Up a Six-Step Approval Workflow

• Import the cost center structure from the ERP and synchronize it automatically
• Set budget limits for each cost center and define warning thresholds
• Limit product assortments by team so that unapproved items are not visible at all
• Set up an approval matrix with a maximum of four approval levels, with limits set per order rather than per line item
• Specify delegation and time escalation for each level
• Review secondary channels: vending machines, small suppliers, and requests for quotes

If more than one in five orders goes through an approval stage, the budget limits are set too tightly—not the approval chains too short.

Conclusion: Rules up front instead of signatures at the end

A good procurement approval workflow isn’t defined by the number of levels, but by how few orders have to go through them. Budget limits, product range restrictions, and a streamlined approval matrix handle most of the control before anyone has to approve anything.