Peppol for developers: Getting started with electronic orders

Peppol is an international open B2B network that enables organizations to exchange structured business documents such as orders and invoices efficiently.

Understanding Peppol’s technical specifications and implementation process is critical for developers to build robust systems that enhance organizational efficiency. This guide outlines key concepts and technical guidance for developers to get started with electronic orders using Peppol.

Peppol (Pan-European Public Procurement Online) is a framework that standardizes electronic document exchange between businesses and public organizations. It is not an ERP system, portal, or procurement platform but a protocol enabling interoperability between different systems.

Peppol uses the four-corner model, meaning each organization connects to the network through its chosen Peppol Access Point provider, removing the need to align service providers with business partners.

The key features of Peppol are:

Implementing electronic orders in Peppol involves understanding its Business Interoperability Specifications (BIS), message syntax, and data exchange requirements.

Here’s a breakdown of the core six steps and their technical considerations.

Developers implementing Peppol invoices must understand how to properly populate cbc elements according to the Peppol BIS guidelines to ensure document compliance and successful transmission.

In the context of Peppol and the UBL (Universal Business Language) syntax for invoices, cbc stands for Common Basic Components. These predefined data elements within the UBL schema represent basic, reusable building blocks of business documents such as invoices, orders, and despatch advice messages.

Peppol supports three primary specifications, also called profiles, for order processes. Each BIS is designed for specific use cases, and business partners must agree on which to use.

BIS Order Only: For simple order submissions without supplier response.
BIS Ordering: Includes order responses to confirm acceptance, rejection, or partial acceptance.
BIS Despatch Advice: Informs the buyer about shipment details.

The Peppol Order transaction (T01) follows the UBL (Universal Business Language) standard.

To implement Peppol effectively, developers need a thorough understanding of how to populate cbc elements in line with Peppol BIS guidelines, ensuring both compliance and smooth transmission. Adhering to the required syntax for all document elements is essential, as deviations from Peppol’s validation rules can lead to errors that disrupt the order process.

Here are a few examples of core elements for order documents:

Data Representation: cbc elements typically represent single data fields, making them straightforward to use and validate.
Attributes: Some cbc elements include attributes like currencyID (for amounts) or unitCode (for quantities).
Mandatory/optional: The Peppol BIS (Business Interoperability Specification) guidelines specify which cbc elements are mandatory, optional, or conditionally required.

While cbc represents basic components, cac (Common Aggregate Components) is used for complex data structures that group related cbc and other cac elements. For example, cac:Party groups all information about a business entity, such as its name, address, and identifiers.

For more details on specific cbc elements used in Peppol UBL ordering, see the official Peppol BIS Ordering documentation.

Peppol transactions are distributed through certified Peppol Access Points, also called Peppol Service Providers. As a developer, your application must connect to a provider’s API to transmit and receive documents. Access Points handle the technical complexities of routing messages to and from trading partners.

Learn more about accessing Peppol orders through Order API.

Validation ensures compliance with Peppol’s rules and BIS requirements. Implement robust validation checks to identify errors before transmission. For example, check mandatory fields such as cbc:ID and cbc:DocumentCurrencyCode. Validate data formats, including dates, currencies, and identifiers.

Format validations are built-in and automated for users of Qvalia’s Peppol Access Point.

Before deploying your solution, test the integration in a sandbox environment provided by your Access Point provider. This allows you to simulate various scenarios, such as submitting orders, receiving responses, and managing despatch advice messages.

Peppol orders rely on XML-based UBL schemas. Below is a brief overview of critical elements in the order structure:

The header contains critical metadata about the order.

The buyer and seller are defined using cac:BuyerCustomerParty and cac:SellerSupplierParty segments.

Each order line specifies the items, quantities, and prices.

The BIS Despatch Advice specification enables suppliers to inform buyers about shipment details.

The message can include:

Follow Peppol BIS guidelines: Always adhere to the official Peppol BIS documentation to ensure compliance.
Handle local variations: While Peppol is a global standard, some sectors or regions may require specific adaptations.
Automate validation: Implement automated checks for syntax and content compliance before transmission.
Secure data: Ensure all transmitted data complies with GDPR and other privacy regulations.

Peppol provides a robust framework for electronic orders, enabling businesses to streamline operations and improve data accuracy. For developers, understanding the technical specifications of Peppol BIS, UBL schemas, and Access Point integration is vital in creating scalable and efficient solutions.