The pay report due next June is already being written, one payslip at a time.

An implementation checklist.

1. 1.Write down what your organisation counts as pay, component by component. Article 3(1)(a) reaches any consideration in cash or in kind, and recital 21 names bonuses, overtime compensation, travel facilities, housing and food allowances, payments for attending training, dismissal payments, statutory sick pay and occupational pensions. Make the list explicit, name the system each component lives in, and record the ones you have decided to exclude along with why. That single page settles most of the arguments that would otherwise surface a week before the report is due.
2. 2.Give every worker an hours basis. Article 3(1)(b) asks for gross annual pay and the corresponding gross hourly pay. Hourly paid staff are easy. Salaried staff are where this breaks, because most payroll systems hold a contract percentage or a full time equivalent rather than hours, and a part time salaried worker compared on annual pay alone will look underpaid for reasons that have nothing to do with sex. Recital 22 lets you base the calculation on the pay actually specified for the worker, so record the basis you used and apply it consistently.
3. 3.Build categories of workers as a real object, not a spreadsheet. Article 3(1)(h) asks for groupings that are non-arbitrary and built on the criteria in Article 4(4), which are skills, effort, responsibility and working conditions. Job title is not that. Grade is closer but usually reflects history. Give each category its criteria, its version, the date it was agreed and, where representatives were involved, who agreed it. The category drives the 5 percent trigger, so it is the most consequential field in the whole exercise.
4. 4.Check whether your pay conditions come from a single source across entities. Article 19(1) says comparison is not limited to workers of the same employer but extends to a single source establishing the pay conditions. A group reward policy or a collective agreement covering several legal entities can be that source. Groups that run one HRIS instance per country often cannot answer this at all, and it is better to find out now than during a claim.
5. 5.Keep a retained snapshot of each reference year. Article 9(9) requires the category level figure to be provided on request together with the previous four years where available. A live query against current data cannot answer for 2026 once 2027 has overwritten it. Snapshot the worker population, the categories, the components and the derived figures at the point the report is confirmed, and keep them together.
6. 6.Decide in advance how a gap gets justified, and what evidence supports it. Article 10 only requires a joint pay assessment where a gap of at least 5 percent in a category is unjustified on objective gender-neutral criteria and unremedied six months after submission. That gives you two routes out, and both need preparation. A justification asserted in a meeting is worth less than one recorded against the category, with the underlying analysis attached, at the time the figure was produced.
7. 7.Join leave records to pay change history. Article 10(2)(e) asks, inside a joint pay assessment, for the proportion of women and men who received any pay improvement on returning from maternity, paternity, parental or carers leave, where such improvement occurred in that category during the leave. Leave sits in absence management and pay changes sit in payroll, and the two are rarely queried together. It is a small join that is awkward to make under time pressure.
8. 8.Make the individual request answerable on demand. Article 7 gives every worker, at any employer of any size, the right to their own pay level and the average pay levels by sex for their category, with a two month deadline and an annual reminder that the right exists. Treat it as a service with a defined output rather than an ad hoc analysis, and the same computation serves both the request and the report.
9. 9.Connect the pay range on a job advert to the structure underneath. Article 5 requires applicants to get the initial pay or its range based on objective gender-neutral criteria. A range invented by a hiring manager and a range derived from the category structure look identical in a job posting and behave very differently when someone asks how the two relate.
10. 10.Run one exception query every quarter while the reference year is open. Workers with no category, categories with no recorded criteria, pay components in systems the report does not read, salaried workers with no hours basis, and gaps above the threshold with no justification recorded are the gaps that matter. Finding them in March is administration. Finding them in May 2027 is an escalation.

Failure modes, framed so you can plan around them.

