Peppol Documents in Tickstar SMP

Tickstar SMP supports all message types (documents) approved for use in the Peppol eDelivery Network. The table below contains the Peppol documents currently in the Tickstar SMP database.

If you would need explanations for the column names, please refer to the document “Policy for use of identifiers” which can be found on https://docs.peppol.eu/edelivery.

If you have suggestions, questions, find errors or know about PEPPOL documents not listed here, please let us know.

The Peppol Document Type Identifier follows the general pattern:

<syntax specific id>##<customization id>::<version>

• <syntax specific id> identifies the base syntax used for the document.
  For XML-based documents, this is a combination of the document’s namespace URI and its root element name, separated by double colons: <document element namespace URI>::<document element local name>
• <customization id> uniquely identifies the specification or set of business rules that the document complies with (for example, a Peppol BIS 3 or PINT specification).
• <version> indicates the version of the underlying syntax (e.g. UBL 2.1).

The DocumentIdentifier is included in the SBDH under <BusinessScope>, inside a <Scope> element where <Type> is set to DOCUMENTID.

The schema value for DocumentIdentifier can be either busdox-docid-qns or peppol-doctype-wildcard (case-sensitive).
Use busdox-docid-qns for traditional Peppol BIS document types, and peppol-doctype-wildcard for PINT and other document types using the Peppol wildcard scheme.

The schema value for a specific ProcessIdentifier (ProfileId) can be found in the table.

The table below contains all the available documents that have been added to the Tickstar SMP.