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: support@pokutsoft.com · pokutsoft.com/
Screenshots
Routed Invoice Matched Route
Multi Endpoint Routing Rules
Onboarding
Peppol Access Point Connecti
Important: scope & BYOK
This module enhances routing, validation and inbound handling around your existing Peppol flow and performs SMP lookups. It is not a Peppol Access Point and we are not a Peppol Service Provider / integrator. Transmission and SMP queries are bring-your-own-key (BYOK): no real endpoints are bundled, and the base URLs and API token you enter are stored only on your own database and used solely to reach the Access Point you configure. You remain the registered taxable person responsible for your Peppol participation; no government, OpenPeppol or third-party accreditation is performed on your behalf. Email support is included at support@pokutsoft.com and the purchase is refundable under the Odoo Apps Store refund policy if it does not work as described.
Update date: 2026-07-02