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 — Manual upload only; no OCR, no metadata beyond file name and folder.
3 — Upload, drag-and-drop and scan import with OCR mentioned, but indexing is manual and no word on email intake or e-invoice formats.
5 — Scanner, email and folder intake, full-text OCR, document types with metadata fields, and automatic extraction of common fields (date, sender, amount) documented.
8 — AI- or rule-based classification and field extraction with confidence and 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
Intake is documented from scanner, watched folders, email and upload with connectors on stated intervals, and capture does the work I care about: classification sets document type, sender and direction and proposes the retention rule at filing time, fields carry confidence, uncertain values go to a review list, and duplicates are flagged. XRechnung and ZUGFeRD are validated against EN 16931, and processing is stated to run in the vendor's own EU data center on its own GPU hardware. It stops short of the top because classification is not documented as trainable per document type and Microsoft 365 mailbox sign-in is not supported yet. 2 5 6 8 10