Document management software: types, rollout and cost

Document management software is a system that gathers a company's documents in one place, moves them along an approval route and keeps the history of every change. Instead of folders on a drive, emails and chats where a contract gets lost between people, the document follows a clear path: created, approved, signed, sent, archived.

Below we look at how an EDMS differs from EDI — the legally binding exchange of documents between companies in Russia — and ECM, what classes of software exist and what each one actually covers, why you need an electronic signature and exchange through an operator, what the rollout stages are, what drives the price and where the law says documents with personal data must be stored.

What is document management software?

In short: it is a system that moves a document along a route on its own and keeps its history, rather than simply dropping files into a folder.

An ordinary file drive stores documents but does not manage them. Nobody can see who is holding up an approval, which version of a contract is current or who made an edit. Document management software closes exactly this gap: a document has a route, owners, deadlines and a full history of actions. A manager can see where the process stands without asking "what stage is the contract at".

Such software has three jobs. The first is to bring order to internal documents: approvals, assignments, execution control, a searchable archive. The second is the exchange of legally binding documents with counterparties and government bodies using an electronic signature. The third is to connect documents with the company's other systems, so that data is not carried by hand between 1C, the accounting and ERP platform most Russian companies run on, CRM and the finance team.

EDMS, EDI or ECM — what is the difference?

In short: an EDMS runs internal documents, EDI handles external exchange, ECM manages all of a company's content. The terms get confused, and that is how companies end up buying the wrong thing.

The easiest way to separate them is by the object and the boundary.

In practice the boundary moves: many products combine EDMS and EDI in a single interface. But their jobs differ, and that matters when choosing. A company that needs to bring order to contract approvals does not have to pay for a full ECM platform. And the reverse: an internal EDMS on its own does not give you a legal way to exchange invoices with a counterparty — that requires an EDI operator. Document management is part of the broader task of process automation, and how that works as a whole is covered in the article on business process automation.

What kinds of document management software are there?

In short: the class of software is defined by the job, and there is no universal solution that covers everything.

The choice between off-the-shelf and custom is a separate fork, and it is settled not by the subscription price but by how distinctive the company's process is. If approvals and document storage are standard, the off-the-shelf product wins. If document flow depends on non-standard logic or is part of a competitive advantage, an off-the-shelf product will need endless tuning. A detailed comparison with the numbers is in the article “Custom system or off-the-shelf”.

Internal or external document flow: which to cover first?

In short: start where documents get lost and cost the most, not where the connection is easiest.

The internal side means contracts, orders, internal memos, requests. The pain here is approval: the document travels by email, stalls while an approver is on holiday, disappears in a thread. The external side means exchange with counterparties and the tax service. The pain here is paper: printing, signing, delivery, storing originals.

Which to connect first depends on where the losses are larger. A company sending hundreds of outgoing invoices a month is better off starting with external EDI. A company where a contract takes weeks to clear between departments should start with an internal EDMS. A common mistake is to connect whatever is technically simpler rather than whatever costs more. A separate document management task is recognizing incoming source documents so that data from scans is not keyed in by hand; how that works is covered in the article on AI recognition of source documents in 1C.

Electronic signature and exchange through an operator

In short: inside the company a simple signature is enough, but exchange with the tax service requires a qualified electronic signature and an accredited EDI operator.

What gives an electronic document legal force is the signature. For internal documents a simple or unqualified electronic signature is often enough. But for formalized documents — invoices and UPDs — the rules are stricter:

Electronic UPDs and invoices are signed with a qualified electronic signature and transmitted exclusively through accredited EDI operators in formats approved by the Federal Tax Service — a walkthrough of how the electronic UPD works, Diadoc, a Russian EDI operator.

This means you cannot simply "email an invoice as a PDF": the exchange goes through an operator. Since January 1, 2026, the electronic UPD has become the primary format for companies working through EDI, and older tax service formats are gradually being retired. The practical conclusion when choosing software: if the company needs to exchange documents with counterparties, the product has to be connected to an EDI operator, not just keep an internal archive.

What stages does a rollout consist of?

In short: five stages, and the first two cannot be skipped, otherwise the existing mess simply moves into the system.

1. Document flow audit (as-is). Which documents circulate, along which routes, where they stall and what that costs in hours. What you need to look at is the real path of a document, not the written policy.
2. Designing the target process (to-be). How approvals and exchange should work after the rollout. This is where the process gets fixed and unnecessary steps are removed, and only then is it locked into the system.
3. Choosing the solution. Off-the-shelf, cloud, low-code or custom; which integrations are needed; where the data is stored. This fork is resolved after the first two stages.
4. Rollout. Configuring routes, integrations with 1C and CRM, archive migration, connecting the signature and the operator, training. Launching everything at once almost always ends in a return to email.
5. Support. Measuring the effect, refining routes based on feedback, supporting users.

The main mistake is choosing the software before the real process has been described. What then gets automated is the mess, and the rework costs more than the original rollout. How to tie document management into the 1C and CRM systems already running, as a single connected loop, is covered in the article on system integrations.

