A mid-sized French firm opening a German subsidiary, a Belgian scale-up hiring in Spain and the UK, a Dutch industrial group consolidating payroll across six countries: in every case, the same question quickly surfaces in the IT and HR departments. Can multi-country payroll be managed from the existing ERP, or does it require assembling a patchwork of local solutions?
The answer is neither binary nor simple. International payroll involves regulatory compliance (social declarations, contributions, withholding tax), HR management (local contracts, benefits, collective agreements), and financial consolidation (salary costs in multiple currencies, accounting provisions). The ERP sits at the crossroads of these three data flows, but its ability to cover them varies significantly across vendors, countries, and company sizes.
This guide structures the decision for IT Directors, HR Directors, and CFOs of mid-market companies (200 to 5,000 employees) operating or planning to operate across multiple European countries.
Five Countries, Five Declaration Frameworks: What an ERP Must Handle
The first trap in international payroll is assuming that only contribution rates differ from one country to the next. The reality runs deeper: each country has developed its own declaration protocol, its own timetable, and its own data reference framework. An ERP that cannot handle these local protocols natively forces companies into double data-entry or manual exports — both sources of errors and costly penalties.
France: the DSN — a Single Monthly Channel
The Déclaration Sociale Nominative (DSN) is mandatory for every employer paying at least one employee in France, regardless of headcount. It centralises in a single monthly flow all social information destined for URSSAF, CPAM, Agirc-Arrco, France Travail, and supplementary insurance bodies.
Deadlines are strict: before the 5th of the month for companies with 50 or more employees, before the 15th for smaller ones. A delay exposes the employer to a penalty of €60.07 per employee per month of delay. Since June 2026, a new development heightens the stakes: URSSAF can now issue “substitute DSNs” if an employer’s data anomalies persist after repeated warnings. This mechanism — initially targeting data affecting pension rights — effectively transfers to the social security body the power to correct declarations (CNP Protection Sociale, 2026).
For the ERP, DSN requires native integration with URSSAF reference data (establishment codes, complementary body codes) and the ability to generate files that comply with the current Neoxia technical specification.
United Kingdom: RTI — Real-Time Reporting at Each Payment
The HMRC’s Real Time Information (RTI) system requires UK employers to submit a Full Payment Submission (FPS) at each payroll run, before or at the point of payment. This is not a consolidated monthly declaration — it is a transactional flow: each payslip generated must be individually reported to HMRC.
Penalties for late FPS submissions are significant: £100 per month for 1–9 employees, up to £400 per month for 250 or more. On the contributions side, employer National Insurance Contributions (NICs) stand at 15% above a threshold of £5,000 per year since the 2025/26 fiscal year — an increase that raises the total labour cost for UK-based employers (Expertsure, 2026).
For the ERP, RTI requires direct connectivity to HMRC’s Government Gateway portal, or integration of a HMRC-recognised payroll module capable of generating and submitting FPS submissions automatically.
Germany: DEÜV — the Foundation of Social Insurance Reporting
The Datenerfassungs- und Übermittlungsverordnung (DEÜV) governs how employers report to health insurance funds (Krankenkassen) for German social contributions. SV-Meldungen (social insurance notifications) cover employee onboarding and departure, status changes, and annual pay declarations.
In Germany, DATEV remains the de facto standard for SME payroll, with native support for DEÜV processes. For mid-market companies seeking to unify German payroll within a group ERP, the key question is whether the ERP can replace DATEV entirely or interface with it via a certified connector. SAP, with its German country version, offers a native localisation that generates SV-Meldungen directly from the payroll module (Deutsche Rentenversicherung).
Belgium: Dimona — Immediate Notification Before Any Hire
Belgium mandates Dimona (Déclaration Immédiate / Onmiddellijke Aangifte) before each new employee’s start date. The declaration is compulsory for all employers — including public sector bodies — and must be transmitted electronically to the NSSO (National Social Security Office, or ONSS) before the employee begins work. On departure, the exit declaration must be filed no later than the next business day (NSSO, 2026).
Beyond Dimona, Belgian employers also submit the DmfA (Multifunctional Declaration), a quarterly return of working hours and remuneration. The ERP must therefore manage two distinct reporting cycles, each with Belgian social security-specific reference codes.
Netherlands: Monthly Loonaangifte and the Handboek Loonheffingen
In the Netherlands, employers submit a loonaangifte (wage declaration) monthly or every four weeks to the Belastingdienst (Dutch Tax and Customs Administration). This declaration incorporates loonheffingen — a combined system that merges payroll tax (income tax at source) and social contributions into a single flow to the tax authority.
The Belastingdienst publishes the Handboek Loonheffingen annually, the definitive technical reference for employers: the Handboek Loonheffingen 2026 has been available since the start of the year and incorporates applicable regulatory changes, including new codes for contract termination reasons. The ERP or payroll module must be updated to reflect these changes before the first declaration of the financial year.
ERP and International Payroll: Three Architecture Patterns
Faced with the diversity of local declaration protocols, multi-country companies typically adopt one of three architectures. The choice depends on the number of countries, headcount per country, and the ambition for centralisation.
Architecture 1: Native Multi-Country Payroll Module in the ERP
In this model, the ERP natively integrates payroll localisations for each target country. The company runs a single system, HR and financial data circulate without interfaces, and regulatory updates are deployed by the vendor across the entire installed base.
Advantages: data consistency, real-time consolidated reporting, lower long-term TCO when the number of countries is limited (5 to 15).
Limitations: not all localisations are equally deep. A vendor may claim coverage for 50 countries in payroll while offering comprehensive modules for France and Germany and only minimal coverage for Poland or Portugal. Each country must be audited individually.
Architecture 2: Central HCM ERP + Certified Payroll Aggregator
In this hybrid model, the ERP manages master HR data (contracts, pay structures, HR policies) and delegates payroll calculation and local declarations to a specialist aggregator — ADP GlobalView, Alight, Papaya Global, or Strada (Workday’s official partner). The aggregator operates legal entities or in-country partners in each country and guarantees regulatory compliance.
Advantages: very broad geographic coverage (up to 180+ countries), local regulatory compliance guaranteed by in-country teams, rapid deployment in a new country without waiting for a vendor localisation release.
Limitations: the ERP–aggregator interface is a single point of failure. A poorly configured data mapping generates payroll errors that are difficult to detect. The aggregator cost adds to the ERP licensing cost.
Architecture 3: Country-by-Country Outsourced Payroll
For companies with low headcounts per country (fewer than 20–30 employees), outsourcing payroll country by country through local service providers (local payroll bureaus, Employer of Record) can be more economical than a localised ERP module. Employer of Record (EOR) solutions such as Deel or Papaya Global take on local legal compliance for a monthly per-employee fee.
Advantages: zero local compliance risk, deployment in days, no localised ERP module to maintain.
Limitations: weak integration with group financial consolidation, HR data scattered across multiple systems, high per-head cost as local headcount grows.
Comparing the Main ERP Vendors for International Payroll
SAP SuccessFactors Employee Central Payroll
SAP is the most comprehensive player for native international payroll within an ERP. SuccessFactors Employee Central Payroll supports 53 payroll locales, with deep localisations for Western Europe (France, Germany, Belgium, Netherlands, UK, Spain, Italy, Switzerland, Austria) as well as Latin America, Asia-Pacific, and emerging markets.
The 1H 2026 release brings targeted improvements for Norway and Canada, confirming the vendor’s continuous localisation update cadence. The integration between SuccessFactors and S/4HANA Finance ensures that payroll costs feed directly into management accounting and budgeting.
Key strength for a European mid-market company: the functional depth of French and German localisations — the two most complex markets regulatorily in Continental Europe.
Caveat: licensing and implementation costs put SuccessFactors beyond reach for companies with fewer than 500 employees without an experienced systems integrator.
Workday HCM + Strada Global Payroll
Workday has a native payroll engine for five countries: the United States, Canada, UK, France, and Germany. For the 180+ remaining countries, Workday relies on Strada, its official partner, which operates payroll services in 186 countries with a certified bidirectional integration into Workday.
This hybrid model gives Workday near-universal geographic coverage while maintaining functional depth in key markets. The platform excels in user experience, HR analytics, and headcount planning.
Notable limitation: Workday remains predominantly deployed at large enterprises and English-speaking mid-market groups. Certified Workday implementation partners are less numerous in Continental Europe than SAP integrators.
Oracle HCM Cloud Payroll
Oracle HCM Cloud Payroll offers native localisations for around twenty countries, with recognised functional depth for the UK, US, Canada, and Australia. In Continental Europe, coverage is more limited than SAP — Oracle groups often combine HCM Cloud with local payroll partners for France, Germany, or Spain.
Oracle’s strength lies in native integration with Oracle EPM for budgetary planning and workforce cost consolidation within an advanced financial planning environment.
Sage and Access Group: Regional Leaders Worth Considering
In the UK and Irish markets, Sage Payroll and Access People offer mature, RTI-compliant solutions with strong local support networks. They are particularly relevant for mid-market companies with primary operations in the UK or Ireland that need reliable, cost-effective payroll compliance.
Sage also serves the French market through its Sage 100 Paie line — making it a pragmatic option for companies straddling the UK and French markets.
For a mid-market European company operating primarily in the UK/Ireland or France with secondary presence in other European countries, these regional specialists can cover the core footprint and delegate secondary countries to local partners — at a lower total cost than deploying SAP or Workday for a modest headcount.
Seven Questions to Ask Your ERP Vendor Before Signing
International payroll is a topic where sales demonstrations can be misleading. A vendor can display data-entry screens for 50 countries without the localisation being genuinely compliant or actively maintained. These seven questions distinguish real coverage from surface-level coverage.
1. Which countries have a certified and actively maintained localisation? Ask for a precise list with the dates of the most recent regulatory update per country. The difference between “supported” and “actively maintained” is material.
2. Who is responsible for regulatory updates during the subscription, and within what timeframe? A new Belgian law or a change to UK NIC rates must be integrated before the first affected payroll run. Request contractual SLAs on this point.
3. Does the localisation cover social declarations natively, or only payroll calculation? Calculating the right amounts is not sufficient: the ERP must be able to generate DSN, FPS, SV-Meldungen, Dimona, and loonaangifte files directly and submit them to the relevant authorities.
4. How does payroll data integrate with general ledger and management reporting? A payroll module disconnected from the group income statement forces manual reconciliations that eliminate the benefits of centralisation.
5. What happens for countries not covered natively? Ask about certified partners available, the nature of the interface (bidirectional API, CSV export, middleware), and who bears contractual liability in the event of a compliance error.
6. What are the conditions for providing payroll data to local audit authorities? A social audit in Germany or an HMRC inspection requires producing a detailed payroll history quickly. The ERP must be able to export this data in a format readable by inspectors.
7. What is the governance model for urgent regulatory patches? Some countries publish rate changes with very short notice (UK Budget in October, emergency DSN measures). The contract must specify patch deployment timelines and premium support conditions when needed.
Three Warning Signs in a Multi-Country ERP Implementation
Beyond vendor selection, the implementation itself carries risks specific to international payroll.
Country scope defined too early in the project. ERP projects often lock in the country scope in the initial brief, then the company opens two additional subsidiaries mid-project. Each country added after the initial configuration phase costs between 50% and 100% of the original localisation cost. It is better to design an extensible architecture from the outset.
The temptation of hard-coded local spreadsheets. In countries where ERP localisation is shallow or insufficient, local teams produce payroll in Excel and then key results into the ERP for posting. This approach, understandable in the short term, creates drift risk: local calculation rules evolve in the spreadsheets without the ERP being updated, audits become impossible, and accounting reconciliation grows more complex.
Underestimating the master data foundation. Unifying multi-country payroll in an ERP requires a shared reference framework for employment structures, pay grades, and salary components. This master data project is consistently underestimated: it typically consumes two to three times more effort than anticipated, yet it conditions the reliability of everything else.
What International Payroll Reveals About Your ERP Maturity
The ability to manage multi-country payroll is not merely a functional problem — it is a diagnostic for the architectural maturity of your management information system. A mid-market company that can correctly file DSN in France, RTI in the UK, and SV-Meldungen in Germany from a single system has, in the process, solved broader challenges: a unified employee master record, real-time payroll-to-accounting integration, and multi-country regulatory traceability.
This maturity is not reserved for large corporations. Mid-market companies with 200 to 2,000 employees operating across 3 to 8 European countries are precisely in the range where a well-configured ERP with solid localisations delivers a direct operational advantage: fewer compliance errors, fewer manual reconciliations, lower risk of penalty audits.
The question is not whether your ERP can handle international payroll — it is at what cost, with what depth of local functional coverage, and with what level of contractually guaranteed regulatory maintenance.
To explore related topics, see our guide to ERP and HR management: integrated HRMS vs dedicated module and our article on workforce planning and payroll budgeting in ERP.
