AI Travel Logistics. 95% Zero-Touch. GPS Instead of Forms. One Agent.
Cross-border trips. EU Mobility Package. Zero manual input.
The AI Agent classifies country assignment and duration from GPS and telematics data. The rule engine calculates per diems and posting documentation deterministically. The driver drives, the system decides.
Cases/year (simulation)
Zero-touch rate
EU/EFTA + UK jurisdictions
High rule complexity
Cases and zero-touch: Gosign simulation model. Jurisdictions: EU/EFTA coverage. EU Mobility Package: Directive 2020/1057.
What the Agent classifies
30+ EU/EFTA + UK jurisdictions, one agent
Border crossings multiple times daily, changing per diems, posting documentation. You know the complexity. Here's how the AI Agent solves it:
GPS-based country assignment
Drivers cross borders multiple times per day. The AI Agent reads GPS coordinates from telematics systems and classifies each segment to its jurisdiction. The rule engine then calculates country-specific per diems based on actual location and duration - no forms, no manual input, no delay.
EU Mobility Package auto-documented
Directive 2020/1057 requires posting documentation for cross-border operations. The AI Agent classifies country of operation and duration from GPS data. The rule engine generates the data basis that compliance teams need for reporting - automatically, for every trip, without creating additional burden for drivers. (UK: The EU Mobility Package does not apply post-Brexit. UK operator licensing and driver CPC regulations are mapped separately.)
Fleet-wide consistency
500 trucks cross the same borders daily. The AI Agent applies identical classification rules to identical routes. The rule engine calculates identical per diems for identical journeys - eliminating person-dependent variation across the entire fleet. Audit risk eliminated at the source.
Zero-touch driver mode
The driver's job is driving, not administration. The AI Agent operates in zero-touch mode: GPS data in, country classification done, per diem calculation out, payroll export ready. The driver never sees a form. Queries only for genuine exceptions - GPS gaps, new routes, edge cases.
Minute-precise border crossing timing
A truck crosses the German-Polish border at 23:45, continues to Czech Republic at 00:15. The AI Agent classifies three country segments with minute-level precision. The rule engine calculates pro-rata per diems based on actual crossing times - three countries, one working day, correct to the minute. Manual capture cannot achieve this precision.
One driver tour. 15 to 40 micro-decisions.
A driver runs a three-country tour with an overnight stay. The Decision Layer decomposes this tour into individual decision steps:
| Step | Decision | Decider | Rationale |
|---|---|---|---|
| 1 | Read GPS track from telematics | Automatic | Data import, no decision |
| 2 | Determine country sequence and duration | Rule engine | GPS coordinates mapped to jurisdictions |
| 3 | Select per diem per country | Rule engine | Country-specific rate per applicable framework |
| 4 | Calculate midnight border crossing | Rule engine | Pro-rata calculation when crossing at midnight |
| 5 | Check long-term posting threshold | Rule engine | Duration-based thresholds per jurisdiction |
| 6 | Generate EU Mobility Package data | Automatic | Posting documentation data for compliance |
| 7 | Map to fleet cost centre | Rule engine | Vehicle to fleet, fleet to cost centre |
| 8 | Generate payroll export | Automatic | Posting-ready per diem data |
| 9 | Check rest time compliance | Rule engine | Driving and rest periods checked against EU Regulation 561/2006 |
| 10 | Generate audit file | Automatic | Sealed decision record per driver tour |
Simulation
Calculated for logistics volumes
We configured the Travel Decision Layer with realistic logistics parameters and ran the numbers. The results show what changes at enterprise fleet sizes.
Simulation parameters
| Fleet | 200 to 2,000+ vehicles (owned and subcontracted) |
| Drivers | 300 to 3,000+ (with various contract models) |
| Cases/year | 500,000 to 2,000,000+ |
| Jurisdictions | 30+ EU/EFTA + UK jurisdictions |
| System integration | Telematics → Decision Layer → ERP/Payroll |
| Border crossings/day | 500 to 5,000+ (fleet-dependent) |
Before / After
| Dimension | Manual | Decision Layer |
|---|---|---|
| Processing cost | from EUR 53 (GBTA)* | < EUR 5 |
| Error rate | 19% (GBTA) | < 0.1% |
| Lead time | 5 - 12 business days | Minutes |
| Zero-touch rate | 0% | 95% |
| Audit-readiness | Manually reconstructed | Automatically generated |
| EU Mobility Package data | Manually captured | Automatically generated |
| Driver queries | 3 - 5 per week | < 0.1 per week |
* GBTA Foundation 2024: USD 58 per transaction (approx. EUR 53). Logistics cases with GPS-based country detection are significantly cheaper in zero-touch mode. EU Mobility Package: Directive 2020/1057. Simulation results: Gosign model calculation.
In the simulation, the Decision Layer achieves a zero-touch rate of 95% - for standard routes with GPS coverage. The remaining 5% involve GPS gaps, new routes and edge cases. For all cases, a complete, audit-proof decision record is available. Drivers do not fill in forms.
Architecture and implementation
The Travel Decision Layer runs entirely on your infrastructure: your data centre, your network, your control. No SaaS dependency, no data leakage. For logistics configurations, this means: telematics interfaces for GPS data import, real-time border crossing processing, and fleet-wide per diem calculation across 30+ EU/EFTA + UK jurisdictions. Typical pilot projects start within 3 months with one fleet group and the most-travelled routes.
Deep Dive in the Agent Briefing
Our article series for decision-makers implementing AI agents in the enterprise.
Travel Decision Layer in Other Industries
Each industry has its own tariffs, cost structures, and complexity drivers. The Decision Layer is the same. The configuration is industry-specific.
Frequently Asked Questions
Does the system work with existing telematics systems?
The Decision Layer is configurable to read GPS data from standard telematics providers. The integration maps location data to tax-relevant country and duration calculations without additional hardware.
How is the EU Mobility Package handled?
The Decision Layer generates the data basis for posting documentation as required by Directive 2020/1057. This includes country of operation, duration and applicable periods. Legal assessment and regulatory reporting remain with your compliance and legal teams.
What happens when GPS data is unavailable?
The Decision Layer falls back to planned route data from dispatch systems. Cases with GPS gaps are flagged for review. The audit trail documents which data source was used for each calculation.
Can it handle mixed fleets (owned and subcontracted)?
The Decision Layer supports multi-tenant configurations. Owned fleet and subcontracted vehicles can operate under different rule sets and cost allocation models within the same system.
How does a project start in practice?
In a 30-minute call, we clarify your parameters: fleet size, routes, telematics systems. This produces a pilot proposal: one fleet group, the most-travelled routes, one data flow. Typical pilot projects start within 3 months.
Let us run the numbers.
30 minutes. Your fleet size, your routes, your result. We configure the Decision Layer with your real parameters.
Book a Call