Turkey UBL-TR e-Invoice Update: Effective 14 Sept 2026

Short summary

With its announcement dated 27.07.2026, GİB (the Turkish Revenue Administration) updated the e-Invoice (e-Fatura) Package, the e-Archive Invoice (e-Arşiv Fatura) Package and the UBL-TR (Code Lists) Guide — UBL-TR being Turkey's national profile of the UBL invoice standard. The announcement states the effective date explicitly: the updates will go live as of 14.09.2026. Two corrections followed — on 11.08.2026 the gaps in earsiv.xsd in the e-Archive package were fixed, and on 24.08.2026 the gaps in the e-Invoice package dated 27/07/2026 were fixed.

In practice this means: the package you downloaded at the end of July is not current. If you prepared with files obtained before the two August corrections, you need to validate again with the latest version before the effective date.

Who does this affect?

• Those using the direct integration method — they must apply the schema and code list update in their own system. This is where the real workload lies.
• Those working through a private integrator — technical compliance is the integrator's responsibility. Still, it is worth asking your integrator when it will put this update live.
• GİB Portal users — on the portal the change is applied in GİB's own infrastructure; no action is needed on the user side.

Why does the code list update matter?

The UBL-TR Code Lists define which values fields used on an invoice — such as unit, country, tax, currency and document type — may take. When you send a code that is not valid in the list, GİB rejects the document. That is the insidious side of code list changes: while the system works with yesterday's code, the same invoice may be rejected after the effective date, and the problem is only noticed with the first rejected document.

Checklist before 14 September

1. Download the packages again from GİB's page — the July copy is no longer valid; get the version released after the August corrections.
2. Run schema validation (XSD) again with the current files; on the e-Archive side especially with earsiv.xsd.
3. Compare the code values you use with the current UBL-TR list; if a code has been removed or changed, fix your mapping.
4. Send a few documents end to end in the test environment — especially the document types you use most often.
5. If you use a private integrator, confirm in writing the go-live date and when the test environment will be ready.

Status for ELPO customers

For ELPO e-Belge users this update is applied on the integrator side; regulatory tracking is included in the subscription and the customer does not need to update schemas separately. Customers who map fields from their own ERP are informed separately if any field is affected by the code list change.

Source

The original announcements and the current packages are on GİB's e-Belge website: ebelge.gib.gov.tr. This article is based on the announcements published as of 4 September 2026; a new correction may come before the effective date, and you can follow the current list on our GİB e-Belge regulatory calendar page.