E-Transformation

E-solutions: end-to-end e-transformation inside SAP

Eight statutory documents and electronic finance processes, from e-Invoice to e-Inventory, in one flow from the SAP document to GİB and back. Updates required by regulatory changes are handled under support.

E-transformation readiness checkView in catalogue
Eight solutions

Document by document, process by process

E-ÇÖZÜM

e-Invoice (e-Fatura)

Generate GİB-compliant UBL-TR e-invoices straight from SAP billing and accept or reject incoming invoices inside SAP.

E-ÇÖZÜM

e-Archive Invoice (e-Arşiv)

Issue e-Archive invoices from SAP for non-registered customers and consumers, and file the daily GİB report automatically.

E-ÇÖZÜM

e-Delivery Note (e-İrsaliye)

Create e-Delivery notes automatically from the shipping document and track recipient responses (accept, partial, reject) in SAP.

E-ÇÖZÜM

e-Ledger (e-Defter)

Produce journal and general ledger in e-Ledger format from SAP; create certificates, upload to GİB and keep the secondary copy.

E-ÇÖZÜM

Customer & Vendor e-Reconciliation

Move account reconciliation to digital — send, track and resolve in one flow.

E-ÇÖZÜM

Electronic Bank Statement (EBS)

Import bank statements (MT940, CAMT.053, bank-specific formats) into SAP automatically and finish bank reconciliation with rule-based clearing.

E-ÇÖZÜM

e-Tax Declaration (e-Beyanname)

Prepare VAT, withholding, advance tax and stamp duty declaration data from SAP; validate with control reports and file in e-Declaration format.

E-ÇÖZÜM

e-Inventory Ledger (e-Envanter)

Produce the period-end inventory ledger and stock count lists from SAP in statutory format, and close count differences with documents.

Who, and when?

2026 obligations calendar

Headline points under VUK General Communiqués No. 509 and 573. Thresholds and dates change with new communiqués; confirm your own position with your tax advisor.

1 January 2026
First-class merchants keeping books on a balance-sheet basis issue e-Archive invoices regardless of buyer and without an amount limit. Paper invoices effectively end for this group.
1 July 2026
Taxpayers with 2025 gross sales revenue of TRY 3 million or more move to e-Invoice and e-Archive.
TRY 500k threshold
In e-commerce, real estate and motor vehicle trading/leasing/brokerage and internet advertising intermediation, revenue of TRY 500k or more triggers the e-Invoice mandate without waiting for the general threshold.
e-Ledger certificates
Certificates are uploaded monthly or per advance-tax period, declared at the start of the year and fixed for the year. Late uploads carry a special irregularity penalty — the calendar has to be part of the close routine.
How it works

From SAP document to GİB, from response back to document

  1. The document is born in SAP

    The invoice, delivery note, ledger or reconciliation record is created as a standard SAP document; users learn no new screen.

  2. Conversion and validation

    UBL-TR / XBRL generation, taxpayer lookup, scenario selection and GİB schema checks run as the document is posted; errors are caught before they reach GİB.

  3. Transmission

    The document is transmitted to GİB through the method chosen during implementation (a private integrator or the GİB portal).

  4. The response is written back

    Acceptance, rejection, certificate confirmation or reconciliation reply is written to the SAP document; status is tracked on one screen and exceptions drop into a list.

Scale

Teams that run these processes every day

At Rönesans Holding, e-invoice, e-ledger and e-reconciliation run on the same SAP landscape across more than 200 company codes, together with SLA-based support on the full set of financial modules. Read the case →

E-transformation FAQ

Do I need a separate integrator licence for the e-solutions?

Yes — transmission to GİB requires a certified integrator or the GİB portal method. Generating and validating the document and handling the responses run on the SAP side; transmission goes through the chosen method. Which integrator or method is used is decided at the start of implementation, taking your existing contracts into account.

Does it run on SAP ECC or is S/4HANA required?

Both. The packages are installed on ECC 6.0 and S/4HANA with the same process logic; on a move to S/4HANA the e-transformation setup is migrated, not rewritten. Fiori-based monitoring screens are used on S/4HANA, classic screens on ECC.

What happens when regulation changes?

GİB schema, scenario and calendar changes are applied at package level and distributed to our clients under AMS. UBL-TR version transitions or e-Ledger certificate calendar changes, for example, are rolled out to every client through a package update rather than company by company.

Is one installation enough for multiple company codes and taxpayers?

Yes. The installation is parameterised per company code: each company has its own tax number, scenario, integrator account and number range while the process is shared. Rönesans Holding manages more than 200 company codes on this structure.

Which document should we start with?

With the document the legal calendar imposes: for most companies that is e-Invoice and e-Archive, followed by e-Ledger. If you are outside the mandate, starting with the process that creates the most manual work — usually e-Reconciliation or the electronic bank statement — gives the fastest return. In the free analysis we propose an order based on your current landscape.

Let's map which document you are in, and on which calendar.

Free e-transformation analysis