What's inside
BillingPlatform as a Peppol Access Point
Certified by OpenPeppol, and what that means for delivery
Más información01
What Peppol is
A network and a standard
Peppol (Pan-European Public Procurement On-Line) began as a European Commission initiative in 2008. Today it is maintained by the OpenPeppol Association.
The name covers two things: the delivery network, and the technical specifications and procedures that govern what travels across it.
Peppol started with public procurement and is now also used between businesses. Several countries require it for some or all invoicing, covered in section 03.
02
How it works
The four-corner model
Peppol connects four parties. The sender and the recipient each use an access point, and the two access points exchange the document across the network.
A two-corner model is a direct link between two participants. A three-corner model runs through one closed provider. The four-corner model keeps the network open while letting each side choose its own provider.
The sender creates the document
The sender originates the invoice and hands it to the access point they have chosen.
The sender's access point forwards it
It receives the document and passes it across the network to the recipient's access point.
The recipient's access point receives it
It is the gateway the recipient has chosen, and it makes the document available to them.
The recipient collects it
The document arrives at its final destination and the exchange is complete.
Not every market relies on Peppol alone. Some also use national formats or platforms, which is why BillingPlatform’s support matrix lists a standard format and a local network for each market (section 05).
03
Where it is required
Mandates that matter now
Mandates differ by country, company size and transaction type, and they keep moving. This is a snapshot of three markets and one EU-wide rule, checked on 1 October 2026.
1 Jan 2025
Germany. Every business must be able to receive structured e-invoices that meet EN 16931.
1 Jan 2026
Belgium. Structured e-invoicing became mandatory for domestic B2B transactions between VAT-registered businesses, exchanged over Peppol using Peppol BIS, unless both parties agree an alternative that meets the European standard. A three-month tolerance period ended on 31 March 2026, and penalties have applied since 1 April 2026.
1 Sep 2026
France. Every VAT-registered business established in France must be able to receive e-invoices. Large and mid-sized companies must also issue them and report transaction data.
1 Jan 2027
Germany. Businesses with annual turnover above €800,000 must issue e-invoices for domestic B2B transactions.
1 Sep 2027
France. Small and medium-sized businesses and micro-enterprises must start issuing e-invoices and reporting.
1 Jan 2028
Germany. The requirement to issue extends to every business.
1 Jul 2030
European Union. Under the ViDA reform, intra-EU B2B transactions require structured e-invoices that meet EN 16931, together with digital reporting.
France routes e-invoices through approved platforms or the public invoicing portal. Check with your tax advisor which obligations apply to you and which channel is acceptable. This overview is general information, not tax or legal advice.
04
Where it is heading
More than exchange
The direction of travel is to attach tax reporting to the exchange itself, and to apply the same approach in more regions.
05
Peppol in BillingPlatform
Supported markets
| Market | Status | Standard format | Local network | Peppol support |
|---|---|---|---|---|
| Germany | Released | XRechnung (UBL/CII) | Sí | Sí |
| Austria | Released | ebInterface/UBL | Sí | Sí |
| Belgium | Released | UBL 2.1 | Sí | Sí |
| Denmark | Released | OIOUBL | Sí | Sí |
| Finland | Released | Finvoice/UBL | Sí | Sí |
| Ireland | Released | UBL 2.1 | Sí | Sí |
| Netherlands | Released | UBL 2.1 | Sí | Sí |
| Norway | Released | EHF 3.0 (UBL) | Sí | Sí |
| Sweden | Released | Svefaktura/UBL | Sí | Sí |
| France | Released with partner support | Peppol BIS 3.0 | Billit (partner) | Sí |
| Australia | Released | Peppol UBL 2.1 | Not applicable | Sí |
| New Zealand | Released | Peppol UBL 2.1 | Sí | Sí |
Status is as listed in BillingPlatform’s product documentation and release notes. Romania is also released but uses the ANAF network rather than Peppol. The France profile is released with partner support: an external partner, Billit, handles delivery and BillingPlatform supports the rest. It uses a pre-audit model over the Peppol network. Confirm availability for your organisation with your BillingPlatform contact.
What the module does
Generates the XML
Invoice and credit XML are generated using compliant XSLT templates. Generation runs automatically when an invoice is closed.
Validates it
Invoice and credit XML validation is available in the released Peppol markets above. For France, file validation is optional and off by default.
Handles credits
E-credit notes can be created from an invoice or from the ledger, with their own e-credit workflow and audit log.
Supports bulk handling
Bulk approval and bulk closure, e-invoice regeneration, and separate e-invoice and e-credit workflows are available in the released markets.
Tracks Peppol responses
Invoice and e-invoicing statuses stay pending until Peppol responds. A valid confirmation finalises the status, and a failure or rejection is shown as failed with the response logged in the e-invoice audit.
Keeps an audit trail
The e-invoicing audit records submission, delivery and acknowledgment. Changes to e-invoice templates are logged with the previous and new values, the user and the time. A separate E-invoicing log keeps the detailed request and response files for generation, validation and submission.
Email submission of e-invoices is available for Germany. The generated XML file can also be downloaded, to keep for your records or to upload to a government or other submission platform.
06
BillingPlatform as a Peppol Access Point
A certified Access Point
OpenPeppol lists BillingPlatform as a certified Access Point. That puts BillingPlatform in the Access Point corner of the four-corner model, so it communicates with the Peppol network directly.
Direct communication
E-invoices sent from BillingPlatform go into the Peppol network through BillingPlatform's own Access Point.
Responses come back to BillingPlatform
Peppol's responses are returned to BillingPlatform. Statuses stay pending until Peppol responds, and a rejection returns the invoice to the Closed state, with the error detail in the e-invoice audit.
Where a partner is involved
In France, delivery is handled by an external partner, Billit, and BillingPlatform supports the rest (see section 05).
BillingPlatform is listed for Access Point services on OpenPeppol’s list of Peppol Certified Service Providers (list updated 7 October 2026). Confirm with your BillingPlatform contact how this applies to your markets.
07
How setup works
Six steps to a submitted e-invoice
BillingPlatform’s tutorial estimates 30 to 45 minutes for the configuration, assuming you have administrative or configurator rights and the XSLT file for your market.
Menu paths below follow the product documentation.
Activate e-invoicing
To activate e-invoicing, contact BillingPlatform support. They will enable the EINVOICE_STATUS system parameter for your instance.
Create the e-invoice profile
Under Settings > Billing > E-invoice Profiles, choose the country. The implementation model, network and e-invoice format pre-populate to match local requirements. Then switch on XML generation and set the storage period in years.
Configure the e-invoice template
Under Settings > Billing > E-invoice Templates, choose the country and the document type (invoice or credit). Load the default XSLT if you want the out-of-the-box version, map the mandatory fields, and use Check Syntax to validate your expressions.
Assign them to accounts
On each account, under Billing Profile Information, select the e-invoice profile and template. An account can have one e-invoice template, and PDF and e-invoice formats can be combined.
Close the invoice
The e-invoice XML is generated when an invoice is closed or reopened, and credit memos generate e-credit XML. You can also generate it manually before approval, and each manual generation is logged in the Invoice Event History. You can also download the generated file. A separate E-invoicing audit log keeps the detailed request and response files for generation, validation and submission.
Approve the invoice
When the invoice is approved, BillingPlatform sends the e-invoice to Peppol. If the invoice is rejected, it goes back to the Closed state.
If a generated file is rejected, the e-invoice or e-credit template is faulty or, when validation is enabled, the field mapping does not match the validator’s schema requirements. An “Unmapped Field” message means a mandatory field in the XML structure has not been mapped.
08
Get started
Start with your markets
Most of the work is checking scope. The configuration itself follows the six steps in section 07.
Check your markets against the table in section 05, including the status of each.
Confirm which mandate applies to you and by when, with your tax advisor.
Check your customers can receive on Peppol. Each participant is addressed by a Peppol ID.
Ask your BillingPlatform contact to confirm availability for your organisation, activate e-invoicing, and explain how submission to Peppol is configured for your market.
Test with one account. Set up the profile, template and assignment, close an invoice, and review the generated XML and the audit entries.
Ready to talk Peppol?
Your BillingPlatform representative can confirm which markets are available to your organisation and what setup involves.