Turkish Chart of Accounts vs Group Chart of Accounts: A Guide for Multinational Companies

What Is the Turkish Uniform Chart of Accounts?

The Turkish Uniform Chart of Accounts — commonly referred to in Turkey as the Tekdüzen Hesap Planı — forms part of the Turkish statutory accounting framework established under the Accounting System Implementation General Communiqués.

It provides a structured account framework and account classifications for the recording of business transactions in Turkish statutory books.

For a foreign parent company, however, the important point is not simply memorising Turkish account codes.

The important question is:

Is the Turkish Chart of Accounts the Same as TFRS?

No.

This distinction is important for international finance teams.

The Turkish chart of accounts is primarily an accounting-record and classification framework. TFRS — Turkish Financial Reporting Standards — is a financial reporting framework.

They perform different functions.

One transaction can therefore have a Turkish statutory account, a group reporting account and additional reporting adjustments without creating a contradiction.

Does a Foreign-Owned Turkish Company Have to Use the Parent Company’s Chart of Accounts?

A Turkish subsidiary can be integrated into the parent’s global chart of accounts, but the group structure should not prevent the company from satisfying Turkish statutory bookkeeping requirements.

In practice, multinational groups generally solve this through account mapping.

This architecture allows headquarters to preserve global consistency while the Turkish entity preserves local accounting integrity.

Example: Mapping Turkish Accounts to a Global Chart of Accounts

Consider a multinational company with a central group chart of accounts.

The mapping might conceptually look like this:

The table is illustrative rather than a universal mapping.

The correct mapping depends on the group’s reporting structure, industry, ERP configuration, management-reporting requirements and the level of detail required by both local and headquarters finance teams.

Why One-to-One Mapping Often Does Not Work

One of the most common misconceptions is that every Turkish account should correspond to exactly one group account.

In reality, the relationship can be:

• one Turkish account to one group account;
• several Turkish accounts to one group account;
• one Turkish account to several group reporting categories; or
• dependent on additional dimensions such as cost centre, department, counterparty or transaction type.

Administrative expenses provide a simple example.

Turkish statutory accounting may capture several costs within a broad local expense structure, while headquarters may require separate reporting for:

• HR;
• legal;
• IT;
• finance;
• professional fees;
• marketing;
• regional management costs; and
• shared service charges.

The mapping therefore needs more than GL account numbers. It may also require cost centres, profit centres, departments, project codes or reporting dimensions.

Turkish Statutory Accounting vs Group Reporting

The local ledger and the group reporting package should not be treated as competing versions of the accounts.

They serve different users.

How Should SAP, Oracle or NetSuite Handle Turkish Account Mapping?

The design depends on the group’s ERP architecture.

SAP, Oracle, NetSuite, Microsoft Dynamics and other global systems can all form part of the accounting architecture of a Turkish subsidiary.

The important issue is how the ERP connects the group’s accounting structure with Turkish statutory requirements.

Common approaches include:

1. Parallel Account Structures Inside the ERP

The ERP maintains sufficient information to produce both group and local accounting views.

This can provide strong integration but requires careful implementation and governance.

2. Global ERP With Turkish Statutory Mapping

The group ERP remains the primary transaction environment while Turkish statutory accounts are generated through a mapping table or localization layer.

This is often appropriate where headquarters operates a centralised global ERP.

3. Global ERP Plus Local Accounting System

Transactions are processed in the global ERP and transferred into a Turkish statutory accounting environment.

This can work efficiently provided the interface is controlled and the two ledgers are reconciled systematically.

For the broader systems architecture, see:

ERP Localization in Turkey: Connecting SAP, Oracle or NetSuite to Turkish Statutory Accounting

What Should a Chart-of-Accounts Mapping File Contain?

A mapping file should be treated as part of the company’s financial-control environment rather than as an informal spreadsheet.

A robust mapping register typically includes:

This turns the mapping table from a one-time implementation document into a controlled finance master-data register.

Why Intercompany Accounts Need Separate Mapping

Related-party balances deserve particular attention.

Headquarters may distinguish between:

• trade intercompany receivables;
• management-fee balances;
• royalty balances;
• intercompany financing;
• cash-pool positions;
• cost allocations;
• shared-service charges; and
• dividend or shareholder balances.

If the Turkish ledger records all related-party flows inside broad accounts without adequate counterparty and transaction-level detail, group elimination and transfer-pricing reconciliation become unnecessarily difficult.

Related reading: Intercompany Accounting & Reconciliation in Turkey .

How Should VAT and Tax Accounts Be Mapped?

Tax accounts are another area where excessive aggregation can create problems.

Headquarters may prefer a single account called “Indirect Taxes,” while Turkish finance may need considerably more granular information to manage VAT, withholding taxes, payroll-related liabilities and other statutory obligations.

The group mapping can aggregate those balances for reporting purposes, but the local ledger should preserve sufficient detail to support compliance and reconciliation.

In other words:

What Happens With IFRS Adjustments?

