Custom BCT integration development
Appfront builds integrations for taxi companies that want to use the data from the Boordcomputer Taxi (on-board 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 (central taxi transport database), we build the integration so that it carries over to the new system.
What is a BCT integration?
For taxi transport, the Boordcomputer Taxi (BCT, on-board taxi computer) is mandatory. It records trips and the driver's working and rest times, and the driver logs in with a driver card. The Human Environment and Transport Inspectorate can read out the data during an inspection, and the operator must also read out and retain 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 (CDT, central taxi transport database).
In practice, the data is read out of the BCT to comply with the rules, and then not used again. Hours worked for payroll are tracked separately, trips for invoicing come from the planning, and nobody puts them side by side. A difference between what was planned and what was driven goes unnoticed. And reading out and retaining the data is manual work done vehicle by vehicle.
We build custom software because taxi companies differ: which BCT and which supplier you use, which planning system, which payroll administration, and how trips are invoiced. Which rules apply to your transport is determined by legislation and enforced by the ILT (the Dutch Human Environment and Transport Inspectorate); if in doubt, check with your adviser or trade association. We make sure the data that already exists works for your business too.
Data in your systems
Trips, shifts and times from the BCT or the supplier's back office, in your own planning system.
Payroll and invoicing
Hours worked go to payroll and trips go to invoicing, with no retyping.
Ready for the CDT
An integration that survives the switch to a system for the Central Taxi Transport Database (CDT).
How we build your BCT integration
We start with your transport operation: which BCT and supplier, which planning and payroll systems, how data is currently read out, and where work is duplicated. We also look ahead to the switch to the CDT, so the integration doesn't have to be rebuilt in a few years' time and only the source changes.
Your BCT, supplier, planning, payroll and invoicing.
Trips, shifts and times from the BCT or the supplier's back office.
Data alongside the planning, into payroll and invoicing, with alerts when figures differ.
Preparing for the CDT, and maintenance after that.
What a BCT integration actually does
The components below feature in almost every BCT integration. Which ones you need depends on your transport operation.
Retrieval
Retrieving data from the BCT or back office.
Trips
Trips linked to planning and vehicle.
Times
Working and rest times per driver.
Payroll
Hours worked into the payroll administration.
Invoicing
Completed trips into invoicing.
Differences
Planning compared with registration, with alerts.
Who we build a BCT integration for
The integration is intended for 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
Trips 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 is about integrations with the Taxi On-Board Computer (BCT). For booking and tracking trips, see our page on a taxi app; for driving times in goods transport, our page on tachograph analysis; and for drivers' passes and documents, our page on certificate monitoring. You can read about our approach on software development.
Why Appfront for your BCT integration?
Data that is only read out to comply with the rules is only half used. That is what we build on: trips and times in your own systems, payroll and invoicing without retyping, and an integration that survives the switch to the CDT.
One source
Payroll and invoicing from the same registration.
Differences made visible
Planned versus driven, per trip.
Future-proof
The source changes, the integration stays.
Security and privacy in a BCT integration
The integration processes data about drivers, their working hours and trips, sometimes including passenger addresses. Access is set up per role, data is only used 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 backups. Data that is read out is retained for the period that applies to you.
Frequently asked questions about a BCT integration
Questions operators ask before they get started.
The Taxi On-Board Computer (BCT) is a mandatory system in taxis that records trips and drivers' working and rest times. The driver logs in with a driver card, and the ILT can read out the data during an inspection.
From 1 January 2028, the BCT (taxi on-board computer) will be replaced by a system that supplies data to the Central Taxi Transport Database (CDT). A system that supplies data to the CDT may already be used since 1 July 2025. What that means for your business is something to discuss with your supplier or industry association.
Not if it has been set up properly. We separate retrieving the data from using it. When you switch, the source changes, but the integrations with planning, 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 look at 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 review. How hours are paid follows your collective labour agreement and arrangements; the integration supplies the data.
The integration puts them side by side and flags differences, such as a trip that was planned but not driven, or a shift that ran longer. That way you can correct invoices and hours before they go out.
For carriers with many vehicles or contract transport, for dispatch centres with affiliated operators, and for planning software suppliers who want to use BCT data or, soon, CDT data.
BCT data that also works for your business?
Tell us which BCT and supplier you use, which planning and payroll systems, and how you currently read out the data. We'll show you what the integration looks like, including after the switch to the CDT.