e-Invoice integration check service for Türkiye’s UBL-TR update

e-Invoice integration check service after the UBL-TR update in Türkiye

Aksiyon Soft is launching an e-invoice integration check service for companies that connect their ERP or e-commerce platform to a private integrator (özel entegratör) in Türkiye. On 27 July 2026 the Turkish Revenue Administration (GİB) announced updated e-Fatura, e-Arşiv invoice and UBL-TR code list packages, which went live on 14 September 2026. New codes and schematron rules can turn into rejected invoices and manual rework for any integration that hard-codes the old lists.

The service is aimed at manufacturers, logistics firms, retailers and service companies that send documents to a private integrator from their own ERP, accounting software or online store. The goal is simple: catch documents that break the new rules in a test environment rather than in production, and document how your integration behaves when something goes wrong.

In short

• GİB’s UBL-TR update went live on 14 September 2026, adding exemption code 233 and foreign plate types.
• The erreceipt alias for the e-expense voucher (e-Gider Pusulası) joined the reserved and envelope alias lists.
• Our check covers field mapping, XSD and schematron validation, test scenarios and rejection monitoring.
• Queue, retry and idempotency behaviour is reviewed separately so duplicate-invoice risk is visible.
• You receive a prioritised analysis report, a fix sprint and a live monitoring plan.

What changed on 14 September 2026?

In its 27 July 2026 notice on the e-Belge portal, GİB updated the e-Fatura package, the e-Arşiv invoice package and the UBL-TR code list guide; follow-up packages on 11 and 24 August fixed remaining gaps. These are the changes that most often create work on the integration side.

New exemption code 233

Code 233 now covers transfers of real estate to the State and public legal entities carrying out expropriation under Expropriation Law No. 2942. Systems that keep the code list as a fixed array cannot select it or fail validation. Investment-incentive exemption codes were also moved to a separate list and are accepted only with the matching scenario and invoice types.

Foreign plate and trailer types

The plate scheme list gained YABANCIPLAKA, YABANCIDORSE and YABANCIDORSEPLAKA. Turkish plates must follow the province code, letters and digits pattern, while foreign plates may only contain capital letters, digits, underscores and hyphens. The schematron also checks that e-waybills carry a vehicle plate.

The erreceipt alias for e-expense vouchers

The erreceipt alias, representing the e-Gider Pusulası, was added to the reserved aliases that must not appear in document XML and to the envelope alias list. User account definitions carry specific rules for it, and GİB refreshed the e-Gider Pusulası package on 15 September 2026.

TÜRKAK-accredited certificates for private integrators

Version 1.14 of the Private Integration Guide, updated on 29 June 2026, requires private integrators to hold ISO 27001 issued by TÜRKAK-accredited bodies, alongside ISO 22301 and ISO 20000. It mainly concerns integrators, but it is now a fair question to ask when you choose or renew one.

What does the e-invoice integration check cover?

The check follows the whole path, from the code that builds the document to the response your private integrator returns. The table shows what we review for each item and what you get at the end.

Check item	What we look at	Output
UBL-TR XSD and schematron validation	Sample documents validated against the current GİB package	Error list mapped to individual rules
Field mapping review	Code 233, investment-incentive codes, plate scheme types, hard-coded lists	List of fields that must change
Test environment scenarios	Exempt sales, foreign-plate shipments, returns and e-Arşiv buyer variants	Repeatable scenario set
Rejected-invoice monitoring	Application responses, rejection reasons, link to the source record	Rejection dashboard and error triage
Queue, retry and idempotency	Resends after timeouts, duplicate documents, ordering issues	Risk note with a proposed fix
Report and fix sprint	Findings ranked by business impact	Analysis report and a planned fix sprint

How does the check work?

We work without stopping your system or touching live document traffic. The steps are:

1. Discovery: we map document types, scenarios, the integrator connection and your error-handling flow together.
2. Analysis report: sample documents are validated and mapping and resilience findings are ranked by impact.
3. Fix sprint: priority findings are fixed in code and delivered with release notes.
4. Testing: the scenario set runs in the integrator’s test environment and results are recorded.
5. Live monitoring and SLA: the rejection dashboard and alerts go live; monitoring can continue under a support contract.

If you want to go deeper into resilience, our guide to the outbox pattern, idempotency and retries explains the design decisions behind safe resends.

What should you prepare before we start?

This checklist speeds up the work considerably:

• The document types and scenarios you use (basic, commercial, e-Arşiv, return, exempt, export).
• Your private integrator, test environment access and connection method (web service, file, API).
• Rejected invoice samples and rejection messages from the last three months.
• Where code lists live: a database table, a configuration file or constants in code.
• The owner of the module that builds documents and your release process.
• Whether you ship with foreign-plated vehicles and whether any sales fall under code 233.

How Aksiyon Soft can help

The check is delivered as part of our API and integration service. If you need a permanent middle layer, the API and data integration platform approach brings mapping, queues and monitoring into one place. Our article on enterprise integration middleware architecture covers the architectural choices, and the GİB UBL-TR update guide walks through the technical details of the update.

Our team is headquartered in Samsun and works remotely across Türkiye; we have no branch offices. Meetings run over video, with planned visits when a project needs them. After go-live, response times are written into a maintenance and support agreement.

Frequently asked questions

Do we have to replace our current system for an e-invoice integration check?

No. We review your existing ERP and integrator connection. Changes are made only for findings prioritised in the report, with your approval, during the fix sprint.

Our private integrator already applied the update. Is there still work on our side?

Quite possibly. The integrator updates its own validation, but the field that writes code 233 or a foreign plate type lives in your system. Hard-coded code lists are the most common source of trouble we see.

How long does the check take?

It depends on the number of document types, scenarios and integration points. After discovery, scope and timeline are set out in the analysis report; we do not promise a fixed duration.

Do you touch live invoices?

No. Validation runs on sample documents and the integrator’s test environment. Go-live happens as a planned release once test results are approved.

Do you need to work on site?

Usually not. Our Samsun team works remotely across Türkiye and can add a planned visit where access rules or security requirements call for it.

Let’s talk about your project

Add your recent rejection messages and the document types you use to a short note on our contact form, and we will agree the scope of the check together in a discovery call.

Sources

• GİB e-Belge — Announcements: e-Fatura, e-Arşiv and UBL-TR code list update (27 Jul 2026)
• GİB — e-Fatura Private Integration Guide, version 1.14 (29 Jun 2026, Turkish)
• PwC Türkiye — e-Transformation Bulletin 2026/23: e-Fatura package and UBL-TR code lists updated (28 Jul 2026, Turkish)
• Vergi Teknolojileri — GİB e-Fatura and e-Arşiv guides updated: changes effective 14 September (2026, Turkish)