SAP Global Rollout for Tier 1 Automotive Suppliers: Designing a Chart of Accounts for Global Standardization and Local Statutory Compliance

When a Tier 1 automotive supplier rolls out SAP S/4HANA globally, the chart of accounts is not simply an FI configuration item. It is the common language that connects procurement, manufacturing, quality, sales, costing, consolidation, and local statutory reporting on a shared data foundation.

If global standards are given too much priority, local entities’ statutory financial statements, tax requirements, and audit needs can become an afterthought. If local chart-of-accounts structures are adopted unchanged, journal entries and cost-comparison dimensions become fragmented by country. This article explains the core design approach Tier 1 suppliers should take, covering SAP chart-of-accounts structures, practical account examples, a multinational subsidiary rollout scenario, and key implementation checks.

Conclusion: Use a common operating chart of accounts (OCOA) for daily postings and global management, then address statutory reporting requirements in each country through a local chart of accounts and reporting mappings. SAP distinguishes the OCOA used for daily postings from country-specific charts of accounts that meet local statutory reporting requirements (SAP Help).

).

Why Chart-of-Accounts Design Is Difficult for Tier 1 Suppliers

Tier 1 suppliers must understand profit and loss and cost performance by OEM, vehicle model, plant, and component. They also need to account for more detailed cost and revenue elements than typical trading or service businesses: prototypes, dies, tooling, development costs, quality defects, warranty provisions, and supplier price variances, in addition to mass-production parts.

Even within a single category such as “revenue,” sales of mass-production parts, service parts, dies, recoveries for engineering changes, and quality compensation represent distinct business realities for management decision-making. If these items are posted using different account numbers or descriptions in each country, manual reclassification is required every time the organization compares global-procurement price variances, plant yield, or OEM profitability.

The first decision in chart-of-accounts design is therefore not which country’s account numbers to adopt. It is how far to standardize, within the OCOA, the management dimensions that must be compared globally. Local statutory requirements should be met without undermining that standard.

The Three Types of Chart of Accounts in SAP

SAP allows charts of accounts assigned to a company code to be organized by purpose. SAP Help explains that the operating chart of accounts “contains the G/L accounts that you use for daily posting in your company code. Financial Accounting and Controlling both use this chart of accounts” (SAP Help).

Type	Role	Typical Tier 1 Use Case
Operating COA (OCOA)	Common foundation for daily postings, FI/CO, and management accounting	Procurement, production, shipments, billing, cost allocations, and monthly close
Group COA	Account dimension for consolidation and group reporting	Consolidation packages, IFRS adjustments, and global P&L comparisons
Country-Specific COA (Local/Alternative COA)	Account structure for statutory reporting in a country or region	Statutory financial statements, local audits, and country-specific filing formats

SAP defines a country-specific chart of accounts as one that contains the G/L accounts required to meet a specific country’s legal reporting requirements, and its assignment to a company code is optional (SAP Help).

“Optional” does not mean that statutory compliance is unnecessary. It means the design must determine, for each country, industry, and legal-entity type, whether the OCOA can be used as is, a country-specific COA must be added, or reporting transformation alone is sufficient.

Core Design Principle: Make the Global OCOA Primary and the Country-Specific COA Secondary

For a Tier 1 global template, the following structure is practical.

1. Design a common OCOA. Standardize the meaning and level of detail of accounts needed to compare profitability by OEM, product group, and plant worldwide.
2. Assign a local COA by company code where needed. Add a local COA only in countries that require statutory account numbers, account descriptions, or statutory aggregation.
3. Map the OCOA to the local COA. Maintain alternative account numbers on OCOA G/L accounts. SAP guidance describes assigning the local COA to the company code, creating the required G/L accounts, and assigning them as alternative accounts to the OCOA (SAP Help).
4. Separate financial statement versions and reports by reporting purpose. Enable global management reports, country-level financial statements, and consolidation reporting to be produced from the same trial balance through different presentation dimensions.

The advantage of this approach is that standardization and local fit do not become an either-or choice. Automated postings across SD, MM, PP, FI, and CO remain stable through the common OCOA, while country-specific statutory presentation is switched through the local COA and reporting definitions.

Practical Tier 1 Chart-of-Accounts Examples

The following is an example of a global OCOA. The account numbers are illustrative only and should be designed to fit each company’s existing coding structure, group-consolidation policy, and local requirements.

