Automating internal purchasing: from an email request to a supplier PO in 24 hours

The purchase request that travels through five inboxes

In a company of 50-250 people, buying something ordinary — a laptop, a spare part, 200 meters of cable — follows a path nobody ever designed. Someone writes an email or a chat message saying "we need...", a manager replies "ok", finance asks whether it's in budget, purchasing hunts for three quotes, and eventually the invoice lands in accounting with no one able to say who approved what.

The numbers we consistently find when we map the flow:

• 40-120 purchase requests per month, of which 60-75% arrive with no standard format: free-text email, chat message, or a hallway conversation
• 3-9 working days of internal lead time from request to a PO actually sent to the supplier — time during which almost nothing happens except waiting for a reply
• 15-30% of orders placed without formal approval (maverick buying), because "it was urgent" — typically 5-12% of annual indirect spend
• 25-40% of supplier invoices arrive with no matching order, which turns every month-end close into a hunt for confirmations
• 2-4 hours per week per person involved lost chasing approvals, sending reminders, digging up old quotes from an inbox

The cumulative effect isn't just wasted time. It's that nobody can answer a simple question: how much did we spend on category X this month, and who decided it.

What an automated purchasing flow actually does

Automating procurement doesn't mean software that buys things on its own. It means one clear path with structured data, in five steps:

1. A structured request — a short form, not an email: what, how many, which cost center, needed by when, with a justification. The data is entered once and travels onward without retyping.

2. Automatic budget and contract check — the system knows the remaining budget on the cost center and checks whether the item already sits in a negotiated framework contract. If it does, the quoting step is skipped entirely.

3. Threshold-based approval — each request goes to exactly the right people based on value and category, with an SLA and automatic escalation when nobody responds.

4. Quoting and comparison — for requests above threshold, the system sends the RFQ to suppliers in that category and lays the responses out in a comparable table: price, lead time, payment terms.

5. PO, receiving and matching — the order is generated in the ERP, sent to the supplier, receipt is confirmed on a phone in the warehouse, and the invoice is matched automatically against order and receipt (3-way match).

The difference from today isn't the speed of any single step. It's that nothing sits in someone's inbox without a deadline attached.

Why Excel plus email doesn't scale

Nearly every company tries the cheap version first: a shared spreadsheet for requests and an email chain for approvals. It fails predictably, for three reasons:

• There's no state. An approved email changes nothing in any system. A human has to read the approval and act on it manually — and if that person is on leave, the request evaporates.
• There's no usable history. After a year you have 4,000 emails, not a database. You can't answer "which supplier delivered on time most consistently over the last 12 months" without a full day of manual work.
• There's no time pressure. An email doesn't escalate itself. A workflow with an SLA does: after 24 hours without a response, the request moves up a level automatically, with a notification.

Case study: a 140-person manufacturer

An industrial components manufacturer we worked with at NEXVA SYSTEM had ~95 purchase requests per month and two people in purchasing who spent most of their day acting as email dispatchers.

What we built:

• A request form in the internal portal, with a catalog for repetitive consumables (over 300 items already at contracted prices)
• A four-tier approval matrix, with automatic escalation after 24 hours and automatic delegation during holidays
• Two-way ERP integration: real-time budget consumption, automatic PO generation after the final approval, warehouse receipt confirmed by barcode scan
• A lightweight supplier portal: suppliers receive the RFQ, reply in a form, and their quotes flow straight into the comparison table
• A spend dashboard by category, cost center and supplier, refreshed daily

Results after 5 months:

• Average internal lead time: from 7.2 days to 1.4 days; for catalog items, under 4 hours
• Orders placed without formal approval: from 22% to 4% — not through stricter rules, but because the approved path became faster than going around it
• Invoices matched automatically against order and receipt: 78%, up from zero
• Purchasing time recovered: ~30 hours/month, redirected into actual supplier negotiation
• The unplanned but most profitable effect: the dashboard revealed that the same consumable was being bought from 6 different suppliers at prices varying by up to 31%. Consolidating to two suppliers saved ~2,400 EUR/month

Thresholds and rules decide whether the system gets used

The technical part is straightforward. The part that decides success is rule design. What works in practice:

• Realistic thresholds: under 500 EUR — a single approval from the direct manager. 500-5,000 EUR — department head plus purchasing. Above 5,000 EUR — add the finance director. Above 25,000 EUR — two signatures and mandatory quoting.
• A catalog for the repetitive stuff: everything bought monthly at contracted prices belongs on a fast track with a single confirmation. If you treat a paper order like a capital investment, people will route around the system.
• An SLA on every step, with automatic escalation. A workflow without deadlines is still an inbox, just a more expensive one.
• Automatic delegation during holidays, driven from the HR system. Most real bottlenecks originate here.

What it costs and when it pays back

For a company with 50-250 employees and 50-150 monthly requests:

| Component | Cost |

|-----------|------|

| Process analysis and approval matrix | 2,000-4,000 EUR |

| Request forms, internal catalog and approval engine | 4,000-7,000 EUR |

| ERP integration: budget, POs, receiving, 3-way match | 5,000-9,000 EUR |

| Supplier portal and quote comparison | 3,000-6,000 EUR |

| Spend dashboard plus maintenance | 200-450 EUR/month |

Payback has two components. Time: 25-35 hours/month saved at a loaded cost of 15-20 EUR/hour is 5,000-8,000 EUR/year. Direct money: visibility into indirect spend typically removes 4-8% of it in the first year, through supplier consolidation and the elimination of off-contract buying. On 600,000 EUR of annual indirect spend, that's 24,000-48,000 EUR. The second component pays for the project — not the first.

The mistakes that kill procurement projects

• Too many approval levels. Each extra approver adds roughly a day and lowers adoption. If someone approves 100% of what reaches them, that's not a control — it's a delay.
• No catalog. If 70% of requests are repetitive but handled as exceptions, the system will be experienced as bureaucracy.
• Dirty supplier data. Duplicates, missing tax IDs, unknown payment terms — any report built on top of them will be challenged in the first meeting. Clean the supplier master first, not later.
• No baseline. If you don't know your current lead time and your share of invoices without a PO, you won't be able to prove anything in quarter two.

How to start

1. Measure for two weeks: how many requests come in, through which channels, how long each step takes, how many invoices arrive without an order.

2. Classify the spend by category and see where the money actually goes — usually 20% of categories cover 80% of the value.

3. Write the approval matrix with finance and department heads, using four thresholds at most.

4. Start with structured requests and approvals, no supplier portal. Value in 4-6 weeks, minimal risk.

5. Add ERP integration and 3-way match only once the approval flow is used consistently across all departments.

Purchasing is one of the few processes where automation delivers operational speed and direct savings at the same time — savings you can point to on an invoice. And the first useful version doesn't need a year-long project. It needs a form, four thresholds, and one clean ERP integration.

Want to find out how long the path from request to PO takes in your company today, and how much of your indirect spend is slipping out of control? Book a free consultation.