Consulting expenses are not a volume problem. They are a split problem.
When every trip serves multiple clients and every day has a different cost centre, the question is not 'how much' but 'who pays what, and why'. The Travel Decision Layer decomposes every consulting expense case into auditable micro-decisions. Three-way split: tax treatment, client allocation, internal cost. Each split documented, each reproducible, each audit-proof.
Three dimensions that expense tools ignore
The three-way split
Every consulting expense has three cost perspectives: tax treatment (deductible, partially deductible, non-deductible), client allocation (billable, non-billable, mixed), and internal cost assignment (cost centre, project, overhead). Most expense tools handle one. The Decision Layer resolves all three simultaneously.
Multi-client weeks
A consultant visits Client A on Monday and Tuesday, Client B on Wednesday, travels home Thursday. The hotel covers three clients. The per diem changes mid-week. The cost allocation must be split by day, by client, by tax treatment. Manually: error-prone. Deterministically: trivial.
Policy enforcement vs. client expectations
Internal travel policies and client-specific budgets often conflict. First-class flight policy meets client economy-only rule. The Decision Layer enforces the stricter rule and documents which policy applied and why.
Decision steps of a consulting week
| Step | Decision | Decider | Rationale |
|---|---|---|---|
| 1 | Map trip to client project | Rule engine | Calendar or CRM integration |
| 2 | Determine per diem | Rule engine | Country-specific rate per jurisdiction |
| 3 | Split hotel cost: billable vs. internal | Rule engine | Client contract terms determine split |
| 4 | Check client-specific travel policy | Rule engine | Client economy-only vs. internal first-class |
| 5 | Apply stricter policy | Rule engine | Whichever is more restrictive applies |
| 6 | Tax treatment classification | Rule engine | Deductible, partially deductible, entertainment |
| 7 | Multi-client day split | AI + Rule engine | AI determines time allocation, rules apply cost split |
| 8 | Generate client invoice backup | Automatic | Audit-ready expense documentation per client |
Architecture and implementation
The Travel Decision Layer runs on Gosign's enterprise infrastructure: EU data residency, containerized, multi-tenant, no external dependencies. For consulting configurations, this means: multi-client capability with separate policy rule sets, integration with project management and time tracking systems, and automated three-way split. Typical pilot projects start within 3 months with one client pool.
Frequently Asked Questions
Can the Decision Layer handle client-specific travel policies?
Yes. Each client project can have its own policy ruleset. The Decision Layer compares internal policy and client policy and applies the stricter rule, documenting which policy took precedence.
How does multi-client week allocation work?
The Decision Layer splits costs by day and by client based on calendar or project management data. Hotel stays spanning multiple client days are allocated proportionally. Every split is documented in the audit trail.
Does it integrate with project management and time tracking tools?
The Decision Layer is configurable to read project assignments from standard tools. The integration maps travel days to projects without requiring consultants to duplicate data entry.
How are entertainment expenses classified?
Entertainment expenses follow jurisdiction-specific rules. The Decision Layer classifies each expense by type and applies the correct tax treatment. Mixed business-entertainment events are split based on configurable rules.
How complex is your consulting travel expense logic?
In the Consulting Simulation, we configure the Decision Layer with your real-world scenarios: your client contracts, your hierarchy policies, your cost centres.
Request Consulting Simulation