Ledgers

A ledger in SAP S/4HANA is a complete set of books for one accounting view. Most companies need only one. Companies that report under more than one accounting principle (for example US GAAP for the group and IFRS or local GAAP for another purpose) keep parallel ledgers so each view has its own balances without spreadsheets.

Leading and non-leading ledgers

Every system has exactly one leading ledger, usually 0L. It is assigned to every company code, cannot be deactivated, and represents the group accounting principle used for consolidated statements. In the standard system, only leading ledger values flow to controlling. Non-leading ledgers are optional, are activated per company code and represent other accounting principles. They can even use a different fiscal year variant from the leading ledger.

Extension ledgers

An extension ledger sits on top of a standard ledger. It stores only the entries posted directly to it and, for reporting, includes everything from its underlying ledger. That makes it cheap: no duplicate data, just adjustments. It suits views such as a management view with extra adjustments. Only manual postings can go to an extension ledger.

How a posting reaches the ledgers

By default, a posting goes to all ledgers assigned to the company code: a supplier invoice appears identically in 0L and any non-leading ledger. When an entry should affect only one accounting principle, such as an IFRS-only provision, you post it to a ledger group. When you create a ledger, a ledger group of the same name is created automatically; groups combining several ledgers can be defined when needed. If no ledger group is entered, the entry posts to all ledgers. In Post General Journal Entries, the ledger group is a header field; in classic transactions, FB50L posts ledger-specific G/L entries.

Reporting and testing by ledger

Every finance report has a ledger, whether you notice it or not. Trial Balance, Display Line Items in General Ledger and the financial statement apps all filter by ledger, and most default to the leading ledger. A non-leading ledger balance that nobody looks at is a balance nobody checks. When Contoso tests a ledger-specific entry, Priya's team displays the line items twice, once filtered on 0L and once on the target ledger, and confirms the entry appears only where it should. They also compare the two trial balances: the difference must equal the sum of ledger-specific postings, and nothing else.

Processes can post differently per ledger automatically too. Asset accounting is the classic example: depreciation areas are assigned to ledgers, so the same asset can depreciate differently under each principle. Those differences come from configuration, not manual entries, and are tested in the asset accounting cycle.

A practical limitation: ledger-specific postings to open-item-managed accounts are typically rejected, because open items must clear the same way in all ledgers. Design separate adjustment accounts without open item management for ledger-specific entries.