HMRC rejects FPS (Full Payment Submission) file submitted as contains an incorrect Payment Date
(Doc ID 2380828.1)
Last updated on APRIL 29, 2020
Applies to:Oracle Fusion Global Payroll Cloud Service - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, UK - United Kingdom Legislation
FPS (Full Payment Submission) FAILS affecting entire population.
HMRC rejects FPS file submitted as contains an incorrect Payment Date.
Run Full Payment Submission should fetch the payment date and not the payroll run date.
The issue can be reproduced at will with the following steps:
1. Run Full Payment Submission;
2. Submitting the file with HMRC;
3. HMRC rejects FPS file submitted as contains an incorrect Payment Date.
An employee is attempting to claim universal credits (via the HMRC).
The HMRC tell that the FPS file submitted contains an incorrect Payment Date.
The Payment date in the FPS file (seeded in Cloud Payroll) for Feb 2018 equals 24/02/18, this date should equal 27/02/18. The HMRC cannot approve the claim for universal credits until this date value is rectified.
We see that all employees in the FPS file have an incorrect Payment date of 24/02/18.
In order to correct the issue we have attempted to change the Payroll Run Date in the Payroll Time Periods table, and we have rolled back and re-run all the locked in processes (after Calculate Payroll) to re-produce the FPS with the correct Payment Date, however the FPS file remains with an incorrect Payment Date of 24/02/18.
Therefore we are non-compliant with HMRC regulations and the employee cannot claim universal credits.
The issue has the following business impact:
Due to this issue, being non-compliant with HMRC regulations and the employee cannot claim universal credits.
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