The Mobility Budget Playbook for Swiss Employers — Turning Parking Allocation from a Fixed Cost into a Flex Benefit

For two decades the corporate parking question in Switzerland was a binary: do you give every senior employee a named spot, or do you not? The answer drove a hard, fixed line in the operating budget — typically CHF 200–350 per spot per month in central Zürich, Geneva, Basel, and Bern — allocated by seniority rather than need. A second, quieter answer is now emerging from Belgium, the Netherlands, and France and finally arriving in Switzerland: the mobility budget. Instead of a fixed spot, the employer gives a monthly mobility wallet that the employee spends on whatever combination of parking, transit, e-bike, or car-share works for their week. This article is the playbook for Swiss CFOs and HR directors evaluating the model, with the real numbers and the operational pre-requisites that make it actually work.

What a mobility budget actually is

A mobility budget is a benefit construct in which the employer allocates a monthly cash-equivalent amount — typically CHF 150–400 in a Swiss context — that the employee can spend across a set of pre-approved mobility categories. The categories typically include:

• Parking: on-site dedicated spot, on-site pool/flex spot, or external lot — charged at actual usage, not a fixed monthly fee.
• Public transit: SBB GA, monthly passes, point-to-point tickets — reimbursed against receipt or via a corporate framework agreement.
• Active mobility: e-bike leasing (typically CHF 80–140/month including service), bike-share credits, scooter-share.
• Shared mobility: Mobility CarSharing credits, car-sharing apps, occasional rental.
• Home-office allowance (sometimes): some Swiss programmes let an employee redirect a portion of an unused mobility budget into a home-office equipment top-up — this overlaps with separate fringe-benefit codes and needs careful tax modelling.

The construct originated in Belgium (formalised in 2019 as the Mobiliteitsbudget) and has since spread to the Netherlands, France (Forfait Mobilités Durables), and Germany. The Swiss version is not codified by federal law but is being adopted by individual employers under existing fringe-benefit rules — primarily large corporate tenants in Zürich, Geneva, Lausanne, and Zug who face both a structural parking shortage and an employee base that mostly arrives via public transit anyway.

Why mobility budgets are arriving in Switzerland in 2026

Three forces line up at the same time:

1. Cantonal zoning is tightening the maximum spot count, not just the minimum. Zürich, Geneva, and Basel-Stadt have all reduced the maximum allowed spots per square metre for new commercial builds in the past three years. Employers literally cannot allocate a spot per employee any more, even if they wanted to.
2. The hybrid-work residual means 30–55 % of headcount is in the office on any given day in Swiss corporate offices (Deloitte CH 2025 survey). Static allocations are 45–70 % over-provisioned by construction.
3. Talent retention: under-35 employees in Swiss cities increasingly prefer transit and active mobility. A «take the parking spot or take nothing» benefit lands poorly. A mobility wallet lands well.

Combined: Swiss employers are paying for parking that no one uses, while their younger employees would prefer a cash-equivalent benefit they can spend on the GA train pass they already buy. The mobility budget closes the gap.

The Swiss tax treatment, in plain language

Swiss fringe-benefit taxation is governed by the Federal Direct Tax Act (DBG) and the cantonal income tax codes. Different mobility-budget components are treated differently:

The practical pattern Swiss employers converge on: keep the mobility budget in-kind wherever possible (book the parking, the transit pass, the bike lease directly), and only convert the residual into cash if the employee explicitly requests it — with the residual taxed as salary. This keeps the construct unambiguously a fringe benefit rather than deferred compensation, and avoids the worst of the cantonal-interpretation patchwork.

The operational pre-requisite that most programmes get wrong

A mobility budget on paper is easy. A mobility budget that actually saves money depends on one thing: knowing who used a parking spot on which day. Without that data, the rest of the construct collapses:

• You cannot reduce dedicated allocations because you have no evidence of under-use.
• You cannot credit unused capacity back to the employee wallet because you do not know there was unused capacity.
• You cannot convert «parking» into a per-day line item in the employee’s expense report because you have no per-day data.
• You cannot enforce a cap of «parking covers 12 days/month» because you do not know how many days a person parked.

This is why most Swiss mobility-budget pilots from 2023–2024 underperformed. They launched the wallet without changing the parking operational layer. The dedicated spots stayed allocated, the costs stayed fixed, and the only savings came from employees who voluntarily gave up their spot. Voluntary opt-out averaged ~8 % — not enough to move the budget needle.

The architecture that works is the inverse:

1. First: convert all parking to a pool/flex model with ANPR-based access (see our access-control article). Each entry/exit is logged against the plate, the plate maps to an employee. You now have per-employee, per-day usage data.
2. Second: introduce dynamic pricing within the pool (dynamic pricing playbook) so that a parking-day has a marginal cost, not a fixed cost. Now you can debit a wallet per usage.
3. Third: launch the mobility wallet on top, with parking-days as one of the line items the wallet covers.

Steps 1 and 2 do not require step 3 to deliver value — they are the standard parking-optimisation engagement Stellos sizes via the audit calculator. Step 3 multiplies their value because the saved capacity now becomes an HR/finance lever, not just an asset-NOI lever.

Real numbers: a 200-employee Zürich office

Concrete scenario. Mid-size professional-services firm, leased floor in a central Zürich building. 200 employees on the payroll. Hybrid policy — office attendance averages 60 % (so ~120 people in the building on a typical Tuesday/Wednesday/Thursday; ~50–70 on Mondays and Fridays).

