Peppol is an international interoperability framework for exchanging structured electronic business documents, including e-invoices, orders, and despatch advices, through a network of certified Access Points governed by OpenPeppol.
Peppol stands for Pan-European Public Procurement Online, the original name from the EU-funded project that created it between 2008 and 2012. The framework was designed to let public sector buyers and their suppliers exchange procurement documents electronically across European borders without each pair of organisations needing a bespoke integration. After the project closed, governance passed to OpenPeppol, a non-profit association based in Brussels that maintains the specifications, accredits Access Point providers, and runs the registry of participants.
The framework is no longer purely European. Australia, New Zealand, Singapore, and Japan have joined as Peppol Authorities, and the network handles millions of documents per month globally. While invoicing is the most common use case, Peppol covers the full procure-to-pay and order-to-cash document set, including orders, order responses, catalogues, despatch advices, credit notes, and message-level responses.
Peppol uses what is called the 4-corner model. The sender (corner 1) connects to their Access Point provider (corner 2). That Access Point routes the document across the Peppol Network to the recipient's Access Point (corner 3), which delivers it to the receiving organisation (corner 4). Neither the sender nor the receiver needs a direct connection to each other, and they can use different Access Point providers.
Each participant on the network has a Peppol ID, also called a Participant Identifier. This is typically based on a national business registration number, such as a VAT number or a country-specific company ID, prefixed with an ISO code that identifies the scheme. The Service Metadata Locator and Service Metadata Publisher services act as the network's directory, telling a sending Access Point how to reach any given Participant ID and which document types that participant accepts.
This architecture means a business connects once to one Access Point and can reach every other participant on the network. There is no per-trading-partner setup, no VPN, and no bilateral testing cycle for each new counterparty.
Peppol BIS, short for Business Interoperability Specifications, defines the structured XML formats used on the network. The specifications are based on UBL 2.1 (Universal Business Language) and, for invoices, conform to the European standard EN 16931, which is the same semantic model that underpins most EU e-invoicing mandates.
The main document types include:
Because every document follows the same semantic model, a receiving system can process invoices from any sender on the network without bespoke mapping per trading partner.
Peppol adoption varies sharply by country. It is dominant in Norway, Sweden, Denmark, Finland, the Netherlands, Belgium, and Singapore. Many of these countries require Peppol-compliant e-invoices for business-to-government transactions, meaning suppliers selling to public sector buyers must send invoices through the network. Belgium has extended this to B2B as part of its 2026 e-invoicing mandate, and other EU member states are moving in the same direction under the VAT in the Digital Age (ViDA) proposals.
Outside Europe, Australia mandates Peppol for federal government agencies and is encouraging B2B uptake. Japan launched JP PINT, the Peppol International Invoice profile for Japan, in 2023 to support its qualified invoice system for consumption tax. Singapore's InvoiceNow programme is built directly on Peppol and is being made mandatory for GST-registered businesses in phases.
It helps to position Peppol against two other ways of exchanging structured documents. Traditional EDI is bilateral. Two trading partners agree on a format, often EDIFACT or X12, set up a direct connection, and test each message type. EDI works well for high-volume relationships but does not scale to a long tail of trading partners. Peppol is open. Once you are on the network, you can transact with every other participant without per-partner setup.
The other contrast is the clearance model, used in Italy via the SDI platform and in several Latin American countries. Clearance requires every invoice to pass through a government platform that validates and authorises it before it reaches the buyer. Peppol does not clear through government. The network handles delivery between private parties, and tax authorities receive reports separately. However, the EU is converging the two approaches under ViDA, which will introduce continuous transaction controls that sit alongside Peppol-based delivery.
Connecting to Peppol traditionally meant working with a certified Access Point provider, mapping internal data fields to UBL XML, validating against BIS schemas, and handling network errors. AI-native AR platforms are collapsing much of this work.
Modern systems automatically resolve a customer's Peppol ID from their VAT or company number, validate documents against EN 16931 and country-specific BIS rules before sending, and translate between internal data models and UBL without hand-coded mappings. When a document is rejected by the receiving Access Point, agentic workflows can interpret the error, correct the underlying data, and resend without finance team intervention. This turns Peppol from a compliance project into a routine delivery channel that runs alongside email, EDI, and direct API integrations.
Peppol is mandatory for business-to-government invoicing in many EU countries, including Belgium, the Netherlands, and the Nordics. Belgium has extended this to B2B from 2026, and other member states are moving in the same direction. Whether Peppol specifically is required depends on the country, but structured e-invoicing aligned with EN 16931 is becoming the EU baseline.
You connect through a certified Access Point provider rather than directly to the network. The Access Point handles authentication, routing, and protocol details. Many AR platforms include Peppol delivery as a built-in channel, so onboarding is a matter of activating it, registering your Peppol ID, and validating a few test documents.
A Peppol ID, or Participant Identifier, is the unique identifier that addresses your organisation on the network. It is usually based on a national business identifier such as a VAT number or company registration number, prefixed with a scheme code indicating which registry it comes from. The network's lookup services use this ID to route documents to the correct Access Point.
UBL (Universal Business Language) is the underlying XML standard for business documents. Peppol BIS is a profile that constrains UBL for use on the Peppol Network, specifying which fields are mandatory, which code lists to use, and how to align with EN 16931 for invoices. Every Peppol document is UBL, but not every UBL document is Peppol BIS compliant.
Peppol does not fully replace EDI but reduces the need for bilateral EDI setups, especially for the long tail of trading partners. High-volume strategic relationships often stay on EDI for historical or technical reasons, while Peppol handles the broader supplier and customer base with a single network connection.
Yes. Peppol is governed internationally by OpenPeppol, and Authorities have been established in Australia, New Zealand, Singapore, and Japan. Country-specific profiles such as JP PINT for Japan adapt the core specifications to local tax requirements, while keeping the same 4-corner architecture and document model.
