Peppol Reporting Specifications
Peppol End User Statistics Reporting Process
peppol

Peppol End User Statistics Reporting Process

OpenPeppol AISBL, eDEC v1.1.1

This document sets out the processes and procedures for reporting End User Statistics data in the Peppol environment.

1. Introduction

End User Statistics reporting of production data helps OpenPeppol as the Peppol Coordinating Authority (PCA) and Peppol Authorities (PAs) to monitor the operations of the Peppol Network and identify and manage risks and issues within the network. The reporting requirements towards Service Providers (SPs) are divided into two areas: reporting about End User Statistics and reporting about Transaction Statistics. This document will explain and outline the procedures for the End User Statistics Reporting. The policy on reporting is stated in Internal Regulations for Use of the Peppol Network.

1.1. Document Structure

This document is structured as follows:

  • Chapter 1 (Introduction) - provides general information about End User Statistics Reporting business process.

  • Chapter 2 (Reporting Business Process) - provides the reader with information on how to implement the End User Statistics Reporting process.

  • Chapter 3 (Description of selected parts of the transaction) - provides the reader with functional information for the End User Statistics Reporting Process.

  • Chapter 4 (Rules) - provides the reader with information on the business rules to be respected for the End User Statistics Reporting Process.

  • Chapter 5 (Data Types) - provides the details on the used data types in an End User Statistics Report.

  • Chapter 6 (Code Lists) - provides the details on the used code lists in an End User Statistics Report.

  • Chapter 7 (Specification Identifiers) - provides the details on the customization and process identifiers.

1.2. Scope

This document is concerned with clarifying the requirements for ensuring compliance to the Internal Regulations (IR) requirements and provides guidelines for the support and implementation of these requirements. This document will also provide a detailed implementation guideline for the End User Statistics Report transaction; to do that, the document sets out the processes and procedure for End User Statistics Reporting process including:

  1. Parties and Roles,

  2. Document Structure,

  3. Data gathered,

  4. Reporting rules.

1.3. Audience

  • OpenPeppol

    • How OpenPeppol will receive the reports.

  • Service Provider (SP)

    • How SPs are to submit their End User Statistics Reports to OpenPeppol.

1.4. References

1.5. Namespaces

The following table lists XML namespaces that are used in this document. The choice of any namespace prefix is arbitrary and not semantically significant.

Prefix Namespace URI

eusr

urn:fdc:peppol:end-user-statistics-report:1.1

1.6. Changelog

Version 1.1.1 (2023-12-11)

  • Updated the Schematron rules to v1.1.4

  • Fixed some editorial bugs

  • Added a statement, that empty subsets are not allowed

  • Updated the example in Appendix 1 and Appendix 2 to be fully consistent

Version 1.1.0 (2023-06-30)

  • Reworked from "End User Report" to "End User Statistics Report"

  • Updated XML Schema

  • Updated Schematron rules

Version 1.0.0 (2022-11-23)

  • Initial version

2. Reporting Business Process

2.1. Parties and Roles

The following Parties are involved in the creation and submission of an End User Statistics Report.

2.1.1. Service Provider (SP)

The reporting Service Provider is mandatory information in each End User Statistics Report.

Each SP will:

  • Collect relevant data, taking care of the accuracy and validity of this data.

  • Report this data in accordance to this document in a standardized and structured dataset.

  • Ensure all data for a Reporting Period is reported within the Statistics Report Submitting Period following the end of the Reporting Period.
    Note: the Reporting Period and the Statistics Report Submitting Period are defined by OpenPeppol in a separate document.

  • Transmit the Peppol End User Statistics Reporting document to OpenPeppol in accordance with this specification.

2.1.2. OpenPeppol Operating Office (OO)

OO will:

  • Automatically check which providers have not submitted their End User Statistics Report. This check will be triggered automatically.

  • Prompt any SPs that have not submitted the End User Statistics Report.

  • Prompting will be done by email and not by eDelivery.

  • Prompt the PA of the SP if an SP fails to provide full and complete reports. The PA of the SP will be informed to handle this as a non-compliance issue

2.2. End User Statistics Reporting Process

The following diagrams provide an overview of the key steps when SPs are reporting End User Statistics:

eusr process simple

Using detailed Archimate notation:

eusr process view

