Check Whether a Document Arrived
Sending has two stages, and it is worth keeping them apart. First the document reaches the e-invoice platform — that is what the send log records. Then the platform delivers it across the Peppol network and the receiving access point confirms it — that is what Check Delivery asks about. A document can be Sent and still not confirmed as delivered.
See what happened to one document
Open the posted sales invoice, credit memo, or the posted purchase document you self-billed. The E-Invoice Status box shows the last attempt: its status, the platform document id, and any error or warning. From there:
- Check Delivery asks the platform whether the receiving side has confirmed arrival.
- Download UBL downloads the XML exactly as it was exchanged.
- Platform Documents shows what the platform holds for this company.
- Open Full Log opens the log filtered to this document.
See everything
Choose the 
Search icon, enter E-Invoice Platform Log, and then choose the related link.
Each row is one send attempt. The columns worth knowing:
| Column | What it tells you |
|---|---|
| Status | Whether the attempt succeeded or failed |
| Message | Why it failed, or what was missing from a document that was sent anyway |
| Platform Document Id | The document's identifier on the platform, for looking it up on the provider's dashboard |
| Delivery Status | Whether the receiving access point has confirmed arrival |
| Sent Via | Whether a person or the job queue started the attempt |
| Document Kind | Sales invoice, sales credit memo, or the self-billed purchase equivalents. The separate Document Type column is free text and is not the same thing |
Recipient is the customer or vendor the document went to, and Customer/Vendor Name is the name as it stood on the posted document, which is not necessarily the name on the card today.
Ask whether it was delivered
Select a log entry and choose Check Delivery. There are two answers.
The platform holds a delivery signal for this document: the receiving access point has confirmed it arrived.
Or:
No delivery signal yet. The document left our access point, but the receiving side has not confirmed it. A signal can take a while to come back, and not every receiver sends one - so this is not in itself a sign that anything is wrong.
That second one is the important one to read properly. No signal is not a failure. Peppol delivery signals are not guaranteed; some receivers never send one. Treat a persistent lack of signals across many customers as worth investigating, and a single one as normal.
Delivery Status stays Not Checked until somebody asks — the app does not poll for signals on its own.
Only a Sent entry has anything to check:
Only a Sent entry has a document on the platform. This entry is status.
Download the UBL
Select a log entry and choose Download UBL to get the XML as it went over the network. This is the authoritative record of what your customer received — amounts, VAT categories, the exemption reason, the buyer and seller identifiers. When a customer disputes what was on an invoice, this is the file to open.
Entries written before the platform document id was recorded cannot be fetched:
This log entry does not carry a platform document id, so there is nothing to fetch. Entries written before this was recorded do not have one - look the document up on the platform dashboard instead, or send it again.
What the log is not
The log is Business Central's record of what it did. For what the platform itself holds — including incoming documents and anything sent outside Business Central — see See What the Platform Holds.