PAYE Penalties for Late Submission and Filing: The RTI Regime for Property-Business Employers

Property-business employers sit inside the same real-time information (RTI) penalty regime as any other UK employer, but the operational risk profile is distinctive. A landlord limited company paying a director's Personal Allowance salary monthly, a portfolio operator with one or two employed property managers, and a serviced-accommodation business with cleaning and front-of-house staff all face the Schedule 55 paragraph 6C late-filing penalty cycle every month of the tax year. The penalty is small per failure (£100 for a small employer) but it attaches monthly, and it stacks with the Schedule 56 late-payment escalator where PAYE is paid late as well as filed late.

This page sets out the operational mechanics of the RTI penalty regime as it actually applies to property-business employers. We cover the statutory framework, the on-or-before deadline rule, the fixed monthly penalty banding, the two HMRC operational concessions that soften the edges of the regime, the Schedule 56 late-payment escalator, the reasonable-excuse defence, and the boundary with Schedule 24 inaccuracy penalties and Schedule 41 failure-to-notify penalties. We end with the interaction between the RTI regime and Making Tax Digital for Income Tax, which becomes mandatory for the largest landlords from 6 April 2026.

The statutory framework: Schedule 55 paragraph 6C and Schedule 56 item 2

The RTI late-filing penalty sits at paragraph 6C of Schedule 55 to the Finance Act 2009. Paragraph 6C is inside the cross-heading that covers real-time information for PAYE and the apprenticeship levy (paragraphs 6B to 6D), and it sets the fixed monthly penalty banding by employee count. The RTI cross-heading was switched on by the Income Tax (Pay As You Earn) (Amendment) Regulations 2014 (SI 2014/472), which staggered commencement: large employers (50 or more employees) from 6 October 2014, and small employers (1 to 49 employees) from 6 March 2015.

The RTI late-payment penalty sits at Table item 2 of Schedule 56 to the Finance Act 2009, which covers PAYE. Schedule 56 uses the standard escalator architecture introduced by section 107 and Schedule 56 FA 2009, with PAYE-specific calibration in paragraphs 3 and 4 of the schedule. The escalator increases with the count of late payments in the tax year rather than the duration of any single late payment.

The underlying filing obligation for the Full Payment Submission (FPS) comes from regulation 67B of the Income Tax (Pay As You Earn) Regulations 2003 (SI 2003/2682). Regulation 67B requires the employer to deliver an FPS to HMRC "on or before" making the relevant payment to the employee. The on-or-before rule is the trigger point for paragraph 6C: any FPS filed after the payment date is, in principle, a chargeable failure (subject to concessions).

Where no FPS is filed at all, HMRC has a separate power under regulation 75A of the PAYE Regs 2003 to issue a Specified Charge based on prior-period PAYE figures. The Specified Charge sits alongside the paragraph 6C penalty rather than displacing it.

The on-or-before deadline and what counts as late

For a monthly payroll, the on-or-before deadline is the date the employee is actually paid, not the end of the payroll month or the date the payroll is processed in the software. If an employee is paid by BACS on the 28th of the month, the FPS for that month must reach HMRC on or before the 28th. Filing on the 29th is a one-day late failure under paragraph 6C.

