Designing the digital infrastructure of a modern business requires clear alignment of ECM and DMS architectural models with international standards, such as ISO/TR 22957 and ISO 15489-1, as well as local requirements for electronic trust services. Organizations often conflate Enterprise Content Management (ECM), Document Management Systems (DMS), and electronic document management (EDM), which leads to incorrect technology stack selection and inefficient implementation.
When a system for external document exchange is expected to provide long-term archival storage or unstructured content management, it creates architectural gaps. Confusing these concepts can result in a solution that fails to meet operational needs, ignores legislative requirements for qualified electronic signatures (QES), or fails to scale according to records management principles.
Anatomy of concepts: Why EDM, DMS, and ECM are not synonyms
To build a resilient infrastructure, it is necessary to clearly distinguish between these classes of systems.
Electronic Document Management (EDM) often focuses on legally significant exchange and management of electronic documents. True EDM cannot be simplified to merely sending PDF files via email; it is governed by strict legislative and operational requirements regarding formats, certificate validation, and timestamps.
Document Management System (DMS) focuses on the lifecycle of structured documents. These are tools for collaboration, version control, workflow routing, and access rights management within an organization.
Enterprise Content Management (ECM) is a broader strategic concept. ECM covers the management of the entire volume of enterprise content, providing an architecture for storing, classifying, and analyzing both structured and unstructured information.
Process standardization: How ISO 22957 and ISO 15489-1 define requirements for ECM and records management
International standards do not mandate the use of specific software or particular features; instead, they define key principles and guidelines for management organization.
The ISO/TR 22957:2018 report provides foundational recommendations for analyzing business requirements, selecting a vendor or integrator, and implementing ECM technologies. Implementing ECM systems typically requires comprehensive business analysis based on the principles outlined in this document.
The ISO 15489-1:2016 standard defines the rules for records management. According to this standard, management principles apply to records regardless of their structure or form, and extend to various business and technological environments. Applying the principles of ISO 15489-1 allows for effective record management within the complex technological ecosystems of a large enterprise.
Legal validity of documents in Ukraine: The role of laws on EDM and electronic trust services
Designing document management architecture in Ukraine relies on two basic laws.
The Law of Ukraine "On Electronic Documents and Electronic Document Management" provides a definition: an electronic document is a document where information is recorded in the form of electronic data, including mandatory requisites. The law explicitly states that the legal validity of an electronic document cannot be denied solely because it is in electronic form.
The Law of Ukraine "On Electronic Identification and Electronic Trust Services" No. 2155-VIII forms the legal framework for qualified electronic signatures (QES) and trust services. The reliability of EDM depends not only on the presence of a signature but also on verifying the trust in the certificate and the status of the electronic trust service provider.
In practice, this requires the implementation of the following scenarios:
- Verifying the status of a qualified electronic trust service provider via the Central Certification Authority (CCA) registry before implementing an EDM workflow.
- Integrating the corporate EDM system with the "Electronic Court" subsystem to ensure legally significant document exchange.
Architectural risks: What happens when trying to replace an ECM strategy with a local EDM service
Conflating EDM with ECM leads to attempts to solve content management tasks using tools not designed for the long-term lifecycle of documents. This causes architectural limitations when the system is unable to support complex metadata operations (according to ISO 15489-1) or provide flexible search across the entire enterprise database.
To avoid these problems, modern enterprises implement ecosystems of solutions on a unified integration foundation. An example of such a platform is the full-stack JavaScript low-code environment UnityBase — a joint development by the companies of the Intecracy Group alliance (where InBase is a key, but not the only, developer). The UnityBase architecture uses Domain metadata — a unified model for generating APIs, interfaces, and data management, ensuring a high level of access control through Role-Based Access Control (RBAC) and Row-Level Security (RLS) mechanisms.
Specialized enterprise products are built on the mechanisms of the UnityBase platform. For example, Megapolis.DocNet implements enterprise content management (ECM) functionality, the Scriptum product line covers document lifecycle management (DMS/BPM) and long-term repositories, and tools like DealsSign handle external exchange and document signing. This model allows for the separation of functions and avoids overloading systems with tasks they were not designed for.
Glossary of key terms: From metadata to qualified electronic signature
- Enterprise Content Management (ECM): A strategic infrastructure for managing all types of enterprise content.
- Document Management System (DMS): Software for managing the lifecycle, versioning, and routing of documents.
- Electronic Document Management (EDM): The organization of exchange and processing of electronic documents with a focus on legislative and operational management requirements.
- Qualified Electronic Signature (QES): A signature that meets the requirements of Law No. 2155-VIII and ensures the legal significance of interactions.
- Electronic trust services: Services that provide verification, identification, and confirmation of the integrity of electronic data.
- Records management: The practice of long-term management of records (assets with evidentiary value) in accordance with ISO 15489-1 principles.
- Metadata: Structured information describing the context and content of documents, necessary for their identification and correct archival storage.
Comparative matrix: ECM vs DMS vs EDM by key criteria
| Criterion | ECM (Enterprise Content Management) | DMS (Document Management System) | EDM (Electronic Document Management) |
|---|---|---|---|
| Primary focus | Managing all content types (video, scans, files, data) | Managing the lifecycle of structured documents | Exchange of legally significant documents (acts, contracts) |
| Standards and regulations | ISO/TR 22957, ISO 15489-1 (records management) | ISO 15489-1, internal office regulations | Law of Ukraine on electronic documents, Law No. 2155-VIII (QES) |
| Key tools | Full-text search, classification, archiving | Versioning, access rights, approval workflows | Applying QES, verifying service provider status |
| Typical use case | Storing and analyzing technical documentation and media files of a holding | Approving internal orders and contracts between departments | External exchange of service acceptance acts with counterparties |
FAQ
Does an electronic document have legal validity without a qualified electronic signature (QES) in Ukraine?
The Law of Ukraine "On Electronic Documents and Electronic Document Management" stipulates that an electronic document contains mandatory requisites necessary for its identification. The legal validity of an electronic document cannot be denied solely due to its electronic form; however, for legally significant operations and signer identification, the use of QES is regulated by Law No. 2155-VIII.
What is the difference between records management according to ISO 15489-1 and standard file storage in a DMS?
Standard storage in a DMS provides current access and collaboration. Records management according to ISO 15489-1 applies stricter principles regardless of the technological environment, requiring the fixation of evidence of business activity, ensuring their immutability, the presence of clear metadata, and a managed lifecycle.
How can a local EDM system be integrated with state registries and the judicial system?
Integration involves using an architecture capable of interacting with external services, for example, by verifying certificates in the Central Certification Authority (CCA) registry or connecting the corporate system to the "Electronic Court" subsystem for legally significant exchange.