Mandatory E‑invoicing in Greece 2026: Legal & Compliance Checklist for Businesses

Greece’s transition to mandatory e‑invoicing is now under way, and every business operating in the country, whether domestically established or invoicing Greek public‑sector entities from abroad, faces a concrete set of legal, contractual and systems‑level obligations that must be addressed in 2026. The phased rollout, which began for the largest taxpayers in early 2026 and extends through transitional windows into May 2026, requires finance directors, general counsel and compliance teams to act immediately on contracts, VAT reporting processes and IT infrastructure.

This article delivers a lawyer‑authored e‑invoicing Greece compliance checklist: a single reference covering who is in scope, the exact deadlines, myDATA transmission rules, the contract clauses that need amending, record‑keeping requirements, penalties for non‑compliance, and a practical 90‑day implementation playbook.

Quick‑Take Legal Checklist: 10 Steps for E‑Invoice Compliance

Before diving into the detail, here is the core e‑invoicing legal checklist that legal and finance teams should work through. Each item is expanded in the sections that follow.

1. Confirm scope. Determine whether your entity falls within the first phase (large taxpayers) or a later phase, and whether you issue B2B invoices, B2G invoices, or both.
2. Map the timeline. Pin down which e‑invoicing deadline 2026 applies to your entity and mark your transitional compliance window.
3. Register with or appoint a certified e‑invoicing service provider. Check the AADE‑published list of approved providers and execute a service agreement.
4. Amend sales contracts and T&Cs. Insert clauses covering electronic invoice format, acceptance mechanics, and transmission obligations via myDATA.
5. Update supplier agreements. Allocate liability for failed transmissions, duplicate invoices and reconciliation disputes.
6. Align VAT reporting. Ensure that e‑invoice data feeding into myDATA reconciles with periodic VAT returns to prevent mismatches and audit triggers.
7. Establish retention and audit‑trail protocols. Define record‑keeping periods, storage formats and internal access controls.
8. Implement internal controls. Set up segregation of duties, approval workflows and exception‑handling procedures for rejected or failed invoices.
9. Test ERP‑to‑myDATA integration. Run end‑to‑end production tests and document results before the enforcement date.
10. Obtain board or management sign‑off. Secure formal approval for the compliance programme, budget allocation and any necessary delegated authorities.

The central question this article answers is straightforward: Does my business need to change its invoicing, contracts or reporting now to avoid VAT mismatches and penalties? For the vast majority of Greek‑established businesses and foreign entities invoicing the Greek public sector, the answer is yes, and the window for action is narrow.

Who Must Comply with Mandatory E‑Invoicing in Greece?

Scope Breakdown: Greek Businesses, Non‑Resident Suppliers, B2B and B2G

The mandatory e‑invoicing regime covers both B2B and B2G transactions. All entities that are registered for VAT in Greece and issue tax documents (invoices, credit notes, debit notes) to other Greek‑registered businesses must transmit those documents electronically through the myDATA infrastructure operated by AADE, Greece’s Independent Authority for Public Revenue. B2B e‑invoicing Greece obligations apply regardless of whether the recipient business has opted in, the sender bears the transmission obligation.

For B2G transactions, invoices addressed to Greek public‑sector bodies, compliance has been building since the European Directive on electronic invoicing in public procurement required EU member states to accept e‑invoices in the EN16931 format. Greece’s implementation now extends the obligation beyond mere acceptance: suppliers to the public sector must issue invoices electronically through certified channels. Non‑resident entities that supply Greek public‑sector contracting authorities should verify whether their invoicing arrangements satisfy the EN16931/Peppol requirements outlined by the European Commission and GOV.GR.

Thresholds and Phased Application

Greece has adopted a phased approach, with the largest taxpayers required to comply first. Industry advisories, including guidance published by Deloitte and corroborated by VATCalc, indicate that AADE has applied a turnover‑based threshold to determine phase sequencing, with entities classified as “large taxpayers” (broadly, those with annual turnover above approximately €1 million) placed in the earliest compliance cohort. Smaller businesses are expected to follow in subsequent phases extending through 2026 and potentially into 2027.

It is essential to verify the precise classification criteria against the latest AADE notices, as the authority has amended threshold definitions and phase assignments on more than one occasion. Businesses that sit near the boundary should err on the side of early compliance rather than risk being caught by a retrospective reclassification.

E‑Invoicing Greece: Timeline and Phased Rollout

Official Timeline

