Payroll & HR Systems Coordination for Non-EU Banks Under CRD VI
Several EU branches. One coordinated payroll and HR model.
From 11 January 2027, CRD VI requires a non-EU bank to provide core banking services through an authorized branch in every Member State it serves, unless an exemption applies. Each new branch is a new employer with no payroll: new tax and social security registrations, a new local provider, a new filing calendar and a new set of data feeds. Set up one country at a time, several branches turn into several payrolls that never quite agree. Any branch you already run under a national regime has to fit the same model.
Europe HR Solutions designs how your local payrolls, employee data and HR systems fit together before the first branch hire, then coordinates the local providers who run each payroll. One model, localized per country, reporting into one place for group HR and finance.
WHO WE ARE
The Partner That Makes Six Branch Payrolls Work as One
The first pay run in a new country is where branch timelines quietly slip: a registration that takes longer than planned, a provider onboarding that misses its cutoff, a new joiner keyed differently in two systems. Our model is built for exactly that point: a senior team in Belgium runs the plan, independent specialists in each country bring the local payroll knowledge, and local providers process each run. We own how the pieces fit, so your team deals with one partner instead of six.
When Genea Biomedx took on employees in six European countries after acquiring a division of Merck, we set up payroll and managed the providers for every entity, and later implemented a new HRIS for the group’s European operations. Read the Genea Biomedx story.
THE MULTI-COUNTRY REALITY
Six Branch Countries. Six Payroll Calendars That Will Not Line Up on Their Own.
A branch authorized in Frankfurt calculates German wage tax, pays German contributions and files with German authorities. The Paris branch is a separate payroll with its own deadlines. Every additional branch country brings its own registrations, filing dates and provider. Group sees one program. Every tax office sees one national payroll.
DEGermany
- An accident insurance number first, then the Federal Employment Agency's employer number, so staff can be registered with health insurers before day one
- Wage tax returned and paid by the 10th of the following month, alongside electronic social insurance reporting
- Works council co-determination before a group HR system goes live in the branch
FRFrance
- The monthly DSN, which carries social contributions and replaced most separate employer declarations
- Where the branch is licensed as a bank, the banking agreement's salary minimums checked in every run
- Mutuelle and prévoyance contributions deducted and reported through payroll
NLNetherlands
- Payroll tax (loonheffingen) registration and a monthly or four-weekly payroll tax return
- Expat ruling applied at the new 27% maximum from January 2027, with transitional cases kept separate
- Pension vehicle confirmed first: a mandatory sector fund where one applies, otherwise an insurer or general pension fund
IEIreland
- Revenue employer registration, with pay, PAYE, USC and PRSI reported on or before every pay date
- A Revenue Payroll Notification retrieved for each employee before tax is calculated
- Start dates for non-EEA hires tied to their employment permit
LULuxembourg
- Affiliation with the CCSS, then monthly salary declarations to it
- Every salary raised by 2.5% whenever an indexation tranche falls due
- Cross-border commuters (47% of Luxembourg's employees in 2024) needing French, Belgian or German tax and social security treatment
ESSpain
- A contribution account code from the TGSS (Social Security Treasury) ahead of any hiring, then monthly contributions
- Two extraordinary payments a year built into the calendar, or spread across twelve where the agreement allows
- Banking agreement pay tables for most staff, while senior managers and identified staff paid above its top scale fall outside it
Six countries means six calendars and six providers. Unless someone designs how they connect, your payroll team becomes the connector.
THE SYSTEMS AND DATA CHALLENGE
One Employee Record at Group. Six Payrolls That Need It Every Month.
Group HR, group finance and every local payroll need the same facts each month: who joined, who left, what changed in pay. Connect them at the start and each change travels once. Leave it for later and every change is keyed by hand in each country, and month-end turns into a reconciliation exercise.
Group HR & Finance
The source of truth for people and cost
BUILT COUNTRY BY COUNTRY
Each branch picks its own provider and file format. A new hire is entered in the group HRIS, then again in a local payroll portal. Figures drift apart, and every group report needs a manual check before anyone signs it.
DESIGNED AS ONE MODEL
A change is entered once in the group record and reaches each local payroll on a shared calendar. Every run ties back to that record, so the group report is one your CFO can sign without a second spreadsheet.
WHAT WE COORDINATE
Six Pieces That Have to Agree Every Month
Get these six aligned across your branches and payroll runs on time, costs reconcile and group reporting holds up. Let any one drift and the others follow.
Payroll RUNS
National rules, shared calendar
Employee data
One master record
HR systems
Integrated, not rekeyed
Registrations
Done before the first hire
Reporting
One monthly view
Providers
Selected and managed centrally
WHAT EUROPE HR SOLUTIONS HANDLES
Payroll Coordination for Non-EU Banks, Workstream by Workstream
Each workstream is planned per Member State and tracked against your CRD VI timeline, so your program office follows one payroll and systems workstream instead of chasing six providers.
Payroll Operating Model
Which decisions sit with group and which run locally, who approves each pay run, and how one calendar works across countries. Agreed before the first provider contract is signed.
Registrations & Provider Setup
Tax and social security registrations in each Member State, payroll providers selected against your group’s vendor and data standards, and a parallel test run signed off before the first real pay date.
Employee Data & HRIS Integration
One employee master record, a defined data flow to each local payroll, and the works council and data protection steps built into the rollout wherever they apply.
Pay, Benefits & Pension Inputs
Group salary structures and bonus elements mapped into each local payroll, with pension and insured benefit contributions set up correctly per market.
Consolidated Reporting & Controls
One monthly view of headcount, gross pay and employer cost across branches, with defined approvals, variance checks and escalation paths behind every figure.
Ongoing Payroll Operations
Monthly cycles, filings, year-end and changes coordinated across providers once branches are live, with one named owner when something goes wrong in any country.
TWO WAYS TO RUN IT
Six Local Payrolls, or One Coordinated Model
Most banks never make this decision. It gets made for them, one branch at a time. Making it before the first provider contract is signed costs far less than unwinding it afterward.
Each branch on its own
Every country chooses its own provider, format and calendar
- A different provider contract, file format and service level in every country
- New hires entered in the group HRIS, then again in each payroll portal
- Cutoffs and pay dates set locally, so group never closes on the same day
- Bonus and benefit elements interpreted differently in each run
- Group cost reports rebuilt by hand from six sets of output
- Nobody accountable when one country's run fails
One designed model
Coordinated across every branch by Europe HR Solutions
- Providers chosen against one set of criteria and one data standard
- Each change entered once and passed to every payroll
- One calendar, with cutoffs agreed across all branches
- Group pay rules applied consistently, localized where the law requires
- One monthly cost and headcount view from a single source
- One owner across providers, countries and escalations
HOW WE RUN IT
Scope. Design. Stand Up. Coordinate.
Four steps per Member State, started alongside the authorization work so each branch has a tested payroll before it needs one.
Scope
Branch countries, planned headcount and pay dates from your CRD VI plan, plus the group systems and data standards every branch payroll has to connect to.
›Design
The target model: what group owns, what each country runs, how data moves between HRIS, payroll and finance, and which provider fits each market.
›Stand Up
Registrations, provider contracts, data interfaces and a tested first run, country by country, in the order your authorizations land.
›Coordinate
Monthly cycles, filings, changes and reporting coordinated across every branch, and extended to the next country when your footprint grows.
PART OF OUR CRD VI SERIES
The Rest of Your CRD VI Branch Setup
Market Entry HR Setup for Non-EU Banks Under CRD VI →
The employer layer each branch needs before payroll can run: contracts for the persons directing it, key function holders, benefits and local policies, built per Member State.
CRD VI · BankingEmployment Documentation for Third-Country Branches →
The documents each branch employee signs and follows, from director contracts to local handbooks, prepared country by country.
QUESTIONS BANKS ASK US
CRD VI Branch Payroll and HR Systems: Your Questions Answered
1. Can every branch run on our head-office payroll system?
Not as the payroll engine. Each branch country’s payroll has to calculate tax and contributions under national rules and file with national authorities: the monthly DSN in France, real-time PAYE reporting in Ireland, wage tax returns in Germany and the Netherlands. Your group system stays the source of truth for employee data, a compliant local payroll runs in each country, and the two connect. We design that connection rather than replace what you already have.
2. We already have a global HRIS. Do we still need payroll coordination?
Yes. The HRIS holds the employee record, but it does not file a Spanish contribution return or check a French run against the sector salary grid. Someone still has to decide which fields each local payroll needs, when changes are cut off, how results come back and who fixes an error. In Germany, if the branch has a works council, rolling out the HRIS there also requires its co-determination under Section 87(1) no. 6 of the Works Constitution Act. Coordination is the layer between the system and the pay run.
3. Do you run the payroll yourselves, or coordinate local providers?
We coordinate. Local payroll providers process and file in each country. Europe HR Solutions selects them with you, sets the inputs, calendar and approvals, checks results against contracts and policies, and owns escalation across all of them. You get one point of contact without any single country depending on us to press the button.
4. We already run a branch in one Member State under the old national regime. Where does its payroll fit?
Inside the same model, not beside it. An existing branch already has its employer registrations, provider and calendar, so the work is mapping it against the target design: the data standard, the shared calendar and the group reporting structure. It often becomes the reference country for the new branches, or the first one brought into line with them.
5. Will group finance see a single payroll report for all branches?
Yes, if it is designed in from the start. Agree a common structure for pay elements and cost codes before providers are appointed, and each provider’s output maps into one monthly report of headcount, gross pay and employer cost, with the country detail behind it. Retrofitting that after six providers have each used their own codes is far harder.
7. Can payroll go live in several Member States at the same time?
Yes, within one constraint. Provider selection, data design and calendars can run in parallel across countries, but registrations only start once each branch exists locally as a legal fact. We sequence every country to its own registration and authorization dates, so first runs are tested in the order branches open.
8. What about moving employee data across borders?
Payroll data on branch employees is personal data under the GDPR, and sending it to a head office outside the EU needs a valid transfer mechanism. The UK has an adequacy decision, renewed in December 2025 to run until December 2031, and Switzerland’s was confirmed in the Commission’s January 2024 review. Transfers to the US can rely on the EU-US Data Privacy Framework where the recipient is certified, or on standard contractual clauses. Payroll also holds sensitive items such as sickness absence, so access should match what each role needs. We build these choices into the data design with your data protection officer and privacy counsel.
Reviewed by Nadia Harris, Client Solutions Director · Last reviewed September 2026
Every Branch Needs a Tested Payroll Before Its First Pay Date. Start the Design Now.
See the whole payroll model before the first branch goes live
Tell us your branch countries, the HR and payroll systems you run today and when each branch is due to open. We lay out the payroll, data and reporting work in every branch country.
You receive a per-country map of how the pieces connect, what comes first and the lead time for each.
No commitment required. You leave with a working picture of how your branch payrolls run as one model.