Capture, OCR & indexing
How this is scored
How documents get in and become findable: scanning and email intake, OCR, classification and metadata extraction, and whether incoming e-invoices (XRechnung, ZUGFeRD) are read as structured data rather than as pictures.
0 — Not a document intake tool: files cannot be uploaded or captured into the product as documents.
3 — Upload, drag-and-drop or scan import with full-text OCR; email intake, document types and field extraction are basic or not described.
5 — Scanner or app capture and email intake, full-text OCR, and document types with metadata fields, some filled automatically (date, sender, amount or similar).
8 — AI- or rule-based classification and field extraction with a validation step, XRechnung and ZUGFeRD read as structured data, mailbox and Microsoft 365 intake, and duplicate detection documented.
10 — Capture is engineered and shown: classification and extraction trainable per document type, validation queues, e-invoice validation against the standard, intake channels listed with their limits, and where AI processing runs (location, model provider) stated.
The Skeptic
Where the documentation exists it is refreshingly concrete: OCR data-capture plugins that lift a date, a number, free text or a barcode into typed fields by pattern, with defined error behaviour, plus a Windows scanner utility and an Invoice Capture application that catalogs invoices automatically. Around it, we found no public information on a validation step, duplicate detection, or XRechnung and ZUGFeRD read as structured data — and the invoice app is documented as not compatible with the Community edition, so the capture a paying buyer gets is the only capture documented. 2 3 4