This page lists some of the terms and abbreviations often used in PEPPOL. 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
AS2Application Statement 2 Transport protocol specified in RFC 4130.
in progress
Application Statement 4 Transport protocol specified by OASIS. It was used in the eSENS project and adopted by CEF. PEPPOL is currently investigating a transition to AS4.
BISBusiness Interoperability SpecificationA PEPPOL created specification that define how a business document exchange should take place and how the UBL elements are bound to semantical elements.
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 an Order Response and an Invoice Response.
Business CardThe document type for describing the non-functional aspects of a PEPPOL participant for listing in the PD.
CEFConnecting Europe Facility An instrument of the EC for funding and informing about e-Delivery, e-Invoicing etc. solutions. See
CIIUN/CEFACT Cross Industry InvoiceOne of the two formats identified by the EN to be supported.
The previous PEPPOL reference implementation now maintained by EC. See Superseded by CEF -
in progress
Core Invoice User SpecificationDefines how to adopt the EN to local requirements.
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.
ECEuropean CommissionGeneric term for all entities directly or indirectly related to them (DG DIGIT etc.).
in progress
European NormUsually this refers to the EN 16931-1, the European Norm on e-Invoicing.
F2FFace to face This defines an event where people are meeting in real (face to face) and not just virtually in telephone conferences.
in progress
Invoice Response Message Special BLR for invoices.
Lightweight Message ExchangeLegacy PEPPOL transport protocol for pulling messages. Has been discontinued.
MCManaging CommitteeThe PEPPOL managing board.
MDNMessage Disposition Notification The technical receipt of acknowledgment for AS2 transmissions defined in RFC 3798.
MLRMessage Level ResponseBusiness document to be exchanged stating technical validation results (see also BLR)
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.
in progress
PEPPOL Directory A central PEPPOL service that should help in mapping PEPPOL participant IDs to the participant names and countries.
PEPPOLPan 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.
PoACCPost-Award Coordinating Community PEPPOL internal team to manage the post-award assets. See
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".
PrACCPre-Award Coordinating Community PEPPOL internal team to manage the pre-award assets. See
SBDStandard Business Document A generic XML envelope structure that defines a header and a payload. See also SBDH.
SBDHStandard Business Document Header The header part inside the SBD.
SMK Test version of the SML ('K' comes before 'L'). Currently operated by CEF.
SMLService Metadata Locator Central PEPPOL service that modifies the DNS. Currently operated by CEF.
SMPService Metadata Publisher Distributed PEPPOL registry. Used to lookup participant endpoint URLs. See for an Open Source implementation.
Secure Trusted Asynchronous Reliable TransportLegacy PEPPOL transport protocol, based on the Webservice stack. Was superseded by AS2.
TCTTICC 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.
TIATransport Infrastructure AgreementThe contract between the PEPPOL user and the PEPPOL Authority
TICCTransport Infrastructure Coordinating Community PEPPOL internal team to manage the technical assets. See
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!