Sage 50 Payroll HMRC Submission Error: Troubleshooting Steps

A Sage 50 Payroll HMRC submission error can prevent an employer from sending payroll information to HM Revenue and Customs (HMRC) on time. You may encounter a failed Full Payment Submission (FPS), an Employer Payment Summary (EPS) rejection, a Government Gateway connection error, or an authentication message indicating that your credentials could not be validated.

These errors can occur even after payroll has been processed successfully. In some cases, Sage 50 Payroll displays a specific error code, such as 1046, 0003, or 1106. In others, the submission remains on a processing screen, fails to receive a response, or appears to have updated the last FPS date despite an unsuccessful submission message.

The correct solution depends on the error code, the type of submission, and whether HMRC actually received the information. Checking these details before resubmitting is especially important because repeatedly sending a submission without confirming its status can create unnecessary confusion.

What Is a Sage 50 Payroll HMRC Submission Error?

Sage 50 Payroll uses HMRC’s Real Time Information (RTI) system to transmit payroll information electronically. An HMRC submission error occurs when Sage cannot complete the submission process, receives a rejection, or cannot confirm the outcome.

The two main submission types are:

• Full Payment Submission (FPS): Reports employee pay, deductions, tax, National Insurance, and other required payroll information. Employers generally submit an FPS on or before the date employees are paid.
• Employer Payment Summary (EPS): Reports certain employer-level information, including applicable statutory payment recoveries, Employment Allowance claims, and other relevant adjustments. It is also used in circumstances where an employer must report that no employees were paid in a tax period.

Both submissions are part of RTI, but they serve different purposes. An EPS is not a replacement for an FPS, and a failed FPS should not be treated as resolved merely because an EPS was submitted successfully. The error may originate from incorrect credentials, employer references, HMRC service availability, Windows compatibility, outdated payroll software, or incomplete internet-submission components.

Common Sage 50 Payroll HMRC Submission Errors

Use the error code displayed by Sage to narrow down the likely cause.

Error code or symptom	What it generally indicates	First action
Error 1046	HMRC cannot validate the supplied credentials or employer details	Check Government Gateway credentials and employer references
Error 0003	Sage cannot connect to the Government Gateway	Check Windows compatibility, internet access, and submission components
Error 1106	An issue involving browser history or the old reCAPTCHA page	Close the relevant window and clear browser cookies and cache
Submission remains processing	HMRC’s response may be delayed or unavailable	Check submission status before retrying
FPS submission failed	The FPS was rejected or its outcome needs investigation	Open the failed submission details
EPS submission rejected	HMRC did not accept the EPS or a required condition is unmet	Review the precise rejection message
Last FPS date updated after an error	The displayed date alone may not establish successful receipt	Review the submission log and HMRC status

Error messages can differ by Sage 50 Payroll release. Always use the full message and the installed software version when selecting a solution.

Why Is Sage 50 Payroll HMRC Submission Failing?

1. Incorrect Government Gateway Credentials:

Sage may be unable to authenticate the employer if the stored Government Gateway user ID or password is incorrect, outdated, or associated with the wrong service. A credential problem can also occur when the user can sign in to another HMRC service but does not have the required access to the employer’s PAYE for Employers service.

2. Incorrect Employer PAYE or Accounts Office Reference:

HMRC validates employer details as part of the submission process. If the Employer PAYE reference or Accounts Office reference in Sage does not match the relevant HMRC records, the submission may fail. These references serve different purposes. Check each one against the employer’s official HMRC information rather than assuming that correcting the login password will resolve the problem.

3. Government Gateway Connection Problems:

Sage may be unable to establish a connection to HMRC because of temporary service disruption, network restrictions, firewall rules, proxy configuration, or an unsupported Windows environment. A connection error does not automatically mean that the employer’s credentials are wrong. Confirm that the software can reach the relevant online services before changing account details.

4. Outdated Sage 50 Payroll Version:

