Late FPS Submission: What Employers Should Do and Possible Penalties

A late FPS submission is rarely just a payroll administration issue. It usually points to a wider breakdown somewhere in the payroll cycle: missing hours, unresolved starter details, software access problems, bank holiday timing, director approval delays, or uncertainty about whether staff are being paid at all.

For employers operating PAYE, the Full Payment Submission is one of the most important Real Time Information filings sent to HMRC. It tells HMRC who has been paid, how much they have been paid, what tax and National Insurance has been deducted, and what employer liabilities arise from that payroll run. If the FPS is late, HMRC’s records may no longer match the payment event, and that can create penalty exposure, employee tax code issues, Universal Credit disruption, and avoidable PAYE account confusion.

The immediate question is usually simple: what should the employer do now? The better question is slightly wider: why did the FPS miss the deadline, what should be reported to HMRC, and how can the payroll process be adjusted so the same failure does not repeat?

What an FPS does in the PAYE process

A Full Payment Submission is the regular RTI report sent to HMRC each time employees are paid. It includes pay, tax, National Insurance, statutory payments, pension-related payroll data, starter and leaver information where relevant, and other details HMRC uses to update the employer’s PAYE position.

The key rule is that the FPS should normally be submitted on or before the date employees are paid. This is the practical deadline for FPS submission that most employers need to work around. It is not the date payroll is approved internally, the date payslips are prepared, or the date the PAYE liability is paid to HMRC. It is tied to the payment date reported through payroll.

That distinction matters. A payroll may be calculated on Tuesday, approved on Wednesday, paid on Friday, and funded to HMRC later. The FPS submission deadline is normally Friday if that is the contractual or actual pay date. If the FPS is sent after that date, HMRC may treat it as a late FPS submission unless an accepted late reporting reason applies.

Why late FPS submission matters beyond the penalty

Employers often focus on the penalty for late FPS submission, but the operational consequences can be just as disruptive. HMRC uses RTI data to maintain employee tax records and employer PAYE liabilities. Delayed or inaccurate submissions can create mismatches that take time to unwind.

For employees, RTI information can affect tax code updates and, for some workers, Universal Credit calculations. If payroll data arrives late or in an unexpected period, the employee may experience queries or payment fluctuations that the employer then has to help explain.

For employers, repeated HMRC late FPS submission issues can make the PAYE account harder to reconcile. A business may have paid staff correctly and even paid HMRC on time, yet still face RTI filing problems because the FPS timing was wrong. This is why payroll compliance is not just about calculating net pay; it is also about filing discipline, evidence, and process control.

The usual deadline for FPS submission

The normal FPS submission deadline is on or before the employee’s payday. If employees are paid weekly, the FPS is normally due weekly. If they are paid monthly, it is normally due monthly. If a business runs more than one payroll, each payroll run carries its own RTI timing requirement.

FPS submission deadlines can become less straightforward where pay dates shift. Common examples include bank holidays, early Christmas payrolls, weekly payrolls processed in advance, and situations where employees are paid before all variable hours have been finalised.

Where pay is brought forward because of a non-working day, the employer should take care over the payment date used in payroll software. Reporting an artificial processing date rather than the contractual payday can cause unexpected issues, particularly for employees receiving Universal Credit. HMRC has published guidance on reporting regular paydays where payment is made early because of non-banking days, and employers should check the current position rather than relying on habit.

What counts as a late FPS submission?

An FPS is generally late where it is submitted after the payment date reported for the employees in that payroll run. HMRC systems compare the filing date with the payment date, then consider whether a late reporting reason has been provided.

Not every late-looking FPS leads automatically to a penalty. HMRC recognises certain reasons for late FPS submission, and there are also limited easements and practical tolerances. However, employers should not assume that a late filing will be ignored simply because it was only a day late or because staff were paid correctly.

Late submission can arise in several ways:

• the payroll was processed after employees had already been paid;
• the FPS was prepared but not successfully filed through payroll software;
• the person responsible for payroll was absent and no backup process existed;
• starter information, National Insurance numbers, or hours data arrived late;
• the employer misunderstood the payday-based filing rule;
• software credentials, PAYE references, or Government Gateway access failed;
• incorrect payroll calendar settings caused the wrong payday to be reported;
• a correction was processed incorrectly as a new or replacement submission.

