| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2767 |
| Technical Name |
l10n_be_peppol_bis_generator |
| 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 | 2767 |
| Technical Name |
l10n_be_peppol_bis_generator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Belgium Peppol BIS 3.0
Peppol BIS Billing 3.0 (BE CIUS) UBL generator for Odoo — ready for the mandatory B2B e-invoicing live 1 January 2026
Generate compliant Peppol BIS Billing 3.0 invoices and credit notes for Belgium — a CIUS of the European norm EN 16931. The free Peppol access point transports invoices but does not enforce the Belgian specifics; this satellite produces the structured UBL with correct CBE enterprise-number identifiers and VAT handling, validates it against the BE CIUS rules, and delivers it through your access point or as a manual export.
Peppol BIS 3.0 UBL document
Invoice and credit note with the correct CustomizationID / ProfileID, document-level allowances and charges, payment means (IBAN / BIC) and credit-note referencing of the original invoice.
CBE enterprise-number handling
Real modulo-97 checksum validation of the Belgian Crossroads Bank for Enterprises (CBE / KBO / BCE) number on the company and partners, legacy 9-digit normalisation and the Belgian VAT (BExxxxxxxxxx) form.
Peppol participant identifiers
EndpointID under the Belgian schemes 0208 (enterprise number, recommended) and 9925 (VAT), and the legal CompanyID carrying the CBE number with its scheme — exactly as the BE CIUS expects.
EN 16931 VAT categories
Standard, zero, exempt, reverse charge, intra-Community and export (S / Z / E / AE / K / G / O), with mandatory exemption-reason injection for the non-standard categories (BR-E-02 / BR-AE-02).
BE CIUS validation
A Belgian business-rule set layered on the engine's EN 16931 core: seller and buyer CBE, valid VAT categories, standard-rate positivity, exemption reasons and EUR currency — surfaced before delivery.
BYOK delivery
Manual UBL export or access-point AS4 delivery with editable endpoints. The sender participant id is derived from your company CBE. Your access point API key stays on your database — bring your own key.
Guided onboarding & clean integration
A one-screen onboarding wizard validates your CBE number, sets the Peppol scheme and delivery mode, and leaves the company ready to issue BIS 3.0 invoices. The module is built on the shared e-Invoice Core Engine, so the UBL builder and validation framework are reused, not duplicated. An optional batch-send cron drains posted customer documents to Peppol.
Compatible with Odoo 18 and Odoo 19. Live test: demo.gencbaris.com · Support: odoo@gencbaris.com
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