Introducing a mobility budget in a large company is rarely a question of persuasion. Usually everyone is in favour. The question is who has to sign off.
IT wants to see the ISO 27001 certification and asks about the data protection impact assessment. The works council points to its co-determination rights and wants to know which usage data ends up where. Payroll asks whether any of this arrives in SAP without manual rework. And procurement wants service levels and references from comparable projects. Every one of these functions can stall the project, and none of them is moved by the argument that employees would like flexible mobility.
This article sets out the criteria that decide whether a platform holds up in an enterprise environment.
The difference from a mid-sized company lies not in the number of employees but in the number of people involved.
At a thousand people, manual CSV transfers are no longer merely inconvenient. They are an error source with compliance consequences. At five thousand, the introduction needs project management with milestones, because a launch across sixteen sites cannot be coordinated on the side. And at ten thousand, every query about a reimbursement becomes a ticket volume that somebody has to work through.
There is also a requirement that rarely arises in smaller companies. Head office needs a consolidated view across all sites, while local HR teams want to manage their own budgets. Enabling both at once is technically harder than it sounds, and many platforms can only do one.
Then there is the security review. Penetration tests, certifications, contractually guaranteed availability: these are hurdles smaller providers regularly fail, not because their product is weak but because they do not have the evidence.
Native interfaces to SAP, Workday, Persis, Sage or DATEV are not an added extra in an enterprise context. They are the precondition for the project being approved at all.
The question worth asking is what the provider means by integration. Between a bidirectional API and a CSV export that IT loads each month lies, at ten thousand employees, a full-time equivalent. Also ask who maintains the interface when systems are updated. If someone in-house has to check after every SAP release whether the connection still works, that is not an integration but a dependency.
This point either shortens or extends the project by months.
Co-determination follows from section 87 of the German Works Constitution Act and applies in several places at once: to company pay structures, because a mobility budget is a component of remuneration, and to the introduction of technical systems, because an app generates usage data.
What speeds up the negotiation is having documents ready. A template works agreement, data protection documentation including the processing agreement, and a communication package for the workforce. Bring those three things to the first meeting and you discuss substance. Have them written afterwards and you discuss dates.
In practice the consultation takes four to eight weeks. It can run in parallel with technical setup, which shortens the overall timeline considerably.
A launch for five or fourteen thousand people is a project, not an onboarding. It needs a plan, milestones and named contacts on both sides.
Ask specifically for references at comparable scale, and how many projects of that size can run in parallel. A provider already running three enterprise projects who takes yours on as the fourth will be sending you the same people.
Deloitte Germany introduced NAVIT in September 2024 for around 14,000 employees across 16 sites, with implementation completed in under two months. What made that possible was central onboarding and a prepared communication campaign rather than unusually fast technology.
Head office needs the consolidated view for payroll reporting, tax documentation and management oversight. Local HR teams need to be able to set their own budgets, because a site in Munich faces different conditions from one in a rural region. Test a genuine multi-site scenario in the demo, not the standard view.
That includes whether mobility policies can be stored per employee group. Without that, exceptions have to be managed by hand, and in a large organisation exceptions are the norm.
A mobility budget is not a single product for tax purposes. Depending on how it is spent, a different provision applies, and that classification has to be right every month for every person, consolidated across every site.
This is the work a platform should take on. Do not ask whether the provider is tax compliant. Ask what happens when someone exceeds the monthly benefit-in-kind threshold, and how the software detects it.
Availability commitments, support response times, security audits: in an enterprise context these belong in the contract, not on a product page. Ask for certifications and audit reports before the selection decision, not after.
Three routes are relevant in an enterprise context, and they can be combined.
The benefit in kind under section 8 (2) sentence 11 EStG allows up to 50 euros per month tax-free. Two conditions apply. The budget must be granted in addition to regular salary; a salary conversion does not qualify. And this is a threshold rather than an allowance: exceed it and the entire amount becomes taxable, not just the excess. At ten thousand employees, that is precisely why automatic monitoring of this limit is not a convenience feature.
The public transport subsidy under section 3 no. 15 EStG has no upper limit and is not counted against the benefit-in-kind threshold. For the Deutschlandticket that currently means up to 63 euros a month; where the employer covers the full cost, no taxable benefit arises for the employee.
One point missing from most accounts, and one that moves large numbers at scale: the tax-free subsidy reduces the employee's commuting allowance by the same amount. Someone with a long daily commute therefore loses part of what arrives on the other side.
That is what the third route is for. Commuting subsidies for travel between home and the primary place of work can be taxed at a flat rate of 25 percent under section 40 (2) sentence 2 no. 2 EStG. The offset then does not apply, but the employer bears the flat-rate tax. Since the commuting allowance rose to 38 cents from the first kilometre in 2026, this calculation favours the flat rate more often than it used to. Where commuting distances vary widely across the workforce, it is worth modelling both.
For budgets well above the threshold, for instance as a company car alternative, the tax treatment has to be established case by case. Blanket statements about budgets of 200 to 400 euros a month are not defensible here.
At enterprise scale the market divides into three groups.
Specialist mobility platforms bring the integrations, compliance automation and project capacity that large organisations need. Their advantage is depth: more transport operators connected, faster response to regulatory changes such as the German Federal Ministry of Finance circular on home charging reimbursement.
Multi-benefit platforms, which carry mobility alongside meal allowances, health and training, have a different advantage: one system for several benefits, one contractual relationship, one interface. Anyone consolidating a benefits portfolio should give this option serious consideration. Depth on the mobility side is typically lower, and adaptations to German tax changes take longer.
In-house solutions and manual processes are effectively ruled out at four-figure headcounts. Not because they are impossible, but because the effort for review, settlement and record-keeping grows faster than the benefit.
Deloitte Germany introduced the Deutschlandticket together with NAVIT in September 2024. The aim was to offer the ticket to around 14,000 employees across 16 sites without creating meaningful internal administration.
All 16 sites have run through a single employer portal since then. Orders, cancellations, status changes and payroll reporting are managed in one place, and the data arrives in payroll in the right format. One consolidated report for all sites replaces sixteen separate downloads.
Around 9,700 Deutschlandtickets are processed each month through a single consolidated payroll report. Total HR effort runs at roughly one hour a month. Implementation was completed in under two months, supported by a tailored communication campaign for the workforce.
Read the full customer story
Eight points worth settling:
At enterprise scale, choosing a provider is not a product decision but an integration decision.
A platform that cannot connect to the systems already in place, cannot give the works council usable documentation and cannot structure a launch across sixteen sites will fail with even the best product. The reverse also holds: where those three things work, surprisingly little day-to-day effort remains. At Deloitte it is one hour a month.
How long does implementation take at enterprise scale?
Two to four months is typical for companies between 1,000 and 15,000 employees. At Deloitte it took under two months for around 14,000 employees across 16 sites. What matters is running the works council phase in parallel with technical setup rather than after it.
Which HR systems are natively supported?
NAVIT offers native integrations with Workday, Persis, Sage and other systems. For SAP environments an API approach is available and agreed individually during the project. Which option applies depends on the version in use and your IT department's own requirements.
Does every site have to be configured separately?
No. Configuration is central, with site-specific adjustments where they are needed, for example different budget levels by region. Head office keeps the consolidated view, and local administrators can make their own settings within the framework that has been set.
What does a mobility budget cost per employee?
Costs consist of the budget itself plus a platform fee per user. At a typical budget of 50 euros a month, structured tax-free, no wage tax or social security contributions arise. Compared with a salary increase producing the same net effect, that is cheaper for the employer. It is not cost-neutral: the budget paid out remains an expense.
Is works council approval required?
Where a works council exists, it must be involved under section 87 of the Works Constitution Act. Co-determination applies to company pay structures and to the introduction of technical systems. With complete documentation on data protection, the works agreement and tax treatment, consultation typically takes four to eight weeks.