• Treating this as a reporting project rather than a data project. The seven figures in Article 9(1) are ordinary arithmetic, and a competent analyst can produce them in an afternoon once the inputs exist. The work is entirely in the inputs: a definition of pay that reaches across four systems, a pay level that needs hours for salaried staff, and a set of categories that has to be defensible. A project plan that starts at the calculation has skipped the part that takes the time.
• Assuming payroll holds pay. It holds most of the cash. The employer contribution to an occupational pension usually sits with the provider, a company car sits with fleet or benefits, and a housing or food allowance may be administered locally and never appear as a wage type. Recital 21 names all of those as complementary or variable components. A gap calculated on payroll alone is a gap in something narrower than what the Directive calls pay, and the second figure in Article 9(1) is specifically the gap in those components.
• Letting job title stand in for category of workers. It is the most available field and the least suitable one. Titles proliferate, drift, and often reflect seniority signalling rather than the value of work. Article 3(1)(h) asks for groupings that are non-arbitrary and based on the Article 4(4) criteria, and Article 4(4) adds that soft skills are not to be undervalued, which is a direct instruction to look again at roles that have historically been graded low. Categories built on titles tend to produce many small groups, which hides gaps rather than explaining them.
• Cutting categories until the gaps disappear. The temptation is real and the design of the Directive anticipates it. Groupings must be non-arbitrary, the criteria are named, representatives are involved where national law provides for it, and under Article 9(6) representatives get access to the methodology. Fine slicing is visible to everyone who looks, and it converts a manageable conversation about one category into a question about good faith.
• Waiting for your member state to transpose. Most missed the 7 June 2026 deadline, and the tracker position immediately after the date was that only Slovakia, Italy, Lithuania and Malta had transposed in full, with Belgium, Ireland and Poland partial. That produces a genuine timing question, because a late transposition may move a national reference year, as the Dutch proposal to start with the 2027 calendar year illustrates. What it does not change is the content of Article 9(1), which is a common minimum across all 27. The data model is the same whichever date applies, and the reference year in the Directive is the one now running.
• Producing a number nobody can reproduce. Article 9(6) requires management to confirm accuracy after consulting workers representatives, who get access to the methodologies. A figure that depends on one analyst, one workbook and a set of undocumented judgement calls meets the letter of that for exactly as long as the analyst stays. Treat the calculation as a pipeline with recorded inputs, recorded choices and a rerunnable result.
• Forgetting that Articles 5, 6 and 7 carry no size threshold. The reporting thresholds in Article 9 are the part everyone quotes, so smaller employers often read themselves out of the whole Directive. The pay range for applicants, the ban on asking about pay history, the published criteria for pay and pay progression, and the individual right to ask apply regardless of size, with only a narrow option for member states to exempt employers under 50 workers from the pay progression element.
• Underrating what Article 18(2) does. Where the transparency obligations in Articles 5, 6, 7, 9 and 10 have not been implemented, the burden of proof shifts to the employer to show there was no discrimination, with a narrow exception for infringements that are manifestly unintentional and minor. Combined with limitation periods of at least three years under Article 21, compensation with no upper limit under Article 16, and the exclusion ground for public contracts in Article 24(2), the data work stops being a compliance cost and becomes the record you would want to have.
• Leaving benefits in kind valued at zero. A component that nobody has valued tends to enter the calculation as nothing, which quietly removes it from both the pay gap and the variable component gap. Where a car, subsidised accommodation or a meal allowance is genuinely part of pay, it needs a value and a basis for that value, recorded once and applied consistently rather than argued each cycle.
• Designing for one country. Thresholds, reference years, the counting basis for workers and the role of representatives are all shaped by national transposition, and those will keep diverging. The seven figures, the definition of pay, the pay level and the category concept come from the Directive and are common. Build the common part once and treat the national differences as a calendar and a parameter set, rather than building a separate answer per country and reconciling them later.

What this asks of the data model.

• Pay is a union, not a column. Each component carries its own type, amount, period and source system, so the figures can be produced at two levels: total pay, and the complementary or variable part that Article 9(1) asks about separately. A single blended number cannot answer both.
• Every worker carries a category and every category carries its reasoning. The criteria in Article 4(4), the version, the date agreed and the parties who agreed it belong on the category itself. Since the 5 percent trigger in Article 10 operates per category, a change to categories changes who is in scope for a joint pay assessment, which makes it a controlled change rather than a refresh.
• An hours basis is a field, not a derivation done at report time. Gross hourly pay is required for every worker, and for salaried staff the basis has to come from somewhere. Record it against the worker, along with how it was determined, so the same answer is produced every cycle and can be explained.
• The worker population is wider than core payroll. Recital 18 brings part time, fixed term and agency workers into scope, along with management, and, where they meet the criteria, on demand workers, platform workers, trainees and apprentices. Several of those are commonly held outside the main payroll system, and the counting basis for thresholds is a matter for national law.
• Quartile bands are computed across the whole employer, not within a category. Article 9(1)(f) asks for the proportion of women and men in each of four equal groups ranked by pay level, which needs one comparable pay level per worker across the entire population before any grouping is applied.
• Leave and pay changes need to be queryable together. The joint pay assessment content in Article 10(2)(e) reaches the proportion of women and men who received a pay improvement on returning from family related leave. That is a join between absence management and pay change history, and it is easier to build while both are current.
• Justifications are data with evidence attached. A gap justified on objective gender-neutral criteria is a recorded decision against a category, with the analysis behind it and a date. Held that way, the six month window in Article 10(1)(c) becomes a tracked clock rather than something to reconstruct.
• Snapshots are the deliverable, not the live table. Article 9(9) reaches back four years on request. Retain the population, the categories, the components, the derived figures and the methodology together for each reference year, so an answer given in 2030 about 2026 rests on what was actually reported.
• Personal data limits are part of the design. Article 12 requires this processing to follow the General Data Protection Regulation, forbids using the data for any purpose other than applying the principle of equal pay, and lets member states restrict access where disclosure would reveal an identifiable worker pay. Small categories are where that bites, and the aggregation rules belong in the pipeline rather than in a reviewer judgement at the end.

