e-Invoice Integration in Turkey: How It Works Between Your ERP, Integrator and GİB

e-Invoice integration in Turkey means that as soon as an invoice is created in your ERP or accounting system, it is converted — with nobody re-keying it — into the Revenue Administration's (GİB) XML standard, UBL-TR, and delivered to the buyer through a licensed private integrator or the GİB system; incoming invoices are pulled back into the ERP the same way.

Registering for e-Fatura meets the legal requirement; integration is what delivers the efficiency, because each invoice is entered once and its status (sent, accepted, rejected, failed) is visible in your own system. If you are exporting invoices from the ERP and uploading them to a portal, or typing supplier invoices in by hand, your integration is incomplete.

What are e-Fatura, e-Arşiv and e-İrsaliye?

For readers new to the Turkish system, three documents matter:

• e-Fatura (e-Invoice): issued when both seller and buyer are registered with the e-Fatura application. It is created in GİB's UBL-TR XML format and delivered electronically.
• e-Arşiv (e-Archive invoice): issued when the buyer is not registered — a consumer or a non-registered business — and usually delivered by email or as a printout.
• e-İrsaliye (e-Dispatch Note): the electronic version of the delivery note that accompanies goods, closely tied to warehouse and shipping processes.

Whether a business must switch is set by GİB communiqués, based on gross sales thresholds, sector and certain special cases, and the thresholds are revised from time to time. International companies operating in Türkiye should confirm their position against GİB's current announcements and with their local accountant.

There are two main invoice scenarios. Under the basic invoice scenario, the buyer does not need to respond. Under the commercial invoice scenario, the buyer can send an accept or reject response through the system within 8 days of receiving the invoice. If the ERP does not assign the right scenario to each customer, rejections and corrections come back to finance as extra work.

The cost of doing nothing

e-Invoicing is no longer the exception in Türkiye; it is the backbone of commercial life.

According to the Revenue Administration (GİB) 2025 Annual Activity Report, the number of taxpayers using e-Fatura reached 1,937,308 at the end of 2025, up from 532,910 in 2021.

Volumes have grown just as fast. The same report shows 1,188,605,103 e-Invoices issued in 2025 (534,971,392 in 2021), while e-Archive invoices reached 11,523,831,577. At this scale, even a business issuing a few hundred invoices a month loses time and introduces errors if every invoice is exported and uploaded by hand, or every incoming invoice is keyed in manually.

The electronic document chain does not stop at invoices. The GİB 2025 Annual Activity Report also shows the number of taxpayers using e-İrsaliye rising from 402,985 in 2024 to 632,288 at the end of 2025. When orders, delivery notes and invoices are carried between three systems by hand, the mismatches surface at month-end reconciliation.

Three ways to connect to e-invoicing in Turkey: portal, private integrator, direct integration

For most businesses the right route is a private integrator. But signing a contract with an integrator is not the same as integrating. Downloading a file from the ERP and uploading it to the integrator's panel is barely different from using the portal. The value comes from an automatic, two-way connection between the ERP and the integrator. Whether to use the integrator's ready-made ERP connector or commission an integration built around your own flow is a small example of a wider decision; the criteria are in custom vs off-the-shelf software.

Seven steps to a well-built e-invoice integration

1. Map your invoice flows. Where are invoices created? ERP, web shop, marketplaces, a B2B dealer portal, service software… Every source belongs in the integration. In construction and contracting, the invoice follows an approved progress payment; we describe that chain in construction progress payment tracking.
2. Clean customer master data. If tax numbers, legal names and e-Fatura registration status are wrong, documents either fail or are issued as the wrong type (e-Archive instead of e-Invoice). We cover weeding out duplicate and incomplete customer records in data quality and duplicate records.
3. Define scenarios and document types. Decide how basic and commercial scenarios, returns, exemptions and withholding cases map to fields in the ERP.
4. Automate outgoing invoices. When an invoice is approved in the ERP it should go to the integrator automatically, with the returned document number and status written back.
5. Pull in incoming invoices. Supplier invoices should be fetched from the integrator automatically, created as draft entries in the ERP and matched to the purchase order and delivery note. For invoices that still arrive as PDFs or on paper, see OCR invoice processing.
6. Design error and rejection handling. Decide who is alerted, and on which screen, when a document is rejected or fails; temporary connection errors should trigger automatic resending.
7. Keep monitoring and an audit trail. Record when each invoice was sent, what response came back and who intervened. This helps in audits and in disputes with customers.

