E-invoicing in Greece in short
Every income and expense document of a Greek business is transmitted to myDATA, the electronic books of the Independent Authority for Public Revenue (AADE), which gives it a registration number, the MARK. Until now a business could send the data from its own software (ERP) or type it into a form. Under decision A.1128/2025 (article 14 of Law 4308/2014), invoices must now be issued electronically, through a certified e-invoicing provider or AADE's free timologio and myDATAapp applications, which pass each one to myDATA in real time. This covers sales to Greek businesses, sales to businesses outside the EU and invoices for public contracts and other spending of the general government.
Businesses with gross revenue above €1,000,000 in tax year 2023 were the first: from 2 March 2026, with their old software or the form still allowed beside it until 3 May 2026 (decision A.1044/2026 moved the start from 2 February). All other businesses follow from 2 November 2026, with the same overlap until 31 January 2027 (decision A.1197/2026). Since 2 February 2026 a business has to accept an e-invoice it receives. The provider makes the invoice available to the buyer at a link, also printed as a QR code, as a PDF, in the detailed myDATA form and in EN 16931.
A Greek supplier's Peppol BIS invoice, as public bodies receive them, follows Greek rules of its own: the invoice number in six parts, the supplier's registered name, the tax numbers of both sides as electronic addresses, and the MARK myDATA gave it.
How to check a Greek invoice
- Open the validator with the myDATA profile. An InvoicesDoc opened or pasted picks it on its own, by its root element and namespace.
- Paste the XML or drop the file, a document your software sends or the detailed form a provider gave you, then press Validate.
- Each finding names AADE's error code; click it for the rule and what usually causes it. For an invoice to a public body, pick Peppol BIS 3.0 Invoice, which runs the Greek rules.
What is checked
First AADE's schema for myDATA 2.0.2 with its code lists, then our rules, written from AADE's REST API documentation of September 2026 and its workbook of classification combinations, with AADE's error codes and English wording: the summary against the lines, the gross value from net value and taxes (MYDATA-203), the VAT of the lines against the total (MYDATA-209), the check digit of each Greek tax number, the ΑΦΜ (MYDATA-202), the countries each document type needs (intra-Community and third country sales and purchases), withholding, fees and stamp duty against their percentage category, taxes either per line or per document, and line numbers.
Then the E3 classifications: on every line or none, their sum against each line's net value, the category and type combinations AADE allows for each document type (MYDATA-313) and the summary's totals (MYDATA-311). Rules marked XV-GR cover what the field descriptions require without an error code of their own, such as the exemption reason of a line without VAT (XV-GR-15).
What needs myDATA is not checked: whether a tax number belongs to an active business, the sender's authorisation, duplicates and the documents a correction refers to, and the issue date against the day of sending. For Peppol, OpenPeppol's Greek rules run with Peppol BIS, among them the MARK (GR-R-004-1).
Profiles to check with
- myDATA 2.0.2: The document Greek businesses send to AADE's myDATA e-books for every invoice, receipt and delivery note, and the detailed form a buyer downloads from an e-invoicing provider. Validate
- Peppol BIS Billing 3.0 Invoice: A Peppol invoice checked the way an access point does: UBL 2.1 schema, EN 16931 rules and the Peppol BIS Billing 3.0 rules. Validate
- Peppol BIS Billing 3.0 Credit Note: A Peppol credit note checked against the UBL 2.1 schema, the EN 16931 rules and the Peppol BIS Billing 3.0 rules. Validate
Rules invoices break most
Each one has a page with what it checks, its test and, for many, how to fix it
MYDATA-203: Gross Value doesn't match with sum of net value plus taxes: totalGrossValue …, net value plus VAT, fees, stamp duty and other taxes less withholdings and deduct...MYDATA-209: The sum of vat amount of the invoice lines doesn't match with total vat amount of the invoice: totalVatAmount …, lines ….MYDATA-202: Invalid Greek VAT number: … (the …'s ΑΦΜ) is not nine digits with a right check digit.MYDATA-313: Classification type … forbidden for Classification category … combined with invoice type … (invoice line …); allowed: ….MYDATA-311: Classification with type and category … not found in invoice summary: the summary's income classifications sum every type and category of the lines.XV-GR-15: Invoice line: …. A line without VAT (vatCategory 7, 0%) gives the reason of the exemption in vatExemptionCategory.GR-R-004-1: When Supplier is Greek, there must be one MARK Number
Questions
Is the invoice uploaded?
No. The schema check and the rules both run in your browser. Only the API and URL monitors validate on our servers.
Does a valid result mean myDATA will accept the document?
It means the document passes the schema and the myDATA checks that need only the file. myDATA also checks the tax numbers against AADE's registry, who sends the document, duplicates and the documents a correction refers to, so it can still reject the document for something a file alone doesn't show.
Can I check the detailed form my supplier's provider gave me?
Yes. The detailed myDATA form (InvoicesDoc_detailed.xsd) is the same document without the classifications, so it passes the same schema and rules.
Are these AADE's own rules?
They are our implementation of the errors AADE documents for myDATA, with its codes and wording, and of its classification combinations. Providers and myDATA run their own.
Can I check invoices from code?
Yes: the API and the command-line client with --schema mydata-2.0.2, or --schema auto for a folder of mixed files.
Official sources
- AADE: mandatory electronic invoicing, deadlines and decisions
- AADE: decision A.1128/2025 on mandatory e-invoicing (in Greek)
- AADE: decision A.1044/2026, the first period moved (in Greek)
- AADE: decision A.1197/2026, the second period moved (in Greek)
- AADE: myDATA technical specifications and XSDs
Other countries
- French e-invoice validator
- E-invoicing in Germany: XRechnung and ZUGFeRD
- Belgian e-invoice validator: Peppol BIS
- Dutch e-invoice validator: SI-UBL 2.0 and NLCIUS
- KSeF invoice validator: FA(3)
- Danish e-invoice validator: OIOUBL 2.1
- E-invoicing in Norway: EHF invoice validator
- Swedish e-invoice validator: Peppol BIS
- Finnish e-invoice validator: Finvoice
- Austrian e-invoice validator for e-Rechnung.gv.at
- E-invoicing in the Czech Republic: ISDOC validator
- Croatian eRačun validator
- RO e-Factura validator
- FatturaPA validator
- Spanish e-invoice validator
- Portuguese e-invoice validator: CIUS-PT
- ZATCA e-invoice validator (FATOORA)
- UAE e-invoice validator (PINT AE)
- InvoiceNow validator (PINT SG)
- JP PINT validator
- Australian e-invoice validator (PINT A-NZ)
- Malaysian e-invoice validator (MyInvois)
- Brazilian NF-e validator (SEFAZ rules)
- Mexican CFDI 4.0 validator (SAT validations)