HMRC Payroll Submissions

The first HMRC payroll submissions problem you hear about is rarely a missed filing.

It is a quiet one: an FPS that left payroll software five minutes after payday, or an EPS that did not reach HMRC because nobody remembered to trigger it in a no-pay month.

By the time the penalty notice lands, you are three pay runs downstream. HMRC issues penalty notices quarterly, so the £100 or £200 you owe often covers a problem you thought you had already fixed.

We walk through FPS and EPS, the on-or-before-payday rule and its five exceptions, the penalty tier table, and the submission discipline that keeps HMRC letters off your desk.

What counts as an HMRC payroll submission in RTI?

Under RTI, HMRC expects two submission types. The Full Payment Submission (FPS) reports what you paid each employee, the tax and National Insurance deducted, and the YTD figures.

The Employer Payment Summary (EPS) reports everything else HMRC needs that is not tied to a specific pay event.

Every pay period triggers an FPS unless you paid nobody. Most pay periods do not need an EPS.

The exceptions are where HMRC has to know something the FPS cannot say: you paid nothing this month, you are claiming Employment Allowance, you reclaimed statutory pay, or you suffered CIS deductions.

Your software sends both over Government Gateway. Once a submission leaves payroll, the only places it exists are your software’s submission log and HMRC’s PAYE record.

See our UK RTI guide for how this ties into PAYE overall.

Rule: treat your submission log as audit evidence. Export it monthly to a location you control.

When exactly must the HMRC FPS reach HMRC?

On or before the date you actually pay employees. The rule is strict. If payday is Friday 24 April, HMRC expects the FPS timestamped no later than 23:59 on 24 April.

If the submission clock slips into 25 April, you are late.

Five exceptions exist, each with its own code in the FPS filing box. First, non-banking days: if payday falls on a weekend or bank holiday and employees are actually paid the next banking day, file with late reporting reason code G.

Second, new employees without a P45 earning under £96 per week: within seven days.

Third, harvest casuals and short-term workers: within seven days. Fourth, where you genuinely cannot calculate the payment on time (for example a commission reconciliation delay): within seven days.

Fifth, delayed foreign-tax input for expatriate payroll: within one month.

Everything else is late. The most common operational failure is not a forgotten FPS, it is a mistimed one.

A payroll manager submits at 17:00 on payday, the software queues it, gateway latency pushes the timestamp to 00:07 the next morning, and HMRC saw late.

Rule: if payday is a Friday, aim to submit by Wednesday. The grace window is for software problems, not your diary.

What does an HMRC EPS actually cover?

The EPS is the second submission HMRC expects, and it handles the five things the FPS cannot.

You file at most one EPS per tax month, and the deadline is the 19th of the following tax month (so an April EPS is due by 19 May).

The five EPS use cases in order of how often we see them in practice:

Statutory pay recovery. If you paid SMP, SPP, ShPP, or SAP, you usually reclaim 92 per cent (103 per cent with Small Employers’ Relief, where total Class 1 NIC for the prior tax year was £45,000 or less).

The EPS reports the recovery; HMRC offsets it against your PAYE bill.

No-payment month. If you paid nobody in a full tax month, you still need to tell HMRC. File a “period of inactivity” EPS, or a “no payment” declaration up to 12 months ahead if the business is dormant.

Without it, HMRC assumes a forgotten FPS and prepares a penalty notice.

Employment Allowance claim. The £5,000 annual reduction in Class 1 secondary NIC is claimed by ticking the Employment Allowance box on the EPS, once per tax year.

Miss it in April and you can backdate four tax years, but only via EPS.

CIS deductions suffered. If you are a limited company in construction and contractors have deducted CIS from payments to you, the EPS is where you report it. HMRC offsets it against your PAYE and NIC bill.

See our CIS guide.

Final submission for the year. Your March EPS carries the indicator declaring the tax year’s figures complete. This unlocks P60 production and triggers year-end reconciliation.

Scenario rule: if any of those five apply, your payroll cycle is not done until the EPS clears. Pin a calendar reminder for the 14th of every month to check EPS status, five days before the statutory deadline.

What are the HMRC late filing penalty tiers?

Penalties scale by headcount at the point of the late submission, not by how late you were or by the amount of PAYE owed. The published tiers for 2025/26 are:

1 to 9 employees: £100 per tax month.
10 to 49 employees: £200 per tax month.
50 to 249 employees: £300 per tax month.
250 employees or more: £400 per tax month.

Three softening rules apply. The first late FPS in a tax year is a warning, not a penalty. HMRC issues penalty notices quarterly (Jan-Mar, Apr-Jun, Jul-Sep, Oct-Dec), so a consolidated notice lands months after the original miss.

New employers get a 30-day grace from the first FPS.

What compounds is monthly repetition. At 50 employees, missing one FPS per month for six months is £1,500 in penalties plus a 5 per cent penalty on unpaid PAYE at day 30.

HMRC’s view is that the infrastructure is automated; “we meant to submit it” carries no weight.

Appeals go via the HMRC PAYE online account within 30 days. Successful grounds are narrow: documented software failure, Government Gateway outage on the filing date, or serious illness of the responsible person.

Forgetfulness and staff departures do not qualify.

