Your site team approved the hours. Your payroll run should be straightforward. Yet by payday, overtime has shifted, a Sunday premium has disappeared, and an employee is asking why their payslip does not match the rota. A recurring problem in Irish payroll is not the calculation itself. It is the handoff.

This tutorial follows those hours out of construction and into Irish payroll. We will look at why payroll errors start at the handoff, not in the payroll run; what payroll-ready time data has to contain; how overtime bands cause hours to drift; how Sunday premiums and public holiday pay differ between entitlement and calculation; and how PRSI, payslips and the HR payroll handoff fit together. We will also show what one approved hours record looks like in practice, work through a week with overtime, a Sunday and a public holiday, and finish with a pre-pay-run checklist. The goal is simple: export approved hours once, flag exceptions early, and stop employees finding payroll errors before you do.

Why Payroll Errors Start at the Handoff, Not in the Payroll Run

The rota lives with the manager. The timesheet lives with whoever approves hours. The payroll file lives with payroll or finance. In practice those three sources produce slightly different versions of the same week by the time the run opens.

In our experience working with Irish employers, the recurring fault is transfer, not calculation. The arithmetic inside the payroll software is usually right. What goes wrong is approved hours re-typed into a payroll file, where a rounded half hour or a dropped shift quietly changes the outcome.

Every handoff adds another chance for overtime bands, Sunday premiums and public holiday treatment to be applied differently from the last run. That is how two identical weeks produce two different payslips, with no change to the employee’s contract or the employer’s policy.

The difference usually surfaces on the payslip itself. The employee spots it before payroll does, and unwinding a shortfall after payday takes longer than checking the inputs before it.

The adult national minimum wage rising to €14.15 per hour from 1 January 2026 is a useful prompt to review payroll inputs, contracts and record-keeping in one pass, since gross pay for minimum wage purposes includes shift premia and bonuses.

This section follows on from our earlier post on capturing hours on site. Hours are only useful once they reach payroll intact, and that journey starts earlier than most employers expect.

What Payroll-Ready Time Data Has to Contain

The way to close that handoff gap is to define, once, what payroll actually needs from time data. Five elements carry the weight.

One approved figure per employee, per pay period, dated. Hours must be broken down by date and shift, not collapsed into a weekly total. A premium belongs to the day that earned it: a Sunday shift is a Sunday shift, not one fifth of 40 hours.

Flags, not just hours. Payroll needs to see which hours crossed an overtime threshold, which shift was worked on a Sunday and which date was a public holiday. A total of 45 hours tells an administrator nothing about where the premium sits.

Leave and absence recorded alongside worked hours. Statutory leave, sick leave and unpaid time kept in the same record removes the end-of-period reconciliation between two sets of figures.

A visible approval trail. Who signed the hours off, and when. A query three months later should be answered by pulling a record rather than reconstructing a week from memory.

Output shaped like the payroll fields it feeds. If the payroll or HR administrator has to translate a report into entries, the retyping has only moved one step downstream.

Get those five right and the rules have something consistent to act on. The next question is where those rules themselves drift.

Overtime Bands and Why Hours Drift Between Pay Runs

Those flags only carry weight if the bands behind them are clearly defined.

Overtime is not one rate. It depends on how the band is set in the contract or in agreed practice, and payroll needs the split between standard and premium hours rather than a single weekly total. The classification carries legal weight beyond the pay run too: whether overtime is regular and predictable or exceptional and unforeseeable affects how it is treated in other calculations, as Irish commentary on the Labour Court approach sets out.

Drift appears when the same week is measured differently across two runs: a manual trim here, a rounded half hour there, a shift that straddled the period boundary. Pay period cut-offs compound it. Hours worked after the cut-off belong to the next run, and without a stated boundary the same hours can present as overtime twice.

Re-keying does the most damage. Retyping a weekly total strips out the per-shift detail that band calculations depend on, so the premium lands on a number rather than on the specific hours that earned it.

Payroll-ready data flags overtime at approval, which makes it a decision taken once rather than a calculation repeated every run with a slightly different answer.

Sunday Premiums and Public Holiday Pay: Entitlement vs Calculation

Overtime bands are only one premium with a date problem. Sunday premiums and public holiday pay fail for a different reason: entitlement and calculation get treated as the same question. Entitlement asks what the employee is due. Calculation asks how payroll reaches the figure on the payslip. Mixing them is where disputes start.

The Workplace Relations Commission publishes guidance on public holidays and Sunday premium entitlement. Confirm the current position for the employee’s specific working pattern before the next run rather than carrying last year’s assumption into this one. Section 21 of the Organisation of Working Time Act 1997 sets out the public holiday options available to the employer, but how pay is calculated is a separate payroll step.

Part-time and casual staff are the group where entitlement is most easily misread: s.21(4) of the Organisation of Working Time Act 1997 excludes a non-whole-time employee from the public holiday entitlement unless they worked at least 40 hours in the 5 weeks ending the day before the holiday. Sunday premiums depend on correctly identifying a shift as Sunday work, which breaks down when shifts are recorded by week rather than by date. One approved record applies the same rule to the same day every time. That is the difference between a policy and a habit, and it is the version an inspector or employee query will test.

