Skip to Content
E-Invoicing Deep Dive

Odoo Peppol:
Community vs Enterprise

Wondering whether you need Odoo Enterprise to send and receive Peppol e-invoices? The short answer may surprise you. Here is exactly what each edition gives you and the one small gap that actually matters.

Talk to an Odoo E-Invoicing Expert See the Comparison
Peppol Access Point Built In Community Supported BIS Billing 3.0 / XRechnung / NLCIUS No Third-Party AP Needed

The Bottom Line

For Peppol specifically, there is almost no feature gap between Odoo Community and Odoo Enterprise. The entire Peppol stack ships as free, open-source Community modules. Registering on the Peppol network, sending customer invoices and credit notes, and receiving vendor bills and refunds all work identically in both editions. Peppol registration is free, and Odoo acts as both your Access Point and SMP, so you do not need a third-party Access Point subscription. The only real difference is one downstream routing convenience for incoming bills, which depends on the Enterprise-only Documents app.
Send invoices via Peppol, works in both editions
Receive vendor bills via Peppol works in both editions
Registration is free, no third-party Access Point fee
One gap: "Receive in Documents" routing requires Enterprise

What Is Peppol?

Peppol is an international network that lets businesses and government bodies exchange structured electronic documents, primarily invoices, through certified Access Points, without email or paper. As mandatory B2B e-invoicing rolls out across Europe and beyond, having an ERP that connects to Peppol natively is shifting from a nice-to-have to a legal requirement. Odoo connects to this network directly, acting as its own Access Point, meaning you do not need to subscribe to a separate Peppol service provider.

International e-invoicing network across 40+ countries
Structured XML documents, tamper-proof, audit-ready
Mandatory for B2B invoicing in a growing number of jurisdictions
Odoo is a certified Access Point no third-party subscription needed

Peppol in Community vs Enterprise

Every Peppol capability, mapped against each edition. Rows marked in amber require Enterprise.

Peppol Capability Odoo Community Odoo Enterprise
account_peppol module (Peppol Access Point connector) Included Included
Module dependencies ( account_edi_proxy_client, account_edi_ubl_cii, certificate, account) All Community Same
Peppol registration (Odoo as Access Point + SMP) Free Free
Demo / test mode (register with "Odoo Demo ID" endpoint) Yes Yes
Send Customer Invoices and Credit Notes via Peppol Yes Yes
Receive Vendor Bills and Refunds via Peppol Yes Yes
Supported formats -- BIS Billing 3.0, XRechnung CIUS, NLCIUS Yes Yes
Contact / participant verification Yes Yes
"Receive in Journal" (incoming bills routed to a purchase journal) Yes Yes
"Receive in Documents" (incoming bills routed to a Documents workspace) Requires Documents app Yes -- Documents included

The One Gap That Actually Matters

When you configure how incoming Peppol vendor bills land in Odoo, you choose between two options. One works in both editions. The other requires Enterprise.

Community + Enterprise
Option 1 -- Receive in Journal

Incoming Peppol bills flow directly into a purchase journal, ready for processing. This is the standard workflow and works identically in both Community and Enterprise. For most businesses, this is all you need.

Enterprise Only
Option 2 -- Receive in Documents

Incoming bills land in a Documents app workspace first, which is useful when you run multiple purchase journals and want a triage or approval step before posting. The Documents app is Enterprise-only, it is not available in Community.

That is the entire gap. In Community, you use "Receive in Journal", and you still receive every Peppol document. Everything else commonly attributed to "Enterprise", OCR digitisation of incoming bills, full Accounting reporting, and advanced reconciliation, is adjacent tooling, not part of the Peppol connection itself. If your question is strictly "can I do Peppol on Community?", the answer is yes.

How Peppol Setup Works in Odoo

The setup flow is the same regardless of edition. Most businesses live within one working day.

1
Install the Peppol Module

Install account_peppol and its dependencies ( account_edi_proxy_client, account_edi_ubl_cii, certificate). All are Community modules and available at no extra cost.

2
Activate Electronic Invoicing

Go to Accounting / Invoicing → Configuration → Settings and click Activate Electronic Invoicing.

3
Set Your Peppol Endpoint Identifier

Select the country-specific Peppol endpoint identifier and enter your endpoint, usually your Company Registry number or VAT number.

4
Activate Peppol

Click Activate Peppol. Registration goes into pending status and is typically activated automatically within one business day.

5
Send Your First Invoice

Open a confirmed invoice, click Send, enable the Peppol e-invoicing format, and send. Odoo generates and attaches the XML automatically -- no manual file handling required.

Testing before going live? Register using the "Odoo Demo ID" endpoint identifier to send and receive in test mode without transmitting real data. Switch to production by deregistering from demo and registering with your live endpoint.

Which Edition Should You Choose?

The decision is rarely about Peppol itself. It is about everything around it.

Choose Community If...

Peppol on a Lean Stack

Your priority is compliant Peppol sending and receiving on a budget
You are comfortable using the "Receive in Journal" workflow for incoming bills
You do not need the broader Enterprise accounting suite or Documents app
You want to validate Peppol compliance before committing to a full ERP upgrade
Community gives you 100% of the Peppol sending and receiving capability. You are not missing any part of the actual e-invoicing network connection.
Choose Enterprise If...

Peppol Inside a Full ERP

You want incoming bills routed into a Documents workspace for triage before posting
You need OCR digitisation for non-Peppol incoming invoices alongside your Peppol flow
You need full Accounting with advanced reporting, reconciliation, and multi-company support
Auditability at scale, long-term archiving, and multi-jurisdictional compliance matter
Enterprise is the better fit when Peppol is one piece of a larger finance and operations workflow, not a standalone invoicing requirement.

Frequently Asked Questions

Yes. Peppol registration is free and the account_peppol connector is a Community module. Odoo acts as your Access Point and SMP, so no separate Access Point subscription is required. You pay nothing extra to connect to the Peppol network.

Yes. You can send customer invoices and credit notes, and receive vendor bills and refunds, in both Community and Enterprise. There is no difference in the core sending and receiving capability between editions.

BIS Billing 3.0, XRechnung CIUS, and NLCIUS, in both Community and Enterprise. These formats cover the requirements for most European jurisdictions including Germany, the Netherlands, and countries using the Pan-European standard.

The "Receive in Documents" routing option for incoming bills, because it relies on the Enterprise-only Documents app. You can still receive every Peppol document, they just go directly into a purchase journal rather than a Documents workspace. For most businesses this is not a meaningful limitation.

The Peppol module depends on the Invoicing module ( account). The Accounting app includes everything Invoicing does, but you can run Peppol on Invoicing alone. If you need full accounting features, reconciliation, reporting, multi-currency, you will want the Accounting app, but it is not a Peppol requirement.

Not Sure Which Odoo Edition Fits Your E-Invoicing Needs?

Whether you are preparing for a B2B e-invoicing mandate or just modernizing your invoicing workflow, we can help you assess readiness, map your invoice processes, and configure Peppol correctly the first time.

Book a Consultation See Our Work