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.
| Term | Meaning | Comments |
|---|---|---|
| AISBL | Association internationale sans but lucratif | A non-profit origanisation under Belgium law. See this page for details (in French). |
| AP | AccessPoint | The technical connector of a software solution that is capable of sending and/or receiving Peppol business documents |
|
AS2
deprecated | 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. |
| AS4 | Application 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. |
| BC | Business 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. |
| BIS | Business 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. |
| BLR | Business 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. |
| C1 | Corner 1 | The "Sending End User" is Corner 1 in the 4 Corner Model. |
| C2 | Corner 2 | The "Sending End User's Service Provider" is Corner 2 in the 4 Corner Model. |
| C3 | Corner 3 | The "Receiving End User's Service Provider" is Corner 3 in the 4 Corner Model. |
| C4 | Corner 4 | The "Receiving End User" is Corner 4 in the 4 Corner Model. |
| CC | Coordinating Community | OpenPeppol internal community that is supposed to deal with cross-community topics. |
|
CEF
deprecated | Connecting Europe Facility | An instrument of the EC for funding and informing about e-Delivery, e-Invoicing etc. solutions. See https://ec.europa.eu/digital-single-market/en/connecting-europe-facility. The successor of CEF is the DEP programme. |
| CII | UN/CEFACT Cross Industry Invoice | One of the two formats identified by the EN to be supported by public entities. |
|
CIPA
deprecated | The previous Peppol reference implementation now maintained by EC. See https://joinup.ec.europa.eu/solution/cipa-e-delivery. Superseded by CEF - https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery. | |
| CIUS | Core 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. |
| CMB | Change Management Board | The Peppol internal team that makes decisions. There is one CMB for TICC, PoACC and PrACC. |
| DNS | Domain Name System | Basic part of Internet technology that maps domain names to IP addresses for technical routing. Used by SML, SMP and AP. |
| DEP | Digital 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 https://digital-strategy.ec.europa.eu/en/activities/digital-programme. |
| EC | European Commission | Generic term for all entities directly or indirectly related to them (DG DIGIT etc.). |
| EDEC | eDelivery Domain Community | The successor of TICC within OpenPeppol. See https://peppol.eu/get-involved/join-a-community/ |
| EN | European 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. |
| EUSR | End User Statistics Report | An OpenPeppol statistics report on the number of transmitted documents. See https://docs.peppol.eu/edelivery/specs/reporting/eusr/ for the specification. See also TSR. |
| F2F | Face to face | This defines an event where people are meeting in real (face to face) and not just virtually in telephone conferences. |
| IR | Internal Regulations | OpenPeppol internal document that provides rules and guidance on several topics. |
| IRM | Invoice Response Message | Special BLR for invoices. |
|
LIME
deprecated | Lightweight Message Exchange | Legacy Peppol transport protocol for pulling messages. Has been discontinued. |
| MC | Managing Committee | The Peppol managing board. |
|
MDN
deprecated | 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.
|
| MLA | Message Level Agreement | Working title for a work group that should deal with structured response messages. The outcome will be the MLS specification. |
| MLR | Message Level Response | Business document to be exchanged stating technical validation results (see also BLR) |
| MLS | Message Level Status | The proposed successor of the MLR specification designed by the MLA work group |
| OASIS | Organization for the Advancement of Structured Information Standards | International standardization organisation. See https://www.oasis-open.org/. |
| OpenPeppol AISBL | The organisation responsible for maintaining Peppol standards and running the transport infrastructure. See http://peppol.eu/. See also AISBL. | |
| PA | Peppol Authority | A local authority managing and supporting the regional Service Providers. Jurisdictions not having their own PA, are managed and supported by OpenPeppol directly. |
| PAC | Peppol Authority Community | OpenPeppol internal group of Peppol Authorities. |
| PCA | Peppol Coordinating Authority | The Peppol Authority that acts as the PA for all jurisdictions where none is defined. This role is fulfilled by OpenPeppol. |
| PD | Peppol Directory | A central Peppol service that should help in mapping Peppol participant IDs to the participant names and countries. See https://docs.peppol.eu/edelivery for the specification. |
|
PEPPOL
deprecated | 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. |
| PoAC | Post-Award Domain Community | Peppol internal team to manage the post-award assets. See https://peppol.eu/get-involved/join-a-community/ |
|
PoACC
deprecated | Post-Award Coordinating Community | The old term for PoAC. |
| PID | Participant 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". |
| PrAC | Pre-Award Domain Community | Peppol internal team to manage the pre-award assets. See https://peppol.eu/get-involved/join-a-community/ |
|
PrACC
deprecated | Pre-Award Coordinating Community | The old term for PrAC. |
| SBD | Standard Business Document | A generic XML envelope structure that defines a header (SBDH) and a payload. See also SBDH. See https://docs.peppol.eu/edelivery for the specification. |
| SBDH | Standard Business Document Header | The header part inside the SBD. See https://docs.peppol.eu/edelivery for the specification. |
| SMK | Test version of the SML ('K' comes before 'L'). Currently operated by EC. See https://docs.peppol.eu/edelivery for the specification. | |
| SML | Service Metadata Locator | Central Peppol service that modifies the DNS. Currently operated by EC. See https://docs.peppol.eu/edelivery for the specification. |
| SMP | Service Metadata Publisher | Distributed Peppol registry. Used to lookup participant endpoint URLs. See https://docs.peppol.eu/edelivery for the specification. See https://github.com/phax/phoss-smp for an Open Source implementation. |
| SP | Service Provider | A company or entity offering Peppol Services. |
| SPC | Service Provider Community | OpenPeppol internal group of Service Providers. See https://openpeppol.atlassian.net/wiki/spaces/SPC/overview for details. |
|
START
deprecated | Secure Trusted Asynchronous Reliable Transport | Legacy Peppol transport protocol, based on the Webservice stack. Was superseded by AS2. |
|
TCT
deprecated | 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. |
|
TIA
deprecated | 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". |
|
TICC
deprecated | Transport Infrastructure Coordinating Community | Peppol internal team to manage the technical assets. See https://peppol.org/join/?membership. Now called EDEC. |
| TSR | Transport Statistics Report | An OpenPeppol statistics report on the number of transmitted documents. See https://docs.peppol.eu/edelivery/specs/reporting/tsr/ for the specification. See also EUSR. |
| UBL | Universal Business Language | An OASIS standard that defines certain XML based document types used in Peppol and the EN. |