Regulation (Türkiye)

Türkiye's ÖKC-POS Integration Rules (2026)

Short answer: yes, it is mandatory. In Türkiye, both a restaurant's bank POS terminal and the POS software it runs must operate integrated with the fiscal cash register, known locally as the new-generation ÖKC. These rules are specific to Türkiye and apply to any food-service business operating there. The legal basis is Tax Procedure Law General Communiqué No. 483; the last leg of the obligation took effect on 1 October 2018, so it has been fully in force for years. The 2026 price of non-compliance starts at TRY 35,000 per detection for first-class merchants and companies, and climbs to three times that amount per transaction in cases like collecting payments through someone else's POS.

This guide reflects the legislation in force as of August 2026.

TRY 35,000
integration fine per detection in 2026
first-class merchants and companies
3x
per transaction, for using someone else's POS
1 Oct 2018
full effective date of the software integration rule

What the integration obligation actually means

Communiqué No. 483 (Official Gazette 30.09.2017, No. 30196, last amended 25.09.2024) imposes four distinct obligations. They all serve the same logic: every step of a sale enters the fiscal record, and no payment is collected outside the fiscal cash register.

  1. The bank POS works as one unit with the fiscal register. External bank and meal-card EFT-POS terminals must integrate with the ÖKC. The sale starts on the register, the amount is passed to the POS automatically, the transaction closes on the register, and the card slip data is embedded in the fiscal receipt. For meal-card payments, the register issues a non-fiscal information slip.
  2. Sales software connects to the register over GMP-3. Restaurant POS software, handheld order terminals, and any device producing non-fiscal printouts must connect to the new-generation ÖKC through the GMP-3 protocol. The deadline was 1 October 2018; there is no transition period left.
  3. Mobile standalone bank POS terminals are banned. The device that goes to the table must be a new-generation ÖKC with built-in EFT-POS capability, not a standalone mobile POS. Banks and payment institutions are barred from issuing standalone mobile POS terminals to businesses in scope.
  4. Z-report data flows to the tax authority automatically. Daily Z-report fiscal data is transmitted to the Revenue Administration (GİB) through TSM centers. Since the 25 September 2024 amendment, businesses that cannot transmit this way may, upon application, use an e-Archive special integrator or the Digital Tax Office channel. Keeping the connection continuously online is the business's responsibility.

GMP-3 and TSM: two acronyms, plainly

Who is in scope

The base rule sits in Article 1 of Law No. 3100: first- and second-class merchants who sell goods or provide services at retail, and who have sales for which they are not obliged to issue an invoice, must use a fiscal cash register. Restaurants and cafés sit squarely in scope.

In addition:

  • New businesses must acquire a new-generation ÖKC within 30 days of starting operations (60 days in priority development regions).
  • Production and sale of old-generation registers has been banned since 30 September 2017. Existing old devices could once be used until their fiscal memory filled up, but Communiqué No. 557 removed that exception and required every old-generation device to be replaced with a new-generation register by 1 July 2024. Today the integration rules apply to new-generation devices without exception.

Which device suits which business is a separate decision; we cover it step by step in our guide to choosing the right new-generation ÖKC. For the full picture of the fiscal register regime, see the 2026 fiscal cash register guide for Türkiye.

The 2026 price tag of non-compliance

Integration violations are punished with the special irregularity fine under repeated Article 355 of the Tax Procedure Law, charged separately for each detection. The 2026 amounts were set by Tax Procedure Law General Communiqué No. 588 (Official Gazette 31.12.2025, 5th bis edition).

Violation2026 amount (first-class merchants and companies)
Using a bank POS without fiscal register integrationTRY 35,000 per detection
Running POS software without a GMP-3 connectionTRY 35,000 per detection
Using a standalone mobile EFT-POS despite the banTRY 35,000 per detection
Failing to transmit Z-report data to GİB on timeTRY 35,000 per detection
Continued non-compliance after a fine and a granted deadlineThe above fines doubled
Collecting through someone else's POS, or lending your POS to someone elseTRY 105,000 per transaction, annual cap TRY 35,000,000

