CIS Returns HMRC: How to File Without the Stress

You're finishing a job outside Stirling, chasing an electrician's invoice and checking whether the labourer's payment left the bank. Then the bookkeeper asks about CIS. Last month was busy; this month you haven't paid any subcontractors. Does HMRC still need something?

That quiet month deserves as much attention as the busy one. Handling CIS returns for HMRC is easier when you separate payment checks, filing decisions and record-keeping, rather than trying to sort everything out just before submission.

What the CIS Is and Who Has to Register

A small Scottish building business can have straightforward site work but awkward payment administration. The owner agrees the work, a subcontractor sends an invoice, and someone in the office must establish how that payment should be treated before releasing it.

The Construction Industry Scheme, or CIS, connects subcontractor payments, verification status and deductions through recurring reporting to HMRC. The scheme originated in 1971, while the current monthly reporting framework replaced the voucher system on 6 April 2007, as explained in HMRC's history of CIS reform.

Establish your position before paying

Don't decide that CIS is irrelevant because your business is small, you describe yourself as a property business, or the subcontractor only helps occasionally. Equally, don't apply a blanket expenditure test without checking which contractor category applies to your activities.

Use a CIS contractor registration review to establish your position before setting up the payment process. Contractor registration and subcontractor registration serve different purposes, so be clear about which role your business performs.

Prepare a working registration file containing:

• Business identity: Your legal name, trading name, tax references and contact details.
• Trading background: What construction work you undertake and when the relevant activity began.
• Payment arrangements: Who engages subcontractors, approves invoices and releases payments.
• Worker arrangements: Contracts and descriptions of how people work on site.

Treat that file as preparation, not an exhaustive list of HMRC's registration questions.

Practical rule: Resolve employment status before relying on a subcontractor label. An invoice headed “self-employed” isn't a substitute for examining the working arrangement.

Verifying Subcontractors Before You Pay Them

Consider a kitchen fitter arranging payment to an electrician. The invoice names a business, but the bank details belong to an individual and the bookkeeping record uses an abbreviated trading name. That's a reconciliation problem before it becomes a deduction problem.

The practical objective is to connect the person or business being paid, the verification record and the payment settings. Don't copy another subcontractor's settings because they do similar work.

Keep verification alongside the payment records, rather than buried in an email conversation.

Handle mismatches before the payment run

A useful subcontractor verification process should leave the bookkeeper with a clear result and supporting details. If information doesn't match, investigate rather than guessing the deduction treatment or assuming the worker has never registered.

• Check identity details: Compare the legal name and tax reference supplied with your subcontractor record.
• Record the result: Keep the verification evidence with the payment instructions.
• Escalate uncertainty: Ask the subcontractor to confirm discrepancies before you finalise the calculation.

For a labourer joining the same job, start with their own details. The electrician's treatment tells you nothing about another worker's position.

Insurance is a separate onboarding question. For broader reading, ABS Insurance Brokers liability insights from ABS Insurance Brokers Pty Ltd offers an insurance-focused perspective, not authority on UK CIS treatment.

Don't let an insurance certificate stand in for verification, or a verification result stand in for a review of employment status. Keep those checks distinct.

Preparing and Submitting a Monthly CIS Return

Start with the bank transactions, not a pile of unpaid invoices. For a small contractor, the useful working document is a subcontractor payment schedule showing who received money, when it moved and how the deduction was calculated.

Use HMRC's filing guidance as the reference point when preparing the submission.

Build a payment-led reconciliation

The CIS period doesn't follow the calendar month. Its boundaries and filing deadline are set out in the deadline section below, so configure your report around those boundaries rather than accepting your software's default month-end selection.

For an illustrative contractor, the preparation might involve an electrician's payment, a labourer's payment and a supplier invoice that needs separate classification. Don't assume every entry carrying a construction-related description belongs on the return.

• Match payments: Trace each relevant payment to the bank and subcontractor ledger.
• Check calculations: Review the payment breakdown and the verification evidence supporting the treatment.
• Resolve differences: Investigate credits, duplicate entries and payments posted against the wrong supplier.
• Review the draft: Compare the proposed return with the reconciled schedule before submitting.

Software can reduce rekeying, but it won't recognise every incorrectly coded transaction. A clean-looking report can still contain the wrong payment date or omit a transaction posted elsewhere.

Keep this video available alongside your working instructions.

After filing, save the acknowledgement with the submitted figures. If you discover an error, check the correction procedure available through your filing service and retain both the original working papers and the correction trail. Changing the bookkeeping alone doesn't demonstrate that the submitted return was corrected.

