Odoo Turkey E-Invoicing: e-Fatura, e-Arsiv, e-Irsaliye in Odoo 19/20
Set up Odoo Turkey e-invoicing: GIB e-Fatura thresholds, e-Arsiv and e-Irsaliye rules, Nilvera setup, integrator options and Odoo 19 vs 20 limits.
Turkey's e-document rules keep widening each year, with lower thresholds and fewer paper exceptions. Odoo covers the core flows, but every Turkish rollout still needs clean partner data, tested tax codes and an integrator account. Our Odoo integration services cover that connector work end to end.
Related service: Odoo for finance teams — accounting, tax and reporting automation.
This guide is for finance leads, IT managers and Odoo partners running or planning Odoo in Turkey. If you are comparing country packs in general, start with our review of what Odoo localization modules cover and what they miss.
What are e-Fatura, e-Arsiv and e-Irsaliye in Turkey?
e-Fatura, e-Arsiv and e-Irsaliye are the three main electronic documents that the Turkish Revenue Administration (GIB, Gelir Idaresi Baskanligi) uses to replace paper invoices and delivery notes. Each one covers a different buyer or business event.
| Document | Turkish name | Used for | Who receives it |
|---|---|---|---|
| e-Invoice | e-Fatura | B2B invoices between registered users | A buyer registered for e-Fatura |
| e-Archive invoice | e-Arsiv Fatura | Invoices to unregistered buyers, B2C and many export cases | Consumers, foreign buyers, unregistered firms |
| e-Dispatch note | e-Irsaliye | Delivery notes for goods in transit | The receiving party, linked to stock moves |
| e-Ledger | e-Defter | Electronic journal and ledger records | Filed with GIB, not sent to customers |
Odoo picks the document type from the customer. The Odoo Turkiye documentation says that if a partner is not registered for e-invoicing, Odoo automatically defaults to e-Archive.
Who must use e-Fatura in Turkey? GIB thresholds explained
You must switch to e-Fatura once your gross sales reach the GIB limit, which has been 3 million TL for most taxpayers since the 2022 accounting period. Lower limits apply to sectors GIB treats as higher risk. In Turkish, this obligation is called e-Fatura zorunlulugu.
The thresholds come from General Communique No. 509 on the Tax Procedure Law (VUK) and its amendments, mainly Communique No. 535 of January 2022. Tax advisers such as KPMG Turkey summarized the limits below.
| Group | Gross sales threshold | When to switch |
|---|---|---|
| General taxpayers | 3 million TL (2022 period onward) | 1 July of the following year |
| Online sales and marketplaces | 500,000 TL | 1 July of the following year |
| Real estate and motor vehicle trading, rental and brokerage | 500,000 TL | 1 July of the following year |
| Licensed hotels | No threshold, mandatory | From licensing |
| New businesses in a mandatory field | Depends on activity | Start of the fourth month after starting |
| e-Irsaliye for e-Fatura users | 10 million TL (2021 period onward) | Start of the seventh month of the following year |
For example, a general taxpayer whose 2025 gross sales hit 3 million TL must be on e-Fatura by 1 July 2026.
e-Fatura users must also use e-Arsiv, and e-Defter follows from the next year for balance-sheet taxpayers. Confirm your date with your mali musavir (financial adviser).
What changed for e-Arsiv in 2026?
Paper invoices are being phased out, and from 2026 most balance-sheet taxpayers are expected to issue every invoice as e-Arsiv or e-Fatura. Smaller bookkeeping groups got more time.
Communique No. 589, published in the Official Gazette on 31 December 2025, extended a transition for taxpayers on the simple method (basit usul) and those keeping income and expense books (isletme hesabi). In 2026 they need not issue e-Arsiv for invoices up to 3,000 TL including taxes.
Turkish e-document providers read this as moving full digitization for these smaller groups to 1 January 2027.
How does Odoo handle Turkish e-invoicing?
Odoo uses the l10n_tr localization for accounting and a set of Nilvera modules that send, receive and store e-documents through Nilvera's API. You do not connect Odoo to GIB directly.
The Odoo 20 Turkiye documentation lists these modules:
- Turkiye - Accounting (l10n_tr): chart of accounts based on GIB's 7/A accounts, taxes, tax report and fiscal positions. It installs automatically.
- Turkiye - Accounting Reports (l10n_tr_reports): Turkish tax and profit and loss reports.
- Turkiye - Nilvera (l10n_tr_nilvera): the base connector, API credentials and e-Ledger file generation. Install it manually.
- Turkiye - Nilvera E-Invoice (l10n_tr_nilvera_einvoice): sends and receives e-Fatura and e-Arsiv invoices. Install it manually.
- Turkiye - e-Irsaliye (l10n_tr_nilvera_edispatch): builds UBL 1.2.1 e-Dispatch files from delivery orders.
Odoo describes Nilvera as a GIB-approved electronic document intermediary. Invoices go out in the UBL TR 1.2 format. For how that compares with Peppol, XRechnung and Factur-X, see our guide to Odoo e-invoice formats.
Odoo 19 vs Odoo 20 for Turkish e-invoicing

