Communities and Work Groups

Click on the tabs below to find out more about each of the stakeholder communities, together with their operational plans for the current year and their associated Work Groups. Information about the current community and work group leaders and members can be found on the WHO-IS-WHO page

There are three stakeholder communities
  • End User Community (EUC)
  • Service Provider Community (SPC)
  • Peppol Authority Community (PAC)
OpenPeppol members self-allocate to one of the three stakeholder communities on first registration as a member of OpenPeppol. The members of each stakeholder community formally elect:
  • a community leader
  • representatives to cross-community bodies
The leader of each stakeholder community participates in the OpenPeppol Coordinating Committee. Each community provides a forum for collaboration and knowledge sharing and hosts face-to-face meetings in March and October each year. Stakeholder community initiatives are approved each year by the General Assembly. Current initiatives are listed below.

Current stakeholder community initiatives

Key initiatives for 2023 – End User Community (EUC)
  • Propose a vision “EUC is to drive efficiency and growth among business and public sector entities around the world”
  • Send a survey to all registered End User members to seek more engagement and increase participation
  • Encourage End User interest in specific subjects, such as
    • Billing
    • Ordering
    • Logistics
    • Potential other business document
  • Have “deep dives” into topics of special interest for the End Users
  • Invite End Users to share their success stories
  • Invite End Users to share their day-to-day practical issues
Key initiatives for 2023 – Service Provider Community (SPC)
  • Key objective – Provide value to the members by creating the base to acquire important information and keep high quality discussions
    • Keep regularity in meetings except summer period
    • Agenda 4-5 days beforehand
    • Maintain the good quality meeting content
    • Regular MC updates of membership and PA development
    • Regular updates from eDEC and PoAC communities
  • Actions:
    • Ensure better on-boarding of new service providers
    • Encourage the members to execute kick-off groups for specific topics
    • Keep contact to local SP communities also emphasize the importance of SP cooperation
Key initiatives for 2023 – Peppol Authority Community (PAC)
  • Co-operate & share knowledge with domains and communities within Peppol. We try to interact with the different stakeholders within Peppol and see where we can help each other to bring Peppol forward.
  • 1 on 1 sessions: we do a “tour around the world” to talk with all PA’s individually to see what keeps them busy in these times and how we, as PA community, can help each other and learn from each other.
  • Create a “blueprint” PA paper. The idea is to write down a guide to set up a PA. We try to achieve this document with the second part of the year.
  • EU – Peppol: re-activate the EU workgroup in the PAC to see how we can position Peppol in a better way with the EC/EU. Also see how this can help on a national level.
  • Actively take part in the strategic planning for Peppol through the MC++ meetings and other gremials.
  • Help Peppol & OO with (re)sources when needed. Our aim is to see if we can find a more structural way to increase capacity within the Operations of Peppol and see how the PA’s can help with that.

There are four domain communities
  • Peppol Network Community (eDeC)
  • Post Award Community (PoAC)
  • Pre Award Community (PrAC)
  • CTC Community (CTCC)

Service Provider members of OpenPeppol must join eDeC. Additionally, Post Award Service Providers must also join PoAC and Pre Award Service Provider members must also join PrAC.

Peppol Authority members of OpenPeppol must join eDeC and may optionally join PrAC and/or PoAC.

End User members of OpenPeppol may optionally join any domain community.

Community participation

End Users

Service Providers

Peppol Authorities

Peppol Networkoptionalrequiredrequired
Post Awardoptionalrequired as relevantoptional
Pre Awardoptionalrequired as relevantoptional
CTCoptionaloptionaloptional

Except for the CTCC, each domain community has a Change Management Board (CMB), which is chaired by the domain community leader. The CMBs determine the annual workplan for their community and prioritise change requests.

The members of each domain community formally elect:

  • a community leader
  • representatives to their Change Management Board
  • representatives to cross-community bodies

The leader of each domain community participates in the OpenPeppol Coordinating Committee.

Each community provides a forum for collaboration and knowledge sharing and hosts face-to-face meetings in March and October each year.

