On most sites, the fastest way to keep a job moving is for the site manager to just buy what's needed. It could be a replacement part, or a delivery that has to be paid on collection, put on a personal card or paid in cash, with a promise to sort the receipt later.
It’s the most common type of purchase on site because it's convenient and easy. But every OOP purchase creates work and risk somewhere else, most of which lands on finance.
The cost of quick purchases on personal cards
While it’s undoubtedly convenient, the real cost of out-of-pocket buying turns up in four other places:
- Admin time. Every personal purchase leads to a reimbursement claim that someone from finance has to submit, code, check and pay.
- Reimbursement lag. Site managers can be hundreds or thousands of pounds out of pocket for weeks, waiting on the next pay run. That's bad for employee goodwill, bad for cash flow, and a poor experience for the people keeping jobs on track.
- VAT leakage. Lost or missing materials receipts all represent VAT that you can’t reclaim.
- Spend detached from its project. When a purchase only surfaces weeks later as a claim, it often arrives with no clear link to the job it was for. Project costs look lower than they really are until the claims catch up, and by then the picture is already out of date.
Why it keeps happening
While this type of buying is annoying for the finance team, it's the reality of buying on a site. Materials are needed now, the nearest merchant takes payment on the spot, and the person standing there is the site manager, not finance.
If the only tool to hand is a personal card, then that’s what’s going to be used. The buying happens far from finance's controls, and the spend only becomes visible after the fact.
Issued cards change where the buying happens
The fix is to give site teams a way to buy that doesn't route through their own pocket. Company-issued cards, mapped to a project and restricted to the merchants and categories that make sense, let a site manager buy what they need without fronting the money or filing a claim. The spend is captured the moment it happens, with the project already attached.
That also closes the visibility gap. Rather than reconstructing who bought what, for which job, from a pile of receipts, finance sees project-coded spend as it lands. Purchase orders and goods-receipt matching add another layer. They line up what was ordered, what arrived, and what was paid per project, instead of having to piece the picture together at month-end.
Where Moss fits in
Moss is built for exactly this kind of ad-hoc construction spend. Project-based, merchant-restricted cards remove the need for anyone to spend personally, while purchase orders, goods-receipt matching and project mapping keep every cost tied to the job it belongs to. Finance gets a structured view of spend by project and by subcontractor, coded at source rather than cleaned up later.
It stops short of the tax treatment so CIS deductions and reverse-charge VAT stay in your accounting system with your accountant, where they belong. What Moss passes downstream is cleaner raw material for that work. Project-coded, receipt-backed spend makes the CIS and VAT steps easier, without Moss ever taking on the compliance itself.
Control and cleaner data, at the source
Paying out of pocket will always feel like the path of least resistance on a busy site, right up until you add up what it costs behind the scenes. Move the buying onto issued, project-mapped cards and most of that cost falls away. Less admin, nobody left waiting to be paid back, more VAT actually reclaimed, and spending tied to the right job from the moment it happens. The tax work still has to be done, but you'll be doing it on clean, reliable data.