The evidence to keep.

• The pay definition, stating component by component what the organisation treats as pay under Article 3(1)(a), which system each component comes from, how components in kind are valued, and what was excluded together with the reasoning.
• The category register, showing each category of workers, the Article 4(4) criteria it rests on, its version history, the date each version was agreed, and where applicable the workers representatives who took part.
• The population extract for the reference year, showing every worker in scope, the category assigned, the contract type, the hours basis used and the source of each pay component, which is the starting point for any test of the published figures.
• The calculation record, showing how each of the seven figures in Article 9(1) was derived from that population, including the quartile ranking, so that the result can be reproduced by someone who did not build it.
• The confirmation trail required by Article 9(6), showing that management confirmed accuracy, when workers representatives were consulted, and that the methodology was made available to them.
• The justification file for any category at or above the 5 percent threshold, recording the objective gender-neutral criteria relied on, the analysis supporting them, and the date, or alternatively the remediation taken within the six month window.
• The joint pay assessment itself where one was triggered, covering the Article 10(2) contents including the pay improvement proportion following family related leave and the evaluation of measures from earlier assessments.
• The Article 7 request log, showing each worker request, the date received, the date answered against the two month deadline, and the figures provided, together with evidence of the annual notice that the right exists.
• The retained snapshots for each reference year, held so that the four year look back in Article 9(9) is answered from what was reported rather than from what the current systems now hold.

Questions worth asking in your own review.

• Can we list today, component by component, everything our organisation would treat as pay under Article 3(1)(a), and name the system each part lives in?
• For a salaried part time worker, can we produce a gross hourly pay figure without someone deciding on the spot what the hours are?
• What are our categories of workers, who agreed them, and could we show the skills, effort, responsibility and working conditions behind any one of them?
• Does the employer contribution to occupational pensions reach our pay gap calculation, and if not, what else is missing with it?
• If a worker asked tomorrow for the average pay levels by sex in their category, how long would the answer take, and would the next worker get the same method?
• Do our pay conditions come from a single source that spans more than one legal entity, and if so, does our reporting reflect that?
• If a category showed a gap above 5 percent, where would the justification be recorded, and what evidence would sit with it?
• Can we reproduce a figure from a prior reference year from a retained snapshot, or would we have to rebuild it from current data?
• Which national timetable applies to each of our European entities, and who is tracking the ones that are still moving?
• Who owns this end to end: payroll, reward, HR systems, finance, or nobody in particular?

What this adds up to.

The compliance question is narrow and well defined. Seven figures, a set of thresholds, a reporting date of 7 June 2027 for the larger employers, and a joint pay assessment where a category shows an unjustified gap of at least 5 percent that is still there six months later. None of that is hard to understand, and a good analyst can compute all of it once the inputs exist.

The operating question is the more interesting one, and it outlasts the reporting cycle. An employer that can state, for any worker, what they were paid in total, which part of that was variable, what hours it corresponds to and which group of comparable work they sit in has built something that answers a great deal more than a Directive. It can price a role before advertising it. It can answer an individual question in days rather than weeks, which is usually the difference between a conversation and a complaint. It can tell whether a gap comes from pay decisions inside a group or from the shape of the group itself, which are different problems with different fixes. And it can show its method to the people affected, which is what Article 9(6) asks for and what makes the number credible regardless of what it says.

If there is one place to start this month, it is the list of pay components and the systems they live in. Write it down, name an owner for each, and mark the ones your current gender pay calculation does not read. That page takes an afternoon and it usually surprises people, because the components most often missing are the employer pension contribution and anything in kind, and those are exactly the ones Article 9(1) asks about separately. Everything else in this article is built on top of that list. The reference year is still open, which is a rare position to be in when a reporting deadline is already fixed.