OCOA	Account Name	Main Business Event	Management Objective
110100	Accounts Receivable – OEM	Billing OEMs for mass-production parts	Collection and credit management by OEM
120100	Raw Materials	Receipt of steel, resin, and electronic components	Visibility into raw-material inventory and inventory count variances
120200	Work in Process	Inter-process inventory and unfinished goods	Visibility into inventory dwell time by plant and process
120300	Finished Goods	Completed components and service parts	Visibility into finished-goods inventory, aging, and write-downs
140100	Dies and Tooling	Dies requiring identification of customer versus company ownership	Alignment of ownership, depreciation, and customer billing
210100	Accounts Payable – Material Suppliers	Liabilities to Tier 2 suppliers and material manufacturers	Global procurement and payment-terms management
400100	Product Revenue – Mass Production	Sales of mass-production parts to OEMs	Profitability by OEM, vehicle model, and plant
400200	Product Revenue – Service Parts	Aftermarket and service parts	Separation of mass-production and service-part profitability
400300	Die and Tooling Revenue	Customer billing for die and tooling costs	Avoidance of confusion with development and mass-production profitability
500100	Material Costs	Direct material consumption based on the BOM	Purchase price variance and yield analysis
500200	Labor Costs	Direct labor, temporary labor, and indirect labor before allocation	Productivity analysis by plant
500300	Manufacturing Overhead	Utilities, maintenance, depreciation, and quality-related costs	Allocation-basis and standard-cost variance analysis
510100	Purchase Price Variance	Difference between standard and actual purchase prices	Analysis of raw-material inflation and supplier negotiations
510200	Production Volume Variance	Variance against standard production volume	Visibility into capacity utilization and fixed-cost absorption
610100	Quality Assurance Costs	Sorting, recalls, and customer-claim responses	Visibility into cost of poor quality and quality costs by customer
220200	Product Warranty Provision	Provision for expected future warranty costs	Warranty-risk management by product group and OEM

The critical point is not to express every business dimension through G/L accounts alone. For example, keep “Product Revenue – Mass Production” as a common account, while maintaining OEM, customer, product hierarchy, vehicle model, plant, profit center, and segment in master data and subledgers. This avoids chart-of-accounts proliferation while allowing multidimensional analysis of OEM and component profitability.

Example: Rolling Out SAP S/4HANA from Japan to China and Europe

Consider a rollout in which a Japan headquarters deploys SAP S/4HANA to a China sales company and plant, as well as to a European manufacturing company.

Case 1: Purchase of Raw Materials from a Japanese Tier 2 Supplier and Receipt at the China Plant

text

Debit   120100 Raw Materials                              10,000,000

Credit  210100 Accounts Payable – Material Suppliers      10,000,000

Use the OCOA accounts for raw materials and accounts payable, with supplier, material, plant, purchasing organization, and cost center held as supporting attributes. When price variances arise, the design should make purchase price variance visible in a separate account according to the standard-price or moving-average-price policy.

Case 2: Shipment and Billing of Mass-Production Parts from the China Plant to an OEM

text

Debit   110100 Accounts Receivable – OEM                  15,000,000

Credit  400100 Product Revenue – Mass Production          15,000,000

Record this revenue in the OCOA. If financial statements, forms, or filings compliant with Chinese Accounting Standards for Business Enterprises (ASBE) are required in China, map the OCOA accounts for receivables and revenue to the corresponding China local-COA accounts, then produce local presentation through alternative accounts and the financial statement version (FSV).

Case 3: Production Volume Falls Below Plan and Creates Under-Absorbed Fixed Costs

text

Debit   510200 Production Volume Variance                  2,000,000

Credit  500300 Manufacturing Overhead                      2,000,000

If volume variance is mixed into a plant’s generic “other costs,” the organization cannot distinguish under-absorbed fixed costs caused by demand fluctuations from actual cost overruns. For Tier 1 suppliers, electrification, vehicle-model changes, and OEM production fluctuations directly affect profitability. It is therefore valuable to define the accounts and cost elements required for variance analysis in the global template.

What Should Change in China and Europe, and What Should Not?

China has guidance for accounting subjects, key accounting treatments, and financial statements that supports ASBE. China’s Ministry of Finance explains that the guidance covers “accounting subjects and financial statements,” including accounting subjects, key accounting treatments, statement formats, and preparation requirements (China Ministry of Finance).

Accordingly, a China company code can use OCOA accounts such as “Raw Materials,” “Product Revenue – Mass Production,” and “Quality Assurance Costs” for daily postings while mapping them to the local accounts, aggregation rows, and statements required for ASBE reporting. However, the primary materials reviewed here do not support a definitive conclusion that identical fixed account numbers are uniformly mandatory for every Chinese enterprise. Legal-entity industry, applicable accounting standards, tax and electronic-filing requirements, and audit requirements should be confirmed with local accounting and tax specialists in China (China Ministry of Finance).

The design decision also differs by country in Europe. In Spain, for example, the General Accounting Plan (PGC) is mandatory for all companies, while exceptions exist concerning the binding nature of Part Four on account numbers and descriptions (Spanish Official State Gazette, BOE).

Do not automatically adopt local account numbers into the OCOA merely because a national accounting plan exists. Confirm whether the actual requirement concerns recognition, measurement, financial-statement presentation, account numbers, or electronic filing.

Ten Items IT and PM Teams Should Confirm First

