One Peppol ID is a unique global identifier that identifies a company as a participant in the Peppol network. In the context of SAP Business One, it serves as a digital „address" for electronic document exchange – for example, when sending and receiving e-invoices in the format XInvoice or Peppol BIS.
The Peppol ID is not a master data field in SAP Business One, but rather a configuration parameter of the integration landscape. It is stored as a participant ID in the SAP BTP subaccount and connected to the Peppol network via the Integration Framework for SAP Business One (B1if). The architecture follows SAP's recommended path via SAP Document and Reporting Compliance, cloud edition, and utilises the Cloud Connector as a bridge between the On premiseThe system and the cloud.
The document flow is as follows: SAP Business One creates and posts a document → the Integration Framework transforms it into a Peppol-compliant format (UBL/CII) → its own Peppol ID and that of the recipient are embedded as routing metadata → the document is handed over via the Cloud Connector to SAP Document and Reporting Compliance → from there, it is delivered to the recipient's Peppol Access Point. The receiving path works in reverse.
For the storage of a business partner's Peppol ID within SAP Business One, there is no standard field. If required, a user-defined field (UDF) of type „Alphanumeric" can be created in the OCRD table (e.g., `U_PEPPOL_ID`) to store the recipient ID directly at Business partner master record to be deposited and integrated into the transformation rules of the Integration Framework.
Technical requirements
The setup requires several components in a defined order: (1) Registration as a Peppol participant with assignment of the Peppol ID, (2) Configuration in the SAP BTP subaccount with participant ID and Access Point URL, (3) Setup of the Cloud Connector with correct access controls and trust relationships, (4) Installation and activation of the Peppol package in the Integration Framework (SAP Note 2915144), (5) Creation of connectors in the Electronic Document Service (EDS). Performance-related factors include network latency across the entire integration chain, transformation time at high document volume, and the scaling of BTPServices.
Demarcation
The Peppol ID is not associated with a VAT identification number or a GLN (Global Location Number) equivalent, even if these can serve as part of the Peppol identification scheme. It is a pure network identifier for routing electronic documents — not a tax or commercial identifier. Companies that exclusively use national channels such as the ZRE Portal (XRechnung) to public clients do not necessarily require a Peppol ID. However, as soon as cross-border B2B exchange via the Peppol network is desired, it is essential.
E-invoicing in Europe: Harmonised standard and national fragmentation
E-invoicing in SMEs: The clock is ticking
France E-invoicing 2026: What companies with a French tax number need to know now
Service description in the e-invoice: How much detail really needs to be included?
Verifactu in Spain: the new invoicing obligation
The e-invoicing regulations in Europe
The advantages of the e-bill 2025
E-bill 2025 FAQs
Preparation for the introduction of CKS.EINVOICE