Home / E-Invoicing / Greece
Greece · myDATA · Live for large enterprises

E-Invoicing in Greece

Greece's B2B mandate is already running. Large enterprises went live in March 2026; everyone else follows from October 2026.

Talk to us about Greece
In short

E-invoicing in Greece requires domestic B2B invoices to be issued as structured electronic documents through the myDATA platform, using EN 16931 via myDATA. Greece's B2B e-invoicing mandate went live for large enterprises on 2 March 2026 — resident companies with revenues above EUR 1 million in 2023 — with a gradual implementation window running from 2 March to 3 May 2026. All other resident taxpayers are mandated in phase 2 from 1 October 2026, with an adjustment period to 31 December 2026 during which existing accounting or ERP software may continue to run alongside. The legal foundation is Council Implementing Decision (EU) 2025/502, published on 25 February 2025, authorising Greece to derogate from Articles 218 and 232 of Directive 2006/112/EC, running from 1 July 2025 until 31 December 2027. Invoices must follow EN 16931 and be transmitted through the myDATA platform, the timologio application, or certified service providers. Whatever the local mechanism, the invoice still has to come out of your ERP correctly — and in our experience that is where projects actually succeed or fail. ROSTAN builds the integration into Oracle EBS and Fusion Receivables so compliance is generated from the invoice the business already raises.

The deadline
Already live, phase 2 in October

Dates reported from published guidance. Confirm your own obligation with your tax adviser — ROSTAN implements the ERP integration and does not provide tax or legal advice.

What Greece requires

Greece's B2B e-invoicing mandate went live for large enterprises on 2 March 2026 — resident companies with revenues above EUR 1 million in 2023 — with a gradual implementation window running from 2 March to 3 May 2026. All other resident taxpayers are mandated in phase 2 from 1 October 2026, with an adjustment period to 31 December 2026 during which existing accounting or ERP software may continue to run alongside. The legal foundation is Council Implementing Decision (EU) 2025/502, published on 25 February 2025, authorising Greece to derogate from Articles 218 and 232 of Directive 2006/112/EC, running from 1 July 2025 until 31 December 2027. Invoices must follow EN 16931 and be transmitted through the myDATA platform, the timologio application, or certified service providers.

EDICOM — Greece mandatory B2B e-invoicing via myDATA
What makes Greece different

The details that change the integration

The threshold looks backwards

Phase 1 captures resident companies with revenues above EUR 1 million in 2023 — a historic year, not the current one. Your obligation date was fixed by a figure already in your filed accounts.

myDATA is the centre of gravity

Greece already ran myDATA for digital tax reporting, so e-invoicing extends an existing platform rather than introducing a new one. If your myDATA submissions are already imperfect, e-invoicing will expose it.

Two adjustment windows, not two deadlines

Phase 1 had a run-in from 2 March to 3 May 2026; phase 2 has one from 1 October to 31 December 2026, during which existing software can run alongside. Those windows are for transition, not for starting.

The derogation has an end date

Greece operates under an EU derogation running to 31 December 2027, after which ViDA changes the legal basis. Build for the requirement, not for the temporary permission that currently underpins it.

The portal is rarely the problem

Statutory e-invoicing is the single largest workload on our own Oracle service desk. These are the causes we see behind rejections, wherever the mandate is.

Tax or product master data that does not match what the schema expects — the most common single cause.
Party identifiers (VAT numbers, registration IDs, addresses) missing or formatted for a human rather than a validator.
A payload that validates in test and fails in production because a real invoice carries a case the sample never did.
No controlled retry path — a rejected invoice is not a valid invoice, and manual re-keying does not scale.
Nobody owning reconciliation: invoices issued in the ERP but never confirmed as accepted downstream.
The receiving side left out of scope, so supplier invoices arrive in a format Accounts Payable cannot process.
FAQ

E-invoicing in Greece

When did B2B e-invoicing become mandatory in Greece?
What is myDATA and how does it relate to e-invoicing?
How was our phase determined?
How does this work with Oracle EBS or Fusion?
Free · No obligation

Get Greece e-invoicing working in your ERP

Tell us which entities are in scope and what you run — Oracle EBS, Fusion or something else — and we will tell you what the integration actually involves for your setup.

A named Oracle consultant replies — not a call-centre
We will tell you if you do not need us
Your details are never sold or shared

Your data is safe. We never share or sell your information.

Back to Top
ROSTAN Support
Online · Typically replies instantly
WhatsApp Chat directly, fastest response Call Us +91-9810958952 Email Us info@rostantechnologies.com Send a Message Fill the contact form
Chat with us