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 Data Protection Officer
Intake is well documented — scanning via TWAIN, WIA or SANE and a network scan folder, email and office files by drag-and-drop or automatic import, and a smartphone ScanApp whose AI crops the image — with automatic OCR full-text indexing and recognition of documents by layout or keyword that reads invoice data on its own. Classification stays manual or semi-automatic via templates, and I found no public information on reading XRechnung or ZUGFeRD as structured data, on a validation step with confidence values, or on where the ScanApp's AI actually processes the image. 1 7 8 14