With this app, you can create participants and register them in the Peppol network.

Key Features

You can use this app to do the following:

Create a participant for the exchange of electronic documents through the Peppol network or for the validation of electronic documents you exchange by e-mail.
Register your participant in the Peppol network to send and receive electronic documents through the Peppol network.
Make your company visible in the Peppol Directory.
View the status of the participant in the Peppol network.
Delete your participant in the Peppol network.

Use

Create a participant for your own company to complete the following tasks in SAP Document and Reporting Compliance, cloud edition:

Exchange and validation of electronic documents among business partners using the Peppol network.
Only relevant for Germany: Validation of electronic documents that you exchange with your business partners by e-mail.

Note

You must create one participant per business system to which you want to route documents or messages to. When creating the different participants you use the different Destinations that you've defined per business system in your SAP BTP subaccount, from which you subscribed to the cloud edition.

Dependencies

You can use the same participant for exchanging electronic documents by e-mail or through the Peppol network.

Example A company has already created a participant with identifier XXXX:123 for the exchange of electronic documents through the Peppol network. Now, the company wants to enable the validation of electronic documents that they exchange by e-mail. The company can use the same participant with identifier XXXX:123 for the validation of electronic documents that they exchange by e-mail. They don't have to create a separate participant.

Definition

Determines the identifier with which your company is registered in the Peppol network. When you create a participant, you enter the Party ID Type and the Party ID, which compose this identifier.

Definition

Identifies the destination that represents the business system with which SAP Document and Reporting Compliance, cloud edition connects when your company sends or receives electronic documents.

When your company sends documents from the business system using the cloud edition, then the cloud edition connects to the business system to return response messages.
When your company receives documents from your business partners using the cloud edition, then the cloud edition connects to your business system to forward the document.

Use

Select the destination that represents the business system with which the cloud edition connects when your company sends or receives electronic documents.

If for receiving documents you want to connect to a different business system than for sending, then maintain the Destination for Received Documents field in addition. The cloud edition continues to use the destination maintained in the Destination Name to connect when your company sends electronic documents to respond messages.

Dependencies

You can only choose from destinations that you've previously maintained with the drccSystemType property in your SAP BTP subaccount, from which you subscribed for the cloud edition application.

Example

You select the following:

Destination Name: Destination to connect to SAP S/4HANA Cloud Public Edition
Destination for Received Documents: No System Specified

This results in the following:

When you send an electronic document created in your SAP S/4HANA Cloud Public Edition business system, the cloud edition connects with SAP S/4HANA Cloud Public Edition and returns messages, for example, a transport acknowledgment confirming that the receiver access point accepted the document.

When you receive an electronic document from your business partner, the cloud edition connects with SAP S/4HANA Cloud Public Edition and forwards the electronic document to this business system.

Example

You select the following:

Destination Name: Destination to connect to SAP S/4HANA Cloud Public Edition
Destination for Received Documents: Destination to connect to SAP Ariba Invoicing

This results in the following:

When you send an electronic document created in your SAP S/4HANA Cloud Public Edition business system, the cloud edition connects with SAP S/4HANA Cloud Public Edition and returns messages, for example, a transport acknowledgment confirming that the receiver access point accepted the document.

When you receive an electronic document from your business partner, the cloud edition connects with SAP Ariba Invoicing and forwards the electronic document to this business system.

Definition

Identifies the destination that represents the business system with which SAP Document and Reporting Compliance, cloud edition connects when your company receives electronic documents.

If you don't specify a Destination for Received Documents, the cloud edition uses the destination specified in the Destination Name field for when your company sends and receives electronic invoices.

Use

Only enter a value to this field if you want the cloud edition to connect to a different business system than the one defined in the Destination Name field when your company receives documents.

Dependencies

You can only choose from destinations that you've previously maintained with the drccSystemType property in your SAP BTP subaccount, from which you subscribed for the cloud edition application.

Example

You select the following:

Destination Name: Destination to connect to SAP S/4HANA Cloud Public Edition
Destination for Received Documents: No System Specified

This results in the following:

When you send an electronic document created in your SAP S/4HANA Cloud Public Edition business system, the cloud edition connects with SAP S/4HANA Cloud Public Edition and returns messages, for example, a Message Level Response (MLR) confirming that the receiver access point accepted the document.

When you receive an electronic document from your business partner, the cloud edition connects with SAP S/4HANA Cloud Public Edition and forwards the electronic document to this business system.

Example

You select the following:

Destination Name: A destination you've created to connect to SAP S/4HANA Cloud Public Edition
Destination for Received Documents: A destination you've created to connect to SAP Ariba Invoicing

This results in the following:

When you send an electronic document created in your SAP S/4HANA Cloud Public Edition business system, the cloud edition connects with SAP S/4HANA Cloud Public Edition and returns messages, for example, a Message Level Response (MLR) confirming that the receiver access point accepted the document.

When you receive an electronic document from your business partner, the cloud edition connects with SAP Ariba Invoicing and forwards the electronic document to this business system.

Definition

Shows if your participant is visible in the Peppol Directory for other participants of the Peppol network.

Dependency

The status reflects your choice for the Make my company visible in the Peppol Directory option when creating the participant.

You can only change the status by deleting the participant and creating it again.

Use

If your business system is SAP Business Network, choose SAP Business Network.

If your business system is not SAP Business Network, choose Other.

Use

Choose the Party ID you want to identify your company with.

If you want to identify your company with a global location number (GLN), you can use the party ID type XX - International.

Dependencies

SAP Document and Reporting Compliance, cloud edition automatically enables the standard document types for your Party ID Type that you can receive from your business partners.
The cloud edition uses the combination of Party ID Type and Party ID of My Company to identify your company in the Peppol network.
If you select the XX - International party ID type, the cloud edition only offers the supported countries/regions for the business system in the Country / Region field.

Use

In the test system, use the same identifier value that you have maintained in your company's data within the test environment of your business system.
In the productive system, you must use the official identifier of your company, for example its VAT or GLN.

Note

For Singapore, you must enter your identifier as follows:

In the test system, enter 0195:SGTST<Unique Entity Number>.
In the productive system, enter 0195:SGUEN<Unique Entity Number>.

Caution

Ensure that the identifier you enter in this field is owned by and identifies your own organization. DO NOT enter the IDs of other organizations as this can lead to routing errors in the Peppol network for which you and your organization can be made responsible.

Dependencies

The cloud edition uses the combination of Party ID Type and Party ID of My Company to identify your company in the Peppol network.

Use

This field is prefilled if the Party ID Type (4-digit code) is specific to one country/region. Otherwise, select one of the countries/regions from the dropdown list.

Use

Choose the name of the company that matches the party ID you’re creating.

In the test system, you can use a random name.
In the productive system, it must be the official name, which your company is registered under.

Example

Example Company ABC Ltd.

Use

Enter the name of the person that SAP Document and Reporting Compliance, cloud edition enters as the contact person in the Service Metadata Publisher (SMP).

Use

Enter the business email address of the person that SAP Document and Reporting Compliance, cloud edition enters as the contact person in the Service Metadata Publisher (SMP).

Use

Enter the business phone number of the person that SAP Document and Reporting Compliance, cloud edition enters as the contact person in the Service Metadata Publisher (SMP).

Use

Choose one or more additional document types that you want your business partners to be able to send to you through the Peppol network.

Dependencies

This field is optional. If you don't choose additional document types, the cloud edition automatically registers your Peppol participant with the corresponding standard document types for your Party ID Type.

Use

You have the following options:

Sign with CorpPass (Participant with UEN)
As a participant using UEN, choose this option.
You receive an email inviting you to confirm the signing.
Sign with PDF (Participant without UEN)
Not valid for participants with the prefix SGUEN.

Use

Enter the name of the person authorized to sign via CorpPass.

Note Once you save a participant, you can't edit the signer's business name. To update it, you need to delete the participant and create a new one.

Use

Enter the email address of the person authorized to sign via CorpPass.

Note Once you save a participant, you can't edit the signer's business email. To update it, you need to delete the participant and create a new one.

Use

If you're creating a participant for Malaysia, upload a PDF that only contains the text "Registration via access point". Ensure the PDF contains no personal data.
If you're creating a participant for Singapore, upload a letter of authorization. For guidelines and the template, see Letter of Authorization.
Note This option is not valid for participants with the prefix SGUEN.

Dependencies

Once you uploaded a authorization document and saved your changes, you can no longer change the document. If you uploaded a wrong authorization document, delete the participant and create a new one.

Use

Choose this option to make your company visible for every participant in the Peppol network in the Peppol Directory website: Peppol Directory Information published on non-SAP site .

For Singapore, this option is checked by default.

We recommend you to make your participant visible in the Peppol directory. This enables your business partners to find out business information and supported document types about your participant.