cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Everything you need to know about banking in QuickBooks Online - Discover more
CJM5
Level 1

FPS Submissions rejected due to spurious (1) in employee name

My FPS submission for August was rejected and I am unable to file September’s FPS.

 

After looking at the HMRC rejection, the issue is that there is a (1) after the name of one of our employees in the FPS submission, and this does not match HMRC’s formatting rules, so the FPC is rejected:

 

Reason: Validation failed for HMRC RTI payload body: cvc-pattern-valid: Value ‘Mxxxx (1)' is not facet-valid with respect to pattern '[A-Za-z \-']*' for type

 

I did not add this (1) and believe it was entered by QB after one of the recent payroll updates.

 

When I look at the Employees tab, there is no sign of this (1), but if I click the show Display Name option, the display name for this employee has a (1) in it. I tried to edit the employee name, but no (1) is not visible in any of employee name fields that I can edit.

 

Yesterday I spoke to “Abdikariem” on QB phone support who also could not find a way to remove the (1) and said I needed to be transferred to a “higher support team”. After waiting for 15-20 minutes Abdikariem said the team was busy and he would get one of them to call me later that day. Annoyingly, this did not happen.

 

I am now late filing both August and September’s FPC and have advised HMRC this is due to a problem with QB.

 

Please can anyone advise how to remove the (1) from the employee name submitted in the FPC?

 

Does anyone else have the same issue?

5 REPLIES 5
John C
QuickBooks Team

FPS Submissions rejected due to spurious (1) in employee name

Hi CJMS Thanks for reaching out to us here on the Community. We sincerely appreciate your frustrations and the inconvenience that the issue is causing you. If you select Payroll > Employees > Select the employee/s > select Edit in the personal Info section > is there a (1) in any of the fields? We note that the case has been raised to the senior support team, the senior support team have between 24-72 hours to reach out to customers from when the case was allocated to them, which was yesterday. We apologise that you've been misinformed regarding the timeframe. 

CJM5
Level 1

FPS Submissions rejected due to spurious (1) in employee name

Thank you for the reply.

 

There is no (1) in any of the fields.

 

 

John C
QuickBooks Team

FPS Submissions rejected due to spurious (1) in employee name

Hi CJM5 Thanks for checking. What has worked for customers is if you access your employee/ss personal info section, the employees that are listed in the FPS rejection message. Change the names in all name fields to something else > save > change the names back to what they should be > rollback/delete the payrun > re-run the payrun and you should be able to submit the FPS. Please note although the above may work and you're able to submit the FPS the payroll journals that are produced will still have the (1) allocated to the affected employee/s. For this to be removed completely will involve your case being raised to the engineers, the senior support agent will explain this when they contact you. In the mean time please try the above.

CJM5
Level 1

FPS Submissions rejected due to spurious (1) in employee name

John C, Many thanks for the reply.

Please could you clarify whether your suggestion is a temporary fix to get the late FPCs submitted or a full solution that will also allow future FPCs to be submitted without any issue?

 

John C
QuickBooks Team

FPS Submissions rejected due to spurious (1) in employee name

Hi CJMS The steps provided previously will resolve the issue moving forward and you should be able to submit future FPS's. The only issue would that on the payroll journals, that are produced when you run the payroll, the employee will still have the (1) noted against their name however it won't be allocated elsewhere e.g. the payslips, that particular issue can only be resolved by an engineer.

Need to get in touch?

Contact us