Executive summary
As organizations grow across entities, regions and currencies, Travel & Expense management becomes more than an employee expense problem.
It becomes a control problem.
A single entity can often manage its T&E activity with a combination of local systems, spreadsheets and manual processes.
At group scale, those same processes create fragmentation.
- Travel may be managed separately from cards.
- Expenses may follow different approval structures.
- Policies may vary by entity.
- Currencies create additional complexity.
- And Finance may receive the consolidated picture only after the reporting cycle is complete.
The challenge is therefore not simply processing expenses.
It is maintaining control across the entire spend lifecycle.
1. The fragmentation problem
A multi-entity T&E environment often contains several separate systems.
- Travel.
- Corporate cards.
- Expense submissions.
- Approvals.
- Policy documents.
- Accounting.
- Reporting.
Each system can perform its individual job successfully.
The problem appears between them.
A transaction starts in one system, moves through another and eventually reaches Finance.
If the connections aren't preserved, Finance has to reconstruct the story.
2. What changes at group scale?
A single-entity Finance team may ask:
A group Finance team needs more context:
The number alone is not enough.
Context becomes part of control.
3. A five-layer control model
A scalable T&E environment can be thought of as five connected layers.
Layer 1 — Global Governance
Common principles and organizational standards.
Layer 2 — Entity Context
Legal entity, employee, cost centre and local rules.
Layer 3 — Transaction Controls
Policy evaluation, limits, approvals and exceptions.
Layer 4 — Financial Record
Transaction, receipt, expense and accounting classification.
Layer 5 — Group Intelligence
Consolidated visibility with drill-down into entities and transactions.
The strength of the model comes from keeping these layers connected.
4. Currency is more than conversion
Multi-currency reporting is often treated as a simple conversion problem.
But Finance needs more than the converted amount.
The organization needs to preserve the underlying context:
- original transaction
- original currency
- entity
- category
- employee
- policy
- accounting context
A consolidated number without that context can tell Finance what happened.
It doesn't necessarily explain why.
5. Local policy without global fragmentation
Multi-entity organizations need local flexibility.
Different entities may require different:
- spending thresholds
- tax treatment
- approval structures
- documentation
- currencies
- operational rules
The answer isn't to build completely separate T&E environments.
Instead:
This keeps governance consistent while allowing appropriate local variation.
6. From group to transaction
A useful Finance workflow should allow questions to move through multiple levels.
This is the difference between simply reporting spend and being able to control it.
7. Why connected data matters
When travel, spend, expense, payments and policy operate separately, Finance has to connect the information manually.
When those stages share a common record, the context can move with the transaction.
That creates a more complete financial picture.
The objective isn't to eliminate every system around Finance.
It is to create a connected layer through which the relevant information can move.
8. What good looks like
A mature multi-entity T&E environment should provide:
- Consistent governance — common organizational principles.
- Controlled local variation — entity-specific rules where necessary.
- Connected transaction data — the relationship between spend, receipt, expense and accounting remains intact.
- Consolidated visibility — Finance can see the group.
- Drill-down — Finance can understand the transaction behind the number.
Conclusion
Multi-entity T&E doesn't need more spreadsheets.
It needs a connected operating model.
Travel, spend, expense, payments and policy should work together while entity and local context remain attached throughout the transaction lifecycle.
The result is more than better reporting.
It is control that scales with the organization.