PAYE Modernisation Ireland Guide 2026

An employer guide to real-time payroll reporting

PAYE Modernisation has applied since 1 January 2019. It changed payroll reporting from a periodic administrative exercise into part of every pay run. Employers now use Revenue data to calculate PAYE and USC, report pay and statutory deductions in real time, and deal with corrections against the payroll period in which the payment actually happened.

The core rule: payroll information must be reported to Revenue on or before the pay date. The deadline applies whether you run payroll weekly, monthly or only occasionally.

That does not make payroll simple. The RPN can change during the year. Employees can move between cumulative and Week 1 treatment. Emergency tax rules vary by pay frequency. PRSI rates change on 1 October 2026. A correction may belong in the next payroll or in the original submission, depending on what went wrong. The monthly return is built from the data already sent. Getting those details right as payroll happens is what keeps the year-end position clean.

The operating sequence: retrieve the latest RPN, confirm the pay date, process the correct pay and deductions, report the payroll on or before that date, check the Revenue response, and keep the records behind the calculation.

PAYE Modernisation 

Before 2019, the employer reporting cycle centred on periodic and annual returns. PAYE Modernisation replaced that structure with payroll submissions sent as payments are made. Revenue then uses those submissions to generate the monthly statement and statutory return.

Employees can also view pay and statutory deduction details reported by employers in myAccount. That visibility is one reason payroll errors surface much faster than they did under annual reporting.

Small employer or large employer, the reporting rule is the same. The process may be simpler where there is only one employee, but the RPN, pay-date and payroll-submission obligations do not disappear because a payroll is small.

Key terms

Start every payroll run with the latest RPN

Before running payroll, an employer must request the latest RPN for each employee. This is how Revenue communicates the figures and basis payroll must use.

The RPN is not a document to copy into payroll once and leave untouched. Tax credits can change. Rate bands can be reallocated between jobs. Revenue can move an employee from Week 1 to cumulative treatment. A taxable Department of Social Protection payment can alter the employee position. If payroll retrieves an old RPN and never checks again, the calculation can be wrong even where the software itself is working perfectly.

What the RPN contains

• The employee’s total tax credits. The employer does not receive a breakdown of the individual credits behind the total.
• Income Tax and USC cut-off points.
• Pay, Income Tax and USC already deducted in a ceased employment since 1 January, unless the RPN is on a Week 1 or Month 1 basis.
• Any Income Tax or USC exemptions that Revenue has applied.

Operate what Revenue returns. That includes an RPN with nil credits or a nil rate band. If an employee asks payroll to add a Rent Tax Credit, move a rate band or change their tax basis, the employer cannot make that adjustment independently. The employee must deal with Revenue, and payroll acts when a revised RPN becomes available.

How employers retrieve RPNs

Most payroll software retrieves RPNs through Revenue integration. Revenue also allows RPN requests through ROS for employers who do not use an integrated payroll package. Whatever method you use, build the request into the payroll workflow rather than relying on a copy retrieved days or weeks earlier.

A simple control that catches a lot: retrieve RPNs after payroll inputs are final but before calculations are approved. This reduces the chance of using a credit or tax basis that Revenue changed during the pay cycle.

First job, later job and re-employment

For a person’s first job in the State, the employee registers the employment through myAccount. For subsequent jobs, the employer registers the employment when requesting the RPN.

Leavers and post-cessation payments

When an employee leaves, include the date of leaving on the final payroll submission. There is no separate P45 and there is no general final-payment flag to complete.

A payment after the employee has left still needs to be reported correctly. For a post-cessation payment in the same year, use the available RPN, the original Employment ID and the original cessation date. For an out-of-year post-cessation payment, Revenue sets out a separate RPN request process. Do not reopen the employment simply to make a late payment.

Revenue explains the post-cessation process for current-year and out-of-year payments.

The January RPN check

