"GİB (the Turkish Revenue Administration) publishes a new package or guide with every update; how do we adapt without breaking our integration and automations?" For companies that generate invoices, dispatch notes and other electronic documents from their own systems, this question is no longer a one-off project but an ongoing operational matter. GİB's e-Belge (e-Document) announcements page lists at least 17 separate announcements from the start of 2026 through September 30; a significant share of them are package, code-list or guide updates.
Why now? Because there are two upcoming dates on the calendar. The e-Döviz ve Kıymetli Maden Alım Satım Belgesi (e-Foreign Exchange and Precious Metals Purchase and Sale Document) package, updated on September 25, 2026, will go live as of November 2, 2026. The development work for the UserList (Kullanıcı Listeleri) Guide, updated on September 30, in turn has to be completed by November 16, 2026. From October 7, the day this article is published, 26 days remain until the first date and 40 until the second.
The framework: what changed on the e-Document side in 2026?
The announcements page shows that updates are both frequent and interconnected. Notable examples:
- January: The e-Fatura (Türkiye's e-Invoice system) and e-Arşiv Fatura (e-Archive Invoice) packages, the UBL-TR Code Lists Guide and the UBL-TR 1.2.1 package were updated; the changes were announced to go live as of February 2, 2026. In the same announcement, the development deadline for the guide on deliveries within the scope of the İnşaat Demiri İzleme Sistemi (İDİS, the Construction Rebar Monitoring System) was, following the feedback received, extended from January 12 to February 2.
- March: On March 16, it was announced that checks based on registry and activity-code records for documents issued through private integrators would start on April 1, and the code "555-KDV Oran Kontrolüne Tabi Olmayan Satışlar" (code 555: Sales Not Subject to VAT Rate Control) was added. With the March 27 announcement, this check was postponed until a further announcement by GİB; it was also stated that no action is to be taken for the package updates dated March 16.
- April: A UserList Guide was prepared for tracking the information of taxpayers whose accounts were closed and the results of the registry integration; the development deadline was announced as April 15, 2026.
- July–August: On July 27, the e-Fatura and e-Arşiv Fatura packages and the UBL-TR Code Lists Guide were updated; it was announced that the changes would go live as of September 14, 2026. On August 24, in turn, it was announced that the deficiencies had been corrected in the e-Fatura package published on July 27.
- September: The e-Gider Pusulası (e-Expense Voucher) package (September 15), the e-Döviz package (September 25) and the UserList Guide (September 30) were updated.
Three lessons emerge from this list. First, there is often a window of a few weeks between the publication date and the go-live date. Second, an announcement can later be postponed, have its deadline extended or have its package corrected; in other words, reading a single announcement is not enough, and the ones that follow need to be monitored as well. Third, several components (a package, a code list, a guide) can change together on the same day.
What do the two upcoming dates mean?
e-Döviz ve Kıymetli Maden Alım Satım Belgesi (November 2). According to GİB's 2023 announcement, this document has the same legal status as paper-based foreign exchange and precious metals purchase and sale documents; it is not a new type of document. It had been announced at that time that authorized institutions (yetkili müesseseler) brought into scope were required to issue their documents as this electronic document from May 1, 2023. The September 25, 2026 announcement, in turn, was published not as a new obligation but as a package update to the existing practice. Version 1.3 of the package can be accessed from the announcements page; the details of the change should be followed through the package contents and the release notes of the integrator in use.
UserList Guide (November 16). The guide describes the XML file in which taxpayers' e-Fatura and e-İrsaliye (electronic dispatch note) label information is shared. In version 1.1 of the guide, test access addresses were added and the descriptions in the "User Temp List" section were updated. For setups that send their documents through their own system or that automatically query recipient labels, this is a change that directly touches the data flow.
For an example of a similar preparation process on the agricultural purchasing side, see our article on SMS verification in the e-Müstahsil Makbuzu (e-Producer Receipt); for the end-to-end use of e-Document data in finance processes, see our article on e-Fatura and e-transformation.
Why are automations affected?
e-Document updates are not just a problem for the integrator or the ERP. In many companies there are additional automations (software robots, scripts, transfer services) that read invoice data, classify it against code lists, check the recipient label or create accounting entries. When a new value is added to a code list or the usage rule of an XML field changes, these automations can produce wrong results without throwing an error. For this reason, update management should not be limited to the system that produces the document; it should cover every step that consumes the document.
A practical path: linking updates to a business process
The steps below are a general framework derived from the pattern on the announcements page; each organization should adapt it to its own issuing channel (the GİB portal, a private integrator or direct integration).
- Assign a single owner for monitoring. Make one person or team responsible for reading the announcements page regularly (for example, weekly). Log each announcement with its publication date, the document type concerned, and its go-live or final development date.
- Build an inventory of documents and components. List which e-Document types you issue and receive, which system produces them, and which automations read this data. When an announcement arrives, the impact analysis can be done from this inventory in a few minutes.
- Plan the calendar backward. Working back from the go-live date, place the testing, approval and production cutover steps. Dates such as November 2 and November 16 should go into the management calendar together with interim checkpoints.
- Ask your integrator and software provider for a written plan. Clarify on what date the current package will be moved to the test environment and to production, and whether any change is required on your side.
- Use the test environment. Documents such as the UserList Guide also include test access addresses. Verify changes in the test environment with sample documents, not on live data.
- Put automations through regression testing, too. After a code-list or field change, check that the bots and scripts that read the document produce the expected output with sample documents. Turn the verification into automated checklists as far as possible.
- Watch for follow-up announcements. As the 2026 examples show, a package can be corrected afterwards and a check can be postponed. After going live, keep watching for a few weeks to see whether a new announcement on the subject appears.
- Keep records. Record which announcement was complied with, on what date and with what change. This record is useful both in internal audit and in planning the next update.
Conclusion
GİB's e-Belge announcements show that the electronic document infrastructure is not static but a system that is updated regularly. Although the nearest dates are November 2 (the e-Döviz package) and November 16 (the UserList Guide), the real gain is building a repeatable process in which every announcement is tied to the inventory, the calendar and testing. Once this process is in place, the next package update turns into planned maintenance rather than a last-minute scramble.
Why logistics experience matters in e-Document change management. In a business that moves goods, an e-Document update is felt on the loading dock as well as in accounting: dispatch notes (e-İrsaliye) accompany the goods, and the UserList file described above covers e-İrsaliye labels as well as e-Fatura ones. The eight steps above will look familiar to anyone who has run a distribution network: an inventory of what is in the network, a named owner for every hand-off, a calendar planned backward from the delivery date, a dry run before go-live and a dated record of every change. One of Orient Global's consultants brings more than 30 years in operations, logistics and supply chain: at a technology distribution company of roughly one billion dollars in scale, he ran logistics, warehousing, technical service and administrative operations end to end, building and leading teams of 100+ people and delivering lasting gains in operational performance through KPI-driven programs. He has also managed nationwide warehouse and transport operations across leading retail, logistics and distribution organizations. An industrial engineer, he now brings that supply-chain discipline to SMEs through AI and automation. Meet our consultants.
This article is for general information purposes only and does not substitute for legal advice.
#interimmanagement #forwarddeployedengineering