HMRC submission requirements can change, and Sage releases software updates to maintain compatibility with the relevant tax year and online services. An installation that is not suitable for the tax year being processed may be unable to submit the required information. Check the installed version against the requirements for the applicable tax year before troubleshooting individual credentials or data fields.

5. Browser or reCAPTCHA Problems:

Some submission errors are associated with the browser component used during an HMRC submission. Error 1106, for example, may occur when the browser retains old reCAPTCHA page information. Closing the relevant window and clearing the browser’s cookies and cache may help. The exact procedure depends on the Sage version and submission workflow.

6. Incomplete Internet-Submission Components:

If the files or components used by Sage’s internet-submission process are missing or damaged, the application may fail to communicate with HMRC even when the employer details are correct. This can occur after an interrupted installation, software update, or application repair. More advanced component repair should be undertaken only when the error and installed version support that diagnosis.

7. HMRC Has Not Returned a Timely Response:

Sometimes Sage sends a submission but does not receive a response confirming the outcome promptly. The Government Gateway may be busy or a service may be unavailable. In this situation, the absence of an immediate confirmation does not necessarily prove that HMRC rejected the submission. Check the available submission log and HMRC status before deciding whether to submit again.

How to Fix Sage 50 Payroll HMRC Submission Error?

Follow these steps in order. They begin with the submission status and basic checks before moving to more specific error-code solutions.

Step 1: Identify the Failed Submission and Exact Error Code

Start by checking which submission failed and why.

1. Open Sage 50 Payroll.
2. Select the Summary area.
3. Find the HMRC Real Time Information (RTI) Scheme section.
4. Locate the submission marked as failed.
5. Select Resolve where available.
6. Record the complete error message and code.
7. Note whether the failed submission is an FPS, EPS, or another RTI submission.

Depending on your Sage version, the relevant submission details may also be available through the e-Submissions Log.

Use the result to choose the next action:

• Error 1046: Check credentials, employer references, and PAYE service access.
• Error 0003: Investigate connectivity, Windows compatibility, and internet-submission components.
• Error 1106: Investigate the browser and reCAPTCHA workflow.
• A different rejection code: Follow the explanation for that specific code rather than applying the 1046 or 0003 procedure.
• No clear error, but processing does not finish: Investigate the submission status before retrying.

Do not delete a failed submission record simply because it is no longer needed on the screen. Its details may help establish what happened and whether further action is required.

Step 2: Confirm Whether HMRC Received the Submission

Before resubmitting an FPS or EPS, determine whether the original submission was accepted, rejected, or left with an uncertain status.

1. Open the relevant submission details or e-Submissions Log in Sage 50 Payroll.
2. Check the date and time of the attempt.
3. Review the complete response or error message.
4. Identify whether Sage explicitly reports rejection, failure, or a missing response.
5. Where the result is uncertain, check the relevant HMRC service or obtain confirmation through the appropriate HMRC support channel.
6. Only retry once you have followed the guidance for the recorded status.

This step is particularly important if the submission remained on a processing screen or the last FPS date changed. A submission attempt, a successful transmission, and HMRC’s acceptance of the data are not necessarily the same event. Use the available confirmation and submission records rather than relying on a single date displayed in the software.

Step 3: Verify Your Sage 50 Payroll Version

If the submission failure began after a software update or near the start of a new tax year, confirm that the installed release is suitable for that tax year.

1. In Sage 50 Payroll, select Help.
2. Open About.
3. Find the program version under the program details.
4. Compare the installed version with the requirements for the tax year being processed.
5. If an update is required, obtain it through the authorized Sage download or update process.
6. Follow the installation instructions for the specific release.
7. Reopen Sage and test the submission after confirming that the update completed successfully.

Do not assume that installing any available update will correct every HMRC submission error. A version check is most useful when the problem is related to tax-year compatibility or a documented software issue.

Before updating, ensure your payroll data is backed up and follow the appropriate maintenance procedures for your installation.

