Greek e-invoicing and myDATA
An engineer's overview of Greek electronic invoicing: what myDATA actually is, how the digital delivery note works, where B2G differs, and which parts of the problem these tools currently help with.
This site is independent and is not affiliated with AADE, GSIS or any tax administration. eDocument Tools performs local technical validation of Greek myDATA documents against the pinned AADE myDATA v2.0.2 schema package — the production baseline since 2026-09-10 — covering all 20 structures the official package declares, including the 8 digital goods movement structures.
Three things are never checked here. AADE acceptance, because this site never contacts myDATA and most AADE rules depend on platform state. Peppol BIS Billing conformance, which Greek B2G requires and which is a different specification with different artefacts. And whether you are permitted to transmit, which is a matter of registration and licensing, not of file structure. A clean result is a statement about your XML and nothing else.
What myDATA is, and what it is not
myDATA — Ηλεκτρονικά Βιβλία ΑΑΔΕ — is the electronic books platform run by the Independent Authority for Public Revenue. Businesses transmit the data of the documents they issue and receive, and AADE maintains the books that result.
Three things get collapsed constantly, and this site keeps them apart:
- The legally issued electronic invoice — the tax document your counterparty receives.
- The myDATA transmission representation — the XML sent to and returned by the platform. An
InvoicesDocis this. Calling it "the Greek invoice" is wrong: it is an envelope carrying the data myDATA requires. - The detailed myDATA representation — a downloadable form a provider may publish, referenced from a document by
downloadingInvoiceUrl. AADE defines it with its own, stricter schema.
Document families
AADE's document type list runs to 55 codes. The families worth knowing before you look at any Greek XML:
- 1.x and 2.x — sales invoices and service invoices, including intra-Community and third-country variants, and sale on behalf of third parties.
- 3.x — Τίτλος Κτήσης, title of acquisition, used when the issuer is not obliged to issue or has refused to.
- 5.x — credit invoices, correlated and non-correlated. First-class documents here, not an afterthought.
- 9.x and 10.x — delivery notes and quantity receipt notes: the goods movement family.
- 11.x — retail and B2C documents. There is no Greek equivalent of an e-archive regime; retail documents are simply a myDATA document family.
- 13.x to 17.x — recipient-side documents, contract and payment expense records, and entity adjustment entries.
The digital delivery note
Greece's Ψηφιακό Δελτίο Αποστολής tracks goods in real time from issuance of a movement document to final receipt, with the issuer, the carrier and the recipient each reporting events. Version 2.0.2 is largely a goods-movement release: it adds a delivery return confirmation and a receiving note cancellation for providers, and its delivery outcome is a three-valued choice of full, partial or none.
The validator checks these structures against their official schemas: register transfer, confirm delivery outcome, confirm delivery return, reject delivery note, delivery status responses and the group QR structures. Where a document declares a delivery status, a move purpose or a vehicle, those are shown as declared values. Whether the goods moved is not something a file can establish.
B2G is a different regime
Greek public-sector e-invoicing is mandatory above €2 500 and runs on Peppol, with the National Interoperability Centre operating as the Greek Peppol Authority and the central hub for distribution to public bodies. The format is EN 16931 / Peppol BIS Billing 3.0, and suppliers transmit through certified Peppol Access Points. Invoice data still reach myDATA.
Three verdicts, never one:
- myDATA schema conformant — the structure matches an AADE schema.
- Peppol BIS Billing valid — a different specification, different artefacts, not offered here.
- Greek B2G accepted — a statement only the receiving authority can make.
The mandatory timeline
Decision A.1044/2026, published 17 February 2026, set two phases: businesses with gross revenue above €1 000 000 for financial year 2023 from 2 March 2026, and all remaining businesses from 1 October 2026.
Keep that separate from the platform version. myDATA v2.0.2 became the production baseline on 2026-09-10. One is an obligation to issue electronically; the other is the version of the reporting interface.
What this site can check today
The myDATA validator checks a document against the official AADE myDATA v2.0.2 schema package, committed here with its SHA-256 and served from this origin, so a result cannot change because a website changed.
The structure is identified from its root element and namespace, never from the file name. Note that the namespace still reads v1.0 even in the v2.0.2 package: AADE versions the schemas without versioning the namespace, so the release is the contract applied and is never inferred from your document.
Retention is not addressed here at all. The taxpayer's own duty to preserve documents, a provider's obligations, and myDATA data availability are three separate responsibilities, and this site is not an archive for any of them.
Frequently asked questions
What is myDATA?
myDATA — Ηλεκτρονικά Βιβλία ΑΑΔΕ — is the Greek tax authority’s electronic books platform. Businesses transmit the data of their issued and received documents to AADE, which maintains the resulting books. It is a reporting and transmission system, so a myDATA payload is not itself the invoice your counterparty receives — it is the structure carrying the data AADE requires about that invoice.
Do these tools check Greek conformance?
Yes, technically and locally, and within a boundary worth stating precisely. This site validates a myDATA document against the official AADE v2.0.2 XML Schema package, pinned and checksummed, entirely inside your browser. It does not check AADE business rules, because nearly all of them depend on platform state a browser cannot see, and it never contacts AADE. A schema pass is not acceptance by myDATA.
When did Greek e-invoicing become mandatory?
Decision A.1044/2026 set two phases: businesses with gross revenue above €1 000 000 for financial year 2023 from 2 March 2026, and all remaining businesses from 1 October 2026. Separately, myDATA v2.0.2 became the production platform baseline on 10 September 2026. Those are different things — an obligation to issue electronically, and the version of the reporting interface.
What is the digital delivery note?
The Ψηφιακό Δελτίο Αποστολής tracks goods in real time from the moment a movement document is issued to final receipt. Issuer, carrier and recipient each report events: movement start or transhipment, delivery outcome, or rejection. Version 2.0.2 extends this area notably, including a delivery return confirmation and partial delivery outcomes. This site validates those structures against the official schemas; it cannot tell you whether a movement actually happened.
Is eDocument Tools an electronic invoicing provider?
No. A Πάροχος Ηλεκτρονικής Τιμολόγησης is licensed by AADE under a suitability framework, operates its own transmission interface, and applies a provider signature. This site is a viewer and a validator. It cannot issue, transmit, clear, store or archive anything, and being able to check a structure locally is not the same as being permitted to transmit it.
Does a myDATA result say anything about Greek B2G invoices?
No. Greek public-sector e-invoicing is a separate regime running on Peppol BIS Billing 3.0, with the National Interoperability Centre acting as the Greek Peppol Authority and central hub. Three verdicts must never be collapsed into one: myDATA schema conformance, Peppol BIS conformance, and acceptance by a Greek public body. This site currently reports only the first.
Does this site store my Greek documents?
No. The browser tools never upload your file, and nothing is retained — a document sent to the Validation API is held for that request only. That also means this site is not an archiving solution, and it does not discharge any retention obligation — the taxpayer’s own duty to preserve issued and received documents, a provider’s obligations, and myDATA data availability are three separate responsibilities.
Why is the Greece module not fully published yet?
Because it has no Greek. This project does not promote a country module until its own language is published with real content, on the view that a page about Greek obligations written only in English is a doorway page rather than something useful to the person who has to comply. The myDATA validator itself is fully built and available today.