Most Irish employers assume their HR data is good enough to underpin pay transparency compliance. Most are wrong. The problem is not their payroll system — it is the absence of a coherent job architecture underneath it.
The conversation about EU Pay Transparency Directive compliance in Ireland has focused heavily on data. What pay data do we have? Where does it live? How do we report it? Those are necessary questions. They are not the first questions.
The first question is whether the organisation has a job architecture that can support meaningful pay analysis at all. Most Irish employers, when they look closely, find they do not. The problem is not the payroll system. It is the layer beneath it that has never been properly built.
What job architecture is and why it matters for pay transparency
Job architecture is the structured framework that organises roles in an organisation by function, level, and relative value. It defines how jobs map to grades, what criteria differentiate levels within a function, and how roles across different functions compare to each other in terms of skill, complexity, and responsibility.
The EU Pay Transparency Directive introduces the concept of "work of equal value." This is not a technical term with a fixed definition. The Directive deliberately leaves the methodology for assessing equal value to employers. What that means in practice is that each organisation must develop, document, and defend its own gender-neutral job evaluation methodology.
Without a job architecture, there is no basis for that methodology. You cannot assess whether a warehouse supervisor's role is of equal value to an accounts payable supervisor's role unless you have a consistent framework for evaluating both against the same criteria. Organisations that have grown by acquisition, that have used informal titling conventions, or that have promoted people into bespoke roles without formal grade alignment will find this gap particularly acute.
The specific gaps most Irish organisations carry
The most common structural problems are accumulated rather than designed. Over years of hiring decisions, reorganisations, and promotions, most organisations end up with:
Job titles that do not map consistently to seniority levels. A "Senior Manager" in one business unit may be a direct report to a Director. In another, three layers of Senior Managers may sit below a single Director. The title carries different weight in different parts of the organisation, and that inconsistency makes pay comparison meaningless without first resolving it.
Grades that have drifted. Formal grade structures exist in most larger Irish organisations, but the actual relationship between a person's grade and their job content has often become loose. Retention adjustments, off-cycle increases, and market corrections have been applied at the individual level rather than through structured grade reviews, creating a population of people whose grade no longer accurately reflects their role.
Missing or inconsistent job descriptions. The Directive requires employers to demonstrate that pay differentials are based on objective, gender-neutral criteria. That demonstration is only possible if the role requirements are documented. In many Irish organisations, job descriptions were written during hiring and have not been updated since. Others were never written at all.
Benefits data that is not consolidated. The Directive's definition of pay covers bonuses, pensions, share options, car allowances, healthcare, and benefits in kind. In most Irish organisations, this data sits across multiple systems: payroll, pension administration, fleet management, benefits platforms. No single view exists. Constructing one for compliance purposes requires a data audit that has not been done.
Why the HRIS is not the answer
A common response to pay transparency preparation is to look to the HRIS. The logic is: our HR data lives there, our pay data lives there, surely we can extract what we need.
The HRIS is only as good as the data put into it. If job titles are inconsistent, they are inconsistent in the HRIS. If grade assignments have drifted, those drifted grades are what the system holds. If job descriptions were last updated in 2019, that is the documentation the system reflects.
Reporting capability in a modern HRIS is real and useful. But reporting on top of poor structure does not produce reliable analysis. It produces numbers that look like analysis but cannot be defended under scrutiny. The Directive shifts the burden of proof to the employer. An employer whose pay analysis rests on an unreliable job architecture is in a worse position than one who has not yet run the numbers, because they have a false sense of what they know.
The remediation sequence matters: fix the architecture, then clean the data, then run the analysis. Running the analysis first leads to rework. In a compliance context where the window is already tight, rework is expensive.
The equal value problem is not solved by technology alone
Several AI-powered tools now offer job description clustering, grade mapping, and pay equity analysis. Some of them are genuinely useful for the analytical phase of this work. None of them resolve the foundational problem if the job architecture does not exist.
A tool that maps job descriptions to a grade framework needs job descriptions to work with. A tool that clusters roles by equal value needs roles that are sufficiently documented to cluster meaningfully. A regression analysis that controls for seniority, performance, and tenure needs clean grade data to define seniority in the first place.
The tools accelerate the work once the foundations are in place. They cannot substitute for foundations that are not there.
Preparation for the EU Pay Transparency Directive typically takes eight to twelve months, according to PwC and the Maples Group. That timeline reflects the reality that building a job architecture, auditing pay data, and developing a defensible equal-value methodology takes time even when organisations move with focus and resource. Only 6% of Irish employers in a recent Mercer survey considered themselves fully prepared. The gap between that figure and readiness is, in most cases, a gap in foundations, not a gap in reporting tools.
Where to start
The starting point is an honest assessment of what currently exists. Map the job architecture as it is, not as it should be. Identify where grade assignment has drifted from role content. Audit the data landscape across all the systems that hold pay data in the broad sense the Directive uses. Document what is defensible and what is not.
That assessment takes weeks, not months. The output is a clear picture of the gap between current state and what compliance requires, prioritised by risk and ordered by the sequence in which the work needs to happen.
Without that picture, organisations run the risk of investing in remediation that addresses the wrong problem, or analytical work that cannot be used because the architecture beneath it is not solid.
Acuity AI Advisory helps Irish organisations map their current pay architecture and identify the gaps before they become legal exposure. If you want to understand where you stand before commissioning remediation work, get in touch.