Finance teams at UK contractors with several sites running at once tend to rebuild the same information twice a month from the same pile of invoices. Around the 10th someone builds the job cost report, assigning each merchant line and subcontractor application to a site from memory. By the 19th someone builds the CIS return from the same invoices, pulling out what each subcontractor was paid and how much of it was materials. The two rarely agree, and until both are done nobody can say what any job has spent this month.
The problem is that none of that spend arrives carrying its job. A subcontractor's application lists labour and materials together. A builders' merchant statement covers several sites on one account. Site managers put fuel and sundries on company cards with no job against the transaction. Every line has to be assigned to a project by hand, after the fact. The cost is a week of finance time each month, and a per-job number that arrives too late to change anything on the job.
This article looks at what HMRC already requires you to capture on every subcontractor payment, why a job-cost spreadsheet and a company card per site manager don't give you a project view, what a project view without guesswork needs, and how cards, coded orders and a single export produce it.
What HMRC already makes you capture
The Construction Industry Scheme already defines most of the data a project view needs. As a contractor you verify each subcontractor with HMRC, deduct what HMRC tells you to, pay it over, and file a monthly return by the 19th of the month following the tax month. A return one day late costs £100. For every payment you keep, for three years, the gross amount excluding VAT, the deduction made and, where a deduction was made, the materials the subcontractor invoiced. HMRC can fine you up to £3,000 if you cannot show those records.
The VAT reverse charge adds a second classification on the same invoices. It applies to construction services between UK VAT-registered businesses that are reported under CIS, materials included. Materials, plant or components supplied on their own are outside it. So a subcontractor's invoice is reverse-charged and a merchant's materials-only invoice is not.
Put the two together and compliance already needs two of the three attributes a cost view needs: what kind of supplier each line came from and, for a subcontractor, how much of it was materials. The cost view needs the third, which job the line belongs to, and HMRC never asks for that one. Capture all three once at the invoice and the cost report and the CIS return are two reports off the same data.
Why the spreadsheet and the site card don't fix it
Most contractors have tried two fixes already. The spreadsheet starts from ledger lines that carry no project, so the assignment is done from memory and the result is only as good as the person doing it. Job costing in the accounting system is better, but only if lines arrive coded, and most arrive as a merchant statement covering several sites or a subcontractor application with the job named in the email subject.
A company card per site manager attributes spend to a person rather than a job, and nothing stops a manager buying for a different site. Asking subcontractors to invoice per project with materials shown separately is necessary and tends to be ignored, and even when it is done the figure sits as text on a PDF unless finance captures it as a field.
What a project view without guesswork needs
It needs the same three attributes captured at source, with no exceptions. Every card line and every invoice carries its project before it can move to the next step. Every supplier is classified when finance creates it, as a subcontractor, a merchant, plant hire or a professional. Every subcontractor invoice carries its materials element as a separate value. Three things deliver that: cards per project, orders raised against the project, and one export.
Project cards, coded orders, one export
This is how Moss does it. Each site manager gets a card issued against their project, with a limit and an end date, and the project set as the card's default accounting attribute, so site purchases carry their job from the start. A missing-receipts policy can block a card until the receipt is attached.
Subcontractor and merchant spend goes through purchase requests. The request is approved against the project's budget and becomes a purchase order. When the invoice arrives it is linked to the order by PO number, or by supplier and date. At or under the order, from the same supplier, it is approved automatically; any overrun at all, or a different supplier, sends it back to an approver. For materials, the invoice is also matched against the site team's goods received note.
The three attributes are enforced as fields. Project, supplier and custom fields such as the materials element can be made mandatory, so an invoice cannot move through review and approval, and a card transaction cannot be completed, without them. The export then carries those fields to your accounting system.
While Moss doesn't verify subcontractors with HMRC, calculate deductions, file the monthly return or decide whether a line is reverse-charged, it does deliver each line to the software that does those things with the project, the supplier type and the materials element already attached. The return and the cost report then come off the same data.
What changes at month-end
The job cost report stops being a reconstruction. Finance can filter the month's spend by project at any point and see it, with receipts, without rebuilding it from the ledger. When the CIS return is due, it reads from the same export as the cost report, and the two agree because they are the same data.