The original e‑invoicing deadline 2026 for Phase 1 entities was reported by multiple advisories as 2 February 2026. However, AADE subsequently issued a notice delaying the effective start to 2 March 2026, providing large taxpayers with an additional month to complete production testing and supplier notification. This delay was widely documented in tax advisory channels and confirmed in commentary by VATCalc and Deloitte Greece.

Transitional Windows and Enforcement Dates

Following the revised 2 March 2026 start date, AADE has signalled a soft‑launch compliance window running through approximately May 2026. During this transitional period, early indications suggest that enforcement is expected to focus on readiness and good‑faith efforts rather than immediate penalties for minor transmission errors. Industry observers expect that full enforcement, with administrative fines for non‑compliance, will commence once the transitional window closes. Businesses in later phases should not treat this grace period as a reason to delay: the systems, contracts and internal controls required take time to implement, and supplier onboarding alone can absorb weeks.

What If You Are in a Later Phase?

Even if your entity is not in the first compliance cohort, best practice is to begin preparation now. Contract amendments, ERP testing and provider selection benefit from lead time, and counterparties in earlier phases will begin requiring e‑invoice‑ready terms immediately.

Note: all dates should be verified against the latest AADE notices, which are published on the official myDATA portal. AADE has amended timelines previously, and further adjustments are possible.

myDATA, Transmission and Certified Providers

What myDATA Does

myDATA (my Digital Accounting and Tax Application) is AADE’s central digital platform for the real‑time collection of transaction data from Greek businesses. Under the mandatory e‑invoicing regime, every qualifying invoice must be transmitted to myDATA either directly through AADE’s API or via a certified e‑invoicing service provider. The data submitted feeds into AADE’s VAT reporting Greece framework, enabling the authority to cross‑reference declared turnover, input VAT claims and output VAT liabilities in near real time. Understanding how myDATA interacts with VAT filings is essential: the platform does not replace the obligation to file periodic VAT returns, but the data it holds will be used to pre‑populate and audit those returns.

Certified Service Providers and EN16931/Peppol for Public Sector

AADE publishes and periodically updates a list of certified e‑invoicing service providers authorised to transmit invoices through the myDATA infrastructure. Businesses must select a provider from this list and execute a formal service agreement that addresses data processing obligations, uptime guarantees, error‑handling protocols and liability for failed transmissions. For B2G invoices directed at Greek public‑sector entities, the EN16931 European standard applies, typically transmitted via the Peppol network. The European Commission’s guidance on eInvoicing in Greece and the GOV.GR portal for electronic invoicing to the public sector set out the technical and procedural requirements. Businesses that already invoice other EU public‑sector bodies via Peppol may find their existing infrastructure largely sufficient, but should verify Greek‑specific routing and validation rules.

Practical Steps for Finance Teams

Finance teams should run end‑to‑end transmission tests well before the enforcement date. This includes sending test invoices through the chosen certified provider, confirming successful receipt by myDATA, and reconciling the data against internal accounting records. Any discrepancies identified during testing, format errors, missing fields, rejected transmissions, must be resolved and documented. Maintaining a log of test results is both good practice and useful evidence of good faith during the transitional window.

E‑Invoicing Legal Checklist: Contracts, T&Cs and Supplier Agreements

The shift to mandatory e‑invoicing does not only affect IT systems. It has direct implications for the legal terms governing commercial relationships. Businesses should undertake a structured review of their sales contracts, general terms and conditions, and procurement agreements. This section of the e‑invoicing legal checklist sets out the key contractual changes required.

Sales Invoices and T&C Amendments

Every set of customer‑facing terms and conditions that references invoicing mechanics needs updating. At a minimum, the following elements should be addressed:

• Invoice format. Specify that invoices will be issued in the structured electronic format required by AADE (and, for B2G transactions, in EN16931/UBL or CII syntax).
• Transmission method. State that invoices will be transmitted via a certified e‑invoicing service provider through myDATA, and identify the provider by name or describe the selection process.
• Unique reference numbers. Include a clause requiring each invoice to carry the myDATA MARK (unique identification code assigned upon successful transmission) as proof of valid issuance.
• Acceptance mechanics. Define when an e‑invoice is deemed received and accepted, for example, upon successful transmission to the buyer’s myDATA account or upon the buyer’s affirmative acknowledgement within a specified number of business days.
• Electronic signature / authentication. Where Greek law or the contract previously required a wet signature, update to reflect that electronic authentication through the myDATA platform satisfies the signature requirement.

Supplier Agreements and Liability Allocation

On the procurement side, businesses should amend supplier agreements to address new risks arising from the e‑invoicing regime:

