Finance Support for Shared Service Centers in Turkey | SystemsCPA

The Gap Between a Global SSC and a Turkish Legal Entity

Centralized finance creates scale. A single shared service center can process accounts payable, accounts receivable, general ledger, fixed assets, payments and reporting for dozens of countries. The model becomes less efficient, however, when local requirements are handled only after the group process has finished.

Türkiye creates exactly this type of interface challenge. The Turkish entity may use the group ERP and centralized workflows, but it still has local requirements around statutory accounting, tax, e-Fatura, e-Arşiv, e-Defter, payroll accounting, withholding, VAT, corporate tax, related-party reporting, audit support and local financial statements.

Why Multinationals Still Need a Local Finance Layer

In multinational finance models, the local controller or statutory finance function typically sits between the shared service center, group finance and local authorities. The local responsibility is not primarily high-volume transaction processing; it is statutory accounting, close quality, tax, audit, reconciliations and interpretation of Turkish requirements.

The problem is rarely that the SSC cannot post an invoice. The problem is that a centralized team may not know whether the Turkish posting creates the correct:

• VAT treatment,
• withholding-tax treatment,
• statutory account classification,
• e-document treatment,
• period cut-off,
• tax deductibility,
• related-party reporting position,
• or year-end statutory adjustment.

Those are local finance-control questions, not merely transaction-processing questions.

A Typical SSC Operating Model for Turkey

1. Accounts Payable: Central Processing, Local Tax Control

An SSC can efficiently receive, approve and post invoices. The Turkish challenge is ensuring that the invoice is not only operationally processed but also locally correct.

Local review can include:

• Whether the document is valid for Turkish accounting and tax purposes.
• Correct VAT coding.
• Reverse-charge / responsibility VAT where relevant.
• Withholding-tax treatment.
• Expense deductibility and documentation.
• Correct Turkish statutory account.
• Related-party identification.
• Accrual and period cut-off.
• Vendor ageing and unusual open items.

The objective is not to duplicate every SSC approval. It is to create a risk-based local review layer around the transactions that can affect Turkish compliance.

2. Accounts Receivable and Turkish E-Invoicing

The group billing process may be centralized, but Turkish invoicing is closely connected with the local e-document environment and VAT rules.

Depending on the entity and transaction profile, the local workstream can include:

• e-Fatura / e-Arşiv coordination,
• invoice timing,
• VAT treatment,
• export / service-export documentation,
• credit notes and corrections,
• customer ageing,
• cash application differences,
• bad-debt or doubtful-receivable review,
• reconciliation of AR sub-ledger to Turkish statutory accounts.

3. Month-End Close: Who Owns the Turkish Sign-Off?

One of the biggest control gaps in a centralized model is ownership. The SSC may close the ERP on Day 3, but the Turkish entity still needs someone to confirm that the resulting local balance sheet is supportable.

A Turkish close review can include:

• Bank reconciliation.
• AR and AP ageing.
• Payroll liabilities.
• Tax accounts.
• Intercompany balances.
• Prepayments and accruals.
• Fixed assets.
• Inventory where relevant.
• Advances and deposits.
• Shareholder / related-party balances.
• Old open items.

SystemsCPA can provide the local close sign-off layer before the numbers are released to headquarters.

See Month-End Close & Financial Control in Turkey.

4. Local Statutory Books vs Group ERP

The group chart of accounts is designed for consolidation. Turkish statutory books are designed to meet local accounting and tax requirements. A well-designed SSC model needs a controlled bridge between the two.

The strongest model maps these structures once and controls the mapping continuously rather than rebuilding a local trial balance manually at year-end.

5. Tax Compliance: The SSC Data Must Tie to the Return

A tax return prepared from local spreadsheets that do not reconcile to the SSC ledger is a recurring control weakness. SystemsCPA can build the bridge from centralized accounting data to Turkish tax compliance.

Depending on scope, this can include:

• VAT returns and supporting reconciliation.
• Withholding-tax returns.
• Payroll-related tax coordination.
• Corporate income tax provision and return support.
• Advance / provisional tax.
• Domestic minimum corporate tax where applicable.
• Transfer-pricing disclosures.
• Pillar Two / QDMTT local data where applicable.

The control principle is simple: each material tax filing should reconcile back to the accounting system.