2.2.1. Data Gathering

  • Reporting Period

    • The exact length of a Reporting Period is defined external to this document.

    • A Reporting Period starts at 00:00:00 UTC (inclusive) of the first day.

    • A Reporting Period ends at 23:59:59 UTC (inclusive) of the last day.

  • Data

    • Only SPs operating a production Peppol Access Point MUST gather this data and transmit an End User Statistics Report.

    • Only Data for the production network MUST be gathered.

    • The following data elements MUST be provided for each End User Statistics Report

      • Number of distinct End Users that have sent a Dataset

      • Number of distinct End Users that have received a Dataset

      • Number of distinct End Users that have sent or received a Dataset

      • Peppol Dataset Type (Document Type ID) and Process ID

      • End Users Country Code

    • Only Dataset exchanges that resulted in a positive transport level acknowledgment (like AS4 Receipts) MUST be included in the End User Statistics Report. Transmissions that failed on a network or protocol level MUST NOT to be considered for the report.

    • End User Statistics Reports MUST NOT be counted for an End User Statistics Report.

    • Transaction Statistics Reports MUST NOT be counted for an End User Statistics Report.

If the same End User is represented with multiple Participant Identifiers, the data needs to be gathered per End User and NOT per Participant Identifier.

2.2.2. Data Preparation

Before the End User Statistics Report data is transmitted to OpenPeppol it needs to be prepared in subsets. The preparation can be performed on any of the above-mentioned data elements.

If there are end users who have sent / received transactions within the reporting period, then the following subsets MUST be prepared to be compliant with this specification.

  • Dataset Type ID (Document Type ID) and End Users Country

  • End Users Country

  • Dataset Type ID (Document Type ID) and Process ID

  • Dataset Type ID (Document Type ID) and Process ID and End Users Country

2.2.3. Data Transmission

  • Frequency

    • An End User Statistics Report MUST be transmitted once per Reporting Period.

    • An End User Statistics Report MUST be transmitted within the Statistics Report Submitting Period after the end of the previous Reporting Period.

    • The End User Statistics Report MUST be transmitted, even if no other Peppol transactions happened in the Reporting Period.

    • In case the End User Statistics Report of one SP is received multiple times for one Reporting Period, only the latest received document will be processed.

    • End User Statistics Reports received after the deadline (=the end of the Statistics Report Submitting Period) WILL NOT be processed.

  • Data

    • Only End User Statistics Reports on the Production environment MUST be transmitted.

    • Each Subset key combination MUST NOT occur more than once in an End User Statistics Report.

    • The data of each End User Statistics MUST be reported in the designated elements.

    • The Reporting Period MUST be part of the End User Statistics Report.

    • An identifier uniquely identifying the reporting SP MUST be part of the End User Statistics Report.

  • Network

    • End User Statistics Reports MUST be transmitted via the Peppol eDelivery Network.

    • Only OpenPeppol is allowed to receive End User Statistics Reports directly.

3. Description of selected parts of the transaction

Description of selected parts of the End User Statistics Report message.

3.1. Header

The element Header contains the reporting period and the ID of the reporting Service Provider.

Example:
<eusr:Header>
  <eusr:ReportPeriod>
    <eusr:StartDate>2022-01-01</eusr:StartDate>
    <eusr:EndDate>2022-01-31</eusr:EndDate>
  </eusr:ReportPeriod>
  <eusr:ReporterID schemeID="CertSubjectCN">POP000360</eusr:ReporterID>
</eusr:Header>

3.1.1. Reporting Period

The element ReportPeriod MUST contain the start date (inclusive) and the end date (inclusive) of the reporting period. The start date can never be after the end date. Start date and end date elements MUST NOT contain time zone information.

Example (for a monthly Reporting Period):
<eusr:ReportPeriod>
  <eusr:StartDate>2022-01-01</eusr:StartDate>
  <eusr:EndDate>2022-01-31</eusr:EndDate>
</eusr:ReportPeriod>

3.1.2. Reporter Identification

The element ReporterID MUST contain the unique identification of the Service Provider that is providing the data. If the schemeID attribute is set to CertSubjectCN than the value must be the Peppol AP Certificate Subject CN (Common Name). See Reporter Identification Scheme for the full code list.

Example:
<eusr:ReporterID schemeID="CertSubjectCN">POP000360</eusr:ReporterID>

