Skip to main content
L
lisa78
October 16, 2019
Solved

Has anyone else had an issue whereby the payrun is correct but an employee is repeating on the payroll audit report?

  • October 16, 2019
  • 2 replies
  • 0 views
Original commenter did not share additional details
Best answer by GeorgiaC

Hi GeorgiaC

 

I cleared the cache and tried opening in MS Edge and Google Chrome, but still the same, I'm afraid.  I haven't actually finalised the payrun yet, so even if I didn't have PensionSync, it makes no difference. Do you think the payrun will be ok to finalise and that the info that goes to the tax office will be good?

 

Thanks

Lisa


Thanks for testing that Lisa. Would it be possible to delete the pay-run, clear the cache on the browser, and then re-create?

 

Alternately if this employee has not been ran on a pay-run previously you can delete and re-create the employee to fix.  


Regarding finalising the pay run, I  have contacted the engineer looking into the investigation and it does not appear that the employees information is duplicated on the FPS submission. If the above does not resolve the error please reply below so I can raise your case to the engineer.


Thanks :) 

 

 

 

2 replies

G
GeorgiaC
October 16, 2019

Hi lisa78,

 

 

We currently have a raised report of this issue whereby one employee is repeating on both the Pay Slips report and on the Pay Run Audit report.

 

Can I confirm if you are using the Advanced Payroll software and if you have PensionSync enabled?

 

 

Thanks

 

 

L
lisa78Author
October 16, 2019

Hi GeorgiaC

 

Thanks for responding.

 

Yes, we do have the PensionSync enabled and Quickbooks OnLine payroll. I hadn’t checked the pay slip report until just, but you’re right, the employee is also repeating on there.

 

I saw a similar query when I checked the help section with part of the reply to the user from QB asking what options they were using when running the report, but I can’t find that query now in the audit trail! I thought I was going mad!

When I was chatting with the help desk yesterday, they suggested I delete the employee and reinstate him, which I said was a bit extreme. I am now waiting for them to get back to me, but I will have to run the payroll tomorrow latest.

 

Kind regards

Lisa

G
GeorgiaC
October 16, 2019

Hi lisa78,

 

 

Thanks for checking the payslip report to verify this is also affected.

 

To confirm the issue is not caused by a temporary cache error please try clearing the cache on the browser you are using or signing into QuickBooks via a different browser on the device.

 

While this is being investigated the workaround is to rollback and re-run the pay run as this has rectified the issue for some customers, however as you are using PensionSync it will not be possible to do this. Let me know how the above goes!

 

 

Thanks :) 

L
lisa78Author
October 16, 2019

Hi GeorgiaC

 

I cleared the cache and tried opening in MS Edge and Google Chrome, but still the same, I'm afraid.  I haven't actually finalised the payrun yet, so even if I didn't have PensionSync, it makes no difference. Do you think the payrun will be ok to finalise and that the info that goes to the tax office will be good?

 

Thanks

Lisa

Terms & ConditionsAccessibility statement