SAP's finance and controlling modules — what each is for, and why S/4HANA brought them together.
FI (Financial Accounting) produces the statutory view: general ledger, payables, receivables, asset accounting, and the statements auditors read. CO (Controlling) produces the management view: cost centres, internal orders, profitability analysis. In ECC they were separate with reconciliation between them; in S/4HANA the Universal Journal puts both in one table.
FI and CO answer different questions from the same transactions. FI asks what the legal entity owes and owns; CO asks where cost was incurred and which product or customer carried it. Keeping both from one posting is the point, and in ECC the periodic reconciliation between them was a standing task that the Universal Journal largely removed.
The statutory backbone. Chart of accounts, company codes, fiscal year variants and document types all configured here.
Sub-ledgers reconciling to control accounts, driving supplier payment and customer collection.
Acquisition, depreciation across multiple valuation areas, transfer and retirement.
Where cost is collected before being assigned. The structure should mirror how the business is actually managed.
CO-PA, reporting margin by product, customer, channel or region, depending on the characteristics configured.
In classic ECC, Financial Accounting and Controlling maintained separate tables. A cost posted in FI was mirrored into CO, and the two were expected to agree. In practice they drifted — reposting within CO, allocations, assessments and distributions all moved amounts in CO that FI never saw.
Month-end therefore included a reconciliation between FI and CO, with a reconciliation ledger to catch the differences. This was normal, it was understood, and it consumed real time every period. Whole roles existed partly to maintain it.
In S/4HANA the Universal Journal puts FI and CO line items in one table. They cannot disagree, because they are the same record viewed through different fields. The reconciliation step largely disappears. This is one of the clearest practical benefits of the migration, and it is also why the data model change has such wide consequences: any custom report that read the old separate tables needs revisiting, because those tables are no longer where the truth lives.
| Term | What it means |
|---|---|
| FI | Financial Accounting — external reporting, statutory books, the general ledger. |
| CO | Controlling — internal management accounting, cost centres, profitability. |
| Company code | The legal entity for which a complete set of books is produced. |
| Cost centre | A unit where costs are collected for internal responsibility reporting. |
| Document splitting | Dividing a posting across dimensions so segment-level balance sheets are possible. |
It is the hardest structure to change after go-live and shapes every report.
Organisations restructure. A hierarchy that tracks reporting lines needs rework each time.
You can only report on characteristics you captured. Adding one retrospectively does not populate history.
Skipping CO because FI produces the statutory accounts leaves the business with no view of where cost arises.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Days to close | The composite measure that FICO configuration most directly affects. | |
| Manual journals per period | High volumes usually indicate configuration gaps being patched by hand. | |
| Open items in clearing accounts | Items that should have cleared and did not, which accumulate quietly. | |
| Cost centre variance to plan | Whether controlling data is actually used for management or only produced. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.