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
Every sale ships with workstation scanning software supporting all TWAIN scanners, server-side OCR turns PDF and TIFF scans into searchable PDFs, and the FileScan Bridge imports files and indexes created by Kofax Capture with auto-filing templates; document schemas carry searchable metadata fields with system-generated unique document IDs, and the mobile app adds files including camera images with metadata entry. We found no public information on email or Microsoft 365 intake, on e-invoice formats such as XRechnung and ZUGFeRD being read as structured data, on a validation step, or on duplicate detection, so I cannot place capture higher. 1 2 4 6 8