On 12 October 2026, IQusion announced the start of document system modernisation under an 8 October agreement, illustrating a combined implementation scope. An enterprise document system must operate alongside existing roles, reference data and services.

Press release · based on IQusion materials

Capability and the team’s task

Implementation therefore starts by defining boundaries and dependencies. IQusion combines document-flow discovery, configuration and integration. A platform architect needs to specify what the document system owns, what remains with adjacent systems and how those boundaries will be agreed before detailed engineering begins.

The news and IQusion’s experience

The October scope combines Megapolis.DocNet for 250 users with process configuration, archive migration, integration and training. A September implementation example covers 30 workstations, an executive-authority exchange module and user preparation. These different scales show the software and organisational components in IQusion’s document work. They describe reported contractual scope rather than measured operational outcomes.

Questions for your own implementation

  • System boundaries
  • service dependencies
  • reference-data ownership

These practical considerations are editorial explanations for this website’s audience.

About the company and sources

IQusion is the brand used by ТОВ «АЙКЮЖН ІТ», EDRPOU 40026988. The examples refer to the scope reported in company announcements. Contract dates and supplier identifiers were checked against Prozorro on 19 October 2026.

IQusion: company profile and publications

Related service explanations