3.2. Full Set Information

Defines the overall amount of end users that have exchanged datasets in the Reporting Period. The element FullSet and its child elements MUST be provided for every End User Statistics Report.

The element eusr:FullSet/eusr:SendingEndUsers contains the overall number of distinct end users that have sent datasets. Only values ≥ 0 are allowed.

The element eusr:FullSet/eusr:ReceivingEndUsers contains the overall number of distinct end users that have received datasets. Only values ≥ 0 are allowed.

The element eusr:FullSet/eusr:SendingOrReceivingEndUsers contains the overall number of distinct end users that have either sent or received datasets. Only values ≥ 0 are allowed.

Example of a FullSet element with 9 sending, 4 receiving and 12 sending or receiving end users:
  <eusr:FullSet>
    <eusr:SendingEndUsers>9</eusr:SendingEndUsers>
    <eusr:ReceivingEndUsers>4</eusr:ReceivingEndUsers>
    <eusr:SendingOrReceivingEndUsers>12</eusr:SendingOrReceivingEndUsers>
  </eusr:FullSet>

The following non-normative diagram shows an overview of the theoretical concept of sets behind End User Statistics. Each shape represents a group of end users. The Full Set is comprised from the outer green and blue shapes. The overlapping part of green and blue indicate the end users that did send and receive. The orange shape indicates the subset of end users that deals with invoices - this affects both sending and receiving end users. The inner yellow indicates the subset of End Users that deals with invoices from/to Finland (FI) and hence is a subset of the orange shape.

eusr venn
The above figure only shows a few selected sets and does not reflect a full breakdown of all possible sets.

Non-normative example how these values are meant to be calculated:

  • End User "A" sent 2 Invoices and 3 Orders

  • End User "A" received 5 Invoices

  • End User "B" sent 6 Invoices

  • End User "C" sent 15 Invoices

  • End User "D" received 2 Orders

  • End User "E" sent nothing and received nothing

→ The value of eusr:SendingEndUsers is 3 (A, B and C)

→ The value of eusr:ReceivingEndUsers is 2 (A and D)

→ The value of eusr:SendingOrReceivingEndUsers is 4 (A, B, C and D)

3.3. Subset Information

An End User Statistics Report contains information about subsets of End Users. Each subset represents a different view on the End User statistics data, and subset cardinality is the concept in set theory that refers to the number of elements in it.

The technical representation of the subsets was designed in a generic way, to allow for future extension without modifying the underlying schema. Each Subset element requires a @type attribute that defines the type of the subset. The value range is defined by the Subset Type code list.

Subsets without any matching transaction (i.e. if SendingOrReceivingEndUsers is 0) MUST NOT be part of the Report.

All values in this subchapter are case-sensitive, except stated otherwise.

3.3.1. Subset Cardinality per End Users Country

This subset is identifierd by the @type attribute having the value PerEUC.

  • This subset requires one Key element with a Meta Scheme ID of CC (Country Code) and the schemeID attribute of EndUserCountry. The value of the Key element MUST have a value according to the Country Codes code list.

The element eusr:Subset/eusr:SendingEndUsers contains the number of distinct end users (cardinality) from the given End Users Country, who have sent transactions. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:ReceivingEndUsers contains the number of distinct end users (cardinality) from the given End Users Country, who have received transactions. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:SendingOrReceivingEndUsers contains the number of distinct end users (cardinality) from the given End Users Country, who have either sent or received transactions. Only values ≥ 0 are allowed.

Example of a subset per End Users Country:
  <eusr:Subset type="PerEUC">
    <eusr:Key metaSchemeID="CC" schemeID="EndUserCountry">PT</eusr:Key>
    <!-- How many distinct end users from PT sent transactions -->
    <eusr:SendingEndUsers>12</eusr:SendingEndUsers>
    <!-- How many distinct end users from PT received transactions -->
    <eusr:ReceivingEndUsers>23</eusr:ReceivingEndUsers>
    <!-- How many distinct end users from PT were involved in transactions (sent or received) -->
    <eusr:SendingOrReceivingEndUsers>26</eusr:SendingOrReceivingEndUsers>
  </eusr:Subset>

3.3.2. Subset Cardinality per Dataset Type and End Users Country