Odoo 20 covers more Turkish scenarios than Odoo 19, adding commercial invoices, return invoices, direct e-Dispatch sending and e-Receipt import. Odoo 19 handles the basic, public and export scenarios well.
We compared the 19.0 and 20.0 Turkiye docs and the public Odoo source.
| Capability | Odoo 19 | Odoo 20 |
|---|---|---|
| e-Fatura basic, public, export scenarios | Yes, via the Extended module | Yes, in the Nilvera e-invoice module |
| Commercial scenario with accept or reject | Not documented | Yes, auto-accepted by GIB after 8 days |
| Return and withholding return invoices | Not documented | Yes, through credit notes only |
| e-Dispatch | Generate XML, upload to Nilvera by hand | Send from the delivery order, or generate only |
| e-Receipt import into stock receipts | Not documented | Yes, XML fetched every 12 hours |
| Separate e-Invoice and e-Dispatch aliases | One alias field | Two alias fields |
Odoo 19 needs a separate Nilvera E-Invoice Extended module for withholding, tax-exempt and export types. Odoo 20 folds these into the main flow and adds Turkish tax offices to l10n_tr.
One point matters for Community users. In the public odoo/odoo source, the Nilvera modules exist in the 18.0, 19.0 and saas-19.4 branches, but we could not find them in the 20.0 branch, even though the Odoo 20 docs still list them. Confirm availability on your edition before you upgrade.
How do you set up Odoo e-Fatura with Nilvera?
Setup takes five steps: clean company data, install the Nilvera modules, add API credentials, verify each partner and send a test invoice in the sandbox. Most delays come from step one. Turkish teams often call this Odoo e-Fatura entegrasyonu.
- Company record: in Contacts, set the legal name exactly as registered with GIB, the Turkish tax office, the 10-digit VKN (or 11-digit TCKN for individuals), full address and the Mersis number as a tag with the MERSISNO category.
- Modules: install Turkiye - Nilvera and Turkiye - Nilvera E-Invoice, plus the e-Irsaliye module if you ship goods.
- Credentials: go to Accounting, Configuration, Settings, Turkiye Electronic Integrations, and enter the Nilvera API key and the incoming invoices journal. Odoo's source shows a test environment switch and a connection check that compares your tax ID with Nilvera's record.
- Partners: on each customer, open the Accounting tab and click Verify next to Nilvera Status. Registered buyers show e-Invoice; the rest fall back to e-Archive.
- Test: create an invoice, pick the scenario or invoice type, send it by Nilvera, then use Refresh e-Invoices Status and Fetch Nilvera PDF.
For incoming bills, Fetch e-invoices on the purchase journal creates draft vendor bills. Rejecting a commercial bill cannot be undone, so decide who reviews them.
What compliance rules does Odoo enforce for Turkish invoices?
GIB's numbering and discount rules are strict, and Odoo's documentation lists them as mandatory for legal validity. Break them and documents get rejected or become non-compliant.
- Numbering: three alphanumeric characters, then the year, then a sequential number, such as INV/2025/00001.
- No reuse: once a number is submitted, even with an error, it cannot be used again; create a new document.
- Gaps: if a number is skipped, the missing numbers must be issued within 7 days.
- Discounts: no global discount lines; apply every discount at product line level.
- Dispatch prefix: Odoo sends only the last three characters of the delivery sequence prefix, and a prefix shorter than three characters is refused.
- Subscriptions: only one date range per invoice, so lines with different subscription periods cannot share an invoice.
- Taxes: do not delete the preloaded taxes, as e-invoices and e-archives use them.
Withholding (tevkifat) needs extra setup: add GIB reason codes under Accounting, Configuration, GIB Codes, then build group taxes following Odoo's WH 20% example.
Which e-invoice integrator options work with Odoo in Turkey?
Nilvera is the only integrator built into Odoo, but third-party apps connect Odoo to other Turkish integrators. The choice depends on whether you already have an integrator contract you want to keep.
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Odoo Nilvera modules | Built into Odoo's Turkish localization | New Odoo users with no integrator yet | Nilvera fees are separate from Odoo |
| Third-party apps for other integrators | Odoo Apps Store modules that send invoices to integrator APIs | Firms tied to an existing integrator contract | Version coverage, e-Irsaliye support, upgrade risk |
| Custom connector | Your own module using the integrator's API | Large volumes or special scenarios | Build and upkeep cost |
| GIB Portal | Free government web portal | Very small, low-volume businesses | No ERP link, 500 uploads a month, manual archiving |
On the Odoo Apps Store, one connector lists support for integrators such as Uyumsoft, QNB e-Finans, Logo, Mysoft, Sovos and Turkcell, but only for Odoo 18 and only for e-Fatura and e-Arsiv. Check version and document type before you buy.
If you need a custom connector, design it on Odoo 20's JSON-2 API. Our Odoo API integration guide explains how Odoo's external API works and what changed in Odoo 20.
What are the limits of Odoo's Turkish localization?
Odoo covers the main document flows, but you should plan for integrator lock-in, edition questions and some process changes. None of these block a project, but each one needs a decision.
- One built-in integrator: switching away from Nilvera means a third-party app or custom code.
- Edition check for Odoo 20: the Nilvera modules are missing from the public 20.0 Community source, so Community users should confirm before upgrading.
- Older versions: Odoo 19 lacks the commercial scenario, return invoices and e-Receipt import that Odoo 20 documents.
- Process changes: line-level discounts, strict numbering and single-period subscription invoices may change how sales teams work.
- e-Ledger: Odoo generates a zipped CSV, and Odoo says the first invoice must represent the period's opening balance; agree the filing flow with your adviser.
For wider changes, see our Odoo 20 accounting release notes.
Turkish e-invoicing in Odoo by industry
Each industry hits a different part of the Turkish rules, so the setup effort lands in different places. The table shows where we usually spend time.
| Industry | Pain or cost driver | Odoo approach | How iVentureTeam helps |
|---|---|---|---|
| eCommerce and marketplaces | Lower 500,000 TL limit, many B2C e-Arsiv invoices | Automatic e-Archive for unregistered buyers | Map webshop orders to invoice types |
| Wholesale and distribution | e-Irsaliye on every shipment over 10 million TL sales | e-Dispatch from delivery orders | Set dispatch sequences, test receipts |
| Manufacturing and export | Export and registered-for-export scenarios | GIB export flag and exemption reasons | Configure exemption codes and taxes |
| Real estate and vehicle trading | 500,000 TL threshold, withholding cases | Withholding group taxes | Build tevkifat taxes and reason codes |
| Subscription and SaaS | One date range per invoice | Subscription dates at header level | Redesign billing periods |
How much does Odoo Turkey e-invoicing cost?
The cost has three parts: your Odoo subscription, your integrator fees and the implementation work. Odoo does not publish Nilvera prices, so ask Nilvera or your integrator for a quote.
On the Odoo pricing page, the US price billed yearly is US$31.10 per user a month for Standard and US$61.00 for Custom.
Implementation depends on scope. Our published Odoo implementation cost ranges run from $3k to $9k for small projects and $9k to $27k for mid-size ones. These are ranges, not set prices. For a quick figure, try the Odoo project estimate tool.
How iVentureTeam helps with Odoo Turkey e-invoicing

