Turkey is one of the most misunderstood ERP markets in the world. For a CIO or CFO of a mid-market company managing a subsidiary in Istanbul, Bursa, or Izmir, the instinct is often to roll out the group ERP: SAP Business One, Microsoft Dynamics 365 Business Central, or Odoo. That instinct is rarely the right call — and often a source of serious regulatory exposure.
Turkey has built, since 2014, one of the most advanced e-invoicing systems in the world, well ahead of Germany or the UK. Its tax authority, the GİB (Gelir İdaresi Başkanlığı), imposes digital compliance requirements that most European ERP systems cannot handle natively. Local vendors — Logo Tiger, Mikro, Netsis, Uyumsoft — were designed from the ground up to meet these demands. Ignoring them means exposing your subsidiary to tax penalties and the chronic double-entry that comes from running a local workaround alongside your group consolidation.
This guide maps the Turkish ERP market, details the e-Dönüşüm regulatory framework, and provides a decision matrix for international mid-market companies entering or already operating in Turkey.
Why the Turkish ERP Market Is Fundamentally Different
The e-Dönüşüm Digital Tax Framework: e-Fatura, e-Arşiv, e-İrsaliye, e-Müstahsil
e-Dönüşüm (“digital transformation” in Turkish) is the fiscal digitization program launched by the GİB in 2012. It encompasses several distinct obligations that any ERP operating in Turkey must cover natively.
e-Fatura is the mandatory electronic invoice exchanged between companies registered on the GİB platform. It relies on an XML-UBL 2.1 format transmitted in real time to the GİB portal, which validates and timestamps each invoice before routing it to the recipient. Any invalid e-Fatura — incorrect format, expired certificate, or duplicate sequence number — has no legal standing. Companies whose annual turnover exceeds 3 million TRY (approximately €85,000 at September 2026 exchange rates) are subject to this requirement, with thresholds lowered to 500,000 TRY for high-risk sectors: e-commerce, real estate, motor vehicles, and energy. As of 1 January 2026, the per-invoice e-Arşiv threshold has been eliminated, effectively making electronic invoicing universal for all Turkish businesses (AccountsOS, January 2026).
e-Arşiv Fatura is the e-Fatura equivalent for invoices issued to recipients not registered on the GİB system (private individuals, smaller businesses not yet enrolled). The format is identical, but the validation circuit differs.
e-İrsaliye is the electronic delivery note. Mandatory for companies subject to e-Fatura whose operations involve physical goods deliveries, it must be issued before transport and transmitted to the GİB. Coverage is steadily expanding: according to the Turkish tax authority, mandatory scope continues to widen through quarterly GİB communiqués.
e-Müstahsil is the electronic receipt for purchases from agricultural producers — a niche requirement but non-negotiable for food and beverage industries or cooperatives with direct farm sourcing.
KDV (Turkish VAT) and Its Accounting Specifics
KDV (Katma Değer Vergisi) is the Turkish equivalent of VAT. Since July 2023, the standard rate rose from 18% to 20%, with reduced rates of 10% (basic food, restaurants) and 1% (housing, press). That mid-fiscal-year rate change exposed the fragility of poorly localized European ERPs: a rate update applied globally on a group ERP can generate incorrect KDV declarations with immediate fiscal consequences.
KDV reporting is monthly for companies above the thresholds, with filing and payment due within 28 days of month-end. ERPs must generate KDV reconciliation reports in the formats mandated by GİB — a constraint few European ERPs meet without a dedicated localization module.
The depreciation of the Turkish lira (TRY) adds another layer of complexity for subsidiaries of international companies: books must be kept in TRY for the GİB, but consolidated in EUR (or GBP, USD, etc.) for the group. Multi-currency management with monthly revaluation of foreign-currency assets is a functional imperative.
The Localization Barrier: Why an Uncertified ERP Generates Fines
The GİB accredits ERP vendors that wish to issue e-Fatura directly (either “entegratör” mode or “portal” mode). An uncertified ERP cannot issue valid e-Fatura documents. Companies must then route through an accredited intermediary (an “özel entegratör” such as Uyumsoft, DIA Yazılım, or Sovos), which adds cost, latency, and operational dependency.
Fines for e-Fatura non-compliance are substantial and escalating: from 3,400 TRY per invoice not issued electronically (2024 schedule, revised annually) up to enhanced penalties for repeat violations. For a subsidiary issuing several hundred invoices per month, non-compliance becomes expensive fast.
Key Turkish ERP Vendors to Know
Logo Tiger 3: Mid-Market Industrial Leader
Logo Yazılım is the largest enterprise software vendor in Turkey. Founded in 1984 in Gebze (Kocaeli province), the group has been listed on the Istanbul Stock Exchange since 2000 (ticker: LOGO) — the first Turkish technology company to IPO. According to its annual reports, Logo serves more than 200,000 companies across its product range, from micro-businesses to large mid-market firms (Logo Software, Annual Report 2024).
Logo Tiger 3 is the group’s flagship ERP, positioned for companies with 50 to 2,000 employees in manufacturing, distribution, international trade, and services. Tiger 3 natively integrates the full e-Dönüşüm framework (e-Fatura, e-Arşiv, e-İrsaliye), KDV management, Turkish payroll (including İşkur contributions and semi-annual minimum wage revisions), and interfaces with the Turkish banking system.
Logo Tiger 3 Enterprise specifically targets multinational mid-market companies with Turkish subsidiaries: it supports intercompany consolidation, simultaneous multi-currency management (EUR/USD/TRY), IFRS reporting alongside local fiscal standards, and open REST APIs for synchronization with a group ERP. Logo has actively built these capabilities to capture multinationals that need a robust connector between their group ERP and the Turkish tax environment.
Strengths. Native GİB-certified e-Dönüşüm coverage, advanced production module with MRP and scheduling, integrated Turkish payroll, a dense partner network across Turkey, and a product roadmap that tracks GİB regulatory changes in near-real time: Logo has historically released compliance patches within weeks of each GİB communiqué.
Limitations. Tiger 3’s UI, although modernized in recent versions, is perceived as less contemporary than cloud-native ERPs by IT teams accustomed to Microsoft or Salesforce standards. Support in European languages (English, German, French) is limited and typically requires local partners.
Mikro Yazılım: SMB Accounting Specialist, Now in the TeamSystem Orbit
Mikro Yazılım, founded in 1988 in Istanbul, is one of the long-standing players in the Turkish SMB ERP market. Its flagship product, Mikro, covers accounting, commercial management (purchasing/sales), inventory, and payroll for companies with 5 to 100 employees. Paraşüt, its cloud product launched in 2012, targets very small businesses with a modern web interface and accounting automation.
Mikro Yazılım was acquired by Italian group TeamSystem in August 2023, as part of the publisher’s European expansion strategy (CB Insights). The combined group — Mikro, Paraşüt, and DIA Yazılım (acquired in April 2026) — is now one of the most significant players in the Turkish SMB ERP market under an international banner. TeamSystem crossed the €1 billion revenue mark in 2024 with more than 2.5 million clients across Europe (Data Manager Online, May 2025).
Strengths. Accessible entry price (Paraşüt: monthly TRY subscription), fast onboarding, native e-Fatura and e-Arşiv compliance, large network of accountants and chartered accountants trained on Mikro across Turkey.
Limitations. Functional coverage is insufficient for industrial mid-market companies: no advanced production module, no project management, basic MRP planning. For a 50+ employee subsidiary with manufacturing processes, Mikro will fall short.
Netsis: SMB Distribution and Trading, Integrated Under Logo
Netsis is a brand acquired by Logo Yazılım (the acquisition dates to 2013 based on available market data). Netsis is now a product line within the Logo group, maintained separately from Tiger for market positioning and installed-base reasons. The platform serves more than 40,000 business customers according to published industry data (Techiz Blog, 2026).
Positioning. Netsis targets distribution, trading, and international commerce (import/export) companies with 20 to 200 employees. Its historic strength is advanced commercial management: multi-warehouse management, order tracking, barcode labeling, e-commerce integration with Turkish platforms (Trendyol, Hepsiburada), and customs compliance for import/export.
Strengths. Deep functional coverage in inventory management and distribution, native e-Dönüşüm, more accessible licensing cost than Logo Tiger, and an extensive partner network in the trading sector.
Limitations. As with all Logo/Netsis products, the UI modernity lags behind cloud-native alternatives. Manufacturing capabilities remain limited compared to Logo Tiger Enterprise.
Uyumsoft: e-Transformation Specialist, 100,000+ Companies
Uyumsoft is a unique case in the Turkish ERP market. The company is not a generalist ERP vendor in the conventional sense: its original positioning is as a digital fiscal compliance specialist (e-Fatura, e-Arşiv, e-İrsaliye) — as its name signals (“uyum” means “compliance” in Turkish). With more than 100,000 business clients, Uyumsoft is one of the most powerful players in the e-Dönüşüm compliance market (Uyumsoft / RocketReach).
Its DIA platform (the predecessor to DIA Yazılım, now merged into the entity acquired by TeamSystem in 2026) offers a cloud ERP covering accounting, CRM, e-invoicing, and e-commerce, with a modular architecture that lets companies of different sizes start with a limited scope — e-Fatura compliance only, for instance — and progressively expand toward a full ERP.
For international mid-market companies, Uyumsoft/DIA is particularly relevant as a compliance connector: a company that retains SAP or Dynamics as its group ERP can route through Uyumsoft solely for e-Dönüşüm management of its Turkish subsidiary, synchronizing data via API without disrupting the group ERP.
Strengths. Best-in-class e-Dönüşüm expertise in Turkey, agile cloud architecture, attractive pricing for a compliance-only scope, easy integration with third-party ERPs via API, and now the financial and technological backing of TeamSystem.
Limitations. Full ERP functional depth (manufacturing, projects, complete HRIS) remains below Logo Tiger. The merger with TeamSystem/Mikro is recent (2026): the consolidated product roadmap has not yet been clarified publicly.
Paraşüt and Cloud-Native Options for Small Subsidiaries
For subsidiaries with fewer than 20–30 employees and no complex manufacturing processes, Turkish cloud-native solutions such as Paraşüt (Logo/TeamSystem), BizimHesap, KolayBi, or Logo İşbaşı offer sufficient coverage at very accessible prices (monthly TRY subscriptions, up and running in hours). These solutions are not suited to an industrial mid-market company but are valid for a representative office, a lightweight commercial subsidiary, or a local holding structure.
Group ERP vs. Local ERP: Four Scenarios for Mid-Market Companies
Scenario 1: Impose SAP/Dynamics/Odoo with Native Turkish Localization
This scenario is viable only if your group ERP vendor offers a GİB-certified Turkish localization maintained in real time. SAP Business One and SAP S/4HANA have Turkish localizations, but they typically require a supplementary module from a GİB-accredited integrator (such as Sovos or a local SAP partner) for e-Fatura transmission. Microsoft Dynamics 365 also offers a Turkey localization, maintained by Microsoft and its partners.
Advantages. Uniform group reference, a single instance to administer, simplified consolidation.
Risks. The Turkish localization of a European ERP is often one or two regulatory cycles behind GİB communiqués. Compliance updates can take three to six months to deploy while the regulatory obligation is immediate. Always verify the date of the last e-Dönüşüm compliance patch before committing to this scenario.
Ideal profile. Mid-market company with a 200+ employee subsidiary, significant IT budget, and a local technical team capable of managing localization updates.
Scenario 2: Standalone Turkish ERP with API Sync to Group Accounting
The subsidiary runs on Logo Tiger or Netsis for all local processes. A custom-built or iPaaS middleware connector synchronizes aggregated accounting data to the group ERP for consolidation.
Advantages. Guaranteed e-Dönüşüm compliance, native Turkish payroll, local teams on a tool they know with local support.
Risks. Dual-reference data governance, risk of KDV/VAT discrepancies in the consolidated balance sheet if accounting mapping is not rigorous, API connector maintenance burden.
Ideal profile. Mid-market company with a manufacturing or commercial subsidiary of 30 to 500 employees and low dependency on real-time processes between Turkey and headquarters.
Scenario 3: Hybrid — Local ERP for Accounting and Payroll, Group ERP for Manufacturing
This scenario is common in industrial mid-market companies with a solid group ERP in production (SAP PP, Dynamics Supply Chain) but insufficient Turkish localization on the finance side. The subsidiary uses Logo Tiger for accounting, payroll, and e-Dönüşüm compliance. The group ERP manages production planning, manufacturing orders, and procurement.
Advantages. Best of both worlds for each functional domain.
Risks. High integration complexity, dual maintenance costs. Synchronizing bills of materials and cost accounting between the two systems is technically demanding.
Ideal profile. Industrial mid-market company with a Turkish production site of at least 100 employees, strong IT maturity, and an integrator capable of managing both platforms.
Scenario 4: Group ERP Retained, e-Dönüşüm Compliance via Uyumsoft/DIA
This scenario keeps the group ERP for all operational processes but outsources e-Dönüşüm compliance to a GİB-accredited intermediary such as Uyumsoft or DIA Yazılım. The group ERP pushes invoice data to the intermediary, which formats, signs, and transmits it to the GİB.
Advantages. Guaranteed e-Dönüşüm compliance without changing the group ERP, fast deployment (a few weeks), cost limited to the intermediary’s service fee.
Risks. Dependency on a third party for a business-critical regulatory process. If the intermediary experiences downtime or revises its pricing, your invoicing flow is directly impacted. Reconciling data between the group ERP and GİB statements requires periodic manual reconciliation.
Ideal profile. Lightweight commercial subsidiary (representative office, holding entity) with no local production, or a mid-market company that wants to secure its Turkish compliance quickly during a longer ERP migration.
Decision Matrix: 8 Criteria for Choosing Your ERP Architecture in Turkey
| Criterion | Logo Tiger Enterprise | Netsis | Mikro / Paraşüt | Uyumsoft / DIA | SAP/Dynamics Localized |
|---|---|---|---|---|---|
| Native GİB Certification | Yes | Yes | Yes | Yes (specialist) | Via partner add-on |
| Turkish Payroll (kıdem tazminatı) | Native | Partial | Native (Mikro) | Limited | Via third-party module |
| MRP Production Module | Full | Limited | No | No | Full |
| Intercompany / Group Consolidation | Yes (Enterprise) | No | No | Via API | Yes |
| TCO 50–150 FTE Subsidiary | €40,000–100,000 | €20,000–60,000 | €5,000–20,000 | €10,000–30,000 | €80,000–200,000 |
| Deployment Timeline | 3–6 months | 2–4 months | 1–3 months | 1–2 months | 6–18 months |
| Local Turkish Support | Excellent | Excellent | Excellent | Excellent | Variable (partner) |
| e-Dönüşüm Roadmap | Proactive | Reactive | Proactive | Market leader | Partner-dependent |
TCO note: The ranges above are indicative figures based on published pricing and 2026 market intelligence. They cover licensing, implementation, and first-year maintenance for a 50–150 FTE subsidiary, but vary significantly based on process complexity and the number of modules activated. No figure is guaranteed without consulting a local integrator.
What Changes in 2027: Obligations to Anticipate
e-İrsaliye expansion to all sectors. The mandatory scope of e-İrsaliye continues to widen. Companies still exempt in 2026 should monitor GİB communiqués: extension to sectors not yet covered is expected progressively through end-2027. Any ERP deployed in Turkey should include a functioning e-İrsaliye module even if the obligation is not yet active for the relevant sector.
Strong signal: real-time VAT reporting. Turkey is watching the Hungarian RTIR (Real-Time Invoice Reporting) model closely — one in which companies transmit invoice data to the tax authority in near-real time, without a monthly delay. The GİB issued signals in 2026 indicating interest in this model, which would represent a major evolution of the current system. An ERP whose e-Fatura architecture relies on daily or weekly batch processing would be structurally ill-suited to such a regime. Companies selecting their Turkish ERP in 2026 should verify that the vendor has a real-time API architecture — not just a file-generation module for e-Fatura.
Conclusion: Recommendations by Subsidiary Profile
The Turkish ERP market is not an “emerging” market where approximate tooling is acceptable. It is one of the most advanced digital fiscal compliance environments in the world, with a significant manufacturing base (automotive, textiles, steel, chemicals) and economic growth that pushes mid-market companies to structure their processes quickly.
Industrial subsidiary with 50+ employees and local production. Logo Tiger 3 Enterprise is the natural choice. The cost is justified by native functional depth and robust GİB compliance. Plan an API connector to the group ERP for consolidation.
Commercial or distribution subsidiary with 20–100 employees. Netsis is competitive in this segment, especially if the activity centers on trading and import/export. Mikro remains relevant for lighter structures.
Small subsidiary or representative office. Paraşüt or Logo İşbaşı cover the requirements with minimal deployment time and TCO.
International company that wants to retain its group ERP. Scenario 4 — an e-Dönüşüm connector via Uyumsoft or DIA Yazılım, now under the TeamSystem umbrella — is the path of least resistance to securing Turkish fiscal compliance without a full ERP project. TeamSystem’s growing footprint in this segment (via Mikro + DIA) offers continuity for groups already using TeamSystem in Italy, the UK, or elsewhere in Europe.
In all cases, auditing the Turkish localization of your group ERP — if one exists — is non-negotiable before deciding. The question is not “does our ERP support Turkey in theory?” but “how long does it take between a GİB communiqué and a compliance patch deployed to production?”. The answer to that question separates genuinely localized ERPs from cosmetic compliance modules.
For further reading, explore our guide to German ERP solutions (proALPHA, ABAS, GoBD, ZUGFeRD) for a comparison with another high-regulatory-constraint local market, our article on the ERP market in Poland and the Czech Republic for Central European context, and our analysis of the TeamSystem acquisition of DIA Yazılım and ACD France to understand the consolidation reshaping the Turkish ERP landscape.
