| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 756 |
| Technical Name |
eu_einvoicing_tracker |
| License | OPL-1 |
| Website | https://entrophy.in |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 756 |
| Technical Name |
eu_einvoicing_tracker |
| License | OPL-1 |
| Website | https://entrophy.in |
EU E-Invoicing Mandate Tracker
Know every deadline. Skip the panic.
Twelve EU countries push new domestic B2B e-invoicing mandates live between 2026 and 2028. Each one has a different format, a different channel, a different legal authority, and a different penalty. This module turns that chaos into one Odoo dashboard — filtered to your company’s country, with automated deadline reminders, format cheatsheets, and direct hints to which Odoo module covers each mandate.
1 January 2026: Belgium goes live. Did anyone tell your CFO?
Belgium B2B was mandatory on 1 January 2026, with graduated penalties from €1,500 to €5,000 per infringement once the 3-month tolerance ends. Poland’s KSeF follows on 1 February for large taxpayers and 1 April for everyone else. Croatia, Greece, Denmark pile on through 2026. France issuing kicks in for SMEs on 1 September 2027. Germany flips on for >€800k issuers on 1 January 2027 — and for everyone on 1 January 2028.
Every quarter, the dates shift. Slovenia postponed once already. Portugal delayed its QES requirement. Romania moved the B2C goalposts. Trying to track this manually on the European Commission’s factsheet pages is a part-time job, and missing a date is a real-money penalty.
32 countries. Every deadline. One dashboard.
Ships with a curated mandate dataset covering all 27 EU member states plus Norway, Iceland, Liechtenstein, Switzerland, and the United Kingdom. Each entry carries:
- B2B + B2G dates with phasing notes (turnover thresholds, tolerance periods, size-based rollouts).
- Required format — Peppol BIS 3.0, FatturaPA, KSeF FA_VAT, e-SLOG, XRechnung, ZUGFeRD, Factur-X, VeriFactu, myDATA, RO e-Factura, NAV RTIR, OIOUBL, and more.
- Transmission channel — SdI, ANAF, FACe, Peppol 4-corner, Peppol 5-corner, NemHandel, KSeF API.
- Legal authority for verification (DGFiP, AEAT, AdE, NAV, AADE, FURS, etc.).
- Odoo readiness rating — first-party, OCA, partner, Peppol-only, or gap — with the suggested technical module name for each mandate.
Reminders at 180, 90, 30, 7 days
A daily cron checks every active mandate against your company’s country and posts an in-app reminder on each mandate’s chatter at the four classic compliance windows: six months out for budget season, three months out for vendor selection, one month out for go-live readiness, and one week out for crisis mode. Account managers in your company are auto-tagged. Duplicate-sending is prevented by an internal reminder log.
Why this exists
Finance teams in 2026 cannot rely on the EC factsheet site alone — it’s comprehensive, but it’s not yours. It doesn’t tell you that your French Odoo install needs a Plateforme Agréée link, that your Slovenian subsidiary will need an e-SLOG module that doesn’t exist on apps.odoo.com yet, that your Polish entity has a 60-day window to onboard onto KSeF or eat the fine.
This module makes that mapping concrete: it knows your company’s country, it surfaces only the mandates that apply to you, and it tells you exactly which Odoo module you need (or warns you that none exists yet).
Pricing
One-time per database. Free updates per Odoo version. Pay once, install on as many databases of that Odoo version as you need. When you upgrade to a new major Odoo version, the module ships free for that version too while you remain a customer of the current one.
Lightweight by design: depends only on base,
mail, and account. Works on Odoo 18 Community
and Enterprise. No external SaaS, no per-seat fees, no API keys, no
tracking. Mandate data is bundled in the module itself — the
module works offline.
Roadmap
Future companion modules will cover the country mandates where no first-party Odoo solution exists yet:
- Slovenia e-SLOG B2B Connector — 1 January 2028 mandate, 8-day FURS reporting, e-SLOG XML.
- Slovakia Peppol 5-Corner Connector — 1 January 2027 IS EFA replacement.
- Portugal QES Plug-In — Qualified Electronic Signature requirement from 1 January 2027 on non-EDI PDF invoices.
Owning the Tracker today means earlier access and discounted bundles on companion modules as they ship.
Snapshot date and verification
Mandate dates in this module reflect the publicly available state as of 13 May 2026. Dates have shifted multiple times in the past 12 months — Slovenia postponed once, Portugal delayed QES, Latvia moved B2B to 2028. Updates ship in future module versions. For any deadline you are about to act on, verify against the European Commission’s eInvoicing Country Factsheets.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module