This subset is identifierd by the @type attribute having the value PerDT-EUC.

  • This subset requires one Key element with a Meta Scheme ID of DT (Dataset Type). The @schemeID attribute of this Key element MUST be the Document Type Identifier Scheme of the exchanged Dataset (usually busdox-docid-qns or peppol-doctype-wildcard). The value of the Key element MUST be the Dataset Type (Document Type) Identifier value of the exchanged dataset.

  • This subset requires one Key element with a Meta Scheme ID of CC (Country Code) and the schemeID attribute of EndUserCountry. The value of the Key element MUST have a value according to the Country Codes code list.

The element eusr:Subset/eusr:SendingEndUsers contains the number of distinct end users (cardinality) from the given End Users Country, who have sent transactions containing the given Dataset Type. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:ReceivingEndUsers contains the number of distinct end users (cardinality) from the given End Users Country, who have received transactions containing the given Dataset Type. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:SendingOrReceivingEndUsers contains the number of distinct end users (cardinality) from the given End Users Country, who have either sent or received transactions containing the given Dataset Type. Only values ≥ 0 are allowed.

Example of a subset per Dataset Type and End Users Country:
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">PT</Key>
    <!-- How many distinct end users from PT sent transactions for dataset ...eu:2017:poacc:billing:3.0::2.1 -->
    <SendingEndUsers>5</SendingEndUsers>
    <!-- How many distinct end users from PT received transactions for dataset ...eu:2017:poacc:billing:3.0::2.1 -->
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <!-- How many distinct end users from PT were involved in transactions (sent or received) for dataset ...eu:2017:poacc:billing:3.0::2.1 -->
    <SendingOrReceivingEndUsers>6</SendingOrReceivingEndUsers>
  </Subset>

3.3.3. Subset Cardinality per Dataset Type and Process ID

This subset is identified by the @type attribute having the value PerDT-PR.

  • This subset requires one Key element with a Meta Scheme ID of DT (Dataset Type). The @schemeID attribute of this Key element MUST be the Document Type Identifier Scheme of the exchanged Dataset (usually busdox-docid-qns or peppol-doctype-wildcard). The value of the Key element MUST be the Dataset Type (Document Type) Identifier value of the exchanged dataset.

  • This subset requires one Key element with Meta Scheme ID of PR (Process ID). The schemeID attribute of this Key element MUST be the Process Identifier Scheme of the process (Peppol profile) used (usually cenbii-procid-ubl). The value of the Key element MUST be the Process ID value of the process (Peppol profile) used.

Each distinct combination of the Dataset Type and Process ID MUST be reported in a separate Subset element.

The element eusr:Subset/eusr:SendingEndUsers contains the number of distinct end users (cardinality) that have sent datasets using this combination of the Dataset Type and Process ID. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:ReceivingEndUsers contains the number of distinct end users (cardinality) that have received datasets using this combination of the Dataset Type and Process ID. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:SendingOrReceivingEndUsers contains the number of distinct end users (cardinality) that have either sent or received datasets using this combination of the Dataset Type and Process ID. Only values ≥ 0 are allowed.

Example of a subset per Dataset Type and Process ID:
  <eusr:Subset type="PerDT-PR">
    <eusr:Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</eusr:Key>
    <eusr:Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</eusr:Key>
    <!-- How many distinct end users sent transactions containing the above dataset type and process id -->
    <eusr:SendingEndUsers>4</eusr:SendingEndUsers>
    <!-- How many distinct end users received transactions containing the above dataset type and process id -->
    <eusr:ReceivingEndUsers>2</eusr:ReceivingEndUsers>
    <!-- How many distinct end users were involved in transactions (sent or received) containing the above dataset type and process id -->
    <eusr:SendingOrReceivingEndUsers>5</eusr:SendingOrReceivingEndUsers>
  </eusr:Subset>

3.3.4. Subset Cardinality per Dataset Type, Process ID and End Users Country

