Skip to Content
Product Information
Author's profile photo Diana Cotelea

Testing with Business Partners in Peppol Exchange Service

In this blog post you will find what do you need to check before you submit test documents to your business partners when using Peppol Exchange Service, as well as details about Peppol SMP and how can test and productive participants be distinguished in the Peppol network.

Peppol SMP (Service Metadata Publisher) is similar to an address book or business registry containing technical details of participants within Peppol network. The participants publish their receiving capabilities, such as supported document types and versions, in the SMP service.

There are two parts of this address book, one meant for test participants – SMK and another one meant to be used for productive participants – SML. A participant can be registered in SML, SMK or both of them at the same time. SMK is also sometimes called test SML.

There are several ways to indicate a test participant in the Peppol network:

  • By registering the participant in SMK. At the moment only a few access points use this approach (example: ZRE in Germany)
  • By registering the test participant in SML, but having a different ID from the productive one, for example by adding a prefix or suffix to the productive ID. In the test environment of the Peppol Exchange Service the test participants are marked with the _TEST suffix.

If you send a document to a participant which is only registered in SML under their productive participant ID, your document will be forwarded to your business partner productive system and therefore it can be considered legally binding.

If you use the test environment of the service and want to send test documents which shouldn’t be treated as productive, then you have to follow the steps bellow.

  1. Request a test participant from your business partner
  2. If the participant ID from point 1 contains a productive ID, for example a real VAT ID, then access the Participant Information page. Fill the Participant ID in the Identifier value and choose the SMK option from the SML to use dropdown.
  3. After you press the Show details button, ensure that the participant appears as registered in SMK. This should look like in the image below:
  4. Only if the participant is registered in SMK as shown in the image at point 3, you should go ahead and submit test documents to your business partner.
  5. You shouldn’t simply submit test documents to a participant with a productive ID for which the SMK look-up is returning an error message as in the image bellow: In this case you should 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.
  6. 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 has only a testing purpose. 

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 post.

 

Please share your feedback and thoughts in a comment. If you have questions about SAP Document Compliance, you can post your question here.

Assigned tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Anders Wasen
      Anders Wasen

      By registering the test participant in SML, but having a different ID from the productive one, for example by adding a prefix or suffix to the productive ID. In the test environment of the Peppol Exchange Service the test participants are marked with the _TEST suffix.

      This is incorrect information and you must follow the intended syntax/structure of the Peppol Electronic Address Scheme (EAS) (https://docs.peppol.eu/poacc/billing/3.0/codelist/eas/) so adding `_TEST` as a postfix to an ID is not correct in the SML (production).

       

      Although only a very few EAS' are actually validated for <cbc:EndpointID> in Peppol Schematron (e.g. GLN code, Norwegian and Greek national registrations). Even though an SMP can register invalid identifiers for EAS doesn't mean you should do it...

      AND, it is never a good idea to send test messages in a live/production environment!