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
Intake is well documented — email-to-folder import, an Outlook add-in, browser, ZIP and desktop-sync upload — with multilingual full-text OCR in 45 languages, an indexing opt-out and custom metadata fields. But we found no public information on document types with automatically extracted fields, a validation step, or XRechnung and ZUGFeRD read as structured data. The optional AI features (document classification, automatic summaries, a private chatbot) are named without any statement of where the model runs or who provides it — the first thing I want to know when the repository will hold personnel files and health certificates. 1 5 11 13 3 9