CIS300 Monthly Return From Invoices: Workflow Guide

A CIS300 monthly return from invoices starts with payments actually made in the tax month, not with whatever invoices happened to arrive in the inbox. For CIS, the month runs from the 6th to the 5th. The prep job is to group those payments by subcontractor, split out the cost of materials, calculate the amount subject to deduction and the CIS deducted, and then file the return from that checked monthly dataset.

One date point is worth correcting up front because it causes regular confusion. The monthly return itself must reach HMRC by the 19th of the following month. The 22nd applies to paying the CIS deductions electronically, not to submitting the CIS300. If a contractor is preparing the return for payments made from 6 May to 5 June, the return needs to be with HMRC by 19 June, while the deductions payment is due by 22 June if paid electronically.

That distinction matters because the return follows the payment date, not the invoice date in isolation. A subcontractor invoice dated 4 June but paid on 7 June belongs in the tax month running from 6 June to 5 July. A worksheet built from invoice dates alone will put payments into the wrong month and create correction work later.

From 6 April 2026, nil months also need an explicit action. If a mainstream contractor made no subcontractor payments in the tax month, the right response is not to skip the process. It is to file a nil return or tell HMRC the scheme is inactive for the period. That means the monthly workflow is still live even when the invoice pile is empty.

The useful way to think about the task is this: the filing screen is the last step. The real work is converting a stack of subcontractor invoices, payment records, and supplier details into one reviewable monthly worksheet with one line per subcontractor. Once that worksheet is right, the CIS300 is mostly a submission exercise.

Build one CIS300 row for each subcontractor before you file

The contractor's monthly return is prepared per subcontractor for the tax month, not per invoice. If the same bricklaying subcontractor sent three invoices between 6 May and 5 June and all three were paid in that period, those payments still need to end up as one monthly line for that subcontractor when the return is filed. The invoice-level detail matters for review, but the filing logic is monthly and subcontractor-based.

A workable prep sheet usually carries these columns for each subcontractor:

• subcontractor name exactly as verified
• UTR and any matching business details needed to avoid identity mismatches
• verification number or verification reference where relevant
• total payments made in the period
• cost of materials
• amount subject to deduction
• CIS deducted

Those fields should be preserved separately. Bookkeepers get into trouble when they try to work backwards later from the net amount paid. A net payment does not tell you, on its own, how much of the gross payment was materials, whether the subcontractor was on 20% or 30%, or whether the row should have been gross-paid. If the prep sheet loses those distinctions, the filing review becomes guesswork.

There is also a return-level declaration sitting behind every line. The contractor is confirming that the listed subcontractors are not employees and that the subcontractors who needed verification have been verified. In practice, that means employment-status review and verification are part of the same month-end control as the invoice totals. They are not a separate admin task to be cleaned up afterwards.

The best monthly worksheet mirrors the return's logic while still keeping invoice-level support underneath it. One line per subcontractor for the filed month, backed by the invoices and payment records that produced the totals, gives the reviewer something they can actually test before the figures go into HMRC's service or commercial CIS software.

Turn individual invoices into monthly CIS300 totals without losing the materials split

This is the section most generic CIS guides leave vague. A subcontractor invoice is not ready for the CIS300 until it has been translated into the figures HMRC actually cares about. Suppose a subcontractor submits an invoice for work in the month with GBP 8,000 labour and GBP 2,000 materials, with a 20% deduction rate applying to the labour element. The mapping looks like this:

Worksheet field	Figure
Total payment	GBP 10,000
Cost of materials	GBP 2,000
Amount subject to deduction	GBP 8,000
CIS deducted	GBP 1,600
Net payment	GBP 8,400

That is the basic logic behind the monthly return. The total payment and the materials figure are both needed because the deduction is calculated on the amount left after allowable materials are taken out. If the same subcontractor sends three invoices in the same tax month, the prep sheet should keep the invoice-level lines for audit trail purposes, then roll them into one subcontractor total for filing. For example, three payments of GBP 4,000, GBP 3,500, and GBP 2,500 with combined direct materials of GBP 1,800 do not become three CIS300 entries. They become one monthly subcontractor row showing GBP 10,000 total payments, GBP 1,800 cost of materials, GBP 8,200 amount subject to deduction, and GBP 1,640 CIS deducted for the month.

The difficult cases are the messy ones. HMRC's approach is that only direct materials paid for by the subcontractor reduce the amount subject to deduction, and VAT is excluded when working out that deduction basis. If the subcontractor cannot support the materials figure, or the invoice lumps everything into a one-line "supply and fit" amount, the contractor still has to arrive at a reasonable figure before filing. That is why it helps when the invoice already separates labour from materials. If it does not, the reviewer needs evidence, a defensible estimate, or a decision to treat more of the payment as labour rather than guessing later.

That is also where invoice review discipline matters. If the source document is missing the detail you need, start with what a CIS subcontractor invoice should show before it reaches your monthly return. If the payment includes VAT considerations that affect how the invoice is reviewed, use where UK VAT invoice rules overlap with CIS invoice review as the companion check rather than trying to rebuild VAT rules inside the CIS worksheet.

For teams handling dozens of PDF invoices each month, the preparation layer is often the bottleneck rather than the filing step. A tool built for extracting subcontractor invoices into a CIS300-ready spreadsheet can turn PDFs and emailed invoices into structured XLSX, CSV, or JSON output with file and page references preserved, so the bookkeeper reviews a monthly worksheet instead of retyping every line. That does not replace the CIS filing software or HMRC service. It makes sure the numbers being keyed or imported into them were built from a reviewable source trail.

