Intercompany Accounting & Reconciliation in Turkey | SystemsCPA

Reviewed by Evren Özmen, CPA (SMMM)
Turkish Certified Public Accountant · Licensed by TÜRMOB, Reg. No. 35675 · Last reviewed September 2026
SystemsCPA | Intercompany Control for Turkish Subsidiaries

Intercompany Accounting & Reconciliation in Turkey

Intercompany transactions are rarely just accounting entries. For a Turkish subsidiary, a management fee, service recharge, loan, royalty or software charge can affect local accounting, VAT, withholding tax, transfer pricing, foreign-currency reporting and group consolidation at the same time. A controlled intercompany process connects all of those layers before month-end.

Updated: 12 September 2026 Reviewed by: Evren Özmen, SMMM Audience: CFOs, Group Controllers, Tax Directors & Foreign-Owned Companies Jurisdiction: Türkiye
Quick Answer

Intercompany accounting in Turkey should follow a documented process: identify the related-party transaction, confirm the contract and business purpose, determine the accounting period and currency, review Turkish VAT and withholding implications, assess transfer-pricing support, record the transaction consistently, reconcile the balance with the group counterparty and resolve differences before consolidation. The exact Turkish tax treatment depends on the nature of the payment, the parties and any applicable tax treaty, so accounting and tax review should be coordinated rather than performed separately.

RecordCorrect entity, period, account, currency and counterparty.
Tax-checkVAT, withholding and treaty implications reviewed where relevant.
ReconcileTurkish balance agrees with the group counterparty.
ConsolidateGroup eliminations start from matched, explainable balances.

Why Intercompany Accounting Is a High-Risk Area

Related-party transactions sit at the intersection of finance, tax and legal documentation. A local accounting team may see an invoice. Group tax may see a transfer-pricing transaction. Treasury may see a funding movement. The consolidation team may see an elimination difference.

If those teams work from different data, the same transaction can be correct in one file and wrong in another.

The SystemsCPA approach

We treat intercompany as a controlled sub-ledger within the monthly close. Each material transaction should have a clear counterparty, transaction type, agreement, accounting treatment, tax review status and reconciliation owner.

Request an Intercompany Process Review

Which Intercompany Transactions Are Common in Turkey?

TransactionAccounting questionTax / control question
Management feeWhich period and cost centre should bear the charge?What services were actually received, how is the fee priced, and what Turkish VAT / withholding treatment applies?
Shared-service rechargeIs it a direct expense, allocated cost or pass-through item?Is the allocation basis supportable and arm’s length?
Software / IT chargeExpense, prepaid cost or another classification?Is the payment a service, licence, royalty or mixed arrangement for Turkish tax purposes?
Royalty / IP feeWhich period and entity uses the IP?Withholding, treaty and transfer-pricing review may be required.
Intercompany loanPrincipal, accrued interest and FX are tracked separately.Arm’s-length interest, withholding, thin-capitalisation and other tax rules may be relevant.
Product purchase / saleInventory, revenue, COGS and cut-off must align.Transfer-pricing method, customs and related tax implications may apply.
Employee rechargePayroll cost and recharge revenue / expense should reconcile.Service substance, allocation and local tax treatment require review.
Cash poolingCash movements and interest must be distinguished.Financing terms and related-party pricing should be documented.

Start With the Agreement — Not the Invoice

A recurring intercompany invoice should be supported by an agreement or other documentation that explains the underlying transaction. The accounting entry should reflect the actual commercial arrangement rather than only the label printed on the invoice.

For a recurring related-party service, the finance file should normally answer:

  • Who provides the service?
  • Who receives and benefits from it?
  • What is the service period?
  • How is the fee calculated?
  • Is there a mark-up?
  • What allocation key is used?
  • Which currency applies?
  • When is the invoice issued?
  • Which Turkish taxes may be triggered?
  • Which transfer-pricing documentation supports the charge?