Step 4: Fix Sage Payroll Error 1046 — Authentication Failure

Error 1046 indicates that HMRC could not validate the supplied credentials or the details associated with the requested service. It may occur because of incorrect login details, employer reference mismatches, inactive PAYE service access, or temporary HMRC validation problems.

A. Check Government Gateway credentials

1. Sign in to the relevant HMRC online service independently, using your usual authorized account.
2. Confirm that you are using the credentials associated with the employer’s PAYE for Employers service.
3. Open Sage 50 Payroll.
4. Navigate to the e-Submission Settings area. The exact menu location may differ by release.
5. Review the stored user ID and password.
6. If necessary, remove and re-enter the credentials carefully.
7. Save the settings and verify the employer details before retrying.

Do not share your Government Gateway password with anyone or enter it into an unverified website.

B. Check employer references

Compare the Employer PAYE reference and Accounts Office reference stored in Sage with the information supplied by HMRC. If a reference has changed or is incorrect, use the supported process to update it. Contact HMRC or Sage support if you are unsure which reference applies or cannot edit the relevant field safely.

C. Confirm PAYE for Employers access

A successful login to an HMRC account does not necessarily establish that the account has the required access to the employer’s PAYE service. Confirm that the service is active and associated with the correct employer.

D. Retry the failed submission

Once the credentials and employer information have been checked:

1. Return to the failed submission in Sage.
2. Select Resolve where available.
3. Review any late-submission reason requested by the software.
4. If the screen offers a choice between saved credentials and entering credentials again, follow the instructions for the error and verify the details.
5. Re-enter the credentials if required.
6. Submit again and review the resulting confirmation.

If the details are correct but error 1046 persists, HMRC may need to investigate the account or service validation issue.

Step 5: Fix Sage 50 Payroll Error 0003 — Unable to Connect to Government Gateway

Error 0003 is a connection-related problem. It should not automatically be treated as an authentication failure. For Sage 50 Payroll, this error can occur when the computer uses a Windows version affected by HMRC online-service changes. Sage’s published guidance specifically identifies Windows 7, Windows 8, Windows Server 2008, and Windows Server 2012 or 2012 R2 as affected environments following HMRC service changes introduced in May 2024.

A. Check the Windows version

1. Press Windows + R.
2. Enter winver.
3. Press Enter.
4. Review the Windows version displayed.
5. Compare it with the supported operating-system requirements for your installed Sage Payroll release and current HMRC online services.

If the computer uses an affected operating system, moving to a supported Windows environment may be necessary. A router restart or credential change cannot make an unsupported operating system compatible with HMRC’s service requirements.

B. Check the internet connection

If you are using a supported operating system:

1. Confirm that the computer can access the internet.
2. Check whether other online services are working.
3. Review any VPN or proxy connection required by your organization.
4. Confirm that the VPN is active if the payroll environment depends on it.
5. Check whether a firewall or security product is blocking Sage’s online submission components.

Do not leave your firewall or antivirus disabled as a permanent workaround. If a controlled test indicates that security software is blocking the submission, restore protection and configure the appropriate approved exception with your IT administrator.

C. Check the Sage internet-submission components

If the connection and operating system appear correct, check whether Sage’s submission components need updating or repair. Use the e-Submission Version Check or the relevant maintenance option available in your release. If Sage requests updated files, follow the instructions for that version.

Do not delete submission files simply because error 0003 appears. File removal and application reinstallation are more advanced steps and should be used only when the applicable Sage instructions identify a component problem.

Step 6: Fix Sage Payroll Error 1106 When Submitting an FPS

Error 1106 is associated with browser history from an older reCAPTCHA page in Sage’s documented troubleshooting guidance. To investigate:

1. Close the browser or reCAPTCHA window involved in the submission.
2. Open the browser’s settings.
3. Clear the relevant cookies and cached browsing data.
4. Close and reopen the browser if required.
5. Return to Sage 50 Payroll.
6. Retry the FPS submission using the supported workflow.

