Does Chiron replace the transport ticket and duty sheet?

Yes: you still need the documents — even if your trips go to Chiron.

In Flanders, sending a trip to the central Chiron database replaces neither the duty sheet (dienststaat) nor the transport ticket (vervoerbewijs). These are three distinct obligations, with three audiences and three different proofs.

Three obligations, not one

For detail on both documents, see transport ticket and duty sheet, the duty sheet and the transport ticket.

What is Chiron?

Chiron is the Flemish government's rittendatabank: a digital platform that registers certain trip data under an IBP licence. Its goals are more transparency, more efficient controls and reliable digital transmissions instead of manual procedures.

See how Chiron works and the official page.

Chiron is not the driver's daily app

The driver works in the operator's software (dispatch, business app, linked taximeter). That software then sends the required messages to Chiron via the API. The driver usually does not open the Chiron portal for every trip.

To connect the company: connect your company to Chiron.

What is transmitted to Chiron?

Trip messages at key moments of the cycle: booking (reservatie), departure (vertrek), arrival (aankomst). Chiron receives data for the administration — not a copy of the day sheet, and not the ticket given to the customer.

A successful transmission proves a message was accepted. It does not prove a ticket was handed over, nor that a complete duty sheet was built during the duty.

Why Chiron does not replace the duty sheet

The duty sheet covers the entire day: start and end of duty, driver, vehicle, mileage, breaks, list of trips, distances (total and with passenger), prices, and depending on the vehicle GPS or taximeter totalisers.

Chiron mainly receives trip-related messages. It does not automatically rebuild a full day with breaks and end totals.

Example

A driver starts at 7 am, takes a 30-minute break at noon, completes eight trips and finishes at 4 pm. Eight arrival messages may be correct in Chiron. If the duty sheet does not record the start, break, totals or end, the day document remains incomplete — despite Chiron.

Why Chiron does not replace the transport ticket

The transport ticket is a document for the customer, given without them asking, at the end of each trip. It must carry the mandatory mentions (operator, vehicle, driver, sequential number, places, times, km, fare, price, complaints, etc.).

Chiron does not generate that ticket and does not hand it to the passenger. A trip visible in the administrative portal does not mean the customer received their vervoerbewijs.

The same software can manage all three — in 13 steps

Chiron, dienststaat and vervoerbewijs are not mutually exclusive. Compliant software can chain the three flows. Example operational path:

1. Open the duty with the correct driver and vehicle.
2. Record duty-sheet start data (time, mileage, location or totalisers).
3. Take or receive the trip booking.
4. Send the booking message to Chiron (when applicable).
5. Start the trip (customer on board).
6. Send the departure message to Chiron.
7. End the trip (drop-off).
8. Send the arrival message to Chiron.
9. Generate the transport ticket with mandatory mentions.
10. Actually give or send the ticket to the customer.
11. Check that the trip appears correctly in the duty sheet.
12. Record breaks and close the duty with end totals.
13. Verify archives (7 years) and consultability from the vehicle.

Example of a correctly managed trip

Before departure

• duty opened in the equipment;
• duty-sheet start data recorded;
• booking created and, if needed, sent to Chiron.

At departure

• trip started in the software;
• departure message sent to Chiron;
• the duty sheet continues to follow the day.

On arrival

• arrival message sent to Chiron;
• transport ticket generated and given to the customer;
• trip included in the duty sheet (times, places, distance, price).

Afterwards

• data stored securely;
• presentable during a check from the vehicle;
• archived for seven years.

If Chiron fails

An outage or API rejection does not cancel the other obligations. The duty sheet and transport ticket must still be produced. Then: diagnose the error, resend or correct the transmission per the provider's procedures and the Chiron error list, and check that the trip appears in the portal.

If Chiron is OK but there is no ticket

Possible shortfall on the transport ticket. The trip may be correct for the administration and incorrect for the customer. The driver must hand over the vervoerbewijs without the customer asking.

If the trip is in Chiron but not in the duty sheet

Possible shortfall on the dienststaat. Chiron and the duty sheet do not sync by magic: the software must write to both flows. An incomplete day remains a control risk, even with green Chiron messages.

Still required for a licence application

The IBP licence application often asks for a sample duty sheet and a sample transport ticket, in addition to the ability to connect to Chiron. See TaxiGer for a licence application.

Watch old article numbers: older documents referred to articles 33 and 34 of the 2019 decree. In the Flemish Government Decree of 9 June 2023, the rules mainly appear in articles 33 to 36 (secured equipment, duty sheet, transport ticket, presentation and retention).

Retention: seven years

Secured duty-sheet and transport-ticket data must be kept for seven years and presented on request by competent officers. The Chiron history does not replace this operator archive.

During a check, “everything is in Chiron” is not enough

That is not sufficient. The driver must be able to present the secured duty-sheet and ticket data from the vehicle equipment, in a readable form. Pointing to the administrative portal does not replace that presentation.

Verify the software: three checklists

1. Chiron checklist

• company connected (test then production);
• booking / departure / arrival messages accepted;
• API errors detected and handled;
• history consultable to check transmissions.

2. Duty-sheet checklist

• start data recorded at opening;
• breaks and trips included during the day;
• end totals coherent (km, prices, number of trips);
• consultable from the vehicle.

3. Transport-ticket checklist

• generation at the end of each trip;
• mandatory mentions present;
• actual hand-over to the customer (paper, email, SMS, etc.);
• reliable link between the ticket and the trip performed.

Errors to avoid

• believing a Chiron transmission replaces duty sheet and ticket;
• handing over the ticket only if the customer asks;
• rebuilding the sheet at month-end without recording during the duty;
• being unable to present data from the vehicle;
• confusing a licence sample with daily production;
• ignoring API failures for lack of alerts;
• forgetting seven-year retention.

What an operator should remember

Three functions, three proofs: Chiron for the administration, the duty sheet for the driver’s day, the transport ticket for the customer. One software can manage everything, but an “OK” trip in Chiron proves neither a complete duty sheet nor a ticket handed over.

Go further: taxi documents hub and TaxiGer features.

FAQ

Official sources

• Flanders — Chiron trip database
• Official Chiron starter guide
• Flemish Government Decree of 9 June 2023 — articles 33 to 36
• Flemish Decree of 29 March 2019 — individual paid passenger transport
• Flanders — Licence for taxi services
• Flanders — Taxi types and conditions