This subset is identified by the @type attribute having the value PerDT-PR-EUC.

  • This subset requires one Key element with a Meta Scheme ID of DT (Dataset Type). The @schemeID attribute of this Key element MUST be the Document Type Identifier Scheme of the exchanged Dataset (usually busdox-docid-qns or peppol-doctype-wildcard). The value of the Key element MUST be the Dataset Type (Document Type) Identifier value of the exchanged dataset.

  • This subset requires one Key element with Meta Scheme ID of PR (Process ID). The schemeID attribute of this Key element MUST be the Process Identifier Scheme of the process (Peppol profile) used (usually cenbii-procid-ubl). The value of the Key element MUST be the Process ID value of the process (Peppol profile) used.

  • This subset requires one Key element with a Meta Scheme ID of CC (Country Code) and the schemeID attribute of EndUserCountry. The value of the Key element MUST have a value according to the Country Codes code list.

Each distinct combination of the Dataset Type, Process ID and End User Country MUST be reported in a separate Subset element.

The element eusr:Subset/eusr:SendingEndUsers contains the number of distinct end users (cardinality) that have sent datasets using this combination of the Dataset Type, Process ID and End Users Country. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:ReceivingEndUsers contains the number of distinct end users (cardinality) that have received datasets using this combination of the Dataset Type, Process ID and End Users Country. Only values ≥ 0 are allowed.

The element eusr:Subset/eusr:SendingOrReceivingEndUsers contains the number of distinct end users (cardinality) that have either sent or received datasets using this combination of the Dataset Type, Process ID and End Users Country. Only values ≥ 0 are allowed.

Example of a subset per Dataset Type, Process ID and End Users Country:
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">FI</Key>
    <!-- How many distinct end users from "FI" sent transactions containing the above dataset type and process id-->
    <SendingEndUsers>4</SendingEndUsers>
    <!-- How many distinct end users from "FI" received transactions containing the above dataset type and process id-->
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <!-- How many distinct end users from "FI" were involved in transactions (sent or received) containing the above dataset type and process id-->
    <SendingOrReceivingEndUsers>5</SendingOrReceivingEndUsers>
  </Subset>

4. Rules

End User Statistics Reporting process rules.

The term "Cardinality" in the business rules below refers to the number of elements in a set.
Table 1. Business rules
RuleID Requirement (depending, as applicable, on the respective business case) Validation Level

BR-EUSR-01

The Report MUST contain an identification of the specification it conforms to.

XSD

SCH-EUSR-01

BR-EUSR-02

The Report MUST contain an identification of the business process context it appears in.

XSD

SCH-EUSR-02

BR-EUSR-03

The Report MUST contain the reporting period in which the reported data was gathered.

XSD

BR-EUSR-04

The Report MUST NOT contain timezone information for the Reporting Period start date and end date.

SCH-EUSR-16

SCH-EUSR-17

BR-EUSR-05

The Report Period start date MUST NOT be after the Report Period end date.

SCH-EUSR-18

BR-EUSR-06

The Report MUST uniquely identify the reporting Service Provider.

SCH-EUSR-08

BR-EUSR-07

The scheme for identifying the reporting Service Provider MUST follow the "Reporter ID Scheme" code list

SCH-EUSR-07

BR-EUSR-08

If the Reporter ID scheme is set to "CertSubjectCN", the Reporter ID MUST be the CN part of the Peppol AP certificate Subject

SCH-EUSR-08

BR-EUSR-09

The Report MUST contain the Full Set End User Cardinality that have sent datasets during the Reporting Period.

XSD

BR-EUSR-10

The Report MUST contain the Full Set End User Cardinality that have received datasets during the Reporting Period.

XSD

BR-EUSR-11

The Report MUST contain the Full Set End User Cardinality that have sent or received datasets during the Reporting Period. This is the Cardinality of the union of the End Users targeted by BR-EUSR-09 and BR-EUSR-10.

XSD

BR-EUSR-12

The Full Set End User Cardinality that have sent or received datasets MUST be lower or equal to the sum of the Full Set End User Cardinality that have sent datasets and the Full Set End User Cardinality that have received datasets.

SCH-EUSR-19

BR-EUSR-13

The Full Set End User Cardinality that have sent or received datasets MUST be greater or equal to the Full Set End User Cardinality that have sent datasets.

SCH-EUSR-20

BR-EUSR-14

The Full Set End User Cardinality that have sent or received datasets MUST be greater or equal to the Full Set End User Cardinality that have received datasets.

SCH-EUSR-21

BR-EUSR-15

The Full Set End User Cardinality that have sent datasets MUST be greater or equal to the Subset maximum End User Cardinality that have sent datasets.

SCH-EUSR-03

BR-EUSR-16

The Full Set End User Cardinality that have received datasets MUST be greater or equal to the Subset maximum End User Cardinality that have received datasets.

SCH-EUSR-04

BR-EUSR-17

The Full Set End User Cardinality that have sent or received datasets MUST be greater or equal to the Subset maximum End User Cardinality that have sent or received datasets.

SCH-EUSR-22

BR-EUSR-18

The Subset End User Cardinality that have sent or received datasets MUST be lower or equal to the sum of the Subset End User Cardinality that have sent datasets and the Subset End User Cardinality that have received datasets.

SCH-EUSR-33

BR-EUSR-19

The Subset End User Cardinality that have sent or received datasets MUST be greater or equal to the Subset End User Cardinality that have sent datasets.

SCH-EUSR-34

BR-EUSR-20

The Subset End User Cardinality that have sent or received datasets MUST be greater or equal to the Subset End User Cardinality that have received datasets.

SCH-EUSR-35

BR-EUSR-21

The Subset End User Cardinality that have sent or received datasets MUST be greater to zero, otherwise the subset MUST not be emitted.

SCH-EUSR-36

BR-EUSR-22

The Report MUST contain the End User Cardinality that have sent datasets during the Reporting Period, subset by Dataset Type ID and Process ID.

XSD

SCH-EUSR-15

BR-EUSR-23

The Report MUST contain the End User Cardinality that have received datasets during the Reporting Period, subset by Dataset Type ID and Process ID.

XSD

SCH-EUSR-15

BR-EUSR-24

The Report MUST contain the End User Cardinality that have sent or received datasets during the Reporting Period, subset by Dataset Type ID and Process ID. This is the Cardinality of the union of the End Users targeted by BR-EUSR-22 and BR-EUSR-23.

XSD

SCH-EUSR-15

BR-EUSR-25

Each Subset combination of Dataset Type ID and Process ID, for which data is reported, MUST NOT occur more than once per Report.

SCH-EUSR-13

BR-EUSR-26

Each Subset combination of Dataset Type ID, Process ID and End User Country for which data is reported, MUST NOT occur more than once per Report.

SCH-EUSR-29

BR-EUSR-28

The Report MUST contain the End User Cardinality that have sent datasets during the Reporting Period, subset by Dataset Type ID and End User Country.

SCH-EUSR-37

BR-EUSR-29

The Report MUST contain the End User Cardinality that have received datasets during the Reporting Period, subset by Dataset Type ID and End User Country.

XSD

SCH-EUSR-38

BR-EUSR-30

The Report MUST contain the End User Cardinality that have sent or received datasets during the Reporting Period, subset by Dataset Type ID and End User Country. This is the Cardinality of the union of the End Users targeted by BR-EUSR-28 and BR-EUSR-29.

XSD

SCH-EUSR-38

BR-EUSR-31

The Report MUST contain the End User Cardinality that have sent datasets during the Reporting Period, subset by End User Country.

XSD

SCH-EUSR-39

BR-EUSR-32

The Report MUST contain the End User Cardinality that have received datasets during the Reporting Period, subset by End User Country.

XSD

SCH-EUSR-40

BR-EUSR-33

The Report MUST contain the End User Cardinality that have sent or received datasets during the Reporting Period, subset by End User Country. This is the Cardinality of the union of the End Users targeted by BR-EUSR-31 and BR-EUSR-32.

SCH-EUSR-40

5. Data Types

5.1. Primitive Data Types

Semantic data type content may be of the following primitive types. These primitive types were taken from ISO 15000, Annex A.

Primitive type Definition

Date

Time point representing a calendar day on a time scale consisting of an origin and a succession of calendar ISO 8601.

Decimal

A subset of the real numbers, which can be represented by decimal numerals.

String

A finite sequence of zero or more characters.

5.2. Semantic Data Types

The different semantic data types are described in the tables below, where various features such as attributes, format, and decimals as well as the basic type are defined for each semantic data type. They are based on ISO 15000.

When used in an instance of an invoice, each data element will contain data. In the below tables this is identified as the "content". Whenever a business term is used this term shall always have content and therefore the content is always mandatory.

5.2.1. Identifier

Identifiers (IDs) are keys that are issued to uniquely identify something.