If a reCAPTCHA page appears, follow the current instructions presented by the software. Sage’s guidance for this error advises skipping the reCAPTCHA window if it appears in the affected workflow.

If error 1106 continues, record the exact message and check whether your installed version requires an update or a different submission procedure. Do not repeatedly submit the same FPS without checking its status. If the previous attempt might have reached HMRC, verify the result before trying again.

Step 7: Fix Sage 50 Payroll FPS Submission Failed After Payroll Processing

A failed FPS can occur after the payroll calculations are complete. The failure does not necessarily mean that you must process payroll again.

1. Confirm that the pay period was processed correctly.
2. Open the failed FPS details.
3. Record the error code and message.
4. Verify the employer references and credentials if the error concerns authentication.
5. Check the installed Sage version if the error concerns compatibility.
6. Correct the identified issue.
7. Retry the submission using the supported process once the status of the original attempt is clear.

An FPS generally reports the employee pay and deduction information associated with the payment. Do not change employee pay, tax, National Insurance, or year-to-date figures merely to make an electronic submission succeed. If the data itself is wrong, follow HMRC’s correction rules for the relevant tax year. If the data is correct but the transmission failed, address the transmission problem instead.

Step 8: Fix Sage 50 Payroll EPS Submission Rejected by HMRC

An EPS reports specific employer-level information and is subject to its own validation rules. An EPS rejection may be caused by incorrect employer information, a submission type that is not available for the employer, or an issue with the data being reported.

1. Open the failed EPS details.
2. Record the complete rejection message and error code.
3. Confirm the relevant tax period and submission type.
4. Review the employer references and online submission settings.
5. Check whether the EPS information matches the employer’s records and the purpose of the submission.
6. Correct any confirmed issue using the appropriate Sage procedure.
7. Retry the EPS only after confirming the status of the earlier attempt and following the guidance for that error.

If the rejection concerns a particular HMRC rule, do not assume that changing the Government Gateway password will resolve it. Follow the rejection’s specific explanation. An EPS is not a substitute for a required FPS. If both submission types are involved, investigate each one separately.

Step 9: Resolve Sage Payroll HMRC Submission Stuck on Processing

A submission that remains on processing may indicate a delay in receiving a response from HMRC. It may also reflect a local software or connectivity problem. Use this sequence:

1. Note the time when the submission started.
2. Avoid repeatedly clicking Submit while the first attempt is still active.
3. Check the current availability of HMRC online services through the appropriate official status information.
4. Review the submission log after the current operation has finished or after following Sage’s guidance for a stalled submission.
5. Determine whether Sage recorded a successful response, an explicit rejection, or no definitive result.
6. If the result remains uncertain, seek confirmation before sending another submission.

When HMRC is busy or a response is delayed, repeatedly initiating submissions may not solve the underlying issue. If the application becomes unresponsive, follow the recovery guidance for your Sage version rather than ending processes or deleting submission files indiscriminately.

Step 10: Investigate an HMRC Submission Error After a Software Update

If the submission error began immediately after a Sage update, check both compatibility and installation integrity.

1. Record the previous and current Sage Payroll versions if available.
2. Confirm that the installed release is appropriate for the current tax year.
3. Check whether the update completed without errors.
4. Run the available e-Submission Version Check if your release provides it.
5. Review whether the error identifies a missing component, connection failure, or credential issue.
6. Apply the documented update or repair procedure for the exact error.

If the error began after a Windows update instead, compare the default browser, internet access, proxy configuration, and operating-system compatibility. Do not roll back software or remove Windows updates without a verified reason. Such changes can affect security and other applications.

Step 11: Resolve an FPS Failure When the Last FPS Date Has Updated

A common concern is that Sage reports an FPS failure even though the last FPS date appears to have changed. The date alone is not sufficient evidence that HMRC accepted the submission. It may reflect a local processing event or another stage of the submission workflow, depending on the software version and circumstances. To investigate:

