Turkey e-Invoice and e-Belge Integration for SAP

Turkey’s digital tax document framework extends beyond e-Fatura and e-Arşiv. SAP teams may also need to address e-İrsaliye, e-Defter and sector-specific e-Belge processes, depending on the legal entity, taxpayer status, activity, turnover and transaction flow.

SAP scope check

Identify the Turkish e-Belge workstreams your SAP landscape may need.

This directional self-check reviews your SAP landscape, document scope, routing, logistics, ledger evidence, integration and operating controls.

7 questions · No login · No data upload

Question 1 of 7

Which SAP landscape is in scope?

Choose the primary landscape used for Turkish finance, billing and logistics processes.

SAP ECC 6.0 S/4HANA on-premise S/4HANA private cloud S/4HANA public cloud Mixed SAP landscape Not confirmed yet

Next question

Evaluating Turkey e-Invoice and e-Belge for your SAP landscape? In force

A short scope review identifies which Turkish document flows affect your SAP landscape.

Landscapes assessed

SAP ECC and SAP S/4HANA; release, edition, installed components and country scenario are reviewed before any support commitment

Delivery model

Confirmed per product and landscape: an on-stack S4FN Add-on, a side-by-side S4FN extension on SAP BTP, or SAP Integration Suite connectivity

Commercial scope

Confirmed in the written proposal by country, legal entities, systems and usage scope

Engagement sequence

Scope review → landscape fit check → written implementation proposal

Get pricing and a 20-minute technical call

Your SAP releaseSAP ECC 6.0S/4HANA on-premiseS/4HANA private cloudS/4HANA public cloudMixed landscapeNot sure yet

Request a scope review Country: Turkey (auto-filled) · We reply with the most practical next step

Which Turkish requirements can affect SAP?

The first task is not choosing an interface. It is determining which document types apply to each legal entity and business process. The following four streams are the most relevant starting points for an SAP landscape review.

Requirement	Typical SAP process	Implementation focus
e-Fatura	SD billing, FI invoices, accounts receivable and payable	UBL-TR mapping, recipient registry checks, GİB or integrator exchange, responses and status reconciliation
e-Arşiv Fatura	Invoices to recipients outside the e-Fatura registry, including relevant consumer and export scenarios	Correct routing, document output, reporting, delivery evidence and current amount-rule handling
e-İrsaliye	SD delivery, MM goods movement, warehouse and transport processes	Scope assessment, dispatch data, sender and recipient flows, status handling and links to the underlying delivery
e-Defter	FI general ledger and statutory bookkeeping	Ledger data quality, file and berat generation, signing, submission evidence and period controls

Sector and transaction-specific e-Belge types

GİB also operates e-SMM, e-Müstahsil Makbuzu, e-Gider Pusulası, e-Bilet, e-Dekont, e-Döviz, e-Adisyon, e-Sigorta and GMÖEBYS document systems. These do not apply universally. Relevance depends on the company’s sector, activity, taxpayer profile and actual document flows.

Sales and finance

Determine whether each recipient is registered for e-Fatura, then route the transaction correctly. Master-data quality and current GİB registry information are compliance controls.

Goods movement

Where e-İrsaliye applies, the electronic dispatch document must remain aligned with SAP deliveries, goods movements and transport events.

Ledger evidence

e-Defter is a separate workstream from invoice exchange. Reconciliation should connect source transactions, ledger output, signed files, berats and submission evidence.

Specialized documents

Professional services, agriculture, banking, foreign exchange, hospitality, insurance and passenger transport can introduce additional e-Belge obligations.

What changed in 2026?

• 1 January 2026: VUK General Communiqué No. 582 removed the amount threshold from the relevant e-Arşiv issuance rule.
• 8 May 2026: VUK General Communiqué No. 593 introduced the option to issue specified mandatory e-documents through New Generation Cash Registers with integrated payment information in defined retail scenarios.
• 22 May 2026: GİB published or updated technical material for e-Arşiv, e-Müstahsil Makbuzu and e-Gider Pusulası.
• 29 June 2026: GİB updated the e-Fatura Special Integration Guide.

Technical teams should follow the current GİB packages, validation rules, code lists and guide versions. A publication date does not automatically mean that every change applies to every company or every invoice scenario.

How S4FN supports the SAP workstream

1. Scope the obligation: identify applicable legal entities, document types, business processes and exceptions.
2. Assess the landscape: review SAP release, modules, existing DRC or local solutions, integrations and master data.
3. Map the documents: connect SAP source fields to the relevant UBL-TR or GİB structure and validation rules.
4. Design the exchange: define GİB or special-integrator connectivity, signing, routing, acknowledgements and retry controls.
5. Close the evidence loop: reconcile SAP documents with authority responses, ledger evidence, exceptions and operational monitoring.

SAP process map

SAP area	Relevant Turkish stream	Questions to resolve
SD and FI billing	e-Fatura and e-Arşiv	Who is the recipient, which route applies, which profile and document scenario are required?
MM, SD logistics and warehouse	e-İrsaliye	Which movements are in scope, when is the document issued, and how are responses linked to SAP?
FI general ledger	e-Defter	Which books and periods apply, and how are files, berats, signatures and evidence controlled?
Industry processes	Specialized e-Belge	Which sector documents exist, where is their source data, and what reporting or delivery flow is required?

Compatibility and delivery scope

SAP ECC and SAP S/4HANA landscapes can be assessed. The appropriate delivery model depends on the release, edition, installed components, current document solution, security policy and country scenario.

The confirmed approach may use an on-stack S4FN add-on, a side-by-side extension on SAP BTP or SAP Integration Suite connectivity. Product fit, supported scenarios and commercial scope are confirmed in the written proposal after the landscape review.

Security and data handling

Compliance processing should remain traceable to the originating SAP transaction. Deployment, data residency, certificate custody, signing responsibilities and authority communication must be agreed during technical design.

DRC Sprint Country Compliance Pack

Turkey: turn mandate scope into SAP delivery

The Turkey pack connects relevant e-Fatura, e-Arşiv, e-İrsaliye and e-Defter requirements to system evidence, architecture decisions, implementation work and operational controls.

Requirement→Evidence→Decision→Implementation→Operation

Explore Country Packs Assess your SAP landscape

What the pack connects

• 01Mandate controlsScope, scenarios, deadlines and exceptions
• 02SAP evidence checksRelease, component, configuration, data and process evidence
• 03Delivery assetsDecision records, test scenarios, work packages and operating controls

Turkey focus: document scope, UBL-TR mapping, taxpayer routing, logistics and ledger evidence, GİB responses, status controls and archiving.