My full payment submission has been rejected for this month. This hasn't happened before?

We don't want you to have this kind of experience, Niel. Let's get your FPS submission sorted out together.

First, can you specify which payroll system you're using? Is it QuickBooks Online (QBO) Core Payroll or QBO Advanced Payroll? Have you received any specific error messages or notifications explaining why the payment was rejected? That information will help us pinpoint the issue.

If you're using QBO Payroll Core, here are a few things to check before submitting your FPS:

• Complete your pay run 
• Use only accepted characters in employee names
• Keep addresses within the 35-character limit
• Assign National Insurance (NI) letters correctly by gender

For more details on common FPS submission issues in QuickBooks Online Core Payroll, you can check out this article: Troubleshooting FPS submissions in Core Payroll.

In the meantime, to check if this is a browser issue, try logging in to your QuickBooks Online (QBO) account using a private browser. If QuickBooks isn't behaving as expected, this can help identify any errors or glitches.

Here are the shortcuts for different browsers:

• Google Chrome: Ctrl + Shift + N
• Safari 11 or newer: ⌘ + Shift + N
• Mozilla Firefox: Shift + Ctrl + P
• Microsoft Edge: Ctrl + Shift + N

After that, switch back to your regular browser and clear its cache to refresh the website's preferences. I recommend using the system's supported browser for the best and most secure experience.

After completing these steps, you can try submitting your FPS in QuickBooks Online again.

Furthermore, for comprehensive guidance on QuickBooks Online Core Payroll, please visit this article: QuickBooks Online Core Payroll | Resource Hub.

If you have further concerns about submitting your FPS, please don't hesitate to reach out. The Community team is here to help you along the way. Keep safe!

I'm in the same boat. A weekly payroll that I've processed for the last two of this tax year have gone through without a hitch. Yesterday I process the week 3 and the FPS submission fails with reason "it cannot resolve the name" when you look in the archive for the FPS filing

Tried deleting the payroll and reentering but still the same fault. Quickbooks tech had no joy either and ended up escalating the problem. One thing that was odd is that the submission deadline date would keep changing between the 25 April 2025 which is correct for the weekly payroll and 19 May 2025 as if it was a monthly submission. 

I expect there has been a mid week update to Quickbooks that has cocked things up. Not great and going to the a real ball ache when I have many monthly payroll runs in a few days if they still haven't resolved the issue.

The core payroll has become a joke and not fit for purpose, Quickbooks need to get this sorted and provide a professional product. 

I'm in the same boat. A weekly payroll that I've processed for the last two of this tax year have gone through without a hitch. Yesterday I process the week 3 and the FPS submission fails with reason "it cannot resolve the name" when you look in the archive for the FPS filing

Tried deleting the payroll and reentering but still the same fault. Quickbooks tech had no joy either and ended up escalating the problem. One thing that was odd is that the submission deadline date would keep changing between the 25 April 2025 which is correct for the weekly payroll and 19 May 2025 as if it was a monthly submission. 

I expect there has been a mid week update to Quickbooks that has cocked things up. Not great and going to the a real ball ache when I have many monthly payroll runs in a few days if they still haven't resolved the issue.

The core payroll has become a joke and not fit for purpose, Quickbooks need to get this sorted and provide a professional product. 

I'm in the same boat.     Tried 4 times today and each time it's rejected.   Will try again tomorrow but if it doesn't work I will have to call QB.    I have to say, the payroll element of the software is poor.

@neil59 @Steve Cooper it is supposed to be fixed now so try submitting them again