Rule: the quarterly penalty notice is a lagging indicator. If HMRC is the one telling you a filing failed, your internal log is not doing its job.

How does HMRC actually receive and match your submissions?

HMRC matches every FPS and EPS to your PAYE scheme reference (three-digit office number plus unique reference, format 123/AB45678). One PAYE reference holds one employer’s RTI data.

Two PAYE schemes means two sets of submissions.

Each FPS carries a submission ID returned by HMRC on successful receipt. Your payroll software stores it.

If you need to prove an FPS landed, that ID is the evidence; without it, HMRC’s default is that the submission was not received.

Two operational quirks. If an FPS contains an error, correct it on the next FPS with an “amended” marker, not by resubmitting; HMRC matches by employee and pay date, so resubmission creates a duplicate record.

If you change payroll software mid-year, the PAYE reference stays the same, so both systems are authorised to file against it unless you disable submissions in the old software.

See our switching payroll software guide.

HMRC’s online PAYE account shows YTD figures by employee, updated from every FPS. Log in after any cutover or suspicious notice and verify the figures match your payroll output.

Payoff: the HMRC online PAYE account is your source of truth, not your payroll software. A monthly five-minute reconciliation catches problems before the penalty notice does.

What submission discipline do UK payroll teams actually use?

Teams that never see a late FPS penalty share three habits. They lock the FPS submission time to a 48-hour buffer before payday. They treat the EPS 19th-of-the-month deadline as a hard calendar event, not a software notification.

And they reconcile the HMRC online account against payroll YTD figures once a month.

A clean monthly cycle: payday on the 25th, payroll closes on the 22nd, FPS submitted and ID logged on the 23rd, any EPS for the prior tax month filed by the 18th. On the first working day of the next month, the payroll manager reconciles YTD by employee against the payroll report.

Fifteen minutes under 50 headcount, thirty minutes at 50 to 250.

Smaller teams sometimes delegate submission to the software’s automatic schedule and assume that covers them. It does not. If the gateway fails, the software license lapses, or a pay run sits in draft, the scheduled submission does not fire.

You find out via the quarterly penalty notice.

Bureau-managed payroll shifts submission responsibility to the bureau, but not the legal liability. The PAYE scheme is still yours. If the bureau misses a filing, you owe the penalty and recover it via service credit or claim.

Read the filing-failure clause before you sign.

Rule: the submission log, HMRC online account, and payroll report should reconcile every month. Divergence is always informative.

How do the HMRC submission deadlines fit with the rest of PAYE?

FPS and EPS are the visible submissions, but the PAYE payment is what HMRC cares about in revenue terms. The PAYE bill for a tax month is due by the 22nd of the following month electronically, or the 19th by post.

Miss it and you enter a separate late-payment penalty regime: 1 per cent for the first month, rising to 4 per cent at month six, plus daily interest.

Submissions and payment track each other. HMRC calculates the monthly PAYE bill from FPS figures, net of EPS recoveries. File an EPS on the 19th claiming £6,000 of SMP recovery and your payment by the 22nd drops by that amount.

File the EPS late and you pay HMRC cash you are entitled to reclaim, waiting for the next cycle to net off.

Year-end adds one hard date. The final FPS or EPS of the tax year, carrying the “final submission” indicator, is due by 19 April. This unlocks P60 production by 31 May.

See our UK payroll year-end guide.

Other outputs sit on their own deadlines. P11Ds are due by 6 July, and the Class 1A NIC payment by 22 July electronically, each with a separate penalty regime.

Scenario rule: build a single UK payroll calendar that stitches FPS, EPS, PAYE payment, P11D, and year-end dates together. Looking at each deadline in isolation is how one missed submission cascades into three.

Which providers handle HMRC submissions cleanly?

Modern cloud payroll system automate the FPS and EPS mechanics reasonably well.

What separates them is how clearly they surface submission status, how easily you can export a submission log, and how they handle amendments.

Xero Payroll shows FPS and EPS status in a clear log, with the HMRC submission ID captured per filing. The amendment workflow is built in but can be slow if the original submission was older than two pay periods.

BrightPay has the most detailed submission log of the UK payroll tools we review, with per-employee timestamps and explicit late reporting reason codes.

The trade-off is a desktop-rooted UI that newer operators take longer to learn.

Sage 50 Payroll and IRIS Payroll Professional file reliably but bury the submission log in menus that newer users miss. If you inherit a Sage or IRIS setup, audit the submission log access first.

Moorepay and other bureaux file on your behalf. Submission log clarity depends on the bureau contract; specify monthly written FPS and EPS confirmation as a deliverable.

Employment Hero, Pento, and Payfit are the cloud-native trio with the cleanest submission dashboards, at-a-glance confirmation, and friendly EPS handling.

Payoff: a payroll tool that hides the submission log is a payroll tool that lets you find out about filing failure from HMRC, not from itself. Demand the log view in demos.

HMRC payroll submissions: your questions answered

A clean HMRC filing year is boring by design. Twelve FPS submissions timestamped before payday, a handful of EPS filings on the 19th, one year-end final declaration in April, one P60 run by 31 May.

If your year looks busier, the problem is submission discipline, not workload. For shortlisting payroll tools with clear submission logs, start with the UK payroll software buying guide.