Chart of Accounts in the SAP System

In SAP, the chart of accounts is a systematic structure that contains all the general ledger accounts used by one or more company codes.

For each general ledger account, the chart of accounts contains the account number, the account name, and control information that defines the account’s function. In the operational chart of accounts, this information also specifies how the account is created and used in the respective company code. The chart of accounts thus forms the central framework of financial accounting in SAP S/4HANA and serves as the basis for every posting as well as for internal and external reporting.

SAP S/4HANA Cloud Public Edition offers three types of charts of accounts for mapping business transactions and generating financial reports in accordance with various accounting standards (e.g., IFRS, HGB, local GAAP):

Operational Chart of Accounts (also known as the global chart of accounts): Contains the general ledger accounts for the daily postings of all company codes and is used in both Accounting and Financial Close as well as in Management Accounting and Margin Analysis. The predefined standard chart of accounts YCOA is country- and industry-neutral and can be adopted as is or customized as a template.
Group Chart of Accounts: Basis for consolidation and group reporting. Note: If you use Group Reporting, a chart of items is also required.
Alternative (Local) Chart of Accounts: Optional and country-specific to comply with local financial reporting requirements. SAP provides standard content for many countries, including mapping to the operational chart of accounts YCOA; if this is missing, you can create and transport your own alternative chart of accounts.

Best Practices for Use

Enable Posting to Alternative Accounts

For company codes with an alternative chart of accounts, enable the use of alternative accounts in the "Posting Document Processing Options" app. When entering a document, you can then enter the alternative account number; the system displays it in the G/L Account field and the corresponding operational account in the G/L Account (Company Code Chart of Accounts) field.

Uniform Operational Chart of Accounts for Multiple Company Codes

Use the same operational chart of accounts (e.g., YCOA) for all company codes to ensure group-wide consistency and reporting. If necessary, supplement this with an alternative chart of accounts for each company code to meet local requirements.

Structured Maintenance Process

Perform configuration and master data changes exclusively in the development system and transfer them to the production system via the test system. For urgent changes (e.g., during upgrades), also use the “Synchronize G/L Account Master Data” app to ensure a complete change log.

Clear Role Assignment

Copy and customize the standard role templates as a basis: SAP_BR_BPC_EXPERT (Configuration), SAP_BR_GL_ACCOUNTANT (General Ledger Accountant), and SAP_BR_ADMINISTRATOR (Administration).

Naming Conventions & Documentation

Define mandatory number ranges for each account class (assets, liabilities, expenses, revenue) and centrally document mappings between the operational, consolidated, and alternative charts of accounts — this reduces errors in consolidation and local financial statements.

Challenges

Transport and Synchronization Process: Changes to general ledger account master data are transported from the development system to the production system. To generate a change log, the changes must also be manually transferred using the “General Ledger Account Master Data Synchronization” app before the transport run — a step that is often overlooked and can lead to a lack of traceability.
Mapping Multiple Accounting Standards in Parallel: Supporting IFRS, local GAAP, and the consolidated view simultaneously requires consistent coordination between the operational, alternative, and consolidated charts of accounts, including correct mappings — mapping errors directly result in incorrect consolidated or local financial statements.
Governance and Authorizations: Since chart of accounts changes have far-reaching implications for postings and reporting, roles such as SAP_BR_BPC_EXPERT, SAP_BR_GL_ACCOUNTANT, and SAP_BR_ADMINISTRATOR must be clearly delineated to prevent uncontrolled changes and compliance violations (e.g., GoBD, SOX).

RELEVANT SAP TRANSACTIONS and Fioris

SAP Transactions

Transaction	Purpose
OB13	Create / Maintain Chart of Accounts
OBY6	Assigning the Operational Chart of Accounts to the Company Code
FS00	Centralized Maintenance of General Ledger Account Master Data
FSP0	Maintain G/L Accounts at the Chart of Accounts Level