示意预览A custom-built Magento 2 / Adobe Commerce module that converts your invoices into Peppol BIS 3.0 UBL,
validates them against the official schematrons, and delivers them over the Peppol network via your chosen Access Point. Built, installed and supported by ECOSIRE.
什么是 Magento 2 Peppol E-Invoicing？
A custom-built Magento 2 / Adobe Commerce module that converts your invoices into Peppol BIS 3.0 UBL, validates them against the official schematrons, and delivers them over the Peppol network via your chosen Access Point. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Magento 2 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
关于此产品
Peppol e-invoicing is now mandatory for B2B and public-sector trade across a growing list of EU and global jurisdictions, and Magento Open Source and Adobe Commerce ship nothing for it natively. This extension closes that gap.
ECOSIRE builds a dedicated module under app/code/Ecosire/PeppolEinvoicing that hooks into Magento's invoice lifecycle. When an Magento\Sales\Api\InvoiceRepositoryInterface::save() completes, an observer on sales_order_invoice_save_after (or a plugin on the invoice service, depending on your flow) maps the invoice, order, store and customer-group data into a Peppol BIS Billing 3.0 UBL document. The mapping layer is a proper service contract (Ecosire\PeppolEinvoicing\Api\UblBuilderInterface) wired through di.xml, so tax rates, unit prices, allowances and rounding follow EN 16931 semantics rather than a brittle template.
Every generated document is validated against the current Peppol and EN 16931 schematron rule sets before it leaves your store, so malformed invoices are caught in Magento admin, not rejected days later by the receiver. Delivery goes out through your Peppol Access Point (we integrate the AP/SMP provider you already use or recommend one); buyer Peppol-ID and SMP capability lookup confirms the recipient can actually receive the document type. Credit notes are handled as first-class UBL CreditNote documents tied to Magento credit memos.
Because this is build-to-order, the module is scoped to your tax configuration, store views and AP contract — not a generic one-size-fits-all download. You get clean, upgrade-safe code (no core hacks), admin ACL, configurable cron retry, and full logging.
你得到什么
- A dedicated Magento 2 module (Ecosire_PeppolEinvoicing) under app/code, written for your Magento Open Source or Adobe Commerce version with no core modifications
- Integration with your nominated Peppol Access Point / SMP provider (or a recommendation if you don't have one)
- Tax and invoice-field mapping configured to your store's tax classes, store views and EN 16931 requirements
- Installation and configuration on your staging environment, then production go-live with a validated end-to-end test send
- Admin configuration UI (system.xml) for sender Peppol-ID, endpoint scheme, AP credentials and per-store overrides
- Technical documentation: install/upgrade steps, configuration reference, and a runbook for failed-send recovery
- A defined post-launch support and update window (see FAQ)
这是给谁的
EU B2B Magento merchant facing a Peppol mandate
Sells to business and public-sector buyers in jurisdictions where Peppol e-invoicing is becoming compulsory, and needs invoices delivered compliantly without re-keying into a separate portal.
Finance / compliance lead
Owns EN 16931 and Peppol compliance and wants validation to happen before dispatch, with an auditable archive of every UBL document and credit note sent from the store.
Magento technical lead or agency
Wants an upgrade-safe module using service contracts, di.xml, observers and ACL — not core hacks — that slots cleanly into an existing Adobe Commerce or Open Source deployment and exposes status via REST/GraphQL for ERP sync.
Magento 2 Peppol E-Invoicing 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Magento 2 原生 |
|---|---|---|---|---|
| Auto-converts Magento invoices to Peppol BIS 3.0 UBL | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Schematron validation (Peppol + EN 16931) before dispatch | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Delivery over the Peppol network via your Access Point | 包含 | 部分支持 | 包含 | 不包括在内 |
| Buyer Peppol-ID / SMP capability lookup | 包含 | 不包括在内 | 部分支持 | 不包括在内 |
| Credit-note (UBL CreditNote) support tied to credit memos | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Scoped to your tax config, store views and AP contract | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Upgrade-safe code (service contracts, di.xml, ACL, no core hacks) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Installed, tested and supported by the builder | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
| REST/GraphQL status endpoints for ERP sync | 包含 | 部分支持 | 部分支持 | 不包括在内 |
关于Magento 2 Peppol E-Invoicing的常见问题
How long does delivery take and how is it installed?
Because this is build-to-order, typical delivery is around one working week from kickoff, depending on your Magento version, tax complexity and Access Point. ECOSIRE builds the module, integrates your AP/SMP provider, maps your tax configuration, then installs and configures it on your staging environment. After a validated end-to-end test send we go live on production with you. You are not downloading a generic package and wiring it up alone.
Do I need a Peppol Access Point, and can you use mine?
Yes — Peppol delivery legally requires an accredited Access Point and SMP. If you already have an AP contract we integrate against that provider's API. If you don't, we'll recommend a suitable accredited AP for your region. ECOSIRE builds the Magento integration; the AP service itself is a separate provider relationship you hold.
What about ongoing support and updates?
Every build includes a defined post-launch support window covering bug fixes and configuration help. Because Peppol BIS and EN 16931 schematron rule sets are revised periodically, and because Magento/Adobe Commerce ship regular security and minor releases, we offer an optional ongoing maintenance arrangement to keep validation rules current and the module compatible across upgrades. Terms are agreed before kickoff.
Will this work on both Magento Open Source and Adobe Commerce?
Yes. The module is built against Magento's stable APIs — service contracts, di.xml, observers/plugins, ACL — so it runs on Magento Open Source and Adobe Commerce. We target your exact version line at build time and keep the code upgrade-safe with no core overrides.
How does it handle credit notes and corrections?
When you issue a Magento credit memo against an invoice, the module generates a corresponding UBL CreditNote document that references the original invoice and sends it over Peppol the same way. Both the original invoice and the credit note are validated against the schematrons and archived for audit.
Can my ERP or middleware read the Peppol status?
Yes. The module exposes REST and GraphQL endpoints returning each document's Peppol lifecycle status (queued, validated, sent, acknowledged, failed), so your ERP or integration layer can reconcile delivery without screen-scraping the admin grid.
相关模块
Magento 2 Peppol E-Invoicing
A custom-built Magento 2 / Adobe Commerce module that converts your invoices into Peppol BIS 3.0 UBL, validates them against the official schematrons, and delivers them over the Peppol network via your chosen Access Point. Built, installed and supported by ECOSIRE.
- Auto-converts Magento invoices into Peppol BIS Billing 3.0 UBL via a service-contract mapping layer (EN 16931 semantics: line items, tax categories, allowances, rounding)
- Observer on sales_order_invoice_save_after (or invoice-service plugin) generates the document at the moment the invoice is created — no manual export step
- Schematron validation against the official Peppol + EN 16931 rule sets before dispatch, with human-readable errors surfaced in Magento admin
- Delivery over the Peppol network through your chosen Access Point (AP/SMP provider integrated via configurable API client)