Every client segment this series has covered so far, bookkeepers, sole traders, landlords, limited companies, ecommerce sellers, charities, audit clients, has one thing in common: the compliance cycle repeats annually, or at most quarterly. Construction Industry Scheme (CIS) clients don't work that way. A contractor operating under CIS has a filing obligation that repeats every single calendar month, for every subcontractor they've paid that month, with a hard deadline and a penalty regime that starts accruing from the first day it's missed.
For accounting firms and payroll bureaus that run CIS for contractor clients, that monthly cycle, multiplied across every subcontractor on the book, is a fundamentally different document and deadline problem than anything a landlord or limited-company client generates.
How CIS Actually Works, in Brief
Under CIS, a contractor paying a subcontractor for construction work must deduct money from that payment and pass it to HMRC as an advance payment toward the subcontractor's tax and National Insurance. The deduction rate depends on the subcontractor's status with HMRC: 20% for subcontractors registered under CIS, 30% for those who aren't registered, and 0% for subcontractors who hold gross payment status. Before a contractor can pay a new subcontractor, they must verify that subcontractor with HMRC, and HMRC tells the contractor which of the three rates to apply.
That verification step means the firm can't treat a new subcontractor as a simple data-entry task. It's a status check that has to happen before money moves, and the answer determines how much of every future payment gets withheld.
A Return Due on the 19th of Every Month, Not Once a Year
Contractors must file a CIS300 monthly return with HMRC covering every payment made to subcontractors in that tax month, and it has to reach HMRC by the 19th of the following month, even if no subcontractors were paid, in which case a nil return is still required. Miss it, and the penalties escalate on a fixed schedule: an initial £100 fixed penalty as soon as it's a day late, a further £200 at two months, a further penalty of £300 or 5% of the liability at six months, and a second further penalty at twelve months that can run to the full liability, with minimums of £1,500 or £3,000 depending on the circumstances.
On top of the monthly return itself, the contractor has a separate, subcontractor-facing obligation: a written payment and deduction statement must go out to each subcontractor within 14 days of the end of the tax month it covers, showing the contractor's details, the tax month, the subcontractor's name and UTR, the gross payment, any materials deducted, and the deduction taken. A firm running CIS for a contractor with fifteen active subcontractors isn't producing one document a month, it's producing one return and fifteen separate statements, every month, on two overlapping deadlines.
The Subcontractor Isn't the Firm's Client, but the Documents Still Have to Reach Them
This is the part that has no real equivalent in the segments already covered. A landlord's MTD obligation, an audit file, a charity's public accounts, all of those involve documents moving between the firm and its own client, or between the firm and a regulator. CIS adds a third party into the loop who is neither: the subcontractor is the contractor client's business relationship, not the accounting firm's, but the firm (or the payroll bureau acting on the contractor's behalf) is often the one that has to get a UTR and verification details from that subcontractor before the first payment, and get a compliant deduction statement back to them every month after.
Want to see how this works in practice? Explore Osuria’s client portal
Handling that over email means the firm is exchanging tax documents containing a UTR and payment details with people who never signed up as its clients and have no reason to trust a random inbox with that information. It also means the paper trail, who was sent what statement, and when, sits scattered across however many email threads the firm has open with however many subcontractors, across however many contractor clients, rather than in one place the firm can point to if HMRC or the contractor ever asks.
Why This Scales Badly for Firms With More Than One Contractor Client
The arithmetic is what makes this segment different from a compliance-once-a-year client base. A firm with twenty contractor clients averaging ten active subcontractors each is managing two hundred verification relationships and producing roughly two hundred deduction statements a month, on top of twenty CIS300 returns, every single month, indefinitely, not as a seasonal spike. A missed statement or a late return doesn't cost the firm a quiet catch-up later in the year, it costs a specific, dated penalty that started accruing the moment the 19th passed.
Firms managing this from a shared inbox or a spreadsheet of subcontractor statuses are relying on someone remembering to check verification status, generate the right statement, and send it to the right person, two hundred times a month, without a system that flags what's outstanding before the deadline rather than after.
What a Structured Process Looks Like for CIS Clients
The firms handling CIS well are treating it the same way they'd treat any recurring, deadline-driven, multi-party document flow: one place to see, per contractor client, which subcontractors are verified and at what rate, which statements have gone out this month and which haven't, and a record that survives an HMRC enquiry or a contractor asking "did you send that to my sub in March." A branded client workspace that can extend limited, secure access to the people who need specific documents, not just the firm's direct client, is a better fit for that shape of problem than an inbox built for one-to-one correspondence.
Osuria brings document collection, secure document delivery, and deadline visibility together in one branded workspace, built to handle exactly this kind of recurring, multi-recipient obligation rather than assuming every document only ever needs to reach one client.
The Volume Only Grows With the Book
A firm that picks up construction clients rarely picks up just one. Contractor clients tend to arrive in clusters, through trade referrals, and each new contractor brings its own list of subcontractors who all need verifying and all need a statement every month from day one. Firms that build a repeatable, visible process for this now are adding contractor clients without adding proportional admin risk. Firms still tracking it ad hoc are one new contractor client away from finding out how many verification checks and statements fell through the cracks last month.
If your firm's CIS workload is generating more "did we send that statement" questions than the returns themselves justify, it's worth seeing what a purpose-built, branded client workspace looks like in practice. Explore the Digital Workspace or start using Osuria to see how a structured process handles a client base where every month brings its own full set of deadlines, for every subcontractor on the book.