Charts of accounts

A chart of accounts is the list of G/L accounts a company uses, with their numbers, names and basic properties. In SAP S/4HANA it is a separate object from the company code: you define a chart once and assign it to as many company codes as you like. That design is what lets a group use one set of accounts across many legal entities, while still meeting local rules.

There are three roles a chart of accounts can play. Most groups use at least two.

Operational chart

The operational chart holds the accounts users actually post to. Every company code must have one. Company codes that share an operational chart share account numbers and chart-level settings, which makes cross-company reporting and controlling simple. SAP's learning material notes an important consequence: company codes that should be analyzed together in one controlling area need the same operational chart of accounts.

Group chart

A group chart gives one uniform set of accounts for consolidated reporting when company codes use different operational charts. Each operational account carries a group account number that maps it to the group chart. If every company code already uses the same operational chart, a separate group chart may not be needed.

Country chart

Some countries prescribe a statutory chart of accounts. Rather than forcing users to post on that chart, the company keeps posting on the operational chart and maps each account to a country account through the alternative account number in the company code data. In SAP S/4HANA the alternative account number is written into the Universal Journal line at posting, so it must be maintained before the first posting to the account, not added later.

Designing an operational chart

A chart of accounts outlives every system it runs on, so a few design choices deserve care. Decide the account number length and keep it consistent. Reserve number ranges by area (for example balance sheet accounts in one range, revenue in another, expenses in a third) so that an account's number tells people roughly what it is. Keep the chart lean: an account should exist because a report, a control or a legal requirement needs it, not because one cost center wanted its own line. Detail that belongs to controlling, such as which department spent the money, belongs on cost centers and profit centers, not in extra G/L accounts.

Assigning the chart to a company code is a configuration step in the company code's global settings. Once postings exist, changing a company code's operational chart is a major project, which is why the decision is made early in an implementation and documented.

In Public Edition

Public Edition delivers predefined charts: YCOA as the operational chart, YGR1 as the group chart, and country-specific charts where needed. Customers add accounts within those charts rather than designing a chart from scratch. In Private Edition and on-premise, the chart is the customer's design, often starting from SAP Best Practices content.