iVentureTeam sets up Odoo's Turkish localization, connects your integrator and tests every document flow before go-live. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.
- Readiness check: your GIB obligations, sector thresholds and current integrator contract, reviewed with your adviser.
- Localization setup: company data, taxes, withholding codes, sequences and fiscal positions in Odoo 19 or 20.
- Integrator connection: Nilvera setup, or a connector to another integrator through our Odoo consulting services.
- Upgrade planning: moving to Odoo 20 for commercial scenarios and e-Receipts, with an edition check first.
- Testing: sandbox runs for e-Fatura, e-Arsiv, e-Irsaliye and incoming bills.
Odoo localization case study: Fernando Tax Management
A Dutch tax and accounting firm needed Odoo reports that met government requirements in two jurisdictions. Fernando Tax Management B.V. was founded in 2008 and serves clients in the Netherlands and Curacao.
Its old system could not adapt, manual entry created duplicate records, and reports had translation gaps in output that feeds government compliance.
We migrated the firm to Odoo 18, built localized tax reports for the Dutch and Curacao contexts, and corrected translation defects across tax and reporting modules. The project took 10 weeks, and the firm reports a 60% reduction in manual data entry.
The same discipline applies in Turkey: get the tax setup and reports right first. Read the Fernando Tax Odoo accounting automation case study.
The bottom line on Odoo Turkey e-invoicing
Odoo is a solid choice for Turkish e-invoicing if you use Nilvera, keep your data clean and follow GIB's numbering rules; Odoo 20 covers more scenarios than Odoo 19. Check your threshold, edition and integrator before you commit.
Confirm your GIB switch date, decide whether Nilvera fits, and test every scenario in the sandbox before your first real invoice.
Ready to set up e-Fatura in Odoo?

