TMS implementation, from the buyer's side of the table.
Independent implementation expertise sitting between treasury, IT and the vendor, where the decisions that determine the configuration actually get made.
An independent TMS implementation consultant works for the organisation buying the system rather than the one selling it. The role is to hold the decisions the vendor cannot make for you — accounting treatment, source of record, connectivity approach, the definition of done, and to tell you which of the vendor’s statements are product facts and which are negotiating positions. It does not replace an internal owner. It gives that owner someone who has seen the same programme before and can recognise an expensive decision while it is still cheap to change.
What does an independent TMS implementation consultant do?
An independent consultant sits between treasury, IT and the vendor and owns none of their agendas. Day to day that means chairing the decisions that cross boundaries, reviewing vendor design documents against your actual processes rather than the demo, testing that the configuration matches what was agreed, and telling the programme owner early when the plan and the reality have separated. The work is judgement and pattern recognition, not additional project-management capacity.
When should you bring one in?
Before the vendor is selected, if you can. The decisions that determine whether an implementation goes well — accounting treatment, source of record, connectivity, the definition of done — are all cheaper to settle before a contract sets the scope. The second-best moment is design freeze, which is the last point at which changing the plan costs less than absorbing it. The most common moment is the first missed milestone, by which time the cost of correction has usually already been incurred.
The decision timelineThe cost of changing a decision rises through a programme, and it does not rise smoothly. Design freeze is the point after which absorbing a wrong decision costs less than correcting it — which is why most treasury teams live with configuration nobody chose.
Cost of changing the decision
Cheaper to change
Before selection
Accounting treatment. Source of record.
The best moment. Every decision here is still free.
Contract
Scope becomes a written commitment.
Design freeze
Connectivity. Definition of done.
The crossover, and the last moment a review changes the outcome.
Build
Configuration follows the design, right or wrong.
UAT
The first missed milestone usually lands here.
Go-live
Cut-over and parallel run.
First month-end
The cost of correction has already been incurred.
The most common moment we are actually called.
Cheaper to absorb
What does it cost you not to?
The visible cost is time: decisions that wait, configuration revisited, a timeline that absorbs the difference. The less visible cost is that the treasury team stops believing the programme is theirs, which is much harder to recover than a date. Neither shows up as a line item, which is why implementations are usually described afterwards as having failed on software.
How is this different from the vendor’s project manager?
The vendor’s project manager is accountable for delivering the vendor’s scope, competently and in good faith. That is a different job from being accountable for whether the system serves your treasury function. Both can be true at once: the implementation delivered exactly what was contracted, and the outcome is wrong. An independent consultant is measured on the second.
Who holds what, on a well-run programme
Responsibility
Holder
The outcome
A named person inside treasury
Configuration and product knowledge
The vendor
Integration, security, infrastructure
IT
Whether the decisions are the right ones
Independent advice
When you don't need this
Against our own interest
If the programme has a strong internal owner with implementation experience, an honest vendor and a simple instrument set, you may not need anyone else in the room. We would rather say that than sell you a seat at a table that is already working.