As the EV charging sector grows rapidly, compliance obligations on the EPDK and GİB side deepen as well. One of the most critical items for charging network operators is the EŞÜ report that must be submitted to GİB every period. In this article we explain what the report is, how it is prepared, and how we automate the process with Echargo.
What is the EŞÜ report?
The EŞÜ (Electric Charging Unit) report is an electronic declaration through which companies holding an EPDK charging network operator license report the revenue arising from services delivered via EV charging stations to the Turkish Revenue Administration (GİB). Each charging transaction is reported periodically with fields such as device serial number, license plate, service quantity (kWh), and total amount.
The EŞÜ report is submitted entirely electronically over the e-Archive infrastructure, signed with an e-Seal. Manual tracking creates both operational burden and risk of error.
What do I need to do to submit a report?
Since reports are submitted electronically, you can build the integration yourself or get help from an integrator. In either case, the report content (EŞÜ XML) must first be prepared correctly. Once the device serial number and the EKS (Electronic Registration System) application/registration processes are complete, the prepared content can be submitted to GİB.
I don’t have the technical infrastructure — how do I report?
Echargo offers an end-to-end solution that lets charging network operators submit their reports securely. Once the device serial number and EKS application/registration are complete, Echargo CPMS establishes a fully automated integration with GİB — just like the notifications sent to EPDK. As long as operators remain in the ecosystem, each period’s report is submitted without manual effort.
- Charging transactions are collected in Echargo CPMS and converted to the EŞÜ format periodically.
- e-Seal signing can be done automatically via an integrator or manually with the Echargo signing tool.
- Submission to GİB is managed from a single point in the same operational flow as EPDK notifications.
- Erroneous/incomplete records are caught in a validation layer before submission.
I’m a developer — I just want to submit notifications
For colleagues who only want to handle the integration, we published an open-source tool that signs the EŞÜ report with an e-Seal and submits it to GİB: gib-signer. You can download the code, adapt it to your needs, and submit your notifications.
<?xml version="1.0" encoding="utf-8"?>
<eArsivRaporu
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns="http://earsiv.efatura.gov.tr">
<baslik>
<versiyon>1.0</versiyon>
<mukellef><vkn>1234567890</vkn></mukellef>
<donemBaslangicTarihi>2024-09-01</donemBaslangicTarihi>
<donemBitisTarihi>2024-09-30</donemBitisTarihi>
<bolumNo>1</bolumNo>
</baslik>
<esuRapor>
<UUID>dbaacd1f-400d-4634-b628-3606ef6b91b9</UUID>
<plakaNo>06ABC123</plakaNo>
<hizmetMiktari unitCode="kWh">7.224</hizmetMiktari>
<toplamTutar>57.07</toplamTutar>
<paraBirimi>TRY</paraBirimi>
</esuRapor>
</eArsivRaporu># 1) İmzalı raporu SOAP mesajına dönüştür (e-Mühür takılıyken)
java -jar gibsigner.jar "convert" "123456" "imzaliesurapor.xml" "soap_message_to_send.xml"
# 2) Hazırlanan SOAP mesajını GİB servisine gönder
java -jar gibsigner.jar "send" "soap_message_to_send.xml"Let’s automate your EŞÜ reporting
Companies that haven’t started reporting or face issues can write to [email protected]. With Echargo CPMS we remove the periodic reporting burden entirely.
Get in touch →
