Comarch ECM

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.

Who may see and change which document, what happened to it, and whether earlier states can be recovered: version history, check-in and check-out, role- and attribute-based rights, and an audit trail of reads and changes.

0 — Files overwrite each other; rights only at folder level or not described; no log of who did what.

3 — Version history and folder permissions exist, but no check-out, no record-level rights and no documented audit log.

5 — Version history with restore, check-in and check-out, roles and groups with document-type or record-level rights, and an audit log of changes documented.

8 — Metadata-driven permissions (by department, client or confidentiality), audit trail covering reads, exports and deletions, single sign-on and directory sync (Entra ID, LDAP) documented, and administrators' own actions logged.

10 — Access is provable: the audit trail is tamper-evident and exportable, permission changes are themselves versioned, field-level rights and need-to-know access for HR or legal records documented, and the log retention period stated.

GoBD-compliant, revisionssicher archiving: immutability of archived documents, retention schedules and deletion, tax-audit data access, and the independent evidence behind the claim — scored on what is certified and documented, not on the word "GoBD-konform".

0 — No statement on archiving, retention or GoBD.

3 — "GoBD-konform" or "revisionssicher" claimed with no certificate, no description of how immutability is achieved and no retention settings documented.

5 — Archived documents documented as unchangeable, retention periods configurable per document type, deletion after expiry, and a sample Verfahrensdokumentation or GoBD guidance offered.

8 — An auditor's report (IDW PS 880 or comparable) published or named with its scope and date, WORM or equivalent storage described, legal hold, GDPR deletion reconciled with retention duties, and Z1–Z3 tax-audit export documented.

10 — Archiving is evidenced end to end: current Testat with scope covering the cloud and on-premises editions as sold, retention and deletion logged and reportable, long-term formats (PDF/A) enforced, and a documented procedure for the tax audit and for moving the archive without breaking its integrity.

What happens to a document after it arrives: approval and invoice workflows, tasks and deadlines, and the connectors that tie the DMS to ERP, accounting, DATEV, Microsoft 365 and the rest of the stack.

0 — No workflows; documents are stored and nothing else.

3 — A fixed approval or sharing step and a handful of named integrations, with no workflow designer and no API documentation.

5 — A workflow designer for approvals and invoice processing, tasks with deadlines and substitutes, Microsoft 365 or Outlook integration, and a documented REST API.

8 — Graphical workflow modelling without code, invoice workflow with ERP or DATEV handover documented, connectors for named ERP systems (SAP, Microsoft Dynamics, DATEV) with their scope, webhooks or events, and e-signature integration.

10 — Workflows are a platform: versioned workflow definitions, process reporting with throughput times, a public API reference with rate limits and a sandbox, a partner marketplace of integrations with stated maintainers, and workflow history kept in the audit trail.

Finding documents again and taking them with you: full-text and metadata search, saved searches and mobile access, and whether documents, metadata, versions and audit trail can be exported in documented formats when the contract ends.

0 — Folder browsing only; no export beyond downloading single files.

3 — Full-text search exists, but no metadata filters, and bulk export is undocumented or only on request.

5 — Full-text and metadata search with filters and saved searches, mobile or web access, and bulk export of documents with their metadata (for example CSV or XML) documented.

8 — Search across versions and attachments with permissions respected, export of documents in original format with metadata, versions and audit trail in a documented structure, and an import path from other DMS or file shares named.

10 — The exit is designed in: a documented complete export with schema, export available self-service at any time, the post-termination retrieval window and data deletion stated, and archives stored in open formats so a successor system can take them over intact.

Who the contracting entity and its owner are, where documents and their metadata are stored and processed in the cloud edition, and who the subprocessors are — including any AI provider that reads document content. Independently sourced by the sovereignty pipeline.

0 — Non-EU contracting entity, no statement on where documents are stored, and subprocessors unnamed.

3 — An EU entity contracts, but the cloud edition runs on a non-EU-controlled hyperscaler without a stated safeguard, or the subprocessor list is absent.

5 — EU contracting entity and EU data centres stated for the cloud edition, with a DPA, but significant parts of the chain (hosting, AI processing, support) are non-EU-controlled without a stated safeguard.

8 — EU entity, documents and metadata stored in named EU data centres, subprocessor list with locations published, AI processing location disclosed, an on-premises or private-cloud option offered, and certifications (ISO 27001, BSI C5) published.

10 — Sovereign end to end and evidenced: European ownership, EU entity, every processing location and subprocessor European, customer-controlled keys or on-premises operation available, and certifications with their scope published.

Whether a buyer can compute the cost of a given number of users, storage and modules — including cloud versus on-premises licensing, maintenance, implementation partner fees and price increases — from public pages alone.

0 — No public prices at all; every quote comes from sales or a partner.

3 — A "from" price or a single edition priced, but modules, storage, maintenance and partner implementation are unstated — the real cost is unknowable.

5 — Editions priced per user or per month, but at least one commonly needed cost (storage, archiving or workflow module, maintenance percentage, onboarding) is missing or "on request".

8 — Every edition and module priced publicly, storage limits and overage stated, on-premises licence and maintenance terms given, and contract term and notice period published.

10 — Complete cost computability: a configurator or price list covering users, modules, storage and deployment model, partner implementation priced or bounded, and price-increase terms on a public page.