If the FPS Has Been Submitted to HMRC And The Starter Declaration is Wrong, Is There Any Oracle Process To Correct It Without Rolling Back the Payroll and Post-Payroll Processes?
(Doc ID 2272163.1)
Last updated on MAY 31, 2017
Applies to:Oracle HRMS (UK) - Version 12.1.3 to 12.2.6 [Release 12.1 to 12.2]
Information in this document applies to any platform.
Given the below scenario :
1 - new employee has started this month
2 - no P46/P46 new starter details has been received in time for the payroll run
3 - payroll user has entered 0T or BR on Tax Information, and in New starter Declaration, has selected "C Other Job or Pension"
4 - the following processes have been run : payroll run, prepayments, FPS, Costing, Transfer to GL ; and the EDI file has been sent to HMRC
5 - then users have received the employee new starter information and payroll are able to complete the details.
6 - Users have done the changes: Tax information > New Starter > Tab down > enter new details provided by the employee
8 - Users have run Quickpay and then FPS
9 - FPS has not picked up the new information.
10- because the RTI didn't pick this up and it wasn't reported to the HMRC, the employee got a P6 placing him on D0 (40% tax) saying it was because we had told them that he had another job.
Is there any seeded Oracle process to correct the new starter declaration for an employee, if all the payroll and post-payroll processes have been run and cannot be rolled back?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document