The most difficult cases are not always caused by negligence. A small employer may have one director approving wages, one bookkeeper collating hours, and an external payroll provider waiting for final confirmation. If one link is delayed, the FPS can miss the deadline even though no one intended to file late.

Accepted reasons for late FPS submission

Where an FPS is submitted late, payroll software may allow the employer to select a late reporting reason. This reason tells HMRC why the FPS was not filed on time. It should be used carefully and honestly; it is not a general-purpose tool for avoiding penalties.

Common late reporting reasons may include circumstances such as a reasonable excuse, correction to an earlier submission, no payment made to employees, or reporting a payment after an employee had already been paid in certain limited scenarios. The available categories depend on HMRC rules and the payroll software being used.

The practical point is that the reason should match the facts. If the employer simply forgot to submit the FPS, selecting a more favourable reason because it appears available in the software may create a worse compliance position if HMRC later asks questions. Payroll records should show what happened, who identified the issue, when the FPS was filed, and what was done to prevent recurrence.

HMRC penalties for late FPS submission

HMRC may charge late filing penalties for FPS delays, usually based on the size of the PAYE scheme. The monthly penalty can apply where one or more FPS filings in a tax month are late, subject to HMRC’s penalty rules and any applicable exemptions.

The standard late filing penalty bands have historically been:

• 1 to 9 employees: £100;
• 10 to 49 employees: £200;
• 50 to 249 employees: £300;
• 250 or more employees: £400.

There can also be an additional penalty where a filing remains outstanding for three months. HMRC may also charge interest or penalties in relation to late PAYE payments, but that is a separate issue from FPS late filing. A business can file its FPS late even if the PAYE payment is later made correctly; equally, it can file on time but pay HMRC late.

Employers searching for “what is the penalty for late FPS submission” should therefore be careful not to treat the answer as one fixed amount. The penalty depends on the employer size, the number of failures in the relevant period, whether HMRC applies a concession or exemption, and whether the employer has grounds to appeal.

When HMRC may not charge a penalty

HMRC does not necessarily issue a penalty for every isolated late filing. There are circumstances where a first failure in a tax year may not trigger a penalty, and there are specific rules for certain new employers and limited exceptions. These rules can change, and employers should check HMRC’s current guidance when dealing with a live case.

There is also a difference between HMRC accepting a late reporting reason and HMRC agreeing that there is a reasonable excuse. A reasonable excuse normally requires something beyond ordinary pressure of work or a simple oversight. Examples might include serious illness, major system failure, or another event that genuinely prevented filing on time, provided the employer acted promptly once the issue was resolved.

Weak excuses tend to fail. “We were busy”, “the payroll person was on holiday”, “we did not know the rule”, or “the director had not approved the figures” may explain what happened internally, but they do not automatically remove penalty exposure. HMRC usually expects employers to have a resilient payroll process, especially where employees are being paid regularly.

What to do immediately after a late FPS submission

If the FPS deadline has already been missed, the employer should usually act quickly rather than waiting for HMRC to issue a notice. Delay rarely improves the position, and practical PAYE filing support may be useful where the employer is unsure how the late submission affects the PAYE account.

• Submit the FPS as soon as possible using the correct payroll figures and payment date.
• Select the correct late reporting reason where the software requires one.
• Keep a short internal record explaining why the filing was late and when the issue was corrected.
• Check the PAYE account after HMRC has processed the submission, particularly if liabilities look unusual.
• Review affected employees where the late filing could affect tax records or benefit-related income reporting.
• Respond promptly to HMRC notices if a late filing penalty or PAYE query is issued.
• Identify the process failure rather than treating the filing as a one-off inconvenience.

The internal record does not need to be elaborate, but it should be factual. For example: the payroll was due to be filed on 28 June, hours for two weekly-paid employees were received late, the FPS was filed on 29 June, the late reason selected was reviewed, and future cut-off times were agreed with the operations manager. That kind of record is far more useful than a vague note saying “payroll delay”.

Where late filing usually starts: the payroll workflow

Late FPS submission often begins before anyone opens the payroll software. In practice, the filing deadline is missed because the upstream payroll information is late, incomplete, or disputed.

