| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2875 |
| Technical Name |
peppol_bis_billing_be |
| 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 | 2875 |
| Technical Name |
peppol_bis_billing_be |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Belgium Peppol BIS Billing 3.0 — Preset Pack
Per-country EAS endpoint scheme defaults + SEPA payment-means presets
A Peppol BIS Billing 3.0 (EN 16931) UBL 2.1 generator focused on getting cross-border B2B invoices accepted by the receiving Access Point. The two fields that most often cause rejections — the per-party EndpointID/@schemeID (the Peppol Electronic Address Scheme) and the payment-means block — are filled from a curated, editable preset registry instead of left generic.
Per-country endpoint schemes
The correct Peppol Electronic Address Scheme code for every EU / EEA country plus major trading partners: Belgium CBE/KBO 0208, Netherlands KvK 0106, France SIRET 0009, Norway 0192, Sweden 0007, the VAT-based schemes for DE / ES / IT / PL and a GLN 0088 fallback. Auto-applied from the party country, overridable per company and partner.
SEPA payment-means presets
SEPA credit transfer (UNCL4461 code 58), generic credit transfer (30), SEPA direct debit (59, with mandate), card and cash — each emitting the correct PaymentMeans block. Real IBAN mod-97 (ISO 7064) and BIC validation with a country IBAN-length table.
Valid BIS 3.0 UBL
Stamps the BIS Billing 3.0 CustomizationID / ProfileID, injects the endpoint schemes and SEPA block at the engine UBL hook points, derives the VAT breakdown (BG-23) and produces a valid UBL 2.1 Invoice / CreditNote ready for the Peppol network.
Business-rule validation
A Peppol rule set layered on the engine's EN 16931 core: party endpoints / schemes, seller VAT, standard-category rate, exemption reason and the IBAN check — shown as a structured report before you send.
BYOK Access Point transport
Generation and validation are always local. Transmission is delegated to the certified Access Point you configure (AS4 / SMP endpoints are editable defaults), with bearer / API-key / basic authentication. Your access token and bank details stay on your own database. Built on the shared e-Invoice Core Engine; this is a thin, focused connector.
Compatible with Odoo 18 and Odoo 19.
Support
Questions or onboarding help: gencbaris.com/odoo_plugins · odoo@gencbaris.com
Screenshots
Belgian Customer Invoice Wit
Generated Peppol Bis Ubl E I
Onboarding
E Invoice Documents List
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