How to prevent unauthorised spending on construction sites.
Unauthorised spending stops when three things are true: every purchase starts with a written request, nobody pays without approval from someone else, and suppliers know you only honour official orders. Put those rules in writing, tell your suppliers, and give site teams a quick, recorded route for genuine emergencies so nobody is tempted to go around the system.
How unauthorised spending usually happens
On most sites it is not dramatic. It looks like this:
- Verbal orders. A foreman phones a hardware shop: "send 50 bags, we will sort the paperwork later".
- Open site accounts. Anyone the shop recognises can collect goods on credit in the company's name.
- Petty cash stretched too far. Items that should have been ordered are bought with cash and explained later.
- One person doing everything. The same person asks, approves and pays.
- "Urgent" purchases that skip approval and are never reviewed afterwards.
- Invoices paid on trust, without checking them against an order or a delivery note.
Most of this is convenience, not theft. The effect on your budget is the same, though, and convenience is exactly where real fraud hides. Unauthorised purchases are one of the ten forms of construction cost leakage we cover in detail.
The rule that does most of the work: no LPO, no payment
For goods and services from suppliers, finance pays only against an approved order that matches what was delivered and invoiced. Anything else goes back for approval before it is paid. The rule moves the pressure: suppliers start asking your site team for an LPO, instead of your office chasing explanations after the money has gone.
| Check before paying | Why it matters |
|---|---|
| An approved requisition exists | Someone with authority agreed to the spend |
| The invoice quotes your LPO number | The supplier is billing for what you ordered |
| A delivery note was signed on site | You are paying for goods that arrived |
| Quantities and prices match | No extras or price changes slipped in |
Tell your suppliers in writing
A short letter, or a WhatsApp message saved as a PDF, removes the grey area. Adapt this example:
Dear supplier,
From 1 December, [company name] will only pay for goods and services ordered with an official LPO approved by our project manager or director. Please do not release goods against phone calls, WhatsApp messages or verbal requests from site staff, and quote our LPO number on every delivery note and invoice.
Orders without an LPO will not be paid until they have been approved. Thank you for helping us keep our records accurate.
Send it to every regular supplier, close informal site accounts, and repeat the message when a new supplier joins.
Set approval limits people can remember
Limits only work if site teams know them without looking them up. One common arrangement is shown below. The amounts are illustrative, so set limits that suit your company and project sizes.
| Request value | Who approves |
|---|---|
| Under KES 50,000 | Site engineer or project manager |
| KES 50,000 to 500,000 | Project manager, then finance manager |
| Over KES 500,000 | Project manager, then director |
Whatever limits you choose, keep three duties apart: the person who asks, the person who approves and the person who pays. For a fuller treatment of levels and limits, see how to manage construction purchase approvals.
Handle exceptions without breaking the rule
Sites do have real emergencies: a burst pipe, a concrete pour that cannot wait, a breakdown. If the only official route is slow, people will take the unofficial one. Give them a fast route that still leaves a record:
- A named person, such as the project manager, can approve an emergency purchase by phone, up to a small cap.
- The approval is confirmed in writing the same day, even if only by a message.
- A requisition is raised within 24 hours, marked as an emergency.
- Emergency purchases are reviewed at the weekly cost meeting.
Watch the count. A site that has an "emergency" every week has a planning problem, or someone has found a way around the rules.
An example spending policy you can adapt
1. Every purchase of materials, services, casual labour or overheads starts with a requisition that names the project, items, quantities, rates and reason.
2. Requisitions are approved by someone other than the person asking, within the limits in the approval table.
3. Supplier purchases are ordered with an LPO. Invoices without an LPO are not paid until approved.
4. Deliveries are counted and signed for on site against the LPO.
5. Payments are made only by finance, only against approved requests, and only to recorded M-Pesa numbers or bank accounts.
6. Emergency purchases follow the emergency route and are reviewed weekly.
7. Directors' own purchases follow the same rules.
The last point matters more than it looks. If the people at the top skip the process, nobody else will take it seriously.
Doing this in MjengoKit
In MjengoKit, every purchase starts as a requisition, goes to the approvers you set for that kind of request, and can only be paid by people with payment permission. Approvers can comment or reject with a reason, and the approval history stays on the record. Approved material requests become LPOs that you can send to suppliers on WhatsApp.
Bring your current purchase rules. We will show you how MjengoKit applies them to every request.
Book a 20-minute demo