For hourly paid staff, timesheets may not be approved in time. For hospitality, construction, care, logistics, and other shift-based sectors, payroll depends on operational managers providing accurate hours. If that information arrives after payday, the payroll team is left choosing between paying estimates, delaying wages, or filing late.

For salaried staff, the issue may be starters, leavers, bonuses, statutory pay, salary sacrifice, pension changes, or attachment of earnings orders. Directors sometimes assume a monthly payroll is simple because the salary figure is fixed, but a single late starter form or pension adjustment can still hold up the FPS.

The risk increases where responsibility is split. An employer may use one system for time recording, another for payroll, another for pensions, and a separate approval route for bank payments. Each handover creates a point of failure. The FPS is the final compliance output, but it reflects the quality of the whole payroll process, including how routine payroll services are managed and reviewed.

Common misunderstandings about FPS late filing penalties

Several misunderstandings appear repeatedly in PAYE compliance work.

“We paid HMRC on time, so the FPS cannot be late”

PAYE payment and RTI filing are separate obligations. Paying HMRC by the due date does not fix a missed FPS deadline. HMRC still expects the RTI submission to be made on or before the employee’s payday unless a valid exception applies.

“The payroll software showed no error, so HMRC must have received it”

Software can calculate payroll without completing the RTI filing. Employers should check submission receipts, filing logs, and HMRC response messages. A payroll marked as processed internally is not the same as an FPS accepted by HMRC.

“No one was paid, so nothing needed to be filed”

If no employees are paid in a tax month, an Employer Payment Summary may be required to tell HMRC no payment is due. Failing to communicate this can lead HMRC to estimate liabilities or show unexpected amounts on the PAYE account.

“A correction means we can ignore the original deadline”

Corrections have their own treatment. If an earlier FPS was wrong, the employer may need to correct payroll data through the appropriate route. Filing a late FPS and calling it a correction will not necessarily remove the original late filing issue.

Practical examples of late FPS situations

Consider a weekly payroll where staff are paid every Friday. The operations team sends hours late on Friday afternoon, after payments have already been released. Payroll is processed on Monday, with Friday as the payment date. The FPS is likely late because the payment date has passed. The employer should file promptly, use the correct late reason if applicable, and address the timesheet cut-off problem.

A second example is a director-only payroll. The director takes a salary at the end of each month, but the FPS is not filed because the company assumes there is no urgency where the director controls the business. HMRC does not treat director status as a reason to ignore RTI timing. The FPS deadline still matters.

A third example involves a new employer. The company pays its first employee before PAYE registration and payroll software access are fully in place. The employer may have a genuine explanation, but this should be resolved quickly. Late PAYE registration, missing employer references and delayed RTI setup often overlap, and the longer the delay continues, the harder the first PAYE period becomes to reconcile.

Appealing an HMRC late FPS penalty

If HMRC issues a penalty notice, the employer should review it rather than paying automatically or ignoring it. The first question is whether the penalty is factually correct: was the FPS late, does the employee count look right, and does HMRC’s notice relate to the correct PAYE scheme and period?

If the employer believes there was a reasonable excuse, an appeal may be appropriate. The appeal should be specific and evidence-based. HMRC is more likely to engage with a clear timeline than a broad statement of unfairness.

Useful evidence may include:

• payroll submission logs and HMRC response receipts;
• software outage evidence or provider incident reports;
• medical or emergency evidence where relevant;
• emails showing when payroll information was received;
• notes of corrective action taken after the failure;
• proof that the employer acted promptly once able to file.

An appeal is not strengthened by overstating the case. If part of the delay was avoidable, it is usually better to explain the facts plainly and focus on the genuine obstacle, the timing, and the corrective action.

How repeated late submissions affect a business

One late FPS submission can often be corrected with limited disruption. Repeated late submissions are different. They suggest that payroll is not properly embedded into the business’s operating rhythm.

For a growing employer, this can become a governance issue. Directors and senior managers may not see payroll filing as a board-level concern, but PAYE failures can indicate weak financial controls. If payroll data is late every month, other records may also be unreliable: pension submissions, accrued wage costs, management accounts, CIS deductions, VAT cash flow forecasts, or corporation tax planning assumptions.