• Failed transmission liability. Allocate responsibility for invoices that are rejected by myDATA or fail to transmit due to technical errors on the supplier’s side. Specify remediation timelines and the consequences of repeated failures.
• Duplicate invoices. Include a clause requiring the supplier to implement controls preventing duplicate transmission and obligating prompt correction if duplicates occur.
• Reconciliation disputes. Establish a process for resolving discrepancies between the data held in myDATA and the buyer’s own records, including timelines for investigation, correction and escalation.
• Indemnities. Consider whether the supplier should indemnify the buyer for VAT penalties, interest or audit costs arising from the supplier’s failure to comply with electronic invoicing requirements.

Procurement and Public Sector Clauses

Entities supplying Greek public‑sector contracting authorities should ensure their procurement contracts expressly reference EN16931 compliance and Peppol transmission. Specific provisions to include are acceptance of the buyer’s designated access point, cooperation with audit and reconciliation requests from the contracting authority, and compliance with any additional data fields required by Greek public procurement regulations. Businesses already participating in cross‑border EU public procurement via Peppol should verify that Greek‑specific access points and validation rules are reflected in their existing agreements. For further guidance on structuring international business contracts, Global Law Experts maintains a dedicated practice guide.

VAT Reporting Greece: Reconciliation and Record‑Keeping Obligations

How E‑Invoices Feed VAT Records

Under the mandatory e‑invoicing regime, every invoice transmitted to myDATA automatically populates a taxpayer’s digital ledger within AADE’s systems. This ledger forms the basis for pre‑populated VAT returns and enables AADE to identify inconsistencies between declared transactions and the invoices recorded in its database. For businesses, the practical effect is that any mismatch between the data in myDATA and the figures reported on periodic VAT returns will be flagged, potentially triggering an automated audit query. Finance teams must therefore build reconciliation steps into their monthly closing processes: the e‑invoice data transmitted to myDATA should be cross‑checked against the company’s own accounting records and the draft VAT return before filing.

Retention Periods, Formats and Audit Trails

Greek tax law requires businesses to retain accounting records and supporting documentation, including invoices, for a period that generally aligns with the statute of limitations for tax assessments. Businesses should retain e‑invoices in their original structured electronic format (not merely as PDF printouts) for a minimum of five years, though longer retention is advisable where the assessment period could be extended due to ongoing audits or disputes. The audit trail should capture the full lifecycle of each invoice: creation, transmission to myDATA, receipt of the MARK confirmation code, any amendments or credit notes, and the reconciliation record linking the invoice to the relevant VAT return line.

Crosschecks to Prevent VAT Mismatches

Automated crosschecks should be implemented at three stages: (1) before transmission, to verify invoice completeness and format compliance; (2) after transmission, to confirm successful receipt and MARK assignment; and (3) at VAT return preparation, to reconcile transmitted data with internal records. Businesses operating across multiple Greek entities or with complex intercompany structures should pay particular attention to consolidation‑level reconciliation.

Penalties, Audits and Enforcement Risk

Typical Penalties for Non‑Compliance

Greek tax legislation provides for administrative fines where a taxpayer fails to issue, transmit or correctly report invoices. Penalties for failure to comply with electronic invoicing requirements can include per‑invoice fines for late or missing transmissions, percentage‑based surcharges on the undeclared VAT amount, and interest on any resulting tax underpayment. The exact penalty ranges depend on the nature and severity of the infringement, the taxpayer’s compliance history, and whether the failure is deemed intentional or negligent. AADE retains discretion to impose reduced penalties where the taxpayer demonstrates good faith and prompt remediation.

Practical Mitigation: Voluntary Disclosure and Remediation

Businesses that identify compliance gaps, whether missed transmissions, format errors or reconciliation discrepancies, should consider proactive disclosure to AADE before the authority’s own systems flag the issue. Early voluntary correction typically attracts more favourable treatment than reactive responses to audit queries. A clear internal escalation procedure, under which e‑invoice exceptions are reported to the compliance function within defined timescales, is essential. Documentation of remediation steps, including timestamped logs of corrective transmissions, should be preserved as evidence of good faith.

When to Involve Legal Counsel

Legal counsel should be engaged at the earliest opportunity when: (a) AADE issues an audit notice referencing e‑invoice discrepancies; (b) a supplier or customer disputes the validity or receipt of an e‑invoice in a manner that could affect VAT recovery; or (c) the penalty amount at stake justifies formal challenge or negotiation. Businesses operating in regulated sectors or with significant public‑sector exposure should consider retaining specialist tax litigation counsel on a standby basis during the rollout period. For businesses seeking specialist representation, the Global Law Experts Greece directory provides a list of qualified practitioners.