For 2026, RPNs were available from early December 2025. A 2025 RPN must not be used for a payment made in 2026. Request 2026 RPNs before the first payroll run of the year.

PAYE works on the payment date. If December overtime is paid in January, it belongs in the January payroll submission and the 2026 RPN is used, even though the work was done in 2025.

Payroll submissions and the on-or-before rule

Every time an employee is paid, the employer must report pay and statutory deductions to Revenue on or before the payment date. That report includes the employee being paid, the amount of pay and the statutory deductions for that payment.

What goes into a payroll submission

The pay date is not always the processing date

Revenue’s pay date guidance distinguishes between cash, cheque and bank transfer. For a bank transfer, use the date the funds are scheduled to be made available in the employee’s account.

This matters when payroll is processed early. A payroll team might calculate salaries on Monday, release the bank file on Tuesday and pay employees on Friday. The payroll submission belongs to Friday, and it must be reported no later than that pay date. Processing early does not move the Revenue pay date to Monday.

Do not sequence Revenue reporting after payment: the safest workflow is calculation, review, payroll submission, response check, bank file release. If your banking process requires a different sequence, make sure the Revenue report still reaches Revenue on or before the pay date.

Submission methods

• Direct reporting through payroll software. The software sends payroll data to ROS and receives a response.
• File upload through ROS, where the payroll package creates a file that is uploaded manually.
• ROS online form for employers without payroll software. This can work for a small payroll but creates more manual steps.

Sending the file is not the end of the control. Check that Revenue accepted it. A rejected or invalid submission still needs action. Keep the submission response or other evidence that the payroll was successfully reported.

Late or missing submissions

A failure to send a required payroll notification can give rise to a fixed penalty of €4,000 under Section 987 of the Taxes Consolidation Act 1997, as amended. The penalty should not be described as an automatic €4,000 charge for every late employee line, but the on-or-before rule is a hard compliance control.

If a genuine system problem prevents filing, keep evidence of what happened and submit as soon as possible. Do not build normal payroll around after-the-fact submissions on the assumption that a technical explanation will always remove the compliance risk.

Cumulative, Week 1 and emergency basis

The payroll submission tells Revenue what was paid. The RPN tells payroll how Income Tax and USC should be calculated. The basis on the RPN determines whether earlier pay periods are brought into the calculation or left alone.

Cumulative basis

Cumulative is the normal year-to-date method. Pay, tax credits, rate bands and tax deducted are considered from 1 January to the current pay date. If Revenue changes an employee’s credit position and issues a cumulative RPN, the next payroll can correct the year-to-date PAYE position in one calculation.

That can produce a surprisingly low PAYE deduction or a refund. Do not override the result just because it looks different from a normal payslip. Check the RPN, the year-to-date figures and the payroll calculation. The size of the adjustment depends on the employee’s actual position, not on a fixed number of months of credit.

Week 1 or Month 1 basis

Week 1 and Month 1 are valid RPN instructions, not emergency tax. Each pay period is calculated on its own. Unused credits do not carry back to earlier pay periods, and an employer does not make a retrospective refund while the non-cumulative RPN remains in force.

If Revenue later issues a cumulative RPN, payroll can then recalculate the year-to-date Income Tax and USC position. Any refund due can be processed through payroll. If Week 1 remains in force at year-end, the employee can review the full-year position through myAccount.

Emergency basis when there is no RPN

Where the employer cannot retrieve an RPN, use the 2026 emergency basis. No tax credits apply and emergency USC is 8% on all income.

Within the temporary band, Income Tax is 20% and income above the band is taxed at 40%. There are no tax credits. PRSI does not have an emergency rate and continues under the employee’s normal PRSI class and earnings rules.

Getting a new starter off emergency tax

• First job in the State: the employee registers the employment through myAccount and gives the PPSN to the employer.
• Later job: the employer registers the employment by requesting the RPN with the correct details.
• Retrieve the RPN before each subsequent payroll. As soon as a valid RPN is available, use the basis shown on it.
• Where Revenue issues a cumulative RPN, any PAYE and USC overpayment can normally be corrected through payroll on the next payday.

