PEPPOL BIS Billing 3.0

The PEPPOL BIS formatter creates UBL XML for invoices and credit notes. It prepares document content for a PEPPOL workflow; it is not an access point and does not transmit anything over the PEPPOL network.

Output

Property	Supported behavior
Profile	PEPPOL BIS Billing 3.0
Syntax	UBL
Document type	XML only
Invoice and credit memo	Both supported

Seller endpoint

Configure a seller endpoint scheme and identifier as a verified pair. Examples include VAT identifiers, GLNs and other EAS schemes. Do not choose a scheme from the label alone; your access-point provider must confirm that the participant identifier is registered and routable.

The default CustomizationID and ProfileID match the module's PEPPOL BIS Billing 3.0 profile. Override them only when the delivery partner gives you exact values.

Buyer endpoint resolution

The formatter looks for the buyer endpoint in this order:

order extension attributes peppol_endpoint_id and peppol_endpoint_scheme;
order data fields with the same names;
billing-address VAT ID, or customer tax VAT, mapped through the module's country-to-scheme list.

The fallback is convenient, but a VAT ID is not automatically the endpoint the buyer registered. Check the result with the access-point provider.

Buyer reference

The formatter resolves BuyerReference (BT-10) from:

order data field buyer_reference;
Magento customer note on the order;
invoice or credit-memo increment ID as a final fallback.

The fallback keeps the element populated; it may still be the wrong procurement reference for the recipient. Capture the real value deliberately whenever their process requires it.

Validation and transport

The module performs deterministic PEPPOL checks for the UBL root, profile identifiers, seller and buyer endpoint schemes, line totals, VAT calculations and payable totals. This local check is separate from XSD validation, provider Schematron/business-rule checks and network delivery. The einvoice:validate CLI command does not accept PEPPOL as an XSD format.

A production flow therefore needs:

generated UBL from Magento and local PEPPOL checks;
receiver/business-rule validation required by the provider;
transmission through an access point;
delivery and rejection feedback returned to operations.

Magento's generated status covers step 1, not the remaining steps.

Email and files

PEPPOL BIS is XML-only. Automatic email attachment sends XML, while PDF-only produces no e-invoice attachment. Emailing XML is not equivalent to PEPPOL delivery.