Who owns the asset-to-ledger gap?
The reason the technical-to-financial asset gap survives for years is not technical. It is organisational: finance treats it as engineering's data problem, engineering treats it as finance's number problem, and the line item that would fix it never finds an owner. Here is how to give it one.
Why "nobody's job" is the natural state
The work of turning a built asset into a correctly-valued, correctly-timed capitalised entry sits across four functions that rarely share a scorecard. The asset engineer knows what was built and where. The project accountant knows what it cost. The fixed-asset accountant knows how it must be componentised and depreciated. And IT owns whether any of it can move between systems safely. No single one of them can close the gap alone, and none of them is measured on closing it. So it stays open — until an auditor or a regulator makes it urgent, at which point everyone owns it at once, badly.
A RACI that actually assigns it
The fix is boring and effective: name Responsible, Accountable, Consulted, Informed for each part of the pipeline, and put a name against Accountable. One person accountable per row is the whole point.
| Step | Accountable | Responsible | Consulted / Informed |
|---|---|---|---|
| As-built data from project delivery | Project-delivery sponsor | Project engineers | Asset / EAM manager (C) |
| Technical asset data quality | Asset / EAM Manager | Asset engineers | Finance (C) |
| Cost capture (AUC / PO) | Project / Capital Accountant | Project controllers | Controller (C) |
| Mapping & componentisation rules | Financial Controller | Fixed-asset accountants | Asset mgmt (C), audit (I) |
| Capitalisation decision & settlement | Financial Controller / CFO | Fixed-asset accountants | External audit (I) |
| System path & security | CIO / IT | BTP / platform team | Finance (C) |
Notice where "Accountable" lands for the decision that matters: the capitalisation decision and posting sit with the Financial Controller and CFO. Not the tool. Not the SI. Not the asset team. That is not an accident of this table — it is the law of how financial statements work.
Where tooling fits — and where it must not
Good tooling collapses the coordination cost between these rows. It lets the asset team's data, the project team's cost, and the controller's rules meet in one governed place, proposes the mapping, apportions the cost to the cent, and records who decided what. What it must not do is quietly make the accountable decision itself. The moment a system decides a capitalisation without a human owning it, the RACI has a hole exactly where the auditor will look.
Automate the coordination. Never automate the accountability. The client owns the outcome — always.
The honest contract
This is worth stating plainly, because it protects everyone. A capitalisation accelerator — Attesta included — is decision-support. It proposes, apportions, and evidences. The client's finance team and its advisors own the capitalisation decisions, the resulting financial statements, and their compliance. Every proposal is approved by a person, and Attesta never posts. A vendor that offered to own your accounting outcome would be offering you a liability, not a feature.
Give the gap an owner, give that owner a governed pipeline and an audit trail, and the problem that survived for years because it was nobody's job becomes a controlled, evidenced process that is clearly somebody's.
Give the gap an owner
A paid concierge on one completed project shows the Controller exactly where the gap sits.
Request a fit call →