Crew travel expenses are not a capture problem. They are a governance problem.
When cockpit, cabin and ground crew travel by definition, every rotation creates a tax event. Changing country-specific per diems, crew-specific collective agreements, shift logic and company agreements. The Travel Decision Layer decomposes every crew travel expense case into auditable micro-decisions and defines for each step: rule engine, collective agreement or human.
Complexity
Five dimensions that expense tools cannot model
Most expense tools are built for occasional business trips: an employee travels, fills in a form, the manager approves. In crew organisations, this does not work. Not because the volume is high, but because five complexity dimensions converge that standard tools cannot model.
Every employee travels. Always.
In crew organisations, travel is not the exception but the norm. Every rotation creates a travel expense case. With hundreds of rotations per day, manual capture is not an option but a system error.
Multiple jurisdictions per duty day
A single rotation can touch three, four or five countries in one duty day. Each country has its own per diem rate. The duration of stay determines whether the full or reduced rate applies. The combination changes with every rotation.
Collective agreements override statutory law
Cockpit, cabin, ground and maintenance crew typically have different collective agreements. Collective agreement per diem rates can override statutory rates. Company agreements add a further rule layer. The result: the same rotation can yield a different calculation depending on the staff group.
Irregularities are normal
Delays, hotel changes, crew repositioning, additional layovers. Every irregularity (IROP) changes location, duration and therefore the tax calculation. Expense tools expect planned trips. Crew operations are volatile by nature.
Governance at scale
When thousands of employees generate identical cases daily, every systematic error is multiplied. Wrong per diem on 50 rotations per day means: thousands of incorrect calculations per month. Tax audit risk is not an individual case but a structural risk.
One rotation. 40 to 120 micro-decisions.
A crew member flies a three-day rotation with layover. The Decision Layer decomposes this into individual decision steps:
| Step | Decision | Decider | Rationale |
|---|---|---|---|
| 1 | Read rotation from duty roster | Automatic | Data import, no decision |
| 2 | Determine country sequence | Rule engine | GPS or schedule: which countries, which duration |
| 3 | Select per diem per country | Rule engine | Country-specific rates per regulatory framework |
| 4 | Check collective agreement override | Rule engine | Crew-specific collective agreement overrides statutory rates |
| 5 | Calculate meal deduction | Rule engine | Provided meals reduce per diem deterministically |
| 6 | Classify IROP | AI | Delay, diversion, repositioning: AI classifies type |
| 7 | Recalculate IROP impact | Rule engine | Changed duration or country: recalculate per diem |
| 8 | Check layover hotel | AI + Rule engine | AI extracts hotel data, rule engine checks policy compliance |
| 9 | Map cost centre | Rule engine | Rotation to fleet, fleet to cost centre |
| 10 | Generate audit pack | Automatic | Sealed decision record per rotation |
Architecture and implementation
The Travel Decision Layer runs on Gosign's enterprise infrastructure: EU data residency, containerized, multi-tenant, no external dependencies. For aviation configurations, this means: crew planning system integration, real-time rotation data processing, and collective agreement-specific rule sets per staff group. Typical pilot projects start within 3 months with one crew group and one collective agreement.
Frequently Asked Questions
Can the Decision Layer handle multiple collective agreements simultaneously?
Yes. Each staff group (cockpit, cabin, ground, maintenance) can have its own collective agreement ruleset. The Decision Layer selects the correct ruleset per employee per rotation based on staff group classification.
How are IROPs (irregular operations) handled?
AI classifies the type of irregularity (delay, diversion, repositioning). The rule engine then recalculates the tax implications based on the actual itinerary rather than the planned rotation. The audit trail documents both the original plan and the actual execution.
Does the system integrate with crew planning tools?
The Decision Layer is configurable to read rotation data from standard crew planning systems. The integration maps duty rosters to tax-relevant events without requiring crew members to enter data manually.
What about cross-border rotations within a single duty day?
The Decision Layer calculates per diem rates for each country touched during a duty day, applying the correct rate based on duration of stay in each jurisdiction. This is deterministic, not estimated.
How complex is your crew travel expense logic?
In the Aviation Simulation, we configure the Decision Layer with your real-world scenarios: your collective agreements, your rotations, your crew groups.
Request Aviation Simulation