Monthly statements, returns and payment deadlines

Revenue generates the employer monthly statement by the 5th of the following month from the valid payroll submissions for that month.

Review the statement rather than treating it as an automatic bill. If the payroll submissions are right, accept it. If something is wrong, correct the payroll submission. If you do nothing, the statement is deemed to be the statutory monthly return on the 14th.

A quarterly or annual payment arrangement changes when cash is remitted. It does not remove the real-time payroll submissions or monthly statutory returns. Revenue also sets eligibility conditions for quarterly remitting, including the annual liability threshold and compliance history.

Variable Direct Debit

Revenue operates a Variable Direct Debit for Employers’ Income Tax. Revenue requests the balance outstanding from the employer bank account on the due date.

It is useful as a payment control, not a substitute for reconciliation. A direct debit can fail. The employer still needs to review the monthly return, make sure the liability is correct and check that the payment was collected. Signing up also moves annual remitters to monthly remitting immediately and quarterly remitters from the first month of the next quarter.

Correcting payroll errors properly

The correction depends on what actually happened to the employee and what Revenue was told. This distinction is easy to miss. A genuine employee overpayment is not the same problem as reporting the wrong figure for a payment that was actually correct.

Revenue’s payroll corrections guidance is built around the same principle: the payroll record should match what happened to the employee on the relevant pay date.

Why the original period matters

Suppose an employee was paid €900 on 31 March but the submission reported €9,000. Do not try to make April negative so the year-to-date total happens to look right. Correct the March submission. Revenue needs the March record to show the March payment.

The opposite can also happen. If the employee should have received €1,000 in March but was actually paid only €900, the €100 is an employee underpayment. Pay the €100 in the next payroll and report it when it is actually paid. The correction follows the money, not the intended amount.

Build an audit trail around corrections

• Record what was wrong and when it was identified.
• Keep the original submission reference or line item information.
• Keep the replacement or amended submission and the Revenue response.
• Where employee net pay changed, retain the communication explaining the adjustment.
• Reconcile the revised Revenue statement or return after the correction is processed.

Self-correction, interest and Revenue interventions

Correcting a payroll submission fixes Revenue’s payroll data. If the correction also reveals an underpayment of PAYE, USC or PRSI, you then have an underlying tax default to regularise. Revenue’s Code of Practice determines the route, time limits and potential penalty treatment.

Self-correction without penalty

Under the Revenue Code of Practice for Compliance Interventions, self-correction without penalty can be available if the conditions and time limit are met.

• Notify Revenue within the applicable time limit. An amended ROS return by itself is not the notification required by the Code.
• Provide a computation of the correct tax and statutory interest.
• Pay the tax and interest in full with the submission.

For PAYE, USC and PRSI returns, the normal self-correction deadline is before the due date for the relevant Income Tax or Corporation Tax return for the chargeable period. Where there is no Income Tax or Corporation Tax filing obligation, the Code gives a 31 October deadline in the year following the year in which the monthly PAYE return was due.

The timing changes once Revenue has notified a Level 2 or Level 3 intervention for the period. At that point, self-correction without penalty is no longer available for the issue under intervention. Material historic payroll errors should be reviewed before correspondence is sent to Revenue so the business understands which correction or disclosure route applies.

Revenue intervention levels

A Risk Review is Level 2, not Level 1. That distinction matters because the opportunity to make an unprompted qualifying disclosure ends when a Level 2 notification is issued. A prompted qualifying disclosure can still be available before the Risk Review or Audit begins, subject to the Code.

Interest on late employer liabilities

Late Employers’ Income Tax, PRSI, USC and LPT currently attracts interest at 0.0274% per day from the date the payment was due.

