Custom BCT integration development
Appfront builds integrations for taxi companies that want to use data from the Boordcomputer Taxi (BCT, in-vehicle taxi computer) in their own systems. Trips, shifts and working and rest times flow from the BCT or the supplier's back office into your planning, payroll and invoicing. And because the BCT is being replaced by a system that supplies data to the Centrale Database Taxivervoer (CDT, central taxi transport database), we build the integration so it can handle that transition.
What is a BCT integration?
For taxi transport, the Boordcomputer Taxi, or BCT, is mandatory. It records trips and the driver's working and rest times, with the driver logging in using a driver card. The Inspectie Leefomgeving en Transport (ILT) can read the data during an inspection, and the operator must also read and store it regularly. A transition period has been running since 1 July 2025, and from 1 January 2028 the BCT will be replaced by a system that supplies data to the Centrale Database Taxivervoer, the CDT.
In practice, data from the BCT is read out to meet the rules and then no longer used. Hours worked for payroll are tracked separately, trips for invoicing come from the planning, and nobody places them side by side. A difference between what was planned and what was driven goes unnoticed. And reading out and storing the data is manual work done vehicle by vehicle.
We build custom solutions because taxi companies differ: which BCT and supplier you use, which planning system, which payroll system, and how trips are invoiced. Which rules apply to your transport is set by legislation and monitored by the ILT; if you're unsure, check with your adviser or industry association. We make sure the data you already have works for your business too.
Data in your systems
Trips, services and times from the BCT or the supplier's back office, in your own planning.
Payroll and invoicing
Hours worked to payroll and trips to invoicing, without retyping.
Ready for the CDT
An integration that can handle the transition to a system for the Centrale Database Taxivervoer.
How we build your BCT integration
We start with your transport operation: which BCT and supplier, which planning and payroll systems, how data is read out today, and where work is duplicated. We also look ahead to the move to the CDT, so the integration does not have to be rebuilt in a few years, only the source changes.
Your BCT, supplier, planning, payroll and invoicing.
Trips, services and times from the BCT or the supplier's back office.
Data alongside the planning, passed to payroll and invoicing, with alerts when there are differences.
Preparation for the CDT, and ongoing management afterwards.
What a BCT integration actually does
The components below come up in almost every BCT integration. Which ones you need depends on your transport operation.
Reading out
Retrieve data from the BCT or back office.
Routes
Trips linked to planning and vehicle.
Times
Working and rest times per driver.
Payroll
Hours worked to payroll administration.
Invoicing
Rides driven to invoicing.
Differences
Planning alongside registration, with alerts.
Who we build a BCT integration for
The integration is intended for transport operators who want to do more with their BCT data.
Taxi companies
Many vehicles and drivers. Reading out the data is the core.
Contract transport
Rides per client. Invoicing matters most.
Dispatch centres
Multiple operators connected. A single overview is what's needed.
Software suppliers
Planning for taxi transport. The integration is the core.
Technology and integrations
This page covers integrations with the Boordcomputer Taxi. For booking and tracking trips, see our page on a taxi app, for driving times in goods transport see our page on tachograph analysis, and for driver passes and certificates see our page on certificate monitoring. You can read about how we work under custom software development.
Why choose Appfront for your BCT integration?
Data that is only read out to meet regulations is used only half as well. That is where we come in: trips and times in your own systems, payroll and invoicing without retyping, and an integration that survives the move to the CDT.
One source
Payroll and invoicing from the same records.
Differences made visible
Planned against driven, per trip.
Future-proof
The source changes, the integration stays.
Security and privacy for a BCT integration
The integration processes data about drivers, their working hours and trips, sometimes including passenger addresses. Access is set up by role, data is used only for the purpose it is needed for, and every exchange is logged.
The integration runs in a European data centre, with encrypted storage and daily back-ups. Data read out is kept for the period that applies to you.
Frequently asked questions about a BCT integration
Questions transport providers ask before they start.
The Boordcomputer Taxi (on-board taxi computer) is a mandatory system in taxis that records rides and drivers' working and rest times. The driver logs in with a driver card, and the ILT (Inspectorate for Transport) can read the data during an inspection.
From 1 January 2028, the BCT will be replaced by a system that supplies data to the Central Taxi Transport Database (CDT). Since 1 July 2025, a system that supplies data to the CDT may already be used. What this means for your business is something to discuss with your supplier or trade association.
Not if it is set up well. We separate retrieving the data from using it. When the switch happens, the source changes, but the integrations with scheduling, payroll and invoicing keep working.
From the BCT itself or, more often, from the BCT supplier's back office, using the options that supplier offers. We work out which route fits in the first step, together with you and the supplier.
Yes. Shifts and times from the registration go to payroll per driver, or are prepared for checking. How hours are paid follows your collective agreement and arrangements; the integration supplies the data.
The integration places them side by side and flags differences, such as a trip that was scheduled but not driven, or a shift that ran longer. This lets you correct invoices and hours before they go out.
For transport operators with many vehicles or contract transport, for dispatch centres with connected operators, and for planning software suppliers who want to use BCT data or, soon, CDT data.
BCT data that works for your business too?
Tell us which BCT and supplier you use, which scheduling and payroll system, and how you currently read out the data. We will show you what the integration looks like, including after the move to the CDT.