Not tax advice. Computation tools only. Have a professional check your work before filing.
openaccountants/skills/greece-einvoice.md

Use this skill with your AI agent

View on GitHub

Paste this skill into your AI agent's context, or save the file to your project. Works with any AI agent that reads markdown.

greece-einvoice.md343 lines16.1 KB
v10Greece
Not yet verified by an accountantContact accountant
1---
2name: greece-einvoice
3description: >
4 Use this skill whenever asked about e-invoicing in Greece, myDATA platform, AADE electronic books, MARK unique registration number, real-time tax book reporting, e-invoicing providers in Greece, myDATA API, income/expense classification, QR code on Greek invoices, or any question about issuing, transmitting, validating, or archiving electronic invoices under Greek law. Trigger on phrases like "myDATA", "AADE", "MARK number", "Greek e-invoice", "electronic books Greece", "myDATA API", "SendInvoices", "e-timologio", "AFM tax number", "income classification", "expense classification", or "Greek VAT invoice". ALWAYS read this skill before touching any Greece invoicing compliance work.
5version: 1.0
6jurisdiction: GR
7category: invoicing
8depends_on:
9 - einvoice-workflow-base
10---
11 
12# Greece E-Invoicing Compliance Skill v1.0
13 
14---
15 
16## Section 1 -- Quick Reference
17 
18| Field | Value |
19|---|---|
20| Country | Greece (Ελληνική Δημοκρατία) |
21| Currency | EUR |
22| E-invoicing system name | myDATA (My Digital Accounting and Tax Application) |
23| Governing body | AADE (Ανεξάρτητη Αρχή Δημοσίων Εσόδων -- Independent Authority for Public Revenue) |
24| Key legislation | Law 4308/2014 (Greek Accounting Standards); Decision A.1138/2020 (myDATA launch); Law 5073/2023 (penalties); Law 5222/2025 (penalty updates); Decision 1128/2025 (B2B/B2C/B2G e-invoicing via providers) |
25| Implementation timeline | myDATA platform launched July 2020; mandatory data transmission phased from 2021; B2G Peppol adopted; B2B/B2C mandatory electronic book reporting; MARK validation in force |
26| Current status (2026) | All businesses must transmit invoice summaries in real-time to myDATA; MARK (Unique Registration Number) required on all invoices; AADE cross-checks myDATA vs VAT returns; escalating penalty regime active |
27| Skill version | 1.0 |
28 
29---
30 
31## Section 2 -- Mandate Scope
32 
33### Who Must Comply
34 
35**All Greek businesses** -- every entity with a Greek AFM (Tax Identification Number) that issues revenue or expense documents must transmit data to myDATA. This includes:
36 
37- Sole proprietors (ατομική επιχείρηση)
38- Companies of all legal forms (ΑΕ, ΕΠΕ, ΟΕ, ΕΕ, ΙΚΕ)
39- Freelancers and professionals
40- Farmers under the special or normal regime
41 
42**B2G (Business-to-Government):**
43Greece has adopted the Peppol four-corner model for B2G. Structured e-invoices (EN 16931) are transmitted via Peppol to public entities. Data also flows to myDATA.
44 
45**B2B (Business-to-Business):**
46Suppliers must transmit invoice summary data to myDATA in real-time or near-real-time. The transmitted data receives a MARK from AADE, which must appear on the invoice delivered to the buyer. Invoices issued through a certified e-invoicing provider are automatically transmitted.
47 
48**B2C (Business-to-Consumer):**
49Retail transactions reported via electronic tax registers (eTax Register Machines / EAFΔΣΣ) are transmitted to myDATA. For invoices (not receipts), same rules as B2B apply.
50 
51### Transmission Methods (By Entity Type)
52 
53| Method | Description | Who Uses It |
54|---|---|---|
55| Certified e-invoicing provider (Πάροχος Ηλεκτρονικής Τιμολόγησης) | Automatic real-time transmission; provider handles XML formatting and AADE communication | Businesses using certified providers |
56| ERP integration via myDATA API | Business transmits directly via AADE REST API | Businesses with in-house or commercial ERP systems |
57| Electronic tax registers (EAFΔΣΣ) | POS/cash register data transmitted automatically | Retail businesses |
58| Special Data Entry Form (Ειδική Φόρμα Καταχώρησης) | Manual entry on myDATA web portal | Small businesses with few documents and no software |
59 
60### Exemptions
61 
62- There is no turnover threshold -- all taxable entities must comply.
63- Small entities issuing very few documents can use the Special Data Entry Form instead of software integration.
64 
65---
66 
67## Section 3 -- Technical Format
68 
69### myDATA XML Schema
70 
71myDATA uses a proprietary XML schema defined by AADE, not UBL or CII. The current schema version is governed by AADE technical specifications.
72 
73| Schema Component | File |
74|---|---|
75| Invoice document | `InvoicesDoc.xsd` |
76| Expense classification | `expensesClassification.xsd` |
77| Income classification | `incomeClassification.xsd` |
78| Response | `response.xsd` |
79| Detailed invoice (for providers) | `InvoicesDoc_detailed.xsd` |
80| Delivery notes | `RegisterTransfer.xsd`, `GetDeliveryStatusResponse.xsd` |
81 
82Current API versions: v1.0.12 (for ERP/provider) and v2.0.1 (with digital delivery notes).
83 
84### B2G Format
85 
86For B2G transactions, Greece uses EN 16931 with Peppol BIS Billing 3.0 (UBL 2.1 XML), transmitted via the Peppol network. The data also flows into myDATA for electronic book purposes.
87 
88### Key Data Elements (myDATA Schema)
89 
90| Element | Description |
91|---|---|
92| `invoiceHeader` | Invoice type, series, AA (sequential number), issue date, currency |
93| `issuer` | Supplier AFM, country, branch |
94| `counterpart` | Buyer AFM, country, branch (for B2B) |
95| `paymentMethods` | Payment method type, amount, payment info |
96| `invoiceDetails` | Line items: line number, net value, VAT category, VAT amount, classification codes |
97| `invoiceSummary` | Total net value, total VAT amount, total withheld amount, total gross value |
98| `taxesTotals` | Tax type, tax category, underlying value, tax amount |
99| `invoiceClassification` | Income/expense classification type and category per line |
100 
101---
102 
103## Section 4 -- Mandatory Fields
104 
105### Fields Required on Every Greek Invoice
106 
107| Field | Description |
108|---|---|
109| Issuer AFM (ΑΦΜ) | Greek tax identification number |
110| Issuer name and address | Full legal name, DOY (tax office) |
111| Issuer DOY (ΔΟΥ) | Tax office of the issuer |
112| Buyer AFM | Required for B2B; "retail" indicator for B2C |
113| Invoice series and number | Unique sequential identifier |
114| Invoice date | Date of issuance |
115| Invoice type | myDATA type code (e.g., 1.1 = Sales Invoice, 2.1 = Service Invoice, 5.1 = Credit Invoice) |
116| MARK (Μ.ΑΡ.Κ.) | Unique Registration Number from AADE -- mandatory on the issued document |
117| QR code | Encodes the MARK verification URL; mandatory on printed/PDF invoices |
118| Description of goods/services | Line-level detail |
119| Quantity and unit | Per line item |
120| Net value per line | Before VAT |
121| VAT category and rate | Per line (code + percentage) |
122| VAT amount per line | |
123| Income classification | Revenue type and category code per line |
124| Total net value | Sum of line net values |
125| Total VAT | Sum of line VAT amounts |
126| Total gross value | Net + VAT |
127| Payment method | Cash, bank transfer, card, cheque, etc. |
128| Withholding tax | If applicable (type, rate, amount) |
129| Stamp duty | If applicable |
130| Fees/charges | If applicable |
131 
132### MARK (Μοναδικός Αριθμός Καταχώρησης)
133 
134The MARK is the critical fiscal identifier. It is:
135- Assigned by AADE upon successful data transmission to myDATA
136- A unique numeric registration number (long integer)
137- Required on the invoice before delivery to the buyer
138- Used to generate the QR code verification URL
139 
140Without a valid MARK, the document is **not fiscally recognized** under Greek law.
141 
142### QR Code
143 
144| Channel | QR Code Source |
145|---|---|
146| E-invoicing provider | `downloadingInvoiceUrl` returned by the provider, supporting `/pdf`, `/myDATA`, `/EN16931` endpoints |
147| ERP (direct API) | `qrCodeUrl` returned by the `SendInvoices` API call |
148 
149---
150 
151## Section 5 -- Transmission Method
152 
153### myDATA REST API
154 
155| Component | Detail |
156|---|---|
157| API type | RESTful web services |
158| Authentication | AADE user credentials (AFM + API key) or e-invoicing provider credentials |
159| Environment URLs | Production: `mydata-api.aade.gr`; Testing: `mydata-dev.aade.gr` |
160| Key methods (ERP) | `SendInvoices`, `SendExpensesClassification`, `SendIncomeClassification`, `RequestDocs`, `RequestTransmittedDocs`, `CancelInvoice` |
161| Key methods (Provider) | Same as ERP plus `SendInvoices` with provider signature block |
162| Response | MARK (on success) or error codes (on failure) |
163| Real-time requirement | Transmission should occur at or near the time of invoice issuance |
164 
165### Workflow (ERP Integration)
166 
1671. **Issue invoice** in ERP system
1682. **Map data** to myDATA XML schema (InvoicesDoc.xsd)
1693. **Call SendInvoices** API endpoint
1704. **Receive response**: MARK + QR code URL (success) or error codes (failure)
1715. **Print/embed** MARK and QR code on the invoice
1726. **Deliver** invoice to buyer
173 
174### Workflow (Certified E-Invoicing Provider)
175 
1761. **Issue invoice** through the provider's platform
1772. **Provider transmits** data to AADE automatically
1783. **Provider receives** MARK from AADE in real-time
1794. **Provider embeds** MARK, QR code, and provider identification on the document
1805. **Document delivered** to buyer electronically (with `downloadingInvoiceUrl`)
181 
182### Connection Loss Handling
183 
184If the connection to myDATA is lost during invoice issuance, the transaction continues normally. The invoice is issued with a "loss of connection" indicator and transmitted with a slight delay. The MARK is obtained shortly after connectivity is restored.
185 
186---
187 
188## Section 6 -- Validation Rules
189 
190### AADE Validation (on SendInvoices)
191 
192- XML schema validation against the current InvoicesDoc XSD version
193- AFM validation for issuer and counterpart
194- Invoice type code validity (must match allowed type codes)
195- Classification code validity (income/expense codes must exist in the designation combinations)
196- Tax category and rate consistency
197- Arithmetic validation (line totals, VAT calculations, summary totals)
198- Duplicate detection (same series/AA from the same issuer)
199 
200### Pre-Submission Checks
201 
202- Validate XML locally against the current InvoicesDoc.xsd before API call
203- Verify AFM validity using AADE's public AFM verification service
204- Confirm income classification codes match the designation combinations spreadsheet (published by AADE)
205- Ensure all line items have valid VAT category codes
206- Verify arithmetic: sum of line net values = total net value; sum of line VAT = total VAT
207 
208### Common Rejection Reasons
209 
210| Reason | Detail |
211|---|---|
212| Invalid AFM | Issuer or counterpart AFM fails check-digit validation or is inactive |
213| Schema violation | XML does not conform to the current InvoicesDoc.xsd |
214| Invalid invoice type | Type code not recognized or not applicable for the transaction |
215| Classification error | Income or expense classification code invalid or mismatched with invoice type |
216| Arithmetic mismatch | Line totals do not sum to invoice summary values |
217| Duplicate submission | Same series/AA already has a MARK for this issuer |
218| Invalid VAT rate | Rate does not match the declared VAT category |
219 
220---
221 
222## Section 7 -- Tax Computation Rules
223 
224### Greek VAT Rates (2026)
225 
226| Rate | Mainland | Aegean Islands (reduced jurisdiction) |
227|---|---|---|
228| Standard | 24% | 17% |
229| Reduced | 13% | 9% |
230| Super-reduced | 6% | 4% |
231 
232Aegean island reduced rates apply to specific islands listed in Annex to Greek VAT Code (Law 2859/2000).
233 
234### Rounding Rules
235 
236- VAT amounts calculated per line, rounded to 2 decimal places (EUR cents).
237- Summary totals are the sum of rounded line-level amounts.
238- myDATA validates arithmetic consistency with a tolerance of ±0.01 per line.
239 
240### Multi-Rate Invoice Handling
241 
242Each VAT rate appears as a separate element in the `taxesTotals` section. Line items must each declare their own VAT category and rate. Mixed-rate invoices are fully supported.
243 
244### Withholding Tax
245 
246Greek invoices frequently include withholding tax (παρακράτηση φόρου). Withholding types include:
247- Income tax withholding (e.g., 20% on professional services)
248- Solidarity contribution (where applicable)
249- Stamp duty (χαρτόσημο)
250 
251These are declared in the `taxesTotals` element with specific tax type codes.
252 
253### Income and Expense Classification
254 
255Every invoice line must carry an income classification code. The designation combinations are published by AADE in a spreadsheet and map invoice types to allowed classification categories. Common categories:
256 
257| Code | Category |
258|---|---|
259| category1_1 | Revenue from sale of goods |
260| category1_2 | Revenue from sale of products |
261| category1_3 | Revenue from provision of services |
262| category1_5 | Revenue from sale of goods/services on behalf of third parties |
263| category1_7 | Revenue from subsidies/grants |
264 
265---
266 
267## Section 8 -- Archiving Requirements
268 
269| Requirement | Detail |
270|---|---|
271| Retention period | 5 years from the end of the fiscal year (general rule under Greek Accounting Standards, Law 4308/2014); extended to 6 years for VAT purposes; indefinite if litigation is pending |
272| Format | Electronic format; myDATA data is maintained on AADE servers; businesses must retain their own records |
273| MARK record | The MARK and associated QR code URL must be retained with the invoice |
274| Accessibility | Must be available for tax audit within 48 hours of request |
275| E-invoicing provider records | Providers must maintain all transmitted data and make it available to both issuer and AADE |
276| Integrity | No modification to issued documents; corrections via credit notes or modification invoices |
277| AADE platform | myDATA retains all transmitted data; businesses can query their electronic books via the API |
278 
279---
280 
281## Section 9 -- Penalties for Non-Compliance
282 
283### myDATA Penalty Framework (Law 5073/2023, updated by Law 5222/2025)
284 
285| Violation | Penalty |
286|---|---|
287| First violation (failure to transmit or late transmission) | 50% of the VAT amount on the untransmitted documents, minimum EUR 250 |
288| Repeat violation | 100% of the VAT amount |
289| Failure to transmit data for an entire period | EUR 2,500 per month of non-compliance |
290| Discrepancy between myDATA and VAT return | Triggers automatic audit; potential reassessment of VAT + 50% surcharge |
291 
292### AADE Cross-Checks
293 
294AADE actively cross-references myDATA electronic books against:
295- VAT returns (Φ2/periodic and annual)
296- Income tax declarations
297- Third-party data (banks, card payments)
298 
299Businesses with zero VAT declarations but active myDATA data face targeted audits. In 2025, AADE identified approximately 400 businesses with zero-turnover declarations despite active transaction data in myDATA.
300 
301### Additional Consequences
302 
303- Untransmitted invoices are not fiscally valid -- buyers cannot claim VAT deductions
304- AADE may impose precautionary tax assessments based on myDATA data alone
305- Persistent non-compliance triggers classification as high-risk taxpayer
306 
307---
308 
309## Section 10 -- Interaction with Tax Skills
310 
311### myDATA → VAT Return (Φ2)
312 
313myDATA electronic books are the primary source for VAT return preparation. AADE pre-fills VAT return data from myDATA. The taxpayer must reconcile any differences between their accounting records and the myDATA data before filing.
314 
315### Expense Classification → Input VAT
316 
317Buyers must classify received invoices in myDATA as expenses with the appropriate classification codes. This classification determines:
318- Deductibility of input VAT
319- Allocation to the correct income tax expense category
320- Reconciliation with the VAT return
321 
322Buyers who do not classify counterpart invoices within the deadline risk having AADE auto-classify them.
323 
324### myDATA → Income Tax
325 
326Income data transmitted to myDATA feeds into the annual income tax return. AADE cross-references declared revenue against myDATA totals. Significant discrepancies trigger audit procedures.
327 
328### B2G → Peppol → myDATA
329 
330For B2G transactions, the e-invoice travels via Peppol to the public entity. The invoice data is simultaneously transmitted to myDATA. The public entity's payment system references the myDATA MARK.
331 
332### Electronic Tax Registers → myDATA
333 
334POS transactions from electronic tax registers (EAFΔΣΣ) are transmitted to myDATA as retail income. This data feeds into both VAT returns and income tax declarations.
335 
336---
337 
338## Disclaimer
339 
340This skill and its outputs are provided for informational and computational purposes only and do not constitute tax, legal, or financial advice. Open Accountants and its contributors accept no liability for any errors, omissions, or outcomes arising from the use of this skill. All outputs must be reviewed and signed off by a qualified professional (such as a CPA, tax attorney, or equivalent licensed practitioner in your jurisdiction) before filing or acting upon.
341 
342The most up-to-date, verified version of this skill is maintained at [openaccountants.com](https://openaccountants.com).
343 

Run this skill, then get an accountant to check it

After running the full skill pack in your AI agent, sign up and upload your worksheet. We'll connect you with a trusted accountant in our network who can review your numbers before you file.

Verification status

Research-verified

Drafted from authoritative sources (tax authority sites, Big-4 summaries). Awaiting credentialed sign-off.

Needs section-by-section practitioner review to reach accountant-verified.

Section review progress

0/34

About

Use this skill whenever asked about e-invoicing in Greece, myDATA platform, AADE electronic books, MARK unique registration number, real-time tax book reporting, e-invoicing providers in Greece, myDATA API, income/expense classification, QR code on Greek invoices, or any question about issuing, transmitting, validating, or archiving electronic invoices under Greek law. Trigger on phrases like "myDATA", "AADE", "MARK number", "Greek e-invoice", "electronic books Greece", "myDATA API", "SendInvoices", "e-timologio", "AFM tax number", "income classification", "expense classification", or "Greek VAT invoice". ALWAYS read this skill before touching any Greece invoicing compliance work.

GRty-2025

Use this skill

This skill is open source and free to use in any AI agent. Copy it, download it, or clone the repo. If you find an error, report an issue — a licensed accountant will review.

5 of 5 in the GR workflow: