Greece extends myDATA e-invoicing to all businesses

Greece's myDATA e-invoicing mandate now covers all businesses as of Nov 2, 2026. See what EDI teams must map and test before Jan 31, 2027.

Share

On 2 November 2026, Greece's Phase 2 e-invoicing mandate went live, extending mandatory structured B2B e-invoicing through the myDATA platform to every remaining Greek business. The rule was pushed back from an original 1 October 2026 start by AADE Decision A.1197/2026, and it closes a gap that previously applied only to large taxpayers. If you run EDI or B2B integration for a company with Greek suppliers, a Greek subsidiary, or Greek carriers on your transport network, this is the deadline you didn't have on your radar in Q3, and you now have until 31 January 2027 to get it right.

What AADE actually changed on 2 November

The postponement applies to businesses that reported annual gross revenue of up to EUR 1 million, based on the tax return for the fiscal year that began in 2023, with the start date postponed from October 1, 2026 to November 2, 2026. That's the group that matters for supply chain teams: the mid-size manufacturers, distributors, 3PLs, and regional carriers you've probably been exchanging paper or PDF invoices with for years, assuming EDI compliance wasn't their problem. It is now. Phase 1, covering 2023 gross revenue above EUR 1 million, started on 2 March 2026; Phase 2, covering all other entities, starts on 2 November 2026 under Joint Decision A.1197/2026, with parallel use to 31 January 2027.

The dates that actually matter

AADE has moved this timeline twice already, so treat every date below as the current version, not a prediction.

DateWhat happens
2 March 2026Phase 1 live for businesses with 2023 revenue above €1 million
30 September 2026AADE formally postpones Phase 2 via Decision A.1197/2026
2 November 2026Phase 2 live for all remaining businesses
2 November 2026 – 31 January 2027Transition window: ERP, manual, or myDATA special-form issuance still allowed in parallel
31 January 2027Transition period ends
1 February 2027Exclusive issuance through a certified provider or AADE's free tools required

2 November 2026 marks mandatory application begins, with a gradual implementation period running to 31 January 2027, after which exclusive use of accredited providers or AADE applications becomes mandatory. One wrinkle worth flagging: businesses that skip the transition entirely and issue only through AADE's own apps from day one don't need to file anything extra. The declaration takes an effective date of 2 November 2026, and you don't need to file it if you issue exclusively through timologio or myDATAapp from 2 November and don't use the transition period at all.

Why this isn't just another XML mapping job

If you've already built EDIFACT INVOIC or X12 810 flows, you know the drill: format conversion, maybe a VAN hop, a 997 or CONTRL acknowledgment, done. myDATA doesn't work that way. myDATA operates on a Continuous Transaction Controls clearance model, where invoices must be transmitted and validated by AADE before they become fiscally valid, unlike the post-audit regimes some EDI teams are used to. For invoices issued by certified e-invoicing providers, submission is real-time: the XML must reach myDATA within seconds of invoice issuance, before the document is delivered to the buyer.

That changes your error-handling model. A rejected myDATA submission doesn't sit in a queue for next-day reconciliation, it blocks the invoice from being legally valid at all. A MARK identifier, the unique numerical reference assigned by myDATA upon successful clearance, must be generated in a structured electronic format compliant with EN 16931, validated in real time by AADE, and carry an official MARK identifier and QR code. There's also a subtlety most EDI veterans miss: what gets transmitted to myDATA is a summary of tax-relevant data, not the full invoice content, since AADE only receives the structured tax data it needs for real-time fiscal oversight. Your mapping logic needs to split cleanly between what goes to myDATA and what stays in the commercial document sent to the buyer.

Three compliant paths, and only one keeps your ERP in the loop

You have options for how to route Greek invoices, but the window for the easiest one is closing. Greece's rules don't technically require a certified provider; there are three compliant paths: a certified e-invoicing service provider, AADE's free Timologio application, or direct integration with the myDATA REST API. After 1 February 2027, direct ERP-to-myDATA transmission without going through one of those channels is no longer an option during the transition.

  • Confirm which revenue bracket your Greek entity or trading partner falls into, since that determines whether they're already in Phase 1 or just entered Phase 2
  • Decide whether you're routing through a certified provider, AADE's Timologio/myDATAapp, or a direct REST API integration against the v2.0.2 schema
  • Map your outbound EDI invoice fields (810, INVOIC) to the EN 16931 semantic model, not just a reformatted copy of your existing structure
  • Build synchronous error handling for MARK rejections, since there's no 997-style asynchronous acknowledgment pattern here
  • File your Declaration of Start of Electronic Issuance if you want to use the transition window at all, with an effective date no later than 2 November 2026

Where this leaves freight and carrier invoicing

This mandate doesn't carve out an exception for transport documents. Greek carriers and 3PLs issuing freight invoices fall under the same Phase 2 scope, which means any TMS or multi-carrier platform pulling invoice data from Greek hauliers now has a compliance dependency, not just a data-quality one. Platforms like Cargoson, alongside Transporeon, Descartes, and Alpega, increasingly sit at the point where carrier invoice data has to pass cleanly into national clearance systems like myDATA, so a messy carrier integration is no longer just an operational headache, it's a tax-compliance risk. On the provider side, EDICOM has already secured full AADE and GSIS accreditation for Greek B2B, B2G, and B2C e-invoicing, and you'll want to check whether your existing EDI or VAN provider, whether that's SPS Commerce, TrueCommerce, or Cleo, has done the same before you build anything in-house.

How Greece compares to the rest of the EU patchwork

Greece's real-time clearance step is stricter than some of its EU peers still running post-audit models, but it's consistent with where the bloc is heading. VAT in the Digital Age is one of the most significant regulation changes to EU VAT in recent years, with changes effective 12 March 2025 and further rules coming into effect in 2030. The next derogation-driven deadline to watch is Romania's, where the Council derogation expires 31 December 2026 unless ViDA applies earlier, a window valid from January 1, 2024 until December 31, 2026. After that, member states have until 30 June 2030 to integrate ViDA's e-invoicing and digital reporting provisions into national legislation, so expect a steady drip of country-specific clearance mandates between now and then rather than one clean EU-wide cutover.

If you have any Greek counterpart in your supplier or carrier base, don't wait for the 31 January deadline to start testing. Pull your AP/AR team into a room with whoever owns your EDI mapping layer this week, confirm which revenue bracket applies, and get a MARK-handling test running against the sandbox before the transition window closes.