PRSI, Payslips and the HR Payroll Handoff

Calculation is only as good as the inputs. PRSI and income tax are worked out inside payroll, but what feeds them, hours, gross pay, additions and deductions, comes from time data. Garbage in the hours means corrections out the other side.

Align the Record to the Pay Period

A payslip must reflect the pay period it covers, so the hours record has to follow the payroll calendar rather than the rota calendar. If an employer cannot produce adequate wage records, the burden of proof shifts to them in a Revenue or WRC query; keeping the approved hours record linked to the payslip removes that exposure.

The quieter failure point is the HR to payroll handoff. Leave balances, contract terms and rate changes sit with HR, the hours sit with the manager, and neither sees the full picture. Treat the approved hours record as the single input both HR and payroll point at, so there is one defensible version of the truth. Confirm current PRSI and payroll reporting requirements on Revenue and gov.ie rather than relying on last year’s notes.

That single record is what the next section puts into practice.

One Approved Hours Record: What the Fix Looks Like in Practice

In practice, that single input looks like this: hours are approved once, in one place, then exported into payroll rather than retyped into it. The record is the input, not a rival to your payroll software. Where an existing payroll process already works, the goal is to remove the retyping step and feed it, not replace it.

Exceptions should surface before the run closes, not after. Approvals flag the cases payroll needs to see: a missing clock-in, overtime not yet approved, a public holiday falling on a rostered day, an employee rostered but never clocked in. Each one becomes a decision taken once, with a name and a timestamp attached, instead of a query raised three months later.

Staffly brings scheduling, time tracking, HR and compliance together in one platform and keeps the resulting records payroll ready, without the complexity of traditional workforce software.

The simplest test is this: if an administrator is still typing hours from one screen into another, the handoff has not been fixed. Next, a worked week shows what the approved record looks like when overtime, Sunday work and a public holiday all fall in the same period.

A Worked Example: Overtime, a Sunday and a Public Holiday in One Week

With the approved record in place, the week’s pay becomes a set of traceable lines rather than a calculation. Rates and multipliers should be verified against gov.ie, Revenue or the WRC before any figure is applied; the structure below holds regardless of the current rates.

Take one employee over one pay period containing a standard weekday, a Saturday, a Sunday and a public holiday. The approved record holds one row per shift: employee ID, shift date, day type, start and end time, approval status, approver and a rate-basis reference pointing to the verified rule.

Payroll draws each line from that row. Weekday and Saturday hours flow as standard hours up to the overtime threshold. Hours above the threshold are flagged as overtime. The Sunday shift is identified by its date and flagged for Sunday premium. The public holiday entitlement is drawn from the same dated shift, using the rule verified for that employee’s working pattern. No figure is typed in; each payroll line points back to a dated, approved shift. In short, hours are approved once, in one place, then exported into payroll rather than retyped into it.

The exception log closes the week: missing clock-ins, unapproved overtime, a public holiday on a rostered day, or a rostered employee who never clocked in. Reviewing it before the run is how payroll sees the problem first.

Your Pre-Pay-Run Checklist

Work through this checklist before every run.

• Lock the approved hours for the period before payroll opens. Once the run starts, stop adjusting them; corrections move to the next run or a documented adjustment.
• Check every premium flag against the actual dates worked. Confirm overtime, Sunday, public holiday and any contract shift premiums line up with dated shifts, not weekly totals.
• Reconcile HR payroll data with the hours being paid. Include leave balances, new starters, leavers and any rate changes agreed since the last run.
• Verify current minimum wage and PRSI positions against official Revenue, WRC and gov.ie guidance. This matters especially after the 1 January 2026 minimum wage change, when rates, contracts and records may need review.
• Clear the exception report before the run closes. Missing clock-ins, unapproved overtime and holiday clashes should be resolved by you, not discovered by an employee on payday.

Bringing It Together

Run the checklist once and a pattern tends to emerge: the arithmetic was never the weak point. That transfer risk, approved hours changing value as they move from rota to timesheet to payroll file, was the starting point. The checklist above puts that structure into a repeatable sequence.

Keep HR data, time records and payroll pointed at the same approved record, so overtime bands, Sunday premiums and public holiday pay are applied identically in every period. That single source is what an employee query, a WRC inspection or a Revenue review will test.

Build the checklist into the run itself rather than keeping it beside it, and confirm current rates and rules with Revenue, the WRC and gov.ie before anything changes.

Staffly keeps scheduling, time tracking, HR and compliance in one place, so approved hours arrive payroll ready. If your existing payroll software works, the aim is to feed it from one approved record, not to replace it.

Conclusion

The handoff, not the calculation, is where Irish payroll errors begin. One approved record, exported rather than retyped, is what keeps those calculations consistent and exceptions visible before payday. The next step is simple: build the pre-pay-run checklist into your process and feed payroll from one approved record. Start with your next pay period.