The Construction Industry Scheme has just got sharper teeth. From 6 April 2026, HMRC reinstated mandatory monthly nil returns and introduced a "knew or should have known" fraud test that can strip a contractor of Gross Payment Status overnight, with a five-year wait to get it back. At exactly the moment CIS compliance became higher-stakes, AI tools are being sold to construction businesses as the answer to it. Some of that is genuinely useful. Some of it is a fast way to find out what "knew or should have known" means in practice.
This piece sits alongside our wider guide to AI automation for construction companies, which covers where AI fits across the whole business, not just compliance.
Quick answer
AI can safely handle the mechanical parts of CIS: extracting invoice data, separating labour from materials, flagging when a subcontractor is due reverification, and chasing missing paperwork before a payment run. It should not be the final decision-maker on verification status, Gross Payment Status risk, or whether a transaction looks fraud-connected. Since April 2026, HMRC can hold the contractor personally liable for those calls, not the software that helped make them.
In this guide
- Why this matters more than it did a year ago
- CIS in plain terms: rates, labour vs materials
- A worked example: where the numbers come from
- Where AI genuinely helps with CIS
- Where AI becomes a liability, not a shortcut
- Who does what: a practical division of labour
- CIS and the VAT domestic reverse charge together
- A seven-point CIS automation checklist
- Frequently asked questions
Why this matters more than it did a year ago
Until this year, getting a CIS deduction wrong was mostly a paperwork problem: a late return, a £100 fine, an awkward conversation with your accountant. The April 2026 reforms changed the level of the conversation. HMRC now applies a "knew or should have known" test, borrowed directly from the VAT fraud rules known as the Kittel test, to CIS transactions connected to fraud in the supply chain. If HMRC decides a contractor should reasonably have spotted a problem with a subcontractor further down the chain, it can cancel that contractor's Gross Payment Status immediately, with no warning, and the reapplication wait has gone from one year to five.
That is the backdrop against which "AI can automate your CIS compliance" is now being sold to construction businesses. The pitch is not wrong. Automation genuinely removes hours of repetitive work. But the same reforms that make CIS more time-consuming also raise the cost of getting a judgement call wrong, and judgement calls are exactly the part of CIS that a language model is worst equipped to make safely on its own.
CIS in plain terms: rates, labour and materials
If you already know CIS inside out, skip to where AI actually helps. If you want the refresher first, here it is without the jargon.
Under the Construction Industry Scheme, as set out by HMRC, a contractor deducts money from a subcontractor's payment and passes it to HMRC as an advance payment towards that subcontractor's own tax and National Insurance. The rate you deduct depends entirely on the subcontractor's verified status with HMRC, and you must verify that status before making the first payment in each tax year.
Gross payment status
Subcontractor has passed HMRC's turnover and compliance tests. Full invoice amount paid, no deduction.
Standard rate
Subcontractor is registered for CIS but does not hold gross payment status. Deducted from labour only.
Higher rate
Subcontractor is not registered, or verification fails. This is the default if you cannot verify at all.
One detail trips up more businesses than any other: CIS deductions apply to labour only. Materials genuinely incurred by the subcontractor are excluded. But if an invoice does not clearly separate the two, HMRC's default position is that the whole amount counts as labour, and the deduction gets calculated accordingly. That single formatting habit, on both sides of a transaction, is responsible for a large share of CIS disputes.
A worked example: where the numbers actually come from
A subcontractor invoices £2,000 for a job: £1,500 labour, £500 materials. They are registered for CIS but do not hold gross payment status, so the standard 20% rate applies.
Standard-rate deduction (20%)
If the same subcontractor had not registered for CIS, the 30% rate would apply to the same £1,500 labour figure, a deduction of £450 rather than £300, a £150 difference the contractor is responsible for getting right, and for which "I didn't check" is not treated as a reasonable excuse.
Where this usually goes wrong in practice
The failure mode isn't usually the maths. It's the invoice itself. A subcontractor who doesn't split labour and materials clearly, or a contractor who accepts an inflated materials figure without checking it, creates exactly the kind of record HMRC now expects a "reasonably diligent" contractor to have questioned. Getting the arithmetic right on a badly-structured invoice still leaves you exposed if the underlying document wouldn't survive scrutiny.
Where AI genuinely helps with CIS admin
None of this requires AI to make a judgement call. It requires AI to do what it's actually good at: reading, extracting, classifying and reminding.
- Reading incoming subcontractor invoices and extracting the supplier, job reference, gross amount, and a proposed labour/materials split for a human to confirm, rather than someone retyping figures from a PDF.
- Flagging invoices where labour and materials are not separated, before payment, rather than after HMRC asks a question about it.
- Tracking reverification dates for every subcontractor at the start of each tax year, and surfacing the list of who is due a check, rather than relying on someone remembering.
- Preparing the monthly return as a draft, pre-populated from payment records, ready for a person to check before it's submitted, including nil months, which are now mandatory rather than optional.
- Chasing missing documentation (insurance, UTR, company registration) from a new subcontractor before their first payment falls due, on a schedule, without someone having to remember to ask.
- Cross-referencing a subcontractor's details against what's already on file and flagging inconsistencies (a changed bank account, a different trading name, a UTR that doesn't match previous records) for a person to look at, rather than silently accepting whichever version arrived most recently.
This is the same principle Construct Virtual applies across the rest of construction admin: automate the information movement, leave the judgement with the person who is accountable for it. Our guide to AI for construction admin covers this model in more depth for the wider office workload, including invoice processing generally; this piece exists because CIS specifically now carries a different, sharper category of risk that deserves its own answer.
Where AI becomes a liability, not a shortcut
This is the part most software vendors selling "AI-powered CIS compliance" skip over, because it's the part that makes the sale harder.
Verification decisions
A verification check is a factual lookup against HMRC's system, not something an AI model should infer or estimate from a subcontractor's paperwork. If a verification genuinely fails, the law requires the 30% rate; it does not permit a confident-sounding AI summary to substitute for that check. Automate the reminder to verify. Do not automate the belief that verification happened.
Gross Payment Status risk
Since April 2026, losing GPS can happen instantly and the reapplication wait is five years. Where HMRC finds the "knew or should have known" test is met, it can also charge the paying business 20% of the amount paid, charge whichever business claimed the CIS credit up to 100% of that credit, and apply a further penalty of up to 30% of the lost tax on top. Deciding whether a transaction "looks" fraud-connected, or whether your due diligence on a subcontractor was reasonable, is exactly the kind of context-heavy, high-stakes judgement that needs a person with real accountability, not a model pattern-matching against training data that has no idea what HMRC's current enforcement priorities actually are.
Materials vs labour disputes
AI can flag that a split looks unusual. It should not decide, on its own, that a materials figure is legitimate. An inflated materials allocation used to reduce a deduction is a known HMRC enforcement target, and the contractor carries the exposure if it later turns out to be wrong, regardless of which tool waved it through.
Version drift across systems
If a subcontractor's verification status, bank details or trading name exist in slightly different forms across your CRM, your accounting software and an email thread, an AI system will confidently use whichever version it can find first. It has no way of knowing that one of those records is six months out of date unless someone tells it. This is the same fractured-identity problem we cover in more depth in entity SEO for trades, just applied to your subcontractor records instead of your public business listings. CIS is simply the place where getting it wrong costs the most. Before pasting subcontractor details such as UTRs or bank details into any AI tool, read is it safe to use ChatGPT or Claude with client data.
Who does what: a practical division of labour
| Task | AI / automation | Person must own |
|---|---|---|
| Reading a subcontractor invoice | Yes – extract figures, propose a labour/materials split | Confirm the split is genuine before it's used |
| Verifying a subcontractor with HMRC | No – trigger the reminder only | Run the actual HMRC check and record the reference |
| Calculating the deduction once rate is known | Yes – simple arithmetic on a confirmed rate | Confirm the rate used is current, not assumed |
| Preparing the monthly CIS return | Yes – draft from payment records, including nil months | Review and submit; the liability is the contractor's |
| Flagging an inconsistent subcontractor record | Yes – surface the discrepancy | Decide what the discrepancy actually means |
| Judging whether due diligence was "reasonable" | No | Always. This is the exact test HMRC applies to the business, not the software |
CIS and the VAT domestic reverse charge, together
The VAT domestic reverse charge (DRC) can apply on the same transaction as CIS, and the two rules interact rather than sitting side by side. Under DRC, the customer accounts for VAT directly to HMRC instead of the supplier charging it. CIS deductions are still calculated on the net labour amount before VAT, and materials are excluded from the CIS calculation while still being included under DRC. An automation system that handles one of these correctly but not the other will produce a plausible-looking invoice that is wrong in a way that's easy to miss until an audit. We flagged this same gap from the other direction, generic marketing and CRM platforms that quietly can't handle CIS or DRC invoicing at all, in our guide to construction marketing automation tools.
If a platform promising "AI-powered CIS compliance" cannot clearly explain how it handles a DRC transaction differently from a standard one, that's a legitimate question to ask before relying on it, not an edge case to worry about later. Our guide to whether AI can do construction estimating, takeoffs and quotes covers the VAT reverse charge alongside other UK checks.
A seven-point CIS automation checklist
- Confirm every subcontractor's verification status is current for this tax year, not carried over from last year's record.
- Check that every subcontractor invoice separates labour from materials clearly, and query any that don't before payment.
- Set nil-return reminders for every month, since these are now mandatory whether or not you paid a subcontractor.
- Decide, in writing, which CIS tasks your automation is allowed to complete unsupervised and which always need sign-off.
- Keep one source of truth for subcontractor records rather than letting your CRM, accounting software and inbox each hold a slightly different version.
- Review your due diligence process specifically against the "knew or should have known" standard, not just against whether your returns were filed on time.
- Confirm whether any of your subcontractor payments involve the VAT domestic reverse charge, and check your system treats those differently.
If you'd rather have this built and checked by people who work inside construction businesses rather than a generic accounting-software vendor, that's the kind of system our AI Business Manager service builds, alongside the wider AI Admin System for Trades.
CIS and AI automation: common questions
Can AI verify a subcontractor's CIS status?
AI can prompt you to run a verification and can track when one is due, but the actual verification is a factual check against HMRC's own system. It should be run and recorded properly, not inferred or assumed by an AI tool based on a subcontractor's paperwork.
What changed with CIS in April 2026?
Three things: mandatory monthly nil returns were reinstated after being removed in 2015, HMRC introduced a "knew or should have known" fraud test aligned with the VAT Kittel test, and Gross Payment Status can now be cancelled instantly for fraud-connected transactions with a five-year wait to reapply, up from one year.
Is CIS software the same as AI automation?
Not necessarily. Most established CIS software (Sage 300 CIS, Archdesk and similar) uses rules-based logic connected directly to HMRC's systems for verification and returns, which is appropriate for that task. AI adds value on top of that by handling the unstructured work around it: reading invoices, flagging inconsistencies, chasing missing documents. The two work best combined, not as substitutes for each other.
What happens if AI gets a CIS deduction wrong?
The contractor is liable, not the software provider. HMRC will pursue the contractor for the shortfall, plus interest and potential penalties. This is precisely why verification, rate confirmation and due diligence should stay as human-owned checkpoints rather than fully automated decisions.
Do I still need CIS deductions if my subcontractor is a limited company?
Yes. Company structure does not exempt a subcontractor from CIS. Verification and the correct deduction rate still apply, based on the company's own CIS registration status with HMRC.
Can I reclaim an over-deduction from HMRC directly?
No. An over-deduction must be reimbursed to the subcontractor directly, with an amended return filed to HMRC. This is one reason getting the labour/materials split right at invoice stage matters more than fixing it retrospectively.
Free AI search check
Does ChatGPT recommend your company?
When someone asks ChatGPT, Gemini or Perplexity to recommend a builder or contractor, is your company named? Find out where you stand today.
See how AI engines answer about you