The connection is not theoretical. Payroll figures feed into bookkeeping, tax provisioning, staff cost analysis, pension contributions, and sometimes grant or finance reporting. A late FPS may be the visible symptom of a wider record-keeping problem.

Preventing late FPS submission

Prevention usually depends less on technical knowledge and more on disciplined cut-offs. The employer needs a payroll timetable that reflects how the business actually operates, not how everyone wishes it operated.

A workable payroll process should define:

• who provides hours, overtime, commission, bonuses and absence data;
• the cut-off date and time for payroll changes;
• who approves payroll and who provides backup approval;
• when payslips are issued;
• when the FPS is submitted and who checks acceptance;
• how payroll corrections are handled after submission;
• what happens if the usual payroll contact is unavailable.

For small employers, the solution may be as simple as moving the internal payroll cut-off two working days earlier and checking submission receipts every pay period. For larger or more complex employers, prevention may require better software configuration, clearer manager responsibilities, integrated time-recording systems, or outsourced payroll management with defined information deadlines.

Software helps, but it does not remove accountability. Xero Payroll, QuickBooks Payroll, Sage Payroll and online payroll software can all support RTI filing, but the employer still needs correct data, correct dates, active PAYE references and someone responsible for checking that HMRC has accepted the submission.

Special care points for employers

Some payroll situations deserve extra attention because they commonly lead to late or incorrect FPS filings.

New employers and PAYE registration

A business taking on its first employee should not leave PAYE registration until the first payday is imminent. HMRC references, software setup and pension duties take time. Paying staff before the scheme is ready often creates avoidable RTI timing problems.

Irregular payments and casual workers

Employers with casual, seasonal or irregular workers need to distinguish between periods with no payment and periods where workers are paid late, paid early or paid after leaving. The RTI treatment can differ, and assumptions can produce errors.

Construction and CIS environments

Construction businesses sometimes manage PAYE employees and CIS subcontractors alongside each other. CIS reporting and PAYE RTI are separate regimes. Confusing the two can lead to missed payroll filings, particularly where office administration is stretched.

Director payrolls

Small companies sometimes treat director payroll informally, especially where salary is used for tax planning. RTI rules still apply. If salary is paid or credited, the payroll reporting position should be reviewed carefully.

Corrections after year end

Errors discovered after the tax year has ended may need a different correction process from in-year changes. Employers should avoid submitting unnecessary or incorrect FPS files without checking the right method for the period involved.

What directors and finance teams should take from this

The strongest payroll processes are not built around panic at the filing deadline. They are built around predictable information flow. The people approving hours, starters, leavers, bonuses and bank payments need to understand that their timing affects HMRC reporting, not just employee pay.

For directors, the practical responsibility is to make sure the business has a payroll process capable of meeting PAYE obligations consistently. That does not mean a director has to run payroll personally, but it does mean the business should not depend on one person, one login, or one last-minute approval chain.

For finance teams, late FPS submission is a useful control signal. If filings are late because the underlying information is unreliable, the problem may sit with operations rather than payroll. If filings are late because software access is unclear, the problem may sit with systems administration. If filings are late because no one checks HMRC acceptance, the problem sits with control design.

Key practical takeaways

• An FPS should normally be submitted on or before the employee’s payday.
• A late FPS submission can trigger HMRC penalties, usually based on the size of the PAYE scheme.
• PAYE payment deadlines and FPS submission deadlines are separate obligations.
• Late reporting reasons should be accurate and supported by the facts.
• Submission receipts and HMRC response messages should be checked, not assumed.
• Repeated late filings usually indicate a wider payroll workflow problem.
• Good cut-offs, backup responsibilities and software controls are the best prevention.

Final perspective

Late FPS submission is easy to underestimate because the filing itself feels administrative. In reality, it sits at the point where payroll calculation, employee payment, HMRC reporting, bookkeeping records and management control meet.

The penalty for late FPS submission is only one part of the risk. The more valuable lesson is often found in the reason the deadline was missed. A single late filing may be a recoverable mistake. A pattern of late filings is usually evidence that payroll has outgrown the process supporting it.

Employers who respond well tend to do three things quickly: file the missing FPS, keep a clear record of what happened, and adjust the workflow before the next payroll cycle. That approach does not remove every risk, but it gives the business a much stronger footing with HMRC and a more reliable payroll process for the people who depend on it.