Turkey's e-Invoice and e-Archive Mandate: the IT Readiness Guide
TL;DR: The fiscal side of Turkey's e-invoice/e-archive transition belongs to your accountant; the technical side belongs to IT: choosing the integration method (portal / special integrator / direct), verifying accounting-software compatibility, managing the fiscal seal certificate, building a ten-year archive arrangement, and planning for the day an invoice cannot be issued.
Turkey's move to electronic documents has advanced in stages for years: revenue thresholds and sector coverage are widened regularly by Revenue Administration communiqués, and each year a new wave of companies falls under the mandate. Which threshold catches you on which date is a question for your accountant — this article covers the other half we see repeatedly in the field: once scope is confirmed, the technical transition gets crammed into the last week. E-document adoption is not "an accounting matter"; it is a rewiring of your invoicing process, and rushed wiring introduces you to a morning when the first invoice cannot be issued.
Three Integration Routes
| Method | How it works | Who it fits |
|---|---|---|
| Government portal (GİB) | Documents issued manually through the administration's web interface | Very low document volume; as a stopgap |
| Special integrator | Your accounting/ERP software sends and receives documents through the integrator | The vast majority of SMBs — practical and fast |
| Direct integration | Your own system connects directly to the administration | High volume with a strong in-house IT team |
SMB practice settles on the special integrator — and the choice seems to end with picking one, but it does not. The critical question is whether your current accounting software has a certified connection to that specific integrator. A contract signed before that pairing is verified comes back in transition week as "your version doesn't have this connector".
The IT Readiness List
- Accounting software version: e-document modules ship from specific versions onward; if an upgrade is needed, it has its own test calendar and must be finished weeks before the transition date.
- Fiscal seal / e-signature: for legal entities, the fiscal seal certificate's application, delivery and installation take time and cannot wait for the last day. Where the certificate lives, how it is backed up and how its PIN is protected must be written down — a seal installed on one forgotten PC stops all invoicing when that PC fails.
- Document templates: the logo, bank details and order/dispatch references on your invoices move into the integrator's template and are approved against samples.
- Scenario tests: test documents are issued to e-invoice taxpayers, to non-taxpayers (e-archive), and for return and cancellation flows; correct posting into the books is verified.
- Authorisation and training: who may issue, who may cancel — an authority matrix is set, and users practise in the test environment before go-live.
The Archive: Infrastructure for a Ten-Year Duty
Electronic documents must remain producible throughout the legal retention window — under tax law, a period extending as a rule to ten years. Integrators offer archive services; the healthy arrangement is still to download documents periodically into an archive under your own control. On the day of an integrator switch, a contract end or an access problem, the only party answering "where are our documents?" is you. That archive joins your own backup regime and is subject to the 3-2-1 rule, with restore tests as part of the routine.
The Day an Invoice Cannot Be Issued: the Continuity Plan
Under the e-document regime, invoicing depends simultaneously on your internet, your accounting server and the integrator connection. When any of the three drops, shipments wait. E-document adoption must therefore be designed together with a continuity plan:
- A backup internet line with automatic failover — the cost of one stopped invoicing hour usually pays the backup line's annual fee by itself.
- A current backup and fast-recovery target for the accounting server; the invoicing machine is not "just another PC", it is critical infrastructure.
- A plan B for integrator outages: manual document issuance rights and know-how on the government portal, held by at least two people.
Where Yamanlar Bilişim Stands in the Project
The fiscal calendar and taxpayer-status questions sit with your accountant; we take the engineering: software–integrator compatibility verification, version upgrades, fiscal seal installation and backup, scenario testing, the archive-and-backup arrangement, and closing the outage scenario. On transition night we are at the console; the next morning the first real document is issued under control.
FAQ
Frequently Asked Questions
How do we find out whether the mandate covers us?
Revenue thresholds and sector coverage are updated by communiqué; confirm the current threshold and your binding date with your accountant. Our advice concerns the process: start the technical preparation the day your inclusion becomes clear — do not wait for the communiqué date.
What should we check technically when choosing an integrator?
In order: certified integration with your accounting software, ease of archive access and export, outage history, and the working hours of support channels. Price differences are usually small; the expensive integrator is the one that cannot talk to your software.
Are the fiscal seal and e-signature the same thing?
No: the fiscal seal belongs to the legal entity, the e-signature to a natural person. Companies use the fiscal seal in e-document flows; which one applies to which document depends on the scenario, and the application processes are separate. Both belong in the IT inventory — installation, backup and access details included.
Once we are on e-documents, can we discard the paper archive?
Pre-transition paper documents follow their own retention periods; the electronic era does not cover them retroactively. In the new regime documents are stored electronically — which means an archive copy under your control and a backup arrangement, not "the integrator keeps them anyway".
Can we really not invoice when the internet is down?
Electronic documents are designed to be transmitted at issuance; offline scenarios are limited and temporary. The practical answer is technical: in a business with a backup line and an integrator plan B, the question stays theoretical; without them, it becomes an afternoon of waiting shipments.
Author
Serdar YAMAN
Yamanlar Bilişim Expert
Writes content on IT infrastructure, cybersecurity, and digital transformation at Yamanlar Bilişim. Get in touch for any questions.
Professional Support
Get help on this topic
Let's design the IT Management solution you need together. Our experts get back to you within 1 business day.
support@yamanlarbilisim.com · Response time: 1 business day
Keep Reading
Related Articles
The Office-Move IT Checklist: Everything Working by Monday Morning
In an office move, furniture fits in the truck; what stops the business is the internet not yet connected, the phones silent, the server not powered up. A scheduled, field-tested IT checklist running from eight weeks out to the post-move tail.
The New-Employee IT Onboarding Package: a System That Works at 09:00 on Day One
A new employee's first day is the first photograph of how the organisation runs: a ready device and open accounts at their desk, or three days of "we told IT, we're waiting"? The onboarding package built on role-based access templates and one trigger from HR.
The Year-End IT Budget: What to Write for 2027, and What to Base It On
In most SMBs the IT budget is last year's number plus a percentage — until an unplanned server death splits it down the middle. A six-line framework, its data sources, and presenting it to management in the language of "risk equals cost".