When CIS Verification Fails on a Friday Afternoon

It's twenty past four on a Friday. You've got three subbies on site finishing a kitchen rip-out and they need paying tonight. You log into HMRC's CIS service to verify the new lad before you process the run. Two come back fine. His comes back at 30%.

You know he's registered net. You paid him at 20% on a smaller job two months ago. But the verification system doesn't care what you know. It only cares what HMRC's database says, right now, when you ask it.

This is the gap between the software you're told you need and the software that actually handles your week.

The real cost

A 30% deduction on a £2,400 weekly figure is £720 instead of £480. The subbie wasn't expecting it. You weren't expecting it. If you pay him at 20% to keep the peace, you're personally on the hook for the difference if HMRC pulls you up. If you pay him at 30%, you've now got a Friday-evening conversation about why his money is short.

From April 2026 the stakes climbed. HMRC has new powers to remove gross payment status immediately where they reckon a payment was connected to fraud. The bar is "knew or should have known". That phrasing matters. It puts the burden of proof on you, not them. You need to be able to show that you verified the right person, with the right UTR, on the right date, and you got the answer the system gave you.

If your verification process is "I rang the office and Sandra checked it", you don't have that audit trail.

How most contractors handle it now

Three patterns, all of them familiar.

The first: you keep a spreadsheet of subbies, their UTRs, their NI numbers, and the deduction rate you last got back. You re-verify when you remember to. Mostly you don't. The spreadsheet gets a year out of date and one Friday it bites you.

The second: you let your accountant handle CIS at the end of the month. They reconcile what you've paid against what you should have paid. By the time anything is wrong, you've already paid five subbies the wrong rate.

The third: you use a job management system that "supports CIS". You enter the deduction rate manually based on what the subbie tells you. The software calculates the deduction. It doesn't verify with HMRC. It doesn't know if the rate is current. It produces a tidy statement that's wrong.

All three patterns have the same root problem. Verification is a human task that gets skipped because it's tedious and the consequences aren't visible until they are.

How Field Forge handles it

When you add a subbie to a job, Field Forge calls HMRC's CIS verification service in the background. The response is logged with a timestamp and stored against the subbie's record. If the result doesn't match what you have on file, you get a flag before you can run the payment, not after.

Mid-month and end-of-month re-verifications happen automatically. The system tells you which subbies need re-verifying based on the two-tax-year rule, so you're not relying on memory.

When April 2026's new HMRC powers come into play, you've got a complete log of every verification request and response, mapped to the payment that came out of it. That's the audit trail that protects your gross payment status if HMRC ever asks.

The deduction calculation itself is deterministic. AI doesn't touch financial figures. It's straight maths on the verified rate.

One thing you can do right now

Even if you never use Field Forge, do this on Monday: pull every subbie you've paid in the last six months, list their UTRs, and re-verify each one through HMRC's online service. Save the results with the date. If anything has changed, you'll find it before HMRC does.

It's a boring afternoon. It's also the cheapest insurance policy you'll ever buy against a Friday in November.