The Global Payroll Association would like to highlight changes to the annual list of RTI data fields (the data item numbers against which employers submit real-time information to HMRC via the FPS, EPS and EYU).
The updated version 1.1 guide was published on the 4th of February 2019 but does not contain any new or amended fields for software developers or employers to be concerned about. What it does do is insert 2 appendices at the bottom of the list of data items that give employers an indication of what happens when incorrect or inconsistent date is submitted to HMRC. Appendix 1 is about incorrect information in certain data fields and appendix 2 is about best practice and common issues and how to resolve them. For example:
- The implications of an incorrect or no National Insurance Number being declared (appendix 1.1)
- The implications of incorrect or incomplete worker name information being declared (appendix 1.2)
- The implications of incorrect or missing date of birth information (appendix 1.3)
- The implications of incorrect or missing address information (appendix 1.4)
- The implications of incorrect or incomplete starter declaration data (appendix 1.5)
- The importance of the field “payroll ID” on the FPS (appendix 1.6)
- Hints and tips such as ensuring that a leaver FPS is sent before a starter FPS (appendix 2.1). This is not always in the control of the new employer but it is good to know the implications of a starter FPS if it is received before the FPS declaring the leave date from the previous employer
- Common issues which that can affect tax codes (appendix 2.2)
- Common issues and tips on how to get them resolved, either by contacting HMRC or making corrections on another RTI file (appendix 2.3)
This updated data items guide really is a handy one for employers to refer to and makes transparent how HMRC’s systems are handling the data that we send them.
The Global Payroll Association would like to highlight changes to the annual list of RTI data fields (the data item numbers against which employers submit real-time information to HMRC via the FPS, EPS and EYU).
The updated version 1.1 guide was published on the 4th of February 2019 but does not contain any new or amended fields for software developers or employers to be concerned about. What it does do is insert 2 appendices at the bottom of the list of data items that give employers an indication of what happens when incorrect or inconsistent date is submitted to HMRC. Appendix 1 is about incorrect information in certain data fields and appendix 2 is about best practice and common issues and how to resolve them. For example:
- The implications of an incorrect or no National Insurance Number being declared (appendix 1.1)
- The implications of incorrect or incomplete worker name information being declared (appendix 1.2)
- The implications of incorrect or missing date of birth information (appendix 1.3)
- The implications of incorrect or missing address information (appendix 1.4)
- The implications of incorrect or incomplete starter declaration data (appendix 1.5)
- The importance of the field “payroll ID” on the FPS (appendix 1.6)
- Hints and tips such as ensuring that a leaver FPS is sent before a starter FPS (appendix 2.1). This is not always in the control of the new employer but it is good to know the implications of a starter FPS if it is received before the FPS declaring the leave date from the previous employer
- Common issues which that can affect tax codes (appendix 2.2)
- Common issues and tips on how to get them resolved, either by contacting HMRC or making corrections on another RTI file (appendix 2.3)
This updated data items guide really is a handy one for employers to refer to and makes transparent how HMRC’s systems are handling the data that we send them.