When using our Switzerland heavy vehicle charge reporting system, there may be situations where the data collected needs to be corrected — for example, if a journey wasn't properly recorded, a trailer was incorrectly assigned, or a VIN was entered with an error. To help ensure accurate toll declarations, we support several types of manual corrections, each designed for specific cases.

Below, you’ll find explanations of each correction type, along with examples.

🌎 Journey Corrections

Sometimes, your tracking device might log movement when your truck isn’t actually being driven. This can happen in special situations — for example, when the truck is being transported on another vehicle or the device has been removed from the truck.

Use the Journey Correction option to explain these situations and avoid incorrect tax-related records. You can also use it to report days with no driving, like during long breaks or holidays.

Correction	When to use	Example
No journey recorded	Use this to report days when your truck didn’t move at all, and you couldn’t access the tracking device. This is useful for planned breaks like holidays, maintenance, or storage.	Your truck is parked for a week during company holidays.
Truck being transported by another vehicle	Use this if the truck (or trailer) is being moved by another vehicle — like on a low-loader truck, train, or ferry — and is not being driven.	A truck with a trailer is loaded onto a transporter for delivery.
Device in transit (not installed in truck)	Use this if the tracking device is moving, but it’s not inside the truck — for example, it’s being shipped separately or sent for service.	The telematics device was removed from the truck and sent to another location, but still recorded movement.

🧾 Track Corrections

Use Track Correction to fix a regular journey declaration when the original data is missing or incomplete. This allows you to add missing distance and trailer details for a trip that wasn't properly recorded.

Correction	When to use	Example
Service failure	Use this if the telematics device couldn’t collect driving data due to a system error that lasted more than 5 minutes on a single day. This applies when a technical issue made it impossible to record the trip properly.	The telematics device temporarily stopped working and missed part of a journey.
Registration in progress	Use this if the service was already registered, but the activation process (commissioning) wasn’t fully completed when the journey occurred. This reason does not apply to device replacements — use Service Failure in those cases.	A vehicle was added to the system, but the telematics device hadn’t been fully activated before the truck started its route.
Journey without tracking device	Use this if the journey was made without the required tracking device (OBU) installed in the vehicle. This applies to any situation where the trip wasn’t recorded because the device was missing or not in use.	The truck made a delivery, but the telematics device had not yet been installed or had been removed.

🚛 Trailer Correction

Use Trailer Correction when the trailer information recorded for a journey was incorrect, but the driving distance was accurate. This lets you fix only the trailer details without changing the rest of the trip data.

Correction	When to use	Example
Incorrect trailer data	Use this if a journey was recorded with the wrong trailer settings — for example, the trailer ID or configuration was not accurate during the trip. This correction must match up with a previously recorded regular GNSS declaration (i.e., tracking data from the telematics device).	The system logged a journey with the wrong trailer assigned, and you need to update it to reflect the actual trailer used.

🔢 VIN Correction

Use VIN Correction when the Vehicle Identification Number (VIN) in one or more declarations was recorded incorrectly. This ensures that the data matches the correct vehicle and avoids issues with tax or system processing.

🔔It’s important to make VIN corrections within the first 10 days of the vehicle's registration, since manual data corrections through the Swiss HVC integration are only possible for the last 10 days.

If there is declarations with the wrong VIN, and more than 10 days have passed, please contact FOCBS (BAZG) directly through the Swiss ePortal and explain what needs to be corrected and why.

Correction	When to use	Example
Incorrect VIN	Use this if a declaration was accepted but had an incorrect or unrecognized VIN, resulting in an error like “VIN not found” or “no registration for VIN.” Once corrected, the system will confirm the affected declarations as valid. Make sure to apply the correction to all related incorrect entries.	A declaration was submitted with a typo in the VIN, causing it to be flagged by the system. This correction updates the VIN so the declaration can be processed properly.

How to make VIN corrections

Update the VIN in your vehicle's settings.
You will need to make the “Incorrect VIN” correction, for each day where the VIN was incorrect.
After submitting the VIN declaration corrections, all future declarations will use the updated VIN.

🔔If you submitted any type of corrections while the VIN was still incorrect, you will need to resubmit them after updating the VIN (regardless of if they were accepted or still pending). This must be done for each day affected by the incorrect VIN.

The declarations and corrections for those days will be accepted by FOCBS (BAZG) once the new VIN is confirmed.

🔁 Revocation

Use Revocation to cancel a manual correction that was previously submitted, if it was sent in error or needs to be withdrawn.

Correction	When to use	Example
Cancel manual correction	Use this if you need to cancel a manual correction that was already submitted. Keep in mind: this can only be done within 10 days after the original declaration period. If the deadline is missed, the request will be rejected with the message “refused – deadline missed.”	You realize that a manual correction you submitted last week was wrong, and want to cancel it before it is processed