A purchase request for EUR 800 can pass without much attention. By month-end, urgent orders, duplicate purchases and invoices waiting for confirmation make the problem much larger. An ERP procurement approval workflow determines who may initiate spend, who validates it and when a request may become a purchase order and invoice.
For finance, control means more reliable cash-flow forecasts and fewer surprises at period close. For operations, it must not mean waiting days for routine supplies. A good process is not the strictest one; it distinguishes routine buying, contractual commitments, urgent procurement and capital investment.
Where procurement approvals usually break
Procurement often starts in chat or email: “We need this now.” A manager replies “approved”, an employee orders from the supplier and finance later tries to discover who authorised the spend and which budget owns it. Another common fault is approval by title rather than responsibility: the director receives everything while a project lead never sees costs affecting project margin.
Business Central can connect the request, approval, purchase order, receipt and incoming invoice in one traceable chain. Software alone cannot repair poorly defined rules. Without clear owners, limits and exceptions, ERP merely digitises existing confusion.
The workflow, step by step
A practical workflow begins with the purchase request, not the invoice. The requester enters the supplier where known, item or service, quantity, expected price, required date and dimensions such as cost centre, project or business unit.
| Step | What is checked | Who acts |
|---|---|---|
| 1. Request | Purpose, quantity, project and budget code | Requester |
| 2. Operational check | Stock availability or existing contract | Purchasing or warehouse |
| 3. Budget control | Available budget and planned spend | Budget owner |
| 4. Finance approval | Amount, account, tax treatment and cash flow | Finance |
| 5. Final approval | Threshold or special category | Director, CFO or board |
| 6. Execution | Create and send the purchase order | Purchasing |
Not every request needs all six steps. Routine items below a threshold may need only cost-centre approval. Capital expenditure, uncontracted suppliers or higher-risk categories require additional checks. The decision must stay attached to the document, showing who approved, when, for which amount and whether the document later changed.
Rules that follow the real business
Amount is not the only criterion
A simple limit matrix is a useful start, but a low-value software subscription may create a multi-year obligation while an expensive spare part may be urgent because production has stopped. Rules should combine amount, category, dimension, supplier and document type. Project spend can route to the project manager; services can require contract confirmation; asset purchases can involve the fixed asset owner before ordering.
Do not turn the director into an inbox
If one person receives every request, the process slows and control becomes superficial. Delegation with clear limits and substitutes during absence is stronger. Approval chains and user limits in Business Central must also be maintained when responsibilities change.
From purchase order to incoming invoice
Control continues at receipt and invoice posting. Purchasing confirms the order, the warehouse or responsible person records receipt and finance compares the invoice with the order and receipt. A meaningful variance can require renewed approval, while sensible tolerances prevent administration for insignificant differences. With Holy Document Capture, electronic and emailed invoices can enter this same controlled chain.
Where Holy AI shortens the work — and where it stops
A user can describe a rule in ordinary language: “For project ALPHA purchases above EUR 5,000, require the project manager and CFO; for emergency repairs marked as production downtime, notify operations.” Holy AI analyses the requirement, proposes workflow logic and prepares an AL change in the test environment. Finance confirms thresholds, purchasing explains exceptions and a Business Central expert checks postings, permissions and integrations before the HOLYERP team signs off.
Introduce control without user resistance
Do not introduce every rule on day one. Analyse recent purchases, urgent orders, invoices without purchase-order references and the people who actually make decisions. Begin with routine operations, project or budget-sensitive spend and higher-risk procurement. Measure request-to-order time, matched invoices, urgent exceptions and requests returned for missing data, then refine the workflow.
Show us where purchasing waits or loses its audit trail. We will help you design a faster, controlled Business Central workflow.