In Turkey, an e-Fatura is an electronic invoice sent through the tax authority’s central platform between two businesses that are both registered for e-invoicing, and an e-Arşiv Fatura is the electronic invoice you issue to everyone else: unregistered businesses, consumers and customers abroad. Both have the same legal standing as a paper invoice, and in 2026 almost every invoice a Turkish SaaS company issues goes through one of the two.
This guide is for founders and developers who sell software from a Turkish company. It explains, based on texts published by the Revenue Administration (Gelir İdaresi Başkanlığı, GİB), which channel to use when, who has to join, how invoices reach the customer, what private integrators do, and what to watch when you sell abroad. Most official sources are in Turkish; we link them anyway so you or your accountant can check the wording.
This is not tax advice. The rules change often, and what applies to you depends on your company type, revenue and activity. Confirm everything here with a Turkish accountant (mali müşavir) and check the current text on GİB’s e-Belge site before you act on it.
What e-Fatura is
According to GİB’s e-Fatura overview, e-Fatura is not a new kind of document. It is an electronic document in a format set by GİB, with the same legal qualities as a paper invoice, and it travels from seller to buyer through GİB’s central platform.
The key rule: e-Fatura works only when both sides are registered in the e-Fatura system. If your customer is a registered company, you must send them an e-Fatura. If they are not, you cannot.
What e-Arşiv Fatura is
The current consolidated text of VUK General Communiqué No. 509 (section IV.2.1) describes e-Arşiv as invoices to taxpayers who are not registered for e-Fatura and to non-taxpayers, created electronically, delivered on paper or electronically at the buyer’s request, with the seller’s copy kept electronically.
For a SaaS company, these customers get an e-Arşiv invoice:
- Individual subscribers (consumers),
- Sole traders and small businesses not registered for e-Fatura,
- Customers abroad, because they are not registered in the Turkish e-Fatura system.
e-Fatura vs e-Arşiv at a glance
| Topic | e-Fatura | e-Arşiv Fatura |
|---|---|---|
| Issued to | Businesses registered for e-Fatura | Unregistered businesses, consumers, customers abroad |
| Delivery | Through GİB’s platform into the buyer’s system | Email/electronic or paper at the buyer’s request; electronic for internet sales |
| How GİB learns about it | The document passes through GİB | The seller or its integrator sends GİB an e-Arşiv report |
| Format | UBL-TR (XML) | UBL-TR (XML) |
| Legal standing | Same as a paper invoice | Same as a paper invoice |
The reporting rule is in section V.8 of the communiqué: for documents that GİB does not transmit itself, such as e-Arşiv, the seller or the private integrator must sign a report with an electronic certificate, time-stamp it and transfer it to GİB’s system.
Who has to join
Thresholds change from time to time. Read the figures below as the text in force when this article was published, and check the current GİB rules before relying on them.
The e-Fatura obligation
Section IV.1.4 of Communiqué No. 509 requires, among other groups:
- The general threshold: taxpayers with gross sales of 3 million TL or more in 2022 or any later accounting period.
- Online sellers: taxpayers who sell goods or services on their own websites, on intermediaries’ sites or in other electronic channels, with gross sales of 500 thousand TL or more in 2022 or later.
A SaaS company that sells subscriptions on its own website falls, on a plain reading, into the second group, so the 500 thousand TL threshold may be the one that applies to you rather than 3 million. Confirm with your accountant which group you are in.
Timing is in section IV.1.5: you must switch by the start of the seventh month of the year after the period in which you crossed the threshold. If your 2025 sales crossed it, you should have been on e-Fatura from 1 July 2026.
Taxpayers who join e-Fatura must also join e-Arşiv (section IV.2.4.1). In practice the two come together: e-Fatura for registered buyers, e-Arşiv for everyone else.
e-Arşiv for everyone else
Even below the thresholds, paper invoices are on their way out. Under section IV.2.4.3, taxpayers who are not in the e-Arşiv system:
- had to issue invoices above 3,000 TL including taxes as e-Arşiv between 1 January and 31 December 2025,
- must issue their invoices as e-Arşiv regardless of amount from 1 January 2026.
For taxpayers taxed under the simple method or keeping single-entry (işletme hesabı) books, Communiqué No. 589 (Official Gazette of 31 December 2025, issue 33124, 5th duplicate; listed on GİB’s legislation page) moved these dates by a year: the 3,000 TL threshold runs until 31 December 2026, and the any-amount rule starts on 1 January 2027.
These invoices can be issued through GİB’s e-Belge portal or through the systems of private integrators licensed by GİB. Issuing a paper invoice instead triggers the penalty in article 353 of the Tax Procedure Law, for each paper invoice, for both the issuer and a buyer who is a taxpayer other than a final consumer.
UBL-TR: the format
GİB adopted UBL-TR, an XML-based format built on the international UBL standard, for e-invoices. Both e-Fatura and e-Arşiv documents use it; what differs is the scenario (profile) the document is sent under and where it goes.
What a developer needs to know:
- The XML is the invoice. The PDF is a rendering of it.
- Every document has a universal ID (UUID) and a legal invoice number, and a number can never be reused.
- Cancellations, credit notes and tax exemption codes are expressed in specific XML fields, and filling them correctly is your job, or your billing system’s.
Three ways to issue
Section V.1 of the communiqué lists three methods:
- GİB portal: issue invoices by hand on GİB’s web portal. Fine for a few invoices a month; with a growing subscriber base, typing every invoice by hand does not scale.
- Private integrator (özel entegratör): issue through the systems of a company licensed by GİB. Most SaaS companies take this route because integrators offer an API.
- Direct integration: connect your own IT systems to GİB directly. The heaviest route technically, and rarely worth it for a small SaaS team.
Private integrators
GİB publishes the licensed companies: the e-Fatura integrator list and the e-Arşiv integrator list, each with dozens of names. When you pick one, ask:
- Is there a REST API with a separate test environment?
- Can you look up whether a buyer is registered for e-Fatura?
- Does it email e-Arşiv invoices to the customer and handle the GİB reporting?
- Is pricing per document or per bundle?
Nilvera, for example, appears on both GİB lists. Its developer documentation describes a REST API with separate live (api.nilvera.com) and test (apitest.nilvera.com) environments; test keys are separate from live keys, and you authenticate with an API key generated in its portal.
How an invoice reaches the customer
The path depends on who the customer is:
- A registered business (e-Fatura): the document goes from you to your integrator, through GİB, to the buyer’s integrator and accounting system. The buyer sees it in their e-Fatura inbox.
- A consumer or unregistered business (e-Arşiv): the document is created, reported to GİB and usually emailed to the customer as a PDF or link.
- Internet sales: under section IV.2.4.5, e-Arşiv users who sell goods and services online must deliver these invoices electronically. The invoice must show the website where the sale took place, the payment method, the payment date and the date the service was performed, and carry the sentence “Bu satış internet üzerinden yapılmıştır.” (“This sale was made over the internet.”)
The practical upshot for SaaS: at signup, collect the customer’s tax ID (or national ID for individuals) and email, then ask your integrator whether the tax ID is registered.
Selling abroad: export of services
If you sell SaaS from Turkey to customers abroad, there are two questions: which document to issue, and whether to charge VAT (KDV).
The document: a customer abroad is not registered in the Turkish e-Fatura system, so under the split in section IV.2.1 of the communiqué, their invoice is an e-Arşiv invoice.
VAT: article 11/1-a of the Turkish VAT Law No. 3065 exempts services performed for customers abroad. Article 12/2 requires both of these:
- The service is performed for a customer abroad,
- The service is used (benefited from) abroad.
The law defines a customer abroad as a buyer whose residence, workplace, legal seat and business centre are outside Turkey. When exactly a SaaS subscription meets these conditions, what records to keep, which exemption code goes on the invoice and how to report it depends on secondary rules and practice. Make these calls with your accountant.
If you collect payments through a merchant of record such as Paddle, the provider is the seller to the end customer. Ask your accountant what that means for your own invoicing and VAT.
How Payrudder handles this
Payrudder is a usage metering, subscription billing and payment orchestration platform written in Go. On the e-invoicing side it:
- Picks the channel. For a seller in Turkey it issues an e-Fatura when the buyer is registered and an e-Arşiv invoice otherwise. If the buyer’s status is unknown and a tax ID is present, it asks the integrator first when the integrator supports that lookup (Nilvera does).
- Builds the UBL-TR itself. It renders UBL-TR 1.2 XML for invoices and credit notes and stores the XML and the PDF.
- Never issues the same invoice twice. Each document’s UUID is its idempotency key, so a retry does not send it again, and a legal number is never reused.
- Offers two integration paths. A ready Nilvera adapter, or a custom integrator: Payrudder sends each document in an HMAC-SHA256-signed request to an endpoint you run, and you pass it on to any integrator you like. The sandbox uses a built-in simulator.
To be plain about the status: the e-invoice integration is built and covered by tests, but it has not yet been run against Nilvera’s test portal or the official UBL-TR schematron. Payrudder is not a tax engine either: you set tax rates per customer country, and the exemption code used on a zero-VAT line is a default that has not been confirmed yet. Ask your accountant which code your export invoices need, and issue your first invoices in your integrator’s test environment before you go live.
On the payment side, local cards can go through iyzico and sales abroad through Paddle; the selling SaaS from Turkey page explains that setup. (The iyzico and Paddle adapters are also written from the providers’ documentation and tested against fixtures; they have not yet been run against the providers’ sandboxes.)
A short checklist
- Do your gross sales and sales channel cross an e-Fatura threshold? (Check the current GİB rules.)
- If you are not on e-Fatura, are you issuing e-Arşiv invoices in 2026?
- Have you picked a private integrator and issued a test invoice in its test environment?
- Does your signup form collect a tax ID or national ID and an email?
- Do your invoices carry the details required for internet sales?
- Have you confirmed the VAT exemption and exemption code for foreign sales with your accountant?
E-invoicing is tedious to set up and quiet once it runs. Payrudder Cloud is in early access, and the plans and limits are on the pricing page.