CIS132 for Limited Companies: EPS Offset Guide

For a limited company, the point behind most CIS132 searches is simple: the filing that matters is the Employer Payment Summary. CIS132 is the record of amounts set off, not a separate reclaim form. A limited company reports CIS deductions suffered year to date on the EPS, HMRC offsets that amount against PAYE, National Insurance, student loan deductions, and any CIS liabilities due, and any excess only carries forward within the same tax year.

That is why the reclaim sits inside payroll RTI. It does not go through Self Assessment, and it should not be claimed through the Corporation Tax return. If the company enters suffered CIS in the wrong place, the problem usually shows up later as an unexpected PAYE balance or a year-end surplus that is harder to recover than it should be.

HMRC's CIS 340 guidance on company set-off through the EPS makes the structure clear: company subcontractors report suffered CIS on the EPS, carry any excess forward only within the same tax year, and deal with any balance still left after the final FPS and EPS as a repayment or Corporation Tax set-off issue.

In practice, the real control question is not whether a separate CIS132 form must be filed. It is whether the year-to-date suffered CIS figure on the EPS is correct and backed by a defensible running record. CIS132 can be that record, but HMRC also accepts an equivalent schedule that shows how each amount was set off. That is the answer most CIS132 limited company searches are actually looking for.

Build the monthly register from each PDS, then submit the year-to-date EPS figure

Start with the statements, not the payroll screen. Each contractor's payment and deduction statement needs to feed a single register for the tax month. If the paperwork itself is inconsistent, first check what a UK CIS payment and deduction statement needs to show so the register is built from the right fields.

A workable register is plain: contractor name, payment date or tax month, gross paid, materials where relevant, CIS deducted, and a running year-to-date suffered total. The month-end EPS number is not just that month's PDS total. It is the cumulative suffered CIS figure after the latest statements have been added to the register and checked against what has already been claimed.

The monthly sequence is straightforward when it is treated as a control routine. First, log every new statement for the closing tax month. Second, total only the new CIS deducted amounts and add them to the prior year-to-date balance. Third, confirm how much of that cumulative balance has already been relieved against earlier PAYE and CIS liabilities. Fourth, file the EPS using the updated year-to-date figure, not just the current month's intake. In most payroll software, the CIS deductions suffered field only appears where the employer is set up as a CIS subcontractor, which is another reason the company setup needs to be right before month-end.

For example, if the register stood at GBP 8,600 suffered to the end of month 4 and the month 5 statements add another GBP 2,150, the EPS field for CIS deductions suffered should show GBP 10,750 year to date. That is the number HMRC reconciles against the company's payroll liabilities, so a clean register matters more than memorising where one software package puts the box on screen.

This is also where extracting CIS payment statements into a monthly register becomes a practical control rather than a software talking point. When contractor statements arrive as PDFs or scans in mixed layouts, Invoice Data Extraction can extract the key fields into Excel, CSV, or JSON so payroll or finance staff start from one spreadsheet-ready schedule instead of retyping each statement before the EPS is filed.

How the offset works against PAYE, NIC, student loans, and CIS liabilities

The EPS relief becomes much easier to manage when the team separates current-month documents from the cumulative tax-year position. Suppose the company had already reported GBP 9,100 of CIS suffered by the end of month 4, and GBP 6,500 of that had already been relieved against liabilities. That leaves GBP 2,600 of unrelieved CIS coming into month 5.

Month 5 adds another GBP 4,200 from new payment and deduction statements, so the EPS now shows GBP 13,300 CIS suffered year to date. The month 5 payroll and contractor figures produce GBP 1,450 of PAYE, GBP 620 of employee NIC, GBP 710 of employer NIC, GBP 120 of student loan deductions, and GBP 300 of CIS due on the company's own subcontractors. Total current liabilities are GBP 3,200.

The arithmetic matters. The company came into month 5 with GBP 2,600 still unused, then added GBP 4,200 of new suffered CIS, giving GBP 6,800 available for relief. HMRC offsets GBP 3,200 of month 5 liabilities against that pool, so the company pays nothing for that period and still carries GBP 3,600 of CIS suffered forward into month 6. That is the practical answer to the limited company CIS reclaim PAYE question: suffered CIS reduces the payroll and CIS liabilities first, and only the balance left after that carries forward.

The control point is the running balance, not the latest statement on its own. If the register does not show how much has already been relieved and how much is still available, the EPS can drift away from the real position very quickly.

What changes after 5 April if a surplus is still left

The carry-forward stops at the tax-year boundary. If there is still unrelieved CIS suffered after the final FPS and final EPS for month 12, that balance does not roll into the next tax year and continue offsetting the next payroll run.

At that point the issue changes from payroll set-off to recovery. The company can ask HMRC to repay the surplus or, where appropriate, set it against Corporation Tax. HMRC now offers an online repayment route for limited companies and agents, but the claim still depends on the PAYE, CIS, and Corporation Tax records lining up with the figures already filed. In practice, that means the company should expect to have all relevant returns submitted before it treats the surplus as recoverable cash.

This is where cash-flow planning matters. A year-end surplus is valuable, but it is not the same as cash in the bank on 6 April. Many practitioners budget for a wait measured in weeks rather than days, and a 6 to 18 week working assumption is more realistic than expecting an immediate refund.

If that sounds different from how the sole-trader CIS reclaim route differs from the limited-company route, that is because it is. Sole traders reconcile through Self Assessment. A limited company closes the year through payroll RTI first, then claims or reallocates any surplus still left after the final submissions.

---

Correcting a wrong EPS figure and fixing HMRC PAYE demands

If the CIS suffered figure on the EPS was wrong, correct the cumulative position with a later EPS. Do not try to fix a CIS suffered mistake through the FPS, because the FPS reports employee pay and deductions, while the EPS is where the company tells HMRC how much CIS suffered is available year to date.

Most HMRC PAYE demands in this area come from one of four problems: the EPS was not sent, the EPS carried the wrong cumulative amount, the register was built from incomplete statements, or the team cannot evidence the figure when HMRC challenges it. In practice, the demand often arrives months after the original error, which is why a weak monthly control becomes an expensive clean-up exercise.

The fix is usually straightforward. Rebuild the schedule from the payment and deduction statements, confirm the year-to-date suffered total, compare it with what was filed, and send a corrective EPS if the filed number was wrong. If HMRC asks for support, be ready to provide both the statements and the register behind the claim.

That evidence point matters. HMRC's current guidance says it can ask for proof of the deductions and, if the company does not respond by the deadline, HMRC may correct the claim and stop further claims for the rest of the tax year. A clean register is what turns a disputed figure back into a defensible payroll position.

Controls that reduce CIS reclaim friction month after month

A stable process is simple. Collect every statement as it arrives, post it to the register before payroll is finalised, keep the cumulative relieved and unrelieved balances visible, and retain the supporting record behind each set-off. Whether that record is kept on CIS132 or on the company's own schedule matters less than whether another person can follow it a month later without rebuilding the file from scratch.

It is also worth remembering why gross payment status removes CIS deductions at source. If the company is paid gross, the monthly reclaim workflow largely disappears because there is no suffered CIS to offset in the first place.

That route distinction keeps the wider CIS picture clear. Limited-company set-off sits inside payroll RTI, sole-trader reclaims sit in Self Assessment, and contractor-side CIS returns are a separate monthly obligation. Keeping those lines separate is what stops a month-end tax control from turning into a year-end repair job.