PEPPOL BIS vs Peppol Delivery in Magento 2

“Supports Peppol” can mean two very different things. A solution may generate an invoice that follows PEPPOL BIS Billing rules, or it may connect to the Peppol network and deliver that document. A Magento project often needs both, but they are separate responsibilities.

Layer 1: the invoice file

PEPPOL BIS Billing 3.0 defines how invoice and credit-note business information is represented in UBL. The file includes a customization identifier, process profile, supplier and customer information, electronic endpoint identifiers, lines, taxes, totals, payment data, and references. Validation rules check more than basic XML syntax.

SoftwareSilo E-Invoice creates PEPPOL BIS Billing 3.0 UBL from Magento invoices. It can resolve seller and buyer endpoint identifiers and also supports BIS credit notes. The generated file can be validated and stored with the Magento document.

Layer 2: the network

The Peppol network uses certified Access Points to exchange documents. Network delivery involves participant discovery, addressing, transport, security, receipts, and operating responsibilities. A valid BIS file does not enter that network by itself.

SoftwareSilo does not include an Access Point, AS4 transport, or participant registration. If the recipient requires Peppol delivery, the merchant needs an Access Point provider or an integration service. The connection then needs its own authentication, retry, status, and support design.

Why endpoint identifiers matter

A Peppol participant is addressed through an identifier and scheme, not merely an email address. Incorrect schemes, missing endpoint IDs, or an unregistered recipient can stop delivery even when invoice totals are correct. Agree where buyer endpoint data lives in Magento and who keeps it current.

A complete Magento flow

Magento creates the commercial invoice.
SoftwareSilo maps seller, buyer, line, tax, payment, and reference data into PEPPOL BIS UBL.
Validation checks the document against the implemented rules.
An Access Point integration receives the file and target identifier.
The network resolves and delivers the document.
Delivery and rejection statuses return to the responsible team.
The original structured document and audit evidence are retained.

Questions for an Access Point provider

Which countries, document types, and participant schemes are supported?
How are Magento files submitted: API, SFTP, email, or another connector?
Which technical and business statuses are returned?
Who handles participant registration and directory changes?
Where are documents stored, and for how long?
How are retries, duplicate protection, and incidents handled?

Keeping format generation and transport separate makes purchasing clearer. It also prevents a successful XML validation from being mistaken for successful delivery.

Sources

Last reviewed: August 9, 2026.

PEPPOL BIS Billing Files vs Peppol Network Delivery in Magento 2