Skip to Content

Malta's 2026 Pay Transparency Rules Are Already Law. Can Your Systems Actually Cope? Your First Report Is Due June 2027

14 September 2026 by
Malta's 2026 Pay Transparency Rules Are Already Law. Can Your Systems Actually Cope? Your First Report Is Due June 2027
Kieran Sant

Most Maltese businesses spent 2026 watching the bigger EU headlines - AI rules, e-invoicing, VAT reform. Meanwhile, a piece of legislation that affects almost every employer on the island came into force quietly, with no warning period and no grace period.

On 5 June 2026, Malta published Legal Notice 173 of 2026 - the Equal Pay (Transparency and Reporting) Regulations, 2026. It took effect immediately. Malta was one of only four EU member states to transpose the EU Pay Transparency Directive by the 7 June 2026 deadline, alongside Italy, Lithuania and Slovakia. Most of Europe, including Germany, France and Spain, missed it.

That's an achievement for Malta. It's also a problem for Maltese employers, because it means there is no "everyone else is behind too" cushion. The obligations are live now, and in several places Malta has gone further than the EU asked.

This article breaks down what the rules actually require, where the real operational risk sits, and what it means for the systems you use to run payroll and HR.

What the regulations do

The Regulations transpose Directive (EU) 2023/970, which strengthens the principle of equal pay for equal work - or work of equal value - between men and women. They apply to employers in both the public and private sectors, and to all workers with an employment relationship under the Employment and Industrial Relations Act (Cap. 452).

Note the scope carefully. This is not a large-company regulation with a size threshold you can sit under. Some obligations scale with headcount, but the core duties apply to everyone.

Two authorities are involved. The Department for Industrial and Employment Relations (DIER) acts as the Monitoring Body, overseeing compliance and reviewing pay gap reports. The National Commission for the Promotion of Equality (NCPE) acts as the Equality Body, supporting workers in enforcing their rights. DIER has already set up a dedicated Pay Transparency portal.

The obligations that apply to every employer


1. Pay structures built on objective criteria

Every employer must have pay structures that allow an assessment of whether workers are in a comparable situation regarding the value of their work. You are still free to pay people differently and to operate pay progression - but it must rest on objective, gender-neutral, bias-free criteria.

The criteria must include skills, effort, responsibility and working conditions, plus soft skills where relevant. Where employee representatives exist, the criteria must be agreed with them.

2. Pay information before hiring and no salary history questions

Job applicants now have the right to be told the initial pay or pay range for the role, based on objective, gender-neutral criteria, along with the relevant provisions of any applicable collective agreement. This must reach them before the recruitment process concludes, so that pay negotiation is informed.

Two hard prohibitions come with it:

  • You cannot ask applicants about their pay history, current or previous.
  • Job vacancy notices and job titles must be gender-neutral, and recruitment must be non-discriminatory.

For many Maltese employers this is the single biggest day-one behavioural change. "What are you on now?" is a normal interview question here. It is now unlawful.

3. Written pay policies, with a tiered exemption

Employers must adopt and maintain written policies setting out the objective, gender-neutral criteria used to determine pay, pay levels and pay progression — accessible to workers at all times.

The size tiers work like this:

  • Fewer than 25 workers: still bound by the underlying equal pay principles.
  • 25 or more workers: must internally document the criteria used to determine pay, pay levels and pay progression.
  • 50 or more workers: full written policy requirements apply, including pay progression.

4. The eight-day clock

This is where Malta went notably beyond the Directive. Workers have the right to request, in writing, information on their own pay level and on average pay levels broken down by sex for categories of workers doing the same work or work of equal value.

You must respond in writing within 8 days. The Directive set a two-month maximum. Malta chose eight days.

And it escalates. If the information is not provided, or is inaccurate or incomplete, within 45 days of the first request, that constitutes an offence and the Director may initiate proceedings.

Alongside this:

  • You must inform all workers annually of their right to request pay information and how to exercise it.
  • You must retain relevant information and data for at least five years.
  • You cannot stop workers disclosing their own pay to the authorities or to employee representatives for enforcement purposes.

