Türkiye e-invoicing on SAP, GİB, and a localization brief
e-Invoicing is not phase 2 of go-live. GİB calendars, parked invoices and internal approval are different clocks. Localization is not a language pack.
Atilla Kuruüzüm · May 8, 2026 · 9 min read
In Türkiye, every SAP conversation eventually hits GİB — the revenue administration. e-Invoice, e-archive, e-despatch, e-ledger: each has its own communiqué, outage and reject window. A global template parks them as a ‘local add-on’ in phase 2. Phase 2 is the first legal month in Excel. The Turkish half of this article is practice; this English half puts the same fact inside the word localization.
Legal acceptance is not the accounting post
A document may be accepted at GİB and still parked in SAP. VAT reports then see two worlds. Internal approval (amount, account, three-way match) is longer than the statutory reject window. Treating them as one SLA either panic-rejects the document or burns the window. The process keeps two clocks.
Whose job is the integration?
A special integrator, SAP e-document options, banks, e-signature edges. They do not fit in one box labelled ‘SAP standard’. Discovery writes which edge, which company code, which document type. If it does not, go-live morning speaks XML and finance is silent.
The close calendar
e-Ledger seals and the period cut belong on the AMS calendar. If they do not, every period is a ‘we made it this time’ hero story. Heroes are not a process. If inflation and IFRS land in the same window, the e-document queue is a third job; priority sits in the contract.
Localization is not a language pack
The template can stay English. A Turkish company code still needs statutory invoicing, ledger filing, tax codes a local inspector recognises, and a calendar that is not the US close. Those rails are localization. GUI language is a smaller, separate call. If the rollout plan says ‘we will add Turkey later’, you are planning an Excel month. GİB does not wait for phase 2. German XRechnung is another rail — do not paste one ‘e-invoice’ story on both countries.
We treat e-documents as a neighbour of AMS and invoice approval. Neighbour, not the same house: statutory clock apart from internal-control clock. Do not mix them.
Frequently asked questions
Does standard SAP cover Türkiye e-transformation on its own?
It does not. e-Invoice, e-Archive, e-Delivery note and e-Ledger require integrator connectivity, local formats and regulatory tracking. Standard SAP provides the foundation; the compliance layer is built separately and updated as regulation changes.
How do a global template and local regulation coexist?
Local requirements are added as a country layer without breaking the template. The critical rule: the central process and chart of accounts stay shared, while statutory output and reporting are solved in the country layer.
What happens when regulation changes?
The deadline is usually short. That is why it must be defined upfront who updates the compliance layer and under which SLA; otherwise every change turns into an emergency project.