Ensuring Compliance with UK Payroll Reporting Regulations for Property-Business Employers

"On or before making a relevant payment to an employee, a Real Time Information employer must deliver to HMRC the information specified in Schedule A1." That is the verbatim text of SI 2003/2682 reg 67B, and it is the single most operationally consequential sentence in the entire PAYE Regulations 2003. The Full Payment Submission must reach HMRC on or before the moment the employee is paid. Not the next morning. Not "before midnight on payday". On or before the time of the payment itself. The discipline is straightforward in principle and unforgiving in practice, and the penalty regime under FA 2009 Schedules 55 and 56 is the mechanism that keeps it enforced.

This page is the operational compliance deep. The companion overview UK payroll taxes and deductions guide for property-business employers covers what payroll is, the 2026/27 rate stack, the Employment Allowance and Apprenticeship Levy positions and the first-hire framework. Read that first if you are new to property-business payroll. Come back here for the reporting calendar: FPS, EPS, payment cycles, penalty stack, correction windows and the year-end reconciliation routine.

The FPS on-or-before-payday rule

SI 2003/2682 reg 67B is the heart of the RTI regime. The rule applies to every employer running PAYE: a director-only landlord LtdCo, a 3-employee BTL portfolio operator, a 50-employee serviced-accommodation business, a 250-employee multi-region property group. Each payroll run, on or before the time the payment is made to each employee, the Full Payment Submission must reach HMRC.

The detail that catches employers is "the time of payment". The time of payment is when the funds are made available to the employee, not when the employer initiates the transfer:

• BACS transfers: the value date on the BACS file. The FPS must reach HMRC before the value date, not the BACS submission date. A BACS file submitted on Wednesday for a Friday value date must have the FPS in by Friday morning, not Friday evening.
• Faster Payments: when the credit posts to the employee's account. Faster Payments typically clear within seconds; the FPS must precede or coincide.
• Cheque payments: the date the cheque is handed over or posted. The FPS must precede or coincide with the cheque hand-over.
• Cash payments: the date of physical handover.

Modern cloud payroll software (Xero Payroll, BrightPay, Sage 50 Payroll, QuickBooks Online Payroll, FreeAgent Payroll, KashFlow Payroll) automates the FPS submission to coincide with the BACS file generation. The integration removes the manual-step risk but does not remove the timing-discipline risk: the employer still needs to start the payroll run early enough to hit the value-date deadline. The standard discipline for a landlord LtdCo paying on the 28th of each month is to run payroll on the 25th or 26th, leaving 2 to 3 working days of slack against the value date.

The EPS: Employer Payment Summary

The Employer Payment Summary is the supplementary monthly return. It is filed alongside (or sometimes instead of) the FPS, and it has three distinct uses:

• Claim the Employment Allowance offset. Each month, the EA reduces the employer Class 1 secondary NIC liability. The reduction is claimed via the EPS and HMRC offsets the relevant amount against the monthly PAYE payment due.
• Report a nil-payment month. Where no employees are paid in a tax month (a dormant period, a holiday shutdown, a director-only LtdCo with no salary paid that month), the EPS records the nil-payment flag. Without it, HMRC's systems would treat the missing FPS as a late filing.
• Recover statutory payments. SSP, SMP, SPP, SAP, ShPP and Neonatal Care Pay (where applicable) are recovered from HMRC via the EPS, either through the Small Employers' Relief route (full plus 3 per cent if the employer paid less than £45,000 in Class 1 NIC in the qualifying year) or the standard 92 per cent recovery route.

The EPS deadline is the 19th of the month following the tax month. The tax month 6 May to 5 June has its EPS due by 19 June. The same deadline applies to the monthly PAYE payment to HMRC by cheque (the 22nd of the same month applies for electronic payment). For an active landlord LtdCo running monthly payroll with EA in play, the EPS is a monthly fixture; for a dormant or low-payroll-month LtdCo, the EPS is the nil-payment flag.

The payment cycle: 22nd electronic, 19th cheque

SI 2003/2682 reg 67G sets the payment cycle. The combined monthly PAYE liability (employee income tax, employee Class 1 NIC, employer Class 1 NIC, Apprenticeship Levy where engaged) is due:

• By the 22nd of the month following the tax month, where paid electronically (Faster Payments, BACS or CHAPS). This is the default for most modern employers.
• By the 19th of the month following the tax month, where paid by cheque (now uncommon). The 3-day differential reflects cheque clearing time.

Where the relevant date falls on a weekend or bank holiday, the deadline is the last working day before. The tax month 6 May to 5 June has its electronic payment due by 22 June; if 22 June falls on a Saturday, the payment is due by Friday 21 June. The 22 June 2026 fact (Sunday in 2026) means the practical deadline is Friday 19 June 2026 for the May tax month payment.

The PAYE payment is made by reference to the employer's Accounts Office reference. The reference is structured as 3 numerals (the HMRC office code), then "P" (for PAYE), then 8 digits (the unique reference). Each monthly payment quotes the reference and the relevant tax-month/year string to ensure correct allocation. Misallocation is a recurring administrative issue and tends to surface when an HMRC payment-not-received query arrives 6 to 8 weeks after the missing month.

The late-FPS penalty stack (FA 2009 Sch 55)

FA 2009 Schedule 55 imposes penalties for failure to make returns on time. The schedule was extended to cover RTI returns by SI 2013/521 (the PAYE Amendment No. 2 Regulations) and subsequent commencement orders. The structure:

• £100 monthly penalty for employers with 1 to 9 employees.
• £200 monthly penalty for 10 to 49 employees.
• £300 monthly penalty for 50 to 249 employees.
• £400 monthly penalty for 250+ employees.

The penalty is per late FPS, charged monthly. A landlord LtdCo with 8 employees that misses three FPSs in a tax year (one in May, one in October, one in January) faces £100 plus £100 plus £100 equals £300, less HMRC's "one free late filing" concession that waives the first late FPS of each tax year. Net penalty: £200.

Daily penalties (£10 per day) engage after 3 months of continuing failure on the same FPS. The daily penalty is rare in practice for cash-paying employers; it tends to surface where a dormant LtdCo has stopped filing entirely and the FPS gap goes uncorrected for a quarter or longer.

The concession ("one free late filing per tax year") was introduced in 2015 and remains operational at the date of writing. It resets at the start of each tax year on 6 April. The concession is not a statutory right but an HMRC administrative discretion; HMRC retains the ability to withdraw the concession in individual cases of repeated non-compliance.

The late-payment penalty stack (FA 2009 Sch 56)

Late-payment penalties under FA 2009 Schedule 56 are distinct from the late-filing penalty stack. A late FPS is a Schedule 55 issue; a late payment of the underlying PAYE liability is a Schedule 56 issue. An employer can have both, neither or one without the other.

The Schedule 56 structure for PAYE:

• 1 default in tax year: no penalty (a "first slip" is unpenalised, mirroring the Sch 55 concession on filings).
• 2 to 3 defaults: 1 per cent of the unpaid liability.
• 4 to 6 defaults: 2 per cent of the unpaid liability.
• 7 to 9 defaults: 3 per cent of the unpaid liability.
• 10 to 11 defaults: 4 per cent of the unpaid liability.
• 12 defaults (effectively every month): 5 per cent.

For a 1-day late payment of a £4,000 monthly liability on the second default, the penalty is £40. For a 1-day late payment on the seventh default, £120. The percentage bands escalate quickly with repeat non-compliance.

HMRC also charges interest on late payments under FA 2009 s.101 from the day after the due date to the date of payment. The interest rate is set by reference to the Bank of England base rate plus 2.5 per cent (the 2026 rate is around 7.5 per cent annualised). For a 30-day late payment of £4,000, interest is around £25. Interest is not penalty-side; it cannot be appealed on reasonable-excuse grounds.

The reg 67E correction window and the 20 April cliff

SI 2003/2682 reg 67E governs corrections. The verbatim text:

"Where an employer becomes aware of an inaccuracy in a return submitted under regulation 67B or 67D, the employer must provide the correct information in the next return for the tax year in question. But if the information has not been corrected before 20th April following the end of the tax year in question, the employer must make a return under this paragraph."

The mechanic in plain English: a mistake in an earlier FPS is corrected by including the correct information in the next FPS for the tax year. The correction route works while you are still inside the tax year, and continues to work up to the 20 April cliff after the tax year ends. After 20 April, the in-year correction route closes and a separate amendment return must be filed.

