Every invoice on the eConnect platform has a status indicating where the document is in the processing workflow. The statuses differ between incoming (purchase) and outgoing (sales) invoices.

The statuses "Under review", "Approved", "Approved for payment" and "Rejected" are used when an approval workflow is configured. Without a workflow, an invoice goes directly to the "Received" status and you can manually mark it as paid if needed. The statuses "Payment started" and "Collection successfull" appear in automated payment and direct debit processes.

A status change in the Inbox (for example to Downloaded, Approved, Rejected, or in everyday language "mark as done" / completed) only changes the status label. The document remains in place. Invoices in the Inbox cannot be deleted. There is no re-routing to connected software, ERP or the API download route.

Scenario: the invoice is already correct in your ERP/package, but the platform status has not been updated yet. Then change only the status. Do not use Re-offer API download: that action does re-offer the document to the integration (risk of a duplicate offer). Re-offer is only intended when the document was genuinely not forwarded.

Did you accidentally mark an invoice as done or Downloaded without downloading it? Do this:

1. Go to the Inbox on platform.econnect.eu.
2. Search by invoice number (set the status filter to Downloaded or All if needed).
3. Open the invoice and download it again as PDF and/or XML from the detail screen.

See also Change the status of a purchase invoice and Download XML invoice.

Via Peppol the invoice arrives as structured UBL/XML. A PDF is only present if:

1. the supplier embedded a PDF in the UBL (AdditionalDocumentReference / EmbeddedDocumentBinaryObject), or sent one separately; or
2. the receiving account has PDF generation from XML (legacy platform, account level; modes: When not present / Always / Never). See Generate PDF and PDF merge.

PSB: on-demand PDF generation from UBL is not yet standard; only an embedded PDF is returned. UBL without an embedded PDF means no PDF via the PSB.

XML-only without a processed PDF is normal when the supplier did not include a PDF and generation did not produce one. That is not a receipt error.

eConnect cannot add a missing sender PDF afterwards and cannot re-deliver the invoice with a PDF that was not received. Missing PDF? Ask the supplier to send the PDF for that invoice and to embed a PDF in the UBL for future invoices (or send it separately).

Invoice view vs attachment (platform): a PDF node in the XML does not automatically mean an invoice view. An embedded PDF counts as the invoice PDF in the dashboard invoice view only if cac:AdditionalDocumentReference contains the exact detection value:

• cbc:DocumentDescription = CommercialInvoice (camelCase, no space), or
• DocumentType = PrimaryImage

Prose saying "Commercial Invoice" (with a space) means the same thing, but platform detection follows the exact literal above. Without that tag the platform treats the PDF as a regular attachment, even if the UI shows "embedded attachment": it then appears at the bottom of the merged PDF instead of at the front as the invoice view. With PDF generation When not present/Always the platform can still create an eConnect PDF from XML (often cover sheet first instead of the original supplier PDF). See UBL invoice structure.

Self-check in the Inbox (platform.econnect.eu) — "which tag does this supplier send":

1. Open the Inbox, search by invoice number or supplier.
2. Detail/invoice view: if a PDF is shown there, it is available (sent/embedded or generated).
3. Attachments: additional PDFs or specifications from the supplier.
4. Download XML via the download option on the invoice, look for AdditionalDocumentReference + DocumentDescription / DocumentType. See Download XML invoice.
5. Missing CommercialInvoice / PrimaryImage? That is a message for the supplier (eConnect does not rewrite the XML): ask them to embed the invoice PDF with DocumentDescription CommercialInvoice in the UBL.

Search variants: omit cover sheet invoices, eConnect PDF first, original PDF first, CommercialInvoice tag, DocumentDescription missing, PrimaryImage, embedded PDF as attachment, contact supplier PDF tag, PDF missing on platform, PDF missing in SAP, embedded attachment not as invoice, attachment in XML but not visible, merged PDF attachment at the bottom, Commercial Invoice space vs CommercialInvoice.

See also: PDF via Peppol (sender and embed path).

The statuses "Under review", "Paid" and "Rejected" for outgoing invoices are set by the receiving party, not by you as the sender. When both parties are on the eConnect platform, status changes are exchanged automatically. When sent via Peppol, the recipient can send back a status message via the Invoice Response Message. Not all recipients send status messages back; that can explain differences in the statuses of invoices to different customers.

When both sender and recipient use the eConnect platform, status changes are shared in real time. When the recipient approves an invoice or marks it as paid, you see this immediately in your Outbox. This also works the other way around: when you mark a purchase invoice as paid, the sender can see that status in their own system.

For invoices sent via Peppol to a recipient at another provider, the status exchange depends on support for Invoice Response Messages at the receiving party. Not all recipients (or their providers) send status messages back. As a result, statuses of similar invoices to different customers can differ, even when the sending itself succeeded.

The platform automatically checks for duplicates by default. This behaviour can be disabled on request. When an invoice arrives that has already been received, even if it arrived through a different channel, the new invoice is marked as "Duplicate". The original invoice retains its status.

An invoice marked as duplicate is not automatically forwarded to your accounting software. Is the marking incorrect? You can mark the invoice as "Original" via the menu (three dots), after which it will be processed. Read more in How is a duplicate invoice recognised?.

Search variants: completeness check invoice flow, eConnect status export, Unit4 SFTP completeness check, eConnect ERP reconciliation, per invoice or per batch SFTP, what is on SFTP vs in ERP.

When delivering to an ERP system (for example Unit4 ERP CR) via To-SFTP, there are three separate steps: eConnect receives and processes the invoice, the PSB places the document on the SFTP server, and the ERP reads the SFTP folder and books the invoice. These are independent steps.

The platform status Downloaded only confirms that eConnect forwarded or made the document available. That is not proof that the ERP also ingested the invoice successfully. Via SFTP the receiving software does not return a booking status to eConnect.

eConnect does not offer a separate self-service completeness report for SFTP versus ERP. For checks you combine:

• the statuses and export in the Inbox (Received, Downloaded, Rejected);
• the files in the SFTP inbox folder and the ERP import log (eConnect cannot see this).

Reconciliation is preferably done per invoice number, not as a batch count: the standard To-SFTP route uploads per document, not as a periodic ZIP. See also the technical background in SFTP integration.

In the dashboard you see a visual overview of your invoice statuses. Green invoices are fully processed; orange invoices have been received but not yet processed. A large number of orange invoices may indicate duplicates that have been deliberately rejected; this is normal behaviour and not an error.

Want to manually change the status of a purchase invoice? Read Change the status of a purchase invoice.