6. Intercompany: One of the Most Common SSC Failure Points

Intercompany transactions move across countries, currencies and teams. That makes them particularly vulnerable to mismatches in a centralized operating model.

Typical issues include:

• One-sided accruals.
• Different invoice timing.
• Gross vs net balances because of Turkish withholding.
• FX differences.
• Incorrect counterparty coding.
• Management-fee or royalty classification.
• Missing agreements.
• Unresolved balances at consolidation.

SystemsCPA can reconcile the Turkish side and coordinate with the group counterparty or SSC before the consolidation deadline.

See Intercompany Accounting & Reconciliation in Turkey.

7. Payroll-to-GL: HR Data Is Not the Same as Accounting Control

Multinational payroll is often processed by a local payroll vendor but funded or controlled through global HR and finance systems. The local ledger then needs to reconcile:

• Gross salaries.
• Employer social-security costs.
• Employee deductions.
• Income-tax withholding.
• SGK liabilities.
• Benefits and bonuses.
• Net payroll payments.
• Payroll accruals.

The SSC may post the payroll journal. The local finance layer should confirm that the journal agrees to the Turkish payroll records and statutory liabilities.

8. Treasury, Payments and Cash Visibility

Central treasury can control liquidity at group level, while the Turkish company still needs local cash planning for payroll, taxes, suppliers and intercompany settlements.

SystemsCPA can support:

• Local bank-account reconciliation.
• Payment-calendar visibility.
• Tax and payroll cash forecasting.
• Intercompany funding reconciliation.
• Cash-flow reporting to headquarters.
• Support for local bank and statutory documentation.

The objective is to make local cash requirements visible early enough for the group treasury team to act.

9. Group Reporting: Translate Turkish Issues Into HQ Language

Headquarters does not need a list of Turkish tax account codes. It needs to know what changed, why it changed and whether the local entity is under control.

A useful Turkish reporting layer can provide:

• Local-to-group trial-balance mapping.
• Statutory-to-IFRS adjustments.
• Balance-sheet reconciliation status.
• Tax provision and deferred-tax summary.
• Intercompany status.
• Audit / compliance open items.
• Material local risks.
• Close commentary for headquarters.

See Management & Group Reporting in Turkey.

10. Audit Readiness in an SSC Model

Auditors frequently request evidence that sits across both the SSC and local finance function. The ledger may be centralized, while tax returns, payroll, legal documents and statutory support remain local.

SystemsCPA can help build one local audit file covering:

• Trial balance and GL support.
• Bank reconciliations.
• AR / AP schedules.
• Fixed assets.
• Payroll.
• Tax returns and tax provision.
• Intercompany confirmations.
• Local contracts and statutory records.
• Audit adjustment tracking.

See Audit Readiness & Year-End Close Support in Turkey.

SSC Responsibility Matrix: Who Owns What?

The exact RACI should be agreed at onboarding. The purpose is to eliminate the phrase: “We thought the SSC was doing that.”

Service Models

When Does This Model Work Best?

The SSC + SystemsCPA model is particularly relevant when:

• The Turkish entity has no full local finance team.
• The company has one local finance manager but needs strong statutory support.
• AP / AR / GL processing has moved to a regional SSC.
• The Turkish entity uses SAP, Oracle, NetSuite or another global ERP.
• Headquarters wants faster month-end close and cleaner reconciliations.
• The group has recurring statutory-to-IFRS differences.
• Local audits generate too many late requests.
• Turkish tax filings depend on manual data extraction from the SSC.
• The group is acquiring or restructuring its Turkish operations.

Onboarding a Turkish Entity Into the SSC Model

Common Failure Points in SSC Models

What SystemsCPA Can Support

Frequently Asked Questions

Related SystemsCPA Guides

• Foreign Subsidiary Accounting in Turkey — the core accounting model for international groups.
• Month-End Close & Financial Control in Turkey — local close and balance-sheet control.
• Management & Group Reporting in Turkey — statutory ledger to headquarters reporting.
• Intercompany Accounting & Reconciliation in Turkey — related-party balances and group close.
• Audit Readiness & Year-End Close Support in Turkey — local audit support and PBC readiness.
• Outsourced Finance Function in Turkey — broader local finance operating model.