The invoice was not delivered
A send can fail in three different places, and the message tells you which one. Read it before changing anything: the fix for each is different — the receiver's registration, the receiver's server, or your own document.
The receiver's registration
These mean the network could not work out where to deliver the document. Nothing is wrong with your invoice.
"The receiver is not registered for the specified document type in the Peppol network." The participant exists but has not published the document type you are sending. A company registered only for orders cannot receive invoices, and one registered only for Peppol BIS cannot receive an XRechnung. Ask your customer which document types their provider published for them.
"The receiver participant is not registered in the Peppol network." The identifier itself is unknown. Check it character by character. A German business is normally addressed as scheme 9930 plus its VAT identification number; a federal public buyer as 0204 plus the Leitweg-ID.
"The receiver supports the document type, but publishes no endpoint for the process and transport profile this document was sent with." Their registration is incomplete, or the document went under the wrong process. This one is worth sending to support with the invoice number, because the fault can be on either side.
"The receiver's participant ID could not be turned into a valid DNS name." The identifier is malformed — it has to be a scheme and a value, such as 9930:DE123456789.
The receiver's server
These are not yours to fix, and most resolve on their own.
| Message | What it means | Retried automatically |
|---|---|---|
| Connection timed out | Their access point did not answer in time | Yes |
| Could not establish a connection | Their endpoint is down | Yes, transient cases |
| No AS4 signal message received | The document went out, no acknowledgement came back | Yes |
| The hostname could not be resolved | The endpoint URL published in their registration is wrong | No |
| SSL/TLS handshake failed | Certificate problem on their side | No |
| The remote access point returned an error | They received it and refused it | No |
| DNS lookup failed temporarily | Their registration is not in question, the lookup failed right now | Yes |
Where the table says the send is retried, wait. Sending again by hand can produce a duplicate at your customer, which is worse than a delay.
Your own document
Required parameters are missing or invalid. Sender identifier, receiver identifier, document type or process is missing. Reopen the invoice and complete it.
A buyer reference or purchase order reference MUST be provided. The XRechnung rule described in XRechnung, ZUGFeRD and choosing a format. For a public buyer this is the Leitweg-ID.
Invoice already sent via Peppol. It left the platform earlier. A correction is a credit note or a corrective invoice, not a second send of the same document.
A public buyer says it never arrived
Delivery and acceptance are two different things, and a federal invoice can pass the first and fail the second.
- Confirm the Leitweg-ID is inside the invoice, not only used as the routing address. The authority checks both, separately.
- Confirm the authority receives through the channel you used. The federal administration now receives through the OZG-RE; a Land or municipal buyer may use something else entirely.
- Ask the buyer for their own rejection message. Their portal produces a reason that never reaches your side of the network.
Your supplier says they sent it and you cannot see it
- Check the company selector at the top of the screen — an invoice addressed to another of your companies will not show under this one.
- Widen the date filter on the purchase invoice list; it defaults to a narrow range.
- Ask the supplier which participant identifier they sent to, and compare it with your own registration. An invoice addressed to an identifier you own but have not activated does not arrive.
- Ask them for the tracking or message identifier from their platform. With that, support can tell whether the document ever reached us.
A supplier can also have sent to an identifier that was yours once and is no longer registered. Their platform accepts the send and the document goes nowhere.