Freight settlement is where SAP TM business cases are won — and where they are quietly lost
Transportation programmes are sold on optimisation savings and delivered as planning projects. The money is usually in charge management, which is also the part most likely to be under-scoped.
Most SAP TM business cases lead with optimisation. Better consolidation, fewer kilometres, higher fill rate — modelled, defensible, and genuinely achievable.
Then the programme gets scoped, and planning takes most of the budget because planning is where the visible complexity sits. Charge management and settlement land in a later phase. Eighteen months on, the optimiser is running, the savings are real but smaller than modelled, and nobody can explain the gap.
The gap is usually in settlement.
Two different kinds of saving
Optimisation saves money by moving freight better. It is a modelling problem, and the model is only as good as its cost inputs.
Settlement saves money in three quieter ways:
- Enforcement. You are already paying rates you negotiated. Automated calculation against the agreement catches the difference between the agreed rate and the invoiced rate — and that difference is systematic, not random.
- Accrual accuracy. Knowing freight cost at order time rather than at invoice time changes what finance can see and what sales can be told about cost to serve.
- Effort. Freight invoice verification is often several full-time roles doing work a calculation sheet does correctly and instantly.
None of these show up in an optimisation model, which is exactly why they get deferred. They are also the ones that do not depend on planner adoption to materialise.
Why charge management gets under-scoped
Because it looks like configuration and behaves like a specification problem.
A calculation sheet is straightforward. What is not straightforward is the answer to: what are we actually agreeing to pay? Most organisations discover during design that this is not written down anywhere in a form a system can execute.
Rates exist. But so do:
- Fuel surcharges on three different index bases, updated at different frequencies
- Accessorials applied inconsistently by carrier and by region
- Minimum charges that interact unexpectedly with break weights
- Scale bases nobody can source the origin of
- Side agreements a regional manager made and never circulated
Turning that into a calculation sheet is not a configuration task. It is a commercial data-gathering exercise with a configuration task at the end, and it needs procurement engaged from week one. A programme that discovers this in build has already lost the schedule.
The rate table conversation
The single most useful early question is: how many genuinely distinct charge models do we have?
Not how many carriers — how many models. Twenty carriers on three structures is a manageable scope. Six carriers on six bespoke structures with different scale bases is harder, and it is the count that drives effort, not the carrier count that appears in the project brief.
Ask it in week one. The answer reorders the plan.
Sequencing that respects the dependency
Settlement depends on planning, so it cannot come first. But it does not have to come last.
A workable pattern:
- Planning and execution live — freight orders exist and are accurate.
- Charge calculation live in shadow — TM calculates expected cost on every freight order but does not settle. The output is compared against actual carrier invoices.
- Settlement live — once shadow-mode variance is understood and the calculation is trusted.
Step two is the one people skip, and it is the cheapest insurance in the programme. Running calculation in shadow surfaces every gap in the rate model against real freight, with no financial consequence and no carrier relationship at risk. The variance report from a month of shadow running is worth more than any amount of design workshop.
What this means for scoping
If you are building a TM business case, put a number on the settlement benefit and put it in the same phase as planning — even if it goes live later.
The programme that ships planning-only and defers settlement is not deferring 30% of the scope. It is deferring the part of the benefit that does not depend on anyone changing how they work, and keeping the part that does.
That is the wrong way round.