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
Automatic capture and classification of incoming invoices, credit notes and advance payments with extraction of vendor, date, amount and purchase-order reference is documented, XML e-invoices are processed from receipt to validation with checks on mandatory fields, tax logic and duplicates, and intake covers paper, e-mailed PDF and XRechnung/ZUGFeRD. I stay below the top level because the pages state a vendor accuracy figure rather than per-document confidence with a validation queue, and I found no public information on where AI processing runs or which provider reads the document content — for personnel files and health certificates that is exactly the disclosure I look for. 4 5 8