Aperçu illustratifA 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.
Qu'est-ce que 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.
Fonctionnalités clés
Fait sur commande, clé en main
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
- 1
Vous commandez
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
- 2
Nous développons et installons
ECOSIRE la développe, la configure et l'installe sur votre Magento 2.
- 3
Mise en ligne + assistance
Vous êtes en ligne en une semaine ouvrée environ, avec deux semaines d’assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.
À propos de ce produit
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.
Ce que vous obtenez
- 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)
Pour qui c'est
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.
Comment Magento 2 Peppol E-Invoicing se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Natif Magento 2 |
|---|---|---|---|---|
| Auto-converts Magento invoices to Peppol BIS 3.0 UBL | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Schematron validation (Peppol + EN 16931) before dispatch | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Delivery over the Peppol network via your Access Point | Inclus | Prise en charge partielle | Inclus | Non inclus |
| Buyer Peppol-ID / SMP capability lookup | Inclus | Non inclus | Prise en charge partielle | Non inclus |
| Credit-note (UBL CreditNote) support tied to credit memos | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Scoped to your tax config, store views and AP contract | Inclus | Inclus | Non inclus | Non inclus |
| Upgrade-safe code (service contracts, di.xml, ACL, no core hacks) | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Installed, tested and supported by the builder | Inclus | Non inclus | Non inclus | Non inclus |
| REST/GraphQL status endpoints for ERP sync | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
Foire aux questions sur 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.
Modules associés
Magento 2 Offline POS Mode
A build-to-order Magento 2 / Adobe Commerce extension that lets your POS keep selling with no internet connection, then auto-syncs every queued order, payment, and stock movement back to Magento the moment connectivity returns.
Magento 2 Order Management & Omnichannel Fulfillment
A unified order hub for Magento 2 / Adobe Commerce that pools web, POS and marketplace orders and routes each to the optimal store or warehouse for ship-from-store, BOPIS, split shipments and centralized fulfillment. Custom-built, installed and supported by ECOSIRE.
Magento 2 POS Create-Product-On-The-Fly
A custom-built Magento 2 / Adobe Commerce extension that lets cashiers create brand-new products and custom-priced ad-hoc line items directly at the POS, with tax, unit, and category set at the till and auto-synced to the Magento catalog. Built, installed, and supported by ECOSIRE.
Magento 2 POS Fiscalization & Receipt Compliance
Country-specific fiscal receipt compliance for Magento 2 POS — fiscal printer integration, cryptographically signed receipts, sequential fiscal numbering, local VAT breakdown and automated daily Z-report submission. Custom-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.
- 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)