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
AI capture is well evidenced: Smart Fields extract data from natural-language descriptions, classify documents, apply metadata templates and handle handwriting, complex tables and many prebuilt document types, with intake via batch scanning, email archiving, bulk import and mobile capture. But no validation step or confidence scores are documented, no duplicate detection, no word on XRechnung or ZUGFeRD as structured data, and no statement of where the AI processing runs — a question I cannot leave open for personnel files. 1 2 5 6