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 GoBD Auditor
Intake channels are listed with their real limits (scanner over SFTP, watched folders, an IMAP mailbox connector from five-minute intervals with Microsoft 365 sign-in not yet supported), classification determines type, sender and direction and proposes the retention rule, fields carry confidence and land in a review queue, and duplicate detection and EN 16931 validation of XRechnung and ZUGFeRD are documented. We found no public information on training classification per document type or on the model provider behind the AI. 2 5 6 10