Page tree
Skip to end of metadata
Go to start of metadata


The purpose of this Wiki is to understand the scenario on how to execute the Earlier Year Update report.


To know more about this behavior, we must first review the necessary information, and then know how to reproduce it. After reading this article you will be able to identify the whole concept.

1. Obtaining the necessary information:

For replicating the above scenario, ensure that GBRTI payroll function in the feature GBCHG should have RTI solution active for the payroll area under which employee was hired.

Now the employee is hired from 01.04.2014 in the payroll area G1. Payroll for this employee is run until March 2014,
and FPS is submitted in live until March 2014.

There is a discrepancy in Year to date (YTD) figures e.g. Taxable pay, tax paid, eenic and ernic, in RTI/RTINI tables for March 2014, as well as FPS for March 2014.

2. Running the EYU report

a) SAP note 1969094 - PY-GB: Earlier Year Update Report Changes 2013/2014 contains the Example spreadsheet for uploading adjustments as required.
b) Data to be entered in the excel file as per the specifications and format as detailed for the required adjustments
to be done, and save the excel file as .xls on desktop folder.
c) Now execute the EYU report thru transaction SA38/SE38, rpceyug0.
Enter the tax reference , as applicable for the employees for whom EYU is run, select the Tax year ending 5th April 2014,
Select the file path for the EYU excel file as saved on the desktop folder, select the radio button XML with ALV,
tick on test in live , and select “New Submission”, and execute the report.

d) The output generated will be as follows:-

 e) The data so generated can be checked through ALV and/or XML display, before submitting the data to HMRC using the B2A Manager Button. Once the data is verified, click on B2A manager, select the relevant record, and click on execute.

f) Once the test in live submission of EYU report is successful as above, remove the tick on test in live, now submit it as a live submission, and execute the report again, and submit the XML file so generated by clicking on execute button in B2A manager.
g) Executing the report in live will also correct/stamp the RTI/RTINI tables with the adjusted EYU values. As an audit trail of the data submitted to HMRC using EYU, the report creates an adjustment line in RTI/RTINI tables.
RTI Table


g) The XML ID for the live EYU submission done along with the EYU-ADJ flag as ‘X’ will be updated in the RTI/RTINI cluster records so created.
h) Further on, the values shown in RTI/RTINI tables will be the amounts with the revised adjusted YTD values which are then used by the P60 report RPCP60G0 for display on the P60 form.
g) Since the execution of the EYU report in live will update the RTI/RTINI tables, the report should be run in test in live first to check on the correctness of the values so adjusted, along with any connection issues while submitting data to HMRC. This needs to be checked/corrected, and once the test in live submission is successful, a live submission is then carried out.

  • No labels