A Turkish statutory trial balance may not by itself equal the balance required for group IFRS reporting.

Depending on the company, additional reporting adjustments may arise from areas such as:

• leases;
• provisions;
• revenue recognition;
• impairment;
• employee benefits;
• deferred tax;
• foreign-currency accounting;
• inflation accounting;
• group accounting policies; and
• purchase-price accounting following an acquisition.

These adjustments should not disappear inside an unexplained Excel workbook.

The group reporting process should clearly distinguish:

Should IFRS Adjustments Be Posted Into the Turkish Statutory Ledger?

Not automatically.

Whether an adjustment belongs in the Turkish statutory books, a separate reporting ledger or the consolidation layer depends on the nature of the adjustment and the financial reporting framework applicable to the company.

This is why multinational finance teams should distinguish between:

• statutory bookkeeping entries;
• Turkish tax adjustments;
• financial reporting adjustments; and
• group consolidation adjustments.

Combining all four into one undifferentiated process makes reconciliation harder and weakens the audit trail.

Chart of Accounts Mapping for Shared Service Centres

The issue becomes particularly important when a Turkish subsidiary is processed by a regional or global shared service centre.

The SSC may understand the group’s global chart perfectly but may not have detailed knowledge of Turkish statutory classification and tax requirements.

The Turkish finance operating model should therefore determine:

See also: Finance Support for Shared Service Centers in Turkey .

The Monthly Reconciliation Is More Important Than the Initial Mapping

Creating a mapping table during ERP implementation is relatively easy.

Keeping it accurate is harder.

Problems usually begin when:

• headquarters opens a new GL account;
• a new product line starts;
• new intercompany flows are introduced;
• an acquisition changes the reporting structure;
• new tax codes are created;
• employees post manually to generic accounts; or
• local accounting changes are not reflected in the group mapping.

For that reason, the mapping should form part of the monthly close.

A Practical Monthly Control

Common Chart-of-Accounts Mapping Mistakes in Turkey

1. Copying the Turkish Trial Balance Into Excel Every Month

Manual extraction can work at small scale, but repeated transformation through spreadsheets creates unnecessary key-person risk and version-control problems.

2. Mapping Only Balance-Sheet Accounts

P&L classification is often equally important because headquarters may require expense reporting by function, department, business unit or cost centre.

3. Using “Other” Accounts Too Frequently

Generic accounts can make local bookkeeping easier in the short term but reduce visibility for headquarters and complicate tax, audit and transfer-pricing analysis.

4. Allowing Headquarters to Open Accounts Without Local Review

A new global account may have unexpected implications for Turkish statutory classification, VAT, withholding or intercompany reporting.

5. Treating the Mapping File as Static

Business models, ERP structures and reporting requirements change. The mapping should therefore have an owner and an approval process.

6. Confusing Statutory Accounting With IFRS Reporting

An account mapping solves classification issues. It does not, by itself, solve differences in accounting recognition, measurement or financial-reporting policy.

Chart of Accounts Mapping During an Acquisition

Chart mapping becomes particularly important after a foreign group acquires a Turkish company.

The acquired entity may have operated for years using its own Turkish accounting structure while the buyer expects reporting under a completely different global model.

The first post-acquisition finance workstream should normally establish:

• the acquired company’s existing statutory trial balance;
• the buyer’s global chart of accounts;
• the initial account mapping;
• opening-balance reconciliation;
• intercompany classification;
• reporting adjustments;
• group reporting deadlines; and
• responsibility for maintaining the bridge.

This is one reason finance integration should begin immediately after completion rather than several months after the transaction.

See: M&A Transaction Advisory in Turkey .

Chart Mapping Checklist for a Foreign-Owned Turkish Company

Who Should Own the Mapping?

Mapping should not belong exclusively to the local accountant, ERP consultant or headquarters finance team.

Each party owns a different part of the answer.

How SystemsCPA Supports Multinational Chart-of-Accounts Mapping

SystemsCPA works with international finance teams that need to connect their Turkish statutory accounting environment with a global ERP and reporting structure.

Our role is not to replace the group’s ERP architecture.

We focus on the Turkish statutory, tax and reporting bridge.

Depending on the company’s structure, support can include:

• reviewing the Turkish statutory chart of accounts;
• mapping local accounts to the group chart;
• identifying tax-sensitive and intercompany accounts;
• designing monthly reconciliation controls;
• supporting ERP localization projects;
• working with shared service centres;
• reviewing statutory-to-group reporting differences; and
• supporting post-acquisition finance integration.

The objective is straightforward: headquarters should be able to understand how the Turkish numbers reach the group reporting package, and local finance should be able to demonstrate how the same numbers reconcile back to the Turkish books.

Frequently Asked Questions

Disclaimer: This article provides general information on accounting, ERP and reporting structures in Türkiye. It does not constitute accounting, tax, legal, audit or ERP implementation advice for a specific company. The appropriate accounting and reporting framework depends on the entity’s activities, regulatory status, financial reporting obligations and group policies.