Blog
Odoo and EU Compliance: Peppol E-Invoicing, VAT and GDPR
How Odoo handles Peppol e-invoicing, OSS VAT reporting and GDPR for EU operations, what works out of the box, and what you still have to own yourself.
- bottom
- odoo
The short answer
Odoo covers the mechanics of EU compliance well enough for most small and mid-sized businesses: it can send and receive structured e-invoices over Peppol, it ships OSS tax reports, and it gives you the tools to answer GDPR data requests. What it does not do is make you compliant. Deadlines differ by country, tax mappings need a human check, and GDPR is mostly about your processes, not your software.
If you sell into the EU from the US, UK or another EU state, treat Odoo as the engine and plan for a compliance owner (an accountant, a DPO or a consultant) to sign off the setup.
E-invoicing and Peppol: the deadline that is already here
Peppol is a network for exchanging structured invoices between businesses. The EU’s direction is clear: the ViDA package sets 1 July 2030 as the date for structured EN 16931 e-invoicing on intra-EU B2B transactions, and several member states are moving much sooner (Fonoa, Ecosio/econnect timeline).
The two countries SMBs ask about most:
- Belgium: mandatory B2B e-invoicing via Peppol started on 1 January 2026, with Peppol BIS 3.0 as the recommended format. Check penalty rules and any transition measures with Belgian authorities (TrueCommerce).
- Germany: receiving structured e-invoices has been required since 1 January 2025. The obligation to issue them is phased in, with the final step on 1 January 2028 (Fonoa, KPMG Luxembourg overview). Confirm the exact thresholds with the German finance ministry or your tax adviser.
What Odoo does
According to the Odoo 19 documentation:
- It sends via Peppol in BIS Billing 3.0, XRechnung CIUS and NLCIUS, and the default format depends on the customer’s country. You can override it per customer.
- Your company registers as a Peppol participant from within Odoo, using a VAT or company registry number, an email and a phone number. You choose between sending and receiving, or sending only.
- Incoming documents can be posted as vendor bills or stored as documents.
- Registration is described as free and available in Community. The page does not state fees for sending and receiving, so confirm those with Odoo before you budget.
- A demo mode lets you test without real data. Moving back to production requires deregistering from demo and registering again.
Eligible countries cover most of Europe, plus places such as Switzerland and the United Kingdom.
What you still have to do
- Check your customers. Before sending, confirm the contact is a registered Peppol participant. If not, you fall back to PDF or another route.
- Clean your master data. Structured invoices are rejected for missing VAT numbers, wrong tax categories and bad unit codes. Most failures we see come from data quality, not software.
- Migrate carefully. If you already use another access point, deregister from it first. Odoo’s page says migration from the old Belgian Hermes platform is automatic.
- Plan for reporting. Belgium, for example, is planning near-real-time e-reporting from 2028 (econnect). Check which reporting rules apply to you; they differ by country and are still being legislated in places.
VAT: OSS is the part to set up properly
If you sell goods or services to EU consumers from another member state (or from outside the EU), the One Stop Shop scheme lets you report VAT in one place instead of registering in every country.
Per Odoo’s distance selling documentation:
- In Accounting settings, enable EU Intra-community Distance Selling.
- Odoo creates fiscal positions and taxes based on your company’s country.
- Review the proposed tax mapping. The docs themselves recommend checking it against the products and services you sell.
- Run the OSS Sales or OSS Imports tax report, export it (PDF, XLSX or XML) and submit it on your national OSS portal.
The docs cover two schemes: Union OSS for cross-border B2C services, and Import OSS for goods valued at up to 150 euros.
Trade-off: Odoo generates the report, but it does not file it for you and it cannot know whether you are in the right scheme. Wrong product tax categories (digital services versus goods, reduced-rate items) are the common source of errors. Have an accountant review the mapping once, then spot check quarterly.
GDPR: tools yes, compliance no
Odoo’s own GDPR page is blunt: using Odoo is not enough for GDPR compliance. The useful parts:
- Roles. On Odoo Online and Odoo.sh, Odoo acts as processor and you are the controller of your database. On-premise, you are both and responsible for security.
- Data processing terms. Odoo says its Enterprise subscription agreement includes data protection clauses acting as a DPA. Read them with your counsel rather than relying on a summary.
- Data subject requests. You have one month to respond. Access and portability need manual exports. Erasure by deleting a contact is blocked when business documents reference it, so you will often anonymize instead.
- Your homework. Data mapping, legal bases, a privacy policy, consent checkboxes where needed, access groups and record rules, retention limits and an incident procedure.
Two practical notes. First, personal data sitting outside Odoo (email, spreadsheets, backups) is still in scope. Second, for consent, Odoo’s page suggests adding a consent checkbox field with Odoo Studio and placing it on your website form.
A realistic setup checklist
| Area | First thing to do |
|---|---|
| Peppol | Register, test in demo mode, clean VAT IDs on customers and vendors |
| Formats | Set country-specific formats per customer (BIS 3.0, XRechnung) |
| OSS VAT | Enable distance selling, review the tax mapping with your accountant |
| GDPR | Map personal data, define retention, rehearse an erasure request |
| Ownership | Name one person responsible for each of the above |
Allow a few weeks for a clean setup if your data is tidy, longer if you are merging multiple entities or migrating from another system.
When to get help
You can handle a single-entity Peppol and OSS setup in-house if someone owns the data cleanup. Bring in outside help when you have several companies, several countries with different e-invoicing rules, or a migration running in parallel.
If you want a second pair of eyes on your Odoo compliance setup, Teknologia Solutions offers a no-charge conversation to walk through your situation and tell you honestly what you can do yourself.
Sources: Odoo 19 Peppol documentation; Odoo 19 EU distance selling; Odoo GDPR; Fonoa on Peppol in Europe; econnect ViDA timeline; TrueCommerce on Belgium; KPMG Luxembourg. Mandates, dates and fees change; this is not legal or tax advice, so verify against primary sources and your advisers before acting.