The Daily Rate Trap in Mid-Month Proration and Arrears

Mid-month contract amendments are a constant in any enterprise: an off-cycle promotion, a change in hours, a new hire starting a few days after the first. The payroll engine has to split the month between two contracts. The question is how.

Standard Irish payroll training, including the iPass syllabus, teaches the 260.9 divisor: annual salary divided by 260.9 (52.18 weeks × 5 days) gives a fixed daily rate. iPass is right about that. For ad-hoc items such as two days of unpaid leave or cashing out untaken holidays on termination, the daily rate is exactly the tool to use.

The trouble starts when the same tool is applied to core salary proration and arrears. A salaried employee's contract guarantees 1/12th of annual pay each month. A fixed daily rate ignores that guarantee and converts the employee, for one month, into a day-rate worker. Because months vary between 20 and 23 working days, the result lands above or below the contractual amount depending on the calendar, not on anything the employee did.

All examples use a EUR 75,000 salary (EUR 6,250 per month, daily rate EUR 287.47) and, where relevant, a promotion to EUR 78,000 (EUR 6,500 per month, daily rate EUR 298.97).

Row 1 is the budget leak. The employee could not have earned more than EUR 6,500 had they worked the whole month on the higher contract, yet the daily rate pays EUR 6,646.31. If 10 per cent of a 1,000-person workforce has a mid-month split in a long month over the course of a year, roughly EUR 15,000 leaves the payroll budget for no reason other than calendar friction, and nobody sees it, because every individual payslip looks plausible.

Rows 2 and 3 show the same joiner in a long month and a short month. In the 23-day month they out-earn a colleague who worked every day; in the 20-day month they are docked EUR 475.57 for missing one. The method is not biased in one direction; it is biased in both, which is what makes it indefensible to the person reading the payslip.

Row 4 is the one that generates complaints. A promotion backdated into a 20-day month, processed in the following cycle, is revalued by the daily rate at EUR 5,864.40. The employee was already paid EUR 6,250, so the arrears run deduct EUR 385.60 from the person who has just been promoted. Technically, the engine did what it was told. Practically, HR now has a grievance.

"It averages out over the year." In aggregate, over- and underpayments across long and short months do largely net off. That is irrelevant. A contract of employment and the Payment of Wages Act 1991 operate per payslip: an underpayment in March is a deduction in March, not a timing difference against an overpayment in May. The real case against the daily rate is per-payslip inaccuracy and inequity, not net budget loss.

"Calendar-day proration is simpler." Dividing by days in the month (28 to 31) also stays within the 1/12th bound, so it avoids the overpayment and clawback problems. It misaligns, however, with how absence, leave and working patterns are actually recorded, which is in working days. A joiner starting on a Monday is prorated for the weekend they could not have worked. Working-day apportionment matches the rest of the payroll's own arithmetic.

"What about part-time staff and public holidays?" The method holds provided the working-day count is the employee's own contracted pattern, not a generic Monday-to-Friday week, and provided public holidays are treated consistently (for salaried staff, as paid working days). Define this once, and the same formula handles full-time, part-time, joiners, leavers and backdated changes.

Period apportionment starts from the true monthly salary (1/12th of annual pay) and slices it by the actual working days in that specific calendar month. For each contract active in the month: monthly salary × days worked on that contract ÷ working days in the month. The sum is always bounded between the lowest and highest monthly salary in force, so a pay rise cannot produce negative arrears, a joiner cannot out-earn a full-month colleague, and no employee is docked for a short month.

In most ERP and HRIS platforms, the fix is configuration rather than code. The basic salary element needs a proration rule attached to it, driven by the effective dates on the contract record, and the retroactive-pay process must call that same rule when it rebuilds a prior period. The dual-method trap almost always arises when the live run uses one rule, and retro uses another, or when a legacy daily-rate formula was hard-coded into a custom element years ago, and nobody has looked at it since. Payroll teams can run the following check against their last three retro cycles without any help from IT:

1. Did any arrears run produce a negative amount for an employee whose pay went up?
2. Did any joiner's or leaver's first or last payslip exceed their monthly salary?
3. Does the proration rule on the salary element match the rule used by the retro process?
4. Are public holidays counted as working days in the proration divisor?
5. Do joiners and leavers use the same proration formula?

A single yes to question 1 or 2 means the daily rate is being used where it should not be.

Under the Payment of Wages Act 1991, a deduction from wages that is not authorised by statute, contract or the employee's written consent is unlawful, and an underpayment is treated as a deduction. A negative arrears entry caused by a proration formula is exactly that: a deduction the employee never agreed to, arising from a method the contract never mentioned. Period apportionment keeps every payslip within the annual contractual limit, which is the only defensible position if a payslip is ever queried before the Workplace Relations Commission.

Fixed daily divisors are the right tool for unpaid leave and holiday cash-outs. Mixed into core salary proration and arrears, they cut both ways: phantom overpayments the employer never sees and clawbacks the employee never forgets. Unifying the payroll engine around period apportionment for mid-month contract changes protects the budget, keeps every payslip within its contractual limit and removes a predictable source of grievances.

About the author

Muhammad Usama Imran is Chief Systems Architect at Numla, where he designs and audits enterprise payroll and HR systems for clients in Ireland and the UK.