Read that again with your current systems in mind. A worker emails on a Monday. By the following Tuesday you need a written breakdown of average pay by sex for everyone doing comparable work. If your payroll lives in a spreadsheet, your job descriptions live in a shared folder, and nobody has ever formally grouped roles into categories of equal value — eight days is not enough time.

Pay gap reporting: who reports, and when

Employers with at least 100 workers must prepare a Pay Gap Report covering seven data points:

  1. The gender pay gap
  2. The gender pay gap in complementary or variable components
  3. The median gender pay gap
  4. The median gender pay gap in complementary or variable components
  5. The proportion of female and male workers receiving complementary or variable components
  6. The proportion of female and male workers in each quartile pay band
  7. The gender pay gap by category of workers, split between ordinary basic wage and complementary or variable components

Deadlines are staggered:

Employer sizeFirst report dueFrequency
250+ workers7 June 2027, covering 1 Jan – 31 Dec 2026Annually
150–249 workers7 June 2027, covering 1 Jan – 31 Dec 2026Every 3 years
100–149 workers7 June 2031, covering 1 Jan – 31 Dec 2030Every 3 years

Employers under 100 workers may report voluntarily.

Here is the part that catches people out. The first report covers calendar year 2026. That year is nearly over. The payroll data you are generating right now - including bonuses, allowances, commissions and every variable component - is already inside the reporting period. You cannot go back and restructure it in May 2027.

Management must confirm the report's accuracy after consulting employee representatives, who must also have access to the methodology used. The report goes to DIER in the format it prescribes. Items 1 to 6 may be published on your website. Item 7, the category-by-category breakdown, must go directly to all workers and their representatives, and to DIER and NCPE on request - including data from the previous four years where available.

The 5% trigger

If your Pay Gap Report shows a difference in average pay between female and male workers of at least 5% in any category, and you cannot justify it on objective, gender-neutral grounds, and you have not remedied it within six months of submitting the report, you must carry out a joint pay assessment with employee representatives.

That assessment is substantial. It covers the proportion of female and male workers per category, average pay and variable components per category, the differences and their reasons, the proportion of workers who received pay improvements after returning from maternity, paternity, parental or carers' leave, the measures you will take, and an evaluation of any previous assessment's effectiveness. It must reach DIER within 10 working days of completion.

The risk nobody budgets for: the burden of proof

Everything above is administrative. This part is financial.

In any non-criminal proceedings where a claimant establishes facts from which discrimination may be presumed, the employer must prove there was no pay discrimination.

More pointedly: where an employer has not implemented the transparency obligations, the employer is obliged to prove the absence of discrimination - unless it can show the breach was manifestly unintentional and minor.

In plain terms, sloppy record-keeping doesn't just risk a fine. It shifts the legal burden onto you in any equal pay claim. Documentation stops being paperwork and becomes your defence.

Claims can be brought within three years of the date the claimant knew or could reasonably have known of the breach, and can be brought even after employment ends. Successful claimants are entitled to full back pay plus compensation covering lost opportunities, non-material damage, and damage from intersectional discrimination.

Criminal penalties run from €2,500 to €5,000, rising to €5,000 to €7,000 where the offence involves a breach of the equal pay principle on grounds of gender and intersectional discrimination. Repeat infringements must attract a more severe punishment within those limits. Victimising a worker for exercising these rights is separately unlawful.

The fines are modest. The back pay, compensation and reputational exposure are not.

Why this is a systems problem, not an HR policy problem

You can write an excellent pay policy in a Word document. It will not help you when a request lands and you have eight days.

What the Regulations actually demand is that pay data be structured, categorised, current and queryable. Specifically:

  • Every worker mapped to a category of work of equal value, using consistent criteria
  • Pay split cleanly between ordinary basic wage and complementary or variable components - bonuses, commission, allowances, benefits in kind
  • Gender recorded as a reportable field, not buried in a personnel file
  • Median as well as mean calculations, and quartile pay bands
  • The pay-setting and progression criteria documented and linked to actual decisions
  • Everything retained for five years, with an audit trail
  • Access controlled, because pay data that could identify an individual may only go to representatives, NCPE and DIER - and all of this sits under GDPR

