Peppol Dictionary/Abbreviations

This page lists some of the terms and abbreviations often used in Peppol. You can consider this an unofficial Peppol glossary. If you are missing a term drop me a note.

AISBLAssociation internationale sans but lucratif A non-profit origanisation under Belgium law. See this page for details (in French).
APAccessPoint The technical connector of a software solution that is capable of sending and/or receiving Peppol business documents
Application Statement 2 Transport protocol specified in RFC 4130. This was the default transport protocol until 2020-01-31. It was replaced with AS4. The usage of AS2 is supported until 2023-09-06 - see Transport Profiles Code List.
AS4Application Statement 4 Transport protocol specified by OASIS. It was used in the eSENS project and adopted by CEF. The Peppol AS4 profile v2 is the mandatory transport protocol in the Peppol eDelivery network since 2020-02-01.
BCBusiness Card The document type for describing the non-functional aspects of a Peppol participant for listing in the PD. It is maintained decentralized in the SMP.
BISBusiness Interoperability Specification A Peppol created specification that define how a business document exchange should take place and how the UBL elements are bound to semantical elements. The most known BIS is "Peppol BIS Billing 3" which defines the exchange of invoices and credit notes.
BLRBusiness Level Response Business document to be exchanged stating business level validation results (see also MLR). Peppol does not contain a single BLR - it contains different responses for different document types, like Order Response or Invoice Response. The usage of a BLR depends on the chosen "Process ID" which identifies the orchestration of message exchange to be used.
C1Corner 1 The "Sending End User" is Corner 1 in the 4 Corner Model.
C2Corner 2 The "Sending End User's Service Provider" is Corner 2 in the 4 Corner Model.
C3Corner 3 The "Receiving End User's Service Provider" is Corner 3 in the 4 Corner Model.
C4Corner 4 The "Receiving End User" is Corner 4 in the 4 Corner Model.
CCCoordinating Community OpenPeppol internal community that is supposed to deal with cross-community topics.
Connecting Europe Facility An instrument of the EC for funding and informing about e-Delivery, e-Invoicing etc. solutions. See The successor of CEF is the DEP programme.
CIIUN/CEFACT Cross Industry Invoice One of the two formats identified by the EN to be supported by public entities.
The previous Peppol reference implementation now maintained by EC. See Superseded by CEF -
CIUSCore Invoice Usage Specification Defines how to adopt the EN to local requirements. It implies, that a CIUS is more narrow then the underlying specification. Billing BIS 3 is a CIUS of the EN.
CMBChange Management BoardThe Peppol internal team that makes decisions. There is one CMB for TICC, PoACC and PrACC.
DNSDomain Name System Basic part of Internet technology that maps domain names to IP addresses for technical routing. Used by SML, SMP and AP.
DEPDigital Europe Programme The Digital Europe Programme (DIGITAL) is a new EU funding programme focused on bringing digital technology to businesses, citizens and public administrations. See
ECEuropean Commission Generic term for all entities directly or indirectly related to them (DG DIGIT etc.).
EDECeDelivery Domain Community The successor of TICC within OpenPeppol. See
ENEuropean Norm Usually this refers to the EN 16931-1, the European Norm on e-Invoicing. Outside of the Peppol world a multitude of different ENs exist.
EUSREnd User Statistics Report An OpenPeppol statistics report on the number of transmitted documents. See for the specification. See also TSR.
F2FFace to face This defines an event where people are meeting in real (face to face) and not just virtually in telephone conferences.
IRInternal Regulations OpenPeppol internal document that provides rules and guidance on several topics.
IRMInvoice Response Message Special BLR for invoices.
Lightweight Message ExchangeLegacy Peppol transport protocol for pulling messages. Has been discontinued.
MCManaging CommitteeThe Peppol managing board.
Message Disposition Notification The technical receipt of acknowledgment for AS2 transmissions defined in RFC 3798. The equivalent in AS4 is a SignalMessage with a Receipt or an Error.
MLAMessage Level AgreementWorking title for a work group that should deal with structured response messages. The outcome will be the MLS specification.
MLRMessage Level ResponseBusiness document to be exchanged stating technical validation results (see also BLR)
MLSMessage Level StatusThe proposed successor of the MLR specification designed by the MLA work group
OASISOrganization for the Advancement of Structured Information Standards International standardization organisation. See
OpenPeppol AISBL The organisation responsible for maintaining Peppol standards and running the transport infrastructure. See See also AISBL.
PAPeppol Authority A local authority managing and supporting the regional Service Providers. Jurisdictions not having their own PA, are managed and supported by OpenPeppol directly.
PACPeppol Authority Community OpenPeppol internal group of Peppol Authorities.
PCAPeppol Coordinating Authority The Peppol Authority that acts as the PA for all jurisdictions where none is defined. This role is fulfilled by OpenPeppol.
PDPeppol Directory A central Peppol service that should help in mapping Peppol participant IDs to the participant names and countries. See for the specification.
Pan European Public Procurement On-Line This is the European project that initiated all this. Started as a European Large Scale Pilot and is now maintained by OpenPeppol AISBL. Since middle of 2019 the abbreviation was officially replaced with "Peppol" as a noun.
PoACPost-Award Domain Community Peppol internal team to manage the post-award assets. See
Post-Award Coordinating Community The old term for PoAC.
PIDParticipant identifier This is the technical identifier for the sender and receiver of a document exchange. This is also used in an SMP as a so called "service group".
PrACPre-Award Domain Community Peppol internal team to manage the pre-award assets. See
Pre-Award Coordinating Community The old term for PrAC.
SBDStandard Business Document A generic XML envelope structure that defines a header (SBDH) and a payload. See also SBDH. See for the specification.
SBDHStandard Business Document Header The header part inside the SBD. See for the specification.
SMK Test version of the SML ('K' comes before 'L'). Currently operated by EC. See for the specification.
SMLService Metadata Locator Central Peppol service that modifies the DNS. Currently operated by EC. See for the specification.
SMPService Metadata Publisher Distributed Peppol registry. Used to lookup participant endpoint URLs. See for the specification. See for an Open Source implementation.
SPService ProviderA company or entity offering Peppol Services.
SPCService Provider Community OpenPeppol internal group of Service Providers. See for details.
Secure Trusted Asynchronous Reliable TransportLegacy Peppol transport protocol, based on the Webservice stack. Was superseded by AS2.
TICC Codelist Team Special team that takes care of the "Peppol Policy for the use of identifiers" as well as the codelists required for document exchange.
Transport Infrastructure Agreement The contract between the Peppol user and the Peppol Authority. Since July 2022 this has been superseded by the "Peppol Agreement Framework".
Transport Infrastructure Coordinating Community Peppol internal team to manage the technical assets. See Now called EDEC.
TSRTransport Statistics Report An OpenPeppol statistics report on the number of transmitted documents. See for the specification. See also EUSR.
UBLUniversal Business LanguageAn OASIS standard that defines certain XML based document types used in Peppol and the EN.
You must be logged in to post a comment!