Megapolis.DocNet EDMS
Megapolis.DocNet document management for organisations of any size, including the public sector.
Electronic document management
We implement an EDMS around the institution's processes — from discovery to QES, archive and support.
Scope
What is included
Digitisation
Scanning, recognition, verification and import/export of documents.
Cataloguing
A flexible document catalogue structure managed by an administrator.
Availability
Any document, instantly — even on low-spec servers.
Why an EDMS
Documents get lost between departmentsA transparent route is needed: who drafts, approves, signs, controls the deadline and stores the final version.
Status must be checked manuallyA manager or executor cannot see the full picture without calls, messages and manual spreadsheets.
The archive exists, but search is hardDocuments live in folders, scans or separate systems, so fast search and verifiable action history are missing.
Legal validity is requiredQES, versions, audit trail, access rights, information protection requirements and integrations must work as one process.
Stages and outcomes
Document workflow discovery
We capture document types, routes, roles, directories, deadlines and existing systems. Output — a document-process map with control points.
Document and role model
We describe cards, attributes, statuses, templates, access rights and control rules. Output — an agreed document and role model.
EDMS configuration
We configure routes, tasks, resolutions, search, logs and workspaces. Output — a configured EDMS environment.
Migration and archive
We prepare the electronic archive structure, import, indexing, recognition and quality control. Output — migrated data and archive.
Signature and integrations
We connect the signature, external exchange, APIs, registers, mail, accounting and HR. Output — connected integrations with legal validity.
Pilot, training, launch
We launch a pilot, train users and scale the system. Output — trained users and a support model: SLA, monitoring and evolution.
Documents and data
SEV OVV
Document exchange with executive authorities in regulated scenarios.
NBU Mail
Connection of official exchange channels for financial and public-sector organisations.
Deals, Vchasno, PTAH
External document exchange, contracts, signing and exchange with counterparties.
CRM, ERP, BPM, HR
Connection of documents with finance, HR, processes, tasks and management accounting.
Registers and directories
Single identifiers, organisational structure, classifiers, recipients, counterparties and roles.
Analytics and reporting
Data about deadlines, workload, execution, overdue items, archive and process quality.
why us
Why IQusion
Typical contractor
RiskOff-the-shelf EDMSIgnores the organisation’s records classification scheme, approval routes and operating rules.
No legal validityDigital signatures and retention periods are bolted on later, if at all.
An island systemThe EDMS is not linked to registries, HR or accounting — double data entry.
Support disappearsAfter rollout there is no one to maintain and update the system.
IQusion
RecommendedEDMS for your processesApproval routes, roles and the records classification scheme fit the organisation’s actual structure.
Legal validityDigital signatures, logs and retention are built into the architecture from the start.
Integrated with systemsLinked to registries, HR and accounting systems with no double entry.
Support for yearsOne team takes end-to-end responsibility for the EDMS in production and its ongoing development.
FAQ
Frequently asked questions
Yes. Routes, roles and the records classification scheme are configured for the organisation’s actual structure rather than imposed by an off-the-shelf template.
Digital signatures, action logs and retention periods are built into the EDMS architecture from the outset in line with applicable requirements.
Yes. We integrate the EDMS with registries, the electronic interaction system, HR and accounting systems — with no double entry.
We migrate existing documents and reference data in a dedicated migration stage with data-integrity checks.
experience
Scenarios from our practice
Anonymised examples: what held the customer back, what we changed and the outcome. We do not tie them to specific clients due to NDA.
Documents on paper
Problem
Approvals ran on paper and document status was opaque.
What we did
Deployed the Megapolis.DocNet EDMS with routing, QES and execution control, integrated with SEV OVV for inter-agency exchange.
Result
Approvals sped up, documents move between agencies and status is visible at once.
Archive was inaccessible
Problem
The paper archive took up space and document search was slow.
What we did
Digitised and catalogued the archive and set up full-text search.
Result
Documents are available online and search takes seconds.
No support after launch
Problem
After EDMS rollout there was no support or adaptation to changes.
What we did
Set up support, training and adaptation of the system to new rules.
Result
The system evolves together with the institution's processes.
Related news
See all →
Process Automation
14.05.2026 · 4 min
Process Automation
09.04.2026 · 6 min
Process Automation
16.03.2026 · 5 min
Let’s discuss the task
Describe the task — we’ll propose an approach, integrations and timing. Need technical support?
Contact us →