Häufig gestellte Fragen
What is the difference between ECM and DMS?
A document management system (DMS) manages, stores and archives individual electronic documents and embeds them in workflows, whereas enterprise content management (ECM) is much broader in scope and covers all of a company's unstructured content across its entire lifecycle. According to the model of the industry association AIIM, ECM comprises the areas Capture, Manage, Store, Preserve and Deliver, with the classic DMS essentially covering the Manage area. A DMS is therefore usually one component of a more comprehensive ECM approach. For pure document workflows a DMS is often sufficient, while ECM becomes relevant for larger volumes of heterogeneous content such as emails, web content, contracts and records.
What functions does an ECM system include?
An ECM system typically maps the content lifecycle along five functional areas that go back to the AIIM model: Capture (ingestion via scanning, email import or interfaces, often with OCR document recognition), Manage (versioning, tagging, permissions and search), Store (short-term storage), Preserve (audit-proof long-term archiving) and Deliver (provision and integration into business processes via a workflow engine). In practice, an incoming document usually passes through these stations automatically – for instance when an invoice is scanned, read out, assigned to a transaction, routed for approval and then filed in an audit-proof archive. The concrete scope of functions varies depending on the vendor and the expansion stage of the platform in use.
Why is ECM becoming increasingly important?
Industry estimates assume that around 70 to 80 per cent of business information exists in unstructured form, i.e. as office documents, scans, emails, PDFs, presentations or media files; some analyses by Gartner and IDC even put the share at 80 to 90 per cent. Such content is harder to capture and analyse electronically than structured database data and is also growing significantly faster. ECM is intended to ensure that this content is systematically captured, classified, enriched with metadata and correctly retained, so that it becomes a usable asset rather than uncontrolled ballast. Added to this are growing compliance and documentation obligations that demand orderly, traceable document management.
How are ECM and ERP connected?
ECM and ERP are complementary systems with different tasks: the ERP manages the structured transaction, such as a purchase order or a posting, while the ECM stores the associated documents and makes them accessible from within the ERP. If a supplier invoice is posted in the ERP, for example, the original document can be opened directly from the accounting entry via a link. Some ERP solutions include a simple document module, others rely on connecting dedicated ECM platforms through interfaces. Clean integration avoids duplicate filing and ensures the document is visible exactly where the business transaction is processed.
What legal requirements must an ECM system meet in Germany?
In Germany, the GoBD above all shape the requirements for proper, immutable and traceable filing of tax-relevant records, supplemented by a GoBD Verfahrensdokumentation describing how the documents are handled. Retention periods under tax and commercial law are, depending on the document type, ten years for commercial books and annual financial statements and six years for business emails and commercial letters, while the period for accounting records was shortened from ten to eight years by the Fourth Bureaucracy Relief Act with effect from 1 January 2025 – although ten years continue to apply to credit, securities and insurance institutions. A complete audit trail documents who changed which content and when. Since these rules are complex and subject to change, consulting your tax advisor is recommended in individual cases.
What does the term content services mean in the context of ECM?
Content services, or content services platforms (CSP), is a newer term with which the market research firm Gartner replaced the classic ECM concept in its analyses in 2017, renaming the ECM Magic Quadrant accordingly. Instead of a single monolithic suite, the concept emphasises a modular approach of services and microservices that work together via shared interfaces and repositories and serve different content types and use cases. In substance, content services overlaps heavily with ECM but shifts the focus from purely managing unstructured content towards cross-platform, integrable services. In practice, the terms ECM and content services are therefore often used synonymously or as an evolution of one another.