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
Capture is well evidenced: documents arrive via web upload, email, mobile capture, API, SFTP or batch import; machine learning sorts 50-plus document types with training of your own; extraction of 150-plus fields runs with configurable confidence levels, human review on uncertain cases, and validation that flags duplicates before anything reaches downstream processes; and ZUGFeRD, XRechnung and Peppol UBL e-invoice formats are supported. What keeps it short of the top: we found no public information on the limits of each intake channel or on where the AI processing actually runs. 4 5 8