| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 2850 |
| Technical Name |
ubl21_export_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 |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 2850 |
| Technical Name |
ubl21_export_validator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Global UBL 2.1 Export
Universal UBL 2.1 / Peppol BIS 3.0 export with a pre-send Schematron-lite validator
Build the structured invoice every Peppol-mandate country needs — then catch the rejections at your desk, not at the access point. EN 16931 and Peppol BIS Billing 3.0 business rules are checked before you send.
Why it matters
The EU ViDA package lets Member States impose domestic e-invoicing mandates, and a wave clusters in 2026–2028 (Belgium, Poland, France, Germany, Croatia, Greece, Latvia, Slovenia, Spain…). Every one resolves to the same structured format: UBL 2.1 / Peppol BIS 3.0 / EN 16931. Odoo can emit UBL, but does not validate it against the Schematron rules an access point enforces. This module fills exactly that gap.
UBL 2.1 builder
Invoice & CreditNote XML with seller / buyer parties, lines (allowances, charges, units, item ids), VAT-breakdown aggregation, monetary totals, payment means & terms, and EAS-coded electronic addresses.
Schematron-lite engine
A real Schematron firing model — context XPath plus assertions and flags — implemented directly over the parsed XML tree. No Saxon, no XSLT toolchain dragged into your Odoo server.
EN 16931 core rule pack
BR-01…BR-26, the BR-CO-* coherence rules, BR-CL-* code-list rules, per-VAT-category math (BR-CO-17) and grand-total math (BR-CO-13 / 15 / 16).
Peppol BIS Billing 3.0 pack
The EN 16931 rules plus the sender-relevant PEPPOL-EN16931-Rxxx restrictions: CustomizationID / ProfileID, EAS endpoint schemes, seller identification and line-sign rules.
Human-readable report
Every violation as a line: rule id, severity, plain-language message, document location and a remediation hint — plus a standard SVRL XML report for archiving and downstream tooling.
Editable official defaults
CustomizationID, ProfileID and EAS scheme are configurable per company — nothing is hard-coded. Optionally block export while fatal violations remain.
How it works
- Open a customer invoice or credit note.
- Click Validate UBL for a report, or Export UBL 2.1 to generate and download the XML.
- Read the human-readable report — fix the flagged fields.
- Export the validated UBL and send it through your own access point.
Privacy & transmission
This is a builder and validator only. It does not transmit any invoice data anywhere — it produces a file you download and send through your own channel. No data leaves your database. Built on the e-Invoice Core Engine.
Compatibility & support
Compatible with Odoo 18 & 19 (Community & Enterprise). Questions? odoo@gencbaris.com · gencbaris.com/odoo_plugins
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