Today (status quo)

• 80 dedicated parking spots in the building’s parking deck, allocated to senior staff by tenure.
• Spot cost: CHF 250/month, paid by the firm to the building landlord. Annual: CHF 240,000.
• Of those 80 spots, internal surveys suggest ~30 are used most days, ~25 are used 1–3 days/week, ~25 are essentially unused (senior staff who now mostly take the train or work hybrid).
• The other 120 employees: no benefit at all. Some buy GA train passes (CHF 3,995/year) out of pocket; some have employer-paid transit reimbursement (~CHF 80/month) but on an ad-hoc basis.

After mobility-budget rollout

• Dedicated spots eliminated. 50 pool spots retained, accessed via ANPR. Marginal cost per parking-day: CHF 18 (calculated from the building’s lease cost amortised over 220 working days × 50 spots, plus a small operating margin).
• Every employee receives a CHF 200/month mobility wallet (CHF 250/month for the previous spot-holders, grandfathered for 24 months as a retention concession).
• Employees self-route: heavy parkers (still ~30 people) spend ~CHF 200 of their wallet on parking-days at CHF 18 each = ~11 days/month. Light/occasional parkers split between parking-days and transit reimbursement. Pure transit users put the full CHF 200 against an SBB GA or a regional pass.

Annual P&L comparison

At first glance the «after» number is more than double. That is the wrong comparison. The right comparison is total benefit-spend per employee, and what each employee receives:

• Today: 80 employees receive a CHF 3,000 annual benefit (the parking spot); 120 receive ~CHF 500. Per-head average: ~CHF 1,500.
• After: 200 employees receive a CHF 2,400 annual benefit (the wallet) plus parking access on demand. Per-head average: CHF 3,375.

The CHF 675k programme delivers more benefit per employee, distributed more equitably, while freeing the company from 30 spots’ worth of waste. The CHF 375k cost difference vs status quo is a re-direction of compensation budget, not new spend — in practice most firms fund it by reducing the next year’s salary-increase pool by 1.5–2.0 pp on the assumption (well-supported by the BE/NL/FR data) that employees value the mobility benefit at roughly its cash value, sometimes more.

Alternative model with no compensation re-direction: keep the wallet at CHF 100/month and the savings vs status quo become CHF 60,000 net positive after operational layer. This is the «pure cost reduction» framing and is the easier sell to a CFO who does not want to redirect compensation.

Implementation timeline for a 200-300-employee Swiss corporate tenant

The standard rollout sequence:

Total elapsed time from board approval to steady-state: typically 4–6 months. The longest single line item is the tax-treatment design because it requires a cantonal-specific written opinion from the tax advisor; budget 3–4 weeks for it and start that workstream in parallel with weeks 1–2 of the audit.

Compliance and zoning interaction

A mobility-budget programme intersects three other Swiss regulatory layers covered in our Swiss parking compliance 2026 article:

• Cantonal zoning maxima: Zürich and Geneva allow employers to reduce their building’s parking-maximum allocation by 15–25 % if they can document a verified mobility-budget programme. The reduction is granted after first-year usage data is submitted to the cantonal Bauamt. This can free leased square-metres or, in a new build, reduce parking-deck construction cost.
• FADP / DSG: ANPR-based per-employee parking tracking is personal data. The legal basis is the employment relationship plus explicit opt-in for the wallet, documented in the HR policy. Retention should match the wallet’s billing cycle (typically 90 days post-month-end).
• CO₂ reporting: a mobility budget that shifts employees from car to transit reduces the building’s scope-3 commuting emissions. Most large Swiss employers now report this in their sustainability disclosure; a documented mobility-budget programme is a strong evidence base.

The Stellos operational layer underneath

Stellos provides the parking operational layer that mobility-budget programmes depend on: ANPR-based access, pool-parking allocation, per-day usage data, integration with the wallet/expense system on top. The audit calculator sizes the parking-side of the equation — spot reduction, marginal cost per parking-day, and CAPEX recovery — which is the input HR/finance needs to model the full mobility-budget P&L.

A typical engagement: Stellos delivers the parking operational layer in weeks 5–14 of the timeline above (vendor procurement through soft launch). The wallet/expense layer is usually a separate vendor (often inside the existing HR stack — SAP SuccessFactors, Workday, or a Swiss-specific platform like Abacus or Bexio) that consumes Stellos’ per-day usage data via API.

The two-paragraph board-pack summary

A mobility budget converts the corporate parking line from a fixed cost (CHF 240k/year for 80 dedicated spots at a 200-employee Zürich office) into a flexible per-employee benefit that distributes more evenly across headcount, freed of the structural over-provisioning that hybrid work has created. The construct is well-understood in Belgium, the Netherlands, and France, and arrives in Switzerland under existing fringe-benefit rules — primarily by keeping the components in-kind (parking, transit pass, bike lease) and treating any cash residual as ordinary salary.

The model only works on top of a dynamic parking operational layer that delivers per-employee, per-day usage data — without it, the fixed allocations stay fixed and the savings do not materialise. Implementation is typically 4–6 months from board approval to steady state. For a 200-employee Swiss office, the choice between «pure cost reduction» (CHF 100/month wallet, CHF 60k annual saving) and «compensation re-direction» (CHF 200/month wallet, equitable distribution, modest cost increase offset by next-cycle salary-pool adjustment) is the headline strategic decision the CFO and CHRO make together.