Operating a charging network in Türkiye creates four separate regulatory obligations, and each one has its own authority, its own format and its own deadline. The compliance package takes all four. Your system keeps doing what it already does — it sends its own data in standard form, and the regulatory logic stays on our side.
Every charging transaction is reported to EPDK in real time, as it happens. Completed sales are reported to GİB periodically, and where the invoice is issued later, the sale is additionally flagged at the moment it happens. And an invoice is issued to the end customer for every payment. Miss one and the others do not cover for it — they are separate duties to separate authorities.
EPDK — real time, on every charging event
GİB device registration — once, at commissioning
GİB sales report — periodic, plus an instant flag at the sale
e-Invoice — on every payment
Where the work sits
The regulatory logic stays with us
This is the point of the package. Not a single line of Türkiye-specific code enters your software. You are not asked to learn the notification families EPDK expects, the identity fields GİB wants on a device, or how a sales report has to be signed. Your platform sends what it already holds, in the standard form it already speaks, and everything between that and the authority is ours.
No Türkiye-specific code in your platform
No regulatory formats to implement
No separate filing calendar to track
Changes in the rules are absorbed on our side
What we need from you
A short list, and most of it you already have
A few things genuinely have to come from your side, because only you hold them. The official station and socket numbers issued in Türkiye, so a transaction can be matched to the right point. The serial number, brand and model of each device, because that is what a device registration is. The plate number where your system captures it. And, if you operate mobile stations, which provinces they serve. Everything else is derived on our side.
Official station and socket numbers
Device serial number, brand and model
Plate number, where you hold it
Mobile stations and the provinces they serve
The network identifier pointing at the right operator
Who answers for it
The liable party is the network operator
It is worth being precise here, because it decides how the commercial side is set up. The sales report and the invoice are technically prepared by the e-document integrator, but the party liable before the authority is in every case the charging network operator. Invoicing is therefore not a protocol question; it follows from who collects the payment. Where an occupancy fee applies, it is invoiced separately, and the invoice QR code has to be shown on the terminal.
Operator is liable, integrator prepares
Invoicing follows whoever collects payment
Occupancy fee invoiced separately
Invoice QR code shown on the terminal
Bring your network to Türkiye
If you run a charging network management system and Türkiye is on your roadmap, the regulatory side does not have to become a development project. Tell us how your platform is built and which markets it already serves, and we will tell you exactly what connecting to the compliance package would involve — including the parts that depend on your commercial structure rather than on technology.
Do we have to change our own software to operate in Türkiye?
No Türkiye-specific regulatory code has to enter your platform. The obligations, formats and deadlines are carried by the compliance package. What your side sends is data you already hold — station and socket numbers, device serial, brand and model, and the plate number where you capture it — in the standard form your system already speaks.
What exactly are the four obligations?
Every charging transaction is reported to EPDK in real time. Completed sales are reported to GİB periodically, with an additional instant notification at the moment of sale where the invoice is issued later. And an invoice is issued to the end customer for every payment.
Who is legally responsible — us or the integrator?
The e-document integrator technically prepares the sales report and the invoice, but the party liable before the authority is always the charging network operator. This matters when the commercial structure is being set up, because it determines who invoices the driver and therefore who answers for it.
We operate mobile charging stations. Does that change anything?
Yes, and it has to be declared. A mobile station is reported as mobile, together with the provinces it serves. That is one of the few items with no standard equivalent, so it is carried explicitly rather than inferred.
How long does connecting take?
That depends on your platform and on how your commercial side is arranged — particularly who collects payment and whether you work with one charging network or several. We would rather look at your setup and give you a real answer than publish a number that turns out not to apply to you.
