Understanding how Peppol Authorities Shape Peppol

As the Peppol network grows across Europe and beyond, many jurisdictions operate under a Peppol Authority (PA) that defines local conditions for service providers as well as end users of Peppol services. These national conditions are formalized through Peppol Authority Specific Requirements (PASR). Although PASRs are largely technical documents, they have real-world implications for any organisation planning to operate or participate in Peppol activities across multiple jurisdictions.

"...national conditions are formalized through Peppol Authority Specific Requirements (PASR)."

What is a PASR?

A PASR supplements Peppol’s core policies and agreements, translating them into a local context. In other words, a PASR defines the rules of the road for how Peppol operates in a given country.

Every PASR automatically applies to all entities that offer Peppol services to end users (participants) located within that jurisdiction. Compliance is assumed as part of operating locally.

Two Types of PASR Content

Although every PASR is different, their content generally falls into one of two categories.

1. Operational Requirements

At Arratech, we use the term Operational Requirements to describe PASR content that covers only operational or behavioral requirements. This content specifies how service providers must behave and what local conventions they must respect, such as security expectations or endpoint naming rules. If a PASR, for example Belgium’s, only contains these Operational Requirements, you can start operating within that jurisdiction immediately, provided you follow those rules. There is no need to contact the Peppol Authority beforehand.

"At Arratech, we use the term Operational Requirements to describe PASR content that covers only operational or behavioral requirements."

2. Accreditation Requirements

Some jurisdictions, for example Italy, extend their PASRs with a formal accreditation process. In these cases, a service provider must first be accredited by the local Peppol Authority before offering services to end users (participants) located in that jurisdiction. The PASR defines how this accreditation works, including testing and documentation. It is worth noting that a service provider is not required to enter into an additional Service Provider Agreement with a PA as part of an accreditation process. The service provider should remain under a Service Provider Agreement with the PA in the jurisdiction where it is located.

Why This Distinction Matters

For service providers, understanding a jurisdiction’s PASR model is crucial. It determines whether you can begin operations immediately or must first go through a national approval process. At Arratech, we find that thinking in terms of Operational Requirements versus Accreditation requirements provides a simple framework for navigating Peppol’s evolving governance landscape. Each Peppol Authority shapes Peppol in its own way, but having a clear picture of the possible nature of different PASRs helps all participants plan their strategy efficiently and remain compliant from day one.

“a PASR containing Accreditation Requirements requires service providers to engage with the local Peppol Authority before starting operations”

Effortless compliance with Accreditation Requirements

Achieving accreditation can be complex, involving documentation, audits, and coordination with multiple local Peppol Authorities. With Arratech’s shared label Access Point and SMP services, those hurdles disappear. Our accredited infrastructure, compliance framework, and continuous monitoring ensure your service operates in full Peppol conformity from day one, without the need to navigate the accreditation process yourself. Instead of managing bureaucracy and technical testing, you can focus on delivering value to your customers. Choose Arratech’s shared label service for immediate market entry, assured compliance, and a frictionless path to offering a Peppol-powered solution.