Automating Purchase Orders and Approvals

Automating Purchase Orders and Approvals

· by Panayot Dimkov

To automate purchase orders, you have to separate two processes that usually get mixed up: the purchase order, which exists so that what is needed arrives, and the purchase approval workflow, which exists to control spending before it is committed. Automating the first without the second speeds up buying and loses control; automating the second without the first adds bureaucracy and saves nothing. What works is a short request form, an approval matrix by amount — automatic below a threshold, routed to the right person above it — and orders issued and followed up without manual work.

The sign that the process is broken is easy to spot: the purchase order is created in the system after the goods have arrived, so that it matches the invoice. If that happens in your company, the problem is not the tool.

1The informal order

Many companies have a written purchasing process and a real one. The real one usually starts with an email or a phone call to the supplier and ends with someone in admin regularising it weeks later.

ConsequenceWhy it hurts
No prior spend control Approval arrives once the commitment already exists. At that point, approving is a formality
The invoice matches nothing With no order, automatic invoice matching is impossible and everything goes through manual review
Committed spend is unknown Available budget is an estimate, because what is ordered and not yet received is missing
You buy worse Without visibility there is no aggregated volume and no negotiation. You pay the urgency price
Before automating anything, one uncomfortable question needs an answer: why do people bypass the process? Almost always because the official process is slower than the need. Automating it as it stands will only speed up something people will keep avoiding.

2How to automate purchase orders: the full workflow

A well-built purchase order process has five stages, and only one of them is approval.

01
Request
A short form, reachable from a phone, with the minimum: what, how much, by when and against which cost centre. If requesting takes more than two minutes, people will go back to email.
02
Approval
Automatic below a threshold, and a targeted notification above it. With the amount, the supplier and the remaining budget visible in the notification itself.
03
Issuing the order
The order is generated and sent to the supplier automatically. This is where much of the administrative time is recovered, and it is one of the stages least often automated.
04
Follow-up
Supplier confirmation, committed date and an automatic alert when it slips. Chasing deadlines is one of purchasing's most repetitive tasks and one of the easiest to remove.
05
Goods receipt
Confirming what arrives against what was ordered, with differences logged. It is what later lets the invoice approve itself.

Stage 4 is often one of the most profitable and one of the least requested. Nobody has "chase the supplier" in their job description, but somebody does it every day.

3Designing the approval matrix

It looks administrative and it actually decides whether the system gets used or bypassed. Three criteria are enough for almost any small or mid-sized company.

  • By amount. With a threshold below which no human approval is needed. Setting it high feels risky, but a low threshold produces hundreds of de facto automatic approvals: people approve without looking.
  • By category. Office supplies and subcontracting should not follow the same path even when they cost the same.
  • By cost centre. Whoever answers for the budget should see the commitment, even if they are not the one signing.

And four mistakes that keep recurring:

🪜
Too many levels
Three signatures for 400 euros is a process people bypass. Every level adds days and diffuses responsibility: if four people sign, none of them looked.
🚧
A single approver with no backup
One person's holiday stops a department's purchasing. Temporary delegation has to be built into the flow, not resolved over messaging apps.
🕳️
No time-based escalation
If nobody responds, the request sits there forever. A rule is needed: after a deadline, notify the next level or the deputy.
📵
Approving requires logging into the ERP
A director who has to open a laptop and find an inbox will approve tomorrow. From email or a phone, they approve now.

4And the orders you receive

The other side of the counter has the same problem in reverse: customer orders arriving by email, each in its own format, with someone typing them into the ERP.

The workflow is symmetrical: extract the lines from the message or the attachment, validate references and prices against the catalogue, create the order as a draft and let a person confirm. When the customer is recurring and the format stable, the hit rate tends to be high and confirmation is a glance. We cover it in more detail in automating email and incident handling.

There is a benefit here that is commercial rather than operational: the time between the customer sending the order and receiving confirmation. Going from a day to ten minutes shows up in perceived service more than many internal improvements.

5What to measure

Four indicators are enough. Measure them before automating so you have something to compare against: it is the baseline we explain in how to calculate process automation ROI.

IndicatorWhat it reveals
Days from request to order issued The central indicator. Above two, people are likely to buy on their own
Share of purchases with no prior order Measures the informal process. It should fall; if it does not, the official route is still worse than the shortcut
Requests approved automatically Shows whether the threshold is right. Too low and everyone approves without looking
Orders received late Justifies automatic follow-up and lets you assess suppliers with data
Use casePurchasingAutomation

Frequently asked questions

Can I build the approval workflow outside the ERP?

Yes, and in many cases that is the sensible option. If the ERP's purchasing module is rigid or expensive in licences, the request and approval flow can live in an automation tool and create the order in the ERP only once approved. What matters is not ending up with two truths: the definitive order must exist in one place.

What automatic approval threshold is reasonable?

It depends on purchasing volume and each company's risk appetite, so there is no universal figure. The useful criterion is different: if the cost of reviewing a request exceeds the risk of not reviewing it, the threshold is too low. Reviewing 50-euro purchases one by one usually costs more in management time than what is at stake.

How do I stop people buying on their own?

By making the official route faster than the shortcut, not by banning the shortcut. A two-minute form with automatic approval below the threshold and the order issued the same day competes well. A three-signature, five-day process competes with nothing.

Can orders be approved from a phone?

Yes, and it is one of the things that most changes adoption. The approval has to arrive as a notification with everything needed to decide — amount, supplier, item, remaining budget — and be resolved with one tap. If it forces someone to open an application and search, the delay comes back.

What if my suppliers do not accept electronic orders?

They do not need to accept any special format. The flow can generate the order as a PDF and send it by email, which is what you already do by hand. The gain is that it is generated automatically, numbered automatically and logged — not the channel it travels through.

In short

These are two processes: ordering and approving. The system works when ordering is faster through the official route than through the shortcut, and when approving can be done from wherever the person is, with the information in front of them.

The stages that usually pay back most are not approval but issuing and follow-up: generating the order, sending it and chasing deadlines are purely repetitive tasks. And once the order exists in the system, the matching invoice can approve itself. That is how we approach AI process automation.

How many purchases happen with no order in your company?

It is the figure that best describes the state of the process. We review the request, approval and issuing workflow with you and tell you which stage to automate first.

Request a process analysis