Get your Turkish localization, integrator link and tests planned by a team that has delivered ERP projects in 35+ countries. Plan your Odoo Turkey e-invoicing setup with us, call +91-90235-15208, or email business@iventureteam.com.
Frequently Asked Questions
Does Odoo support e-Fatura in Turkey?
+
Yes. Odoo's Turkish localization includes Nilvera modules that send and receive e-Fatura and e-Arsiv invoices, generate e-Ledger files and create e-Irsaliye dispatch notes. You need a Nilvera account and API key.
Who has to switch to e-Fatura in Turkey?
+
Taxpayers with gross sales of 3 million TL or more must switch from 1 July of the following year. The limit is 500,000 TL for online sales, real estate and motor vehicle trading. Licensed hotels must use it regardless of sales.
What is the difference between e-Fatura and e-Arsiv?
+
e-Fatura is for buyers registered in GIB's e-invoice system. e-Arsiv is for buyers who are not registered, such as consumers and many foreign customers. Odoo picks e-Archive automatically when a partner is not registered.
Who must use e-Irsaliye?
+
e-Fatura users with gross sales of 10 million TL or more must issue electronic dispatch notes from the start of the seventh month of the following year. Odoo creates them from validated delivery orders.
Can Odoo connect to integrators other than Nilvera?
+
Not out of the box. Third-party apps on the Odoo Apps Store connect to other Turkish integrators, or a partner can build a custom connector using the integrator's API. Check version and document coverage first.
Is Turkish e-invoicing available in Odoo Community?
+
The Nilvera modules appear in the public Community source for Odoo 18 and 19, but we could not find them in the 20.0 branch. If you run Community, confirm availability before you upgrade to Odoo 20.
What does Odoo 20 add for Turkey?
+
The Odoo 20 docs add commercial scenario invoices with accept or reject, return invoices through credit notes, direct e-Dispatch sending, e-Receipt import into stock and a list of Turkish tax offices.
Why was my Turkish e-invoice rejected?
+
Common causes are wrong partner tax IDs, a reused or skipped invoice number, global discount lines and deleted or edited preloaded taxes. Fix the data, create a new document and send it again.
Can I still use paper invoices in Turkey in 2026?
+
Mostly no for balance-sheet taxpayers. Simple-method and income-expense book taxpayers may still issue invoices up to 3,000 TL including taxes on paper in 2026 under Communique No. 589.
Free e-invoicing and tax readiness check
Getting Odoo ready for e-invoicing?
We check your Odoo version, localization and invoice flows against e-invoicing, then send what to set up, what to test and the effort involved.
Free, with no obligation. A senior consultant replies within 12 business hours.
Free Odoo tools
All tools- Odoo Health CheckVersion, modules, findings and upgrade cost
- Odoo App SelectorWhich apps you need, by industry
- Odoo Project EstimateIndicative cost and timeline in minutes
- Odoo Implementation Cost CalculatorImplementation cost and timeline, in minutes
- Odoo Migration Cost CalculatorVersion jump or legacy ERP, priced in minutes
Continue reading
Odoo Accounting for CFOs in the GCC: VAT, E-Invoicing and Controls
Odoo accounting for CFOs in the GCC: UAE and Saudi VAT, ZATCA and UAE e-invoicing, AED and SAR multi-currency, lock dates and hashed audit controls.
Odoo E-Invoicing Compliance in Egypt: ETA E-Invoice, E-Receipt and KSA
Odoo e-invoicing compliance for Egypt: what Odoo 19 and 20 cover for ETA e-invoices, why the e-receipt needs a partner, and how it compares with ZATCA.
Odoo Argentina Localization: ARCA E-Invoicing, ARBA and Withholdings
Odoo Argentina localization for Odoo 19 and 20: l10n_ar_edi ARCA e-invoicing, ARBA retenciones, IIBB percepciones, setup steps and the padron gap.