Global-template design should not be left to the FI team alone. IT and PM should include at least the following ten items in their design-review exit criteria.

1. Management comparison dimensions: Determine whether OEM, region, plant, product group, vehicle model, program, and service parts will be compared through accounts, organizational structures, or master-data attributes.
2. OCOA design principles: Define how far account-level granularity will be standardized based on common business processes and global profitability analysis, rather than country-specific requests.
3. Need for a local COA: Identify, country by country, whether statutory account numbers, descriptions, financial-statement lines, or electronic filing are required.
4. Mapping ownership: Define who approves OCOA-to-local-COA mappings among global finance, local accounting, tax, and audit stakeholders.
5. Impact on automatic account determination: Confirm that the design does not disrupt MM GR/IR, inventory valuation, price variances, SD billing, manufacturing costs, fixed assets, taxes, or intercompany account determination.
6. Alignment with cost management: Confirm consistency with cost elements, cost centers, activity types, internal orders, production orders, product costing, and margin analysis.
7. Ownership management for dies and tooling: Decide where customer-owned versus company-owned assets, depreciation, billing, and return status will be managed across accounts, fixed assets, inventory, and sales orders.
8. Visibility into quality and warranty costs: Ensure sorting, scrap, customer claims, recalls, and warranty provisions can be tracked by OEM, product, and plant.
9. Migration and comparability: Ensure unique mappings can be established among legacy accounts, the new OCOA, the local COA, and consolidation accounts during balance migration.
10. UAT and statutory-reporting audit trail: Confirm that journal entries, trial balances, statutory financial statements, tax and electronic filings, and consolidation reports can be reproduced from the same balances and approved by local owners.

SAP presents the option of adding and assigning country-specific and group charts of accounts to the OCOA (SAP Help).

Configuration alone, however, does not automatically make taxes, electronic filing, fixed assets, withholding tax, or subsidiary ledgers compliant. IT and PM teams need to govern COA design as one part of the broader localization scope.

Common Failure Modes and How to Avoid Them

Failure 1: Using Local Statutory Account Numbers as the Global Standard

Directly adopting local statutory account numbers in the OCOA creates unnecessary constraints for other countries and group reporting. Design the global OCOA as the common language for business processes and management accounting, and handle local numbers through a local COA or report mapping.

Failure 2: Trying to Build OEM Profitability Through G/L Accounts Alone

Creating separate accounts for every OEM, vehicle model, product, and plant quickly makes the COA impossible to maintain. Use accounts for economic nature, and distribute analytical dimensions across profit centers, segments, materials, customers, sales orders, and cost objects.

Failure 3: Confirming Local Statutory Requirements Late in Template Design

When local requirements are confirmed too late, rework affects not only the COA but also tax configuration, reports, electronic filing, interfaces, and migration design. During the early Fit-to-Standard stage, establish a gate at which local accounting and tax specialists sign off on the requirements.

Failure 4: Managing COA Mappings Only in Excel

Excel is useful during early design, but it does not provide control unless it is connected to change history, effective dates, test evidence, transport requests, and the legal basis for each requirement. The mapping register should include the OCOA, local COA, FSV line, consolidation account, legal basis, owner, approver, effective date, and test cases.

Summary

In a SAP global rollout for a Tier 1 automotive supplier, the chart of accounts is not a task of merely configuring local account numbers. It is the architecture that enables global standards for comparing profitability by OEM, plant, and component while also meeting statutory reporting requirements in each country.

The practical starting point is to place the OCOA at the foundation of global daily postings and management accounting; map country-specific COAs for statutory reporting; and validate the design across FSVs, taxes, electronic filing, and subsidiary ledgers. SAP’s separation of the OCOA, Group COA, and country-specific COA by purpose is an important premise supporting this design approach (SAP Help).

).

The quality of a global template should not be measured by the number of account codes. It should be assessed by whether the same business facts can be recorded consistently in every country while correct local statutory reporting can be reproduced at the same time.

---

Reference Links

• SAP Help: Chart of Accounts
  SAP’s definition of operating, group, and country-specific charts of accounts, including their roles in daily postings, group reporting, and country-level legal reporting.
• SAP Help: How to Create an Alternative Chart of Accounts
  SAP’s process for assigning an alternative local chart of accounts to a company code and linking alternative G/L accounts to operating accounts.
• Deloitte IAS Plus: China
  An English overview of China’s Accounting Standards for Business Enterprises (ASBEs), including their application to listed companies and their relationship with IFRS.
• ICAC: Spanish General Accounting Plan — English Translation
  An English translation published by Spain’s accounting and audit authority. It includes the accounting framework, recognition and measurement standards, annual accounts, and the chart of accounts.
• ICAEW: Accounting in France
  An English overview of French accounting, including the Plan Comptable Général and the availability of the latest official French source.

---

Disclaimer

Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.

---

Back to Top