Troubleshoot Sending Documents
This article covers what stops a document going out. Every refused send is written to the E-Invoice Platform Log with its reason, including the ones that fail before anything reaches the platform — so "I pressed Send and it refused" always has evidence to look at.
For problems with the connection itself, see Troubleshoot the Connection and Setup.
Customer number has no Peppol Endpoint. Set it on the customer card.
Cause: The customer has no Peppol address, so there is nowhere to deliver to.
Solution:
- Open the Customer Card.
- Choose Find in Peppol Directory to search by name, or type the endpoint as
scheme:value. - Choose Verify Recipient to confirm it resolves on the network.
To fill in many customers at once, see Fill Peppol Endpoints in Bulk.
Sales Invoice number has no VAT Registration No. on its header and customer number has no VAT Registration No. on the card either.
The full message names the rule it breaks:
Peppol BIS 3.0 requires a buyer VAT for standard-rated invoices (BR-S-02).
Cause: A standard-rated document must carry a buyer VAT identifier. Neither the posted document nor the customer card has one.
Solution: Fill in the VAT Registration No. on the customer card. The posted document keeps the value it was posted with, so correct the card and, if the document must go out, credit and re-issue it.
The credit memo version of this message is identical apart from the document type.
Vendor number has no self-billing agreement.
A self-billed document is only valid where the supplier has agreed that you issue invoices in their name, so turn on Self-Billing Agreement on the vendor card before sending.
Cause: Purchase documents only ever leave as self-billed documents in the supplier's name, and that requires an agreement.
Solution: Switch on Self-Billing Agreement on the vendor card — but only where the supplier really has agreed. This is a legal position, not a checkbox.
Vendor number has no Peppol Endpoint. Set it on the vendor card.
Note that the vendor must also be registered on the Peppol network for self-billing documents, which is a different registration from ordinary invoices - use Verify Recipient to check.
Cause: No endpoint, or an endpoint that cannot receive self-billed document types.
Solution: Set the endpoint, then choose Verify Recipient and Show Peppol Details on the vendor card to confirm the vendor has published the document types you are about to send.
Purchase Invoice number has no VAT Registration No. or Enterprise No. on its header, and vendor number has none on the card either.
A self-billed invoice names the vendor as the seller, and every invoice needs a seller VAT identifier (BR-CO-26).
Cause: On a self-billed document the vendor is the seller, so the vendor's VAT identifier is required.
Solution: Fill in the VAT Registration No. or Enterprise No. on the vendor card.
Vendor number has the same VAT number as this company
so this would be an invoice from us to us. Check the vendor card.
Cause: The vendor carries your own VAT number.
Solution: Correct the vendor card. This usually means a vendor record was created for an internal entity by mistake.
Company Information has neither a VAT Registration No. (W1 field) nor an Enterprise No. (BE local field).
Cause: The sending company's own identity cannot be resolved.
Solution: Open Company Information and fill in one of them.
The send failed and the message includes the payload
A failure returned by the platform comes back with the first part of what was sent:
error We sent the following payload (first 1500 chars): payload
Cause: The platform rejected the document. The reason comes from the platform, not from Business Central.
Solution: Read the platform's error first. The payload is there so you can see what actually went on the wire rather than what you assume was sent — check the parties, the amounts and the VAT categories in it before concluding the app built it wrongly.
The document was sent, but with a warning
A send can succeed and still report something. The two you will see:
No report is configured in Report Selections for usage usage, so the document was sent without the PDF attachment.
The PDF rendering failed (reason), so the document was sent without the PDF attachment.
Cause: Attach PDF to Outgoing Documents is on, but the report or its layout could not produce a PDF.
Solution: Configure a report for the usage on Report Selection - Sales, or fix the layout. The document itself went out and needs no resend — only the PDF copy was missing.