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 Data Protection Officer
Advanced Capture is documented in depth: form identification by text value or image match, data-field zones, automatic and manual line-item extraction, ICR and the vendor's own OCR engine, bar-code processing, index verification, and ad hoc, batch and point-and-shoot modes, with document upload and photo capture on mobile. Document types carry keyword types with AutoFill sets and auto-numbering, and Outlook archiving is documented. We found no public information on reading XRechnung or ZUGFeRD as structured data, on duplicate detection, or on where OCR processing runs. 1 2 6 8