You prepare an invoice for the bicycle shop, and your provider says it will travel through Peppol. What does that protection mean? To answer, follow the document rather than treating the supplier’s whole package as one action. Preparing an invoice, transporting it, opening it later and paying it are different kinds of work.
Peppol provides an arrangement for participating services to exchange business documents. A useful comparison is a delivery service carrying a prepared document. Protected delivery matters, but the carrier does not thereby approve the figures or decide who may later read the filed copy. To understand the actual digital protection, we need to look at the programs and messages involved too.
First identify the four participants
Start with your business and its accounting program. The program holds the invoice information and submits it to the service you use. The next participant is the sending Access Point, a service that sends messages in the Peppol network. It exchanges a message with the receiving Access Point, the third participant. The fourth is the receiving business, the bicycle shop in our example. This arrangement is called the four-corner model. The Peppol AS4 profile is the set of transport rules for the exchange between the two Access Points, the middle part of this journey. 10
Your accounting program’s first connection can be different. It may send a request directly to the provider’s software asking it to accept the invoice. A request is a message asking for work or information, and a response is the answer sent back. The agreed way programs make these exchanges is an API; in this case, a customer API. One company can operate both the customer API and the Access Point, but that does not make the two interfaces identical.
Imagine your program receives an answer saying that the provider has accepted the invoice for processing. Next, the Access Points exchange it. Afterward, the receiving service makes the document available to the bicycle shop through its agreed arrangement. The shop still needs to import or view it, compare it with the purchase and arrange any payment. Transport is not the same event as those business decisions. Likewise, a portal for viewing documents or a long-term archive adds functions around transport; the AS4 transport profile does not define every such function. 10
Protection applies to both the connection and the message
When the two Access Points communicate, their computers need a protected connection over the network. The technology used for protecting that connection is called TLS. It protects the exchange against outsiders reading or altering the traffic while it travels between these services. The receiving service can still work with the information at its end; protection of the journey is not a rule for who may use a copy afterward. 15 The AS4 profile requires transport protection and separately addresses message protection. 10
The message also has a digital signature. This is not a picture of somebody’s handwritten signature. The sending software produces verification data associated with the signed content, using secret mathematical data held by the sending Access Point. The receiving software can check this signature against that content. Changing signed content causes the signature check to fail rather than preserving a valid signature for the new content. This helps check origin and integrity: whether the signed information corresponds to the signing identity and has remained unchanged. 10
Here “key” means data used for a mathematical protection operation. The sending Access Point keeps a private key secret. A corresponding public key can be shared and used to check signatures. Knowing the public verification key does not mean being given the secret signing key. The names explain their handling, but they do not make every unrelated item called an API key public; those items have different roles. 14
The link between an Access Point’s identity and its public key is described in a certificate, a digital document issued within a trusted certificate arrangement. The receiving side uses the sending Access Point’s certificate for signature checking. It must check certificates as required, not trust any document merely because it calls itself a certificate. 10
The invoice message is also encrypted: its contents are transformed into a protected form that cannot be read without the appropriate decryption material. For this protection, the sending side uses the receiving Access Point’s certificate. That certificate provides public information usable in protecting the message for that receiving point, while the matching private key stays with the recipient. The receiving software uses its secret material to recover the readable contents. The AS4 profile specifies the sender’s certificate for signing and the receiver’s certificate for encryption. These are different roles, not a single certificate doing every job for everybody. 10 14
The two message protections answer different questions. Encryption protects readability during the protected exchange. Signature checking detects changes to signed content and checks the signing identity. A signature does not hide the invoice, and unreadable encrypted contents do not, by themselves, explain who approved the figures. Nor should connection protection be treated as the same operation as message signing.
The signing identity in this exchange is the Access Point’s transport identity. It is not automatically the personal signature of the employee who approved the bicycle shop’s invoice. A correctly protected message can still contain an incorrect amount or an unauthorized bank-account change entered before transmission. Transport protection cannot establish that goods were delivered or that your finance team approved the payment details. Those are business checks before and after the network exchange.
How does the sender know where to send it?
The sending Access Point needs the receiving details for the intended business and document exchange. It cannot simply choose a destination because another supplier has a familiar name. Peppol has a lookup arrangement that helps the sending service find the relevant technical information, including the receiving address and certificate. 10
The sending Access Point first needs to find the service that publishes the recipient’s receiving details. The Service Metadata Locator, or SML, helps it find that service. The sending Access Point then obtains the details from the Service Metadata Publisher, or SMP. Metadata here means information about the receiving service: where and how an appropriate message can be sent. These lookup services do not thereby become stores containing all your invoice copies. 10
In our example, the sending service uses the recipient’s registered information to discover the appropriate receiving service, then obtains the relevant address and receiving certificate. It can then arrange the exchange with that receiving Access Point. Discovering a route is a different step from transmitting the invoice along it. 10
This distinction becomes useful when changing providers. Your company’s receiving details may need coordinated changes, and your accounting program’s customer connection may need changes too. Ask who handles each part and how the planned handover is confirmed. Do not use invoices sent to unrelated real recipients as a routing experiment; an agreed transition or an expressly authorized test arrangement is the appropriate place for demonstration.
Certificates and secret keys need continuing care
Certificates depend on a system of issuers and trust. A certificate authority is an organization or service trusted to issue the relevant certificates. The wider arrangement of certificates, issuers and trust is called public key infrastructure, or PKI. Peppol’s documented certificate hierarchy distinguishes live operation from testing and distinguishes issuing roles for Access Points and metadata publishers. A certificate used in a test setup is therefore not interchangeable evidence of operation in the live network. 12
A certificate is not a permanent badge to acquire and forget. The provider must manage certificates and their private keys over time. A renewal or a change in trusted issuers can affect whether services accept each other’s identifying information. If a private key might have reached an unauthorized person, the provider needs a response process. For the business, the useful question is who handles those events and how invoice service is maintained. Ask for the process, never a copy of a private key.
Even a date printed in certificate documentation needs the right meaning. A date at which an issuing authority should become trusted is not necessarily a certificate issue date or the date a particular provider completed a change. Peppol’s hierarchy documentation defines “In Service” dates as the start of required trust for the relevant service area. A supplier’s actual deployment is a separate fact to confirm. 12
The received invoice still needs access and storage decisions
Once the document is available to the bicycle shop, somebody may open it in a portal or retrieve it through a customer API. The service must decide whether that person or program may perform this action on this document. A protected arrival does not give every signed-in customer permission to read it. Record-level access checks remain necessary. 1
Keeping a copy is another responsibility. A provider that sells transmission alone should not automatically be assumed to supply a long-term archive, backups and recovery. If those functions are part of your service, clarify where the records are kept and how they can be recovered or exported. Ask only for functions the supplier actually provides; account for the remaining work elsewhere.
You can understand your own arrangement by following one invoice through these stages with the provider: preparation, customer submission, discovery, Access Point exchange, availability to the recipient and retention of your copy. Use documentation or a permitted demonstration with invented documents, not live experiments. Peppol’s transport protection has real value. Knowing its specific job helps you use that protection without leaving approval, customer permissions or record keeping unexplained.
Sources
15 — MDN: Transport Layer Security — protection against eavesdropping and tampering
10 — OpenPeppol AS4 Profile 2.0.3
14 — MDN: Public-key cryptography — private/public keys, signatures and encryption
12 — OpenPeppol PKI 2025 hierarchy and certificate authorities
1 — OWASP API1:2023 Broken Object Level Authorization