Companies in the German Mittelstand rarely have a dedicated benefits team. That makes the choice of platform less about feature counts and more about how much monthly work is left over afterwards. Four things decide it: which mobility services are booked inside the app rather than reimbursed against receipts, how settlement works, whether the platform handles the tax classification itself, and whether it connects to the payroll system you already run.
The questions usually arrive in this order. Someone on the management team asks whether the company could offer a mobility budget too. HR then asks who is supposed to administer it. And at some point payroll asks how any of this ends up in the monthly run.
In a mid-sized company, the second question decides whether the project happens at all. A corporate group assigns someone to it. An HR department of three does it on the side or not at all. So the question worth asking is not which platform can do the most, but which one can actually be operated with the people you have.
This article walks through the criteria that decide that.
Mid-sized companies face the same tax compliance requirements as large ones. The tax office does not offer volume discounts. What they lack is the internal capacity to meet those requirements by hand.
In practice this means three things. Monthly administration has to run alongside everything else, including settlement, tax reporting and the employee asking why her reimbursement has not arrived. The tax classification between the different components has to be handled by the system, because nobody calls their tax adviser about individual cases. And the data has to reach payroll without an intermediate step, because manual transfers create errors exactly where they are most expensive.
There is also the question of time. A project requiring three months of technical setup does not get approved in a mid-sized company. It gets postponed. And on price: large corporates negotiate special terms, mid-sized companies need fair list prices without surcharges for things you only discover once you are live.
The biggest difference between two platforms does not show up in a feature comparison. It shows up in the usage rate after six months.
The reason is mundane. If employees can order a Deutschlandticket directly in the app, they do. If they have to buy it privately, photograph the receipt, upload it and then wait for reimbursement with the next payslip, fewer of them bother. Every additional step costs participants, and a benefit that half the workforce ignores is an expensive misunderstanding.
So check each category individually for whether it is integrated or merely reimbursed: Deutschlandticket, public transport generally, fuel and charging, bike leasing, car subscription. Providers like to list everything that is somehow claimable in their comparison tables. That is not the same as a booking in two taps.
Three models exist, and the difference in effort between them is considerable.
With integrated booking, employees book and pay directly in the app. HR does effectively nothing, and it is the most convenient route for users. The model only works, however, for services the provider has actually connected.
A virtual debit card is topped up automatically each month and works wherever cards are accepted. It covers everything that is not directly connected, from a car-sharing trip to a charging point on the road.
Receipt-based reimbursement is the oldest model and the most laborious. Employees pay upfront, upload receipts, someone reviews them, and reimbursement runs through payroll. For a small team that may be fine. Above roughly a hundred participants it becomes a process in its own right, with error sources of its own.
The most workable combination for mid-sized companies pairs the first two. Deutschlandticket and bike leasing run through integrated booking, everything else through the card. Pure receipt models are hard to recommend when nobody has time to review receipts.
A mobility budget is not a single product for tax purposes. Depending on what it is spent on, a different provision applies, and that classification has to be correct every month for every person.
This is precisely the work a platform should take off your hands. In vendor conversations, do not ask whether the provider is "tax compliant". Ask how the classification works technically, and what happens when someone exceeds the monthly benefit-in-kind threshold. The answers vary more than the websites suggest.
DATEV is the standard in the German Mittelstand, and a native connection to it is not a nice-to-have. Without one you get a manual transfer every month, and every manual transfer is a potential correction.
Ask what "integration" actually means for each provider. Between a genuine interface and a CSV file that someone imports lie several hours a month.
Technical setup is rarely the bottleneck. One to four weeks is normal, and anyone needing longer should explain why.
What comes afterwards is more interesting. Are there ready-made materials for the workforce, an announcement text, an FAQ, a short guide? Is there someone available for questions, or does everything land in general support? And does a template exist for the works council, or does it still have to be written? Those are the things that decide the timeline in a mid-sized company, not the server configuration.
A single flat amount for everyone is the simplest way to start and rarely the best solution. Check whether budgets can be tiered by location, function or tenure, whether unused amounts carry over into the following month, and whether individual categories can be excluded.
This flexibility matters most in works council negotiations. Answering the fairness question with "everyone gets the same" is an argument. Being able to explain why a site with no rail connection is treated differently from headquarters is a better one.
The mobility budget market has become crowded in recent years, and the differences rarely sit where the websites suggest.
One dividing line runs between dedicated mobility platforms and multi-benefit providers that carry mobility alongside meal allowances, health and training. Both have their place. If you want to steer several benefits through one system, a multi-benefit platform makes sense. If mobility is your primary use case, specialist providers generally offer deeper integration, simply because they have connected more transport operators.
The second dividing line runs through the feature set.
The following points should be settled during the vendor conversation, so that you implement a solution that fits and keep the administrative effort to a minimum.
All the mobility categories you want, such as the Deutschlandticket or bike leasing, are integrated directly into an app that employees can use themselves. A mobility budget that runs on submitting and reimbursing receipts only creates unnecessary work. The settlement model has to match the HR capacity you actually have.
Tax classification happens automatically, including the question of what occurs when the monthly benefit-in-kind threshold is exceeded. A native connection to your own payroll system is therefore worth insisting on. When selecting a provider, make sure that technical setup takes no more than four weeks and that there is a named contact person. As for configuring the budget itself, the minimum requirement is that it can be differentiated by group and by location, and that there is a setting for whether unused amounts carry over.
It should also be possible to agree a pilot phase with defined locations and a defined period, so that the mobility budget can be tested on a smaller scale first.
Choosing gets easier once you know what you can realistically operate. A platform with thirty features is no help if nobody has time to configure twenty-five of them.
What does help is a solution that runs once it is set up. The categories the workforce actually uses sit in the app. The system handles the tax. The data reaches payroll without an intermediate step. What is left fits into an hour a month.
At persona service, a staffing company with more than 200 branches, that is roughly how it went: ten branches at the start in March 2023, more than 200 by August of the same year. Today the budget is actively used in 80 percent of branches. Starting with a limited pilot is almost always the better route for mid-sized companies, because it allows adjustments before they become expensive.
What does a mobility budget cost per month?
Costs consist of the budget itself plus a platform fee per user. The budget is the larger item and typically sits at 50 euros in mid-sized companies. Structured tax-free through the benefit-in-kind threshold and the public transport subsidy, no wage tax or social security contributions arise, so the cost to the company is broadly the amount distributed. Platform fees vary considerably by provider and contract, so it is worth comparing directly.
How long does implementation take?
Technical setup takes one to four weeks. Where a works council exists, allow a further four to eight weeks for consultation. Six to twelve weeks from decision to live operation is realistic. Starting with a pilot at a few locations lets you begin earlier.
What budget amount is typical?
50 euros a month has become the standard, because it matches the benefit-in-kind threshold exactly. 30 and 75 euros are also common. Where the budget replaces a company car, amounts are considerably higher, often between 250 and 300 euros a month, though the tax treatment then differs.
Does the works council have to approve it?
Where a works council exists, it must be involved. Co-determination follows from section 87 of the Works Constitution Act and applies to company pay structures and to the introduction of technical systems. With complete documentation on data protection, mobility policy and tax treatment, consultation typically takes four to eight weeks.
Can we switch providers later?
Technically yes, though not without effort. A switch means setting everything up again, communicating afresh to the workforce and, depending on the arrangement, a new round with the works council. So look for contract terms without long commitments when you first choose.
What happens to unused budget?
Every provider handles this differently. On many platforms the amount simply lapses at month end. A carry-over into the following month noticeably improves how the benefit is perceived, but it is not standard and should be raised explicitly during selection.
