A custom-built Magento 2 / Adobe Commerce extension that turns your Magento invoices into Peppol BIS Billing 3.0 UBL documents and delivers them over the Peppol network to EU B2B and public-sector buyers. Built, installed and supported by ECOSIRE on your own store. One-time license from $499.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.

A custom-built Magento 2 / Adobe Commerce extension that turns your Magento invoices into Peppol BIS Billing 3.0 UBL documents and delivers them over the Peppol network to EU B2B and public-sector buyers. Built, installed and supported by ECOSIRE on your own store.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Peppol E-Invoicing (BIS Billing 3.0) for Magento 2 is a build-to-order extension that closes the gap between Magento's native invoicing and the EU's Peppol e-invoicing mandates. When a Magento Invoice is created — through the admin, the REST/GraphQL API, or your order workflow — the module maps it to a Peppol BIS Billing 3.0 UBL 2.1 document and hands it to a configured Access Point for delivery over the Peppol network to your buyer's receiving point.
Generates Peppol BIS Billing 3.0 invoices and credit notes as UBL 2.1 XML, mapped from Magento's native sales_order_invoice and creditmemo entities
Delivers documents to a configured Peppol Access Point (your provider or one we recommend) over the live Peppol network
Validates every document against EN 16931 / BIS 3.0 business rules (Schematron) before send, surfacing BT/BG-level errors in the admin
B2B-only routing: skips B2C orders with no buyer Participant ID so consumer invoices never hit Peppol
Country-based routing rules to scope delivery to the EU markets and receiver countries you actually serve
Receiver Peppol ID (Participant ID) lookup via SMP/SML to confirm the buyer can accept the document type before sending
This is not an instant Adobe Commerce Marketplace download. ECOSIRE builds the module against your Magento 2 Open Source or Adobe Commerce version, your tax/VAT configuration, and your chosen Access Point provider, then installs and supports it on your environment. That lets us get the parts that actually break right: correct UBL semantic mapping (BT-/BG- business terms), VAT category codes, your registered Peppol Participant ID, and EN 16931 validation rules.
Technically it ships as a proper module under app/code/Ecosire/PeppolEInvoicing with a registration.php and module.xml. An observer on sales_order_invoice_save_after (or an async queue consumer for higher volumes) triggers UBL generation through a service contract interface, so your own code can call it too. Routing rules decide which invoices go to Peppol: B2B-only (skip B2C orders that have no buyer Participant ID), and country-based allow-lists. A Receiver Peppol ID lookup queries the SMP/SML to confirm the buyer can receive the document type before you send. Configuration lives under Stores → Configuration with admin ACL resources, secrets stored encrypted, and a sandbox/test endpoint so you can validate documents end-to-end before going live. Delivery status, payloads and validation errors are logged and visible in the admin grid, with a cron retry for transient Access Point failures.
Sells to other businesses across the EU and now has buyers (or national rules) requiring structured Peppol e-invoices. Needs invoices delivered automatically from Magento without a parallel manual portal.
Supplies goods or services to public buyers that only accept Peppol BIS 3.0 invoices. Needs reliable Access Point delivery, EN 16931 validation, and an audit trail of what was sent and accepted.
Owns the Magento codebase and wants a clean, service-contract-based module under app/code with proper ACL, queue support and logging — not a black-box extension they can't maintain or extend.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Peppol E-Invoicing (BIS Billing 3.0) for Magento 2 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Peppol E-Invoicing (BIS Billing 3.0) for Magento 2,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Peppol BIS Billing 3.0 UBL generation from Magento invoices | ||||
| Delivery over the Peppol network via an Access Point | ||||
| EN 16931 / Schematron validation before send | ||||
| Mapped to your specific VAT classes and tax rules | ||||
| B2B-only and country-based routing rules | ||||
| Receiver Participant ID lookup via SMP/SML | ||||
| Installed, validated in sandbox and supported on your environment | ||||
| Certified Peppol Access Point operation (provider-side) | ||||
| Source code owned by you, no module licence lock-in |
This is build-to-order, not an instant Marketplace download. After a short scoping call we confirm your Magento version (Open Source or Adobe Commerce), your VAT/tax setup and your Access Point provider. Typical delivery is around 2 to 4 weeks: we build the module, validate documents end-to-end in sandbox, then install on your staging and production environments. You receive the source code in your repository, so there's no black box.
A post-launch support window is included for bug fixes and for keeping the module compatible with your Magento upgrades and with BIS Billing 3.0 / EN 16931 spec changes (the Peppol spec is versioned and updated periodically). Because we build against your specific install, support is hands-on rather than a generic ticket queue. We can also extend the window or move to a retainer for continuous compliance monitoring.
No — the extension delivers through a Peppol Access Point, but ECOSIRE is not a certified Access Point operator and we don't pretend to be. You connect your own Access Point provider (most EU sellers already have one, or we'll recommend options). We integrate Magento to that provider's API and handle SMP/SML receiver lookup, UBL generation and validation on the Magento side.
That's exactly why it's built-to-order. UBL BIS 3.0 requires correct VAT category codes, reverse-charge handling and EN 16931 business-term mapping. We map the module to your real Magento tax classes and customer-group / country rules so the generated invoice passes validation instead of being rejected at the receiver. Generic off-the-shelf extensions usually leave this mapping to you.
Yes. Generation and delivery sit behind a Magento service contract interface, and the default trigger is an observer on sales_order_invoice_save_after. So whether an invoice is created from the admin, via REST/GraphQL, or by your custom order automation, the Peppol document is produced. For high volume we wire it through an async queue consumer so the storefront and admin stay responsive.
A custom-built Magento 2 / Adobe Commerce extension that turns your Magento invoices into Peppol BIS Billing 3.0 UBL documents and delivers them over the Peppol network to EU B2B and public-sector buyers. Built, installed and supported by ECOSIRE on your own store.