The on-or-before rule applies regardless of how the underlying payment is made. It applies to BACS, to faster payments, to cheque payments, and to cash payments. It applies even where no income tax or National Insurance is actually due in the period (for example, where a director's monthly salary sits at or below the National Insurance Primary Threshold).

The two operational concessions that soften the on-or-before rule are HMRC administrative discretion, not statutory exemptions. They reduce the practical exposure of an organised property-business employer who occasionally slips a day, but they do not protect a persistent late filer.

The one-unpenalised-failure-per-tax-year concession

HMRC's published RTI penalty operational policy treats the first FPS failure in any tax year as unpenalised, provided the employer rectifies the position promptly. The concession sits inside HMRC's risk-based administrative discretion within the Schedule 55 framework. It does not appear on the face of paragraph 6C. Employers cannot rely on a future continuation of the concession indefinitely, and HMRC has reserved the right to tighten it in any future tax year.

The three-day risk-based filing concession

From March 2015 onwards, HMRC announced that employers would not face a paragraph 6C penalty where the FPS is filed within three days of the on-or-before deadline, provided the delay is not part of a persistent pattern. The concession was originally framed as a transitional measure during the small-employer commencement period in 2015 but has remained in operational force in the years since. It is reviewed periodically and could be withdrawn.

The risk for property-business employers is the word persistent. A bookkeeper who batches FPS submissions on the last working day of the month, two days after a 28th payday, will rely on the three-day concession every month. That settled pattern is exactly what HMRC has reserved the right to look through. The clean fix is to align FPS submission to the payment date in the payroll software, removing dependence on the concession entirely.

The fixed monthly penalty banding under paragraph 6C

Paragraph 6C(2) sets the fixed monthly penalty by employee count at the date of the failure:

• 1 to 9 employees: £100 per chargeable failure
• 10 to 49 employees: £200 per chargeable failure
• 50 to 249 employees: £300 per chargeable failure
• 250 or more employees: £400 per chargeable failure

The penalty attaches once per tax-month of failure, subject to the one-unpenalised-failure concession and the three-day risk-based concession. A property-business employer who misses three FPSs in a tax year sits at £100 × 2 = £200 (the first failure is unpenalised under the operational concession). The same employer with five missed FPSs sits at £100 × 4 = £400.

An additional uplift applies under paragraph 6 of Schedule 55 where the failure runs beyond 12 months. That uplift is up to 5% of the unpaid tax for non-deliberate failures and up to 100% of the unpaid tax for deliberate failures. In RTI terms the underlying unpaid tax is typically modest, so the 12-month uplift is usually a contained risk, but it is a separate exposure on top of the fixed monthly amounts.

Worked example 1: single-director SPV missing three FPSs

Aldridge Lettings Ltd is a single-director BTL special-purpose vehicle. The director takes a Personal Allowance salary spread across 12 monthly payments. The bookkeeping is done in-house and the director processes payroll the day after each pay date. In months 4, 5, and 6 of the tax year, the director processes payroll on time but forgets to submit the FPS.

HMRC issues a penalty notice after month 5 (the second failure crosses the one-unpenalised-failure concession). Penalty exposure under paragraph 6C: 1 to 9 employees → £100 per month × 2 chargeable failures (months 5 and 6; month 4 is the unpenalised first failure of the tax year) = £200 fixed penalty.

The director's reasonable-excuse defence under paragraph 18 (workload pressure as a single-director SPV with no other employees) is unlikely to succeed under the Perrin four-stage test. Ordinary forgetfulness fails at the third stage of Perrin (is the excuse reasonable in the taxpayer's specific circumstances). The remediation is to submit the missing FPSs immediately, accept the £200, and put a calendar reminder or software-automation safeguard in place so the same pattern does not repeat in the following months.

Worked example 2: portfolio operator with on-time payment but late FPS

Caulfield Estates Ltd runs a 14-property BTL portfolio with one employed property manager on a £32,000 salary plus auto-enrolment pension. Payroll runs on the 28th of each month. The manager's pay clears the bank on the 28th but the FPS is submitted on the 30th, because the bookkeeper batches FPS submissions at month-end.

Regulation 67B requires on or before payment. The two-day late FPS each month is technically a paragraph 6C failure every month. The three-day risk-based concession protects each individual filing in isolation, but the settled pattern is exactly what HMRC has reserved the right to look through. If HMRC identifies the systematic pattern, the concession can be withdrawn and the penalty exposure becomes £100 × 11 (the first failure remains unpenalised) = £1,100 fixed penalty in a year.

The fix is operational: move the FPS submission to the 28th in the payroll software, ideally as an automated submission triggered by the payroll run. The penalty risk is real but typically dormant under the concession; the right response is to remove the dependence, not to test how patient HMRC's risk-based screening is.

Worked example 3: serviced-accommodation cessation mid-tax-year

Kingsgrove Holiday Lets Ltd runs a serviced-accommodation portfolio with four employed cleaners on salaries between £14,500 and £18,000. The company ceases trading on 31 December (mid-tax-year) and dismisses all four employees with proper P45 issuance. However, the bookkeeper forgets to mark the final FPS as the final submission for the tax year (the ceased-trading indicator in the FPS schema).

HMRC continues to expect monthly FPSs for January, February, and March. Three months pass with no FPS. HMRC issues a Specified Charge under regulation 75A based on prior-month payroll figures, treating Kingsgrove as if it owed PAYE for January to March at the December run-rate. The presumed PAYE liability sits on Kingsgrove's HMRC account until reversed.

Penalty exposure: paragraph 6C late-filing penalty for each of the three missed FPSs (£100 × 3 = £300, less the unpenalised-failure concession = £200); plus the Specified Charge itself, which the company must displace by submitting Nil EPSs (Employer Payment Summaries) for each of the three months or by submitting a final FPS with the cessation marker retrospectively. The cessation route also requires the PAYE scheme to be closed properly via the gov.uk closure process.

Worked example 4: Schedule 56 PAYE late-payment escalator across a tax year

Northcliffe Properties Ltd runs a 28-property portfolio with three PAYE employees. The company pays PAYE late by 5 to 15 days in 8 of 12 months in the 2026/27 tax year because of cash-flow pressure during a refurb cycle. The percentage on the Schedule 56 item 2 escalator rises with the count of late payments in the tax year, not the lateness duration of any single one.

• 1st default in tax year: no penalty (first-default concession)
• Defaults 2 to 4: 1% of unpaid tax each
• Defaults 5 to 7: 2% of unpaid tax each
• Defaults 8 to 10: 3% of unpaid tax each
• Defaults 11 onwards: 4% of unpaid tax each

Northcliffe has 8 late payments in the tax year. The first is unpenalised. Defaults 2 to 4 at 1% × £2,500 PAYE per month × 3 = £75. Defaults 5 to 7 at 2% × £2,500 × 3 = £150. Default 8 at 3% × £2,500 = £75. Total in-year Schedule 56 escalator cost: £300.

None of the late payments reaches the 6-month overdue threshold so no additional 5% accrues, and none reaches 12 months overdue so the second 5% does not accrue either. The escalator is mild at the 8-default level. If Northcliffe's pattern continued and defaults crossed 12 in a single tax year, the in-year cost would cross £1,000, and habitual late-payment behaviour combined with 6-month and 12-month accruals can push the cumulative penalty cost to around 10% of annual PAYE.

The reasonable-excuse defence under paragraph 18 and the Perrin test

Schedule 55 paragraph 18 disapplies a penalty where the taxpayer has a reasonable excuse for the failure and remedies the position within a reasonable time of the excuse ceasing. The Upper Tribunal in Perrin v HMRC [2018] UKUT 156 (TCC) set out the controlling four-stage test:

1. Identify exactly what the taxpayer was supposed to do (here, file the FPS on or before the payment date).
2. Identify the excuse the taxpayer is relying on.
3. Assess whether that excuse is reasonable in the taxpayer's specific circumstances.
4. Assess whether the failure was remedied within a reasonable time of the excuse ceasing.

Excuses that typically fail the Perrin test in RTI cases:

• Ordinary workload pressure and routine staff turnover.
• Forgetfulness or relying on memory rather than a calendared system.
• Bookkeeper or payroll provider failure where the employer did not actively monitor.
• Ignorance of the on-or-before rule.

Excuses that more often succeed:

• Serious illness of the person responsible for filing, supported by medical evidence.
• Bereavement close to the deadline.
• Documented system failure (payroll software outage, HMRC gateway outage, ISP outage) where the employer has filed at the next opportunity.
• Unexpected events outside the employer's control (theft of records, fire, flood).

HMRC v Hok Ltd [2012] UKUT 363 (TCC) sets the jurisdictional limit on appeals: the First-tier Tribunal cannot consider general fairness, only reasonable excuse and the application of the statutory framework. Arguments that HMRC should have sent a reminder, or that the penalty is disproportionate, fail at the threshold.

The boundary with Schedule 24 and Schedule 41

The three penalty regimes that touch RTI compliance sit at different points in the cycle and should not be collapsed into each other:

• Schedule 55 paragraph 6C FA 2009: penalises the failure to file the FPS on time.
• Schedule 24 FA 2007: penalises an inaccuracy within an FPS that has been filed (career, deliberate, or deliberate and concealed behaviour categories).
• Schedule 41 FA 2008: penalises the failure to register for PAYE in the first place (failure to notify chargeability).

All three can apply concurrently. An employer who registers PAYE late, files the first FPS late, and includes incorrect data in that late FPS faces a Schedule 41 penalty (for the registration failure), a Schedule 55 paragraph 6C penalty (for the late FPS), and a Schedule 24 penalty (for the inaccuracy). Each carries its own statutory test and its own appeal route.

Specified Charge under regulation 75A: how it interacts with the penalty

Regulation 75A of the PAYE Regs 2003 gives HMRC the power to issue an estimated PAYE liability where no FPS has been filed at all for a period. The Specified Charge is computed by reference to prior-period PAYE figures and is treated as the employer's actual liability for the period unless and until displaced.

The Specified Charge is not a penalty. It is a presumptive liability that sits on the employer's HMRC account. The Schedule 55 paragraph 6C late-filing penalty continues to apply on top of it. The displacement route is to submit the missing FPS (or a Nil EPS where no payments were made in the period), at which point HMRC adjusts the Specified Charge to match actuals.

For a serviced-accommodation operator with seasonal employment patterns, the most common Specified Charge trigger is failing to submit a Nil EPS during low-let weeks. The fix is mechanical: a Nil EPS for any month with no FPS activity, marked correctly in the payroll software.

