Chart of accounts, dimensions, and parallel accounting

How SAP's three-layer chart of accounts, field-status-driven account assignment, New GL document splitting, and parallel ledgers are translated into D365 main accounts, account structures, posting layers, and fixed-asset books.

What you will be able to do

• Translate the three-layer SAP chart of accounts into a single D365 chart of accounts with consolidation overlays
• Build Account Structures and Advanced Rules that replicate the intent of SAP field status groups
• Select the correct D365 mechanism for each parallel-accounting pattern in the source system
• Design a fiscal calendar that matches the SAP fiscal year variant
• Explain the differences in period-close tooling and what replaces the SAP period-locking mechanism

Introduction

SAP's finance configuration is a layered architecture: three chart-of-accounts tiers stacked on each other, field status groups that govern what must be entered on every posting line, parallel ledgers for multiple GAAP frameworks, and a fiscal year variant system that can represent any accounting calendar.

SAP's three-layer chart of accounts

SAP supports three distinct chart-of-accounts concepts, and the field-level mechanics matter — the concepts are frequently confused in migration documentation.

Decomposing the coding block: main account and dimensions

Every SAP posting line in BSEG carries a coding block: a combination of G/L account plus cost centre, profit centre, internal order, WBS element, business area, functional area, and other fields — each a distinct organisational reference. This is the SAP account assignment model.

Parallel accounting: posting layers and the ledger question

SAP's New GL supports multiple parallel ledgers per company code: a leading ledger (0L, reported in FAGLFLEXT or FAGLFLEXA) that receives all postings, and non-leading ledgers (e.g., 2L for local GAAP) that receive the same postings plus GAAP-specific adjustments.

Fiscal calendars, currencies, and period close

Fiscal calendars. SAP's fiscal year variant (T009, with period definitions in T009B) supports non-calendar fiscal years, 4-4-5 patterns, special periods for year-end adjustments, and split-year configurations. D365 uses a Fiscal Calendar (FiscalCalendar) per legal entity, which replicates any period structure.

Knowledge check

Summary

SAP finance configuration is a layered architecture that must be translated by intent, not migrated by field. Every configuration choice encodes a business requirement; that requirement is what carries across to D365.