Closing relies on late reconciliation and margin variance is explained after the useful period.
Finance leadership guide
Turn operational flows into actionable financial visibility
Connect physical events, valuation rules, commitments, invoicing, margin and working capital.
For: Finance, controlling, operations and IT leadersWhat to clarify before discussing a solution
Which operational event should trigger financial recognition, valuation or control?
The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.A management model linking every financial measure to its operational source and a decision.
Four decisions to make before configuration
These decisions make the scope testable and prevent structural choices from being discovered during the project.
Connect each posting to an explainable event
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Define work units useful for margin
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Assign variance to an operating cause
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Set a management cadence before closing
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
A readable end-to-end flow
Scope is not a list of modules. It is a chain of events, ownership and decisions.
1Trigger events
2Valuation
3Commitment and invoicing
4Margin and contribution
5Cash and tied-up capital
In the first scoping
- One representative flow and its useful variants
- Authoritative events and minimum data
- Roles, decisions and escalation times
- Acceptance criteria and baseline measurement
To sequence in waves
- Additional sites, activities or populations
- Rare variants that do not condition the pilot
- Automations whose rule is not yet stable
- Advanced dashboards after source reliability
To decide explicitly
- Connect each posting to an explainable event
- Define work units useful for margin
- Assign variance to an operating cause
- Set a management cadence before closing
From direction to measured improvement
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.
Measure to decide, not to fill a dashboard
Every KPI needs a definition, a source, a cadence and an associated decision.
KPIFormulaSourceDecision
Contribution marginRevenue − directly attributable costsSales, purchasing, operations and chargesArbitrate portfolio, service and terms
Working capital requirementInventory + receivables − operating payablesInventory, sales, purchasing and collectionsReduce tied-up capital without weakening service
Transport cost per unitConsolidated transport costs ÷ units deliveredServices, kilometres, charges and invoicingArbitrate transport plan, utilisation and providers
Decision lead timeDecision date − signal dateAlerts, decisions and actionsShorten the path from signal to action
06 · Business scenario
Margin explained by the flow
- Situation
- Finance knows the overall result, but operations do not see the causes of deterioration early enough.
- Approach
- Scoping connects services, consumption, movements and exceptions to valuation rules, then builds an actionable variance dashboard.
- Target outcome
- Decisions bring operating performance and financial contribution together.
Useful answers before the first discussion
01Where should we start in practical terms?
Choose a representative scope spanning “Trigger events” and “Valuation”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.
02Do all existing systems need replacing?
No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.
03What data should be prepared before a workshop?
Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure Contribution margin. The quality of examples matters more than the quantity of documents.
04How should the right pilot scope be chosen?
Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.
05How can scope changes during the project be limited?
Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.
Next step
Turn this guide into a personalised review
Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Complementary guides
Guides by suite
EMS Logistics suite
Transform transport & logistics
Connect order, warehouse, transport, delivery and invoicing around the same events and responsibilities.
- Service promise
- Warehouse execution
- Transport plan
Guides by suite
EMS Industry suite
Connect planning to the shop floor
Build decision continuity across demand, materials, capacity, execution, quality, maintenance and cost.
- Demand and schedule
- Materials and capacity
- Execution and WIP
Guides by suite
EMS Commerce suite
Unify omnichannel commerce
Connect catalogue, availability, order, payment, fulfilment, delivery, return and customer relationship.
- Catalogue and pricing
- Available-to-promise inventory
- Order and allocation