Auto-enrolment pension Ireland does not end when the first enrolment form is processed. It becomes a permanent payroll and HR record-keeping duty, repeated every pay period and every time a new hire joins. MyFutureFund, administered by NAERSA and overseen by the Pensions Authority, identifies and enrols eligible employees, manages opt-in, opt-out and suspension requests, and collects contributions. Employers still run payroll as usual, with contributions beginning January 2026. That means the real work is the recurring loop: assessing who is in scope, applying the correct contribution tier, handling statutory windows, keeping evidence, and diarising re-enrolment so it survives staff turnover.

This guide is for employers already inside the system. You will learn why auto-enrolment is a recurring payroll duty, what to confirm before your first pay run, how to run eligibility assessments each period, how to track contribution step-ups, how to handle opt-ins, opt-outs and suspensions within the statutory window, how to build an evidence trail, how to diarise re-enrolment, and what records to keep. By the end, you can turn auto-enrolment into a routine you can prove.

Why Auto-Enrolment Is a Recurring Payroll Duty, Not a One-Off Sign-Up

Auto-enrolment is live. Contributions to the new Ireland pension scheme began in January 2026, and contributions are due by the employee’s pay date, as set out in gov.ie guidance for employers.

Roughly 750,000 workers earning €20,000 or more with no workplace pension are in scope (MyFutureFund).

NAERSA carries most of that administration at no cost to employers, and employer contributions are deductible for corporation tax, leaving payroll accuracy and record-keeping as your real workload (MyFutureFund Employer Handbook).

That makes auto-enrolment a recurring duty, not a sign-up. Four jobs repeat every pay period:

1. Assess who is in scope.
2. Apply the correct contribution tier.
3. Handle any opt-in or opt-out inside its statutory window.
4. Keep a re-enrolment date that survives staff turnover.

Skip one and the gap surfaces later as a contribution shortfall, or as a trail you cannot reconstruct. Before any of that, you need to know exactly who sits in scope.

Prerequisites: Know Who Is In Scope Before Your First Pay Run

Before you can run assessment as a routine, confirm who is genuinely in scope. Employees aged 23 to 60 earning €20,000 or more who are not already in an exempt occupational scheme or a PRSA are automatically enrolled, per the MyFutureFund participant guide.

Outside that band, entry is voluntary: MyFutureFund states that people earning under €20,000 and those aged 18 to 22 or 60 to 66 may opt in. Broker commentary instead describes the upper voluntary limit as being under state pension age, which does not produce the same cut-off. Treat the 60-to-66 figure as unconfirmed and reconcile it against current NAERSA guidance before you apply an age rule in payroll.

If exemption rests on an existing workplace scheme, check that scheme meets the minimum contribution levels set by the Section 52 amendment regulations, effective 1 January 2026.

Portability also matters at the front door: employees may remain enrolled when they change employers, so a new hire is not automatically a clean-slate assessment.

Before the first pay run, make sure payroll holds usable flags for date of birth, annualised earnings, scheme membership status and start date. That turns assessment into a report you run rather than a check you remember.

Step 1: Run the Eligibility Assessment Every Pay Period

Run that report every pay period, not once at hire. Eligibility is a live status: a change in pay, age band or scheme membership can pull someone into scope part-way through the year.

Annualise before you test. Convert the current period’s gross to an annual figure before comparing it with the €20,000 threshold. Testing a single week’s or month’s pay against an annual limit will misclassify part-time, seasonal and variable-hours staff.

Treat age as a live trigger, not a fact on file. Payroll should report the pay period in which an employee turns 23, entering the auto-enrolment band, and the period in which they reach the upper limit and leave it. Discover these at year end and the deduction has already started late.

Assess every new hire as its own case, with a prior status check. Check for ported enrolment status on every new hire, as gov.ie confirms enrolment travels with the employee.

Log every outcome against its pay period: enrolled, opted in, excluded or exempt. A later query about a specific week should be answered from a dated record, not reconstructed from memory.

With each period’s assessment logged, the next task is applying the correct contribution tier.

Step 2: Apply the Right Contribution Tier and Track the Step-Ups

Once the assessment outcome is logged, the rate follows. The schedule reported by Lockton steps up every three years: years 1 to 3 at 1.5% employee, 1.5% employer and 0.5% State (3.5% combined); years 4 to 6 at 3%, 3% and 1%; years 7 to 9 at 4.5%, 4.5% and 1.5%; and 6%, 6% and 2% from year 10, the target tier. Confirm each rate against NAERSA guidance before you configure payroll, as the tier schedule is broker-sourced.

The State adds €1 for every €3 the employee contributes. Employer and State contributions apply up to €80,000 of gross salary, and that figure is a calendar-year test rather than a per-pay cap: contributions stop after the pay period in which the threshold is breached, and contributions on the excess are not refunded (Auto-enrolment: Your questions answered). NAERSA then issues a new AEPN carrying a 0% rate for the rest of that year. High earners need a threshold calculation, not a straight percentage of pay.

Two controls keep the steps manageable. Diarise the step-up dates once confirmed with NAERSA: a tier change is a deliberate payroll configuration change, and missing one creates a shortfall that is far harder to unwind than to prevent. Then build one rate table per scheme year and apply it from a single source, so a mid-year change of pay frequency, hours or salary cannot leave two conflicting percentages on the same employee record.

