E-Invoice Integration in Turkey: A Practical Guide

E-invoice integration in Turkey means issuing invoices straight from your own software — e-commerce store, ERP, CRM — and delivering them to the Revenue Administration (GİB). There are three routes: the free GİB portal, a licensed private integrator's API, and direct integration. Of Turkey's 1,937,308 registered e-invoice taxpayers, 95.4% use a private integrator; only 1,988 connect directly to GİB.

That single ratio settles most of the architecture debate before it starts. Direct integration sounds like the clean engineering choice, and it is the one we almost never recommend. The useful question is different: where does your software stop and the integrator begin?

The system is bigger than most newcomers expect. According to the Revenue Administration's 2025 Annual Report, 1.19 billion e-invoices and 11.52 billion e-archive invoices were issued in 2025 alone. Registered e-invoice taxpayers grew from 532,910 in 2021 to 1,937,308 by the end of 2025 — a 3.6x increase in four years.

This guide covers who is in scope in 2026, how the three methods actually differ, the technical flow your software has to implement, what to ask an integrator before signing, and realistic budgets and timelines.

Table of Contents

• What E-Invoice Integration Actually Means
• Who Must Comply in 2026: Thresholds and Dates
• Paper Invoices Ended in 2026
• Three Methods: Portal, Private Integrator, Direct Integration
• Which Method Fits You? Decision Table
• The Technical Flow, Step by Step
• Ten Questions to Ask a Private Integrator
• Integration Cost and Timeline
• Seven Mistakes We Keep Fixing
• Frequently Asked Questions

What E-Invoice Integration Actually Means

Two separate things get bundled under one phrase, and mixing them up wastes weeks.

The first is joining the application: obtaining a financial seal certificate, applying to GİB, and becoming a registered e-Fatura and e-Arşiv taxpayer. That is an administrative process you run with your accountant.

The second is software integration: making the system where the sale actually happens — your store, ERP, CRM, field sales app or dealer portal — generate and transmit the invoice automatically. That is the engineering problem, and it is where the return on investment sits.

Turkey uses two invoice documents, and your software must choose between them per transaction:

• e-Fatura — issued between taxpayers who are both registered in the e-Fatura application. It travels through GİB's infrastructure, and the recipient receives it inside the system.
• e-Arşiv Fatura — issued to buyers who are not registered e-Fatura users, including consumers. It is delivered by email or as a printout, and reported to GİB.

Registration is not optional once you are in scope for e-Fatura: joining the e-Fatura application also obliges you to join e-Arşiv. So a single "issue invoice" button in your UI always hides two document types behind it — a routing rule most teams building an e-commerce platform in Turkey discover late.

The chain has a third link. Under the Electronic Ledger Communiqué (Serial No. 1), taxpayers who become e-Fatura users during a year must move to e-Defter (electronic ledgers) from the beginning of the following year. A company that enters e-Fatura on 1 July 2026 is therefore an e-Defter taxpayer from 1 January 2027 — worth putting in the accounting roadmap early.

Who Must Comply in 2026: Thresholds and Dates

Scope is set by General Communiqué No. 509 of the Tax Procedure Law. The general rule: if you exceed the threshold in a given accounting period, you must join e-Fatura from the start of the seventh month of the following year. So 2025 figures point to 1 July 2026.

Two details catch foreign-owned entities off guard. First, the threshold is calculated on total gross sales revenue in the books, not just core-business revenue — selling a company vehicle counts. Second, the TRY 500,000 e-commerce threshold is low enough that almost any online seller with a Turkish entity crosses it in the first full year of trading.

Foreign ownership by itself changes nothing. What matters is whether you have a Turkish taxpayer entity issuing invoices under Turkish rules — if you do, the same thresholds apply as to any local company.

Paper Invoices Ended in 2026

This is the most frequently misreported point in English-language summaries, which still quote a TRY 30,000 consumer threshold. That threshold no longer exists.

Under the current text of Communiqué No. 509, invoices issued by taxpayers who are not part of the e-Arşiv application must be issued electronically:

• between 1/1/2025 and 31/12/2025, if the tax-inclusive total exceeded TRY 3,000;
• from 1/1/2026, regardless of amount.