The use of the attributes is specified for each information element.
Table 2. Identifier.Type
Component Use Primitive Type Example

Content

Mandatory

String

example-value

Scheme identifier

Conditional

String

example-scheme

5.2.2. Text

Text is the actual wording of anything written or printed. Line breaks in the text may be present, and any line breaks should be preserved and respected by the receiver’s system

Table 3. Text.Type
Component Use Primitive Type Example

Content

Mandatory

String

Here is my example text

5.2.3. Date

Dates shall be in accordance to the "Calendar date complete representation" as specified by ISO 8601, in the format YYYY-MM-DD.

Date values MUST NOT include timezone information.
Table 4. Date.Type
Component Use Primitive Type Example

Content

Mandatory

Date

2022-11-04

6. Code Lists

6.1. Country Codes

Country Codes are identifiers designed to identify countries. Country Codes must be coded according to the ISO-3166-1 Alpha-2 encoding.

Document location

eusr:EndUserStatisticsReport/eusr:Subset/eusr:Key[@metaSchemeID="CC"]

Source code list

Country Codes code list

6.2. Document Type Identifiers

Document Type Identifiers (aka Dataset Type Identifiers) are used to uniquely identify the type of a Peppol business document instance.

Document location

eusr:EndUserStatisticsReport/eusr:Subset/eusr:Key[@metaSchemeID="DT"]

Source code list

Document Type Identifiers (latest version)

6.3. Process Identifiers

Process Identifiers define the orchestrations in which business documents are exchanged. A Process Identifier Value is referenced in a Peppol specification as "profile identifier" *.

Document location

eusr:EndUserStatisticsReport/eusr:Subset/eusr:Key[@metaSchemeID="PR"]

Source code list

Process Identifiers (latest version)

6.4. Reporter Identification Scheme

Reporter Identification Schemes are used to identify the Service Provider inside the End User Statistics Report.

Document location

eusr:EndUserStatisticsReport/eusr:Header/eusr:ReporterID/@schemeID

Source code list

Reporter ID Scheme code list

6.5. Subset Type

The Subset Type determines the kind of subset that is contained in a Subset element. It determines the count and types of keys for a subset.

Document location

eusr:EndUserStatisticsReport/eusr:Subset/@type

Source code list

Subset Type code list

6.6. Subset Key Meta Scheme

The Subset Key Meta Scheme defines the type of a single key in a subset.

Document location

eusr:EndUserStatisticsReport/eusr:Subset/eusr:Key/@metaSchemeID

Source code list

Subset Key Meta Scheme code list

7. Specification Identifiers

In the table below you will find the values to be used as the specification identifier and the business process type for this profile

Type Element CustomizationID Process ID

End User Statistics Report

urn:fdc:peppol.eu:edec:trns:end-user-statistics-report:1.1

urn:fdc:peppol.eu:edec:bis:reporting:1.0
XML example representation
<eusr:CustomizationID>urn:fdc:peppol.eu:edec:trns:end-user-statistics-report:1.1</eusr:CustomizationID>
<eusr:ProfileID>urn:fdc:peppol.eu:edec:bis:reporting:1.0</eusr:ProfileID>
Full Peppol Document Type identifier
urn:fdc:peppol:end-user-statistics-report:1.1::EndUserStatisticsReport##urn:fdc:peppol.eu:edec:trns:end-user-statistics-report:1.1::1.1

8. Appendix 1 (non-normative)

The following example report represents a valid example message. This example represents the data for a Service Provider that both sent and received documents within a Reporting Period.