Nil Returns, Inactivity Notices and the April 2026 Rule Change

No subcontractor payments doesn't mean no CIS administration. For mainstream contractors, the rule taking effect from 6 April 2026 requires a monthly nil return unless HMRC has been notified in advance that no relevant payments will be made; an inactivity request covers six months, according to HMRC's CIS340 guide.

The useful distinction is between an unexpectedly empty month and a planned gap. A joiner who occasionally brings in help needs a different routine from a business that knows it won't engage subcontractors for an extended period.

Choosing What to Send When No Subcontractor Was Paid

A nil CIS return routine suits businesses whose workload changes without much warning. Inactivity can reduce repetitive administration when the gap is predictable, but someone must monitor its end and any change in plans.

An inactivity notice belongs in the diary as well as the filing folder. Don't treat it as permanent permission to stop checking CIS.

Understanding CIS Deadlines and Penalties

The return must reach HMRC by the 19th following the relevant CIS tax month, which runs from the 6th to the 5th. For example, payments in the period ending 5 June must be reported by 19 June, under HMRC's monthly return rules and published penalty schedule.

The following charges come from that same published schedule. The amounts describe filing exposure, not a substitute for calculating the underlying deductions correctly.

Prevent the administrative gap

The awkward failures aren't always calculation errors. A bookkeeper prepares a draft, the director assumes it has been filed, and neither checks for an acknowledgement. Or the person responsible leaves, but their calendar reminders don't transfer with the work.

Give submission responsibility to a named person and agree who covers their absence. A reminder that says “CIS due” is weaker than an instruction identifying the return, its review status and the person authorised to submit it.

If a penalty arrives, compare the notice with the filing evidence and any inactivity correspondence. If you believe it's wrong, follow the notice's challenge instructions and build a dated account of what happened.

Don't assume that correcting the return automatically resolves the penalty. Treat the filing problem and the penalty correspondence as separate tasks, with separate records of completion.

Record-Keeping That Survives an HMRC Inspection

A submitted return is a summary. Your working records need to explain how you reached it, particularly where the invoice, payment and deduction aren't identical figures.

The most useful filing system follows the questions a reviewer would ask: who was paid, why was that treatment used, and where did the reported amount come from? Organise the evidence around those questions rather than around whichever application produced it.

Keep the records accessible to whoever covers the bookkeeping.

Use folders that explain the figures

• Subcontractor records: Keep identity details, verification evidence, contracts and notes supporting employment-status decisions together.
• Return evidence: Store submitted figures, acknowledgements and explanations of amendments by reporting period.
• Reconciliations: Retain the schedule connecting invoices, payments, deductions and bookkeeping entries.

The reconciliation should explain differences, not merely repeat totals. If the invoice value differs from the bank payment, record the reason so another person can follow the calculation without reconstructing it from messages.

A useful internal test is to select a payment and follow it through the entire file. Can a colleague identify the subcontractor, find the supporting treatment, understand the deduction and locate the relevant submission evidence?

Review test: Someone unfamiliar with the job should be able to follow the payment trail without asking the site manager what happened.

Don't rely on a software dashboard as your complete evidence file. Keep supporting documents and readable exports accessible, and agree the applicable retention requirements with your adviser before deleting historical records.

That approach also makes handovers less fragile. The business retains the explanation, rather than leaving it in the memory of the person who normally runs CIS.

A Practical Monthly CIS Checklist

Keep the routine short enough to repeat, but specific enough that someone else can cover it. Use the tax-month boundaries, nil-return decision and filing rules above rather than working from memory.

• Collect the evidence: Gather subcontractor invoices, payment details and unresolved queries.
• Review worker records: Investigate new subcontractors and changes to existing details before approving payments.
• Reconcile the period: Match the payment schedule to the ledger and bank transactions.
• Choose the filing route: Confirm whether the period needs a payment return, a nil declaration or action concerning an inactivity notice.
• Approve and submit: Have the responsible person review the figures and complete filing.
• Save completion evidence: Store the acknowledgement and close outstanding correction tasks.
• Check the payment position: Review the PAYE/CIS account separately rather than assuming submission settles the account.

For support, options include an in-house bookkeeper, a payroll bureau or Stewart Accounting Services, which provides subcontractor verification and monthly CIS return assistance.

If you're repeatedly rebuilding payment records or discovering missing submissions, arrange a CIS process review before the next filing cycle. Bring your latest return, subcontractor ledger, bank reconciliation and any inactivity correspondence so your adviser can identify exactly where the routine needs fixing.