Internal Controls, IT and ERP Integration Checklist

Controls: Segregation of Duties, Approvals and Reconciliation

Robust internal controls are essential to maintain e‑invoice compliance over time. Segregation of duties should ensure that the person creating an invoice is not the same person authorising its transmission to myDATA. Approval workflows should be configured within the ERP or invoicing system so that no invoice is transmitted without appropriate sign‑off. Monthly reconciliation between the ERP’s invoice register, the myDATA transmission log and the VAT return working papers should be a standing item in the financial close process. Exception reports, identifying rejected, failed or unmatched invoices, should be reviewed by a designated compliance officer.

ERP‑to‑myDATA Integration: Legal Checkpoints

Before going live, legal and IT teams should jointly verify that the ERP‑to‑myDATA integration satisfies the following checkpoints: (a) data mapping from ERP invoice fields to the AADE‑specified XML schema is complete and tested; (b) the certified provider’s service‑level agreement includes uptime, error‑handling and liability provisions that align with the company’s risk tolerance; (c) change‑control procedures are in place so that any ERP update or provider change triggers a re‑validation of the transmission process; and (d) supplier onboarding procedures include verification that each supplier can receive and respond to e‑invoices through compliant channels. Greece’s broader 2026 regulatory landscape, including property law changes and migration law updates, may also affect operational planning for businesses with diversified Greek interests.

Roles and Responsibilities Matrix

90‑Day Implementation Playbook for Legal and Finance Teams

The following action plan provides a practical roadmap for businesses entering the e‑invoicing compliance process. Adjust timelines according to your entity’s phase assignment.

• Days 1–30: Foundations. Confirm AADE phase classification and applicable deadlines. Appoint or shortlist a certified e‑invoicing service provider. Conduct a contract audit across all sales T&Cs, supplier agreements and procurement frameworks to identify clauses requiring amendment. Obtain board or management approval for the compliance programme and allocate budget for IT integration and legal advisory costs.
• Days 31–60: Build and test. Execute the service agreement with the chosen certified provider. Complete ERP‑to‑myDATA data mapping and begin transmission testing. Draft and circulate amended contract clauses to key customers and suppliers. Establish the internal controls framework (approval workflows, reconciliation schedules, exception‑reporting templates). Conduct initial training for finance, procurement and legal staff.
• Days 61–90: Go live and monitor. Transition to production transmission. Run the first full monthly reconciliation cycle, matching myDATA transmission logs to the VAT return working papers. Resolve any remaining system or format issues flagged during the first live cycle. Distribute finalised amended T&Cs and supplier agreements. Schedule the first internal compliance review for 30 days post‑go‑live.

Businesses with exposure to the short‑term rental regulatory framework in Greece or other sector‑specific invoicing rules should layer those requirements into the implementation plan alongside the general e‑invoicing obligations.

Conclusion: Recommended Next Steps for E‑Invoicing in Greece

Mandatory e‑invoicing in Greece is not a distant regulatory prospect, it is operational now for the largest taxpayers and will extend to the wider business population in the coming months. The compliance obligations span legal, tax, IT and procurement functions, and the risk of VAT mismatches, administrative penalties and contractual disputes is real for businesses that delay preparation. The e‑invoicing Greece legal checklist set out above provides a structured starting point, but every business’s circumstances are different. Legal teams should prioritise contract amendments and liability allocation, finance teams should focus on myDATA reconciliation and record‑keeping, and both should work closely with IT to ensure that the technical infrastructure is tested and documented before the enforcement window closes.

For tailored legal guidance on implementing e‑invoice compliance in Greece, including contract drafting, VAT reporting risk assessment and audit defence, businesses can consult a qualified practitioner through the Global Law Experts lawyer directory.

Last reviewed: 14 May 2026. AADE notices should be monitored weekly. This article provides general legal information and does not constitute legal advice. Businesses should verify all legislative references and deadlines directly with AADE and qualified Greek legal counsel before acting.

Sources

1. AADE, E‑invoicing / myDATA
2. GOV.GR, Electronic invoicing to Greek public sector
3. European Commission, eInvoicing in Greece
4. EDICOM, Greece B2B/B2G Electronic Invoicing via myDATA
5. EY Greece, Mandatory e‑invoicing
6. Deloitte Greece, Mandatory B2B e‑invoicing guidance
7. VATCalc, Greece myDATA e‑invoices update
8. Ecosio, Greece e‑invoicing requirements explained
9. Zepos & Yannopoulos (Zeya), B2B e‑invoicing becomes mandatory