HMRC RTI: SAP's Proposed Solution

SAP have outlined their potential solution to accommodate the new HMRC Real Time Processing. The solution is still in development so some details may well change. The proposed process will be as follows:

New programs
• RPCFPSG0
• RPCEPSG0
• RPCEASG0
• RPCRTI_DISP
• Amendments to RPCP45GN and RPCDTAG0

Features
• GBIEI
• Amendment to GBCHG - Node 11

Payroll function
• GBRTI in Schema GEND

Personnel calculation rules
• GRTI
• G048

Processing class 48
• Specification 1 - cumulates into /177
• Specification 2 ¡V cumulates into /176

New technical wagetypes

New/amended model company wagtypes
• A080 Expenses
• A081 Expenses Niable only
• A082 Taxable Benefit
• A083 Tax/Ni Benefit
• A084 Niable Benefit

Changes to SAP Payroll

A new feature will be delivered which will allow you to activate RTI processing for different payroll areas and feature GBIEI will allow you to define groups of employees who work irregularly.

Function GBRTI will be called at the end of schema GEND prior to function EXPRT. This function will create all the information required for RTI and perform complex checks of the data. The calculated values will be updated into new tables RTI and RTINI for the In Period only. They will not be changed in retro calculations.

Cumulation classes in the range /7** have been created and relevant customer wagetypes will need to be mapped to these to identify expense related payments.

N.B. If customers have used the /7* range for their own processing this will need to be changed.

Wagetype NHWK will be made available to capture weekly hours paid. By default RTI processing will take the weekly working hours from Infotype 0007. If, for some reason this is not appropriate, the new wagetype can be entered on Infotype 0014 to store the weekly hours value for the employee. The wagetype could also be created during the payroll processing if the value fluctuates.

N.B.Payroll processing will be updated so that employees without an Infotype 0009 record will be rejected.

The Pre-DME process will generate the random RTI indicator (/###). This value will be entered in to the new table RTI. The RTI indicator is used to create the hash code.

Infotype 0065 will be updated to include a new tab ‘Tax Details’ driven be go-live date in feature GBCHG. Tax code source has 6 options:

• Starter - Employee
• Starter - Expat
• Starter - Pensioner
• HMRC - P6
• HMRC - P9
• HMRC - Uplift

Infotype 0088 will be extended to include:

• Additional Statutory Paternity Pay
• Subtypes STPA and STPB
• Partner Details
• Last name, first name, middle name, initials and NI number

The RTI program (RPCFPSG0) will be very simplistic and will perform some basic checks to make sure that there are not umlauts or accents in the name fields that could cause the file to be rejected. The random RTI indicator will be picked up from the RTI table. This report can be run by PAYE Reference or payroll area and chunking up the running is possible to make sure files remain within size restriction imposed by the Government Gateway.

It is assumed that all companies will run the RTI program in ‘Test in Live’ mode prior to exiting payroll. This will allow any problems/rejects from the government gateway to be corrected and reprocessed through payroll if required.

Once payroll has exited the RTI program can be run as a live updated. The status of Exit Payroll is not mandatory but probably the process most customers will follow.

A Clean Sweep report will also be available to allow final checking to ensure all employees have been processed for RTI.

Any rejections by HMRC resulting from the “live” run will not be able to be resolved via the payroll. A BADI will be provided to amend data (at EE level) to facilitate correcting erroneous data (if required) Customers must raise a VERY HIGH message for any HMRC rejections as they should NEVER occur!

back to top