Modeling Regulatory Uncertainty: The German Truck Toll Through 2031 and Beyond

Ayush Mania

A Cost Variable That Eats the Decision

Germany's truck toll - Maut - is governed by the Bundesfernstraßenmautgesetz (BFStrMG). It has been amended twice in eighteen months: a CO2-based surcharge added in December 2023, then weight-class adjustments in July 2024. The rate that a heavy truck pays per kilometer now depends on its emission class. For a long-haul truck running 120,000 kilometers a year, the diesel-class rate of roughly 0.348 EUR per kilometer translates to about 41,760 EUR per year. Over a seven-year holding period, that is nearly 292,000 EUR. Zero-emission vehicles - battery electric, hydrogen fuel cell, hydrogen ICE - are exempt. Until June 30, 2031. What happens after that is unknown. The exemption could be extended. It could be replaced with a partial discount. It could be allowed to lapse, with ZEVs paying the same rate as the cleanest combustion class. The legislation has not been written.

The Real Calculation

If you are building a tool to help fleet operators choose a drivetrain for the next seven years, that uncertainty is the calculation, not a footnote on it.

Three Choices When Policy Doesn't Exist Yet

There are three honest things you can do with an unknown future rule. Pick a single number and document it.
Defensible if you are explicit, but invisible to the user. They see one TCO and do not know what it depends on. Refuse to project past the known horizon.
Cleanest, but useless for the actual decision - fleet operators are choosing trucks they will own through 2032 today. Model multiple scenarios as a user input.
Show the TCO under each scenario and let the user form their own view about which is plausible. I went with the third. The scenarios live in the UI as a radio toggle, with a default that is deliberately conservative.

The Three Scenarios

The tool models three post-2031 futures for ZEVs.

Scenario	ZEV rate after June 30, 2031	Where the number comes from
A. Full rate	Class 1 toll (~0.168 EUR/km)	The lowest-emission combustion class today. Floor assumption.
B. Partial discount	75% off Class 1 (~0.052 EUR/km)	Common policy precedent in EU emissions tooling.
C. Exemption extended	0.000 EUR/km	The current rule, projected forward.

Default is Scenario B. It is neither the worst case nor the best, and it forces the user to make a deliberate choice if they want either extreme. The toll is one of eleven cost components in the TCO model. Switching scenarios re-runs the calculation; the user sees the numbers move in real time. For a 120,000 km per year fleet over seven years, the three scenarios produce a roughly 290,000 EUR spread on the toll line alone - wider, in many cases, than the gap between drivetrains.

What This Forces You to Build

A scenario-toggleable cost component is a small UI feature on top of a larger architectural decision: no rate is a constant. Every toll, fuel price, electricity price, residual value matrix, and battery cost lives in JSON, not code. The UI exposes overrides for all of them. The reasoning is not hypothetical.

The CO2 component shifted in 2024 and may shift again as the EU revises Directive 2022/362.
Diesel and HVO prices are volatile enough that a six-month-old default is wrong.
Electricity contracts vary by site, by time of day, and by negotiating power. A single national average is a fiction useful only in the absence of better information.

Every default in the JSON has a comment that says where it came from and when it was last updated. The user is encouraged to override anything they have better data on. The result, when shared, is reproducible because the values are visible in the export.

Why "Conservative Default" Is Not Neutral

A common mistake in modeling tools is to treat the default as neutral and the override as the user's responsibility. Defaults are advocacy. Whatever you put in front of users on first load is the answer they remember, regardless of how many tooltips you add about it being adjustable.

Why not default to 'exemption extended'?

Why not default to 'full rate'?

Why partial discount in the middle?

This is a judgment call. The right answer here is that the user can change it, the tool tells them they can change it, and the documentation explains why the default is what it is.

Working Around Confidential Data

The cost defaults in this tool are informed by industry data that I cannot expose. The toll module does not reference any of it. The toll rates and scenarios come from public legislation - BFStrMG amendments, EU Directive 2022/362, published Toll Collect rates. This separation matters in two directions. The toll module is independently citable, which means it can be reused or audited without dragging confidential inputs along. And the proprietary cost defaults stay clean because no public regulatory data depends on them. If you are ever in a position where you need to publish part of a tool whose foundations are under NDA, build the public modules to stand alone from the start. Retroactive separation is an invitation to leak something you did not mean to.

What Generalizes

The pattern is not specific to German tolls. Any cost model that depends on a regulation will face the same problem the moment the regulation changes.

Identify the rates that are regulatory in origin. They are the ones you cannot negotiate and cannot predict.
Treat them as inputs, not constants. Even if they do not move during your modeling window, the next legislative cycle is rarely far away.
When the future is genuinely unknown, model the cases. A scenario toggle is honest. A single "best estimate" is a guess pretending to be an answer.
Document the source of every default. When the rule changes, you will want to know where to update from.

Regulatory uncertainty is normal. Treating it as an emergency every time it surfaces is the bug. The tool that survives the next BFStrMG amendment is the one where the amendment is a JSON edit, not a sprint.

Share this post: