| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2412 |
| Technical Name |
l10n_be_peppol_cius_validation |
| 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 | 2412 |
| Technical Name |
l10n_be_peppol_cius_validation |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Belgium Peppol BIS 3.0 CIUS Validation
Pre-flight your B2B invoices before they hit the Peppol network
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 documents — a CIUS of EN 16931. The free Peppol access point can send, but it does not pre-flight your invoice against the Belgian CIUS business rules. This module does — so invalid documents are caught inside Odoo, not bounced by the receiver's access point.
Real CIUS rule pack
What it checks
- Peppol BIS 3.0 envelope identity (CustomizationID / ProfileID)
- Belgian VAT (BTW/TVA) with full CBE/KBO modulo-97 check digit
- Seller & buyer Peppol EndpointID + EAS scheme (9925 / 0208)
- EN 16931 VAT category codes on lines and breakdowns
- EUR currency, BE seller country, SEPA payment means + IBAN
- Buyer reference (BT-10) and credit-note referencing
On the invoice
One click Validate Peppol CIUS on any customer invoice or credit note. A clear status — Valid, Valid with Warnings or Invalid — plus an error/warning count and a readable report tab. Build a candidate Peppol BIS 3.0 UBL 2.1 document, optionally blocked while blocking errors remain.
Built to last
Runs on the shared e-Invoice Core Engine (EN 16931 core profile + UBL 2.1 builder). Onboarding wizard, company/partner configuration, an optional batch pre-flight cron and a Peppol profile registry entry. Compatible with Odoo 18 and Odoo 19.
Disclosure
This module performs validation and document generation entirely inside your own Odoo database. It does not transmit any data to Belgian authorities, to Peppol, or to any third party; transport is handled by your existing Peppol access point.
Screenshots
Belgian Peppol Bis 3 0 Cius
Generated Cius Checked Bis 3
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