Import logs

The Logs tab on a document shows what the module did during analysis: which structs matched, which tables it rejected, how it interpreted the rows and where it stopped.

When to look here

No lines were read. Usually it means no table passed the struct’s column bounds, or the document has no text layer (it is a scanned image). → Structs

Too few lines were read. A frequent cause: a multi-page invoice with no page-header marker; rows from later pages are merged into the last item of the previous one. → the Page marker in Mappings

Values landed in the wrong fields. That is a matter of mappings or column ranges, not of the document. → Columns

Products not recognised. Check whether the identifier on the invoice matches what is in the catalogue. If the supplier uses their own numbers, describe them as a Supplier identifier.

A rule for working through it

Fix one thing at a time and upload the document again. Imports are cheap to repeat, and changing three things at once does not show which of them worked.

Diagnostics beyond the import

If the problem is not the reading but that nothing is happening at all, look at the background jobs; analysis runs in the queue. → Background jobs