Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

What is SAP FICO?

SAP's finance and controlling modules — what each is for, and why S/4HANA brought them together.

In short

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.

Why It Matters

Why this matters in practice

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.

FI is the statutory and external view; CO is the internal one
Both derive from the same operational postings
The Universal Journal in S/4HANA holds both in one line-item table
Chart of accounts and cost element design are decided once
How It Works

How it works in practice

General ledger

The statutory backbone. Chart of accounts, company codes, fiscal year variants and document types all configured here.

Payables and receivables

Sub-ledgers reconciling to control accounts, driving supplier payment and customer collection.

Asset accounting

Acquisition, depreciation across multiple valuation areas, transfer and retirement.

Cost centres and internal orders

Where cost is collected before being assigned. The structure should mirror how the business is actually managed.

Profitability analysis

CO-PA, reporting margin by product, customer, channel or region, depending on the characteristics configured.

Worked example

A worked example: why FI and CO used to disagree

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Chart of accounts designed late

It is the hardest structure to change after go-live and shapes every report.

Cost centre hierarchy mirroring the org chart

Organisations restructure. A hierarchy that tracks reporting lines needs rework each time.

CO-PA characteristics chosen without asking finance

You can only report on characteristics you captured. Adding one retrospectively does not populate history.

Treating CO as optional

Skipping CO because FI produces the statutory accounts leaves the business with no view of where cost arises.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

FI is external and statutory — the balance sheet and P&L a regulator or auditor sees. CO is internal — cost centres, orders and profitability, used to manage the business.
No. It merged the data: FI and CO line items now live in one Universal Journal table, which removes the reconciliation between them but keeps both views.
FI alone gives you statutory books and nothing about internal responsibility. CO is what lets you report by cost centre, internal order, project or profitability segment — the dimensions management actually asks about. If your questions are limited to statutory reporting, FI covers them; the moment someone asks which department or which product line is responsible for a cost, you are describing CO.
Producing complete financial statements at a level below the company code — segment, profit centre, business area. Without splitting, a payment covering invoices across two segments cannot be allocated properly and segment balance sheets will not balance. It must be configured correctly from the start, because retrofitting it to a system with posting history is genuinely difficult and sometimes not practical at all.
A cost centre collects costs for a responsibility area — a department, a function — and answers who spent it. A profit centre collects both revenue and cost for an internal business unit and answers whether that unit made money. Most organisations need both, and the common error is designing one hierarchy to serve both purposes, which produces a structure that does neither well.
Primarily the Universal Journal, which merges FI and CO line items into one table and removes the reconciliation between them. Beyond that, the material ledger becomes mandatory, customer and vendor master data moves to the business partner model, and a range of aggregate tables are replaced by views computed on read. Together these mean that FICO migration is not a technical lift of the same configuration — it is a data model change with real functional consequences.
Related

Where to read next

What is SAP S/4HANA?

Read more

What is a chart of accounts?

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.