Construction Procurement, From Plan to Payment
Last updated 2026-07-13
Procurement is where a project spends most of its money, and it is where the least attention is paid to the process by which the money leaves.
This guide follows one arc — from the annual plan to the moment a payment clears — and stops at each point where money reliably escapes. Every one of these leaks is ordinary, none of them requires a bad actor, and most of them are invisible in the cost report until long after the option to fix them has expired.
The plan: buy-out is where margin is made or lost
Buy-out — converting the tender allowances in a winning bid into awarded subcontracts and orders — happens in the first months of a project, quietly, while everyone is looking at mobilisation. And it is where a contractor’s margin is genuinely decided.
The pressure to award fast collides directly with the value of awarding well. A package bought in a hurry, uncompeted, gives back the margin the estimator earned — and nobody will ever attribute the loss to that decision, because it will surface months later as an unremarkable line in a cost report.
The plan is also where long-lead items are either caught or missed. A transformer or a chiller with a lead time measured in the high tens of weeks is a schedule item, not a procurement item, and it belongs on the programme with a decision date. Discovering it late does not cost you a procurement cycle. It costs you the difference between the lead time and the time remaining.
The tender: a fair process is a commercial asset
Most of the value in tendering is created before any bid arrives. A well-defined scope, a clean bill of quantities, and properly answered queries produce comparable bids. A vague scope produces bids that differ by more than price, and no amount of clever evaluation recovers that.
Then comes levelling, which is the most valuable hour in the process and the first one to be compressed when an award is urgent. A bid is rarely low because the bidder is efficient — it is usually low because something is missing: an exclusion buried on page forty, a qualification about access, an assumption about who supplies the crane. Levelling is the work of finding those and adding them back.
And the abnormally low tender deserves its own paragraph, because the tempting response is to take the money. It is not a saving. It is a transfer of risk to you, and the mechanism by which the bidder recovers is a claims campaign that will consume your project team for two years. Or — worse — the bidder simply made an error, and a contractor working at a loss will cut corners, slow down, defer payments to its own supply chain, and eventually stop.
One more thing, and it is easy to underestimate: a bidder pool that believes your process is fair is a commercial asset. Run one sham tender to justify a decision already made, and the good contractors will price your next one accordingly, or not price it at all.
The award: what belongs in a contract, and what belongs on a PO
A purchase order buys a thing at a price. That is what it is for, and it does it well.
It cannot carry supervision obligations, insurances, liabilities, intellectual property or a professional indemnity requirement. Those belong in a contract. A services engagement run on a two-line purchase order has no answer to the question of what happens when it goes wrong — and the question arrives eventually.
And on services, there is no delivery truck to inspect. The control instrument is the milestone, and the entire integrity of service procurement rests on whether the milestone was written well enough to be verifiable at all. "Design 60% complete" is not a milestone; it is a disagreement with a payment attached. If two reasonable people could look at the same evidence and disagree about whether it is met, you have scheduled an argument and agreed to fund it.
The commitment: the overrun is real before the invoice arrives
The moment an approved purchase order is issued, the cost is committed. Legally. Not when the goods arrive, and certainly not when the invoice does.
Which means a project tracking only actuals learns about its overruns thirty to sixty days late — not through carelessness, but because that is how long invoices take to arrive. By the time the cost report shows the problem, the problem has finished happening and every option that might have been taken has expired.
A project’s true position is budget against committed against actual. All three. And the middle one is the only one that warns you.
The related leak is maverick spend — purchasing that bypasses the process entirely. It is almost never dishonest; it is people solving a problem faster than the process allows. Which is the key to fixing it: punishing maverick spend produces a site that hides it, not a site that stops. A process fast enough to actually use, plus a genuinely quick low-value channel, produces a site that complies.
The receipt: count at the gate, record what was accepted
The supplier’s delivery note is the supplier’s account of what it sent. The goods-received note is your account of what actually arrived. When they disagree — and they do — the GRN is the document that protects you.
Provided somebody counted. A GRN signed unchecked to get the truck off site is worse than no GRN at all, because it is positive evidence that you accepted what was delivered.
And the material does not stop being your problem once it is through the gate. Cement ages. Waterproofing membrane degrades in UV. Rebar in ground contact contaminates. Material that passed inspection on arrival can fail on the day it is installed — and the inspection record saying it was acceptable will still be sitting there, entirely correct, describing a condition that no longer exists.
The match: ordered, received, billed — and all three must agree
Three-way matching reconciles the purchase order, the goods-received note and the invoice before payment. It is the single most effective control against paying for what never arrived, and it is unglamorous enough that it is routinely weakened into a two-way match, which checks that you were billed for what you ordered and says nothing about whether anything showed up.
The tolerance band is what makes it workable and what makes it exploitable. Tolerances exist because perfect matching is impossible: freight rounding, currency conversion, a partial delivery. But a supplier who learns your tolerance will invoice just inside it, every time — and each individual difference is fine, which is the point.
The counter is cumulative monitoring. One invoice slightly over tolerance is a rounding error. The same supplier consistently and slightly over, for eleven months, is not an accident, and it is invisible to a control that only ever looks at one invoice.
- Two-way (PO ↔ invoice): does not check that anything was delivered.
- Three-way (PO ↔ GRN ↔ invoice): the standard. Ordered, received, billed.
- Four-way (+ inspection): adds the quality result, so you do not pay for material that arrived and failed.
- Services: the certificate replaces the GRN. The certifier is doing the gate’s job — on judgement rather than on a count, which is harder.
The payment: the clock, and the notice that saves the deduction
The application is the contractor’s assertion; the certificate is your decision. They are different documents doing different jobs, and conflating them is how contractors come to believe they are owed money that has never been certified.
And the clock matters more than the arithmetic. Most contracts set a period within which the employer must certify and pay, and a period within which any deduction must be notified. Miss the notification window and the deduction can be lost in full — however justified it was. Defective work, a legitimate contra charge, a genuine re-measurement: all of it, gone, because a notice went in a day late.
It is one of the few places in construction where the law hands a party a genuinely powerful procedural weapon, and it is worth understanding which end of it you are on.
And the retention that nobody releases
Retention is the employer’s security and the contractor’s working capital, and it is the same money. It sits, unpaid, for the length of the defects liability period — a year or more after the work is finished and the crew has moved on.
The systemic problem is not disputes. It is inattention. The DLP expires, nobody applies, the employer does not volunteer, and the sum quietly ages into a bad debt on a balance sheet nobody is reading.
A retention ledger with release dates against every contract is the entire remedy. It is unglamorous enough that most contractors do not keep one — which is precisely why the money is still sitting there.
Common questions
Why is the lowest bid not the cheapest?
Because it is rarely low through efficiency. It is low because something was excluded, qualified or misunderstood — and you will pay for it later, through variations, claims, or a contractor working at a loss who cuts corners and eventually stops. Levelling the bids is where you find out which.
Read the full answerWhat is committed cost, and why does it matter?
Money legally promised but not yet invoiced — the value of approved purchase orders and subcontracts. It is the leg that budget-versus-actual leaves out, and the only one that warns you: the overrun is real the moment the PO is approved, and the invoice merely reports it thirty to sixty days later.
Read the full answerWhat is three-way matching?
Reconciling the purchase order, the goods-received note and the invoice before payment. Ordered, received, billed — and all three must agree. Two-way matching skips the delivery and therefore checks nothing about whether anything arrived; four-way adds the inspection result.
Read the full answerWhat is maverick spend, and how do you stop it?
Purchasing that bypasses the process — no PO, no approved supplier, no negotiated rate. It is almost never dishonest; it is people solving a problem faster than the process allows. Which means punishing it produces a site that hides it. A process fast enough to use is the only fix.
Read the full answerWhy does retention so often go unreleased?
Inattention, not dispute. The defects liability period expires, nobody applies for release, the employer does not volunteer it, and the sum ages into a bad debt. A retention ledger with release dates against every contract is the whole remedy, and most contractors do not keep one.
Read the full answerReferences
- Standard-form payment and notice mechanics — application, certification, and the deduction-notice window
- Three-way match doctrine — anchored with its evidence on /modules/three-way-matching/
- Every statistic referenced in this guide is anchored on the module page that owns it — /modules/purchase-orders/, /modules/delivery-notes/, /modules/tender-management/, /modules/invoices/. One finding, cited once, on the page that carries its source.
In depth
- Why is the lowest bid not the cheapest?
- What is an abnormally low tender — and can you reject it?
- Budget vs committed vs actual — what is the difference?
- Two-way vs three-way vs four-way matching — what is the difference?
- What is maverick spend in construction?
- What happens when work starts without a purchase order?
- What makes a good service-contract milestone?
- How does retention release work?
- What are long-lead items in construction right now?
- What is a pay-less notice?
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting