Key Capabilities
- Pan-European e-invoicing and e-procurement network integration using AS4-based four-corner model architecture
- Universal Business Language (UBL) format support with automatic message routing based on party identifiers
- SMP integration for dynamic endpoint discovery with certificate-based encryption and digital signatures
Overview
A Peppol connection is configured in two places. Configure the Peppol Profiles page with a local party identifier and a private certificate. Then configure individual Peppol connectors with connection settings specific to a single trading partner. When an input file is processed by a Peppol connector, it is packaged and sent to the specified trading partner. When receives a file over Peppol, it attempts to route the file to a specific Peppol connector. The application uses the Peppol party identifiers in the Peppol message to determine which Peppol connector should receive the file. When a file is routed to a Peppol connector, that file is placed in the connector’s Transactions tab, and is passed along to the next connected connector in the flow (when there is one).Prerequisites
Before you can configure and use the Peppol connector, you must complete the following:- Go to https://Peppol.org/ to register and complete the certification to become a Peppol access point.
- Register with an external SMP (Service Metadata Publisher). You must either register with an existing SMP or host your own.
Profile Configuration
The Peppol Profile must be configured before connections can be established with individual Peppol connectors. Click Profiles on the navbar, then click the Peppol tab.Peppol Profile Tab
Personal Id
Settings for identifying the local profile.| Setting | Description |
|---|---|
| Party Identifier | The Party Id used by in AS4 Peppol exchanges. Identifiers are case-sensitive. |
Personal Certificate
Settings related to the private decryption and signature certificate.| Setting | Description |
|---|---|
| Private Certificate | The certificate used to decrypt incoming messages and sign outgoing messages. Never share this certificate with external parties. Click the Create Certificate button to generate a self-signed certificate that is ready to use in a Peppol transaction: a corresponding public key is also generated with the same filename and a .cer extension. |
| Private Certificate Password | The password required to access the Private Certificate. |
Application URLs
Settings and displayed values related to accessing from the public web.| Setting | Description |
|---|---|
| Receiving URL | The URL at which listens for incoming Peppol messages. Share this URL with all your trading partners. It is in this format: <application_base_URL>/pub/Peppol.rsb. |
Connector Configuration
Once you configure the global Peppol profile settings, create and configure individual Peppol connectors for each trading partner on the Flows page.Settings Tab
Configuration
| Setting | Description |
|---|---|
| Connector Id | The static, unique identifier for the connector. |
| Connector Type | Displays the connector name and a description of what it does. |
| Connector Description | An optional field to provide a free-form description of the connector and its role in the flow. |
| Peppol ID | The unique identifier of the trading partner you are exchanging documents with. This is how you connect to the Peppol network, which enables secure and targeted message exchange. |
Advanced Settings
| Setting | Description |
|---|---|
| Local File Scheme | A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see Macros. |
Advanced Tab
Other Settings
Settings not included in the previous categories.| Setting | Description |
|---|---|
| Duplicate Message Action | How the connector should behave when it receives a Peppol message with a Message Id that the connector has seen before. The connector detects duplicate messages by remembering Message Ids that have been received within the number of minutes specified in Duplicate Interval. |
| Duplicate Interval | The number of minutes that a message with the same Message Id is considered a duplicate. If you set this to 0, the Message Ids are stored until the server is restarted. |
Proxy Settings
Logging
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.| Setting | Description |
|---|---|
| Send | Whether files arriving at the connector are automatically sent as Peppol messages. |
| Retry Interval | The number of minutes before a failed send is retried. A retry is triggered when the server does not respond to a send attempt, or responds negatively to communicate that the file was not received. |
| Max Attempts | The maximum number of times the connector processes the input file. Success is based on a successful server acknowledgement and validation of the receipt (when requested synchronously). If you set this to 0, the connector retries the file indefinitely. |
Performance
Alerts Tab
SLAs Tab
Transactions Tab
This tab lists all messages associated with the connector. Use the search bar to find specific messages, or click the funnel icon to apply a filter. You can filter by time, message direction, and/or status.Sending Documents
When sending documents, the following occurs:- The connector uses the Peppol Id to look up the metadata (such as the endpoint and certificates) for the partner that has that ID.
- The receiver defined in the Standard Business Document Header (SBDH) of the outbound message must match the Peppol Id of the connector where the message being sent.
- You can configure the SBDH using an XML Map connector when it is connected as the input to a Peppol connector.
- The metadata that is returned from the lookup is used by the connector to send the document to the partner.
Receiving Documents
When receiving documents, the steps described in Sending happen in reverse:- Your partner’s Peppol AP looks up the metadata details that you provided to the SMP you registered with.
- That metadata is used by your partner’s Peppol AP to send you the message(s). When a message reaches , the engine looks at the sender Peppol Id defined in the message SBDH, then routes the message to the Peppol connector that is configured with that Peppol Id.