Configuring Parallel Ledgers: Ledger Setup, Ledger Groups, and Posting Flow
Walk through how parallel ledgers are configured, how documents flow into multiple ledgers at posting time, and how ledger-specific postings and document splitting interact in practice.
Explanation
Configuring parallel ledgers begins with defining the ledgers themselves in the General Ledger configuration: the leading ledger (0L) is delivered by SAP and cannot be deleted, while non-leading ledgers are defined with their own ledger ID, description, and optionally a distinct fiscal year variant and posting period variant if the statutory requirement differs from the leading ledger's calendar. Each ledger is then assigned to the relevant company codes that need to report under that accounting principle; not every company code needs every ledger, so multinational configurations often show a matrix of company codes against ledgers reflecting which subsidiaries need which parallel books. A key configuration decision is the accounting principle assignment - each ledger or ledger group is tied conceptually to an accounting principle (IFRS, US GAAP, local GAAP), and this assignment drives which valuation methods (in Asset Accounting, in inventory valuation, in provisions calculation) apply. Depreciation areas in Asset Accounting are configured to post to specific ledger groups: a 'book depreciation' area might post to the leading ledger's group, while a 'local tax depreciation' area posts only to the non-leading ledger group, allowing genuinely different depreciation expense between books without duplicate manual entries. At runtime, the vast majority of business transactions - vendor invoices, customer invoices, goods receipts, bank postings - are ledger-independent, meaning the transaction amount is identical across all ledgers, and SAP automatically distributes the same posting to every ledger assigned to the company code in one underlying document (in New GL and S/4HANA, this is represented as one document with multiple ledger views, or in S/4HANA's Universal Journal as line items tagged by ledger in table ACDOCA). Where valuation actually differs - depreciation runs, tax provisions, or manual adjustment entries - the posting transaction allows the user or the automated job to specify a Ledger Group, restricting the posting to only the ledgers in that group. This is done, for example, when finance needs to book an HGB-only provision that should not appear in the IFRS books; the accountant enters the journal entry and explicitly selects the non-leading ledger's ledger group so the entry does not distort the leading ledger. Document splitting, a New GL/S4 feature that derives additional account assignments (like profit center or segment) to achieve fully balanced financial statements per dimension, operates consistently across all ledgers by default, but exceptions and rules can be ledger-specific if a local statutory reporting need differs from group reporting. Careful testing of document splitting rules against every active ledger is essential since a rule that works cleanly for the leading ledger might produce unbalanced segments in a non-leading ledger if fiscal year variants or period structures differ. Period-end closing activities such as depreciation runs, foreign currency valuation, and accruals engine postings must be executed per ledger or ledger group, since these processes are value-determining and often produce different results by accounting principle. Consultants must build the close calendar to reflect that a non-leading ledger with a different fiscal year variant may close on a different date than the leading ledger, requiring careful sequencing of closing activities and communication with local finance teams to avoid missed or duplicate postings.
Real project scenario
During a system configuration workshop for a chemicals company rolling out New GL, the FI lead configured ledger 0L (IFRS, leading) and ledger N1 (US GAAP, non-leading) for the US company code, since the parent required both books due to a pending merger. The team discovered that the depreciation area used for US GAAP book depreciation had not been mapped to ledger N1's ledger group, so all depreciation was only posting to the leading ledger. This was caught during a parallel test cycle when the local controller reconciled the fixed asset register against the trial balance and found no depreciation expense in the US GAAP ledger view. The fix involved correcting the depreciation area-to-ledger-group assignment in Asset Accounting configuration and rerunning the depreciation posting run in test, followed by a full regression of the month-end close simulation before go-live.
Common mistakes
• Forgetting to assign a non-leading ledger to all the company codes that actually require it, leaving some entities without proper local-GAAP reporting. • Not mapping depreciation areas correctly to ledger groups, causing local-only or group-only depreciation values to be missing from the intended ledger. • Assuming document splitting rules behave identically for a non-leading ledger with a different fiscal year variant without testing, leading to unbalanced segment reporting. • Posting an adjustment journal entry without explicitly restricting it to the correct ledger group, accidentally contaminating the leading ledger with a local-GAAP-only adjustment. • Building the close calendar around only the leading ledger's periods and missing that a non-leading ledger may close on a different date, causing late or incomplete local postings.
Best practices
• Build and maintain a clear matrix mapping company codes, ledgers, accounting principles, and assigned depreciation areas before configuration begins. • Test document splitting behavior separately for each active ledger, especially when fiscal year variants differ. • Use ledger groups deliberately for any manual adjustment posting that should not appear in all books, and train accountants on when to specify a ledger group. • Align the close calendar explicitly with each ledger's fiscal year variant and communicate differences to local finance teams. • Reconcile ledger-specific balances (like fixed asset registers per ledger) during test cycles before go-live, not just after production cutover.
Interview angle
Expect questions on how a posting reaches multiple ledgers automatically versus how a user restricts a posting to one ledger group, and how depreciation areas relate to ledger assignment in Asset Accounting. A strong answer distinguishes ledger-independent transactions (posted everywhere identically) from ledger-specific ones (restricted via ledger group), and explains the operational impact of differing fiscal year variants across ledgers on period-end close sequencing.