The CFO's business case for closing the asset-to-ledger gap

A CFO doesn't fund software. A CFO funds risk reduction, capacity, and defensible numbers. Here's how to build an honest case for the gap most SAP-run asset-intensive organisations are quietly carrying, without a return multiple that nobody can defend.

Start with the control, not the feature

SAP automates both ends of a capital project: cost into the asset under construction, and settlement posting and depreciation once a rule exists. The middle is typed by hand: which equipment the project created, how it links to fixed assets, and which final assets, IAS 16 components and shares it becomes. A control that depends on one person's spreadsheet is a control finding waiting to happen. That, not a headline saving, is the case.

The uncomfortable part: the gap between what the technical register (EAM) says exists and what the financial register (FI-AA) says was capitalised is real, and it is under-watched precisely because S/4HANA's Universal Journal removed a *different* reconciliation and everyone assumed the whole problem was solved.

The three levers a CFO scores

Structure the case the way finance leaders actually evaluate technology, weighted toward control for this buyer. We do not claim a return multiple, a regulated-return uplift or a timing gain; none of them survives scrutiny.

1. Control and audit evidence (lead here)

An auditor asks for the asset behind a capitalised dollar and where the dollar came from. Today the answer is often a spreadsheet and a person's memory. The case is to make that answer repeatable: every amount from a cost source, every split approved by a different user, and an evidence pack your team attaches to the asset in SAP. We do not put a number on this; you size it from your last audit finding.

2. Capacity (hours you get back)

Manual fixed-asset work — mapping, spreadsheet apportionment, chasing AUC settlements — is capacity, not cash, and it concentrates in a few large projects. The honest version your Controller will recognise: how many hours the last three large settlements took, and how many of those a rule book and a tie-out would have removed. You supply the hours; we do not.

3. Hygiene (assets in service, not in construction)

A completed project that sits in assets under construction delays the start of depreciation and clutters the register. We treat this as close hygiene and an ageing measure, not as a material misstatement. Doing the work inside an S/4 migration, when the Asset-Accounting foundation is already open and funded, costs a fraction of doing it afterward.

The number that makes the case — and where it comes from

Here is the discipline that separates a credible business case from a vendor pitch: you do not promise the saving. You measure it. The honest business case has one figure the vendor supplies — the cost of the tooling — and every other figure supplied by you, from a diagnostic run on your own data. AUC ageing, hours spent today, audit points raised: your inputs, your numbers.

A business case built on someone else's benchmark is a guess. A business case built on your own AUC balance is a decision.

This is why a paid concierge on one completed project is the right first step, not a slide deck. It shows what the control looks like on your own data, and the diagnostic across the estate can follow.

Who owns the outcome (say it out loud)

A CFO will — rightly — ask who is responsible if a capitalisation decision is wrong. The answer has to be unambiguous: you do. Tooling of this kind proposes, apportions, and evidences; your finance team and your advisors own the decisions, the financial statements, and their compliance. Every proposal is approved by a person, and Attesta never posts: SAP's own run does. That is not a weakness in the case — it is the reason it is defensible. A system that quietly posted capitalisation would be a liability; one that governs and evidences a human decision is an asset.

The one-slide version

The middle of every capital handover is a manual control. It can be made repeatable and evidenced, funded from a line that already exists (migration, revaluation, audit remediation), and tried on one completed project before you commit. That is a business case a CFO can sign.