DocuWare vs M-Files

DocuWare

OCR and handwriting recognition, pre-processing, splitting and AI classification are documented, and the extraction engine is genuinely trainable: a custom model learned from a few sample documents, confidence scores per field, verified bank details, and a named validation step in the invoice process. What keeps it below the top band is that XRechnung and ZUGFeRD appear by name nowhere on these pages (only PEPPOL and generic e-invoice validation), and we found no public information on mailbox or Microsoft 365 intake, on duplicate detection at intake, or on where the AI that reads the documents is processed.

M-Files

Scanning and drag-and-drop with conversion to searchable PDF is documented, as is automatic email archiving through an Outlook add-on and native Microsoft 365 intake; classification is described as automatic via the metadata-driven architecture. But we found no public information on a validation step for that automatic classification, on XRechnung or ZUGFeRD being read as structured data, or on duplicate detection — and the built-in Aino AI is described only as supporting "everyday document tasks", with no word on where that processing runs.

DocuWare

What is documented: documents can be locked against other users during editing, a workflow history shows which user made which decision, and the licence terms describe named and concurrent users. We found no public information on a version history with restore, on roles or folder-level permissions, on single sign-on or directory sync, or on an audit log covering reads and exports; the sentence about exporting the history is phrased as what a system 'should' offer rather than as a documented feature.

M-Files

Check-out of documents and an Event Log of changes to the vault are documented, and the editions page names version control, access controls and — for Enterprise — federated authentication plus an extended audit log with exports. We found no public information on metadata-driven permissions, on whether the log covers reads, exports and deletions or administrators' own actions, or on any tamper-evidence; the vendor's own user guide states modifications made before the feature was enabled do not appear in the log.

DocuWare

'Revisionssichere Archivierung' is claimed for invoice processing, and the archiving pages are largely legal education — German retention periods, when paper originals may be destroyed, that e-invoices must stay in original digital form — plus a generic statement that such systems offer workflow tools for protecting or destroying documents at set times. We found no public information on how immutability of archived documents is achieved, on WORM storage, on an auditor's report or Testat, or on a sample Verfahrensdokumentation; the captured page itself points to certifications on a separate page and makes no certification claim of its own.

M-Files

Retention is mentioned — integrated governance is said to enforce compliance and retention policies — and archived objects, PDF/A conversion and a Compliance Kit are documented, but GoBD is never claimed and no auditor's report is named anywhere on the captured pages. We found no public information on how immutability of archived documents is achieved, on retention periods configurable per document type, or on tax-audit data access; the documented "archiving" is an admin-right marker on objects, not evidence of revisionssichere storage.

DocuWare

Workflow design is documented in depth: drag-and-drop modelling without programming, defined triggers, deadlines with escalation, substitution rules, task assignment to employees or roles, automatically updating task lists, a supervising controller and a decision history. The integration side is thinner than the '500+ applications' headline: the API is described only as seamless and available, and we found no public information on an API reference, webhooks or connector scope for named ERP systems — DATEV appears via export formats and a customer reference, and e-signature is covered only as an explanation of the three signature levels.

M-Files

Graphical workflow automation ships in both editions, approval assignments with any-assignee-approval exist down to the API level, and the SAP integration actually states its scope — importing vendor and product data and serving as SAP's content repository — alongside Salesforce, Microsoft Dynamics CRM and an Adobe Acrobat Sign package. What keeps it below the top: we found no public information on substitutes and escalation in workflows, on DATEV or invoice handover, or on a REST API with webhooks — the documented interface is the COM API.

DocuWare

Full-text and index-data search with filters, remote and mobile access are documented, and there is a real export module: scheduled or click-triggered export of index and table-field data as CSV, filtered by document, included in every cloud licence and available on-premises via additional licences. But the documented export feeds accounting systems with index data — we found no public information on bulk export of the documents themselves with their metadata, versions and audit trail, or on an import path from other systems, and for the exit question that is the decisive gap.

M-Files

Executed searches can be saved as reusable views, a Smart Migration tool is documented for moving content in, and a Reporting Databases add-on sends metadata and vault data to a separate database. But we found no public information on bulk export of documents with their metadata and versions in a documented structure, on a complete exit export, or on mobile access — only Enterprise's extended audit log is described as exportable.

DocuWare

The contracting entity is proven European — DocuWare GmbH in Germering, German governing law, Munich venue, personal data processed in Germany and other European countries — and dedicated data centres are offered in the EU and in the USA, alongside a documented on-premises edition. But the sourcing records Japanese ownership (Ricoh, since 2019), and we found no public information on a subprocessor list for hosting, support or the AI that reads document content, or on a data processing agreement; the named processors in the privacy policy are website tools such as Hubspot, SurveyMonkey and Matomo.

M-Files

The provenance identifies a Finnish company (M-Files Oy, Espoo), an on-premises edition is offered, a DPA with a German annex is published, and the trust center claims an ISO- and SOC-certified management system. But the host and location of the standard multi-tenant cloud are not named — Microsoft Azure appears only for the optional Premium Cloud add-on, which carries US CLOUD Act exposure — and we found no public information on where the Aino AI processes document content or on ownership beyond private-equity backing.

DocuWare

No public price appears on the captured pages: the terms speak of individually agreed prices ex works plus VAT, 14-day payment terms for insured deliveries or prepayment otherwise, detailed licence mechanics for named and concurrent users, and a price list that the terms reference but that is not shown on the captured pages. The buying path published is a free demo and a 30-day trial; a buyer cannot compute the cost of a given number of users from anything published here.

M-Files

One edition carries a public figure — Essentials at €65 monthly per seat, with billing period and inclusions listed — and a pricing page is linked from the homepage. But Enterprise and every add-on (Outlook Pro, Reporting Databases, Additional Storage, Premium Cloud) appear without prices, and we found no public information on storage limits, on-premises licensing, implementation or support pricing, or contract term and notice period.