At that rate, a €50,000 underpayment accrues about €13.70 a day. Interest is separate from any penalty. Paying the underlying tax quickly stops the daily interest from continuing to build.

PAYE assessments

Revenue can raise an employer PAYE assessment where too little tax has been reported. The general time limit is four years, with no time limit in cases of fraud or neglect. This is separate from the six-year record retention rule.

The 1 October 2026 Class A PRSI change

The Department of Social Protection Class A schedule changes from 1 October 2026.

The rate change follows the pay date, not the work period. A September salary paid on 5 October uses the rates in force on 5 October. A weekly payroll paid on 30 September uses the pre-October rates.

Do not apply the Class A percentages as a flat shortcut around the lower earnings bands. Class A includes a tapered employee PRSI credit on weekly earnings between €352.01 and €424, and different subclasses apply at different earnings levels. Use the current DSP schedule where pay sits near a threshold.

Payroll control for October: confirm the software update before the first October pay date, then test at least one employee below the PRSI charge threshold, one inside the tapered-credit range, one below the €552 employer threshold and one above it.

Keep taxable BIK and ERR separate

Taxable benefits in kind belong in payroll as notional pay. Company cars, taxable employer-paid medical insurance and other taxable benefits are dealt with through the PAYE payroll process. This did not begin in 2024.

Enhanced Reporting Requirements are a separate real-time reporting obligation introduced from 1 January 2024 for specified non-taxable payments and benefits.

• Travel and subsistence paid within the applicable tax-free rules.
• Remote working daily allowance, currently up to €3.20 per qualifying day.
• Qualifying Small Benefit Exemption benefits, up to five benefits with a combined annual value not exceeding €1,500 in 2026.

Report an ERR item on or before the date it is paid or provided. The ERR report does not make a payment tax-free. The payment must satisfy the underlying exemption conditions first. Likewise, do not put a taxable BIK through ERR instead of payroll.

Records matter here as well. Revenue requires supporting ERR records to be kept for six years after the end of the tax year to which they relate.

PAYE Settlement Agreements for minor and irregular benefits

A PAYE Settlement Agreement can allow the employer to settle Income Tax, USC and PRSI on qualifying minor and irregular non-cash benefits rather than taxing each employee through ordinary payroll.

The scope is deliberately narrow. Cash wages, salaries and bonuses do not qualify. Large benefits such as company cars, accommodation and preferential loans are outside the PSA rules. Round-sum allowances are also excluded.

• Apply to Revenue in writing on or before 31 December of the relevant tax year.
• Use the PSA only for benefits Revenue accepts as minor and irregular.
• Keep the underlying benefit records and the calculation of the tax settled by the employer.

A PSA is not a general repair mechanism for benefits that should have been processed through payroll. If an item was ordinary taxable pay or a recurring substantial benefit, first establish the correct payroll treatment rather than assuming it can be swept into a year-end agreement.

Payroll software and outsourcing controls

Software can automate a lot of PAYE Modernisation. It cannot decide whether your inputs are right. The same is true of outsourcing. A payroll bureau can operate the process, but Revenue still holds the employer responsible for compliance.

Revenue expressly states that the employer remains responsible whether payroll is reported through payroll software, a payroll company, another agency or ROS.

If you outsource payroll, agree the workflow in writing

• Cut-off times for salary changes, starters, leavers, benefits and expenses.
• Who retrieves RPNs and when.
• Who submits payroll data and checks the Revenue response.
• Who handles rejected submissions and corrections.
• Whether ERR reporting is included, and which team supplies the data.
• How legislative changes are tested and applied.
• Who reviews monthly statements and authorises tax payment.

The employer should still retain visibility. At minimum, management should be able to see the payroll approval, Revenue submission status, monthly liability and any corrections made. Outsourcing should reduce work, not create a blind spot around a statutory obligation.

Records and year-end controls

Employer payroll records must generally be retained for six years after the end of the tax year to which they relate.

