If you run a foreign-owned subsidiary in Türkiye, you live with two reporting realities. The local books follow VUK (Vergi Usul Kanunu — Tax Procedures Law) for tax and statutory purposes. The group reporting pack typically expects IFRS (International Financial Reporting Standards) and a foreign reporting currency. Many subsidiaries reconcile the two manually each month — Excel sheets, side accounting, late closes. This guide explains how a properly architected Turkish ERP produces both views from the same source transactions, and where the manual reconciliations live in the meantime.

Note: Specific accounting policies, GAAP gap mappings and tax treatments are jurisdiction- and entity-specific. Always work with your CPA and group controller for the exact treatment in your circumstances.

Why this matters

A typical foreign-owned Turkish subsidiary closes its local books by day 7 of the month, then spends days 8-15 manually mapping to group format. By the time HQ sees results, the data is half a month old and re-keying introduces errors. Audit findings and tax inspections then reveal that the manual mapping was inconsistent across periods.

A correctly configured ERP can run parallel ledgers — local TL/VUK for statutory and IFRS/group-currency for HQ — automatically. Group close drops from 10-15 days to 3-5.

The four reconciliation areas

1. Currency translation (TL → EUR/USD/GBP)

Three FX policies typically coexist:

Transaction date rate — for revenue, COGS, expenses (income statement items)
Period-end rate — for monetary assets/liabilities (balance sheet items)
Historical rate — for non-monetary assets like inventory, fixed assets at original cost

Manual translation each month is where errors creep in. The ERP should:

Capture the rate at every transaction
Apply the right policy per account class
Produce both TL ledger and group-currency ledger
Track translation differences in OCI (other comprehensive income)

2. Timing differences (VUK vs IFRS)

Common gaps:

Item	VUK treatment	IFRS treatment
Severance pay	Recognized at termination	Accrued each period (defined benefit)
Inventory	Often ortalama / FIFO with simple LCM	Cost or NRV with detailed obsolescence policy
Fixed assets	Tax depreciation rates	Useful life-based, possibly different
R&D	Often expensed	Capitalize when criteria met
Leases	Mostly operating	IFRS 16 right-of-use asset for most leases
Bonuses	When paid (cash basis)	Accrued in period earned

The ERP should record transactions once and produce two views through GAAP-mapping rules.

3. Inflation accounting (when applicable)

When Türkiye is classified as a hyperinflationary economy under IFRS criteria, IAS 29 inflation accounting applies. This adjusts non-monetary balances using a price index (typically TÜFE / CPI). VUK has its own inflation accounting framework when activated by the government.

These two systems differ in mechanics. ERP can pre-compute the IAS 29 adjustment for group reporting while keeping VUK statutory books intact.

4. Intercompany transactions

If your Turkish subsidiary trades with sister entities, the ERP must:

Tag intercompany transactions clearly
Match against the counterparty subsidiary's records
Surface mismatches before group consolidation
Support transfer pricing documentation

A good ERP includes an intercompany matching dashboard so reconciliations happen continuously, not at month-end.

What "good" looks like

A well-architected setup:

One transaction record, two ledger views (TL/VUK + Group/IFRS)
Daily FX rates loaded automatically (TCMB or third-party feed)
Monthly close runs the GAAP adjustments and currency translation in one batch
IFRS pack is produced automatically by close + 3 days
Audit trail shows every adjustment with reason code
Intercompany variances raised and resolved before close

What "manual" looks like (and why it fails)

Symptoms:

Excel "translation sheet" maintained by one person
Group close blocked when that person is on leave
Severance, bonus, lease accruals re-derived each month
IC variances surfaced at year-end, then back-dated
Two data sets that drift apart, audit findings on consistency

Useful additional reports for HQ

Beyond the standard P&L / balance sheet pack, group controllers typically request:

Working capital roll-forward (DSO, DIO, DPO)
Cash flow waterfall by entity and currency
Headcount and personnel cost split by department / cost center / project
Capex commitments and pipeline
Tax balances (current and deferred)
Significant variance commentary (auto-flagged if >X% deviation)

A modern ERP makes all of these one-click reports in group format.

ERP capability checklist for cross-border reporting

Parallel ledgers (statutory + group)
Multi-currency with policy-driven translation
GAAP adjustment engine (configurable mappings)
IAS 29 inflation accounting toggle
Intercompany matching dashboard
Daily FX rate ingestion (auto)
Group reporting pack templates
Drill-down from group balance to underlying transaction
Audit trail on every adjustment

Birasyo's group-reporting approach

Birasyo ERP includes:

Parallel TL (VUK) + group-currency (IFRS) ledgers
TCMB FX feed integration with overlays for special agreements
GAAP adjustment library for the 8 most common gap items
IAS 29 module activatable per period
Intercompany matching workbench
Group reporting pack generator (Excel + PDF + CSV for consolidation tools)
Drill-down from group P&L line to source transaction with full audit
API export to common consolidation tools (OneStream, BlackLine, Tagetik patterns)

If you're closing a Turkish subsidiary into a group structure and want a focused review of your reporting flow, book a session — we'll examine your current close calendar and identify quick wins.

Sources

VUK (Vergi Usul Kanunu) — Tax Procedures Law
Türkiye Sustainability and Financial Reporting Standards (TSRS / TFRS) frameworks
IFRS (IAS 21, IAS 29, IFRS 16) standards published by IASB

Cross-Border Group Reporting from a Turkish Subsidiary: VUK to IFRS, TL to EUR/USD