Step 3: Handle Opt-Ins, Opt-Outs and Suspensions Inside the Statutory Window

With the tier table settled, the next exposure is timing: a contribution can be configured correctly and still be wrong if a notice is applied outside its window.

Treat opt-out as a two-move sequence: six months of enrolment, then a two-month period in which the employee can opt out or suspend. Secondary commentary reports the first opt-out window opening in July 2026, but the primary NAERSA wording was not confirmed here, so verify current dates and wording directly with NAERSA before relying on them.

Diarise two dates for every auto-enrolled employee: the six-month enrolment anniversary and the end of the two-month window. The anniversary is the trigger; the deadline makes it a compliance task.

Do not assume an opt-out is permanent, confirm the re-entry mechanic with NAERSA.

Treat an opt-in from the voluntary groups as a payroll instruction, not a preference note: it needs a start period, a contribution tier and an audit entry dated when it was received. Run every opt-in, opt-out and suspension request through one queue with receipt timestamps, so nothing sits in an inbox while a deadline passes. The next step is turning that queue into evidence.

Step 4: Build the Evidence Trail That Proves the Window Was Met

Getting the window right in Step 3 only counts if you can prove it later. No source prescribes a format for opt-out records, but the operational need is unambiguous: an employer must show that a notice was received and actioned inside the statutory window.

Record three things for every notice: date and time received, pay period applied, and resulting payroll change. Those fields answer almost any later query, whether from an employee, an auditor or NAERSA. If a notice arrives after payroll cut-off, the log should show both the receipt date and the period it took effect.

Reconcile each pay period before you close it: the total auto-enrolment deduction should equal the sum of individual employee deductions for that period, and any variance should be investigated rather than carried forward.

Keep one log per pay period covering enrolments, opt-ins, opt-outs, suspensions and nil returns. A nil return is evidence too: it shows the assessment ran even when nothing changed.

Finally, confirm retention periods and document requirements with NAERSA. Where official guidance is silent, say so and point readers to the source rather than asserting a rule it does not contain.

With the evidence trail in place, the next recurring trigger is re-enrolment, which needs a date that survives staff turnover.

Step 5: Diarise Re-Enrolment and Make It Survive Staff Turnover

The evidence trail tells you what happened in each period. It cannot tell you when the next obligation falls due.

This research set offers no explanation of how or when re-enrolment occurs. The honest operational answer is to diarise the date per employee, keep each assessment complete and current, and confirm the process with NAERSA. Do not assume an opt-out is permanent or that a re-enrolment date can be moved.

A date-based trigger only works if it lives in a system rather than in someone’s head. Staff turnover in payroll and HR is one of the most common reasons a re-enrolment date gets missed.

That turns every leaver into a handover task, because the enrolment status leaves with them.

Build a joiner handover note that captures prior enrolment status, current contribution tier, date of last assessment and any notices on file. A leaver note should confirm the same information is passed on.

Re-check the assessment flags at every employment anniversary and every pay rate change, so the re-enrolment trigger is backed by accurate data when it fires. With dates and handover data in place, the final step is the checklist that proves the routine ran.

Your Pay-Period Records Checklist

Dates and handovers are only as strong as the records behind them. Keep the following so each pay period can prove itself.

Per pay period: log assessment outcomes for every employee, the contribution tier applied, any opt-in, opt-out or suspension notice with its receipt date, the reconciliation total, and confirmation that step-up dates were checked against the calendar.

Per employee: hold date of birth, annualised earnings, scheme membership status, enrolment date and the pay period of the last assessment. That set lets you re-test eligibility without rebuilding a file.

Calendar: six-month enrolment anniversaries, the two-month opt-out window attached to each, contribution step-up dates (confirmed in your tier table), and any re-enrolment date NAERSA has confirmed.

Quarterly: review everyone recorded as exempt or excluded. A scheme change or a salary change can quietly move someone into scope.

Where workforce tools help: Staffly covers scheduling, time tracking, HR and compliance records, shift cover and payroll-ready output for Ireland and UK teams, so hours and pay data arrive in one place to feed the assessment step. Staffly does not perform NAERSA assessment, opt-out or re-enrolment duties; those stay with the scheme administrator and your payroll.

Conclusion: Turn Auto-Enrolment Into a Routine You Can Prove

Records only protect you if the routine behind them runs every period. Auto-enrolment is a permanent payroll and HR record-keeping duty, and the employers who handle it well are those who turned it into a routine rather than a memory exercise.

Three actions for this month:

1. Run a full assessment of your current workforce against the age and €20,000 earnings rules.
2. Put the confirmed contribution step-up dates, plus every six-month enrolment anniversary, in the payroll calendar.
3. Check with NAERSA on the opt-out window, the age band question and re-enrolment mechanics, so your process rests on confirmed rules rather than assumption.

Then set the evidence standard: every notice timestamped, every pay period reconciled, every assessment logged against the period it applied to.

Do that and staff turnover becomes a handover task rather than a compliance risk, because the dates and the records live in the system, not in the person who used to run payroll.