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
Digital post intake captures, classifies and distributes documents from scanner, email and Peppol, and booking-relevant invoice fields such as number, date, creditor and position data are read out automatically; ZUGFeRD and XRechnung are processed as structured formats meeting EN 16931, with an AI-supported review step in the invoice workflow. What holds this below the top is that I found no public information on extraction confidence values, duplicate detection, or where and by which provider the AI that reads document content actually runs. 5 6 9 10