DocuWare vs M-Files

DocuWare

Intake is documented as a pipeline: batch-scan splitting, classification and extraction with a trainable custom model that needs only a few sample documents and no coding, confidence scores per mapped field, OCR plus handwriting recognition, and e-invoice receipt with validation and PEPPOL support. The automated index capture of vendor name, amount, due date and line items on invoices is exactly what I want feeding the archive. I found no public information on the German e-invoice formats being read as structured data, on intake channels and their limits, on duplicate detection at capture (the duplicate handling shown concerns exports), or on where the AI and GenAI models process document content.

M-Files

Scanner and drag-and-drop intake with conversion to searchable PDF is documented, but only when an OCR licence and a separately installed OCR module are present, and mailbox intake arrives via the Outlook Pro add-on; automatic classification is claimed through the metadata-driven architecture. We found no public information on XRechnung or ZUGFeRD being read as structured data, on duplicate detection, or on a validation step for extracted fields, and the workflow OCR path needs VBScript the vendor's own support declares out of scope.

DocuWare

Documents can be locked for other users during editing, a workflow history records which user made which decision, and the document history is described as viewable in the system and exportable to a common file format. Beyond that I found no public information on version history with restore, on role- or folder-based permission models, on single sign-on or directory synchronisation, or on an audit log covering reads, exports and deletions — that silence matters when I wire a DMS into the directory.

M-Files

Check-out is documented for objects, and the Event Log records vault changes including who created or modified workflows once an administrator enables the advanced event-log feature. Federated authentication and an extended audit log with exports are listed as Enterprise-only, while we found no public information on directory sync with Entra ID or LDAP, on reads and exports in the trail, or on tamper-evidence of the log.

DocuWare

Revisionssichere Archivierung is claimed on the invoice-processing page and in a customer reference, and the vendor publishes genuinely useful GoBD guidance: retention periods by document class, booking deadlines, e-invoices to be kept in digital original form, and exports in CSV, XML or DATEV formats. How immutability of the archive is technically achieved, retention configurable per document type, a sample Verfahrensdokumentation, a tax-audit data export and any auditor's report are not documented; certifications are pointed to on a separate page whose contents the captured pages do not show.

M-Files

Retention policies are mentioned as part of integrated governance and configurable workflows, PDF/A output and a Compliance Kit appear in support notes, and marking objects to be archived requires full-control vault rights — but that reads as lifecycle archiving, not revisionssichere Archivierung. We found no public information on a GoBD or revisionssicher claim, on how immutability of archived documents is achieved, on retention periods per document type, or on an auditor's report.

DocuWare

The workflow engine is well evidenced: a drag-and-drop designer without programming, triggers such as a document type being added or a due date arriving, substitution rules, deadline escalations, an overseeing workflow controller, task assignment to employees or roles, and invoice approval flowing into export toward the accounting system. The integration story is thinner than the product: "integrates with 500+ applications" is a count with no stated scope per connector, DATEV appears in a customer reference and as an export format rather than as a documented connector, and the API is asserted for real-time data flow without any REST documentation, webhooks or events. I also found no public information on Microsoft 365 integration or an e-signature handover; the captured signature content explains the three signature levels but names no integration.

M-Files

Graphical workflow automation is included in both plans, a public API reference is versioned and documents approval-assignment semantics, and connectors carry stated scope for SAP — importing vendors and products via standard database connections or acting as SAP's content repository — alongside Microsoft Dynamics, Salesforce, Microsoft 365 and an Adobe Acrobat Sign package. We found no public information on DATEV, on webhooks or events alongside the API, or on substitutes and escalation in the workflow designer, which keeps this short of the top band despite the breadth.

DocuWare

Full-text and index-data search with remote and mobile access is documented, and the export tool is real and clearly licensed: filter-driven selection, CSV output with a configurable structure including line-item table fields, manual or scheduled runs, included in cloud licences and available on premises via additional licences on the PROFESSIONAL or ENTERPRISE servers. As an exit path this is only half the story — it moves index and posting data to ERPs and dashboards; I found no public information on bulk export of the documents themselves with their versions in a documented structure, on saved searches, or on an import path from other DMS or file shares.

M-Files

Quick search and saving executed searches as reusable, renameable views are documented, and a Reporting Databases add-on sends metadata and vault data to a separate external database, which is a partial metadata exit path. We found no public information on bulk export of documents with metadata and versions in a documented structure, on mobile access, or on post-termination retrieval and deletion terms; the Smart Migration tool in the catalog is tied to M-Files Server build versions rather than described as a path in from other systems.

DocuWare

Proven: a German contracting entity in Germering under German law with Munich as venue, dedicated cloud data centres in the EU as well as the USA with same-region mirroring, personal data generally processed in Germany and other European countries backed by adequacy decisions and standard contractual clauses, and a locally installable edition. Not proven: a published data processing agreement, and locations for the subprocessors behind hosting, support and — the one I care most about — the GenAI provider that reads document content during extraction; the provenance note also records that the company has belonged to Ricoh of Japan since 2019, and certifications are only referenced on a separate page not captured.

M-Files

A cloud and an on-premises deployment are both offered, a data-processing agreement with language add-ons and a qualified-subcontractor list are published, and the trust centre claims an ISO- and SOC-certified management system without naming the standards or their scope. Storage location for the standard multi-tenant cloud is not stated, the Premium Cloud add-on is built in Microsoft Azure, and we found no public information on subprocessor locations or where the Aino AI processes document content, so the processing chain is unproven beyond the add-ons and the DPA.

DocuWare

No price figure for any edition, licence or user count appears in the captured pages; the route to cost shown is a demo request followed by a 30-day trial, and the general terms reference a price list whose contents are not public on these pages. Licence mechanics are public — named and concurrent licences with conversion rules, add-on modules requiring a current maintenance and support subscription, 14-day payment terms or prepayment, ex-works prices plus VAT — which describes the model but gives a buyer nothing to compute a total from.

M-Files

The editions page publishes "€65 monthly / per seat Essentials" with the billing period and the plan inclusions listed, and names the add-ons such as Outlook Pro, Premium Cloud and Additional Storage. Enterprise, the add-on prices, storage limits and overage, on-premises licensing and maintenance terms carry no public figures in the captured pages, so a buyer cannot yet compute a full configuration including implementation services.