Peppol in AS4
Learn about Peppol network integration with AS4 eStandards for secure electronic document exchange. Transacting on the Peppol network enables standardized, secure, and interoperable electronic document exchange. It ensures compliance with international and local regulations and allows seamless connectivity with global trading partners.
What is Peppol?
Peppol is a set of artifacts and specifications enabling cross-border e-procurement. The use of Peppol is governed by a multi-lateral agreement structure owned and maintained by OpenPEPPOL. Peppol enables trading partners to exchange standards-based electronic documents over the Peppol network (based on a 4-corner model). These documents include e-orders, e-advance shipping notes, e-invoices, e-catalogs, and message level responses.
What is an access point?
An access point is a gateway that connects participants to the Peppol network. It exchanges documents on behalf of the participants based on the Peppol specifications. Senders and receivers can choose their preferred single access point provider to connect to all Peppol participants on the network.
A sender might operate as a certified access point provider or use a third-party access point service provider.
Peppol capabilities
Peppol includes the following capabilities:
- Peppol e-delivery Network
- Peppol Business Interoperability Specifications (BIS)
Peppol e-delivery Network
Peppol uses the e-delivery Network to connect different e-procurement systems by establishing common business processes and technical standards. This service provides an interoperable and secure network connecting all access points using the same electronic messaging protocol and formats and applying digital signature technologies to secure message content.
Peppol SMPs (publishing the capabilities of Peppol participants) and SML (central registration system for addressing)
An SMP (Service Metadata Publisher) is a registry that publishes details about a Peppol participant, such as endpoint URL and document types. To deliver electronic documents from a sender to the correct recipient, all Peppol access points need to know about each other. Peppol maintains one centralized service, called the Service Metadata Locator (SML). The Peppol SML defines which Service Metadata Publisher (SMP) to use for finding out the delivery details of any Peppol participant.
System assets
The AS4 module startup service creates the assets.
The corresponding TPA data have the default values as per the Peppol specification. These values are required for submitting the payload in the Peppol network. The agreement id for the default TPA is Peppol, and for sender and receiver the value is Unknown.
The following parameters are listed in the TPA:
| Parameter | TPA | ||
|---|---|---|---|
| IS Document Type | com.wm.estd.as4.documents.pmode:PMode_V1 | ||
| agreement | urn:fdc:peppol.eu:2017:agreements:tia:ap_provider | ||
| mepBinding | One-Way/Push | ||
| initiator/role |
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/ |
||
| responder/type | urn:fdc:peppol.eu:2017:identifiers:ap | ||
| responder/role |
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/ |
||
| legs[0]/label | requestUM | ||
| legs[0]/businessInfo/mpc |
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/ |
||
| legs[0]/security/receipt/sendReceipt | true | ||
| payloadService/validate | both | ||
When you create any custom TPA, the agreement id must be Peppol and IS Document Type value must be com.wm.estd.as4.documents.pmode:PMode_V1.
Ensuring Peppol compliance for AS4 module
Complete the following prerequisites before using the module:
- Both the sender and the receiver must be registered with a Service Metadata Publisher (SMP) provider that publishes capabilities such as endpoint URL and supported document types to exchange documents in the Peppol network. For more information, see Peppol SMPs and SML.
The SMP must comply with the OpenPeppol SMP specification.
- Both the sender and the receiver must have a Peppol participant identifier. This ID uniquely identifies the sender or receiver in the network. The format of the external ID must be in CNAME(ParticipantID) format. CNAME is mentioned in the certificate.
- The sender and the receiver must be connected to the Peppol certified Access Point partner profile. For more information about access points, see What is an access point?.
- Valid Generation 3 (G3) certificates chains defined by OpenPeppol must be available and associated with both the participants' access point partner profiles.
- The sender must have the details of the receiver's Peppol participant identifier (Peppol ID). The receiver's Peppol ID is used to locate the SMP and retrieve the endpoint to send the message.
- Set the property as4.peppol.smp.dns.url.resolution.method to u-naptr to locate the SMP endpoint using DNS resolution through U-NAPTR.