What your financial close reveals about the true state of your SAP core.

We have made a habit, when arriving at a client, of sitting with the accounting team through a close before reading any documentation at all. Not for the ritual of it: the close concentrates into a few days everything the rest of the year conceals. Upstream processes can live with their approximations for a long time. The close has no such luxury: it must produce a figure that is accurate, dated and defensible. So it absorbs, month after month, the cost of everything that was badly recorded, worked around or patched together upstream. How long it takes, and how much it hurts, is the consolidated bill for those compromises.

Three symptoms, three causes

The first symptom is manual reconciliations. When a team spends its evenings reconciling the general ledger with controlling, inventory with the ledger, intercompany with itself, the problem is not the accountants' competence. It is that the data does not agree at the source: the same operations recorded twice under two different logics, diverging master data, account assignments left to the discretion of whoever keys them in. The month-end reconciliation repairs by hand what upstream data should have guaranteed.

The second symptom is Excel adjustments. Every adjustment workbook tells the same story: somewhere, a real process no longer goes through the system. The discount granted outside the tool, the provision calculated on the side because "the module can’t do it," the logistics flow whose valuation gets corrected after the fact. The spreadsheet is rarely laziness; it is the trace of a workaround that has become an institution. It works, until the day its author changes jobs.

Which leads to the third and most revealing symptom: the close that rests on two people. If the closing calendar is organized around the vacation dates of two employees, it is because whole sections of the system, custom developments, bespoke reports, chains of batch jobs, exist only in their memory. An undocumented custom development is not an asset; it is a risk waiting for a date. The close is simply the place where that risk becomes visible twelve times a year.

The close absorbs, month after month, the cost of everything that was badly recorded, worked around or patched together upstream. Its length is the consolidated bill.

What the Universal Journal changes, and what it does not

S/4HANA brings a fundamental change on this ground: the Universal Journal. General ledger, controlling, fixed assets and inventory valuation cease to be worlds kept in parallel and reconciled after the fact; they are written into a single record, as events occur. A whole category of reconciliations disappears, not because it was automated, but because the discrepancy it corrected can structurally no longer occur. That is real progress, and we see it at clients who have made the move: the raw material of the close is healthier.

But the Universal Journal changes the data, not the discipline. If upstream processes keep being bypassed, the adjustment workbooks will survive the migration; they will simply start from fresher extracts. If account assignments remain a matter of individual preference, the single record will carry inconsistent choices with perfect fidelity. An S/4HANA core inherits the habits brought to it. The technology removes the structural reconciliations; it removes none of the cultural ones.

Reading your own close as an audit

Hence a suggestion we often make, because it costs nothing: instrument your next close the way you would instrument an industrial process. List every task, its owner, its duration, and above all its nature: legitimate control, or repair of an upstream defect? Every manual reconciliation points to data to be made reliable at the source. Every Excel workbook points to a process to bring back into the system, or a gap in the system to close. Every task that only one person knows how to do points to a custom development to document, standardize or remove. You will end up with a map of your SAP core’s weaknesses that is more honest than many audits, drawn up by the very people who live with them.

The exercise takes on a particular edge as the 2027 deadline approaches. The list of your close’s recurring repairs is exactly the list of what a badly prepared conversion will carry, as is, into S/4HANA. Conversely, the close is where a successful conversion is judged: the first close afterwards says immediately whether the program cleaned up the data and the processes, or merely moved the problems into a faster system. We encourage our clients to make it an explicit criterion of their S/4HANA program, on a par with data migration or keeping to budget.

That is the whole conviction of our finance practice: the close is not a chore to be sped up, it is the most reliable measuring instrument a finance function has on its own system. Provided you are willing to read what it tells you.