Connect your fleet systems in Benelux and France

A fleet operating between Belgium, the Netherlands, Luxembourg and France often already has a TMS, telematics, fuel cards and an accounting system. The useful question is which work still falls between them: entering an order twice, matching a fuel transaction to a truck, or chasing the delivery document. Konvoi connects supported systems and uses their data to support that follow-up.

Keep a clear owner for each record

Let the TMS own the transport order and the telematics provider supply measured positions. Keep accounting responsible for the books. Agree which system may change each record before connecting them. An integration that copies data both ways without that agreement can produce conflicting orders and duplicate documents.

The FleetGO eTrans connector illustrates this approach: orders owned by eTrans remain read-only in Konvoi Orders. Orders created in Konvoi can be sent to eTrans. Setup is on request and depends on access to the relevant API.

Start with one cross-system job

Job	Existing sources	What Konvoi adds
Check a fuel purchase	Fuel-card export, vehicle position and tank level	Links the transaction and the available evidence for review
Follow an eTrans order	TMS status and delivery documents	Brings execution updates and documents into Konvoi Orders
Prepare maintenance	Vehicle record, inspection and workshop	Connects the reported problem to workshop follow-up
Collect fleet documents	Email attachments and vehicle records	Reads documents for review and tracks recorded expiry dates

Pick a small sample of real trucks and records. Include a missing document, a corrected transaction and an unavailable source in the acceptance test. A useful integration shows what failed and can retry without duplicating the work.

Use the languages and documents your team already works with

For Belgian teams, test Dutch and French documents together. For the Netherlands, check Dutch sender formats and the identifiers used by your own TMS. For Luxembourg, check the languages your office and drivers actually use. For France, include French supplier exports and delivery paperwork. These are onboarding checks, not promises of country-specific fiscal or legal coverage.

Konvoi’s website is available in English, Dutch and French. Its AS24 importer reads the Dutch and French XLSX layouts. Its Transics connection and Ruptela connection bring supported telemetry into the fleet view. Check the method and fields for your provider rather than assuming that every integration is live or bidirectional.

Know what is connected today

The integration catalogue separates API connections, tracker connections, file imports, email processing and app connections. Availability is shown separately. FleetGO eTrans setup is on request; TAS and Mendrix are not available connectors today. Remote tachograph downloads and a complete accounting workflow need specialist systems.

An API and webhooks can support additional integrations, but an API’s existence does not mean a connector to your software has already been built. Bring the product name, version, sample exports and required data direction to the integration discussion.

Verify a useful result before expanding

Test one complete job across the connected systems. Check the vehicle or customer match, source timestamps, ownership, duplicate handling and who can approve changes. Compare the manual steps before and after. Then expand to the next workflow. Review the available connections or see pricing.