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 is broadly documented — email, scanners, mobile devices, API, SFTP and batch import — with high-accuracy OCR extracting 150+ data fields, AI classification of 50+ document types that can also be self-trained, configurable confidence with human review on uncertain cases, validation against business rules and master data, duplicate detection, and support for ZUGFeRD, XRechnung and Peppol UBL. I found no public information on where the AI processing runs or which model provider is behind it, on the capacity limits of the individual intake channels, or on validation of e-invoices against the standard itself. 4 5 8