Control point: a generic invoice description such as “management fee” is not a substitute for understanding the underlying service, pricing logic and tax characterisation.

Transfer Pricing: The Arm’s-Length Principle

Article 13 of the Turkish Corporate Tax Law applies the arm’s-length principle to transactions between related parties. The law covers not only ordinary purchases and sales but also transactions such as rentals, financing, remuneration and other arrangements that create payments between related parties.

For the finance team, this means the accounting amount and the transfer-pricing amount cannot be managed in isolation. The local ledger should contain enough transaction detail to support the annual related-party reporting and transfer-pricing documentation process.

A strong operating file can therefore include:

  • Related-party master list.
  • Transaction category by counterparty.
  • Annual transaction value.
  • Agreement reference.
  • Pricing methodology.
  • Benchmark / support reference where relevant.
  • VAT / withholding status.
  • Transfer-pricing documentation status.

VAT and Withholding: Do Not Use One Rule for Every Recharge

Cross-border related-party charges can trigger Turkish VAT or withholding obligations depending on the nature of the underlying payment. A service fee, royalty, interest payment and software arrangement should not automatically be treated the same way.

The review should consider:

  • What is the legal and economic character of the payment?
  • Where is the service performed and where is it utilised?
  • Is reverse-charge / responsibility VAT relevant?
  • Does Turkish domestic withholding apply?
  • Could an applicable double-tax treaty change the withholding result?
  • Is a residency certificate or other treaty evidence required?
  • Does the transaction contain more than one element?

Because the outcome is transaction-specific, SystemsCPA recommends documenting the tax treatment by transaction category rather than applying a blanket rate to all intercompany invoices.

Intercompany Loans and Financing

Related-party financing requires a separate control file because principal, interest and foreign-exchange movements can easily become mixed in the ledger.

Accounting controls

  • Loan principal by agreement.
  • Accrued interest.
  • Payments and repayments.
  • Currency and FX movements.
  • Current / non-current classification.
  • Counterparty confirmation.

Tax controls

  • Arm’s-length interest rate.
  • Withholding analysis.
  • Treaty analysis where relevant.
  • Thin-capitalisation review.
  • Transfer-pricing documentation.
  • Potential VAT or other transaction-specific implications.

Management Fees and Shared-Service Recharges

Management-fee and shared-service charges often create the largest volume of questions because the commercial benefit is less visible than a product purchase.

A defensible recurring process should show:

  1. The nature of the service provided to the Turkish company.
  2. The evidence that the Turkish entity received or benefited from the service.
  3. The cost pool used by the group.
  4. The allocation key applied to the Turkish entity.
  5. The mark-up, if any, and the pricing rationale.
  6. The period covered by the charge.
  7. The Turkish accounting classification.
  8. The VAT / withholding analysis.
  9. The transfer-pricing support.

The accounting team should be able to connect the invoice back to this support without rebuilding the file during a tax audit or statutory audit.

Monthly Intercompany Reconciliation Process

1

Extract balances by counterparty

Separate receivable, payable, loan, accrued interest and P&L transactions for each related entity.

2

Exchange statements

Send the Turkish balance to the group counterparty and obtain its corresponding balance before consolidation.

3

Classify differences

Identify whether the difference is caused by invoice timing, FX, cut-off, missing documents, credit notes, accruals or accounting classification.

4

Post corrections where appropriate

Record agreed accounting corrections in the correct period and retain support for the journal.

5

Document unresolved items

Items not resolved before the group deadline should remain on an open-issues schedule with owner, amount and expected resolution.

6

Release the group balance

Provide headquarters with the matched balance and any documented differences that remain for consolidation.

Why Intercompany Balances Do Not Match