Spreadsheets fail on nearly every one of these. Not because the numbers are wrong, but because the structure isn't there. Categories drift. Bonuses get lumped into one column. Nobody can reproduce last year's figures. And there is no audit trail to show a tribunal.

Where Odoo fits

Odoo won't make you compliant on its own - no software will, and anyone claiming otherwise is selling you something. What it does is put the underlying data into a shape where compliance becomes a reporting exercise rather than a fire drill.

Employees and contracts as one source of truth. Odoo's Employees app holds contracts, salary structures, job positions, departments and employment history in structured fields rather than documents. Salary structures let you separate basic wage from variable components at the point of calculation, so the split the Regulations require already exists in your data.

Job categorisation you can defend. Job positions and skill records let you group roles into categories consistently, and apply the same criteria across the organisation. When DIER or a tribunal asks how you determined that two roles are of equal value, you have a system-recorded answer rather than a recollection.

Recruitment that follows the new rules. The Recruitment app is where the pre-employment obligations get enforced in practice: pay ranges attached to the job position itself, gender-neutral vacancy templates, and critically, application forms with the salary history question removed. If nobody can ask it, nobody accidentally asks it.

Documented progression. The Appraisals app links performance and competence assessments to individuals over time. Since pay progression must rest on objective criteria, having those assessments recorded in the same system as the pay decisions is what turns a policy into evidence.

Policies workers can actually access. The Regulations require written pay policies to be accessible at all times. Odoo's Knowledge and Documents apps give you a controlled, versioned place to publish them, rather than a folder people have to ask for.

Reporting without a rebuild. Because the data sits in structured fields, Odoo's built-in pivot and list reporting can produce breakdowns by gender, category, quartile and pay component, mean and median,without exporting to Excel and rebuilding the calculation each time. That's the difference between an eight-day response and an eight-day panic.

Access control and retention. Odoo's user groups and record rules let you restrict who sees identifiable pay data, which matters both for the Regulations' confidentiality provisions and for GDPR. Records persist with their history intact, which supports the five-year retention requirement.

One honest caveat: Odoo's Payroll app relies on country-specific localisation modules, and Maltese payroll rules, FSS, NI, statutory bonuses, typically need to be configured by an implementation partner rather than switched on out of the box. That's exactly the kind of work we do, and it's worth scoping properly rather than assuming.

What to do in the next 90 days

  1. Stop asking about salary history today. Pull it from your application forms, interview scripts and screening calls. This is the fastest thing to fix and the easiest to get caught on.
  2. Audit your vacancy notices for gender-neutral language and add pay ranges.
  3. Count your workers properly. Your headcount determines which tier you sit in. If you are near 100, 150 or 250, know exactly where you stand.
  4. Check whether you can produce the seven data points for 2026. If you are at 150+, do a dry run now on the year to date. Whatever breaks in the dry run is what you have a few months to fix.
  5. Write down your pay-setting and progression criteria if you have 25 or more workers, and publish them properly if you have 50 or more.
  6. Set up an eight-day response process with a named owner, a template, and a defined source for the numbers.
  7. Set your annual notification to workers about their right to request pay information - calendar it now so it doesn't get missed.

The honest summary

Malta moved faster than almost every other EU member state, and it applied tighter deadlines than the Directive required. Employers here have less time to respond to requests than employers anywhere else in Europe, no transitional period, and a reporting period that is already most of the way through.

The businesses that will handle this well are the ones whose pay data is already structured. The ones that struggle will be those discovering, on day six of an eight-day clock, that the numbers exist in four different places and don't reconcile.

If you're not sure which one you are, the dry run in point 4 will tell you within an afternoon.

Centric Malta is an Odoo implementation partner based in Birkirkara. If you'd like to talk through how your HR and payroll data is structured, and what it would take to get reporting-ready, get in touch.

This article is general information, not legal advice. The obligations under Legal Notice 173 of 2026 depend on your specific circumstances, and employers should take professional legal advice on how they apply.

Helpful resources

Primary legislation

Maltese authorities

Legal analysis from Maltese firms

EU-wide context

Odoo documentation

Digitalise Your SME Malta 2026: A Simple Guide to the Grant, the Deadlines and What You Can Claim