Keep enough to reproduce the payroll, not just the payslip. That means the pay inputs, RPN used, calculation, submission, Revenue response, correction trail and supporting documents for items such as BIK and expenses.

• Gross pay and payslip records.
• RPNs or evidence of the RPN data used in each run.
• Payroll submissions and Revenue responses.
• PRSI class decisions and supporting employee information where relevant.
• BIK calculations, vehicle or benefit records and employee contributions.
• ERR supporting records for travel, remote working and Small Benefit Exemption items.
• Correction records, revised submissions and monthly-return reconciliations.

What year-end looks like now

There is no annual P35 to rescue a messy year. A clean year-end comes from accurate pay-date reporting and prompt correction during the year. The December review is a final control, not the first time the employer should compare payroll with Revenue.

Payroll scenarios

The examples below are fictional and show the payroll treatment, not individual tax advice.

Scenario 1: first job, emergency tax and cumulative correction

Aoife starts her first job in Ireland and gives the employer her PPSN, but she has not registered the job through myAccount. The employer cannot retrieve an RPN, so emergency tax applies. Aoife registers the job after her second payslip. Before the third payroll, the employer retrieves a cumulative RPN. Payroll uses that RPN, recalculates the year-to-date Income Tax and USC position and refunds any overpayment due through the payroll calculation.

Scenario 2: a submission error is not an employee overpayment

ABC Engineering pays Liam €3,000 correctly, but the payroll submission reports €30,000. Liam was not overpaid. The Revenue record is wrong. The employer amends the original submission for that pay date rather than creating a negative adjustment in the next payroll. Once Revenue processes the correction, the employer checks the revised statement.

Scenario 3: employee was genuinely overpaid

Niamh should receive €850 but is paid €950 because an unpaid absence was not supplied before payroll. That is a real €100 overpayment to the employee. The employer recoups the €100 through the next payroll using Revenue’s overpayment correction approach. It does not rewrite the previous submission to pretend Niamh received only €850 when she actually received €950.

Scenario 4: September work, October pay date

A monthly payroll covers work performed in September but employees are paid on 5 October 2026. The October Class A PRSI rates apply because the pay date is 5 October. The payroll team does not use the September rates simply because the work was done in September.

Scenario 5: Week 1 changes to cumulative

Conor changes jobs and the new RPN is on Week 1 basis. Payroll treats each pay period separately and does not refund earlier overdeductions while Week 1 remains in force. Conor deals with Revenue, which later issues a cumulative RPN. The next payroll recalculates the year-to-date position and makes any PAYE and USC refund due.

PAYE Modernisation payroll checklist

• Confirm every employee being paid is registered correctly and has the right Employment ID.
• Retrieve the latest RPN immediately before payroll calculations are approved.
• Use the tax basis and figures on the RPN. Do not add employee credits manually.
• If no RPN is available, apply the correct emergency basis for the pay frequency and PPSN position.
• Confirm the pay date, especially where payroll is processed several days before funds reach employees.
• Apply the correct PRSI class, subclass and pay-date rates.
• Include taxable BIK in payroll and keep ERR items in the separate ERR reporting stream.
• Submit the payroll on or before pay date and check the Revenue response.
• Review the monthly statement and correct errors before the 14th where possible.
• Pay the employer liability by the correct monthly, quarterly or annual remittance deadline.
• Correct the original submission when Revenue was told the wrong amount for an earlier payment.
• Use the next payroll only where the employee was genuinely overpaid or underpaid and the later payment or recoupment is what actually happens.
• Keep payroll, RPN, submission, BIK, ERR and correction records for the required retention period.
• Run a January RPN refresh and an October PRSI-rate check as explicit annual controls.

Frequently asked questions

General information

This guide is based on Revenue and Department of Social Protection guidance available on 31 August 2026. It is general payroll information, not personal tax, legal or financial advice. The correct treatment of a specific payroll issue can depend on facts not covered in a general guide.