Peppol error codes and resolutions
The document contains a list of error codes and messages for Peppol.
| Error code | Summary | Explanation | Resolution |
|---|---|---|---|
| 1100 | Validation failed. | The validation process that is resulted in errors and failed to validate. | Fix or resend |
| 1360 | The participant ${customData} cannot be resolved in the SML. | Ensure that the RecipientIdentifier element in the SBDH envelope is valid. Search for and verify Particpant Lookup. If resending fails, then either the SMP where the participant is registered or the SML encountered a temporary disruption. | Resend |
| 1361 | Unknown reason. The SMP query failed and reported an error. | The response from the SMP in which the receiver is registered cannot be used to initiate a transaction to the Receiving Access Point. Resend the file. If the error persists, contact the admin of the SMP in which the receiver is registered. | Fix or resend |
| 1362 | Identifier not found. | Ensure that the RecipientIdentifier element in the SBDH envelope is valid. Search for and verify Particpant Lookup. If resending fails, then either the SMP where the participant is registered or the SML has encountered a temporary disruption. | Fix or resend |
| 1363 | Identifier not found. | Either the ProcessIdentifier in the SBDH was incorrect or the receiver is not able to receive the document type you tried to send. Correct the ProcessIdentifier in the SBDH or change to a document type that the receiver is capable of receiving. | Resend |
| 1364 | Failed to unmarshall the response. | The response from the SMP in which the receiver is registered cannot not be used to initiate a transaction to the Receiving Access Point. Resend the file. If the error persists, contact the admin of the SMP in which the receiver is registered. | Fix or resend |
| 1365 | Unexpected documentidentifier returned. | Either the ProcessIdentifier in the SBDH was incorrect or the receiver is not able to receive the document type you tried to send. Correct the ProcessIdentifier in the SBDH or change to a document type received. | Fix or resend |
| 1366 | No matching processidentifier found or no processidentifier with valid endpoint. | Either the ProcessIdentifier in the SBDH was incorrect or the receiver is not able to receive the document type you tried to send. Correct the ProcessIdentifier in the SBDH or change to a document type received. | Fix or resend |
| 1367 | Cannot parse the endpoint certificate. | The certificate of the receiving Access Point that was fetched from the SMP, where the receiver is registered, cannot not be parsed. Contact the receiving AP and notify them to update their certificate in the SMP. | Fix or resend |
| 1368 | Unknown transport profile found. | An incorrect schema type for the ProcessIdentifier (or Profile ID) was used. This error is returned only if you use the legacy envelope type TransactionRequest when exchanging files with GalaxyGateway. | Fix or resend |
| 1369 | The resolved endpoint Access Point URL ${customData} is malformed. | Check the encoding of your file. It must be UTF-8. |
Fix or resend |
| 1403 | Unable to parse the payload. | Ensure that the document is valid XML. Used for integration method TxAPI. | Resend |
| 1373 | Timeout occurred communicating with SMP using ${customData}. | The SMP where the receiver is registered might suffer from a temporary disruption. Resend the file. | Fix or resend |
| 1700 | The stored certificate for ROID ${customData} cannot be parsed. | The stored certificate for ROID ${customData} cannot be parsed. | Fix or resend |
| 1701 | Certificate for the ${customData}ID is invalid. | The certificate of the receiving AP is invalid. For resolution, contact the receiving Access Point. | Fix or resend |
| 1702 | The certificate has expired in ${customData}. | The certificate of the receiving AP is expired. For resolution, contact the receiving Access Point. | Fix or resend |
| 1703 | The certificate cannot be entrusted. | The certificate of the receiving AP cannot be trusted. For resolution, contact the receiving Access Point. | Resend |
| 1803 | Unable to use resolved AS4 endpoint address. | For resolution, contact the receiving Access Point. | Resend |
| 1804 | AS4 exchange with ${customData} either failed unexpectedly or is nonconformant. | The receiving Access Point encountered temporary disruption. Resend the file. If the issue remains, contact the receiving Access Point. | Fix or resend |
| 4000 | The data in the received file is corrupted. | Ensure that the document is valid XML that is used for integration method SFTP. | Fix or resend |
| 4100 | The document is validated with reported errors:
ValidatorResult=[${customData}]. |
Fix the validation issues in the document. | Fix and resend |
| 4101 | The document that is provided is not supported by the document validator. | The document was forwarded to the receiving Access Point but not be validated. For more information, see PEPPOL validator. | Fix and Resend |
| 4102 | The document is validated with reported mismatch:
ValidatorResult=[${customData}] |
The document that you sent did not match what was declared in the DOCUMENTID element in the SBDH envelope. Fix the document and resend it. For more information, see PEPPOL validator. | Fix and Resend |
| 4200 | The certificate [${customData}] is revoked. | The receiving Access Point configured a certificate that is revoked. This issue might be due to a misconfiguration or the Access Point might be excluded from the PEPPOL network. The receiving Access Point needs to be informed about the situation, and possibly the relevant PEPPOL Authority. Tickstar can help these contacts if necessary. After the configuration-related issue is resolved, you can resend the transaction. | Fix and Resend |
| 4310 | Resolved profile ${customData} is unsupported and cannot be exchanged with this Access Point implementation. | Correct the transport profile in the SBDH envelope of your file. | Fix and resend |
| 4311 | Possible security flaw detected. Receiving AP might be subject for an MITM-attack. The receipt of ${customData} exchange signed with a different certificate than expected. | Alert this issue with relevant PEPPOL authority. Expected:
${customData} Actual: ${customData}. To raise
a help ticket with PEPPOL, see Service desk. |
Fix and resend |
| 4312 | Resolved transport profile [${customData}] has been deprecated since [${customData}]. | Receiving AP supports only deprecated transport profiles. If the error persists, contact the receiving Access Point. Click here to find the contact details. | Resend |
| 4330 | Receiving AP reported a ${customData} error during the exchange. | A negative MDN was received from the receiving Access Point. Resend the file. If the error persists, contact the receiving Access Point. | Resend |
| 4340 | Communication with receiving AP @ ${customData} failed and error is reported. | The receiving Access Point might encounter a temporary disruption. Resend the file. If the error persists, contact the receiving Access Point. | Resend |
| 4378 | Receiving AP responded with an error or negative MDN. | A negative MDN was received from the receiving Access Point. Resend the file. If the error persists, contact the receiving Access Point. | |
| 4379 | Failed to find an ISO6523 sender identifier. | For a list of valid identifiers to Tickstar. Update the SenderIdentifier in the SBDH envelope. | Fix or resend |
| 4390 | Malformed envelope. | The SBDH envelope is malformed. Check and resend the document. | Fix and resend |
| 4407 | The value for the DocumentIdentifier field is not according to specification (POLICY1). | For more information about the use of identifiers, see PEPPOL Policy for use of Identifiers. | Fix and resend |
| 4413 | Provided value ${customData} for ParticipantIdentfier is not compliant. | Provide a valid value field in the SBDH envelope and retry. | Fix and resend |
| 4414 | Provided value ${customData} for DocumentIdentifier is not compliant. | Provide a valid value for the DOCUMENTID field in the SBDH envelope and retry. | Fix and resend |