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
Scanner intake into a central inbox, collection of incoming emails with tax-relevant content, hot folders and a server-side OCR engine that produces searchable PDFs and reads barcodes give me capture I can trust, and an AI tool extracts invoice data and tables through the Mistral OCR API. The control layer is thin: we found no public information on a validation step or confidence values for extraction, on XRechnung and ZUGFeRD being read as structured data (an e-invoice module is listed but not described), or on duplicate detection. 2 5 6 10