Multi-country ERP from the CFO's perspective: what matters?

From the CFO's perspective, four things count in a multi-country ERP: comparable figures across all countries through uniform account and dimension logic, a fast and reliable group close, cost transparency within the programme itself, and a rollout plan that distributes risk instead of stacking it. Comparing only licence and consulting costs means steering past the real risk.

Which questions should the CFO ask before the programme?

• From when does each country deliver its figures from the new system, and what applies until then?
• How long does the group close take today, and what is the target after the rollout?
• Which assumptions sit in the business case, and who has verified them?
• How large is the internal effort of the business departments that never appears as a cost line?
• What happens to the programme budget if one country goes live six months later?

These questions sound banal, but they force answers that many programmes only give once they are in crisis. A programme that can answer them before the start has already done its most important governance work.

These questions have one thing in common: none of them is technical, and all of them can be answered before the first euro is spent. Whoever puts them to the steering committee and gets no clear answers has already received the most important result of the meeting.

Where do the costs really arise?

Licence costs are rarely the biggest block in an international rollout. Experience shows the expensive items are: data migration per country, interim interfaces during mixed operation, the double load on key users, and the extensions that follow when decisions get stuck.

The most honest cost indicator of a running programme is decision speed: where scope, template and exception decisions take weeks, everyone's cost clock keeps running without progress. Budget drift almost never starts in the technology; it starts in governance.

The largest invisible item is the time of your own people. Key users in the countries who clarify processes, test and train are absent from day-to-day work while they do it. That effort appears in no proposal and is, in our experience, the single largest block in multi-country programmes.

What does the rollout mean for the close and for reporting?

During the rollout, group close and reporting live in a transitional state: some companies deliver from the new system, the rest from the old ones. This state needs defined reconciliations, otherwise every monthly meeting debates data states instead of the business.

After the rollout, the gain is concretely measurable: shorter closing times, because intercompany reconciliation and Consolidation run in the system, and reporting that is no longer assembled by hand. The CFO should fix this target in advance, because it is the real business case.

During the transition phase two reporting worlds exist, and they have to be brought together. That belongs planned as a work stream of its own, with clear rules about which system is the leading one for which figure and how the group close is produced at all during this transition.

What role should the CFO play in the programme itself?

Not a patron, but a decision-maker: the CFO belongs on the programme steering committee, because the critical decisions are almost all financial decisions: rollout sequence, budget adjustments, template exceptions with cost impact, go-live approvals.

And the CFO is the natural owner of the data foundation question: comparable, reliable figures are a finance topic, not an IT topic. Where the CFO actively fills this role, the programme gains the decision speed that determines budget and timeline. Control on your side here means, concretely: on the CFO's side.

The most effective role is not that of the client but that of the decision-maker in conflicts of goals. When the date, data quality and scope collide, the programme needs one person who prioritises with authority, and in multi-country undertakings that is in practice almost always the CFO themselves.

Which metrics should the CFO track in the programme?

Not percentage completion. In an ERP programme that figure is a lying metric: it reliably climbs to 80 percent and then sits there for months. Five other values are meaningful, and all can be collected monthly:

• Decision latency: how many days pass between a question being raised and a decision being made? When this value rises, the budget rises with it.
• Open scope items: the number of unresolved requirements. If the list grows faster than it is worked off, the date cannot hold.
• Test coverage of the core processes: what percentage of business-critical flows has been tested with real data and signed off by the business?
• Data quality ratio: the share of cleansed and approved master data per object.
• Forecast to complete on an actuals basis: what does the remainder cost, calculated from actual consumption rather than the original plan?

These five figures fit on one page and answer the only question that really interests the CFO: will the date and the budget hold, and if not, since when has that been known?

What belongs in the contract so the budget holds?

The contract is the cheapest instrument of control a CFO has, and usually the least used. Four points later decide whether there are change orders:

First, a scope definition that also names the exclusions , not only the deliverables. Second, a change process with pricing logic: who may commission a change, what does it cost, and how does it affect the date? Third, the staffing with names and roles, plus a rule for what applies when people are replaced. Fourth, acceptance criteria per phase, so that "done" is not a matter of negotiation.

In addition, build in exit points: defined moments at which the programme can be halted or rescoped without conflict. That sounds defensive but works the other way round: knowing that orderly exits exist makes people decide more boldly along the way.

These four points cost time in the negotiation and nothing else. They are the only steering instrument that already works before the programme starts, and the only one that still holds when the relationship with the partner becomes strained.