This blog post provides a step-by-step guide on how to implement the new legal requirement released by GIB (GELİR İDARESİ BAŞKANLIĞI) for eInvoice and eDespatch under the Construction Rebar Tracking System (IDIS) using Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud.
Background:
We have already published a blog titled Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud which explains how SAP S/4HANA Public Cloud customers can leverage developer extensibility to modify the content of XML files generated during electronic invoice submissions, in accordance with specific business and legal requirements.
Note for SAP S/4HANA Private Cloud and ECC environments:
In SAP S/4HANA Private Cloud and SAP ECC environments, the same extensibility approach is available. However, in these systems, the BAdI implementation must be carried out for EDOC_ADAPTOR instead of EDOC_ADAPTOR_CLOUD.
What’s New?
GIB has published a legal requirement for invoices issued under the Construction Rebar Tracking System, which impacts certain companies starting from 21st November 2025. In this blog, we aim to address this requirement by building on the learnings from the previous blog highlighted in the background.
What are the technical specifications of the requirement?
Currently, the system does not automatically determine whether a billing or finance document is related to the Construction Rebar Tracking System. Customers must explicitly indicate that the invoice belongs to a Construction Rebar Tracking System and provide the required values.
As part of the legal requirements published by the authorities, the following new Profile IDs must be used in the UBL (Universal Business Language, an ISO standard XML) representation:
IDIS – for eInvoice ScenariosIDISIRSALIYE – for eDespatch scenarios
eInvoice
ProfileID for IDIS Scenario
For IDIS-relevant invoices, the ProfileID in the UBL-TR XML will be set to IDIS.
Cardinality: 1 (Mandatory)This value determines that the invoice belongs to the IDIS scenarioThe solution will automatically populate this value for applicable
Shipment Number (Sevkiyat Numarası) at Header Level:Mapped to: Invoice/AccountingSupplierParty/Party/PartyIdentification
SE-<number> with schemeID as SEVKIYATINO – This would carry the shipment number prefixed with SE. The total number of characters is 10.
Example: SE-1345840IssueDate should be filled with the investment certificate date in DD/MM/YYYY format
Tag Number (Etiket Numarası) at Item Level:Invoice/InvoiceLine/Item/AdditionalItemIdentification/ID should be filled with tag number generated within the scope of IDIS (Rebar Monitoring System). This number is a 9-character alphanumeric value, where the first 2 characters are letters followed by 7 numeric digits.
SchemeID should be ETIKETNO.
Example: CV0152457
eDespatch
ProfileID for IDISIRSALIYE Scenario
For IDISIRSALIYE-relevant invoices, the ProfileID in the UBL-TR XML will be set to IDISIRSALIYE.
Cardinality: 1 (Mandatory)This value determines that the invoice belongs to the IDISIRSALIYE scenarioThe solution will automatically populate this value for applicable
Shipment Number (Sevkiyat Numarası) at Header Level:
Mapped to: /DespatchAdvice/DespatchSupplierParty/Party/PartyIdentification
SE-<number> with schemeID as SEVKIYATINO – This would carry the shipment number prefixed with SE. The total number of characters is 10.
Example: SE-1345840IssueDate should be filled with the investment certificate date in DD/MM/YYYY format
Tag Number (Etiket Numarası) at Item Level:/DespatchAdvice/DespatchLine/Item/AdditionalItemIdentification/ID should be filled with tag number generated within the scope of IDIS (Rebar Monitoring System). This number is a 9-character alphanumeric value, where the first 2 characters are letters followed by 7 numeric digits.
SchemeID should be ETIKETNO.
Example: CV0152457
Result:
When you display the XML file of the electronic document in the eDocument Cockpit (EDOC_COCKPIT) corresponding to the above invoicing scenario, you will see that the mentioned tags are populated accordingly. Please note that any error handling and troubleshooting will depend on the actual submission of this document to the authorized service provider.
Conclusion:
With recent enhancements to the Türkiye Document and Reporting Compliance solution, SAP has made it significantly easier to tailor electronic document outputs.
This improvement gives you more flexibility and helps ensure compliance with Türkiye’s legal requirements.
This blog post provides a step-by-step guide on how to implement the new legal requirement released by GIB (GELİR İDARESİ BAŞKANLIĞI) for eInvoice and eDespatch under the Construction Rebar Tracking System (IDIS) using Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud.Background:We have already published a blog titled Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud which explains how SAP S/4HANA Public Cloud customers can leverage developer extensibility to modify the content of XML files generated during electronic invoice submissions, in accordance with specific business and legal requirements.Note for SAP S/4HANA Private Cloud and ECC environments:In SAP S/4HANA Private Cloud and SAP ECC environments, the same extensibility approach is available. However, in these systems, the BAdI implementation must be carried out for EDOC_ADAPTOR instead of EDOC_ADAPTOR_CLOUD.What’s New?GIB has published a legal requirement for invoices issued under the Construction Rebar Tracking System, which impacts certain companies starting from 21st November 2025. In this blog, we aim to address this requirement by building on the learnings from the previous blog highlighted in the background.What are the technical specifications of the requirement?Currently, the system does not automatically determine whether a billing or finance document is related to the Construction Rebar Tracking System. Customers must explicitly indicate that the invoice belongs to a Construction Rebar Tracking System and provide the required values.As part of the legal requirements published by the authorities, the following new Profile IDs must be used in the UBL (Universal Business Language, an ISO standard XML) representation:IDIS – for eInvoice ScenariosIDISIRSALIYE – for eDespatch scenarioseInvoiceProfileID for IDIS ScenarioFor IDIS-relevant invoices, the ProfileID in the UBL-TR XML will be set to IDIS.Cardinality: 1 (Mandatory)This value determines that the invoice belongs to the IDIS scenarioThe solution will automatically populate this value for applicableShipment Number (Sevkiyat Numarası) at Header Level:Mapped to: Invoice/AccountingSupplierParty/Party/PartyIdentificationSE-<number> with schemeID as SEVKIYATINO – This would carry the shipment number prefixed with SE. The total number of characters is 10.Example: SE-1345840IssueDate should be filled with the investment certificate date in DD/MM/YYYY formatTag Number (Etiket Numarası) at Item Level:Invoice/InvoiceLine/Item/AdditionalItemIdentification/ID should be filled with tag number generated within the scope of IDIS (Rebar Monitoring System). This number is a 9-character alphanumeric value, where the first 2 characters are letters followed by 7 numeric digits. SchemeID should be ETIKETNO.Example: CV0152457eDespatchProfileID for IDISIRSALIYE ScenarioFor IDISIRSALIYE-relevant invoices, the ProfileID in the UBL-TR XML will be set to IDISIRSALIYE.Cardinality: 1 (Mandatory)This value determines that the invoice belongs to the IDISIRSALIYE scenarioThe solution will automatically populate this value for applicableShipment Number (Sevkiyat Numarası) at Header Level:Mapped to: /DespatchAdvice/DespatchSupplierParty/Party/PartyIdentificationSE-<number> with schemeID as SEVKIYATINO – This would carry the shipment number prefixed with SE. The total number of characters is 10.Example: SE-1345840IssueDate should be filled with the investment certificate date in DD/MM/YYYY formatTag Number (Etiket Numarası) at Item Level:/DespatchAdvice/DespatchLine/Item/AdditionalItemIdentification/ID should be filled with tag number generated within the scope of IDIS (Rebar Monitoring System). This number is a 9-character alphanumeric value, where the first 2 characters are letters followed by 7 numeric digits. SchemeID should be ETIKETNO.Example: CV0152457Result:When you display the XML file of the electronic document in the eDocument Cockpit (EDOC_COCKPIT) corresponding to the above invoicing scenario, you will see that the mentioned tags are populated accordingly. Please note that any error handling and troubleshooting will depend on the actual submission of this document to the authorized service provider.Conclusion:With recent enhancements to the Türkiye Document and Reporting Compliance solution, SAP has made it significantly easier to tailor electronic document outputs.This improvement gives you more flexibility and helps ensure compliance with Türkiye’s legal requirements. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
