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 genuinely documented: scanner via TWAIN/WIA/SANE or network folder with separator-sheet batch splitting, email and drag-and-drop, and a mobile ScanApp whose AI crops the photo into the inbox, with OCR full-text indexing and automatic invoice-data extraction from the Scaninput folder. Classification, however, is described only as manual or semi-automatic via templates, and we found no public information on XRechnung or ZUGFeRD read as structured data, on duplicate detection, on a validation queue, or on where the AI cropping runs. 1 7 8 14