Embedded Files
This section lists common BACS and FPS related errors that may appear in Audit log when you running payroll from XCD.
Message (on Click Log):
Insert failed. First exception on row 0; first error: UNKNOWN_EXCEPTION, common.exception.SqlNoDataFoundException: ORA-01403: no data found
User message description:
An error has occured while creating BACS for the pay run. Please check BACS Service User Number (SUN) on Employer and BACS processing date on Pay run are populated.
Resolution
Resolution
We recommend you check the following then try re-draft employee:
On Employer record, check the BACS service User number is entered correctly
Message (on Click Log):
Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Version Data]: [Version Data]
User message description:
An error has occured while creating BACS for the pay run. Please check BACS Service User Number (SUN) on Employer and BACS processing date on Pay run are populated.
Resolution
Resolution
We recommend you check the following then try re-draft employee:
On Employer record, check the BACS service User number is entered correctly
Message (on Click Log):
Attempt to de-reference a null object
User message description:
An Exception has occurred while calculating BACS for period.April-2022
Resolution
Resolution
We recommend you check the following then try re-draft employee:
On Employer, check Bank details are entered correctly
Message (on Click Log):
Blank
User message description:
Employee Pension contributions YTD are negative in error. Please review for Employee's name
Resolution
Resolution
An negative YTD value will cause FPS failure
We recommend you check the following before you submit the FPS:
On employee's pay summary > Pay summary YTD > check any negative pension value
Message (on Click Log):
Blank
User message description:
Required field Starter declaration is missing or not in accepted format for Employee's name
Resolution
Resolution
This message can be caused by an employee with a P45 with no starter declaration.
This message can be caused by an employee with a P45 with no starter declaration.
We recommend you check the following before you submit FPS:
On employee's record → under Employment tab, Payroll tab and personal tab, check the Starter declaration is selected
Message (on Click Log):
Blank
User message description:
Required field Tax code is missing or not in accepted format (e.g. 1234P) for Employee's name
Resolution
Resolution
An incorrect tax code format will cause incorrect tax calculation and FPS failure.
We recommend you check the following before you submit FPS:
On employee's record → payroll tab, check the Tax code is in the correct format
Message (on Click Log):
Blank
User message description:
Required field Address1/Address2/Postcode is missing or not in accepted format (e.g. Rectory Stable Cottage) for Employee's name
Resolution
Resolution
Employee information such as name and address must included in FPS submission.
We recommend you check the following before you submit FPS:
On employee's record → Contacts tab, check the address 1, address 2, address 3 and post code are filled in with the correct format
Message (on Click Log):
Blank
User message description:
Required field Employer accounts office reference is missing or not in accepted format (e.g.: 123PQ7654321X).
Resolution
Resolution
Employer information such as account office reference and PAYE reference must included in FPS submission.
We recommend you check the following before you submit FPS:
On employer's record → HMRC administration section, check the Accounts office reference field is filled in with the correct format
Message (on Click Log):
IO Exception: Read timed out
User message description:
Exception during batch start execution
Resolution
Resolution
We recommend you check the following before you submit FPS:
On Employer, check HMRC credential are entered correctly
Page updated
Report abuse