The new Employment ID is used in the following cases:

Concurrent employments

When employers have the same employee twice on their payroll, with two separate employments. Its main purpose is so that the correct RPN can be allocated to the correct employment for the employee.

This scenario does not happen very often, with most employers combining the salary. In practice, the vast majority of users will have no use for the Employment ID as this condition is unlikely, and can safely ignore it.

Consecutive employments

If an employee leaves employment and then is re-employed during the same tax year, then they should be allocated a new, different employment ID to their previous employment.

How Employment IDs are set up

Employment IDs can be allocated by one of these methods:

  • When you submit a payroll submission in the Revenue>Submit screen, when the Employment ID entered in the Employee screen>Contact tab Employ ID field has been changed since the last submission.
  • Creating a New RPN request manually via, using a different Employment ID
  • A new employment can also have a blank employment ID if it was set up through jobs and pensions by the employee.

Note: You should not change an employment ID for a current employment once an Employment ID is notified to Revenue. Each time a payroll submission is made with a different or new Employment ID a new employment is created on Revenue systems for that employee.

You may find that there are duplicate RPNs for the same employee, even if this wasn't your intention. These can be resolved by following the instructions in this document:


How to change the employment ID in Payback

You will find the Employment ID in the Employee screen Contact tab. It is a field called 'Employ ID'

In order to successfully submit a PSR, each employee with a PPSN should also have an Employment ID. Payback automatically sets this up for you and defaults the Employment ID to zero if you are setting up a new employee, or importing data from an old back up where employees did not have Employment IDs (Pre - PMOD)

Generally, you should leave this value alone, otherwise you may end up with duplicate RPNs for the employee as described above.

Instances when this value should be changed are:

  • You want the match the Employment IDs for imported RPNs, so the tax information will be updated for the employee
  • ID the employee leaves and then is re-employed
  • The employee has concurrent employments.

Importing RPNs with Duplicates

If when you retrieve your RPNs there are duplicates, you may have to change the Employment ID in the Employee screen to match that of the record you wish to import.

RPNs are matched up to employees using PPSN and also Employment ID

For example, if an employee has two RPNs, one with an EmploymentID of 'XZY' and the other with an employment ID of '3' and you want to use the record with Employment ID of '3', then you should ensure that the Employ ID field in the Employee Screen is set to '3' before importing the RPNs


  • Payback defaults the Employment ID to 0. New employees set up in Payback will automatically have an Employment ID of 0. 
  • If you import an old database (from before PMOD) then the Employment IDs will automatically be set to 0.
  • It is recommended not to change the Employment ID unless you have Duplicate RPNs, an Employee has rejoined your company, or you wish to set up a concurrent employment
  • Blank Employment ID are matched to '0'. This means that imported RPNs with a blank Employment ID will automatically be linked to the appropriate employee with a 0 in the Employment ID and matching PPSN

Try out a fully functional version of Payback. You can process payroll for all your employees for 2 pay periods.

Visit our secure webstore

Download a Free Trial

Get started with a free trial. You can process two full payments and be confident that Payback does everything you require at no risk.