Testing the Peppol Exchange Process with Your Business Partner
If you want to send test documents through the Peppol network to your business partners using the cloud edition of SAP Document and Reporting Compliance, you must make sure that the document is really only considered as a test document and not as legally binding. This blog post will tell you what you need to check to ensure this. In addition, you’ll find out what Peppol SMP is and how test and productive participants can be distinguished in the Peppol network.
What is Peppol SMP?
The Peppol Service Metadata Publisher (SMP) is similar to an address book or business registry containing technical details of participants within the Peppol network. The participants publish their receiving capabilities, such as supported document types and versions, in the SMP service.
The SMP registers the participants in the Peppol network using a registration service. There are two types of registration services: one for test participants – SMK, and another one to be used for productive participants – SML. A participant can be registered using the SML, the SMK or both of them at the same time. The SMK is also sometimes called test SML.
When using the cloud edition to exchange electronic documents with participants of the Peppol network, you can create a test subaccount in SAP BTP (see Subscribing to the Cloud Edition Application). In this test subaccount, you can register a test participant you use for testing. This participant is then registered in the Peppol network using the SMK.
|ATTENTION: If you send a document to a participant which was only registered using the SML, your document will be forwarded to your business partners productive system and therefore it can be considered legally binding.|
How to make sure you’re testing with SMK?
If you use the test subaccount of the cloud edition and want to send test documents which shouldn’t be treated as productive, then do the following:
|The following screenshots were taken on February 9, 2023. Since the website from which they originate is not maintained by SAP, it is possible that the user interface has changed since then and those changes are not reflected in the screenshots.|
- Request your business partner to provide you their test participant information.
- If the participant identifier from step 1 is a productive identifier, for example a real VAT ID, then access the Participant Information page. Enter the productive participant identifier in the Identifier value and choose the SMK Peppol option from the SML to use dropdown.
If the participant identifier isn’t registered with the SMK, you get an error message like shown in the screenshot below:
In this case, contact your business partner and request a correct test participant or make an agreement that you are going to send test documents to their productive participant.
- After you press the Show details button, ensure that SMK Peppol is used. This should look like in the screenshot below:
- Only if SMK Peppol is used for the participant registration as shown in the screenshot in step 3, you can go ahead and submit test documents to your business partner.
A participant registered for productive use – SML – has the following representation in the participant information:
In any case, you should mark all your test documents, for example, with a note text that specifies that the document is for test purposes only.
This blog post only contains instructions for the outgoing process, if you want to run a complete test then I recommend to follow the End-to-end Testing blog post. You can also check the Best Practices for Testing in the help portal!
Please share your feedback and thoughts in a comment. If you have questions about SAP Document Compliance, you can post your question here.