For second-class merchants the per-detection amount is TRY 17,000, and TRY 8,700 for other taxpayers. Fines for failing to issue receipts follow a separate regime with a tiered detection system that climbs from TRY 17,000 to TRY 170,000; see the full list of 2026 fiscal register fines.

Someone else's POS: the most expensive shortcut

A 2024 amendment introduced by Law No. 7524 directly targets a practice still seen in restaurants: collecting payments through a POS not registered to your own tax identity, or letting someone else collect through yours.

The fine is heavy in two ways:

  • It is charged per transaction, not per detection. In 2026, TRY 105,000 per transaction for first-class taxpayers, with an annual cap of TRY 35,000,000.
  • It is charged to both sides separately: the party lending the POS and the party using it.

Shortcuts like "running the restaurant's card payments through a relative's sole-proprietorship POS" can reach seven figures in a single inspection at a restaurant doing ten card transactions a day. Collecting revenue through someone else's name or bank account is a separate fine as well: 10% of the transaction amount, never less than the repeated Article 355 fine.

An exemption exists, but not a realistic one for restaurants

Article 6 of Communiqué No. 483 offers a fiscal register exemption to taxpayers who issue e-invoices or e-archive invoices for all their sales. The conditions make clear who it was written for: under the thresholds in the 2024 amendment text, a business must meet at least two of the criteria of TRY 110 million in sales revenue, TRY 110 million in total assets, and TRY 11 million in equity; own more than 50 new-generation ÖKC devices; be registered for e-invoice, e-archive, and e-ledger; and apply to GİB in writing and obtain approval. These amounts increase each year at the revaluation rate; check GİB announcements for the current thresholds.

In other words, the exemption is a door designed for the centralized invoicing scenario of chains with hundreds of branches. A standalone restaurant, or a business with a few branches, does not fit through it.

Common misconceptions

Many guides online either describe outdated rules or mix up the fine categories. The ones we see most often:

  1. The main risk is not the "failure to acquire a register" fine. The 2026 fine for not acquiring a fiscal register on time is TRY 11,700 and largely symbolic. The real financial risk accumulates in receipt violations (a tiered fine starting at TRY 17,000 per document and climbing to TRY 170,000 on repeat detections) and in the TRY 35,000 per-detection integration fines.
  2. "Only the user of someone else's POS gets fined" is outdated. Since 2024 the fine hits both sides separately, and per transaction.
  3. A customer complaint now multiplies the fine. A buyer who receives no receipt and reports it to the administration within 5 business days faces no fine themselves, while the seller's fine is tripled.
  4. Claims of "fines stacking endlessly" are exaggerated. If a single act triggers more than one fine under repeated Article 355, only the heaviest is charged. But separate acts detected separately are each fined on their own.

Compliant infrastructure protects both sides

In practice, all of this reduces to one sentence for the restaurant: the POS software and payment setup you use must be able to talk to your fiscal register over the GMP-3/TSM line. dojofood POS runs on this architecture; with its Pavo fiscal register integration and live e-Adisyon integration, the sale, the fiscal receipt, and the data transmission move in a single flow. Compliant infrastructure protects not just the business but the software supplier as well; the legislation places responsibility on both sides. Details on our payment integrations page.

Official sources

  • Law No. 3100 on the Obligation of Value Added Tax Payers to Use Payment Recording Devices, consolidated text: mevzuat.gov.tr
  • Tax Procedure Law No. 213 (Article 353, repeated Article 355), consolidated text: mevzuat.gov.tr
  • Tax Procedure Law General Communiqué No. 483 (Official Gazette 30.09.2017, No. 30196; last amended by Official Gazette 25.09.2024, No. 32673), published in the Communiqués section of mevzuat.gov.tr
  • Tax Procedure Law General Communiqué No. 588, 2026 thresholds and amounts (Official Gazette 31.12.2025, 5th bis edition, No. 33124): resmigazete.gov.tr
  • Law No. 7524 (Official Gazette 02.08.2024, No. 32620), the omnibus law that tightened POS and integration penalties

This content is for general information; consult your tax advisor or certified accountant for your specific situation.