Why the same mistakes repeat
Construction firms are not failing at CIS because they do not understand it. They are failing because the monthly process is weak. Records are incomplete. Verification is late. Deduction status is guessed. Materials are unclear. Returns are prepared under pressure. Statements are an afterthought.
These are operational failures, not knowledge gaps. And they repeat for a simple reason: nobody owns the monthly CIS process.
If the subcontractor is not verified, the contractor does not know what deduction treatment to apply. They are guessing. And if they apply the wrong rate — or pay gross when they should not — the liability sits with the contractor, not the subcontractor.
Verification should happen before the first payment runs. Not after. Not during. Before.
Verification confirmed and deduction rate recorded before subcontractor enters the payment run.
A name and a bank account are not a CIS record. A proper CIS subcontractor record needs the UTR, entity type (sole trader, limited company or partnership), the appropriate identity details and the verification status with a date.
Contractors often start building subcontractor records from invoice headers, text messages and conversations. By the time the return is due, the records are patchy and the verification is uncertain.
Structured subcontractor onboarding form completed before any work begins.
Gross payment status means the subcontractor is paid without CIS deductions. It must come from HMRC verification. It cannot come from the subcontractor telling you they are gross, from previous experience, or from a reasonable assumption about a reputable firm.
If HMRC verification does not confirm gross status, the contractor should not pay gross. Full stop.
Gross status evidenced from HMRC verification record before the payment runs.
CIS deductions apply to the labour element of the payment. Materials are generally excluded. But if the invoice says "works as agreed" or "labour and materials — £4,500" with no breakdown, the contractor has no reliable basis for the calculation.
Some contractors apply CIS to the full invoice. Some guess the materials split. Both approaches create records that would not survive scrutiny.
Subcontractors required to itemise labour and materials separately on invoices before payment is processed.
Bank payments show money leaving the account. They do not show verified subcontractor details, correct deduction treatment, labour/materials splits or the CIS liability position. A return built from bank payments and invoice scraps is not a controlled return.
The return should be built from structured data: verified subcontractor records, reviewed invoices, calculated deductions and approval records.
Monthly return built from controlled records, not reconstructed from bank statements at deadline time.
Subcontractors rely on CIS payment and deduction statements for their own tax records. Statements should be issued every month for every subcontractor who was paid. They should not be produced only when a subcontractor chases, or accumulated for issue at year-end.
Late or missing statements create friction, undermine trust and leave both parties without clean records.
Statements issued as part of the monthly close — not as a response to subcontractor requests.
Many construction firms have both employees and subcontractors. Directors on PAYE. Site staff on PAYE. Subcontract trades on CIS. When CIS and PAYE are managed separately — different spreadsheets, different timelines, different people — the total compliance picture becomes blurry and the owner loses visibility over total labour cost.
PAYE and CIS controlled inside the same monthly compliance rhythm with one timeline and one approval process.
If nobody signs off the return before it is filed, accountability is weak. If HMRC queries the return, or a subcontractor disputes a deduction, the contractor should be able to show that the return was reviewed and approved before submission.
An approval timestamp, an email confirmation or a signed summary is not bureaucracy. It is evidence.
Contractor approval captured and saved before every CIS return is filed.
CIS does not remove employment status risk. A contractor cannot label someone as a subcontractor and assume the issue is closed. If the working arrangement looks like employment — regular hours, one client, no financial risk, equipment provided by the contractor — there may still be PAYE, NMW and employment rights exposure.
CIS is a tax reporting framework. Employment status is a separate question that CIS does not answer.
Employment status considered before a subcontractor arrangement is established, not after a CIS return is filed.
Deadline-week CIS is where errors breed. Verification gets skipped because there is no time. Invoices get accepted without review. Materials splits get estimated. Approval gets waved through without proper review. Statements get delayed.
The deadline is the filing point — not the starting point. CIS should be built throughout the month so that deadline week is just confirmation and submission.
CIS process starts at the beginning of the tax month, not at the end of it.
The pattern behind all ten mistakes
Every mistake on this list comes back to the same root cause: no one owns the monthly CIS process. The records are scattered. The timeline is reactive. The review happens under pressure. The evidence is weak.
CIS should have the same operational discipline as payroll: a data deadline, a verification check, a deduction review, an approval, a filing, a statement issue and evidence retention. Not scrambled from the bottom up every month.
If CIS currently lives in spreadsheets, email threads or last-minute messages to your accountant, it is weaker than you think.
Want CIS moved into a controlled monthly workflow?
Bookd handles CIS records, verification, monthly returns, deduction calculations, statements and filing for construction contractors.
Book a CIS payroll review