1. Open the e-Submissions Log or the relevant submission history.
2. Locate the FPS attempt and record its date and time.
3. Review the full message returned by Sage.
4. Check for a confirmation of successful submission or an explicit rejection.
5. If the log is inconclusive, verify the submission status through the appropriate HMRC service or support channel.
6. Follow the documented recovery procedure for the actual status.

If HMRC confirms that the FPS was received, do not send a duplicate simply because the local message is confusing. If HMRC confirms that it was not received, follow the supported resubmission procedure. If the submission status cannot be established, resolve that uncertainty before making further changes to payroll records or sending another submission.

How to Check Failed HMRC Submissions in Sage 50 Payroll

The submission history is important when investigating an FPS or EPS failure, especially if the original attempt may have reached HMRC.

1. Review the RTI Summary

1. Open Sage 50 Payroll.
2. Select Summary.
3. Find the HMRC RTI Scheme section.
4. Identify any submission marked as failed.
5. Select Resolve where available.
6. Record the error code and full message.

This is often the quickest way to identify the reason Sage has flagged a submission.

2. Review the e-Submissions Log

Sage 50 Payroll provides an e-Submissions Log for reviewing and printing submission information. Use it to compare the attempted submission with any recorded response. Look for the date and time, submission type, and available confirmation or rejection details.

If the summary and log appear inconsistent, preserve the information and seek clarification before retrying. Do not rely on the last FPS date alone to determine whether HMRC received the data.

3. Keep a Record of the Outcome

For each failed attempt, document:

• The submission type: FPS or EPS
• The payroll period or relevant tax period
• The date and time of the attempt
• The exact error code
• The response recorded by Sage
• Any correction or maintenance performed
• The result of the next attempt

These details make it easier to distinguish a credential problem from a connection failure, a rejected submission, or a delayed HMRC response.

Prevention: Reduce Future Sage Payroll HMRC Submission Errors

Use these practices to reduce interruptions during payroll processing and RTI reporting.

1. Keep Sage 50 Payroll up to date. Install the appropriate release for the tax year and follow the supported update sequence.
2. Verify employer references. Keep the Employer PAYE reference and Accounts Office reference accurate.
3. Maintain secure credential records. Ensure authorized users know which Government Gateway account is associated with the employer’s PAYE service.
4. Check submission results. Review confirmations and the e-Submissions Log rather than assuming that a completed processing screen means success.
5. Monitor HMRC service availability. Check for reported delays when submissions remain pending.
6. Maintain supported Windows environments. Confirm that the operating system is compatible with the installed payroll release and HMRC’s current online services.
7. Protect internet-submission components. Avoid manually deleting application files or using unverified replacement components.
8. Back up payroll data. Verify backups before installing updates or performing repairs.
9. Keep an audit trail. Record error codes, submission dates, and the outcome of corrective actions.
10. Avoid unnecessary duplicate submissions. Establish the status of the original attempt before resubmitting.

These practices help preserve accurate payroll records and make it easier to address problems before they affect reporting deadlines.

Conclusion

A Sage 50 Payroll HMRC submission error can result from incorrect Government Gateway credentials, mismatched employer references, a connection problem, outdated software, browser-related issues, or damaged internet-submission components. The most effective solution begins with identifying the exact error code and checking whether HMRC received the original submission.

For error 1046, verify credentials, employer information, and PAYE service access. For error 0003, check Windows compatibility, internet connectivity, and the relevant submission components. For error 1106, investigate the browser and reCAPTCHA workflow. If an FPS or EPS remains pending or appears to have failed after the last submission date changed, confirm its status before retrying.

Make changes in a controlled sequence, protect payroll data, and retain the submission history. If the error continues after the relevant checks, provide Sage support with the complete message, installed version, submission type, and troubleshooting results.

FAQs of Sage 50 Payroll HMRC Submission Error: