What sits in your AUC past close

Point a diagnostic at an asset-intensive SAP estate and the first finding to look for is an Asset-Under-Construction balance that should have been settled quarters ago. On our demonstration estate it is $4.82M sitting past close (illustrative data). Here's why it hides, and how to find it.

"But S/4HANA reconciles everything now"

This is the most expensive sentence in enterprise fixed-asset accounting. The Universal Journal genuinely did remove one reconciliation: the FI-AA subledger no longer drifts from the GL, because there is no separate subledger to drift. So the instinct — "reconciliation is solved" — is half right.

It's also half wrong in a way that costs real money. The reconciliation S/4 removed was financial-to-financial. The reconciliation it never touched is technical-to-financial: the gap between what your EAM/PM system says exists in the field (the equipment, the functional locations, the renewals) and what your FI-AA register says you've capitalised. Nobody owns that seam, so it quietly widens.

SAP's own ecosystem admits it: finance and operations "execute asset events separately," and PM functional-location structures "diverge from asset class and valuation structures in FI-AA, creating reconciliation challenges."

Where the money actually gets trapped

Three patterns are worth sizing, and a read-only diagnostic can report all three without posting anything:

• AUC past close. Work is mechanically and operationally complete — the asset is in service — but the AUC was never settled to a fixed asset. Depreciation hasn't started; the cost sits in construction-in-progress. On the demonstration estate this is the biggest number.
• Depreciation misstatement. Componentisation wasn't applied, or useful lives were set once and never revisited (IAS 16.51 says revisit them prospectively). The asset depreciates on the wrong curve until someone revisits it.
• Ghost assets. The financial register carries assets that no longer physically exist, or carries them at the wrong location/cost centre. The reverse — physical assets with no financial record — is the reverse problem, and just as hard to evidence.

Why it's tolerated

Not because anyone is careless. Because the fix is genuinely cross-disciplinary and the standard tooling stops short:

• The standard Equipment → Asset link in SAP is one-to-one and manual. Real estates are many-to-many: one project becomes a dozen assets across several classes; one substation is a bundle of components on different useful lives.
• There's no rule-based %-apportionment of an AUC across the assets it produced — so it's done in a spreadsheet, by hand, once, and never governed.
• The work needs FI-AA and PS/IM and EAM and integration knowledge in one head. That person is expensive and rare, so it gets re-bought as project cost every migration.

The result: the gap is real and chronically tolerated — until a trigger (an S/4 migration, a revaluation cycle, an audit finding) makes it suddenly urgent.

How to quantify it in a week

You don't need to commit to a transformation to find out how big the number is. A read-only diagnostic reads your AUC, equipment and asset extracts (CSV) and produces a $-at-risk report: AUC past close, depreciation misstatement exposure, and ghost-asset counts — with the dollar figure attached to each. No postings and no changes to your SAP system. Treat it as a control-hygiene view of your close, not a forecast of recovered value.