Sources.

• Directive (EU) 2023/970 of the European Parliament and of the Council of 10 May 2023 to strengthen the application of the principle of equal pay for equal work or work of equal value between men and women through pay transparency and enforcement mechanisms. Downloaded and read directly, article by article, rather than through a summary. Source for every requirement described here: the definitions of pay, pay level, gender pay gap, median pay level, median gender pay gap, quartile pay band and category of workers in Article 3(1); the pay structure and job evaluation criteria in Article 4; pay transparency before employment in Article 5; the pay setting and pay progression criteria in Article 6; the right to information and the two month response period in Article 7; the seven reporting items and the employer size thresholds and dates in Article 9; the joint pay assessment trigger and contents in Article 10; the data protection limits in Article 12; the shift of the burden of proof in Article 18; the single source comparison in Article 19; the limitation periods in Article 21; penalties in Article 23; public contracts in Article 24; and the transposition date of 7 June 2026 in Article 34.
• Recital 21 of the same Directive, read directly. Source for what counts as a complementary or variable component of pay: any benefit in addition to the ordinary basic or minimum wage or salary that the worker receives directly or indirectly, in cash or in kind, with a non-exhaustive list naming bonuses, overtime compensation, travel facilities, housing and food allowances, compensation for attending training, payments in the case of dismissal, statutory sick pay, statutory required compensation and occupational pensions. Recital 22 is the source for the point that pay levels are expressed as gross annual pay and the corresponding gross hourly pay, and that the calculation may be based on the actual pay specified for the worker whether it is set annually, monthly, hourly or otherwise. Recital 18 is the source for the breadth of the worker population, which includes part time workers, fixed term workers, agency workers, workers in management positions and, where they meet the relevant criteria, on demand workers, platform workers, trainees and apprentices.
• European Commission, EU action for equal pay. Background on the Commission position that following the transposition deadline of 7 June 2026, attention turns to assessing whether national legislation conforms to the Directive, and on the two obligations most visible to workers, namely that employers may not ask job seekers about pay history and must provide pay related anonymised data on request.
• Ogletree Deakins, European Commission Confirms the EU Pay Transparency Directive Implementation Deadline Remains 7 June 2026. Source for the point that the Commission declined to postpone the deadline despite requests, which matters because it removed the main argument for waiting.
• DCI Consulting, The Transposition Deadline Has Passed And Most Member States Missed It. A practitioner tracker, used here only for transposition status and national timetables, not for anything normative. Source for the position immediately after 7 June 2026: four member states transposed in time, namely Slovakia, Italy, Lithuania and Malta; Belgium, Ireland and Poland were partially implemented; ten had published drafts and missed the date; and ten had published no draft. Also the source for several national timetables cited here, including the Netherlands targeting 1 January 2027 and Czechia targeting the same date with pay gap reporting later.
• Littler, European Pay Transparency Directive: Implementation Challenges, Status, and Risks. Background on national divergence, and the source for the point that the Dutch reporting obligation for employers with 150 or more employees was proposed to apply first to the 2027 calendar year rather than 2026, which is the clearest published example of a national reference year differing from the one the Directive sets.
• L and E Global, Pay Transparency Directive: Europe Nears the Deadline, but Most Member States are Not Ready, May 2026. Background on the state of readiness across member states shortly before the transposition date, used as corroboration of the tracker position rather than as a primary source.

Every requirement described here was read directly from the text of Directive (EU) 2023/970 and its recitals, downloaded and read article by article rather than through a summary. That covers the definitions in Article 3, the job evaluation criteria in Article 4, the obligations before employment and on pay setting in Articles 5 and 6, the right to information in Article 7, the seven reported items and the thresholds and dates in Article 9, the joint pay assessment in Article 10, the data protection limits in Article 12, the burden of proof in Article 18, the single source comparison in Article 19, limitation periods in Article 21, penalties in Article 23, public contracts in Article 24 and the transposition date in Article 34. Transposition status and national timetables are the one area drawn from secondary sources, namely practitioner trackers published around the deadline, and they are attributed as such in the text because national law is moving and any position stated here is a snapshot. The names, amounts and dates in the worked record are placeholders for shape rather than real values, and the figures in it are not a benchmark of any kind. No embedded posts from X appear here, because no public post on this topic could be verified as current, relevant and authentic at the time of writing, and an unverified embed is worse than none. Nothing here is legal, tax or employment advice for a specific organisation, and the obligations that actually apply to any employer come from its member state transposition rather than from the Directive alone.