The PEPPOL transport module of ET-Connector handles the sending to the peppol network by looking up the service-meta-publisher database to get the certificate and the URL of the destination access point. Furthermore it generates the Standard business document header (SBDH). ET-Connector expects as DATA-IN X-Path selection the standard business document payload (BIS).

The errors, that are reported by the PEPPOL network are sometimes misleading and sometimes incorrect. This article describes a best practice and an ongoing error handling advice.


Validate the document

Before sending the document to PEPPOL network validate the BIS document manual in testing phase using one the known online validators:

Common errors and symptoms

  • ERROR: Unable to parse SBDH: nullThis error may indicate a wrong EndPointID specification in the payload, i.e.<cbc:EndpointID schemeID=”NO:ORGNR”>978632378</cbc:EndpointID>
    instead of
    <cbc:EndpointID schemeID=”NO:ORGNR”>9908:978632378</cbc:EndpointID>
  • The message  was transmitted successfully, but the recipient did not receive the message.

    If you have received a positve MDN (HTTP status 200) you can be certain, that the file was successfully delivered to the next PEPPOL Access Point. If that file did not reach the end receiver, the receiving Access Point has to be notified. Use the RecipientIdentifier to find the receiver’s PEPPOL Access Point contact details by doing a Participant Lookup.