What changed

A system conversion keeps your processes, your history and most of your configuration. It does not keep the ECC data model. For controllers, three changes matter more than the rest: cost elements are now G/L accounts, all accounting components write to the Universal Journal, and the material ledger is mandatory. None of them changes what a controller is trying to achieve. All of them change where the numbers live, how they are maintained, and what can be tested.

Cost elements became accounts

In ECC, a primary cost element mirrored a P&L account and a secondary cost element existed only in controlling. In S/4HANA there is one field, the account, covering both. Primary cost elements merged with their P&L accounts; secondary cost elements were migrated into the G/L account master. You maintain them in the G/L account master data (transaction FS00 or the Fiori app for G/L account master data), not with the old cost element transactions. The account carries a G/L account type that separates Primary Costs or Revenue from Nonoperating Expense or Income and Secondary Costs, and a cost element category that tells controlling how the account may be used: 1 for primary costs, 41 for overhead, 42 for assessment, 43 for internal activity allocation, and so on.

Day to day, controllers notice three effects. First, creating an account that is also a cost element now needs authorization for both the G/L account and the cost element, so role design has to cover it. Second, secondary postings such as assessments and activity allocations are on the trial balance if the financial statement version includes their accounts, so finance and controlling see the same totals. Third, configuration objects still say "cost element" (assessment cycles, settlement profiles, costing sheets), which confuses new team members but works as before.

The Universal Journal

SAP describes the Universal Journal as the single source of truth for financial data: FI and CO record the same line items, so reconciling them becomes unnecessary. Old CO line item and totals tables are not where the data lives any more; SAP provides compatibility views so that classic reports such as the cost center line item report keep working, but custom programs that write to or rely on old table structures need review. Kenji's team found 37 custom programs in ED1 that read controlling tables; most work through the compatibility views, and a handful that used direct table updates had to be rewritten.

What it means for a controller's month

The daily work of a controller changes less than the data model. Cost center managers still read plan/actual reports, the cost accountant still runs allocations and settlement, and product costing still releases standards. What changes is the route to an answer. A question such as "why is Detroit Assembly over budget?" can now be answered from journal entry lines that carry the G/L account, the cost center, the order, the profit center and the partner object together, so drilling from the P&L to the cost center to the document is one path rather than three reports in three modules. Month-end also loses steps: the FI-CO reconciliation and the transfer of cross-company controlling postings at period end are gone, because the journal records them as they happen. And trial balance reviews gain lines, because secondary cost accounts are now visible there. Teach the finance team what those lines mean before the first close, or someone will try to "correct" them.