Common mistakes in integration projects

• Connecting outgoing invoices only. Sales invoices go out automatically, but supplier invoices are downloaded one by one from the integrator's panel and keyed in. An integration without the incoming side leaves half the workload untouched. Where the panel offers no API, RPA bots can take over that repetitive download-and-key work.
• Not writing status back. The invoice is sent, but "delivered, accepted, rejected" never shows in the ERP. A rejection is noticed only when the customer fails to pay.
• Skipping the test environment. If every document type (return, exemption, withholding, foreign currency) is not tried in the integrator's test environment first, the first faulty documents go to real customers.
• Depending on one person. If only one finance employee knows the error screen, faulty documents pile up while they are on leave. Alerts should go to a role, not a person.
• Leaving the external accountant out. Where bookkeeping is outsourced, how and how often documents reach the accountant is part of the integration design. We cover the accountant's side of the document flow in document management for accounting firms.

If you want the technical background first, our article API integration explained is a good starting point. Guides to the systems that feed invoicing, such as ERP, WMS and dealer portals, are collected in our Software Development articles.

For exporters, the e-invoice is only one link in a shipment's document chain and needs to be kept alongside the bill of lading, packing list and origin certificates. We explain how to hold that chain in one file in import export document management.

For automotive suppliers, the e-İrsaliye and the despatch advice (DESADV) sent to the customer describe the same shipment. Our article on automotive EDI integration shows how to produce both from one source. For the general picture of order and invoice exchange with retail chains and other large buyers, see what EDI is.

How we deliver e-invoice integration at Digital Bridge

We treat e-invoicing not as a standalone compliance project but as one link in the order–delivery–invoice chain:

• We review your current flow. We map which systems produce invoices, which integrator you use and where manual transfers happen.
• We connect the ERP to the integrator. Through our API and system integration work we link Logo, Mikro, SAP and custom ERPs to private integrators in both directions, with failed-document alerts and automatic resending built in. Where the ERP has no API, we can integrate at database level.
• We bring other sources into the same flow. Automatic e-Archive invoices from web shop orders, marketplace orders flowing into the ERP, carrier connections — we combine these system integrations into a single data flow. We cover these channels in more depth in our marketplace integration and B2B ecommerce ERP integration guides.
• We fix the data side. We clean inconsistencies in customer and product master data before go-live and, where needed, complete missing fields on the ERP side.

We do not sell off-the-shelf packages: after a needs analysis, you receive a written proposal setting out scope, phases and cost. If you have not moved to ERP yet, our guide to ERP for small businesses will help with that decision.

Invoices that arrive by email: where Smart360 fits

The e-Fatura system does not cover every invoice. e-Archive invoices, invoices from foreign suppliers, pro formas and quotes still arrive by email and pile up in the finance inbox. Our own Smart360 product family organises that document traffic; sending e-Invoices remains the job of the ERP–integrator connection described above.

• SmartMail classifies incoming messages automatically, so invoice and payment emails are grouped together. From an attached invoice PDF it extracts the parties, issue and due dates, subtotal, VAT, grand total, document number and tax number — without the file being downloaded. Finance staff see the amount and due date without opening the invoice and can check them against the ERP record.
• In the shared finance mailbox, access is split into nine separate permissions; delete and quarantine management are off by default for new assignments, and every message carries an action log. You can see who viewed which invoice and who added a note.
• Every incoming email is checked for identity (SPF, DKIM, DMARC), structure and content, and warning signs such as lookalike domains, display-name impersonation and Reply-To mismatches are reported with a written explanation — an important layer against fake invoice email scams.
• Attachments can be saved to SmartFiles in one click. In SmartFiles, uploading a file with the same name creates a new version rather than overwriting, and earlier versions can be restored; eight permissions such as read, write and delete are managed per person or department in a single matrix. Each upload is analysed by AI automatically, and you can ask a whole folder questions such as "which invoices this quarter are overdue?".

Your next step

Start by measuring the manual work: last month, how many invoices did you export from the ERP and upload elsewhere, and how many incoming invoices did you key in by hand? With those two figures, contact us and we will plan the link between your ERP and your integrator.