Chiron guide · Flanders · IBP

How does Chiron work?

Since the reform of individually remunerated passenger transport (IBP) in Flanders, operators and drivers must meet new administrative obligations. Chiron is central to that system.

But concretely: what is Chiron and how does it work day to day?

In short

Chiron is not an app the driver opens on every trip. It is an official register fed by the operator’s management or dispatch software — at each key step: booking, departure and arrival.

Customer books → driver departs → trip ends → software sends to Chiron

What is Chiron?

Chiron is the digital platform of the Flemish government to register certain trip data carried out under IBP (individually remunerated passenger transport).

The goal is simple:

  • more transparency in the sector;
  • more efficient controls on the road and administratively;
  • compliance with Flemish regulations;
  • replacing certain manual administrative procedures with reliable digital transmissions.

Today, dispatch and management software can automatically send the required data to Chiron — without the operator re-entering every trip.

Chiron does not replace your business software. It connects to it: your management tool remains the centre of your activity; Chiron is the regulatory register.

Who must use Chiron?

Chiron mainly concerns actors of individually remunerated passenger transport in Flanders, under the IBP reform.

ProfileRole regarding Chiron
IBP operatorLegally responsible — must ensure trips are correctly declared
Transportbedrijf in FlandersMust connect its software to Chiron
Driver under IBP licenceGenerally does not interact directly with Chiron
Taxi software vendorSends data on behalf of the operator

Even if the driver never opens Chiron, their trip data can (and often must) be sent via their operator's software.

Do you work with Uber, Bolt or Heetch in Flanders? Obligations depend on your operator's framework and licence. See also: Chiron and Uber · Chiron and Bolt

How is a trip registered?

The system works on three key moments in the trip lifecycle. At each transition, connected software sends a message with the current trip status.

1. Booking (reservatie)

When a customer books a trip — by phone, app or platform — certain data is recorded and sent:

  • date and time of the booking;
  • planned pickup location;
  • administrative data required by regulations.

This step confirms a job has actually been planned.

2. Departure (vertrek)

When the job actually starts, a vertrek event is generated. This tells authorities the trip has actually started, not just booked.

3. Arrival (aankomst)

When the job is complete, an aankomst event is recorded. The trip is then considered closed in Chiron.

Horizontal timeline of the three Chiron statuses

Important: these are not three separate systems. It is a single flow — software sends the full trip status at every status change.

Does Chiron record payments?

No.

Chiron is not an invoicing or accounting system. Customer payments, platform commissions (Uber, Bolt, etc.), driver income and accounting data remain managed by your business software or platform.

Chiron and invoicing have different purposes: one tracks trips for regulatory compliance, the other manages your business activity.

Is Chiron mandatory?

Exact obligations depend on your activity, licence type and the regulatory framework in Flanders.

In practice, IBP operators must ensure that:

  • their internal processes meet Flemish authority requirements;
  • their tools (dispatch software, fleet management) can send the required data;
  • transmissions over time are complete and reliable.

Starting with IBP? See our guide: IBP-vergunning aanvragen in Flanders.

What happens if something goes wrong?

The most common mistakes are not bad faith, but a gap between reality and what Chiron receives.

ErrorPossible consequence
Missing bookingTrip not traceable from departure
Departure niet geregistreerdInconsistency during a control
Arrival ontbreektTrip considered unfinished
Incomplete dataTransmission rejected
Software ↔ Chiron connection issueData loss on one or more trips

These situations can cause problems during a roadside control or an administrative audit.

Sandbox vs production: two environments

Before sending real data, operators and software vendors usually test their integration in a sandbox environment (test), separate from production (real data).

EnvironmentUse
SandboxTests, certification, technical validation
ProductieOfficial transmissions of real trips

The sandbox → production transition is part of compliance. See: How to pass Chiron certification.

Why use software connected to Chiron?

Managing these declarations manually becomes unmanageable as trip volume grows — especially for fleets with multiple drivers or operators active on several platforms.

Software connected to Chiron enables you to:

  • automate transmissions at every status change;
  • reduce the risk of human error;
  • keep a history of sent events;
  • simplify administrative controls;
  • save time daily for the operator and drivers.

The driver keeps doing their job. Software handles compliance in the background.

Conclusion

Chiron has become a central part of individually remunerated passenger transport in Flanders.

Although the system remains largely invisible to drivers day to day, it plays a decisive role in regulatory compliance for IBP operators.

Understanding how it works — booking, departure, arrival — helps you anticipate administrative obligations and avoid mistakes that could cause problems during a control.

Next step

You now know how Chiron works. Next step: connect your company to the official portal.

Connect your company to Chiron

FAQ

Read more

This article is for information only. For regulatory decisions, consult official Flemish sources or your legal adviser.