An HR lead at an engineering group is asked to introduce the Deutschlandticket across the whole organisation: 14 to 16 legally independent subsidiaries, each with its own HR function, its own payroll, and its own subsidy practice built up over years. The pilot in one subsidiary of around 500 employees went well. The real problem surfaces on the attempt to scale out of the existing tool: a separate login per subsidiary, no consolidated reporting, no wage type mapping per entity. What began as an introduction project turns into a platform migration.
This pattern is typical for mid-sized groups and large enterprises. What works at a single legal entity in a few weeks becomes a multi-month project in a holding structure, with its own demands on policy design, payroll, reporting, and master data. This guide sets out the five points where multi-entity introductions get stuck in practice, a phase model that has worked, and three pitfalls HR teams tend to identify only after go-live, when correcting them is expensive.
Terminology for readers outside Germany: "entity" here means a legally independent German subsidiary with its own payroll run and its own works council. Groups in other jurisdictions often share a single payroll across subsidiaries, which removes most of the complexity described below.
Most benefit platforms were built for one legal entity, not for a holding. With every additional subsidiary, what looks like a configuration problem turns into a data model problem. Three symptoms recur.
HR has to log in separately per subsidiary, maintain separate master data, and pull separate reports. Across 14 to 16 entities that adds up to several person-days per month, which is the opposite of the efficiency the tool was bought for.
Where site A subsidises 80 % of the Deutschlandticket, site B 100 %, and site C 50 %, with no central rule deriving those figures, the differences widen with every personnel change. At the latest when a group works agreement or a transfer of undertaking comes up, those differences have to be justified retroactively. That rarely goes well.
SAP HCM runs alongside other payroll systems, DATEV with different wage type conventions per subsidiary, plus international payroll providers. A platform that only produces one DATEV format becomes the bottleneck.
These symptoms usually appear together, because they are organisationally connected. A multi-entity mobility budget needs a data model in which group, entity, and site are separate dimensions, not merely the ability to support several clients.
Create the work place of tomorrow with NAVIT. We are happy to support you with designing the best mobility solution for your company. Get in touch with us!
Contact us
A group-wide mobility policy needs two layers: a framework at the top defining mobility types, tax treatment, and exclusions, and a local layer underneath for subsidy rates and site specifics. The same budget then works in a city with dense public transport and at a rural site where a car is unavoidable.
The central policy should set at minimum: the permitted mobility types (Deutschlandticket, bicycle leasing, a mobility budget for public transport, a fuel and charging card, a car subscription), the tax treatment per benefit (§ 3 Nr. 15 EStG, § 3 Nr. 37 EStG, § 8 Abs. 2 Satz 11 EStG, § 40 Abs. 2 Satz 2 Nr. 2 EStG), the maximum group subsidy per employee per month, and the group-wide exclusions.
Who is eligible, and from when? What applies to interns, working students, part-time staff, parental leave? It sounds simple and becomes complex as soon as the rule has to map onto the master data fields that actually exist in each entity, and the provider is expected to verify automatically from which date a given person qualifies.
Before the roll-out, each entity should have an answer to the following points:
These five questions should have the same answer in every entity, or the deviations have to be documented and justifiable to the works council. Otherwise a tax audit becomes an exercise in explanation.
Logging into each subsidiary separately and merging reports by hand makes group-level controlling effectively impossible. One consulting group put the requirement plainly during a selection process: a single report across all companies, with a column for the respective entity.
Multi-entity reporting should make at least these dimensions combinable:
Even with a central shared service centre, posting runs separately per entity. The platform therefore has to produce exports per subsidiary rather than one group export that payroll then splits by hand.
In practice that means that wage type mapping should be configurable per entity. For instance, the wage type "Deutschlandticket § 3 Nr. 15 EStG" can be called LA 4711 in subsidiary A and LA 8830 in subsidiary B.
Additionally, there should be a cost centre logic per entity, so that subsidies automatically post to the right cost centre in the right subsidiary.
Flat-rate taxation on the other hand can be configurable per entity. Whether flat-rate taxation under § 40 Abs. 2 Satz 2 Nr. 2 EStG is applied can be decided differently in each subsidiary.
The consequences of a poor handover are invisible during a pilot. They surface once three months of data have accumulated and payroll starts cleaning up by hand.
In a group, monthly leavers across all companies quickly reach a double-digit figure. Every leaver maintained by hand is both effort and a source of error, because a Deutschlandticket paused too late keeps running at the employer’s expense.
Bulk onboarding and offboarding should work across entities. That means, an automatic process is in place for a CSV upload of new joiners per entity or group-wide and a leaver list with an entity column, pausing all benefits automatically at the effective date. Subsidy changes for employee groups across several entities should be updated at once.
The HRIS integration is where it becomes clear how consistently the multi-entity data model was carried through. If the platform requires a separate sync configuration per entity, the architecture was never designed for group structures.
Multi-entity introductions are not big-bang projects. Taking 14 subsidiaries live at once increases risk without any return. A three-stage model across 18 to 24 months has worked well.
Pick one entity with clear HR ownership, a settled payroll, and 100 to 500 employees. The goal is validation rather than introduction: does the policy work, which eligibility rules generate queries, how cleanly does the payroll export run? After six months the defensible measures are take-up rate, monthly HR effort, the number of manual payroll corrections, and qualitative employee feedback. Those are the basis for the argument to management and to the works council.
Three to five further entities go live in parallel, using the same policy structure, subsidy logic, and wage type mapping as the pilot. Deviations should be justified and documented rather than arising by accident. The typical problems are organisational: local HR leads with their own preferred solution, works councils wanting separate agreements, payroll staff resisting a new wage type scheme. A clear escalation route to group HR and documented pilot results shorten those discussions.
The remaining entities are connected, reporting is unified, and special arrangements are brought back to the group standard where possible. By this point group controlling should be working productively with the consolidated data, for example for ESRS E1 reporting on employee commuting or CSRD-relevant Scope 3 Category 7 data. A group works agreement marks the formal transition from pilot project to established benefit.
Our mobility experts at NAVIT would love to share their knowledge with you about the new mobility product. Feel free to get in touch with us!
Get infoOne site has had a 100 % Jobticket subsidy for 15 years, another gives a fuel voucher, a third gives nothing. Trying to harmonise that retroactively meets substantial resistance. The more pragmatic route is grandfathering with a sunset clause: existing arrangements continue for current employees, new hires fall under the group policy from a set date. The difference disappears through natural turnover.
Combined benefits in kind are the tax-sensitive part. Where an existing fuel card arrangement is set off against a new mobility budget, the €50 monthly exemption limit under § 8 Abs. 2 Satz 11 EStG is quickly exceeded. This is an exemption limit rather than an allowance: exceed it by one cent and the entire amount becomes taxable, not just the excess. A binding ruling from the tax office for the place of business is worth having here, ideally before go-live rather than after the first audit.
A group-wide introduction typically touches several levels of co-determination at once. German works council structure is three-tiered: a Betriebsrat at establishment level, a Gesamtbetriebsrat covering several establishments of one company, and a Konzernbetriebsrat covering the group. Which body is competent depends on whether the matter can sensibly be settled at the lower level.
Three questions should be answered before the start. Which works council is competent at which level under § 87 BetrVG? Which existing works agreements need amending? Can a group works agreement serve as a framework with local supplements? A prepared briefing for those bodies, with data on expected take-up, tax treatment, and the inclusiveness of the benefit, noticeably shortens the discussion.
In consultancies, law firms, and partnership organisations, no central body decides on new benefits. A partner meeting or a shareholder committee does, on its own cycle, and those cycles do not accelerate in response to HR escalation. The decision process therefore belongs in the project plan from the start. Nine to twelve months from first pitch to productive introduction is realistic, with two or three preparatory sessions in individual partner committees before the final decision.
NAVIT manages mobility benefits across all subsidiaries in one platform: a central policy, entity-specific subsidy tiers, consolidated reporting across all sites, and a configurable payroll export per entity. Instead of logging into each subsidiary, HR works from a single dashboard. A combined leaver list can be uploaded for all companies at once, reporting shows the entity per row alongside the subsidy tier and wage type mapping, and HRIS connections deliver the entity as an attribute of the person, so internal moves between subsidiaries need no manual correction.
Two documented results show what this looks like in practice. Deloitte manages approximately 9,700 Deutschlandticket subscriptions across 16 German locations from a single consolidated payroll report, with monthly HR effort of around one hour. At MERKUR PRIVATBANK KGaA, administrative effort fell by around 90 % after introduction: employees previously submitted receipts for Deutschlandtickets they had bought themselves, which then had to be checked, settled, archived, and reimbursed through payroll. Those steps no longer occur.
This architecture becomes relevant from about five entities upwards with different payroll systems or distributed HR ownership. At that point it is the consistency of the data model, rather than any individual feature, that decides whether the mobility budget stays administrable.
How long does a multi-entity introduction usually take?
For groups with ten or more entities, 18 to 24 months from pilot to full consolidation is realistic: three to six months of pilot, six to twelve months of scaling, and a further six months of consolidation. Acceleration is possible but increases risk, particularly around works council communication and payroll integration.
Can different subsidiaries have different subsidy rates?
Yes, and it is often sensible. A subsidiary with dense public transport benefits from a higher Deutschlandticket subsidy, one in a rural location from a larger share for the fuel and charging card. The central policy defines the frame; the subsidy tier per entity sits inside it.
How is payroll handled per entity?
Each subsidiary has its own wage type scheme. The platform should produce entity-specific exports with configurable wage type mapping, correct cost centre logic, and support for the payroll systems actually in use. A single group export almost never suffices in practice.
What happens to local arrangements that have grown up over the years?
Usually grandfathering with a sunset clause: existing arrangements continue for current employees, new hires fall under the group policy from a set date. Where benefits in kind are combined, for example a fuel card alongside a mobility budget, a binding ruling from the tax office is advisable so the €50 exemption limit under § 8 Abs. 2 Satz 11 EStG is not exceeded unintentionally.
Does every subsidiary need its own works agreement?
It depends on the co-determination structure. Where a group works council exists, a group works agreement can usually serve as a framework with local adjustments. Without one, or where local arrangements differ substantially, separate agreements per entity are the realistic route. Early alignment with the works councils, ideally before the pilot, considerably reduces the risk of delay.
Disclaimer: NAVIT accepts no liability for the accuracy of the information provided. The content on our website is for general information purposes only and does not constitute tax or legal advice. It cannot and is not intended to replace individual, binding tax and legal advice addressing your specific circumstances. All information is provided without warranty as to accuracy or completeness.
Sign up for our newsletter to receive the latest insights about our mobility solution products like the 49 eurojob ticket.
