Compliance used to mean filing on time, calculating correctly, and staying current on local rates. Those requirements haven’t gone away, but they’re no longer the test that decides whether a company is actually compliant.
The real test is whether someone can answer a question: a regulator asking how a pay decision was made, an employee asking why two people doing equivalent work are paid differently, an auditor asking what criteria sit behind a compensation band.
If producing that answer takes days of digging through spreadsheets, emailing vendors, and tracking down whoever made the original call, payroll compliance is the risk.
This expectation is spreading across jurisdictions, and the EU Pay Transparency Directive is the clearest, most structured example so far. Under Article 7, any worker in an EU jurisdiction can request a written breakdown of their pay against colleagues doing equal-value work, with no headcount threshold and a two-month deadline to respond. Miss that window, and discrimination is presumed.
This guide covers what that means in practice: a checklist for building pay processes that hold up, where the infrastructure usually breaks first, and what needs to be in place before anyone asks.
What is payroll compliance?
Payroll compliance covers the operational basics: accurate tax withholding, pension and benefit contributions, statutory payments, employment contracts, and record-keeping in every jurisdiction where a company employs people.
Increasingly, payroll compliance covers something else too: the ability to reconstruct and defend a pay decision after the fact, for a regulator, an auditor, or the employee themselves.
Even when pay is calculated correctly and filed on time, what’s missing is a record of why:
- Why this person sits in this band
- Why their increase was 4% rather than 6%
- Why two people doing equivalent work earn what they earn
When someone asks, there’s no system to reconstruct that decision, just whoever made the call at the time, assuming they still work there.
Amanda Frayne, Chief Legal and Compliance Officer at Multiplier, sees this pattern across the companies Multiplier works with: “Where teams are generally failing at the moment, they’re treating this as a disclosure problem or a legal problem instead of a data HR model problem.”
That distinction matters because, under the EU Pay Transparency Directive, workers don’t need to file a complaint or trigger an audit to create an obligation.
Say an employee submits a written request on a Tuesday morning. Within two months, the employer must produce structured, defensible pay data covering every compensation element, broken down by sex, mapped to a defined comparator group. If the infrastructure to support that response doesn’t exist, the compliance failure is immediate.
If you hire in the EU, each new hire adds a potential future Article 7 request, so getting payroll right is no longer enough on its own. Employers now need infrastructure that can justify how pay decisions were made, to whom, and on what basis: under Article 7 in the EU, and increasingly wherever a regulator, auditor, or employee asks the same question.
At scale, this becomes an even more complex issue. Around 37% of companies name compliance complexity as the single biggest source of friction in global hiring, according to Multiplier’s Global Hiring Gap report, unsurprisingly, as each new market adds a new ruleset.
Payroll compliance checklist for global teams
Running compliant payroll across borders takes more than software.
Step 1: Treat labor laws as a moving target
Employment laws, tax obligations, minimum wage requirements, mandatory benefits, termination rules, and notice periods vary by jurisdiction, and in some countries by region or sector.
Confirming the applicable law for each employee’s country of residence isn’t a task to complete before the first payroll run and then file away. It needs checking on an ongoing basis, because the rules underneath it keep moving.
For EU employees, this now includes tracking each member state’s transposition of the Pay Transparency Directive, and those transpositions are moving at very different speeds.
Slovakia is a useful example of how fast this can happen. The country passed its Equal Pay Act on 15 April 2025, which fixed clarification response windows at 30 days, introduced a hard annual reporting deadline of 15 April, and requires fully compliant pay structures by 31 July 2026.
A company that built its compliance calendar around the EU-wide transposition deadline of 7 June 2026 and stopped there would already have missed Slovakia’s.
Amanda is direct about what this means for companies operating across several EU states: “If you’ve got multi-jurisdictional across Europe, you’re going to have to look at every single member state, how they’re transposing it into their local national legislation. It’s unfortunately not one-size-fits-all.”
And the fact that other member states haven’t transposed the directive yet isn’t a reason to wait. As Amanda puts it: “Don’t use that as an excuse. They should be getting ready now.”
The same logic applies to notification, not just calculation. Article 7(3) requires EU employers to tell every worker, every year, that they have the right to request pay information. This obligation repeats annually, starting from the moment national law takes effect and continuing afterward. Amanda flags this as a common trap: “It’s not a case of ‘you must say on day one of transposition this is your right’ — a lot of employers are going to do that. But it’s an annual requirement moving forward.”
Step 2: Build payroll records that pass the “show me” test
Payroll records need to be retained in a format that can be audited and retrieved under pressure. Under GDPR, EU employers must manage payroll data in line with data protection obligations. Under the Pay Transparency Directive, those same records become the evidence base for responding to pay comparison requests.
Amanda is specific about what defensibility requires: “If you can’t reproduce the logic, it’s not defensible.” She frames it as a standing test for any pay decision: “You’ve gotta have what I call the ‘show me’ test. Pay transparency is the ability to justify pay decisions with objective criteria and evidence that there’s no discrimination.”
That means keeping a clear audit trail of job classification, pay band, criteria used, and decision rationale, in a form that can be reconstructed on demand rather than pieced together from memory.
For instance, in Germany, payroll records must be retained for up to ten years under the Abgabenordnung, a reminder that “on demand” can mean years after the original decision was made.
The “show me” test isn’t specific to the Pay Transparency Directive, or to the EU. Swap “Article 7 request” for “labor board audit” or “internal pay equity review,” and the requirement is identical: a system that can produce the criteria behind a decision, no matter the country or region.
For more on what this looks like in practice, see Multiplier’s salary banding guide and guidance on managing pay transparency alongside GDPR.
Step 3: Calculate total pay, not just base salary
Pay calculation has to account for every statutory component: gross pay, tax withholding, social security contributions, pension deductions, and any applicable allowances or benefits, each at the correct local rate for each jurisdiction.
Multiplier’s Global Hiring Gap report found that 53% of companies cite international tax compliance as their top payroll challenge, ahead of managing multiple vendors (51%), currency fluctuations (47%), and payment delays (39%).
This is specifically where the Pay Transparency Directive catches companies out. Under the directive, “pay” means every compensation element: bonuses, overtime, allowances, pensions, and variable components, whether paid in cash or in kind. A system built to calculate and report base salary, with bonuses and allowances tracked separately or processed outside the main payroll run, produces a number that’s accurate for payroll and incomplete for an Article 7 response.
Take an employee whose quarterly performance bonus was processed outside the main payroll run and never reconciled into their compensation record. Their total pay, as it appears in the system, understates what they actually received. When that figure feeds a comparator average, everyone compared against them sees a skewed result.
This isn’t a one-time disclosure exercise. An unexplained gap of more than 5% can trigger a remediation obligation, sometimes with worker representatives involved, on a window she put at roughly six months.
Somwya Murthy, Product Director of Payroll at Multiplier, points to where this is heading: “In the near future, we’ll see agents constantly scanning for errors, such as incorrect contract configurations, punitive clauses, or missing mandatory payments like 13th-month bonuses, and flagging them before they become liabilities.”
Step 4: Review employees’ work hours
Overtime thresholds, rest period requirements, and maximum working hours are statutory in most jurisdictions, and they feed directly into pay calculations.
For hourly and variable-pay workers, accurate time records are the basis of a correct payroll run. Errors here produce inaccurate pay figures, which means an employer can’t accurately report total compensation when a pay comparison is requested.
This is also where compensation management discipline matters. Pay decisions made inconsistently, with different overtime treatments for comparable roles or variable allowance policies applied unevenly, create exactly the kind of indefensible pay gap the directive targets.
Step 5: Be cautious about misclassification
Payroll accuracy depends on clean data: correct legal name, tax identification number, bank details, employment classification, and compensation components. Errors here create calculation failures down the line.
Under the Pay Transparency Directive, they create a more specific problem: if compensation records are incomplete or misattributed, an employer can’t produce the structured pay data an Article 7 response requires.
Of everything that can go wrong with employee data, classification carries the most weight. An employee misclassified as a contractor won’t have the right statutory deductions applied, will sit outside the comparator group structure the directive requires, and creates a liability that compounds with every pay cycle.
The data backs up how widespread this is. Multiplier’s report found that 46% of companies have failed to onboard international talent due to compliance issues, with misclassification one of the main reasons.
Worker misclassification risk isn’t unique to the EU. It determines which tax rules, benefit obligations, and statutory protections apply in any jurisdiction. What the Pay Transparency Directive adds is a second layer. Even correctly paid employees can fall outside a valid comparator group if the job classification behind their role doesn’t map to a recognized framework.
For example, in the US, data shows that during 2024 10% to 30% of employers misclassified all or some independent contracts who should have been categorized as employees.
The fix is a classification that maps to local legal definitions, not an internal standard applied the same way everywhere.
For EU employees, that means job classifications that can support an equal-value assessment under each member state’s own framework:
- Spain evaluates roles through sectoral collective agreements
- Sweden relies on role content and labour market benchmarks
- Germany layers in sector-specific collective agreements negotiated with works councils, which can set pay structures independent of internal job grades
An internal pay band that looks consistent across both jurisdictions may not hold up under either country’s legal test.
Amanda sees many companies fail there. “Without standardised job classifications, they can’t explain or prove equal value,” she says. Without a valid comparator group, an Article 7 response can’t be produced, however accurate the underlying pay figures are.
Common payroll compliance mistakes and how to address them
Two patterns account for most of the gap between payroll that runs and payroll that’s defensible.
Fragmented records and missed deadlines
When a compliance obligation arrives with a deadline attached, pulling a complete, coherent picture from disconnected systems is slow, expensive, and often incomplete.
For example, under Article 7, an employer who can’t produce structured compensation data within two months is in breach. The directive doesn’t treat internal data fragmentation as a mitigating factor.
An employer running payroll through one vendor in Germany, a different vendor in France, and a spreadsheet for two remote hires in Poland has no single view of who earns what across the comparator group the directive requires. When a request lands, someone has to manually reconcile three systems against a two-month clock, and any gap between them becomes a gap in the response.
The same fragmentation is usually behind missed recurring obligations, like the annual Article 7(3) notification covered in step one. Usually everyone knows the obligation exists. What’s missing is a system that tracks it against a calendar, so it falls to whoever happens to remember, and eventually no one does.
The fix is consolidating payroll records into a single system, or building a documented process for rapidly aggregating data across systems before a request arrives, along with a compliance calendar that covers every jurisdiction’s deadlines, including the recurring ones.
For more on the risks that fragmented records create, see Multiplier’s guidance on wage compression, one of the structural consequences of pay data that has never been audited in full.
The transparency-privacy tension
Payroll data is sensitive personal data under GDPR. A breach involving payroll records, through system compromise, unauthorized access, or improper disclosure, creates notification obligations, regulatory exposure, and potential liability to affected employees.
The Pay Transparency Directive adds a specific tension on top of that. Article 7 requires employers to disclose comparative pay data. GDPR requires that the privacy rights of the employees being compared are protected. Both obligations apply at the same time, and they can pull in opposite directions.
For small employers, this isn’t a theoretical problem. A two-person comparator group where one person is male and the other female makes comparison data effectively identifiable. The challenge is in how companies can respond in an anonymous way that doesn’t disadvantage the other people involved, according to Frayne.
If one person requests a pay comparison against a colleague doing the same role, the response identifies that colleague’s pay by implication, whether or not their name appears anywhere.
A policy decision made once won’t resolve this. The fix has to be structural: a system that can aggregate and anonymize comparator data automatically, at whatever group size a request involves, rather than relying on someone to judge case by case whether a response would identify a colleague.
As pay transparency obligations spread beyond the EU, expect this tension to show up wherever transparency requirements meet data protection law, not only under GDPR specifically.
For a full breakdown, see Multiplier’s guide to EU pay transparency and GDPR.
True global payroll compliance requires infrastructure, not administration
Getting payroll right in a single country is an administrative task. Getting it right across multiple jurisdictions, with real-time compliance monitoring and the ability to respond to an Article 7 request inside a two-month window, takes building solid infrastructure.
Vamsi Krishna, Co-Founder of Multiplier, describes the structural issue plainly: “The traditional model of setting up individual entities and managing disparate vendors is too slow for the modern speed of business, creating a fragmented system that drains resources. To be competitive, companies need a unified operational layer that allows them to scale without the administrative drag.”
Multiplier’s global payroll solution consolidates payroll across more than 160 markets into a single operational layer: owned entities, native payroll engines, and in-house compliance expertise, so every compensation component is captured, structured, and audit-ready from day one.
For companies running their own entities, that means pay band analysis, gender breakdowns, and audit trails are available across borders rather than reconstructed from separate vendors when a request lands.
Talk to our team to understand what payroll compliance looks like for your specific global footprint and get tailored guidance on hiring, paying, and managing employees across borders. Book a demo.
FAQs
What is payroll compliance?
Payroll compliance means meeting every legal obligation tied to paying employees in the jurisdictions where they work: accurate tax withholding, pension and benefit contributions, statutory payments, record-keeping, and the ability to document and justify pay decisions when employees or regulators ask.
Under the EU Pay Transparency Directive, that last requirement applies to every employer with EU staff, regardless of size, and similar expectations are emerging in other jurisdictions as pay transparency rules expand.
Why is payroll compliance important?
Compliance failures create financial penalties, legal liability, and reputational risk. Under Article 7 of the EU Pay Transparency Directive, failing to respond accurately to a pay request shifts the burden of proof to the employer, and discrimination is presumed unless disproved.
Building the infrastructure to respond only after a request arrives makes that defence harder to construct and more expensive to mount.
How can employers make payroll defensible?
Through infrastructure: standardized job classifications, structured pay data that can be audited by location, level, sex, and comparator group, documented pay criteria defined before decisions are made, and a response process that operates within statutory deadlines.
Software helps, but the architecture behind it determines whether compliance holds under scrutiny.
What are the most common payroll compliance gaps?
Worker misclassification, fragmented records spread across multiple vendors with no single view of who earns what, missed recurring obligations like annual pay transparency notifications, and a structural tension between disclosure requirements like Article 7 and data protection requirements like GDPR that needs an infrastructure answer rather than a one-off policy decision.
How does GDPR affect global payroll?
GDPR governs how employee personal data, including payroll records, is collected, stored, and disclosed.
For EU employers, the Pay Transparency Directive adds a specific tension: Article 7 requires pay comparison disclosures, while GDPR requires protecting the privacy of the employees being compared. Both obligations apply at the same time and need compatible processes.
What is the EU Pay Transparency Directive and does it affect payroll?
The EU Pay Transparency Directive (2023/970) requires employers to disclose pay information, close unjustified pay gaps, and give workers the right to request pay comparisons. It affects payroll directly: "pay" under the directive covers every compensation element (base salary, bonuses, overtime, allowances, pensions, and variable components), which means payroll records are the underlying data source for every Article 7 response.
The directive applies to all employers operating in EU member states, regardless of where the company is headquartered, with no minimum headcount threshold for the Article 7 right.
