A build-to-order Magento 2 / Adobe Commerce module that generates, validates and exchanges Peppol BIS 3.0 (EN 16931) e-invoices through your chosen Peppol Access Point. Built, installed and supported by ECOSIRE on your store. One-time license from $799.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.

A build-to-order Magento 2 / Adobe Commerce module that generates, validates and exchanges Peppol BIS 3.0 (EN 16931) e-invoices through your chosen Peppol Access Point. Built, installed and supported by ECOSIRE on your store.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
The Peppol E-Invoicing Connector for Magento 2 (EU) is a custom extension that turns your Magento orders and invoices into compliant Peppol BIS Billing 3.0 / EN 16931 documents and exchanges them over the Peppol network through your Access Point — covering the Belgium, Poland and France 2026+ mandates and other EU rollouts.
Generates Peppol BIS Billing 3.0 / EN 16931 compliant UBL XML from Magento invoices and credit notes
Schematron + EN 16931 business-rule validation runs before dispatch so invalid documents are blocked at source
Integrates with your chosen Peppol Access Point provider (transport client registered via di.xml)
Country-specific format profiles for the Belgium, Poland and France mandates, extensible to other EU members
Outbound flow: observer on sales_order_invoice_save_after plus an admin Send-to-Peppol action behind a dedicated ACL resource
Inbound flow: ingests, validates and lists received Peppol documents in an admin grid (where the Access Point exposes pull/webhook)
This is not an instant Adobe Commerce Marketplace download. It is a build-to-order engagement: ECOSIRE builds the module against your Magento version (Open Source or Adobe Commerce), wires it to your Access Point provider, installs it on your environment, and supports it. We confirm scope and lead time with you before any payment is finalised.
How it is built. The connector ships as a proper module under app/code/Ecosire/PeppolEinvoicing with a versioned module.xml. An observer on sales_order_invoice_save_after (and an admin "Send to Peppol" controller behind an ACL resource) triggers a service contract that maps the Magento invoice to an EN 16931 UBL XML payload. We use plugins/interceptors rather than core rewrites, register the Access Point transport client via di.xml, and validate every document against the EN 16931 / Schematron business rules before dispatch — so malformed invoices never leave your store.
Outbound and inbound. Outbound invoices and credit notes are queued and submitted via your Access Point; delivery status and Peppol message IDs are written back to the order. Inbound documents (where your provider supports a pull/webhook) are ingested, validated and surfaced in the admin grid. Country profile mapping (BE/PL/FR and more) handles the format and identifier nuances each tax authority requires. A REST/GraphQL endpoint and a cron retry queue round out the integration so your ERP or finance team can reconcile programmatically.
You bring the Access Point contract; we build the bridge.
A Belgian, Polish or French B2B seller on Magento whose customers will legally require structured Peppol e-invoices. Needs compliance handled inside the store they already run, not a separate portal.
Owns VAT and audit obligations and needs every issued invoice to validate against EN 16931, carry a Peppol message ID, and be traceable from the order. Cares about validation-before-send and a clean audit trail more than features.
Maintains the store and refuses core rewrites. Wants a clean module using di.xml, plugins, observers and service contracts that won't break on the next Magento or Adobe Commerce upgrade, with REST/GraphQL hooks into the wider stack.
Buy the license on ecosire.com and download the Peppol E-Invoicing Connector for Magento 2 (EU) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Peppol E-Invoicing Connector for Magento 2 (EU), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Peppol BIS 3.0 / EN 16931 compliant XML output | ||||
| Validation against EN 16931 rules before dispatch | ||||
| Country-specific profiles for BE / PL / FR mandates | ||||
| Inbound (receive) invoice flow, not just outbound | ||||
| Built against your exact Magento / Adobe Commerce version and installed for you | ||||
| Works without writing your own integration code | ||||
| Upgrade-safe (no core rewrites; di.xml, plugins, observers, service contracts) | ||||
| Includes your specific Peppol Access Point wired and smoke-tested | ||||
| Ongoing maintenance as EN 16931 / country mandates change |
No. This is a build-to-order extension. ECOSIRE builds it against your specific Magento Open Source or Adobe Commerce version, connects it to your Peppol Access Point, installs it and supports it. There is no instant Marketplace download and we don't claim one.
Typical lead time is roughly 2 to 4 weeks from a confirmed scope, depending on how many country profiles you need and your Access Point's API. We agree a firm timeline and the exact in-scope mandates with you in writing before the build starts and before payment is finalised.
Each engagement includes a post-launch support window (terms agreed up front) covering bug fixes and configuration help. Because EN 16931 rules and country mandates change, we also offer ongoing maintenance to keep the module aligned with new Peppol BIS releases and Magento/Adobe Commerce version upgrades. Update terms are confirmed before the build.
Yes. Peppol requires a certified Access Point to send and receive on the network, and that is a contract you hold with a provider. This module is the bridge between Magento and your Access Point's API; we wire it to your provider and smoke-test it with a live document.
It is built the right way — a self-contained module using di.xml, plugins/interceptors, observers and service contracts rather than core rewrites. That minimises upgrade breakage, and our maintenance option covers retesting and adjustments when you move to a new Magento or Adobe Commerce version.
A build-to-order Magento 2 / Adobe Commerce module that generates, validates and exchanges Peppol BIS 3.0 (EN 16931) e-invoices through your chosen Peppol Access Point. Built, installed and supported by ECOSIRE on your store.