AI Guide

Peppol: The pan-European network standard for electronic invoicing

Peppol (Pan-European Public Procurement OnLine) is an international network and messaging standard that lets businesses exchange structured e-invoices and procurement documents across borders without bilateral integrations. It defines a common access point model, document formats, and interoperability rules used by public and private buyers across more than 35 countries. Learn below how Peppol works, how it relates to Germany's XRechnung mandate, and what Mittelstand companies need to join the network.

Key Facts
  • Peppol connects businesses in more than 35 countries through a single standardized network
  • Germany's XRechnung format is based on the Peppol BIS Billing 3.0 specification
  • The network uses a four-corner model: sender, sender access point, receiver access point, receiver
  • OpenPeppol reports over 500 certified access point providers worldwide as of 2025
  • Public buyers in several EU member states already mandate Peppol for B2G invoice receipt

Definition: Peppol

Peppol is an international network and set of technical standards that enables businesses and public authorities to exchange e-invoices and other procurement documents electronically through certified access points, regardless of which software or country either party uses.

Core characteristics of Peppol

Peppol was built to solve a specific problem: without a shared network, every company trading across borders would need a separate technical integration with every partner. Peppol replaces that with one connection per company.

  • Governed by the non-profit association OpenPeppol, not a single vendor
  • Based on a four-corner interoperability model with certified access points
  • Defines document specifications (BIS) built on the UBL and EN 16931 standards
  • Active in over 35 countries across Europe, Asia-Pacific, and the Americas

Peppol vs. direct EDI integration

Direct EDI (Electronic Data Interchange) integration connects two trading partners through a dedicated, often custom-built technical link that both sides must configure and maintain. Peppol instead gives each participant a single connection to a certified access point, which then routes documents to any other participant on the network through standardized addressing. This means a company only sets up its connection once, rather than once per trading partner. The tradeoff is less customization per relationship, but dramatically lower integration cost at scale.

Importance of Peppol in enterprise AI

Peppol delivers invoice data in a structured, validated format before it ever reaches an accounts payable system, which removes the extraction step that intelligent document processing would otherwise need to perform on unstructured files, and feeds the data straight into automated invoice processing pipelines. According to the European Commission, Peppol has been adopted as the technical backbone for public procurement e-invoicing in more than 20 EU member states, making it the de facto standard for cross-border structured document exchange in Europe.

Methods and procedures for Peppol

Joining Peppol involves choosing an access point, mapping internal data to the required format, and testing message flows end to end.

The four-corner model

A sender (Corner 1) transmits a document to its chosen access point provider (Corner 2), which forwards it over the Peppol network to the receiver’s access point (Corner 3), which delivers it to the receiving business (Corner 4). Each access point handles routing, format validation, and delivery confirmation.

  • Corner 1 and 4: the actual trading businesses
  • Corner 2 and 3: certified access point providers, often ERP or fintech vendors
  • Peppol directory: the lookup service that resolves where a document should go

Access point selection

Companies rarely build their own access point. Instead, they subscribe to an access point service, frequently bundled into an existing ERP, accounting platform, or dedicated e-invoicing provider that is already certified by OpenPeppol. Evaluation criteria include supported document types, pricing per transaction volume, and integration depth with existing workflow automation tools.

Document mapping and validation

Outbound documents must be mapped from internal data structures into a Peppol BIS format, most commonly BIS Billing 3.0 for invoices, and validated against the underlying EN 16931 schema before transmission. Access point providers typically run this validation automatically and reject non-compliant documents before they enter the network.

Important KPIs for Peppol

Measuring Peppol adoption and performance spans technical reliability, cost, and compliance readiness.

Operational performance metrics

  • Message delivery success rate: target above 99%
  • Document validation failure rate: target below 3%
  • Average time from send to delivery confirmation: target under 5 minutes
  • Trading partners reachable via Peppol: tracked as a growing share of total volume

Strategic adoption metrics

Beyond technical performance, finance leaders track how much invoice volume flows through the network versus email or paper. Bitkom’s 2025 digitalization survey found that structured e-invoicing adoption among German B2B companies roughly doubled year over year as the domestic mandate took effect, a trend that directly expands the addressable volume for Peppol-based exchange with international partners.

Quality and compliance metrics

Access point providers should maintain schema compliance rates above 97% for outbound documents, since rejected or malformed messages create downstream reconciliation work and delay payment cycles for the receiving party.

Risk factors and controls for Peppol

Joining a shared network introduces dependency and configuration risks that differ from a point-to-point integration.

Access point provider reliability

