i-teq integration
Appfront builds custom integrations around i-teq, the Dutch Transport Management System from Centric. We connect your i-teq environment to accounting, customer portals, telematics, ERP, Portbase, eCMR and custom apps, via REST, XML and SOAP. That way i-teq is not an isolated planning system but the hub of a transport landscape that grows with you.
What is i-teq and what does an i-teq integration do?
i-teq is a Dutch Transport Management System supplied by Centric, building on the original Pionira package. The platform is aimed at transport and logistics companies and serves a broad spectrum: road transport, distribution, couriers, construction logistics and freight forwarders. i-teq handles planning, order processing, trip administration, invoicing, driver dispatching and reporting: in short, the heart of operational transport administration.
An i-teq integration makes sure this heart doesn't stand alone as an island. In practice, that means: orders that come in through your customer portal land in i-teq automatically, trip status is pushed back to shippers, invoiced trips flow smoothly into Exact, AFAS or Twinfield, driving data from Webfleet or Trimble enriches the planning, eCMR consignment notes are exchanged digitally, and BI dashboards draw on the i-teq database for management information.
Appfront builds these custom integrations for hauliers who need more than the standard i-teq functionality. We work through the i-teq REST API and XML integrations, fall back on SOAP services for legacy components where necessary, and tailor the integration to your market, whether you handle groupage, international freight or complex construction logistics. Our role is often that of the technical link between i-teq, your existing systems and the end users in the field.
TMS as the hub, not a silo
i-teq remains the source of truth for planning and orders, but it is fed by, and delivers data to, customer portals, accounting, ERP and telematics. Every department in the company works with the same data.
Track and trace for shippers
Through a customer portal, shippers get real-time insight into trip status, ETAs and PODs, fed by i-teq and your telematics partner. Fewer emails, fewer phone calls, higher customer satisfaction.
Accounting without double entry
Invoicing from i-teq flows automatically into Exact, AFAS or Twinfield with the right ledger accounts, VAT codes and cost centres. No manual retyping and no discrepancies between your TMS and the general ledger.
Our development process for i-teq integrations
We follow a proven methodology that surfaces the complexity of a TMS integration early and delivers a stable result. From mapping your i-teq environment and adjacent systems through to go-live and ongoing maintenance, every step is aimed at an integration that your own planners, administrators and drivers can trust.
We map out which i-teq modules you use, which other systems need to be integrated and which data flows take priority: orders, invoicing, telematics or reporting.
We design the integration architecture, choose between REST, XML or SOAP for each endpoint and work with Centric to set up the right API access rights.
Implementation with automated tests, structured logging and monitoring. You see working integrations along the way in an acceptance environment.
A controlled go-live with data validation and a safety net, followed by ongoing maintenance, monitoring and further development.
What an i-teq integration delivers in practice
Every i-teq integration is configured specifically for your type of transport, planning approach and adjacent systems. Below are the features we deliver most often for transport companies that use i-teq as their core system and want to connect the platform to their wider IT landscape. Our experience with custom TMS software comes together here with our API expertise.
Accounting integration
i-teq invoice lines flow automatically into Exact Online, AFAS Profit or Twinfield, with the right ledger accounts, VAT codes and cost centres. Incoming payments can be fed back so your accounts receivable are always up to date.
Customer portal and track and trace
A shipper portal where clients track their consignments, download PODs and submit orders. Data comes from i-teq and is enriched with real-time position updates from your telematics platform, so customers no longer need to call for trip status.
Telematics integration
Connect Webfleet, Trimble, Geotab or another telematics platform to i-teq: vehicle position, driving and rest times, trip assignments sent to the driver and POD signatures sent back to the TMS. Planning and execution work from the same real-time data.
Portbase and sea freight
For freight forwarders and container logistics: Portbase messages (Cargo Declaration, Notification of Arrival, Pre-Notification) linked to i-teq orders. Container status, customs handling and sea freight administration run in a single flow with your road transport planning.
eCMR and digital consignment notes
Digital CMR consignment notes in line with the eCMR protocol: signing by driver and consignee on mobile, automatic storage against the trip in i-teq, and exchange with clients and customs. Ready for the European requirement in 2026.
BI & data warehouse
A read integration from i-teq to your data warehouse or BI tool (Power BI, Looker, Metabase). Trip margins, vehicle utilisation, customer profitability and cost trends become visible without managers having to run SQL queries on the TMS.
Typical i-teq integrations in practice
An i-teq integration works out differently for every transport company. A number of scenarios come up again and again, and for each of them we have a working set-up that takes into account the particulars of i-teq and the specific rules around driver data, driving times and consignment notes.
Road transport and distribution
Medium-sized and large hauliers using i-teq for planning, trip administration and invoicing. We integrate i-teq with accounting, telematics and your customer portal, so planners, administration staff and drivers all work from a single source. Read more about our approach to transport software partnerships.
Freight forwarders and sea freight
Container logistics and sea freight forwarders with Portbase flows, customs handling and multimodal planning. We link Portbase messages to i-teq orders and make sure sea, road and rail transport are visible in a single trip overview for planners and customers.
Custom driver app
For hauliers who want to replace the standard i-teq driver app with their own mobile application, for example because they have non-standard workflows, want their own tone of voice or have specific offline requirements. The app talks to the TMS via the i-teq API and syncs as soon as a connection is available again.
Construction and specialist market segments
Construction logistics, couriers, dangerous goods and other market segments where i-teq drives the planning but specific documents, calculations or meetings call for custom screens or integrations. We build these extensions around i-teq, without blocking standard upgrades to the TMS.
Technology we use
We build i-teq integrations using the platform's available APIs: REST endpoints where possible, proprietary-format XML where that is the standard mechanism, and legacy SOAP services for components that have not yet been modernised. We tailor the backend stack to your IT landscape, so your own team can keep managing or further developing the integration over time.
Why choose Appfront for your i-teq integration?
Appfront has extensive experience with API integrations for transport and logistics organisations in the Netherlands. We always start with a thorough analysis of your i-teq environment and the surrounding systems, because a TMS integration must not only be technically sound but also add practical value for planners, administration staff and drivers.
For every integration, we write clear documentation and make sure your own team, or a future supplier, can understand and manage what is running. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. That keeps you independent and lets you stay in control of your integrations at any time.
You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication with Centric and speeds up decisions when choices have to be made during the build around data models, eCMR flows or telematics mappings.
Also take a look at our broader services around custom transport software, smart API integrations and the wider overview of integrations we build.
- Experience with i-teq REST, XML and SOAP integrations
- Specialist in transport and logistics software
- Familiar with accounting integrations to Exact, AFAS and Twinfield
- Telematics integrations with Webfleet, Trimble and Geotab
- Knowledge of Portbase, eCMR and the EU 561/2006 driving time rules
- Secure by default: API key rotation, scoped permissions, signature validation
- Structured error handling and retry mechanisms
- Extensive logging and monitoring from day one
- Clear documentation your planners and IT team can read
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
Security, GDPR and driving time legislation
Transport data is sensitive: driver personal data, driving and rest times, shipment information and payment data fall under both the GDPR and sector-specific rules. Appfront builds in line with OWASP ASVS and the specific requirements around driver data: minimal data collection, encrypted storage and strictly separated permissions per integration.
We document the data flows between i-teq, telematics, customer portal and accounting so that your record of processing activities is complete and you can demonstrably comply with the GDPR. For driving and rest times, we take EU Regulation 561/2006 into account: data is not retained for longer than legally permitted and is only accessible to roles that genuinely need it, such as planning or compliance officers.
For eCMR flows, we apply the TransFollow and OpenTrip standards and ensure that digital signatures, timestamps and signatory identity are recorded in a forensically tamper-proof way. More about our approach: information security policy and coordinated vulnerability disclosure policy.
- GDPR-compliant processing of driver and customer data
- EU 561/2006: driving times retained for the statutory retention period
- eCMR-compliant digital consignment notes with audit trail
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Automatic retry and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management following best practices
- Documentation for your record of processing activities
Frequently asked questions about i-teq integrations
Answers to the questions we are asked most often about i-teq integrations for transport and logistics companies.
i-teq is a Dutch Transport Management System (TMS) from Centric (formerly Pionira) that is widely used in the road transport and logistics sector for planning, trip administration, order processing, invoicing and driver dispatching. The platform supports specialist segments as well as general freight transport, couriers, distribution and construction logistics. An i-teq integration means getting i-teq to work together with other systems in your IT landscape, such as your accounting software, customer portal, telematics, ERP or eCMR solution.
We see a fixed set of recurring integration patterns around i-teq: integrations with accounting packages such as Exact, AFAS or Twinfield for automatic invoice and general ledger synchronisation; a customer portal with track and trace so shippers can follow trip status in real time; telematics integrations with Webfleet, Trimble or Geotab for vehicle and driving-time data; Portbase integrations for sea freight and container logistics; ERP integrations with SAP or Microsoft Dynamics; eCMR for digital consignment notes; BI and data warehouse integrations for reporting; and a mobile driver app or invoice recognition. Which combination you need depends on your market and existing systems.
Yes. For carriers with specific needs that don't fit within the standard i-teq functionality, we build custom flows around the platform, for example a dedicated order portal for large clients, an adapted costing module for specific rate structures, or a driver app that deviates from the standard. The custom layer talks to the TMS via the i-teq API, so the core stays stable and you can keep expanding independently.
i-teq offers a combination of REST endpoints, proprietary-format XML integrations and legacy SOAP services, depending on the module and version. For modern integrations, we preferably work via REST and webhooks; for older components or specific export/import flows, we fall back on XML or SOAP. We map out which endpoints are relevant to your scenario and agree the right documentation and environment arrangements with Centric before we start building.
The cost depends on the number of systems you want to integrate, the complexity of the transformation and validation rules between i-teq and the receiving system, whether the data flows one way or is synchronised in both directions, and the monitoring and maintenance arrangements you want. One-off integration costs at Centric and any licences for the other system also play a part. We always provide a clear quote after a no-obligation analysis of your situation.
Yes. Driver data, driving and rest times, and parcel data fall under the GDPR and specific EU regulations such as EU 561/2006 on driving times and the eCMR protocol for digital consignment notes. Appfront builds to OWASP ASVS, limits personal data to what is strictly necessary, uses encrypted connections and documents the data flows so that your record of processing activities is complete and you can demonstrably comply with the GDPR, driving-time legislation and eCMR requirements.
Yes. Appfront regularly takes over the management of existing i-teq integrations, even if they were originally set up by another party or put together by in-house IT. We review the API calls, error handling, monitoring and data quality, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions and ongoing maintenance.
An i-teq integration becomes particularly interesting if you already use or are considering i-teq and don't want the platform to stand alone as a silo. Typical profiles: medium-sized and large road hauliers, distribution companies, couriers, construction logistics, sea freight forwarders and logistics service providers with their own customer portal. The more adjacent systems you have (accounting, customer portal, telematics, ERP, BI), the more value an integration delivers.
Talk to us about your i-teq integration
Tell us how you use i-teq and which systems the platform needs to connect to: accounting, customer portal, telematics, ERP, Portbase or a custom app. We are happy to think along on scope, priorities, data model and coordination with Centric. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.