| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3632 |
| Technical Name |
peppol_enhancement_suite |
| 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 | 3632 |
| Technical Name |
peppol_enhancement_suite |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
EU Peppol Enhancement Suite
Multi-endpoint routing, UBL attachments and inbound notifications for the European Union Peppol network
A Peppol enhancement satellite for the e-Invoice Core Engine that fills the gaps the minimal core Access Point integration leaves open. Built for the wave of EU national e-invoicing mandates clustering across 2026-2028 under the VAT in the Digital Age (ViDA) package, where Peppol BIS Billing 3.0 is the default transport. Compatible with Odoo 18 and Odoo 19.
Multi-endpoint routing per partner
Declarative routing rules resolve, per recipient and document type, which Access Point to transmit through and which Peppol document-type and process identifiers to use. Rules match on the recipient electronic-address scheme, country and document type, most-specific-first, with a default fallback. A Norwegian buyer and a Belgian buyer can be routed over different Access Points from the same database.
Peppol participant identifiers (EAS)
A built-in ISO 6523 / Peppol electronic-address-scheme code list on partners and the company, with canonical scheme:value participant ids, structural validation and real national check-digit algorithms: the Norwegian organisation-number MOD-11, the Dutch elfproef and EU-VAT structure checks. SMP DNS lookup names are built with the genuine Peppol hash naming convention.
UBL attachments
Embed the human-readable PDF rendering and supporting documents (CSV line detail, contracts) into the structured invoice as AdditionalDocumentReference / EmbeddedDocumentBinaryObject, with MIME allow-listing, a single-primary-rendering rule, a size budget and a SHA-256 integrity fingerprint per attachment.
Inbound notifications
Parse the asynchronous responses the network returns: the Message Level Response (MLR) and the Invoice Response (UBL ApplicationResponse) plus Access Point transmission status. Each inbound notification is stored, classified (accepted / rejected / paid / under-query) and linked back to its invoice so a rejection is visible where it matters.
Bring-your-own-key, no surprises
Submit, poll status, perform SMP lookups and pull inbound documents over a configurable Access Point REST facade. No real endpoints are bundled: the base URLs and the API token are bring-your-own-key, stored only on your database and transmitted solely to the Access Point you configure. A Peppol BIS Billing 3.0 pre-send validation rule set, layered on the engine's EN 16931 core, mirrors the most common Access Point MLR rejections so you catch them before sending.
What's included
- Per-partner and per-company Peppol participant identifiers with EAS scheme selection and validation
- Routing-rule manager with priority and specificity ordering
- UBL attachment embedding on customer invoices and credit notes
- Inbound notification inbox with MLR / invoice-response parsing and invoice linkage
- BYOK Access Point connection with send / status / SMP / inbound endpoints
- Guided onboarding wizard, inbound-poll cron and full transport logging
- Requires the e-Invoice Core Engine; compatible with Odoo 18 and Odoo 19
Support: 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