EU Peppol BIS Universal E-Invoicing

Hauptfunktionen

Generates compliant Peppol BIS Billing 3.0 UBL 2.1 documents from Odoo invoices and credit notes (account.move)

Single connector covering all Peppol-eligible EU member states — one app, no per-country integration sprawl

Certified Access Point connectivity for outbound transmission and inbound reception (AS4 handled by your provider)

SMP/SML participant lookup to resolve the recipient's Peppol endpoint and supported document types before sending

Multi-country participant registration workflow to register your legal entities on the Peppol network

Inbound document reception that lands supplier invoices in Odoo as draft vendor bills for review and posting

Auto-billing of received documents with configurable mapping to your chart of accounts and tax codes

Country-specific CIUS and national profile handling (e.g. localized mandatory fields and validation nuances)

Pre-send UBL validation against BIS 3.0 / EN 16931 business rules so malformed invoices are caught before transmission

Transmission status tracking per invoice (queued, sent, delivered, rejected) surfaced on the account.move form and in the chatter

res.partner extensions storing each contact's Electronic Address Scheme, participant ID and endpoint details

Compute fields with @api.depends that flag whether an invoice is Peppol-ready in real time

Automated push/poll via scheduled actions (ir.cron) plus base.automation triggers — no manual clicking

Role-based access via ir.model.access.csv and record rules so only accounting users can register or resend

XML-RPC / JSON-RPC endpoints to send, receive and query Peppol status from external systems

Full audit trail of every transmitted and received document, retained on the invoice for compliance

Multi-company support so each legal entity uses its own participant identity and Access Point credentials

Works on Odoo 17, 18 and 19, Community or Enterprise, aligned to your existing accounting configuration

Auf Bestellung gebaut, komplett für Sie erledigt

Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.

Sie bestellen

Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.

Wir bauen & installieren

ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Odoo.

Go-live + Support

Sie gehen in etwa 2–4 Wochen live, mit einem Support-Zeitraum nach dem Launch.

Über dieses Produkt

EU Peppol BIS Universal E-Invoicing is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for you — it is not an instant apps.odoo.com download. After purchase, our Odoo engineers scope your exact country footprint, legal entities and Access Point choice, then deliver a production-ready connector on your Odoo 17, 18 or 19 database within a 2–4 week lead time.

The module turns every Odoo customer invoice and credit note (account.move) into a compliant Peppol BIS Billing 3.0 UBL 2.1 document, transmits it through a certified Peppol Access Point, and receives inbound documents back into Odoo as draft vendor bills — all from one connector, regardless of which EU member states your customers and suppliers sit in. No more juggling a separate integration per country: SMP/SML participant lookup, CIUS profile selection and per-country validation rules are handled inside a single, unified Odoo app.

Under the hood it is real Odoo engineering, not a black box. We extend account.move and res.partner with the fields Peppol needs (participant IDs / Electronic Address Scheme, endpoint IDs, transmission status), add compute fields with @api.depends for live UBL-readiness checks, generate the UBL via QWeb/lxml templates you can inspect, and expose the whole flow through the standard Odoo UI plus XML-RPC/JSON-RPC for headless automation. Security is enforced with ir.model.access.csv and record rules so only accounting roles can register participants or resend documents, and automated actions (ir.cron / base.automation) push and poll the Access Point without manual clicking.

Because it is built for your instance, we align it with your chart of accounts, tax mapping, multi-company setup and preferred certified Access Point (your existing provider or one we recommend). You get the source code, documentation, a training session and a support window — and it keeps working across Odoo 17, 18 and 19, Community or Enterprise.

Was Sie bekommen

Production-ready Odoo module source code (models, views, security, QWeb/UBL templates) installed on your database

A complete __manifest__.py with pinned dependencies and versions for Odoo 17, 18 and 19 (Community or Enterprise)

Access Point integration configured — credentials wired to your chosen certified provider (yours or one we recommend)

Participant registration for your legal entities on the Peppol network across your target EU countries

Country/CIUS profile configuration mapped to your chart of accounts, tax codes and multi-company setup

Administrator and accounting-user documentation plus a UBL field-mapping reference for your team

A live training session for accounting and finance staff on sending, receiving and troubleshooting documents

A defined post-go-live support window with fixes, guidance and compatibility upkeep across Odoo 17/18/19

Für wen das ist

EU multi-country finance manager

Runs Odoo accounting for a group invoicing customers across several EU member states and needs one Peppol connector that handles every country's BIS profile instead of a patchwork of national tools.

Odoo implementation partner

