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 Records Manager
A Windows scanner tool and a Hot Folder get paper and files in, and the OCR data capture plugins fill date, number, string and barcode values from OCR text by pattern, with an Invoice Capture application that catalogs PDF invoices automatically. I found no public information on reading XRechnung or ZUGFeRD as structured data, on a validation step before filing, on mailbox or Microsoft 365 intake, or on duplicate detection — and invoices arrive as PDFs to be read, which is exactly the picture-of-an-invoice problem I want gone. 2 3 4