What Is a Fiscal POS (ÖKC)? Relation to the Cash Register

What is ÖKC?

ÖKC (fiscal payment recorder) is the hardware and software set that records collections in retail and services in line with tax rules. Under Revenue Administration (GİB) oversight, the device stores sale totals, payment types, VAT breakdown and day-end summaries and sends them electronically when required.

In everyday speech ÖKC often means the same device as a cash register or POS terminal; legally it is the device that fulfills the payment recording duty. In restaurants, cafes and delivery businesses, order software runs the ticket; ÖKC turns collection into a fiscal document. When the two run separately you risk double entry, day-end drift and audit exposure.

For official information and device lists use the GİB new-generation ÖKC portal at ynokc.gib.gov.tr. The portal is the current source for taxpayer duties, device types and announcements.

Cash register and ÖKC

Legacy cash registers focused on printing slips; new-generation ÖKC devices add card payment, multiple VAT departments, e-document integration and software links (GMP3/TSM). For a restaurant owner the practical result is this: the Android or EFT-POS terminal at the counter is usually also an ÖKC.

"Cash register" suggests paper slips and Z report flow; "ÖKC" stresses fiscal records reportable to GİB. With integration, Ritapos order lines match device departments and totals; when payment completes the ticket closes. We explain that chain step by step in what cash register integration is.

Brand and model choice (Inpos, Ingenico, PAX, Pavo, Paycell and others) depends on volume, counter vs table collection and bank agreements. On integration Ritapos supports GMP3 (wired) and TSM (wireless) with common brands; see the comparison on cash register integrations.

New-generation ÖKC features

New-generation ÖKC adds touchscreen, Wi-Fi or mobile data, multiple payment methods (cash, card, meal cards), secure payment modules within the scope of GMÖ/VUK Communiqué 507, plus cloud updates. Pay-at-table in restaurants is supported with TSM; busy takeaway counters often prefer wired GMP3.

Device software license, bank POS agreement and integration license are separate cost lines. The device vendor's own annual package or commission sits outside Ritapos integration pricing.

On new devices you pull X and Z reports, department sales summaries and error logs from the digital menu. At day end, comparing the Ritapos sales report with the device Z report is the fastest check that integration is healthy.

EFT-POS taxpayer vs simplified regime

Taxpayer type defines which documents and devices apply. Simplified regime taxpayers follow lighter books and documents within limits; exceeding limits or sector rules can bring new-generation ÖKC into scope.

For EFT-POS / full regime retail, card collection and ÖKC use become mandatory more often. As restaurant and cafe turnover grows, plan e-adisyon, e-archive invoice and integrated ÖKC together.

Confirm your taxpayer type with your accountant and GİB announcements; then aim to bring bank POS and Ritapos integration type (GMP3/TSM) live the same day as the device supplier. That reduces double slips or off-books collection during transition.

The three terms in the table are not interchangeable: Ritapos runs orders, ÖKC records collection, virtual POS collects cards without a physical terminal. Prepaid marketplace orders use virtual POS; cash or card at the table uses physical ÖKC.

For physical POS steps see how to use a POS device. For an Inpos setup example see Inpos integrated POS.

Integration in restaurants: GMP3 and TSM

GMP3 (wired integration) keeps the payment app inside the secure module defined by GİB. A fixed counter terminal links by cable or local network to the Ritapos desktop or counter PC; amount goes to the device in one action.

TSM (wireless / remote management) gives central control of security config on Android POS devices the server carries. For table payment, TSM keeps fiscal records while service stays fast.

With Ritapos integration, order lines map to device departments; discounts, comps and delivery fees go to the correct VAT band. When payment completes the order closes in Ritapos; day-end reports align.

1. Create the order in Ritapos. Add items from table, delivery or pickup.
2. Send payment to ÖKC. Push the total to the device via GMP3 or TSM with the integration button.
3. Complete card or cash on the device. The slip prints and the fiscal record is created.
4. Confirm the ticket closed. Ritapos order status should be paid.
5. Take the day-end Z report. Compare device Z with Ritapos day-end sales summary.

Manual cash/card close without integration can stay for emergencies; for audit and consistency, turning off manual payment in business settings is safer long term. If the payment provider column in reports does not show the device brand, that line was closed without integration.

In multi-branch groups, defining each branch device in the same Ritapos account with a central menu lets you map departments once. On a new branch opening, align menu and VAT rates first, then copy device mapping.

ÖKC selection checklist

• Read GİB duties for your taxpayer type and sector on the ynokc portal.
• Plan GMP3 or TSM based on counter vs table collection.
• Keep bank POS, device brand and Ritapos integration in one project timeline.
• Test department count and VAT rates against your menu.
• Run a low-value test sale before the first service day.

ÖKC investment is not hardware alone; budget training, integration testing and day-end discipline. Staff should habitually send totals from Ritapos without changing amounts on the device; otherwise stock and turnover reports drift from slip lines.

Marketplace prepayment and on-site collection are different channels; Ritapos order source and payment provider fields keep that split in reports. In central kitchen or dark kitchen models with one ÖKC serving multiple brands, brand-based department names keep reports readable.

Continue in the Academy

To see the topic step by step on screen, browse the related lessons in Ritapos Academy.

• Paycell integration
• Inpos cash register integration
• Ingenico device integration

After you clarify ÖKC and integration, review the brand table on cash register integrations.