Odoo Greek Localization
& myDATA
The most advanced and complete Greek localization and myDATA modules for Odoo in Greece. Three products that work as one system: Greek accounting, real-time AADE reporting, certified e-invoicing and card payments signed at the terminal.
Greek Tax Compliance, Simplified
Since 2022, every Greek business must report transactions to AADE myData in real time. Odoo's default localization leaves critical gaps — no ΕΓΛΣ chart of accounts, no myData integration, no DOY management.
Our package fills every gap. Built over 5+ years of real-world implementations, it delivers a complete, production-proven Greek accounting and e-invoicing stack for Odoo. It is the most advanced and complete Greek localization and myDATA package for Odoo on the Greek market.
Three products that work as one
The localization gives Odoo the accounts and journals Greek bookkeeping is organized around. The myDATA product connects those books to the electronic books of the state, in both directions. The EFT POS product closes the loop with the certified providers and the payment terminal.
EXN Greek Localization
Two statutory charts of accounts, every Greek tax mapped to the VAT return, 51 document-type journals, the reports Greek practice expects, and guards that keep the books audit-ready.
Explore EXN Greek LocalizationEXN MyData
A bidirectional integration with AADE myDATA. Documents transmit as they are posted, supplier documents flow back in, and the Φ2 return is checked against AADE before it is filed.
Explore EXN MyDataEXN EFT POS
Certified e-invoicing through Oxygen or Impact, card payments signed over the WebECR protocol, and invoicing to the public sector through the Peppol network.
Explore EXN EFT POSThe most complete Odoo Greek localization
Developed and maintained independently of the localization Odoo ships, EXN Greek Localization gives a Greek company an accounting configuration that is ready to post from the first day, structured the way Greek accountants expect and pre-wired for the myDATA obligations that follow.
Two charts of accounts: ΕΓΛΣ and ΕΛΠ
The classic ΕΓΛΣ chart carries around 1,350 accounts in the familiar ten-digit notation. The modern ΕΛΠ chart of Ν.4308/2014 carries around 2,130 accounts, and every account already knows its myDATA characterization, so the classification of each invoice line follows from the account it was posted to. The accountant chooses which chart each company applies; installing the modules never applies a chart on its own.
Every Greek tax, mapped to the Φ2 return
VAT at 24, 17, 13, 9, 6, 4 and 0 percent in product, service and retail variants, intra-EU zero-rated taxes, withheld taxes, stamp duty and the accommodation fees, all pre-configured in Greek and English. Each tax is mapped to the boxes of the periodic VAT return, so the Φ2 structure fills itself from ordinary posting.
One journal per official document type
51 journals with Greek names and short codes, one for each myDATA document type, each with its own numbering and its own refund sequence. Fiscal positions can carry a journal mapping, so an invoice to an intra-EU customer lands in the intra-EU series by itself, and subscription invoices follow the same rule without anyone watching over them.
Master data from the official registries
A button on any Greek contact queries the AADE business registry by VAT number and fills in the legal name, address, tax office and business activity. EU counterparties are validated against VIES. Behind these sit all 320 Greek tax offices with their official codes, the Greek prefectures, and partner fields for the legal name and the ΓΕΜΗ number.
The reports Greek practice actually uses
The statutory trial balance (ισοζύγιο) with its five column groups and a formatted Excel export. The partner ledger (καρτέλα), printable from any contact and emailable one by one or in bulk with a branded PDF per customer. An EC Purchase List for intra-community acquisitions. Printed documents that carry ΑΦΜ, ΔΟΥ, ΓΕΜΗ and the company bank accounts.
Guards that keep the books audit-ready
Per journal, numbering and dates advance together so a series never runs backwards, the customer field can be restricted to companies so a Τιμολόγιο is never issued to a private individual, and a due date can never precede the invoice date. Each guard is a switch the accountant controls.
A complete Odoo myDATA integration, in both directions
myDATA transmission is built into everyday invoicing. Documents flow out as they are posted, documents issued to you flow in, and everything that can go wrong in daily use has a designed path back.
MARK, UID and QR on every invoice
When an invoice is posted it is converted to the official myDATA format and transmitted to AADE. The MARK, the UID and the QR code come back onto the document, and the QR is printed on the invoice PDF so any recipient can verify it.
All 110 official document types
Sales and service invoices, credit notes, retail receipts (ΑΛΠ, ΑΠΥ), self-delivery, acquisition titles, contracts and rents, delivery documents, and the accounting entry types for payroll, depreciation and accruals.
Transmission that follows your workflow
Immediate on posting, deferred until the accounting transaction is safely committed, or fully automatic in the background on a schedule. Per journal, the accountant controls what is created and transmitted automatically.
Classifications, including the accountant's side
The full official E3 code tables ship with the product, and classifications derive from the taxes and accounts each line touches. Expenses can be classified in bulk, and submitted under the accountant's own myDATA credentials when that is preferred.
The documents your suppliers issued
A scheduled job fetches what other businesses reported against your VAT number, creates them as received documents, and a matching assistant proposes the vendor bill that corresponds to each one, so the two sets of books converge instead of drifting apart.
Mistakes are survivable
Every official error code is translated into plain Greek and English with a remediation hint. Documents already transmitted once are recovered automatically, cancellations store their own MARK, and a transmission log keeps every request and response.
For businesses that issue documents on their own behalf, a dedicated self-invoicing flow (αυτοτιμολόγηση) re-targets the invoice correctly, applies the mandatory fiscal position, invoices at cost, and settles the document with one click.
Reconciled before it is filed
The periodic VAT return exists as a live report with three columns per box: the value in Odoo, the value AADE has on file, and the difference, highlighted when they disagree. Supporting views break the same data down per day and per individual MARK, so a discrepancy can be traced to the specific document that caused it.
For the accountant, this turns VAT preparation from an act of faith into a verified close. The books and the electronic books are shown to agree, box by box, before anything is filed.
Delivery notes from the warehouse
The digital consignment note is covered where the goods actually move. Stock transfers transmit to AADE as delivery documents directly from the picking: the MARK and QR code are printed on the delivery slip, the movement purpose comes from the official list, and the loading address, delivery address, vehicle and dispatch time travel with the document.
Transmission can happen when the transfer is confirmed, with ordered quantities, or when it is done, with what was actually delivered. Cancelling the transfer can cancel the AADE document with it.
Certified providers and the payment terminal
Greek law requires card payments to be interconnected with the invoicing system: a POS terminal may only complete a transaction that is tied to a fiscal document, through a signature issued by a certified party. EXN EFT POS implements this interconnection for businesses that issue their documents through a certified e-invoicing provider (πάροχος ηλεκτρονικής τιμολόγησης), using the WebECR protocol.
Issuing through Oxygen or Impact
The provider issues the document, returns the MARK and its own authentication code, and hosts it at a public URL that becomes the invoice QR code. Each journal chooses whether it issues through the provider or directly, so mixed setups are possible, and the channel extends to delivery notes from the warehouse. Failed transmissions retry every hour and duplicate submissions are absorbed rather than double-issued.
Card payments signed at the terminal
Before a document with a card payment is finalized, a payment signature is requested from the provider over WebECR, carrying the amounts, the document series and the identity of the physical terminal. The signature and the transaction identifier are embedded in the document transmitted to myDATA. If a signature cannot be obtained, the flow stops rather than letting an unsigned card payment through.
Public-sector invoicing over Peppol
Invoices to the public sector are routed through the provider to the Peppol network as B2G invoicing requires, carrying the public entity's identification, the contract references and the CPV codes per line. Odoo then follows the document on the government side, from submission through acceptance, rejection or payment, with an hourly status check and a facility to correct and resubmit.
From configuration to a filed return
Configure
Apply the chart your accountant chooses, enter the myDATA or provider credentials, and decide per journal what is created and transmitted automatically. The background jobs ship disabled, so nothing transmits without a decision.
Post
Work in Odoo as usual. When an invoice is posted it is converted to the official format and transmitted, and the MARK, UID and QR code come back onto the document.
Reconcile
Supplier documents are fetched from myDATA and matched to vendor bills, while the Φ2 report shows Odoo and AADE side by side, box by box, down to the individual MARK.
File
The VAT return is verified before submission, and every request and response is kept in a transmission log that survives even failed transactions.
22 modules, one complete package
Everything installs from one repository and Odoo resolves the dependencies automatically: the chart module first, then the AADE modules the company needs.
// EXN Greek Localization
l10n_existanze_gr
ΕΓΛΣ chart of accounts, Greek taxes, VAT return grids, 51 document-type journals and the fiscal position to journal mapping
l10n_existanze_gr_elp
ΕΛΠ chart of accounts pre-classified for myDATA, with fiscal positions, asset models and product categories
l10n_existanze_gr_doy
All 320 Greek tax offices (ΔΟΥ) as reference data, with the tax office field on contacts
l10n_existanze_gr_partner
Legal name and ΓΕΜΗ fields, Greek prefectures and VIES validation
aade_vat
Contact autofill from the AADE business registry by VAT number
l10n_existanze_reports
The Greek statutory trial balance (ισοζύγιο) with Excel export
l10n_existanze_partner_ledger
Partner ledger (καρτέλα) button on the contact form
l10n_existanze_partner_ledger_send
Partner ledger sending by email, individually or in bulk
l10n_existanze_gr_ec_purchase
EC Purchase List report for intra-community acquisitions
l10n_existanze_sale_recurring
Subscription invoices follow the fiscal position journal mapping
l10n_existanze_due_date_guard
A due date can never precede the invoice date
journal_partner_companies_only
Companies-only customer filter per journal
journal_sequence_date_constraint
Numbering and dates advance together per journal
base_report_setup
Greek document header and footer layout, bank accounts on invoices
// EXN MyData
aade_base
The AADE user group and the AADE settings page on the company form
aade_invoice
The myDATA engine: transmission, MARK, UID and QR codes, classifications, cancellations, received documents, error handling and the transmission log
aade_invoice_stock
Delivery notes from stock transfers, with the QR code on the delivery slip
aade_sale
The self-invoicing flow (αυτοτιμολόγηση) from Sales
aade_f2_tax_report
The Φ2 VAT return with live reconciliation against AADE
l10n_existanze_gr_partner_aade
AADE transmissions always use the partner legal name
// EXN EFT POS
aade_provider
The certified provider channel (Oxygen, Impact): provider transmission, B2G invoicing over Peppol and the WebECR payment signature service
aade_provider_stock
Delivery notes through the provider channel
Common questions
Which Odoo version does the suite support?
The current release targets Odoo 19, Enterprise edition. The charts, the myDATA engine, the Φ2 report and the provider channel are delivered as a set of Odoo modules that install from one repository, and Odoo resolves the dependencies between them automatically.
Do we need an e-invoicing provider to be myDATA compliant?
No. The suite transmits directly to the AADE myDATA API with the company's own credentials. The provider channel through Oxygen or Impact exists for businesses that want certified e-invoicing, EFT POS interconnection or B2G invoicing over Peppol, and each journal can choose its channel, so mixed setups are possible.
Which chart of accounts is installed, ΕΓΛΣ or ΕΛΠ?
Both ship with the suite and the accountant decides per company. The ΕΓΛΣ package carries around 1,350 accounts in ten-digit notation. The ΕΛΠ package of Ν.4308/2014 carries around 2,130 accounts, pre-classified for myDATA. Installing the modules never applies a chart by itself.
Is the digital delivery note (ψηφιακό δελτίο αποστολής) covered?
Yes, from the warehouse. Stock transfers transmit to AADE as delivery documents directly from the picking, with the MARK and QR code printed on the delivery slip, official movement purposes, addresses, vehicle and dispatch time, either on confirmation or on completion of the transfer.
What happens when a transmission fails?
The document stays in a pending state with the error explained on its history in plain Greek and English, and is retried. Duplicate submissions are detected and absorbed, and every request and response is kept in a transmission log, so nothing is silently dropped and there is always an audit trail.
Can we test before going live?
Yes. Every external connection has a test counterpart and a switch: the myDATA development environment, the provider sandbox, and separate credentials for each. A new deployment runs against the test endpoints until the accountant has verified transmissions, classifications and the Φ2 reconciliation, and a staging copy resets itself to the development endpoint so it can never transmit real documents.
0
Odoo Modules
0K
Investment
0B+
Transactions Turnover
0M+
myDATA Transmissions
Ready to Modernize Your Business?
Get in touch for a personalized demo and see how the EXN Greek Localization and myDATA suite simplifies your AADE compliance in Odoo. The team that builds the modules is the team you talk to.