DifferenceExampleControl response
TimingParent books a recharge in December; Turkey receives the invoice in January.Apply agreed cut-off and accrual policy.
FXEntities use different exchange rates or revaluation dates.Separate true principal difference from FX difference.
One-sided accrualOne entity accrues an invoice that the other side has not recorded.Exchange accrual schedules before close.
Credit noteCredit note posted by one entity but not the other.Match invoice / credit-note references.
Wrong counterpartyCharge posted to the parent instead of a regional service company.Use counterparty master-data controls.
Different classificationTurkey records a loan; counterparty records trade payable.Agree transaction nature and mapping.
WithholdingNet cash paid differs from gross intercompany invoice balance.Reconcile gross invoice, withholding liability and net settlement separately.

Gross vs Net: Withholding Can Create False Differences

Where Turkish withholding applies, the cash paid to the foreign related party may be lower than the gross invoice or accrued expense because part of the amount is paid to the Turkish tax authority.

The accounting reconciliation should therefore distinguish:

  • Gross intercompany expense or payable.
  • Withholding tax liability.
  • Net cash paid to the counterparty.
  • Tax payment to the Turkish authority.

If the counterparty records only the net cash receipt while the Turkish entity carries the gross payable, the group may report an intercompany difference even though the underlying settlement is economically correct.

Foreign Currency and FX Differences

Intercompany balances are frequently denominated in EUR, USD or another foreign currency. The Turkish ledger and the parent company may therefore show different local-currency amounts even when the foreign-currency principal agrees.

The reconciliation should first match the transaction currency. Only then should the finance team explain:

  • Local-currency translation.
  • Month-end revaluation.
  • Realised FX differences on settlement.
  • Unrealised FX differences at period-end.
  • Group reporting translation differences.
If the EUR 100,000 principal matches on both sides, a TRY / EUR reporting difference is not automatically an intercompany break. Reconcile the transaction currency first.

Intercompany and Month-End Close

Intercompany reconciliation should occur before the group reporting pack is released, not after headquarters discovers an elimination difference.

A strong close calendar therefore places intercompany work alongside bank, payroll and tax reconciliations. This makes the Turkish finance team responsible for delivering a confirmed or clearly explained position by the group deadline.

See Month-End Close & Financial Control in Turkey.

Intercompany and Group Reporting

The local accounting balance and the consolidation balance need different but connected controls. The Turkish ledger records the transaction. Group reporting then maps the account, counterparty and reporting category so consolidation can eliminate the corresponding balances and transactions.

Useful group-reporting fields include:

  • Counterparty legal entity code.
  • Transaction category.
  • Balance-sheet / P&L account.
  • Transaction currency.
  • Group reporting currency.
  • Confirmation status.
  • Difference amount.
  • Difference reason.
  • Expected resolution date.

See Management & Group Reporting in Turkey.

Year-End and Audit Readiness

Related parties are a recurring audit focus because they can affect both recognition and disclosure. A year-end intercompany file should therefore be more complete than the ordinary monthly reconciliation.

The year-end package can include:

  • Related-party master list.
  • Year-end confirmations.
  • Transaction totals by category.
  • Loan and interest schedules.
  • Management-fee and recharge calculations.
  • Agreements.
  • Transfer-pricing documentation references.
  • VAT / withholding support.
  • Outstanding disputes or unmatched items.

Common Intercompany Control Failures

No owner

Accounting records the charge, tax reviews it later, and group finance assumes someone else reconciled it.

No counterparty dimension

All related-party balances sit in one account, making entity-level reconciliation difficult.

No recurring tax logic

The same monthly charge is reassessed manually every period because no transaction tax matrix exists.

No gross/net bridge

Withholding payments create apparent group differences.

No cut-off policy

Entities record the same recharge in different months.

No documentation link

The ledger amount cannot be tied quickly to agreement, invoice, allocation and transfer-pricing support.

What SystemsCPA Can Support

Accounting

  • Counterparty mapping
  • Intercompany sub-ledger design
  • Accruals and cut-off
  • Loan and interest schedules
  • FX reconciliation

Tax coordination

  • VAT treatment review
  • Withholding analysis
  • Treaty-document coordination
  • Transfer-pricing data preparation
  • Tax-to-GL reconciliation

Group close

  • Counterparty confirmations
  • Difference analysis
  • Open-items tracking
  • Group reporting mapping
  • Audit support

Frequently Asked Questions

What is intercompany reconciliation in Turkey?

It is the process of comparing the balances and transactions recorded by a Turkish company with the corresponding records of its related group entities and resolving or documenting differences before reporting and consolidation.

Why do intercompany balances differ?

Common causes include invoice timing, different exchange rates, one-sided accruals, missing credit notes, incorrect counterparty coding, withholding tax, different transaction classifications and late document processing.

Are management fees subject to Turkish tax?

The Turkish tax treatment depends on the nature of the underlying service, the parties, where the service is used, domestic tax law and any applicable tax treaty. VAT, withholding and transfer-pricing issues should be reviewed for the specific arrangement.

Does a related-party service charge need transfer-pricing support?

Related-party transactions fall within Turkey’s transfer-pricing framework. The appropriate documentation depends on the transaction and applicable reporting requirements, but the pricing should be supportable under the arm’s-length principle.

How should intercompany loans be accounted for?

The finance file should separately track principal, interest accruals, payments, repayments and foreign-exchange movements and reconcile the balance with the counterparty. Turkish withholding, transfer-pricing and other financing rules should also be reviewed.

Can withholding tax cause an intercompany mismatch?

Yes. The Turkish company may record a gross expense or payable while paying part of the amount to the foreign counterparty and part to the Turkish tax authority as withholding. The reconciliation should bridge gross invoice, withholding and net settlement.

Should intercompany balances be reconciled monthly?

For multinational groups with monthly or quarterly consolidation, monthly reconciliation is usually the stronger control because differences can be identified before the group reporting deadline instead of at year-end.

Should reconciliation be done in TRY or transaction currency?

Where the transaction is denominated in a foreign currency, it is usually useful to reconcile the original transaction currency first and then explain local-currency and reporting-currency FX differences separately.

Can SystemsCPA coordinate directly with group counterparties?

Yes. Depending on scope, SystemsCPA can exchange intercompany statements, investigate differences and report unresolved items directly with the relevant group finance contacts.

Can SystemsCPA also support transfer-pricing compliance?

SystemsCPA can support the accounting data, related-party transaction mapping and finance-side documentation needed for transfer-pricing compliance and coordinate the relevant tax analysis based on the agreed engagement scope.

Related SystemsCPA Guides

Official Reference Framework

  • Turkish Corporate Tax Law, Article 13 — transfer pricing through disguised profit distribution and the arm’s-length principle.
  • Transfer Pricing General Communiqué No. 1 and subsequent amendments.
  • Turkish VAT Law and the VAT General Application Communiqué for cross-border service and responsibility-VAT analysis.
  • Applicable Turkish withholding-tax rules and double-tax treaties for transaction-specific cross-border payments.
Intercompany accounting & reconciliation

Does Your Turkish Intercompany Balance Match Before Group Close?

Send us your related-party list, intercompany trial balance, recurring charge types, loan schedules and group reconciliation template. We can map the transactions, identify recurring accounting and tax control points and build a monthly intercompany process for the Turkish subsidiary.

Request an Intercompany Review Explore Group Reporting

This material is general information and does not constitute a transaction-specific tax or legal opinion. VAT, withholding, treaty and transfer-pricing treatment should be confirmed for each material related-party arrangement.

Work with a licensed Turkish CPA firm

Turn Turkey compliance into certainty

SYSTEMS CPA supports foreign-owned companies with company formation, accounting, tax compliance and payroll in Turkey — one accountable local partner. Reviewed by Evren Özmen, SMMM (Certified Public Accountant), TÜRMOB Reg. No. 35675.

Schedule a Consultation →

Evren Özmen, CPA (SMMM)

Turkish Certified Public Accountant (SMMM), licensed by TÜRMOB — Reg. No. 35675. Advising international investors and companies on Turkish tax, accounting and compliance at OZM Consultancy, Istanbul.