Serves EU clients and wants a reusable, ECOSIRE-supported Peppol module they can deploy on client instances — with clean models, security rules and documentation — rather than rebuilding UBL generation from scratch each engagement.

Shared-services / AP-AR lead

Manages both outbound customer invoicing and inbound supplier bills; wants received Peppol documents to auto-land as draft vendor bills in Odoo and outbound invoices transmitted and status-tracked without leaving the ERP.

Wie EU Peppol BIS Universal E-Invoicing im Vergleich abschneidet

Kriterium	ECOSIRE	Benutzerdefinierter Build	Konkurrent	Odoo nativ
Coverage of all Peppol-eligible EU countries from one connector	Im Lieferumfang enthalten	Possible, but you build and maintain every country/CIUS profile yourself	Often single-country or a small country set per module	Nicht im Lieferumfang enthalten
Peppol BIS Billing 3.0 UBL 2.1 generation from account.move	Im Lieferumfang enthalten	You implement UBL/lxml templates and EN 16931 rules from scratch	Usually yes for its target country	Teilweise Unterstützung
Inbound reception into Odoo as draft vendor bills	Im Lieferumfang enthalten	Requires building the whole inbound parser and mapping	Sometimes; often outbound-only	Nicht im Lieferumfang enthalten
SMP/SML participant lookup and per-country CIUS handling	Im Lieferumfang enthalten	You code and maintain the lookup and profile logic	Teilweise Unterstützung	Nicht im Lieferumfang enthalten
Built, installed and configured on your instance for your countries/entities	Im Lieferumfang enthalten	You do the build and configuration yourself	Nicht im Lieferumfang enthalten	Nicht im Lieferumfang enthalten
Ongoing support and Peppol/CIUS spec upkeep across Odoo 17/18/19	Im Lieferumfang enthalten	Your team owns all future maintenance	Vendor-dependent; varies by publisher	Teilweise Unterstützung
XML-RPC / JSON-RPC access for headless send/receive/status	Im Lieferumfang enthalten	You expose and secure the endpoints yourself	Teilweise Unterstützung	Teilweise Unterstützung
Role-based security via ir.model.access.csv and record rules	Im Lieferumfang enthalten	You define all access rules	Teilweise Unterstützung	Im Lieferumfang enthalten

Häufig gestellte Fragen zu EU Peppol BIS Universal E-Invoicing

How long until the module is live, and is this an instant download?

This is a build-to-order module, not an instant apps.odoo.com download. After purchase we scope your country footprint, legal entities and Access Point, then build, install and validate the connector on your database. Typical lead time is 2–4 weeks depending on how many EU countries and legal entities you register and how much tax/chart-of-accounts mapping is involved. You get a timeline confirmed during the kickoff scoping call.

What support and updates are included after go-live?

Every build includes a defined post-go-live support window covering bug fixes, configuration guidance and compatibility upkeep. Because Peppol BIS profiles and national CIUS rules change over time, we keep the module aligned with current specifications during your support window and maintain compatibility across Odoo 17, 18 and 19. Extended support and enhancement retainers are available if you want ongoing coverage beyond the initial window.

Do I still need a Peppol Access Point provider?

Yes. Peppol requires transmission through a certified Access Point that speaks the AS4 protocol. The module is the Odoo-side connector: it builds compliant UBL, performs SMP/SML lookups, and pushes/pulls documents to and from your Access Point. We integrate with your existing certified provider, or recommend one and wire up the credentials as part of delivery.

Which EU countries and Odoo editions are supported?

The connector is designed to cover all Peppol-eligible EU member states from a single app, with per-country CIUS profile handling for localized validation rules. We configure it for the specific countries you invoice into. It runs on Odoo 17, 18 and 19, in both Community and Enterprise editions, aligned to your existing accounting configuration.

Does it handle inbound supplier invoices too, or only sending?

Both. Outbound, it converts Odoo customer invoices and credit notes to Peppol BIS 3.0 UBL and transmits them with status tracking. Inbound, it receives supplier documents from your Access Point and creates draft vendor bills in Odoo, with configurable mapping to your chart of accounts and tax codes so your AP team simply reviews and posts.

Can external systems trigger sending or check status without using the Odoo UI?

Yes. The whole flow is exposed through Odoo's standard XML-RPC / JSON-RPC API, so an external ERP, e-commerce platform or middleware can create an invoice, trigger transmission, and query delivery status programmatically. Access is still governed by Odoo's security model — ir.model.access.csv and record rules — so only authorized accounting roles can send or resend.