---

Keep verification numbers and deduction rates attached to the right subcontractor

Once the invoice values are correct, the next risk is applying them to the wrong deduction basis. Verification is what tells the contractor whether the subcontractor should be paid under deduction at 20%, under deduction at 30%, or gross with no deduction at all. A monthly worksheet that carries only invoice totals, without the verified rate and identity details beside them, is incomplete.

HMRC's current rule is practical and easy to miss: a subcontractor needs to be verified again if they have not appeared on a CIS return in the current or last two tax years. That matters when an old supplier comes back onto site after a long gap. The previous spreadsheet row may still exist, but that does not mean the verification basis can simply be copied forward.

The verification number is not just a filing formality. It is the link between the subcontractor's identity on the invoice, the business details held in the contractor's records, and the rate HMRC expects the contractor to use. If the trading name, legal name, or UTR has drifted from what was verified, the rate can be wrong even though the invoice totals are fine. In month-end terms, the question is not "does this look like the same subcontractor?" but "does this payment line up with the subcontractor HMRC told us how to pay?"

Gross payment status fits into the same control. The subcontractor still belongs on the monthly return, but the deduction amount is nil because the rate is 0%. That is why a gross-paid row should still sit in the worksheet beside the payment total and materials figure rather than being excluded from the prep process. If the team needs a deeper refresher on the rate side of that issue, how gross payment status changes whether CIS is deducted at all is the right supporting read.

In practice, keeping the verification reference, the rate, and the exact subcontractor identity attached to each monthly row prevents a common class of error: accurate invoice math filed against the wrong subcontractor status. Those mistakes are harder to spot at the submission stage than they are in the prep sheet.

File the return, handle nil months, and correct mistakes the HMRC way

Once the worksheet is complete, the submission route is straightforward. Contractors can file through HMRC's online CIS service or through commercial CIS software. The choice changes how the figures are entered, but not what has to be prepared first. HMRC's own service is workable when the team is manually keying a relatively small number of subcontractor rows. Commercial software becomes more practical where the month involves larger volumes, repeat subcontractor records, or a handoff from a worksheet that the team wants to import or manage inside payroll or CIS workflows. Either way, the service still needs the same monthly subcontractor totals, the same materials figures, and the same deduction basis that the worksheet has already established.

Nil months now need active handling. HMRC's CIS 340 guidance on nil returns and late monthly return penalties says that from 6 April 2026 mainstream contractors who have not paid any subcontractors must file a nil return or notify HMRC of a period of inactivity, and if they do neither a penalty is due. For a contractor that knows there will be no subcontractor payments for a while, an inactivity request can cover a period of up to six months. For a contractor that simply had no payments this month, the nil return is the cleaner month-end action.

Corrections need a different mindset from VAT-style netting off. If the worksheet is wrong before filing, fix the worksheet and then submit the correct month. If the return has already been filed, the contractor needs to correct that filed month through HMRC's amend-return process or the equivalent correction route in commercial software. Many practitioners refer to that as a replacement return because the corrected filing replaces the original month in practical terms. The important rule is that the return should reflect what was actually paid and deducted in that month, not what the team wishes had been paid.

Typical correction triggers are ordinary operational misses: one subcontractor was left out of the monthly roll-up, materials were overstated on a supply-and-fit invoice, or a returning subcontractor was left on the old rate without re-verification. Those are all reasons to correct the filed month itself rather than trying to force the difference into the next period.

One software-specific point is worth remembering during that process. HMRC guidance says commercial CIS software returns must not include negative values. If a correction would produce a negative figure on a row, that is a sign the team should use the formal amendment route, not try to reverse the earlier month with improvised minus entries.

---

Reconcile the month before the 19th and pay deductions by the 22nd

The strongest control before filing is a simple reconciliation chain. Start at the invoice level, confirm each payment belongs in the relevant tax month, roll those payments into one subtotal per subcontractor, and then compare those subtotals with the CIS300-ready worksheet. After that, compare the worksheet with the bookkeeping records or CIS control account. Once the return has been submitted, the filed figures and the deductions paid to HMRC should still reconcile back to that same monthly support.

The timeline should also be checked in that order. The return needs to reach HMRC by the 19th. The deductions payment then needs to reach HMRC by the 22nd if paid electronically, or earlier where the 22nd falls on a weekend or bank holiday. Treating those as two separate deadlines avoids one of the most common month-end misunderstandings around CIS300 work.

Before submitting, it helps to stop on a short failure-point review:

• every subcontractor paid in the tax month appears in the roll-up
• materials have evidence behind them, or a documented reasonable estimate
• verification is current for any subcontractor returning after a long gap
• gross-paid subcontractors are still included on the worksheet, but with no deduction
• nil months have been handled through a nil return or inactivity request, not left untouched

That review is where payment dates, invoice dates, and deduction rates need to be kept separate in the reader's mind. An invoice can belong to one month, the payment to another, and the deduction rate to a verification check done at a different point again. The prep sheet is only trustworthy when every monthly row can be traced back to the payment actually made in that tax month and the subcontractor status that applied when it was made.

Seen that way, the CIS300 is not mainly a filing exercise. It is a monthly reconciliation exercise that ends with filing. Contractors who build the dataset first, then submit from a checked worksheet, spend less time correcting returns and less time arguing with their own records after the deadline has passed.