They must be issued as e-Arşiv Fatura, either through GİB's own e-document portal or through a licensed private integrator. For taxpayers on the simplified basis or the business-account basis, the TRY 3,000 threshold runs until 31/12/2026, and the amount-free obligation begins on 1/1/2027.

In practice: if your company keeps books on the balance-sheet basis, every invoice you issue in 2026 must be electronic — even if you never crossed the e-Fatura threshold.

Penalties are not symbolic. Article 353 of the Tax Procedure Law explicitly covers "issuing on paper a document that must be issued electronically." Under General Communiqué No. 588, which sets the 2026 amounts, the fine starts at TRY 17,000 for the first detection and rises through TRY 35,000, 53,000, 70,000 and 87,000 to TRY 170,000 for repeat detections, with an annual ceiling of TRY 17,000,000 per document type. The fine applies per document, which is what turns "we'll just handwrite a few" into a six-figure problem.

Three Methods: Portal, Private Integrator, Direct Integration

The communiqué defines exactly three ways to use e-document applications, and every e-invoice integration in Turkey starts by choosing one of them.

GİB portal. Free, browser-based, manual. The communiqué states plainly that it exists for users without sufficient infrastructure to integrate. It offers a bulk XML upload feature, but GİB's own e-Fatura Portal user guide caps that channel at 500 invoices per month, a limit in force since 1 April 2014. The portal does not talk to your software.

Private integrator. You send invoice data to a GİB-licensed provider's API; signing, transmission, reporting and archiving happen on their side. The communiqué lets you request that the integrator's own financial seal and time stamp be used on your documents, which means you can go live without buying seal hardware. GİB currently lists 92 licensed e-invoice private integrators.

Direct integration. You connect your own systems to GİB. It is a heavier commitment than the name suggests:

• GİB sets conditions on business activity, turnover, document volume and IT infrastructure, and your application must be approved.
• Integration work must be completed within one year of application.
• If you stop meeting the conditions, your account is closed at the start of the third month following that determination — and a new application will not be considered for one year after closure.
• Non-compliance with the technical guides triggers the penalty provisions of the Tax Procedure Law.

GİB's own numbers confirm how rare this path is: 1,988 taxpayers out of 1,937,308 use direct integration for e-Fatura, and just 133 for e-Arşiv. Turkey's largest enterprise IT teams overwhelmingly go through integrators.

Two constraints matter especially for international groups. Using an integrator does not transfer your retention and presentation obligations — the communiqué says so explicitly, so you still need your own copy of every document. And the software and hardware infrastructure used to send and receive e-documents must be located within the borders of the Republic of Turkey, which rules out simply routing everything through an EU or US data centre.

Which Method Fits You? Decision Table

Our standing recommendation to clients is a boundary, not a product: let the integrator own the tax protocol; keep the business logic in your software. Discount rules, currency handling, withholding scenarios, refund matching and order reconciliation belong to your system. XML schema validation and GİB's quarterly code-list updates do not.

The Technical Flow, Step by Step

Here is what an integrator-based e-invoice integration actually involves. Use it as the checklist for your scoping session.

1. Check the buyer's registration status. If the buyer's tax number (VKN) or national ID (TCKN) appears in GİB's registered-user list, the document is an e-Fatura; otherwise it is an e-Arşiv Fatura. Query before every invoice, and if you cache the list, refresh it daily — on mass transition dates like 1 July, thousands of taxpayers join overnight and a stale cache means invalid documents.

2. Pick the scenario and document type. The choice between the basic and commercial e-Fatura scenarios has operational consequences: under the commercial scenario the buyer can accept or reject the invoice inside the system within 8 days of receipt, while the basic scenario has no in-system rejection. On the document side, your software needs sale, return, withholding, exemption, special-base and export-registered variants.

3. Build the document in UBL-TR. Both e-Fatura and e-Arşiv are UBL-TR XML, digitally signed. The packages and code lists change regularly, each with an effective date. GİB's announcement of 27 July 2026 updated the e-Fatura package, the e-Arşiv package and the UBL-TR code list guide, with changes taking effect on 14 September 2026. Under an integrator, that calendar is their problem; under direct integration, it is yours.

