Document Management (DMS)
Comarch ECM
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: not determined
by Comarch S.A. · www.comarch.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Comarch ECM at a glance
- Vendor
- Comarch S.A.
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- Comarch ECM is a document-management product the bench could judge from page titles rather than product documentation. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Comarch ECM is a document-management product the bench could judge from page titles rather than product documentation. Its strongest area is capture: the vendor publishes pages on OCR and on XRechnung e-invoicing in Germany, and capture and indexing drew the highest single score recorded, 3. That is also where the judges split most — scores range 0 to 3, some crediting that capture is publicly addressed, others declining to count page titles as evidence of a pipeline. Document workflows scored 0 to 2, mostly 2, on a Comarch Workflow product page and pages on EDI implementation. Weakest are versioning and permissions and search and portability, both 0 to 0: the judges found no public information on version history, access rights, audit logs, search, or any documented export of documents, metadata and audit trail. Audit-proof archiving reached 0 to 1, its captures being regulatory news on Italy and Germany rather than product statements. Sovereignty scored 0 to 1: the only confirmed fact is that Comarch SA is the administrator of your data. No public prices appear on any captured page.
Speaks for it
- Vendor publishes pages on OCR and on XRechnung e-invoicing in Germany, so capture is publicly addressed.
- A Comarch Workflow product page and pages on EDI implementation via web or integration exist.
- The GDPR policy names Comarch SA as the administrator of your data.
- Capture and indexing drew the highest single score recorded for this product, 3.
Held against it
- We found no public information on version history, check-in and check-out, role- or record-level rights, single sign-on or any audit log.
- We found no public information on search, mobile access, or a documented export of documents with metadata, versions and audit trail.
- The captured archiving pages are regulatory news on Italian and German e-document rules, not product documentation.
- Beyond the administrator's name, we found no public information on data residency, ownership, a subprocessor list or where any AI processing runs.
- No public prices appear on any captured page.
Best for
- You are comparing vendors for OCR capture and German XRechnung e-invoicing and value a vendor that publicly addresses these topics.
- You are shortlisting for workflow and EDI integration and plan to verify the detail in demos and sales conversations.
- You are comfortable sourcing capability details and every price through sales or partner conversations.
Avoid if
- You need version history, access rights and audit logging documented before a system can enter evaluation.
- You must show a tax auditor or Steuerberater public evidence of immutable archiving and retention settings.
- You need a documented export of documents, metadata, versions and audit trail for contract end or migration.
- You need data residency, ownership and the subprocessor chain documented before a data-protection review.
The scores
Too little public evidence to rate — fewer than 1 captured source or 3 proven facts — so no star rating is shown. The panel's reasoning is below.
Capture, OCR & indexing
Show reasoningHide reasoning
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
The only capture evidence is that pages titled OCR and XRechnung e-invoicing in Germany exist. We found no public information on intake channels, metadata fields, classification, or automatic field extraction, so this is OCR mentioned and little more. 3 4
The Records Manager
Nothing captured tells me how documents get in: I found no public information on scanning, email or mailbox intake, OCR, classification, or metadata set at capture rather than typed later. The OCR and German e-invoicing pages were captured but yielded no confirmed detail on automatic field extraction or on XRechnung and ZUGFeRD being read as structured data. 1 3 4
The IT Integrator
The vendor's site carries a page on OCR and one on XRechnung e-invoicing in Germany, so capture is at least addressed publicly. We found no public information on intake channels, indexing, classification, field extraction or duplicate detection, or on whether e-invoices are read as structured data rather than as pictures. 3 4
The Mittelstand Owner
Comarch publishes pages on OCR and on XRechnung e-invoicing for Germany, so the topics exist, but the captures show no detail: we found no public information on intake channels such as scanner, mailbox or folder, on metadata fields and automatic extraction, or on whether e-invoices are read as structured data. 3 4
The Data Protection Officer
We found no public information on how documents get in — nothing on scanner, mailbox or Microsoft 365 intake, on OCR, or on whether XRechnung and ZUGFeRD invoices are read as structured data; the captured OCR and e-invoicing pages yielded no confirmed product facts. For a system that will hold personnel files and health certificates, I also found no word on where any AI-assisted capture runs. 3 4
The Skeptic
The vendor's site carries a page on OCR and one on XRechnung e-invoicing in Germany, yet the captures confirm nothing about scanning, email intake, classification, metadata extraction or whether e-invoices are read as structured data rather than as pictures. A page named OCR is a promise, not a pipeline. 3 4
Versioning, permissions & audit trail
Show reasoningHide reasoning
How this is scored
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.
The GoBD Auditor
We found no public information on version history, check-in and check-out, role or record-level permissions, or any audit log of reads and changes. Having sat on the company side of audits, I will not credit a right or a log I cannot see documented. 1
The Records Manager
I found no public information on version history or restore, check-in and check-out, role- or record-level rights, single sign-on or directory sync, or any audit log of reads and changes. Rights and history that are not documented are rights and history I cannot rely on when a 2019 contract has to be produced. 1
The IT Integrator
We found no public information on version history, check-in and check-out, role- or record-level rights, single sign-on or any audit log. With nothing published here I cannot assess directory sync or provable access for auditors. 1
The Mittelstand Owner
We found no public information on version history, check-out, role- or record-level rights, single sign-on or any audit log; in a forty-person company where only the accountant should see invoices, that silence settles it. 1
The Data Protection Officer
We found no public information on version history, check-in and check-out, role- or record-level rights, or any audit log of reads, exports and deletions. The privacy disclosure I can confirm says only that the administrator of the data is Comarch SA, with nothing on who inside a customer may see which document. 1 2
Audit-proof archiving & retention
Show reasoningHide reasoning
How this is scored
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.
The GoBD Auditor
The captured archiving content is two news articles about e-document archiving rule changes in Italy and Germany, not product documentation. I found no auditor's report with scope and date, no description of how archived documents are kept unchangeable, no retention settings per document type, and no Z1–Z3 tax-audit export — a buyer would have nothing to show their Steuerberater. 5 6
The Records Manager
The archiving-related pages captured are news items about Italian and German regulation changes, not statements about the product; I found no public information on immutability of archived documents, configurable retention, deletion after expiry, WORM storage, a sample Verfahrensdokumentation, or any auditor's report. Nothing captured would let me answer a tax auditor about this archive. 5 6
The IT Integrator
What the captured pages show on archiving is market commentary on changing e-document archiving rules in Italy and Germany, not product documentation. We found no public information on retention settings, immutability of archived documents, a Verfahrensdokumentation, an auditor's report, or tax-audit export. 5 6
The Mittelstand Owner
The captured archiving pages are news items about Italian and German regulation changes, not statements about the product itself; we found no public information on immutability of archived documents, configurable retention, a Verfahrensdokumentation or any auditor's certificate. 5 6
The Data Protection Officer
The captured pages on archiving are regulatory news about Italy and Germany, not product documentation; we found no public information on immutability of archived documents, retention schedules, deletion after expiry, or any auditor's report. I also found no word on how GDPR deletion is reconciled with retention duties — my central question for any archive holding contracts and certificates. 5 6
The Skeptic
The only archiving-related captures are regulatory news pieces on postponed Italian e-document rules and a German action plan — commentary on the law, not statements about the product's archiving. We found no public information on immutability, retention settings, a Verfahrensdokumentation, WORM storage or any auditor's report; not even a "revisionssicher" claim is confirmed in what was captured. 5 6
Document workflows & integrations
Show reasoningHide reasoning
How this is scored
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.
The GoBD Auditor
A workflow product page and a page on EDI implementation via web or integration exist. We found no public information on approval or invoice workflows, tasks and deadlines, DATEV or ERP handover, or documented APIs — page titles are not workflow documentation. 7 8
The Records Manager
A workflow product page and an EDI implementation page were captured, but I found no public information on approval or invoice workflows, tasks with deadlines and substitutes, a workflow designer, DATEV or ERP connectors, or a documented API. I cannot see what happens to a document after it arrives. 7 8
The IT Integrator
A dedicated Comarch Workflow product page and pages on EDI implementation via web or integration show that workflows and integrations are at least public topics. We found no public information on a workflow designer, a documented API with webhooks, e-signature, or connectors to ERP, DATEV or Microsoft 365 with their stated scope, and stated connector scope is the first thing I look for. 7 8
The Mittelstand Owner
A product page for a workflow tool and one on EDI implementation exist, which hints at approvals and an accounting handover, but we found no public information on a workflow designer, tasks with deadlines and substitutes, a documented API, or named connectors such as DATEV, SAP or Microsoft 365. 7 8
The Data Protection Officer
We found no public information on approval or invoice workflows, a workflow designer, tasks with deadlines, or connectors to ERP, DATEV or Microsoft 365 with their scope. The captured workflow and EDI pages gave no confirmed product facts. 7 8
The Skeptic
A product page named Comarch Workflow exists for public administration and a piece describes EDI implementation as web or integration, but neither capture confirms a workflow designer, tasks with deadlines, ERP or DATEV handover, or an API. Named but undocumented is as far as I will credit. 7 8
Search, retrieval & exit
Show reasoningHide reasoning
How this is scored
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.
The GoBD Auditor
We found no public information on full-text or metadata search, saved searches, mobile access, or bulk export of documents with metadata, versions and audit trail. Without a documented exit path, the buyer downloads what they can and hopes. 1
The Records Manager
I found no public information on full-text or metadata search, filters or saved searches, mobile access, or a documented bulk export that keeps documents, metadata, versions and audit trail together. The exit path a successor system would need at contract end is undocumented in everything captured. 1
The IT Integrator
We found no public information on full-text or metadata search, saved searches, mobile access, or any documented export of documents with their metadata, versions and audit trail. With no published exit path I could not plan a migration in or out without depending on the vendor's services team. 1
The Mittelstand Owner
We found no public information on full-text or metadata search, saved searches, mobile access, or any export of documents, metadata and audit trail when a contract ends; as an owner I want the exit designed before I sign, not after. 1
The Data Protection Officer
We found no public information on full-text or metadata search, saved searches or mobile access, and nothing on a documented export of documents with their metadata, versions and audit trail when a contract ends. Without an evidenced exit path, an operator's archive is a one-way door. 1
The Skeptic
We found no public information on full-text or metadata search, saved searches, mobile access, or any documented export of documents, metadata, versions and audit trail. From what was captured, the exit path is undocumented, and portability without a documented export is exactly what I decline to take on faith. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
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.
The GoBD Auditor
One confirmed fact names Comarch SA as the administrator of your data, and a GDPR policy page exists. Beyond that, we found no public information on the entity's jurisdiction, ownership, where documents and metadata are stored, the subprocessor list, or where any AI reading document content runs — nothing I could rely on in a data-protection review. 8 2
The Records Manager
The only confirmed fact is that Comarch SA is named as the administrator of your data, alongside a captured GDPR policy page; I found no public information on the entity's jurisdiction, where documents and metadata are stored or processed, a subprocessor list, or an on-premises option. Processing location is the first question I put to a vendor, and it is unstated here. 2 8
The IT Integrator
Comarch SA is named as the administrator of your data, but the captured pages give no confirmation of its jurisdiction, no data-centre locations, no subprocessor list and no statement on where OCR or AI processing runs. The independently sourced attributes likewise all come back unknown, so nothing on this criterion is evidenced. 2 8
The Mittelstand Owner
The GDPR policy names Comarch SA as the data administrator, which is a start, but we found no public information on where documents and metadata are stored in the cloud edition, on the company's ownership or jurisdiction, or on any subprocessor list including AI providers. 2 8
The Data Protection Officer
The only confirmed fact is that the administrator of the data is Comarch SA, with no statement of its jurisdiction or ownership; we found no public information on where the cloud edition stores documents and metadata, on any AI provider reading document content during capture, or on the subprocessor chain. Personnel files, health certificates and customer contracts in the cloud edition therefore have no publicly assignable location. 2 8
The Skeptic
The single confirmed statement in the entire capture is who administers the data — Comarch SA — with no jurisdiction, ownership, storage location, subprocessor list or AI-processing location published. The privacy-policy page was captured but confirms nothing on data residency or subprocessors. 8 2 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
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.
The GoBD Auditor
We found no public prices on the captured pages: no per-user edition prices, no storage or module costs, no maintenance or on-premises licensing terms, no contract term or notice period. Every figure would have to come from sales or a partner, so no buyer can compute a total from public pages alone. 1
The Records Manager
No captured page shows a price of any kind — no editions or per-user fees, no storage limits, maintenance, contract term or notice period. A buyer cannot compute any part of the cost from the public pages I saw. 1
The IT Integrator
We found no public prices — no editions, per-user figures, storage limits, maintenance terms or on-premises licensing. From public pages alone the cost of a given number of users and modules is not computable. 1
The Mittelstand Owner
We found no public prices at all: no per-user or per-month figure, no storage limits, no module, maintenance or implementation costs, so before a partner visit I could not even roughly compute what forty users plus archiving would cost me. 1
The Data Protection Officer
We found no public information on prices for any edition, user, storage tier or module, nor on maintenance terms, partner implementation fees or price-increase terms; the captured pages show no price at all. 1
The Skeptic
We found no public prices at all — nothing on editions, per-user fees, storage, maintenance or on-premises licensing. From these captures a buyer cannot compute any part of the cost, which leaves every number behind a sales conversation. 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Comarch ECM
Is Comarch ECM European?
Not determined: the vendor’s pages as captured do not say where Comarch ECM is based.
Where does Comarch ECM store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Comarch ECM have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Comarch ECM?
As of 21 Oct 2026, the panel rates PaperOffice (3/5), AMAGNO (3/5) and Doxis (3/5) highest among the other 17 Document Management (DMS) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is AMAGNO (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Comarch ECM alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 56 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 25 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.comarch.com Checked 20 Oct 2026 Details →
- 2 Data processing agreement (dpa) — found from the homepage www.comarch.com Checked 20 Oct 2026 Details →
- 3 Capture, OCR & indexing — found from sitemap www.comarch.com Checked 20 Oct 2026 Details →
- 4 Capture, OCR & indexing — found from sitemap www.comarch.com Checked 20 Oct 2026 Details →
- 5 Audit-proof archiving & retention — found from sitemap www.comarch.com Checked 20 Oct 2026 Details →
- 6 Audit-proof archiving & retention — found from sitemap www.comarch.com Checked 20 Oct 2026 Details →
- 7 Document workflows & integrations — found from sitemap www.comarch.com Checked 20 Oct 2026 Details →
- 8 Document workflows & integrations — found from sitemap www.comarch.com Checked 20 Oct 2026 Details →