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 — Not a document intake tool: files cannot be uploaded or captured into the product as documents.
3 — Upload, drag-and-drop or scan import with full-text OCR; email intake, document types and field extraction are basic or not described.
5 — Scanner or app capture and email intake, full-text OCR, and document types with metadata fields, some filled automatically (date, sender, amount or similar).
8 — AI- or rule-based classification and field extraction with 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
Documents come in through browser and ZIP upload, arranged SFTP migration, a desktop sync app, email-to-folder import and an Outlook add-in, with multilingual OCR in 45 selectable languages feeding content search that an account can switch off. Folder metadata templates, custom metadata and automatic document numbering are documented, and AI document classification is named for the on-premises edition, where it requires additional GPU resources. We found no public information on XRechnung or ZUGFeRD being read as structured data, on a validation step for classification, on duplicate detection, or on where cloud AI processing runs. 1 3 5 8 9 12