Domain community initiatives are approved each year by the General Assembly and the current initiatives are listed below.

Current domain community initiatives

Key initiatives for 2023 – Peppol Network Community (eDeC)
  • Progress alignment with change and release management based on new agreement change processes
  • Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS SMP2.0, SML
  • Commence work on future of SML –defining business requirements followed by solution implementation in due course
  • Documentation of Peppol eDeliveryNetwork Architecture
  • Ensure and maintain safe & secure operation over Peppol eDeliveryNetwork
Key initiatives for 2023 – Post Award Community (PoAC)
  • Continue to improve the Peppol BIS messages
  • Strengthening stability and improve the functionality
  • Continue to review the use of business and message responses in the network Mandatory or optional use
  • Review the use of country specific rules
    Which country identifiers to use Rules on sender and receiver dataInvestigate the implementation via PINT
  • Continue the support for the Proof of Concept and implement the PINT propositionCollaborate with eDECand the Stakeholder Communities
  • Deliver new releasesMay and November
  • Implement the new agreementsImplement the new development and release process

    Survey the communities to drive CMB decisions

  • Align the versioning of the specifications
  • Complete eTenderingProcedure III workgroup
Key initiatives for 2023 – Pre-Award Community (PrAC)
  • Phase 1:Analysis of needs and definition of tasks to finalize Restricted Procedure, ESPD BIS 3.0 and pre-award Catalogue, identification of gaps and architecture needs.
  • Phase 2:New development of Peppol BIS (guidelines) and business modelling based on CEN BII profiles, eFormsand ESPD 3.0.
  • Phase 3:Maintenance and improvement of profiles based on the feedback of early adopters, upcoming changes and architecture needs (e.g., ESPD 4.0, eForms, CEN TC 440).

    Assessment of gaps in existing Peppol pre-award BIS with regard to data driven procurement vision.

  • Pre-Award catalogue for structured RFQ/Quote process
  • Alignment with CEN/TC 440 to create a common standard for pre-award
Key initiatives for 2023 – CTC Community (CTCC)
  • Contribute to market development activities and supporting the recruitment of new Peppol Authorities and, more generally, the expansion of Peppol into new countries and territories where CTC is a relevant priority for the governmentGet at least 1 TA or PA to test the playground

    Get at least 1 TA to commit to deployment of Peppol CTC (DCTCE or CCTCE)

    Focus on collaboration with DG TAXUD and GROW, and OECD

  • Subject to engagement of relevant stakeholders and resources availability in the Association, further refine and develop some additional aspects of the Peppol CTC model, such as cross-border, B2C, Centralised clearance scenarios (CCTC)
  • Improve, enhance, and further develop the existing playground environmentImproved look and feel 

    More automated “external” SP on-boarding

    Prepare several test scenarios, demonstrating both good/approved scenarios and varying bad/rejected scenarios

    Visualise in a user-friendly manner the outcomes/results of tests in UI

    Enable TA’s to test the playground without real SP’s involvement

  • Contribute to the work of other communities, investigating whether an increased number of tax codes in Peppol BIS (and later PINT) needs to be introduced to improve the granularity from TA perspective

 

Work Groups

OpenPeppol establishes formal work groups to manage specific initiatives to ensure the development and sustainability of the Peppol specifications and network.

Work groups are run by a work group leader and populated by volunteer representatives of OpenPeppol members. Work group members commit to actively participate in the discussions and activities of the group, supporting the work group leader in completing the agreed deliverables.

Work groups may be established at an organisational level or within stakeholder and domain communities. Each work group has a documented mandate, setting out the areas of responsibility and the expected deliverables.

Organisational-level work groups

  • Peppol Agreement Revision
  • Peppol Activity Reporting

Community-level work groups

Post Award work groups
  • International Invoicing
  • Core Invoice Response
  • Peppol BIS Development
  • Peppol Test Team
Pre Award work groups
  • eTendering
  • ESPD
  • Qualification
  • eForms/publishing

Join a Community or Work Group

Contact the Community Leader or Work Group Leader – details can be found under “who-is-who”.