| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3205 |
| Technical Name |
einvoice_format_be_validator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3205 |
| Technical Name |
einvoice_format_be_validator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Belgium EN 16931 Check
Deep Peppol BIS 3.0 business-rule validation for the Belgian B2B mandate
Belgium made structured B2B e-invoicing over the Peppol network mandatory on 1 January 2026 (sanction tolerance to 31 March 2026; repeat breaches up to EUR 5 000). Belgian invoices travel as Peppol BIS Billing 3.0 UBL — a CIUS of EN 16931 — and a Belgian access point runs the document against the official EN 16931 + Peppol-EN16931 Schematron before it will route it. This module runs that same body of business rules inside Odoo, so a non-compliant invoice is caught up front instead of being bounced downstream.
Real EN 16931 rule engine
The calculation chain (BR-CO)
- Line net = qty × (price / base qty) − allowances + charges
- Sum of invoice line net amounts (BT-106)
- Document allowance / charge totals (BT-107 / BT-108)
- Tax-exclusive total (BT-109) and per-category VAT math (BT-116/117)
- Total VAT (BT-110), grand total (BT-112)
- Amount-due chain — prepaid / rounding / payable (BT-113/114/115)
Every check uses the EN 16931 ±0.02 rounding tolerance.
VAT categories done right
- BR-S standard rated — positive rate + seller VAT id
- BR-Z zero rated · BR-E exempt
- BR-AE reverse charge — buyer VAT id required
- BR-G export · BR-O out of scope
- BR-IC/K intra-community supply
- Mandatory VAT exemption reason (BT-120 / BT-121) with the standard VATEX code
Belgian VAT-category classifier
Beyond the naive mapping
A naive connector maps “rate > 0 → S, rate = 0 → Z” and ships invoices a Belgian access point rejects. A 0 % line can legitimately be Z, E, AE, K, G or O — and each demands a different exemption reason. This module inspects the Belgian 21/12/6/0 % rates and the partner context (domestic, EU B2B, EU B2C, export; VAT-registered or not) to assign the correct category and reason.
Decimal & payment-terms rules
- BR-DEC — at most two decimals on monetary amounts
- BR-CO-25 — a positive amount due needs a due date or payment terms
- PEPPOL-EN16931 — one VAT breakdown per category/rate; allowance/charge reasons
Workflow
- One-click Validate EN 16931 on every customer invoice
- Per-invoice status: Valid / Valid-with-Warnings / Invalid
- Error & warning counters and a report tab citing each BR-* rule
- Optional batch cron to pre-flight posted documents
- Company settings: enable, block-on-error, strict-warnings
Built on the e-Invoice Core Engine
This validator layers on the shared e-Invoice Core Engine
framework and the Belgium Peppol CIUS rule pack (both
installed automatically as dependencies). The EN 16931 rules are
real, deterministic algorithms — not stubs — and are
unit tested with plain python.
Privacy: validation runs entirely inside your own Odoo database. No data is transmitted to Belgian authorities, to Peppol, or to any third party; transport stays with your existing access point.
Compatible with Odoo 18 and Odoo 19.
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