Annual PAYE schemes: are they an escape route?

HMRC operates an Annual PAYE scheme for very small employers where payment is made only once per tax year. The scheme constrains the employer to a single annual FPS rather than monthly returns, which removes the monthly paragraph 6C exposure entirely.

The scheme has tight conditions. The employer must pay all employees only once per tax year, in the same tax-month, and must opt in formally. A single-director limited company running a Personal Allowance salary through monthly payroll cannot retroactively claim Annual scheme treatment to avoid late-filing penalties for monthly cycles that have already happened. The choice must be made prospectively with HMRC's agreement.

For a landlord LtdCo with one director and no other employees, switching to an Annual scheme is a real option, but it is a payroll-architecture choice rather than a penalty-mitigation tactic. The cash-flow and pension-contribution patterns of the company need to support a single annual pay-out.

Appeals: HMRC review and the First-tier Tribunal

The appeal route runs first to HMRC and then onwards to the First-tier Tribunal. The mechanics:

1. Initial appeal to HMRC: made in writing within 30 days of the penalty notice. The appeal should set out the reasonable-excuse argument with supporting evidence.
2. HMRC review: if HMRC refuses the appeal, the employer can request an internal review under TMA 1970 sections 49C to 49G. A different HMRC officer takes a fresh look. The request must be made within 30 days of the refusal.
3. First-tier Tribunal notification: under TMA 1970 section 31A read with the Tribunals, Courts and Enforcement Act 2007. The 30-day window runs from the HMRC review conclusion or, where the employer skips the review, from the original refusal.

The FTT does not charge fees for tax appeals. The tribunal can hear the case in person, by video, or on the papers depending on complexity. Representation is permitted (by an accountant, tax adviser, or counsel) but not required.

How this regime interacts with MTD for Income Tax

Real-time information for PAYE and Making Tax Digital for Income Tax are separate digital reporting cycles with no statutory overlap. They run in parallel for a landlord LtdCo employing PAYE staff where the same individual landlord-director also files MTD ITSA personally on rental or self-employed income.

The penalty regimes are distinct. Schedule 55 paragraph 6C continues to apply to RTI. The MTD ITSA late-submission regime sits at a different point of Schedule 55 (the points-based regime as amended for MTD), and the MTD ITSA late-payment regime uses the accelerated Schedule 56 schedule with 3% / 3% / 10% accrual thresholds rather than the slower PAYE-specific escalator. The reasonable-excuse defence at paragraph 18 applies to both regimes, and the Perrin four-stage test governs both.

For a property-business employer planning compliance from 6 April 2026, the practical implication is that two separate calendars need to be maintained: the monthly RTI / FPS calendar for the LtdCo and the quarterly MTD ITSA calendar for the individual director. The two calendars do not relieve each other; missing one does not excuse missing the other.

Practical safeguards for property-business employers

The penalty regime can be managed down to near-zero exposure with a small number of operational safeguards:

• Automate FPS submission to the payment date in the payroll software, removing dependence on the three-day risk-based concession.
• Submit Nil EPSs for any month with no FPS activity, particularly in seasonal serviced-accommodation businesses, to head off Specified Charges under regulation 75A.
• Mark the final FPS of a ceased trading period as the year-end / cessation submission and close the PAYE scheme formally via gov.uk.
• Diary the Schedule 56 escalator threshold: an employer crossing four late payments in a tax year is at the 2% band; an employer crossing seven is at 3%. The escalator is reset at the start of each tax year, but persistent late-payment patterns build through the year.
• Document any reasonable-excuse facts contemporaneously. Medical records, system-outage emails, postal-disruption notices, and gateway-outage screenshots are the evidence the FTT weights heavily under the Perrin test. Reconstructed narratives without supporting documents have a low success rate.
• Treat the one-unpenalised-failure concession as fragile. It exists at HMRC's discretion and can be tightened. Compliance plans that depend on always being allowed one free miss carry tail risk.

The underlying principle for a property-business employer is that the RTI regime is mechanical. The FPS is due on or before the payment date. The fix for every penalty risk in this article is to make the FPS submission a deterministic step in the payroll process, not a discretionary one. The penalty cost of getting that wrong is modest per month but stacks over a tax year and can interact unfavourably with Schedule 56 late-payment escalator if the employer is also paying late.

If your property business runs payroll for a small employed team and you would like a review of where your FPS process actually sits relative to the on-or-before deadline, the regulation 75A Specified Charge exposure, and the Schedule 56 escalator, we work with landlord LtdCos, portfolio operators, and serviced-accommodation businesses on exactly this kind of operational review.