i-teq integration
Appfront builds custom integrations around i-teq, the Dutch Transport Management System by Centric. We connect your i-teq environment with accounting, customer portals, telematics, ERP, Portbase, eCMR and your own apps, via REST, XML and SOAP. That way i-teq becomes 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, built on the original package from Pionira. The platform is aimed at transport and logistics companies and serves a broad range: road haulage, distribution, couriers, construction logistics and freight forwarders. Within i-teq you run planning, order processing, trip administration, invoicing, driver dispatch and reporting. In short, it is the heart of operational transport administration.
An i-teq integration ensures that this heart does not stand alone as an island. In practice, that means: orders received via your customer portal automatically land in i-teq, trip status is pushed back to shippers, invoiced trips flow smoothly into Exact, AFAS or Twinfield, vehicle data from Webfleet or Trimble enriches your planning, eCMR consignment notes are exchanged digitally, and BI dashboards draw from the i-teq database to provide management information.
Appfront builds these integrations to measure for hauliers who want more than i-teq's standard functionality offers. We work through the i-teq REST API and XML integrations, fall back on SOAP services where legacy components require it, and tailor the integration to your market, whether you do subcontracted haulage, 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 to customer portals, accounting, ERP and telematics. Every department works with the same data.
Track and trace for shippers
Through a customer portal, shippers gain real-time visibility of trip status, ETA and proof of delivery, 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 correct ledger accounts, VAT codes and cost centres. No manual retyping and no errors between the 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 management, every step is aimed at an integration your own planners, administration and drivers can rely on.
We map which i-teq modules you use, which other systems need to connect, and which data flows matter most, whether that's orders, invoicing, telematics or reporting.
We design the integration architecture, choose between REST, XML or SOAP per endpoint, and, together with Centric, set up the appropriate API access rights.
Implementation with automated tests, structured logging and monitoring. You'll see working integrations in an acceptance environment along the way.
Controlled go-live with data validation and a safety net, followed by ongoing management, monitoring and further development.
What an i-teq integration concretely delivers
Every i-teq integration is configured specifically for your type of transport, planning method and adjacent systems. Below are the functionalities we most often deliver 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 practice.
Accounting integration
i-teq invoice lines flow automatically into Exact Online, AFAS Profit or Twinfield, with the correct general 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 in which clients follow their consignments, download proofs of delivery 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 phone for trip status.
Telematics integration
Connect Webfleet, Trimble, Geotab or any other telematics platform to i-teq: vehicle position, driving and rest times, trip instructions sent to the driver, and POD signatures returned to the TMS. Planning and execution run on the same real-time data.
Portbase & sea freight
For forwarders and container logistics: Portbase messages (Cargo Declaration, Notification of Arrival, Pre-Notification) linked to i-teq orders. Container status, customs clearance and sea freight administration run in one flow alongside road transport planning.
eCMR & digital consignment note
Digital CMR consignment notes in line with the eCMR regulation: signed by driver and consignee via mobile, automatically stored against the trip in i-teq, and exchanged with clients and customs. Ready for the European requirement coming into force in 2026.
BI and data warehousing
A read-only 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 against the TMS.
Typical i-teq integrations in practice
An i-teq integration looks different for every haulage company. Several scenarios come up time and again, and for each we have a proven setup that takes into account the specifics of i-teq and the rules around driver data, driving hours and consignment notes.
Road haulage & distribution
Mid-sized and large hauliers using i-teq for planning, trip administration and invoicing. We integrate i-teq with accounting, telematics and customer portals, so planners, administration and drivers work from a single source. Read more about our approach to transport software partnerships.
Freight forwarding & sea freight
Container logistics and sea freight forwarders with Portbase flows, customs clearance and multimodal planning. We connect Portbase messages to i-teq orders and make sea, road and rail transport visible in one 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 different workflows, want their own tone of voice, or have specific offline requirements. The app communicates with the TMS via the i-teq API and synchronises when connectivity is restored.
Construction & specialist sectors
Construction logistics, couriers, dangerous goods or other specialist sectors where i-teq drives the planning but specific documents, calculations or meetings require their own 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 XML formats where that is the standard mechanism, and SOAP legacy services for parts not yet modernised. We match the backend stack to your IT landscape, so your own team can maintain or further develop 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 begin with a thorough analysis of your i-teq environment and adjacent systems. A TMS integration must not only work technically but also add practical value for planners, administration and drivers.
For every integration, we write clear documentation so that your own team, or a future supplier, can understand and manage what is running. No black box, just transparent code and clear agreements on monitoring, alerting and maintenance. This keeps you independent and in control of your integrations at all times.
You work with a dedicated point of contact who understands both the technical and the functional side. This keeps lines short, avoids miscommunication with Centric and speeds up decisions when choices need to be made during the build around data models, eCMR flows or telematics mappings.
You may also be interested in our broader services around custom transport software, smart API integrations and our 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 EU 561/2006 driving and rest time rules
- Secure by default: API key rotation, scoped permissions, signature validation
- Structured error handling and retry mechanisms
- Comprehensive logging and monitoring from day one
- Clear documentation that your planners and IT can read
- A fixed point of contact, no account managers passed around
- 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 the GDPR as well as sector-specific rules. Appfront builds in line with the OWASP ASVS and the specific requirements around driver data: minimal collection, encrypted storage and strictly separated permissions per integration.
We document the data flows between i-teq, telematics, the 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 kept longer than legally permitted and is only accessible to functions 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: our information security policy and responsible disclosure policy.
- GDPR-compliant processing of driver and customer data
- EU 561/2006 — driving times in line with the statutory retention period
- eCMR-compliant digital consignment notes with an 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 retries and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management in line with best practice
- Documentation for your record of processing activities
Frequently asked questions about i-teq integrations
Answers to the questions we most often receive 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 handling, invoicing and driver management. The platform supports both subcontracting and 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 package, customer portal, telematics, ERP or eCMR solution.
We see a fixed set of recurring integration patterns around i-teq: integration 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 XML integrations and legacy SOAP services, depending on the module and version. For modern integrations we prefer working 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, together with Centric, agree on the right documentation and environment arrangements before we start building.
Costs depend on how many systems you want to connect, the complexity of the transformation and validation rules between i-teq and the receiving system, whether the flow is one-way or bidirectional synchronisation, and the monitoring and maintenance arrangements you want. One-off integration costs with Centric and any licences for the other system also play a part. We always provide a clear quote following a no-obligation analysis of your situation.
Yes. Driver data, driving and rest times and parcel information fall under the GDPR and specific EU regulations such as EU 561/2006 on driving times and the eCMR directive 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 your record of processing activities is complete and you can demonstrably comply with GDPR, driving-time legislation and eCMR requirements.
Yes. Appfront regularly takes over existing i-teq integrations, even if they were originally set up by another party or built in-house. 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 adjustments, extensions and ongoing maintenance.
An i-teq integration becomes especially valuable if you already use or are considering i-teq and do not want the platform to operate as an isolated silo. Typical profiles include medium-sized and large road hauliers, distribution companies, couriers, construction logistics firms, 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 with — accounting, customer portal, telematics, ERP, Portbase or a custom app. We are happy to think along about scope, priorities, data model and alignment with Centric. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.