Resolving Peppol error codes with D Soft

Sien Jans
7 days ago
2 min read

Developers who connect to our Peppol solution receive a lot of feedback via status messages and error codes. Below is an overview of common error messages, how to recognize them, and what steps you can take. All examples are based on the processes we describe on our Peppol page.

General debugging approach

Check the document format: validations are performed against EN 16931/Peppol BIS. A missing IBAN or incorrect VAT code will quickly cause an error.
Verify your SMP data: the register determines which document types you can receive. If new processes have not yet been registered, you will receive a rejection. Use this link to validate your documents: https://ecosio.com/en/peppol-e-invoice-xml-document-validator/ (select Openpeppol UBL Invoice/CreditNote).
Use DocTrails monitoring: our solution displays status messages so that developers can see exactly at which corner in the 4-corner model the error occurred.

Frequently searched error codes

Missing mandatory fields

This error occurs when a mandatory field (e.g., `cbc:ID` or `cbc:EndpointID`) is missing. The Access Point validator stops the transmission.

Solution: check the mapping in your ERP or integration connector. Fill in the field and resend.

Invalid CBE number

You will receive this message if the CBE number does not meet the required structure (10 digits) or does not match what is in the SMP.

Solution: validate the CBE number via the ERP master data. If the number has changed recently, ask our consultants to update the SMP.

Incorrect code list value

Peppol uses fixed code lists for VAT codes, country codes, and document types. An unknown value will result in a rejection.

Solution: Replace the value with an allowed code (e.g., `S` for standard VAT). Consult the documentation on our Peppol page or in DocTrails.

Incorrect Peppol ID

If your participant cannot be found in the SMP or your JWT token linked to our API has expired, you will receive this message.

Solution: check that the Peppol ID (=CBE number) is correct and that the participant registration is active.

Recipient unavailable

This status occurs when the recipient's Access Point is unavailable or when the document type is not permitted for that party.

Solution: verify with the customer whether they support the document type. If necessary, our SMP service can quickly register it for you.

Business rule blocked

DocTrails can contain custom rules (e.g., mandatory PO reference). If a rule fails, this error appears.

Solution: check in DocTrails which rule has been triggered. Add the missing information or adjust the rule via the management portal.

Best practices for developers

Automatic retries: resend documents in the event of a temporary network error, but limit the number of retries to three.
Logging + correlation IDs: use the same ID as in DocTrails so that support can quickly find the message.
Test environment: use our Acceptance Environment to validate new mappings before going live.
Use our checklist: combine this article with the Peppol Readiness Checklist 2026 to determine whether your setup is ready.