4. Handle the VAT rate check. Since 1 April 2026, per GİB's announcement of 16 March 2026, documents issued through private integrator systems are checked against the taxpayer's registry and activity code records. For cases where the VAT rate cannot match the activity code — cost reflection invoices, fixed asset sales — a new code "555 – Sales Not Subject to VAT Rate Control" was introduced. If your software has no field for it, those invoices will be rejected.

5. Sign the document. Legal entities use a financial seal (mali mühür); individual taxpayers use a qualified electronic certificate. Per TÜBİTAK BİLGEM Kamu SM's published tariff, a three-year financial seal certificate with a card reader costs TRY 2,040 (TRY 1,700 + VAT), and a three-year certificate loaded onto an HSM costs TRY 6,300 (TRY 5,250 + VAT). At high volume, an HSM replaces the smart card because it signs far more documents per unit of time.

6. Guarantee numbering and uniqueness. Invoice numbers are 16 characters and must be sequential within the year. Every document carries a UUID, and resubmitting the same UUID and number returns an error. Generate numbers under a database lock and make your transmission layer idempotent: on a network timeout, query status rather than resend.

7. Track status properly. Submission is not confirmation. You need a queue, a retry policy, and a document-status table fed by the integrator's status service or webhooks. If your order screen says "invoiced," that flag should reflect what GİB actually returned.

8. Design cancellation and returns on day one. The commercial scenario's 8-day response window, and the different objection routes under the basic scenario, both need code paths. On returns, if the buyer is a registered e-Fatura taxpayer they usually issue the return invoice; if not, you issue a return e-archive invoice or an expense voucher. This is the single most commonly skipped requirement in e-commerce projects.

9. Keep your own archive. Because the retention obligation stays with you, store the transmitted XML and its rendered version in your own system. It also makes switching integrators a routine task instead of a migration project.

10. Finish in the test environment. Every integrator provides a sandbox. Withholding, exemption, full and partial returns, foreign-currency invoices and line-level discounts should all pass there before you go live.

In our custom software projects, this flow is scoped as its own module and usually ships alongside the order, account and inventory modules.

Ten Questions to Ask a Private Integrator

Integrator marketing pages read alike, so an e-invoice integration quote tells you very little on its own. The differences show up in the answers to these:

1. What kind of API is it? REST/JSON or SOAP/XML? Is the current documentation public, or only shared after signature?
2. How do I get a sandbox? Is test access available before contracting, and how quickly?
3. What are the rate limits? How many documents per minute on a peak sales day, and how does the queue behave?
4. Are there status callbacks? Webhooks on status change, or must you poll?
5. Which scenarios are supported? Withholding, exemption, special base, export-registered, foreign currency and returns — all through the API?
6. Who does e-Arşiv reporting? Does the integrator generate and submit the reports, or do you?
7. How do I access the archive? Can you bulk-download historical documents as XML and PDF, and for how many years are they kept?
8. What is the pricing model? Credits or subscription? Do unused credits roll over? Does a cancelled invoice consume a credit?
9. Is there an SLA and a status page? Is the incident history public?
10. What does exit look like? How is the archive handed over at contract end, and at what cost?

Questions eight and ten are the ones clients skip. Switching integrators is technically cheap; not having agreed the archive handover is expensive.

Integration Cost and Timeline

An e-invoice integration has three cost lines: certificate, integrator fee, and development.

Certificate. TRY 2,040 for three years, or nothing up front if you use the integrator's seal.

Integrator fee. Two models compete: per-invoice credits and flat subscriptions. Based on 2026 market pricing guides, credit unit prices generally sit in the TRY 0.75–1.50 range, while SME packages run roughly TRY 150–1,000 per month. Above about 2,000 invoices a month, flat-rate plans usually win.

Development. This is the line that actually varies, and it scales with scope:

These are 2026 ranges for a Turkish development team; the state of your existing data and the maturity of the integrator's API decide where you land. Budget 15–20% of the project value per year for maintenance, which covers the small changes each GİB guide update brings.

For a broader view of how to size and stage a build like this, see our software project budget planning guide and the website cost calculator. If you are weighing an off-the-shelf package that already ships invoicing, our ERP comparison for smaller companies covers the licensing side of the same decision.

Seven Mistakes We Keep Fixing

These recur in almost every e-invoice integration project we inherit:

1. Hard-coding registration status. Writing "this customer is an e-Fatura taxpayer" onto the account record once and never re-checking produces batches of invalid documents on transition dates.

2. Generating invoice numbers in application code. Two concurrent orders produce the same number, the document is rejected, and the sequence breaks. Use a database-level lock.

3. Skipping the sandbox. A withholding invoice tested in production cannot always be cancelled, because of the 8-day rule.

4. No path for cost reflection and asset sale invoices. Since the 1 April 2026 VAT rate check, these fail without the "555" code.

5. Ignoring rounding. When line-level VAT and total-level VAT disagree by a cent, schema validation fails. Define the rounding rule in one place.

6. Deferring returns. In e-commerce, returns are routine, not exceptional. They belong in the initial scope.

7. Outsourcing the archive entirely. Retention and presentation obligations remain with the taxpayer. Without your own copy, both audits and integrator changes get painful.

Frequently Asked Questions

Is e-invoice integration mandatory in Turkey?

Joining the e-Fatura application is mandatory for taxpayers who exceed the thresholds in Communiqué No. 509. Software integration itself is not mandatory — you can issue invoices manually through the GİB portal. Integration becomes an economic necessity rather than a legal one as invoice volume grows.

Why pay an integrator when the GİB portal is free?

Because the portal offers no automation and does not connect to your software, and its bulk XML upload is capped at 500 documents per month by GİB's own user guide. Of Turkey's 1,937,308 e-invoice taxpayers, 1,848,492 use a private integrator, while only 86,828 issue through the portal.

Can I connect my own system directly to GİB?

Technically yes, but it is rarely the right call. You must meet GİB's conditions, have your application approved, and complete integration within one year. If conditions lapse, the account is closed and no new application is accepted for a year. GİB reports just 1,988 taxpayers using this method.

What is the difference between e-Fatura and e-Arşiv Fatura?

e-Fatura is exchanged between taxpayers who are both registered in the e-Fatura application, travelling through GİB's infrastructure. e-Arşiv Fatura is issued to unregistered taxpayers and to consumers, delivered electronically or as a printout, and reported to GİB. Your software should choose between the two automatically based on the buyer's status.

Can a company still issue paper invoices in 2026?

Not if it keeps books on the balance-sheet basis. From 1 January 2026, invoices issued by taxpayers outside the e-Arşiv application must be electronic regardless of amount. Taxpayers on the simplified or business-account basis keep the TRY 3,000 threshold until 31 December 2026, with full obligation starting 1 January 2027.

What is the penalty for issuing a paper invoice instead?

Article 353 of the Tax Procedure Law treats issuing on paper a document that should be electronic as a special irregularity. Under the 2026 amounts set by Communiqué No. 588, the fine starts at TRY 17,000 on first detection and rises to TRY 170,000 for repeat detections, applied per document.

Do foreign companies have to use e-Fatura in Turkey?

Foreign ownership by itself is not the test. If you operate through a Turkish taxpayer entity issuing invoices under Turkish rules, the same thresholds and obligations apply. Note also that the systems used to send and receive e-documents must be hosted within Turkey, so a purely offshore invoicing stack is not compliant.

How long does an e-invoice integration take?

A one-way basic e-invoice integration takes 2–3 weeks; a mid-range implementation including returns and cancellation takes 3–6 weeks; a comprehensive project with two-way ERP sync and e-waybill runs 6–10 weeks. The biggest schedule risk is the quality of existing customer and product data.

How do I correct an incorrectly issued e-invoice?

Under the commercial scenario, the buyer can reject the invoice inside the system within 8 days of receipt, which voids it. Under the basic scenario there is no in-system rejection, so correction usually happens through a return invoice or the objection routes provided by law. Which scenario your software selects therefore directly affects how expensive corrections are later.

Done properly, e-invoice integration is infrastructure you stop thinking about. Done badly, it produces a few hours of manual correction every month, painful period-end reconciliation, and a standing penalty risk. The difference is rarely the technology — it is drawing the boundary correctly at the start: tax protocol with the integrator, business logic and data ownership in your own software.

If you are planning to connect a store, an ERP or a custom business system to Turkey's e-invoice chain, we can scope it against your current stack and invoice volume and give you a firm timeline. Get in touch and we will review your setup together.