How much does it cost and what drives the price?

In short: the licence price is the tip of the iceberg; what you need to count is total cost of ownership over three to five years.

Quoting specific price lists is pointless: the range varies tenfold depending on the process. It is more useful to understand the cost drivers:

• the number of approval routes and how complex they are;
• the volume of integrations with 1C, CRM, accounting and banks;
• archive migration, its volume and quality;
• how deeply the system has to be adapted to non-standard logic;
• connecting the electronic signature and an EDI operator;
• staff training and ongoing support.

The point that regularly breaks budgets: rollout costs often exceed the price of the licences themselves. Configuring routes, integrations and moving the archive cost more than the subscription, and the vendor's website shows only the subscription. An off-the-shelf product has a low entry cost, but the payments repeat and the customizations accumulate. A custom system has a higher entry cost, but the code and the rights stay with the company. Many companies arrive at document management while moving away from spreadsheets; why Excel stops coping is covered in the article “When a business should move off Excel”.

Personal data in documents and Federal Law 152-FZ

In short: contracts, HR files and client documents contain personal data, and under Federal Law 152-FZ, Russia's personal data protection law, that data must be stored on servers in Russia.

Document flow almost always contains personal data: names, passport details, phone numbers, bank details. That turns the choice of software from a question of convenience into a question of legal compliance. The localization requirement is stated directly:

When collecting personal data, including over the internet, the operator must ensure the recording, systematization, accumulation, storage, updating and retrieval of the personal data of Russian citizens using databases located in the territory of the Russian Federation — Federal Law 152-FZ, article 18, part 5, ConsultantPlus, a Russian legal reference database.

From this comes a practical criterion for the choice. You need to know where the documents and the archive are physically stored: if a cloud service keeps the data outside Russia, that is a risk. A personal data operator must be able to prove on paper where the data sits. How to build a setup that documents and personal data never leave is covered in the article “AI models without data leaks”.

Why does the software fail to take root?

In short: the cause almost always sits outside the software — in the process, the people and where the data is stored.

The typical scenarios, repeated from company to company:

1. The chaos was moved across. An unfixed process, locked into a system, starts reproducing its problems faster. The only cure is the as-is and to-be stages.
2. The off-the-shelf product did not fit the process. What follows is either endless customization or breaking the business to fit someone else's approval logic.
3. Staff were not trained. People go back to email and paper because it is more familiar and faster.
4. Data in someone else's cloud. Documents with personal data move to an external service, and control over them is lost.
5. Dependence on the contractor. Every month there is a budget line for yet another route tweak, while the business model has not changed.

The first point is the most common. Document management software does not fix a process, it fixes it in place. If the process is broken, the system will cement the breakage.

What is changing in the Russian market?

In short: foreign vendors have left, domestic EDMS products hold a high share in the public sector, and AI in document management is still running ahead of actual adoption.

A few facts that are useful when choosing a system for several years ahead.

Growth and import substitution. According to a review of the EDMS market, the top 20 Russian vendors grew their revenue by roughly 25% in 2024, and about 80% of Russian state-owned companies moved to domestic electronic document management systems. At the same time the market is stabilizing: analysts expect more restrained growth within 10% a year.

AI in document management. The same review records a gap between interest and practice:

About 60% of companies believe in the value of artificial intelligence, but only around 30% have actually adopted AI in their document management — the review “EDMS Market 2025”, CNews.

For an owner this means two things. It makes sense to choose a domestic system with data stored in Russia, and to treat "AI inside" promises as a feature to be tested on your own process rather than taken on faith.

Where to start?

An order of steps that does not have to be redone:

1. Define the scope. Internal approvals, external exchange with counterparties, or both. The class of software follows from this.
2. Describe how a document moves today. With the delays and the workarounds, not according to the policy.
3. Put a number on the disorder. Hours spent on approvals, lost documents, fines. Without that figure there is nothing to measure the effect against.
4. Design the target route. Remove the unnecessary steps first, then lock it into the system.
5. Check where the data is stored. Documents with personal data belong on servers in Russia, under 152-FZ.
6. Choose a solution that fits the process. Standard document flow is covered by an off-the-shelf product; a process with its own logic requires a custom system.

At IncubeAi we build systems around a company's process: document management, integrations with 1C and external services, source document recognition and AI agents. The code and the data stay on the business's side, the data stays in Russia, the work runs under a contract, and support continues after handover. If the process is already clear, start with a conversation about it — discuss your project.

Sources

• Federal Law "On Personal Data" No. 152-FZ of July 27, 2006, article 18, part 5, ConsultantPlus — the localization requirement: the personal data of Russian citizens must be stored in databases located in Russia.
• Diadoc, “The electronic UPD and invoice: the basics and how the process works” — exchanging formalized documents through an accredited EDI operator with a qualified electronic signature.
• The review “EDMS Market 2025”, CNews — growth of the top 20 vendors in 2024, the share of domestic EDMS products in the public sector, and the gap between interest in AI and its adoption.