The 20 April cliff is the single most important date in the RTI correction calendar. A landlord LtdCo that discovers in February 2027 that the November 2025 FPS over-stated an employee's pay by £500 has multiple routes:

• Correct in the next FPS (the February 2027 FPS includes the correction).
• If discovered after 20 April 2026 (the cliff for the 2025/26 tax year), file a separate amendment return per the reg 67E paragraph.

The amendment return is more administratively onerous than the in-year correction. It also tends to attract HMRC compliance attention more readily, particularly where the correction reduces the year-end position in the employer's favour (HMRC's adverse-amendment review process is more aggressive on this side of the line). The discipline is to surface errors and correct them in-year wherever practicable, rather than allowing them to drift past the cliff.

The 'reasonable excuse' defence under Sch 55 para 23

FA 2009 Sch 55 paragraph 23 provides a reasonable-excuse defence where the failure was not due to the taxpayer's fault. The defence is a partial shield: if accepted, the late-filing penalty is removed.

The leading authority is Christine Perrin v HMRC [2018] UKUT 156 (TCC). The Upper Tribunal set out a four-stage test:

1. Identify the cause of the failure as a matter of fact.
2. Determine whether that cause amounts to a reasonable excuse, judged objectively against the standard of a reasonable taxpayer.
3. Determine when the reasonable excuse ceased to operate.
4. Determine whether the failure was remedied without unreasonable delay thereafter.

HMRC typically accepts as reasonable excuse:

• Genuine system failure (cloud payroll software outage on payroll day with documentary evidence).
• Sudden illness or hospitalisation of the payroll-runner (with documentary evidence).
• Unforeseen and unavoidable events (a fire, a flood, a power outage spanning multiple working days).
• HMRC's own system being down at the moment of attempted submission (documented via HMRC's incident reporting).

HMRC typically rejects:

