Magento 2 Peppol E-Invoicing

Key Features

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)

Buyer Peppol-ID and SMP capability lookup to confirm the receiver can accept the document type before sending

Full credit-note support: Magento credit memos map to UBL CreditNote documents linked to the original invoice

Admin grid showing per-invoice Peppol status (queued, validated, sent, acknowledged, failed) with resend action

Cron-based retry queue with exponential backoff for transient Access Point or network failures

Granular admin ACL resources so only authorized roles can view, resend, or void Peppol documents

Multi-store / multi-store-view aware: per-store sender Peppol-ID, endpoint scheme and AP credentials via system.xml configuration

REST and GraphQL endpoints to query a document's Peppol status programmatically for ERP/middleware sync

Structured logging plus archived UBL payloads for audit and dispute resolution

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

What you get

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)

Who this is for

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.

How Magento 2 Peppol E-Invoicing Compares

Criterion	ECOSIRE	Custom Build	Competitor
Auto-converts Magento invoices to Peppol BIS 3.0 UBL	Included	Partial support	Partial support
Schematron validation (Peppol + EN 16931) before dispatch	Included	Partial support	Partial support
Delivery over the Peppol network via your Access Point	Included	Partial support	Included
Buyer Peppol-ID / SMP capability lookup	Included	Not included	Partial support
Credit-note (UBL CreditNote) support tied to credit memos	Included	Partial support	Partial support
Scoped to your tax config, store views and AP contract	Included	Included	Not included
Upgrade-safe code (service contracts, di.xml, ACL, no core hacks)	Included	Partial support	Partial support
Installed, tested and supported by the builder	Included	Not included	Not included
REST/GraphQL status endpoints for ERP sync	Included	Partial support	Partial support

Frequently Asked Questions about 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 3 to 5 weeks 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.