- Switching provider
Payroll Migration: Switching Payroll Provider in Ireland
You do not have to wait until the end of the tax year to change payroll provider. A mid-year switch can be handled cleanly when the existing payroll data, Revenue access, year-to-date figures and cutover date are reconciled before the first live pay run.
The aim is continuity, not a restart. If the legal employer is unchanged, the migration normally continues under the employer’s existing PAYE registration while the people, systems or agent permissions used to process payroll change. Payrollcompany.ie manages that transition as a structured handover, then moves you into the ongoing process of running it.
A structured handover, not a software import
- Continuity under your existing PAYE registration
- Year-to-date balances reconciled, not rebuilt from scratch
- Revenue access arranged through proper agent/sub-user routes
- Known errors corrected, not carried forward silently
- A cutover date built around your real payroll calendar
Who it’s for
Who This Payroll Service Is For
A payroll migration can make sense if you are:
Switching bureau or provider
Changing from one payroll bureau or outsourced payroll provider to another.
Moving away from an accountant
You want a specialist payroll service rather than payroll bundled into general accountancy work.
Leaving an in-house or DIY process
Taking payroll out of an internal or do-it-yourself process.
Moving off spreadsheets
Moving from spreadsheets or a largely manual workflow into a managed service.
Changing software and provider together
Changing payroll software while also changing the person or provider responsible for running it.
Moving a book from a practice
Moving a payroll book from an accountancy practice to a white-label payroll partner.
Accountancy practices moving client payrolls can also use the same migration principles. Our For Accountants service section explains the separate white-label workflow and Revenue relationship in more detail.
The legal picture
What Stays the Same When You Change Provider
Changing payroll provider is not the same as changing employer. Your employees do not leave one employment and start another merely because a different provider processes the pay run.
Registration follows the employer, not the provider
Where the legal employer remains the same, the existing employer PAYE registration normally remains the registration used for payroll. Revenue treats employer registration as an obligation of the employer, while a new registration question can arise where there is a genuine change of employer or ownership.
Revenue ties the registration to the employer, and its change-of-ownership process deals separately with situations where a new employer takes over a business.
The employee’s existing Revenue employment record and payroll submissions also remain in Revenue’s systems. What does need to move is the payroll information required to continue calculating and reporting the same employment correctly in the new payroll system.
Opening balances
Year-to-Date Figures Do Not Rebuild Themselves
One of the most important migration steps is carrying forward accurate year-to-date payroll balances. The latest Revenue Payroll Notification (RPN) gives the current tax credits, Income Tax and USC cut-off points and other Revenue instructions, but it is not a replacement for a complete payroll handover.
Before every live payroll, Revenue requires the latest RPN to be requested and used. Our Revenue Payroll Notification guide explains that process in detail, while the migration itself also needs opening balances from the existing payroll records.
Depending on the payroll, those balances can include:
- Gross pay and taxable pay to date.
- Employer PRSI to date.
- Benefits-in-kind and other taxable benefits already processed.
- Director payroll figures where directors are included.
- Any adjustments or corrections that have already been made during the tax year.
- Income Tax, USC and employee PRSI deducted to date.
- Pension contributions and other payroll deductions.
- Statutory or authorised deductions currently in operation.
- MyFutureFund contributions already processed where applicable.
If those figures are wrong at cutover, the new payroll may produce incorrect cumulative results, inaccurate year-to-date payslips or confusing payroll reports even when the current RPN itself is correct.
Revenue access
Revenue Access Needs Its Own Cutover Plan
A provider switch may require a change to Revenue access, but the exact setup depends on how the outgoing and incoming providers are authorised.
Where the new provider will act as a Revenue agent, Revenue’s current agent e-linking process allows an online customer to approve or reject the agent-link request in ROS or myAccount.
The old provider’s access should also be dealt with deliberately. Revenue’s current agent guidance says that when an agent ceases to represent a client, Revenue should be notified so the agent can be removed from the relevant client listing.
Previous Payroll Submissions Can Need Additional Access
An agent can only view and amend payroll submissions filed under that agent’s own certificate. If a new agent needs to view or amend submissions filed by a previous agent or directly by the client, the employer may need to provide an appropriate ROS sub-certificate.
That makes access planning part of the migration rather than an afterthought. A new provider should not assume that being linked as the current payroll agent automatically gives visibility of every historical submission made by someone else.
Do Not Hand Over the Employer's ROS Login
A payroll migration should use the appropriate Revenue authorisation and user-permission route rather than sharing the employer’s administrator login details. Revenue provides agent links and employer sub-user certificates so access can be controlled without passing around the employer’s own ROS credentials.
Before cutover
What We Review Before Cutover
The handover starts with the payroll as it actually operates today. We review the records, the Revenue position and the recurring pay setup before deciding what should be carried into the new system.
- Employer name, PAYE registration number and payroll frequency.
- Hourly rates, salaries and recurring pay elements.
- Current RPN availability and any employees on emergency or Week 1/Month 1 treatment.
- MyFutureFund information relevant to enrolled employees.
- Enhanced Reporting Requirements processes where they form part of the payroll workflow.
- Outstanding payroll corrections or discrepancies.
- Current employee list, PPSNs, start dates and Employment Identifiers.
- Year-to-date payroll totals for each employee.
- Pension deductions and employer pension contributions.
- Benefits-in-kind and recurring taxable benefits.
- Current payslip and payroll-report requirements.
- Who supplies payroll inputs, who approves them and the current payroll cut-off.
- Any different pay frequencies, locations, director payrolls or specialist employee groups.
Process
How a Payroll Migration Works
1
Agree the scope
2
Set the cutover date
The date is chosen around your actual payroll calendar. It can be mid-year and does not need to be 1 January.
3
Collect the handover records
4
Confirm Revenue access
Where an agent link or employer sub-user access is needed, the appropriate Revenue route is put in place before the first live submission.
5
Reconcile the opening balances
We compare the figures being loaded into the new payroll with the agreed source records and the Revenue information available for the employer.
6
Resolve known discrepancies
If an earlier payroll submission is wrong, the correction is dealt with through the appropriate payroll or ROS process rather than silently carrying the error forward.
7
Retrieve current RPNs
8
Run payroll and review control totals
9
Make the live payroll submission
Payroll information is reported to Revenue on or before the pay date under the employer’s correct registration.
10
Close the old access route
Data quality
Corrections Discovered During Migration
A migration sometimes exposes issues that were already present, such as a duplicated employee, an incorrect year-to-date balance, a missed taxable benefit or a payroll submission that does not match the payroll records.
Revenue allows payroll submissions to be corrected through payroll software or ROS, as explained in its payroll corrections guidance. The right correction depends on what was wrong and when it occurred.
We don't paper over the difference
We don’t simply create an off-payroll balancing figure to make the new system agree. Where a discrepancy affects Revenue reporting, the payroll records and Revenue submission need to be aligned through the proper correction route.
No bureau required
Switching From an In-House or DIY Payroll
A migration does not need an outgoing payroll bureau. If you have been running payroll internally, the same controls still apply: confirm the employer registration, review employee records, reconcile year-to-date figures and identify anything that needs to be corrected before the next live pay run.
DIY migrations often need more attention to process as well as data. The new setup should define who sends payroll changes, the cut-off for inputs, who approves the run and how employee queries are handled. That prevents the informal habits of the old process being recreated in the new one.
Payroll Data Needs a Controlled Handover
Payroll files contain detailed employee personal and financial information. The Data Protection Commission specifically uses outsourced payroll as an example of a controller-processor relationship. The employer is the data controller and the payroll company is the data processor in that arrangement.
The migration should therefore use an agreed secure transfer method and a written processing agreement that reflects the payroll work being performed. Access should be limited to the people who need it for the handover and ongoing service.
Getting started
What We Need From You
You do not need to rebuild the payroll from memory. We start with the records you already have and identify any missing information during the review.
Year-to-date payroll totals.
Details of recurring pay, benefits and deductions.
Pension and MyFutureFund information where relevant.
Details of any unresolved payroll corrections.
Contact details for the outgoing provider if you authorise us to coordinate the handover directly.
After cutover
What Changes After the Migration
Once the cutover is complete, payroll moves from a one-off transition project into a repeatable pay-run process. The agreed inputs come in by the payroll cut-off, the latest RPNs are retrieved, payroll is calculated and reviewed, the Revenue submission is made on or before the pay date, and payslips and reports are issued through the agreed workflow.
Employees may notice a different payslip layout or a new payroll contact, but a provider change should not be used to reset their employment history, tax-year payroll totals or existing statutory records.
What goes wrong
Common Payroll Migration Problems
Choosing a cutover date before the data is ready.
A convenient date is not useful if the opening balances, employee records or Revenue access are still incomplete.
Assuming the new agent can see everything the old agent filed.
Revenue restricts agent access to submissions filed under that agent’s certificate unless the employer provides the appropriate additional access.
Loading totals without reconciling them.
Opening balances should agree to the source payroll records and the Revenue information available to the employer before they are relied on.
Sharing administrator credentials for convenience.
Use the proper agent or sub-user access route rather than circulating the employer’s ROS administrator credentials.
Treating the RPN as the whole handover.
The RPN provides current Revenue instructions, but the new payroll still needs accurate year-to-date and recurring payroll data.
Leaving old Revenue access open indefinitely.
Once the old provider no longer represents the employer, its agent relationship or other unnecessary access should be removed.
Carrying a known error into the new system.
If an earlier payroll or Revenue submission is wrong, deal with the correction as part of the transition instead of embedding it in the new opening balances.
Changing too many things in the first live run.
Where practical, preserve established pay frequencies and pay elements through cutover, then make separate planned changes once the new payroll is stable.
Frequently asked questions
Common questions about payroll migration
Can We Switch Payroll Provider Mid-Year?
Yes. A provider change can be made during the tax year. The key is to reconcile year-to-date payroll information, arrange the correct Revenue access and choose a cutover date that fits the real pay cycle.
Do We Need a New PAYE Registration?
Not simply because you appoint a different payroll provider. If the legal employer remains the same, payroll normally continues under the existing employer PAYE registration. A new registration question can arise where there is a genuine change of employer or business ownership.
Will Employees' Tax Credits Reset?
No. The new provider requests the latest RPN from Revenue for the existing employment. The payroll system also needs the correct year-to-date opening balances so the employee’s ongoing payroll record is not treated as if the tax year started again.
Can the New Provider See Payroll Submissions Filed by the Old Provider?
Not automatically. Revenue says an agent can view and amend submissions filed under that agent’s certificate. Access to submissions filed by a previous agent or directly by the employer can require an appropriate employer sub-certificate.
Should We Give the New Provider Our ROS Password?
No. Revenue access should be arranged through the appropriate agent relationship or controlled sub-user certificate rather than sharing the employer’s administrator credentials.
What Happens to the Old Revenue Agent Link?
If the outgoing provider is recorded as a Revenue agent and no longer represents you, the agent relationship should be removed through the appropriate Revenue process once the handover is complete.
What If We Discover an Error From an Earlier Payroll?
Revenue allows payroll submissions to be corrected through payroll software or ROS. The migration review should identify the issue and determine the proper correction instead of hiding it inside a balancing adjustment.
Do We Have to Start on 1 January?
No. The cutover should be chosen around your payroll timetable and readiness of the migration data. Year-end can be convenient, but it is not the only practical point to change provider.
Can You Take Over Weekly or Multiple Pay Frequencies?
Yes, where those pay frequencies form part of the agreed payroll scope. The migration maps each payroll calendar and cut-off so the first live runs are sequenced correctly.
Can You Take Over Payroll We Currently Run Ourselves?
Yes. We review the existing records, Revenue registration, employee data and year-to-date figures in the same way, then agree the cutover and ongoing payroll process.
Can You Coordinate With Our Current Provider?
Yes, if you authorise us to do so. Direct coordination can make it easier to obtain the agreed payroll reports, employee data and outstanding-issue list, while you remain in control of the relationship and access permissions.
How Long Does a Payroll Migration Take?
It depends on the number of employees, pay frequencies, payroll complexity, data quality and Revenue access required. We do not use a fixed timeframe unless it has been agreed for your specific migration.
Disclaimer: This page provides general information about payroll migration and Irish payroll administration. It is not legal, tax or data-protection advice. The correct Revenue access, correction process and data-protection arrangements can depend on the facts of the employer’s existing setup. Employers remain responsible for payroll compliance and should obtain appropriate specialist advice where a particular legal or tax issue requires it.