We act as a Peppol orchestrator. We can connect with multiple Access Points.

Yes, for Belgian customers, invoices must be sent via Peppol as from 01/01/2026.

Check if integration Peppol is active (green), the selected invoice has an UBL, and invoice lines in UBL.

This error indicates a problem at the receiver's access point — for example a misconfiguration, a temporarily high invoice volume, or another transient issue. There is no automatic retry for this error type. The only resolution is to resend the invoice manually via Peppol.

The UBL contains incorrect data for the receiving party. The receiver is registered in the Peppol network under a different scheme ID than the one used — for example, only under their KBO number. Verify the correct Peppol identifier for the receiver and update the customer record accordingly before resending.

There is a (temporary) problem with the receiver's access point. This issue is not specific to invoices sent through Twikey — it affects all senders trying to reach that access point. If the problem persists, the receiver should contact their own access point provider to resolve it.

Peppol was able to reach the receiver's access point, but the access point could not deliver the UBL. Possible causes:

• Wrong UBL version — The receiver's access point is not configured for the UBL version being sent (e.g. configured for UBL 2.1 only, but receiving UBL 3).
• Receiver no longer active — The receiver still appears in the Peppol directory but has cancelled their account and is no longer reachable.
• Temporary access point issue — A transient problem at the receiver's access point (e.g. a broken VAT mapping).

In all cases, the issue is on the receiver's side. If the problem persists, the receiver should contact their access point provider.

Twikey periodically refreshes Peppol reachability data from the official Peppol directory. If a customer appears incorrectly marked as reachable or not reachable, this will be corrected automatically on the next update.