No fluff - just straight guidance on quoting, job costing, purchase orders, invoicing, CIS, VAT and keeping multi-week projects under control.

Partial invoices are easy to miss because they look like normal claims at first glance. A simple check against the original commitment, delivery evidence, and approved scope keeps bookkeeping from posting the wrong number.

Partial invoices are easy to miss because they look like normal claims at first glance. A simple check against the original commitment, delivery evidence, and approved scope keeps bookkeeping from posting the wrong number.

An approved PO is only useful if the supplier actually receives it. Missing the send step can create delays, duplicate follow-up, and invoices that arrive before the commercial record is complete.

One absent approver can stall materials, labour and subcontract packages. A simple approval chain keeps decisions moving and shows who can sign what when the usual reviewer is away.

A commercial handover sheet keeps job references, approvals, and invoice status together so site and accounts are not working from different versions of the truth.

Small site spends still need a proper job reference. Capture receipts while they are fresh, keep them on the right job, and stop small costs drifting.

PO revisions are normal on live jobs. The risk is not the change itself — it is losing the original value, the reason for the update, and the approval trail before accounts sees the invoice.

Variation instructions often start in WhatsApp, email, or a site conversation. A single log gives the business one trusted record before the cost reaches accounts.

An invoice without a PO number is not a small admin gap. It is a sign that the cost may be hard to match, query, or post correctly unless the team follows a clear triage step.

A good site diary is not admin for the sake of it. It is the record that helps a contractor prove what changed, who said what, and why a later invoice or variation should be accepted.

If invoices, delivery notes, and small purchases arrive with different references, job costing breaks fast. One project-code rule keeps the paperwork attached to the right job.

Retention is easy to forget once the invoice has been posted net of the deduction. A simple record for the amount, trigger, and release date keeps the money visible.
One job can pick up several names across site, office, and supplier paperwork. A simple reference rule keeps the right cost on the right job.

One job can pick up several names across site, office, and supplier paperwork. A simple reference rule keeps the right cost on the right job.

One job can pick up several names across site, office, and supplier paperwork. A simple reference rule keeps the right cost on the right job.


If a subcontractor payment application arrives without a clear approval trail, accounts ends up guessing who signed it off, what was agreed and whether any balance is disputed. Keep the decision, evidence and next action together before posting.

A clean approval trail for subcontractor applications for payment keeps accounts moving, reduces chases, and makes job cost reviews easier.

If site approvals live in email, WhatsApp and memory, accounts ends up chasing sign-off at the worst possible time. A clear approval trail keeps the invoice, the approver and the next action in one place.

Unapproved variations create a quiet cash flow problem: the work gets done, the cost lands, and the money is still stuck in approval limbo. Here’s how to tighten the process.

If a PO system only issues numbers, it is not doing enough for construction. The useful part is the data it captures and keeps visible.

The right purchase order software does more than issue numbers. It keeps approval, job reference, and invoice matching visible before spend turns into a surprise.

When an invoice question lives only in email, WhatsApp or a memory of a phone call, it is easy for the query to vanish. This workflow shows how to keep the reason, owner and next action visible until the issue is closed.

An invoice on its own is not enough evidence. If the PO, delivery note, timesheet or sign-off is missing, accounts is left to guess whether the cost is ready to post.

Takeoff software is only useful if the quantities it produces make it into the next step without retyping. BuilderDash and solidtakeoff.com are working towards a cleaner hand-off between estimating and job control.

One supplier invoice can belong to more than one job. The fix is a clear split allocation, not a guess in accounts after the cost has already landed.

Labour-only invoices are only easy to approve when the timesheet, site reference, and sign-off are already attached. Without that evidence, accounts is left to guess.

On fit-out jobs, a generic site name is not enough. Room and zone references make it easier to match POs, variations, and invoices to the right part of the job.

If invoices, delivery notes, and small purchases arrive with different references, job costing breaks fast. One project-code rule keeps the paperwork attached to the right job.

Retention is easy to miss when the deduction sits inside a normal invoice total. Contractors need a simple way to record the retention amount, the release trigger, and the date it should be chased.

A weekly committed cost review gives contractors a clearer view of what has been approved, what is still open, and what will hit the job next.
A spend report can show what has already happened. Control means knowing what is committed, approved, and still open before the invoice lands.

A payment run should not be a race to clear the accounts inbox. This checklist helps UK contractors decide which supplier and subcontractor invoices are ready to pay, which need a query, and which need better approval evidence first.

Supplier statements are useful only when they are checked against the work, orders, invoices, and queries behind them. Here is a practical month-end workflow for construction teams.

A subcontractor invoice should be easy to trace, easy to match, and easy to query. The workflow matters more than the invoice file itself.

An invoice may be accurate and still not be payable. Construction teams need a simple rule for checking PO approval status before costs reach accounts.

WhatsApp is quick for site communication, but it is a poor place to store commercial approvals. Contractors need a simple rule for turning chat requests into proper purchase orders before spend starts drifting.

A materials invoice should not be approved simply because it names the right site. Matching the purchase order, delivery evidence and invoice helps contractors catch missing, damaged or incorrectly charged goods before payment.

A queried invoice should not disappear into an email chain or remain fully approved while the site team investigates it. This practical workflow shows how construction businesses can record the issue, protect job costs and reach a clear payment decision.

Making Tax Digital for Income Tax now applies to some sole trader builders, with lower income thresholds following in 2027 and 2028. This practical guide explains who is affected, what qualifying income means, and how to keep job records ready for quarterly reporting.

Duplicate invoices can enter a construction business through several routes and still look legitimate. Here is a practical checking workflow for catching repeats, applying credit notes correctly, and keeping job costs accurate before the payment run.

A purchase order only controls spend if changes are recorded before the invoice arrives. Here is a practical workflow for handling overspend, revised orders, and construction variations without losing sight of the committed job cost.

Accounts automation works best when the basic construction controls are already clear. Before pushing more invoices through software, contractors should standardise purchase orders, job references, approval rules, and exception handling.

When every supplier invoice, subcontractor claim, and purchase order query waits for a director, accounts slows down and job costing becomes less useful. A cleaner approval workflow keeps control visible without turning one person into the bottleneck.

Materials invoices become harder to control when the job, site, PO, and delivery context are missing. Clear project codes and site references help accounts and project teams agree what the cost belongs to before it reaches bookkeeping.

Partial subcontractor invoices are not a problem by themselves. The problem is when nobody can see what has already been claimed, approved, queried, or held back.

Month-end invoice chasing is usually a sign that job references, approvals, purchase orders, and invoice checks are not joined up early enough.

For small UK contractors, purchase orders are not just paperwork. They are the point where spend control starts, before supplier and subcontractor invoices reach accounts.
Put it into practice with BuilderDash - one system for every enquiry, job, quote and invoice.