<?xml version="1.0" encoding="UTF-8"?>
<EndUserStatisticsReport xmlns="urn:fdc:peppol:end-user-statistics-report:1.1">
  <CustomizationID>urn:fdc:peppol.eu:edec:trns:end-user-statistics-report:1.1</CustomizationID>
  <ProfileID>urn:fdc:peppol.eu:edec:bis:reporting:1.0</ProfileID>
  <Header>
    <ReportPeriod>
      <StartDate>2023-12-01</StartDate>
      <EndDate>2023-12-31</EndDate>
    </ReportPeriod>
    <ReporterID schemeID="CertSubjectCN">PDE000001</ReporterID>
  </Header>
  <!-- Full set -->
  <FullSet>
    <SendingEndUsers>9</SendingEndUsers>
    <ReceivingEndUsers>4</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>9</SendingOrReceivingEndUsers>
  </FullSet>
  <!-- Subsets per Dataset Type and Process ID -->
  <Subset type="PerDT-PR">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <SendingEndUsers>9</SendingEndUsers>
    <ReceivingEndUsers>4</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>9</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <SendingEndUsers>9</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>9</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>4</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>4</SendingOrReceivingEndUsers>
  </Subset>
  <!-- Subsets per End User Country -->
  <Subset type="PerEUC">
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerEUC">
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerEUC">
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <!-- Subsets per Dataset Type, Process ID and End User Country -->
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>2</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:OrderResponse-2::OrderResponse##urn:fdc:peppol.eu:poacc:trns:order_response:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>1</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
</EndUserStatisticsReport>

9. Appendix 2 (non-normative)

The following example report represents a valid example message. This example represents the data for a Service Provider that only sent documents within a Reporting Period.

<?xml version="1.0" encoding="UTF-8"?>
<EndUserStatisticsReport xmlns="urn:fdc:peppol:end-user-statistics-report:1.1">
  <CustomizationID>urn:fdc:peppol.eu:edec:trns:end-user-statistics-report:1.1</CustomizationID>
  <ProfileID>urn:fdc:peppol.eu:edec:bis:reporting:1.0</ProfileID>
  <Header>
    <ReportPeriod>
      <StartDate>2023-12-01</StartDate>
      <EndDate>2023-12-31</EndDate>
    </ReportPeriod>
    <ReporterID schemeID="CertSubjectCN">PDE000001</ReporterID>
  </Header>
  <!-- Full set -->
  <FullSet>
    <SendingEndUsers>9</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>9</SendingOrReceivingEndUsers>
  </FullSet>
  <!-- Subsets per Dataset Type and Process ID -->
  <Subset type="PerDT-PR">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <SendingEndUsers>9</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>9</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <SendingEndUsers>5</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>5</SendingOrReceivingEndUsers>
  </Subset>
  <!-- Subsets per End User Country -->
  <Subset type="PerEUC">
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerEUC">
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerEUC">
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <!-- Subsets per Dataset Type and End User Country -->
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>2</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>2</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>1</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
  <!-- Subsets per Dataset Type, Process ID and End User Country -->
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>3</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>3</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">AT</Key>
    <SendingEndUsers>2</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">BE</Key>
    <SendingEndUsers>2</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>2</SendingOrReceivingEndUsers>
  </Subset>
  <Subset type="PerDT-PR-EUC">
    <Key metaSchemeID="DT" schemeID="busdox-docid-qns">urn:oasis:names:specification:ubl:schema:xsd:Order-2::Order##urn:fdc:peppol.eu:poacc:trns:order:3::2.1</Key>
    <Key metaSchemeID="PR" schemeID="cenbii-procid-ubl">urn:fdc:peppol.eu:poacc:bis:ordering:3</Key>
    <Key metaSchemeID="CC" schemeID="EndUserCountry">CY</Key>
    <SendingEndUsers>1</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>1</SendingOrReceivingEndUsers>
  </Subset>
</EndUserStatisticsReport>

10. Appendix 3 (non-normative)

The following example report represents a valid example message. This example represents a message in case no transmissions were performed within a Reporting Period.

<?xml version="1.0" encoding="utf-8"?>
<EndUserStatisticsReport xmlns="urn:fdc:peppol:end-user-statistics-report:1.1">
  <CustomizationID>urn:fdc:peppol.eu:edec:trns:end-user-statistics-report:1.1</CustomizationID>
  <ProfileID>urn:fdc:peppol.eu:edec:bis:reporting:1.0</ProfileID>
  <Header>
    <ReportPeriod>
      <StartDate>2022-01-01</StartDate>
      <EndDate>2022-01-31</EndDate>
    </ReportPeriod>
    <ReporterID schemeID="CertSubjectCN">POP000360</ReporterID>
  </Header>
  <!-- Full set -->
  <FullSet>
    <SendingEndUsers>0</SendingEndUsers>
    <ReceivingEndUsers>0</ReceivingEndUsers>
    <SendingOrReceivingEndUsers>0</SendingOrReceivingEndUsers>
  </FullSet>
</EndUserStatisticsReport>