If an access point provider has an outage or fails certification renewal, outbound and inbound document flow stops entirely for that company until service resumes.

  • Confirm the provider’s uptime history and incident response commitments
  • Keep a documented fallback process for manual invoice exchange during outages
  • Review certification status periodically rather than assuming it is permanent

Format and specification drift

OpenPeppol periodically updates BIS specifications, and documents built against an outdated version can fail validation at the receiving access point. Companies relying on a legacy integration without a maintenance contract risk silent delivery failures that surface only when a partner complains about missing invoices.

Data protection across borders

Because Peppol routes documents through access points that may be hosted outside the sender’s home country, companies handling personal data in invoice line items should confirm their provider’s hosting location and data processing terms align with GoBD retention duties and applicable EU data protection rules before onboarding.

Practical example

A 160-employee industrial components exporter in Bavaria sold to buyers across Germany, France, and the Netherlands and previously handled each country’s invoicing requirements through separate manual processes, including faxed paper invoices to some French public-sector clients. After subscribing to a Peppol access point bundled with their ERP upgrade, the company connected once and reached all three markets through the same network, including public buyers that mandated Peppol receipt.

  • Single access point connection covering invoices to Germany, France, and the Netherlands
  • Automatic BIS Billing 3.0 validation before any document leaves the building
  • Elimination of country-specific manual invoice formatting for public-sector clients
  • Delivery confirmation receipts replacing unreliable fax transmission records

Current developments and effects

Peppol’s role is expanding as EU member states align domestic e-invoicing mandates with the broader VAT in the Digital Age initiative.

Convergence with national mandates

Germany’s XRechnung specification is itself built on the Peppol BIS Billing 3.0 model, meaning companies that are Peppol-ready are largely already positioned to meet the domestic B2B e-invoicing mandate for structured formats.

  • XRechnung reuses Peppol’s core invoice data model and validation logic
  • Several EU states now require Peppol for business-to-government invoicing
  • Cross-border readiness increasingly overlaps with domestic compliance readiness

Expansion beyond invoicing

OpenPeppol has extended the network’s scope beyond invoices to include procurement documents such as orders, catalogues, and dispatch advice, positioning Peppol as infrastructure for the full procure-to-pay cycle rather than invoicing alone.

AI-assisted exception handling

As more companies receive Peppol documents automatically, AI-driven straight-through processing increasingly handles the exceptions, mismatched purchase orders or unexpected line items, that validation alone cannot resolve, while routine compliant documents post without manual review.

Conclusion

Peppol turns cross-border e-invoicing from a per-partner integration problem into a one-time network connection, and that model is becoming more relevant as EU member states converge their domestic mandates on the same underlying document standards. For German Mittelstand companies already building XRechnung capability, Peppol readiness is often a smaller additional step than it first appears. As procurement documents beyond invoices move onto the network, the case for joining early, rather than retrofitting later, continues to strengthen.

Frequently Asked Questions

What is Peppol used for?

Peppol is used to exchange structured e-invoices and other procurement documents, such as orders and catalogues, electronically between businesses and public authorities across different countries and software systems. It works through certified access points rather than direct connections between trading partners.

Is Peppol the same as XRechnung?

No, but they are closely related. XRechnung is Germany’s national e-invoicing format, and it is built on the Peppol BIS Billing 3.0 specification. A company that can generate Peppol-compliant invoices is generally close to meeting the XRechnung requirement, though the two serve different primary purposes: Peppol is the cross-border network, XRechnung is the German domestic mandate format.

Does a small or mid-sized company need to join Peppol?

It depends on trading partners. A company that only invoices domestic German customers can meet its legal obligation through XRechnung or ZUGFeRD without joining Peppol directly. Companies that invoice public-sector buyers in other EU states, or international business customers who request it, typically need Peppol access to reach those partners.

What does joining Peppol cost for a Mittelstand company?

Most companies do not build their own access point connection. Instead, they subscribe to an access point service through their existing ERP, accounting software, or a dedicated provider, often at a modest per-transaction or monthly fee layered on top of existing software costs, typically far cheaper than building bilateral EDI links with each partner.

How does Peppol relate to GDPR and data protection?

Invoice documents routed through Peppol often contain personal data such as contact names and bank details, so standard EU data protection rules apply regardless of which access point handles the message. Companies should confirm their chosen access point provider’s hosting location and data processing agreement before onboarding, particularly when documents cross into non-EU jurisdictions.

How long does it take to get Peppol-ready?

For companies already using a modern ERP or accounting platform, activating a certified access point module typically takes a few weeks, covering provider selection, configuration, and test message exchange with a trading partner. Companies without existing e-invoicing infrastructure should expect a longer timeline closer to that of a full e-invoicing implementation project.

Building better software Contact us together