The distinction between E-Invoicing vs E-Reporting is one of the most common sources of confusion for businesses navigating Greek digital tax compliance. Both terms describe ways of communicating transaction data to tax authorities digitally, but they operate differently and impose different obligations on businesses. In the Greek context, the AADE myDATA platform is unusual in that it combines elements of both concepts within a single framework, making it especially important to understand how the two relate.
The E-Invoicing vs E-Reporting distinction matters practically because it determines how your systems must interact with AADE, what data must be transmitted and when, and what happens if you get it wrong. This guide defines each concept clearly, explains how myDATA combines them in the Greek national framework, and helps you determine which obligations apply to your specific business situation under Greek tax reporting requirements.
Key Takeaways
- E-Invoicing vs E-Reporting: E-Invoicing vs E-Reporting differ in who controls the invoice and when the tax authority receives data.
- E-Invoicing: E-invoicing involves the tax authority in the invoice issuance process itself, issuing or validating the document.
- E-Reporting: E-reporting submits invoice summary data to the tax authority separately from the invoicing process.
- AADE myDATA reporting: AADE myDATA reporting combines both by requiring structured invoice data to be transmitted at issuance time.
- myDATA E-Invoicing compliance: myDATA E-Invoicing compliance means all invoices are validated by AADE before being considered legally complete.
Definition of E-Invoicing
E-Invoicing, in its strictest technical sense, refers to a system in which the tax authority is involved directly in the invoice creation or validation process. Under a true e-invoicing model, an invoice is not legally complete until the tax authority has seen it, validated it, and assigned an official identifier. The authority may generate the invoice on behalf of the issuer, validate the issuer’s pre-generated invoice, or simply record its existence — the key characteristic is real-time or near-real-time authority involvement at the point of issuance.
Greece electronic invoice submission to myDATA follows this model. When a business submits an invoice to the AADE myDATA API, the platform validates it against AADE’s technical rules and assigns a MARK number. Only after the MARK is issued is the invoice considered legally complete. This makes Greece’s approach a true e-invoicing system rather than a simpler e-reporting system, because the tax authority is not just receiving a report — it is validating the invoice itself.
Definition of E-Reporting
E-Reporting, by contrast, refers to the periodic or real-time transmission of invoice summary data — or transactional data extracted from invoices — to the tax authority separately from the invoicing process. Under an e-reporting model, invoices continue to be exchanged directly between buyer and seller as before, and the tax authority receives a report of those transactions either in real time, daily, or on a periodic basis. The authority uses this report for audit and VAT verification purposes but is not involved in the invoice issuance process itself.
Several EU countries operate e-reporting systems where invoices are exchanged peer to peer and then reported to the tax authority via a separate data feed. The report typically contains summary-level invoice data — issue date, counterparty IDs, total amounts, VAT breakdown — rather than the full invoice XML. This contrasts with the E-Invoicing vs E-Reporting distinction, where e-invoicing requires the authority’s involvement before the invoice is legally effective.
| Feature | E-Invoicing | E-Reporting |
|---|---|---|
| Tax Authority Involvement | At issuance — invoice validated before legal completion | After issuance — periodic or real-time data feed |
| Invoice Exchange | Between buyer, seller, and authority simultaneously | Between buyer and seller; authority receives separate report |
| Official Identifier | Assigned by authority (e.g., MARK in Greece) | Not typically required |
| Legal Completeness | Invoice legally complete only after authority validation | Invoice complete on issuance; report is secondary |
| Error Impact | Rejected invoice is not legally issued | Errors affect tax record but not invoice itself |
How myDATA Combines Both
The AADE myDATA platform is a hybrid system that combines elements of both E-Invoicing vs E-Reporting into a single framework. It functions as an e-invoicing system in that invoices must be transmitted to myDATA and receive a MARK before they are legally complete — the authority is involved at the point of issuance. At the same time, myDATA functions as a digital accounting and tax application, maintaining bookkeeping summary records for income and expenses that are updated as invoices are submitted — a function more associated with e-reporting frameworks.
This dual function is what makes AADE myDATA reporting unique among EU digital tax systems. Businesses are not simply sending invoices through a clearance system and receiving them back validated. They are also populating a digital version of their own accounting records that AADE can review at any time. The summary books maintained in myDATA — income records, expense records, and VAT calculations — are derived from the invoice submissions and serve as the basis for tax audit and VAT reconciliation.
Real-Time vs Periodic Reporting
In the Greek framework, real-time transmission is the default requirement for myDATA E-Invoicing compliance. Invoices must be submitted to myDATA at or before the time of issuance, meaning the MARK must be obtained before the invoice is sent to the recipient. This real-time requirement distinguishes the Greek system from periodic e-reporting frameworks where batches of invoice data are submitted daily, weekly, or at the end of the VAT period.
There are limited exceptions where periodic submission is permitted — for example, certain retail transaction data collected from fiscal cash registers may be submitted in daily batches rather than invoice by invoice. However, for the standard B2B invoice workflow, Greek tax reporting requirements specify real-time transmission, and businesses should plan their integrations accordingly. Any delay between invoice issuance and myDATA submission creates a period during which the invoice is legally incomplete.
Systems Needed for Each
Implementing the E-Invoicing vs E-Reporting elements of the Greek framework requires specific technical capabilities. For the e-invoicing element, businesses need a system that can generate AADE-compliant XML invoices, connect to the myDATA API in real time, handle submission responses, extract MARK numbers, and manage error retries. This typically requires an ERP integration, a certified e-invoicing provider, or custom API development. Oman Advintek helps businesses streamline digital invoicing through solutions designed to support e-invoice processing and compliance workflows.
For the e-reporting element — maintaining accurate summary books in myDATA — businesses need systems that can categorise each invoice correctly using AADE income classification codes, ensure that counterparty data is accurate so that expense entries are created correctly for the recipient, and reconcile their own records against the myDATA summary books periodically. The reconciliation step is a new compliance task that many businesses underestimate when planning their implementation.
Impact on VAT and Income Records
The myDATA framework has a direct impact on VAT and income records because the summary books maintained by AADE are the basis for VAT declarations and income tax calculations under Greece electronic invoice submission requirements. If a business submits an invoice with an incorrect VAT classification or income category code, the myDATA summary books will reflect the error, and the business’s VAT declaration will need to be reconciled against the incorrect entry.
This interconnection means that data quality in invoice submissions directly affects tax obligations. A business that uses incorrect VAT codes consistently will find that its myDATA summary books show different VAT totals from its accounting system, creating a discrepancy that AADE can identify during an audit. Meeting Greek tax reporting requirements accurately at the point of submission is therefore more efficient than correcting errors retrospectively.
Which One Applies to Your Business
For most Greek businesses issuing standard B2B or B2C invoices, both dimensions of the E-Invoicing vs E-Reporting framework apply simultaneously through myDATA. The e-invoicing element applies because invoices must be submitted to myDATA and receive a MARK before they are legally complete. The e-reporting element applies because the submitted invoices populate myDATA summary books that serve as digital accounting records and the basis for tax declarations.
Businesses that operate fiscal cash registers follow a slightly different path for their retail transactions, as the fiscal register transmits transaction data through a separate channel. However, these businesses still have myDATA E-Invoicing compliance obligations for the B2B invoices they issue outside the fiscal register system. Understanding which transactions follow which channel is an important part of the implementation scoping exercise.
Conclusion
The E-Invoicing vs E-Reporting distinction is important for understanding Greece’s approach to digital tax compliance, but in practice most businesses need to implement both capabilities simultaneously through AADE myDATA reporting. The Greek framework is more demanding than a simple e-reporting system because it requires real-time tax authority involvement in the invoice issuance process, and it is also broader than a simple clearance system because it maintains full digital accounting records for every taxpayer. Meeting myDATA E-Invoicing compliance requires integrating both dimensions into your invoicing and ERP workflows.
Frequently Asked Questions
What is the difference between E-Invoicing vs E-Reporting?
E-Invoicing involves the tax authority in the invoice creation or validation process — invoices are not legally complete without authority involvement. E-Reporting submits invoice summary data to the tax authority separately from the invoicing process. Greece E-Invoicing vs E-Reporting is resolved by myDATA, which combines both in a single framework.
How does AADE myDATA reporting work?
AADE myDATA reporting requires businesses to submit structured invoice XML to the myDATA platform in real time. myDATA validates the submission, assigns a MARK number, and updates the business’s digital accounting summary books with the corresponding income or expense entry.
What is Greece electronic invoice submission?
Greece electronic invoice submission is the process of transmitting invoice XML data to the AADE myDATA API. The submission must occur at or before invoice issuance, and the MARK number returned by myDATA must be stored alongside the invoice record before the invoice is sent to the recipient.
What are Greek tax reporting requirements?
Greek tax reporting requirements include the real-time submission of all invoices to myDATA, the use of AADE income classification codes on every invoice line, the maintenance of accurate counterparty data, and the reconciliation of myDATA summary books against the business’s own accounting records on a periodic basis.
What is myDATA E-Invoicing compliance?
myDATA E-Invoicing compliance means that all invoices issued by a business are transmitted to the AADE myDATA platform in real time, pass AADE’s technical validation rules, receive MARK numbers confirming legal completeness, and are archived in a manner that meets AADE’s statutory retention requirements.
Source by:
Image by Pexels
