How eConnect recognises document types, what is processed and which documents are not accepted as invoices.
When you submit an email with attachments, the system must determine for each attachment what type of document it is. Is it an invoice, a delivery note, a reminder or a logo? This is done via the Detect API, eConnect's entirely proprietary classification technology.
eConnect processes invoices and purchase orders. Documents that are not invoices or orders are automatically filtered. Some are placed as an attachment to an invoice; others are not processed.
The Detect API analyses each document in two steps:
Classification is fully automatic. The Detect API is eConnect's own technology, not an external classification service.
The system distinguishes the following categories:
Non-invoice documents that are in the same email as an invoice are automatically placed as an attachment to that invoice:
This only works if there is also an invoice in the same email.
Images from email signatures (company logos, banners) are automatically recognised as logos and filtered. This prevents a signature logo from being processed as a document.
The concept of "invoice" is independent of VAT liability. A document from a non-VAT-liable organisation that charges an amount for services rendered can legally be an invoice, even if the organisation calls it a "payment request". It is about the content, not the label the sender puts on it.
If you think a document has been incorrectly rejected, report this to support.
An important distinction: the Detect API classifies documents, but does not reject them itself. The actual rejection of a conversion task is always a manual action by the quality team. A document can be correctly classified as "not an invoice" and then assessed by the team before being rejected.
If an invoice is incorrectly classified as another document type, you can report this to support. The eConnect team can improve the classification so that similar documents are correctly recognised in the future.
Per-sender classification corrections are not possible: classification works generically across all senders. However, the classification model can be extended to recognise specific names (for example if a supplier writes "payment request" but the document is an invoice).
Report this to support so that the classification model can be improved. Classification works generically across all senders, but the model can be extended to recognise specific names. The actual rejection is always a manual action by the quality team, not by the Detect API itself.
Yes, documents such as delivery notes, specifications and terms and conditions that are submitted in the same email as an invoice are automatically placed as an attachment to that invoice.
A sales order is never recognised or converted as an invoice. eConnect does not modify the source document. The supplier must submit a correct UBL Invoice with InvoiceTypeCode 380.
Per-sender classification corrections are not possible, as classification works generically. However, the classification model can be extended to better recognise specific names. Report this to support.
Has a document been incorrectly rejected? Report it to support so that the classification model can be improved.
Report a classification error