Peppol E-Invoicing (BIS Billing 3.0) for Magento 2

核心功能

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

Sandbox / test-environment toggle to validate UBL and Access Point delivery without touching production receivers

Triggered by an observer on sales_order_invoice_save_after, with an optional async queue consumer (RabbitMQ / db) for high invoice volumes

Exposed as a Magento service contract interface so your order workflow, REST or GraphQL endpoints can request generation or delivery

Admin configuration under Stores -> Configuration with dedicated ACL resources; seller Participant ID, VAT IDs and Access Point keys stored encrypted

Delivery log grid in the admin showing status, raw UBL payload and validation errors per invoice, with re-send action

Cron-based retry for transient Access Point / SMP failures so a temporary outage doesn't silently drop an invoice

VAT category code and tax mapping aligned to your Magento tax classes and the buyer's country (reverse-charge, exempt, standard)

Configurable Magento system.log / monolog channel for Peppol delivery so issues are traceable in your existing logging stack

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Magento 2 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

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.

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.

你得到什么

A Magento 2 module installed under app/code/Ecosire/PeppolEInvoicing (or supplied as a Composer package for your deployment pipeline)

UBL BIS Billing 3.0 mapping configured to your real VAT setup, tax classes and registered Peppol Participant ID

Integration wired to your chosen Peppol Access Point provider, validated in sandbox then switched to production

Admin configuration section with ACL roles, encrypted credential storage and the delivery-log grid enabled

Sandbox validation run: sample invoices generated, EN 16931-validated and test-delivered before go-live

Composer/setup-upgrade install notes plus a short runbook covering routing rules, retries and re-send

Source code handed to you in your repository — no licence lock-in on the module itself

Post-launch support window for fixes, Magento version compatibility and BIS 3.0 spec updates (see FAQ)

这是给谁的

EU B2B Magento seller facing a mandate

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.

Public-sector / government supplier

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.

Adobe Commerce technical lead / agency

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.

Peppol E-Invoicing (BIS Billing 3.0) for Magento 2 如何比较

标准	伊科西尔	定制建造	竞争对手	Magento 2 原生
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	包含	包含	不包括在内	包含

关于Peppol E-Invoicing (BIS Billing 3.0) for Magento 2的常见问题

How long until it's live on my store, and how is it delivered?

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.

What ongoing support and updates are included?

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.

Does ECOSIRE provide the Peppol Access Point itself?

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.

Will it work with my Magento tax and VAT configuration?

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.

Can my own code or order workflow trigger invoice generation?

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.