• "I forgot" or "I was too busy".
• "My payroll software was too expensive to renew on time".
• "My agent was unreliable" (the agent's failure is the employer's failure unless the agent's failure was itself unforeseeable, per Perrin).
• Cash-flow difficulty as a cause for late payment (the HMRC standard is that a tax obligation is an obligation; cash-flow management is the employer's responsibility).

The defence is most likely to succeed where the employer's compliance history is otherwise clean. Barrett v HMRC [2015] UKFTT 0329 (TC) is a useful First-tier Tribunal authority on the RTI-specific application. The Tribunal accepted reasonable excuse where the employer had a clean prior compliance record, the failure was demonstrably one-off, and remediation was prompt.

The year-end reconciliation routine

The tax-year-end runbook for an in-house payroll function:

1. Mark the final submission for the year. The final FPS or EPS of the tax year must be marked as "Final submission for year". This is a single checkbox in cloud payroll software but is the gating step for HMRC's year-end processing. Best practice is to make the mark by 19 April; the legacy 5 April end-of-day window is no longer the operational cliff.
2. Issue P60 to each employee by 31 May. The P60 summarises the employee's gross pay, tax deducted and NIC for the tax year. Cloud software generates and distributes the P60 automatically; the deadline is 31 May for employees employed at 5 April.
3. Prepare and submit P11D by 6 July. Where any employee has benefits-in-kind (employer-provided accommodation, company car, private fuel, private healthcare, gym membership, child-care vouchers in legacy cases), a P11D is required for each. The P11D reports the BIK value for the year just ended and is filed online via the HMRC employer portal.
4. Prepare and submit P11D(b) by 6 July. The P11D(b) is the employer-side declaration that aggregates the BIK values across all P11Ds and quantifies the Class 1A NIC liability (15 per cent on the aggregate BIK value for 2026/27, matching the secondary Class 1 rate from FA 2025).
5. Pay Class 1A NIC by 22 July (electronic) or 19 July (cheque). The Class 1A NIC is a separate payment from the standard monthly PAYE liability, paid annually after the P11D(b) is filed.
6. Update payroll software for the new tax year. New rates, new thresholds and new tax codes (received via HMRC P9 or P9X notifications) need to be loaded before the first payroll of the new tax year. The mid-April window is the critical period.

The window between 6 April and the late-May / early-July deadlines is the busiest period for in-house payroll teams. A landlord LtdCo running payroll in-house should diary the year-end runbook 6 months in advance; the year-end is otherwise the surprise that crystallises in late April when the new tax-year-1 FPS is due.

The Anand-LtdCo three-employee monthly cycle

To bring the elements together: Anand-LtdCo. Three employees: the director (Mr Anand, monthly salary at the Personal Allowance £12,570 a year), the in-house bookkeeper (£30,000 a year, paid on the 28th), and a part-time property manager (£18,000 a year, paid on the 28th). The portfolio is 14 BTL properties across the East Midlands.

Monthly cycle for tax month 6 May to 5 June 2026:

• 25 May 2026: Payroll run starts. Bookkeeper runs the BACS file generation with 28 May value date.
• 26 May 2026: Payroll review and approval. Director Anand signs off.
• 27 May 2026: BACS file submitted, value date 28 May.
• 27 May 2026: FPS submitted via Xero Payroll, on or before the 28 May value date per reg 67B. EPS submitted same day claiming Employment Allowance offset for May.
• 28 May 2026: Employees receive net pay in their bank accounts.
• 5 June 2026: Tax month closes.
• 22 June 2026: PAYE payment to HMRC due (electronic). Combined PAYE plus NIC, less EA offset for the month, paid via Faster Payments quoting the Accounts Office reference.

Failure scenarios:

• FPS late by 1 day (submitted 29 May): £100 penalty under Sch 55 (1 to 9 employee band). HMRC concession waives the first late filing of the tax year, so effective penalty £0 if this is the first slip of the 2026/27 year. Second slip in October would attract the full £100.
• FPS late by 31 days continuous (no submission until 28 June): £100 monthly penalty under Sch 55. Concession waives if first slip.
• Quarter-long FPS gap (no submission 28 May, 28 June, 28 July): £100 a month for 3 months equals £300, plus daily penalties (£10 a day) start to accrue from late August. Material exposure.
• Payment 1 day late (23 June electronic): Sch 56 1 per cent penalty on the unpaid liability if this is the second late payment in the tax year, equals approximately £40 on a £4,000 monthly liability. First slip is unpenalised.
• Failure to mark final FPS for year by 19 April: no direct penalty, but HMRC's year-end processing systems may treat the employer as not having completed the year, leading to incorrect P60 issuance and follow-up administrative complications.

EPS Employment Allowance draw-down for Anand-LtdCo:

Anand-LtdCo's monthly employer NIC liability runs approximately £500 a month (15 per cent on the £25,000 above ST for the bookkeeper, plus £13,000 for the manager, plus £7,570 for the director, all annualised and divided by 12). Each monthly EPS claims the EA offset, drawing down from the £10,500 annual allowance. The draw-down exhausts the allowance at around month 8 of the tax year (approximately November or December), after which the employer NIC liability is paid in full each month.

The CIS overlay for landlord LtdCos with refurb pipelines

Landlord LtdCos that engage construction sub-contractors for refurbishment work operate the Construction Industry Scheme alongside their PAYE obligations. The CIS regime is parallel and distinct: FA 2004 Part 3 (ss.57 to 77) and SI 2005/2045 govern the regime; the operational mechanic is the monthly CIS300 return.

Key features:

• The CIS300 is due by the 19th of the month following the tax month, with its own penalty regime: £100 initial, escalating £200 and £300 at later milestones, plus percentage-based penalties at 6 and 12 month points where the return remains outstanding.
• A landlord LtdCo can be both an employer (FPS for in-house employees) and a contractor (CIS300 for refurb subcontractors). The two regimes are administered separately within HMRC: a failure on one does not automatically engage the other.
• Where a CIS subcontractor is later re-categorised by HMRC as an employee (the Ready Mixed Concrete v Minister of Pensions [1968] employment-status test), the employer is exposed to back-PAYE and back-NIC on the substituted-employee earnings, plus penalties.

The interface between PAYE and CIS is operationally important on portfolio operators running both regimes. The CIS verification mechanic (verify each subcontractor with HMRC before the first payment, deduct 20 per cent registered or 30 per cent unregistered on the labour element) is the gating discipline. Our CIS verification guide walks the operational depth.

Auto-enrolment compliance: the parallel pension regime

The auto-enrolment regime under the Pensions Act 2008 and the Occupational and Personal Pension Schemes (Automatic Enrolment) Regulations 2010 (SI 2010/772) sits alongside PAYE. The FPS data feeds The Pensions Regulator's compliance monitoring.

Three operational obligations:

• Auto-enrol each qualifying worker per payday. The qualifying-worker test (aged 22 to State Pension Age, earning above the £10,000 trigger, working in the UK) is run each payday. New qualifying workers are auto-enrolled into the chosen scheme (NEST is the default; Smart, The People's Pension and Aviva are common alternatives).
• Submit the Declaration of Compliance to TPR within 5 months of the duties start date. The declaration is the formal confirmation that the employer has complied with the auto-enrolment duty. Filing the declaration online via the TPR portal closes the duty's compliance loop for the start date.
• Re-declare every 3 years. The cyclic re-enrolment obligation requires the employer to re-enrol any worker who has opted out, every 3 years from the original duties start date. The worker is free to opt out again immediately; the discipline is the re-enrolment act.

Failure to comply triggers TPR's escalating notice and penalty regime: fixed penalty notice (£400 initial), daily penalties (£50 to £500 a day depending on employer size), and ultimately court action where non-compliance continues. The TPR penalty stack is separate from the HMRC penalty stack; an employer can be in the clear with HMRC but exposed to TPR, or vice versa.

Record-keeping

SI 2003/2682 reg 90 requires payroll records to be kept for 3 years from the end of the tax year (the HMRC standard). The required records cover:

• Each payment to each employee, with gross and net amounts.
• Each deduction (income tax, employee NIC, employer NIC, student loan, postgraduate loan, AEOs, DEAs, pension contributions).
• Employee identification: NI numbers, addresses, P45 or starter checklist information.
• Benefits-in-kind valuations and supporting documents.
• Statutory payment claims and recoveries (SSP, SMP, SPP, SAP, ShPP).
• FPS and EPS submissions with timestamps.

The 3-year retention is the floor. VAT-registered employers must retain VAT-related records for 6 years under VATA 1994 Schedule 11 paragraph 6. For portfolio operators with VAT-engaging commercial property, the practical recommendation is 6 years across the board: a single retention regime is simpler than tracking separate ones, and cloud-storage costs make the additional 3 years of payroll records effectively free.

Late retention (records still held beyond the statutory minimum) is rarely a problem; the issue is records destroyed too soon. An HMRC compliance review typically reaches back 4 to 6 years (4 years on innocent error, 6 on carelessness, 20 on deliberate behaviour under TMA 1970 s.36). Where records have been destroyed before the review window closes, HMRC may apply best-judgement assessment to fill the gap.

How the pieces fit together

The reporting calendar for a typical landlord LtdCo:

• Monthly: Run payroll. Submit FPS on or before each payday. Submit EPS by 19th of following month if EA, statutory-payment recovery, or nil-pay flag applies. Pay HMRC by 22nd (electronic) or 19th (cheque) of following month.
• Tax-year cycle (in-year): Correct any inaccuracies via the next FPS. Mark final submission for year by 19 April.
• Post-tax-year-end (April to July): Issue P60 by 31 May. Issue P11D and P11D(b) by 6 July. Pay Class 1A NIC by 22 July. Reset payroll software for new tax year parameters.
• Reg 67E cliff: 20 April following tax-year end is the in-year correction route's hard cliff. After that, separate amendment return required.
• Parallel obligations: Auto-enrolment Declaration of Compliance to TPR (one-off plus every 3 years). CIS300 monthly return where construction subcontractors engaged.

The discipline that keeps landlord LtdCos clean on the calendar is the diary entry. Each monthly deadline diaried 5 working days in advance, with payroll run earlier than nominally required, leaves the slack to absorb the bank holiday, the system outage, the unforeseen absence of the payroll-runner. The cost of building the slack into the routine is small; the cost of the alternative (one missed FPS per year on average over a 10-year compliance period, with the second-onwards each year attracting £100 per month) is the steady-state outcome where the slack is not there. For the upstream framework on what payroll obligations look like across the rate stack and the gross-to-net mechanics, the complete guide to UK payroll taxes sits as the entry-tier companion. For the firm-services view of payroll outsourcing for landlord LtdCos, the payroll services page is the next step.