Organizing document management: routes, bottlenecks, choosing an EDMS, and cost

Organizing document management means setting the order in which a company's documents are created or received, registered, approved, signed, executed and archived. It records who is responsible for each step, how much time that step gets, and where the document is at any given moment. The Russian national standard GOST R 7.0.8-2025 defines document flow itself as “the movement of documents from the moment they are created or received until they have been executed or sent.” This order is held in place by an electronic document management system (EDMS), or document management software: it registers the document, moves it along its route, tracks deadlines and keeps a log of actions. The work of organizing starts before the software is chosen, by describing routes, owners and the places where a document waits longer than anyone works on it.

Below we look at what an EDMS does and how it differs from EDI (legally binding electronic document exchange between companies in Russia) and ECM. The main part covers organizing document management before choosing a system: how to describe routes and owners, how to use dates to find where a document gets stuck, how to calculate what the current process costs, and which parts of the described process an off-the-shelf system will cover. After that come the classes of solutions, the implementation sequence and the reasons it fails, published license prices, the requirements of Federal Law 152-FZ (Russia's personal data protection law) on storing documents, and a list of what to prepare before starting. Approval routes, using contracts as the example, are covered in detail in a separate article: contract document workflow.

What does organizing document management mean, and what does an EDMS do?

In short: organizing sets the rules for how a document moves, and the EDMS enforces them and remembers every action. A shared folder on a server only stores files.

GOST R 7.0.8-2025 “Records management and archiving. Terms and definitions” was approved by Order No. 30-st of Rosstandart, Russia's standards agency, dated January 28, 2025, and has been in force since March 1, 2025. It describes an EDMS as an information system that manages a document through its entire life cycle, up to archival storage or destruction. The system moves document flow into a single database: verbal agreements are replaced by rules the system enforces on its own. Who to pass a letter to, how many days to reply, who signs an order — all of it is written into the route.

In working form, an EDMS covers five tasks:

1. Registration. A letter, order or request gets a number, a date and a record card with the author, addressee and deadline. The standard describes registration exactly this way: recording a document's details in an established form and assigning it a registration number and date.
2. Route. Who endorses it, in what order, who signs it and what happens when the deadline passes. A manager can see whose desk the document is on right now without calling around departments.
3. Execution control. An instruction issued on an incoming letter or order has an assignee and a date. An overdue item becomes visible before a counterparty or an inspection brings it up.
4. Versions and log. Who opened it, who edited it, which version is current. The “I have a different file” argument is settled by the change history.
5. Archive and search. A document can be found by number, counterparty, date or words from its text, and its retention period is set in advance.

A file server and email cover only storage, and only partly. You can't ask them how many letters from the Federal Tax Service, Russia's tax authority, are awaiting a reply, whose desk an order has been sitting on for three days, or which of four copies of a contract was sent to the other party. In an EDMS a report answers these questions, but only if someone has described in advance the rules it is calculated by.

How does an EDMS differ from EDI and ECM?

In short: an EDMS handles documents inside the company, EDI handles legally binding exchange with counterparties, and ECM handles the organization's entire body of corporate information. Mixing up the three acronyms often ends with buying a product built for someone else's problem.

Inside the company, a simple electronic signature is often enough for endorsements and sign-offs. The rule for VAT invoices is stricter. The procedure approved by Ministry of Finance Order No. 14n of February 5, 2021 states directly that issuing and receiving them in electronic form “is carried out through electronic document interchange operators.” A VAT invoice is signed by an authorized representative of the seller, and the signature must be a qualified one (Ministry of Finance Order No. 14n, ConsultantPlus). The same applies to the UPD, a Russian form that combines an invoice and a delivery note, when it serves as a VAT invoice.

The law does not require completion certificates and contracts to go through an operator: the parties can sign them with an electronic signature and exchange them under their own agreement. In practice they usually go through the same channel anyway, so that the entire exchange with a counterparty sits in one place. An internal EDMS without a connection to an operator does not provide legally valid exchange of VAT invoices, and an EDI service without internal routes will not sort out internal orders and letters. Where document management fits into automation as a whole is covered in the article on business process automation.

How do you organize document management before choosing a system?

In short: a manager needs to go through three steps — describe routes and owners, use dates to find where a document gets stuck, and calculate what that costs. Only then does it become clear what a standard system will cover and what will have to be built around your own process.

Records management instructions answer the question of how to draw up and register a document correctly. For an owner, something else matters more: how many days a payment request takes to reach accounting, whose desk it is sitting on, and what that costs the company. Three surveys from 2025–2026 show the scale of the losses:

• According to a survey by VK WorkSpace and Hi-Tech Mail of 4,000 Russians, 42% of employees sometimes spend more time looking for the right file or message thread than working with it (ComNews, May 15, 2026).
• According to a survey by the Weeek service of 1,140 specialists at Russian companies, searching for information takes about an hour and fifty minutes a day on average, and 17% spend four hours or more (Lenta.ru, Alena Shevchenko, July 1, 2026).
• According to a survey by the job site hh.ru (May 5–12, 2025, 3,283 respondents), 38% of workers spend more than six hours a week getting documents, requests and queries approved. Among HR staff the figure is 46% (CNews, February 26, 2026).

The first two surveys were run by vendors of workplace software, and the publications do not disclose the methodology, so the numbers indicate the order of magnitude of the problem. A company gets its own figures by measuring, and that starts with a map of flows. Document flow consists of three directions, and each has its own entry point and its own places where time is lost.

For each flow, list the document types: what the document is, who creates it, how many per month, and where the final version is kept. It usually fits in one table, and that table alone reveals the types that move without any rules. From there, work on the three to five highest-volume types: they carry most of the load, and that is where the effect shows up fastest.

How do you describe routes and owners?

In short: for each high-volume document type, write down the steps, the role at each step, the deadline, the deputy and what happens when the deadline is missed. Above the routes sits an owner with the authority to change the rules.

Routes are described by role, not by name: “head of unit”, “financial analyst”, “chief accountant”. People go on vacation and leave; the role remains. Here is an illustrative example for a payment request:

For each document type, the description should cover six things:

1. Entry. Where the document comes from and who registers it: a secretary, the initiator, or the system itself when a letter arrives through the EDI operator.
2. Steps and roles. Who endorses it, in what order, and which steps run in parallel. Every unnecessary “FYI” sign-off adds a day of waiting.
3. Branching conditions. What changes the route: amount, budget line, legal entity, project, counterparty type. This is where it later becomes clear whether a standard system will be enough.
4. Deadline per step. In business days or hours, with separate deadlines for urgent documents.
5. Delegation. Who signs and endorses when the main person is away, and how soon the document passes to them automatically.
6. Exit. Where the final version is kept, where the paper original is, and who gets a copy.

Above all of this you need an owner — one person with the right to change the rules. They approve new document types, sort out disputed and stuck documents, and are responsible for the reference lists. Without an owner, every exception is decided from scratch, and whoever is loudest wins. What has been described is collected into a written procedure of one or two pages. If the company already has records management instructions and a file classification scheme, the procedure is built on them.

Delegation needs separate attention if the deputy signs documents that go to counterparties. Under Article 17.2 of Federal Law 63-FZ, Russia's electronic signature law, a representative of an organization acting under a power of attorney signs an electronic document with their own qualified signature. The document is accompanied by a power of attorney in electronic machine-readable form, known as an MChD (63-FZ, Article 17.2, ConsultantPlus). One line in the procedure is not enough here: powers of attorney are issued before the system goes live. Sequential and parallel schemes, using contracts as the example, are covered in the article “Contract document workflow”.

How do you find where a document actually gets stuck?

In short: by dates, not by impressions. Take the last two or three dozen documents of a high-volume type, reconstruct the date of each step, and separately calculate how long the document waited and how long people worked on it.

The procedure describes how a document should move; measurement shows how it moves in reality. The measurement process:

1. Sample. For each of the three to five high-volume types, take the last two or three dozen documents from one or two months: payment requests, incoming letters, contracts, orders.
2. Step dates. Using email, 1C, the registration log and correspondence, reconstruct when the document arrived or was created, and when it was handed on, endorsed, signed, executed or sent.
3. Waiting and work. For each step, calculate two times: how long the document sat idle and how long someone actually worked on it. The second is usually measured in minutes, the first in days.
4. Loops. Separately note returns for rework: how many times the document went back and at which step.
5. Causes. Next to each long wait, write down the cause. After two or three dozen documents, the causes start to repeat.

Recurring causes usually fall into a few types, and each has a different fix:

Two causes are so common that they made it into a survey on switching to EDI by Moe Delo, a Russian online accounting service (June 2026, 2,200 respondents from small and medium-sized businesses). At 35% of participants, documents stall when the manager is out of the office, and 33% are held back from a full switch by the signature being tied to a physical token (CNews, July 1, 2026). The survey is about exchange with counterparties, but both causes arise inside the company, so they are worth checking on the internal route as well.

The paper branch from the last row of the table isn't going away either. According to the same survey, only 10% of companies have gone fully paperless. Completion certificates are still issued on paper by 63%, contracts by 45%, and HR documents by 43%. So tracking originals needs to be built into the route from the start, rather than waiting until everyone has switched to electronic signatures.

The measurement also shows which area to start with. If most losses come from hundreds of outgoing invoices and completion certificates, exchange with counterparties is connected first. If orders and requests travel between departments for weeks, start with the internal route. A common mistake is to switch on whatever is technically easier to connect, even though the money is being lost somewhere else.

How do you calculate what the current process costs?

In short: multiply the number of documents per month by the minutes people spend searching, chasing and forwarding, and by the hourly cost. On top of that, add the cost of delay: penalties, missed discounts, blown reply deadlines.

An illustrative example for payment requests:

1. Volume. Two hundred requests a month.
2. Time lost per request. The initiator and the accountant together spend about twenty minutes finding the invoice, reminding approvers and checking the status. That is about 67 hours a month.
3. Rate. At 700 rubles an hour, that comes to about 47,000 rubles a month just on running around after requests. The rate here is illustrative: substitute your own, including payroll contributions.
4. Cost of delay. A payment that was late because an approver was on vacation can cost contractual penalties or a disrupted delivery. A single such incident can outweigh the monthly figure from the previous point.

These numbers are needed twice. Before choosing a system, they show which flow accounts for most of the losses and how much it makes sense to invest in automating it. After launch, they are compared with the new figures, and the effect is shown in days and rubles rather than impressions.

Vendors describe the effect the same way. On August 24, 2026, CNews published Directum's data on an implementation at Right line. Contracts and key financial documents were moved into the system. The average contract approval time fell from three to five business days to one or two. Labor spent on searching for documents, forwarding versions and tracking approvals dropped by about 40% (CNews). This is a supplier's data about its own implementation, but it uses the same units as the measurement above. How to calculate the cost of routine work and choose the first area is covered in the article “Automating routine work: where to start”.

Which parts of the described process will an off-the-shelf EDMS cover?

In short: an off-the-shelf system covers the standard steps — registration, a route with deadlines, delegation and the archive. Customization starts with branching conditions, reference data from accounting systems, complex access rights and the paper branch.

The route descriptions and the measurement give you a ready-made selection criterion: each element of the process either matches the product's logic or it doesn't.

The right-hand column is where the off-the-shelf system ends for a particular company. If your described process has one or two such items, a standard system with configuration will do the job faster and cheaper at the start. If more than half of the items fall there, customization on top of someone else's logic starts to cost about as much as a system built around your own procedures. And a year later, a product update may break some of that customization.

A product demo usually shows the standard scenario, so come to the meeting with the supplier with a description of your routes and ask about the right-hand column. How to connect an EDMS with your existing 1C and CRM into a single environment is covered in the article on system integrations.

What kinds of document management systems are there?

In short: solutions fall into classes by where they run and how far they can be adapted to your own process. None of them is universal.

The classes overlap: cloud services add internal routes, and off-the-shelf systems connect to EDI operators. That is why it is easier to choose a class using the table from the previous section: how many items of your process ended up in the right-hand column, and which systems the document exchanges data with.

How does an EDMS implementation work?

In short: from assessment to a pilot on one flow, and only then to the whole company. Launching every flow on the same day risks sending people back to email.

1. Assessment. A map of flows, routes, an owner and a measurement of timelines for high-volume document types. Add to that a list of the systems the document crosses paths with.
2. Choosing a class of solution. Cloud, off-the-shelf, a module in the accounting system, or custom; where the data is stored; which integrations are needed at launch and which can wait.
3. Pilot on one flow. Incoming correspondence or payment requests are the usual choice: they are high-volume and the effect shows quickly. The pilot tests routes, access rights, notifications and how signing works, and compares timelines with the pre-launch measurement.
4. Rollout and archive migration. The remaining flows are connected one at a time, and the archive is migrated with checks on scans and record cards. Each flow gets a date after which the old email route is closed.
5. Ongoing support. Adjusting routes based on feedback, new document types, updates, user support.

A project often breaks down when the second step is done first: the product has already been bought, but nobody has described the routes yet. The system then locks in the current workarounds, and redoing it costs more than the first launch. The other reasons an EDMS fails to take hold also have to do with what surrounds the product:

• The old route was left open. If an order can be sent both through the EDMS and by email, many will choose email.
• There's nothing to show the effect with. No measurement was taken before launch, and six months later the argument over whether things got better is settled by opinions.
• The archive stayed in folders. People still go to the shared drive for old documents, and new ones gradually drift back there too.

Staff resistance should be planned for in advance. In the same Moe Delo survey, at 30% of companies employees don't want to give up familiar processes. Evgenia Samarova, an expert at the service, attributes this to some employees still considering a handwritten signature more reliable than an electronic one (CNews, July 1, 2026). For an internal system the remedy is the same: a date for switching off the old route and an owner who holds to it.

How much does a document management system cost?

In short: a published price list shows the cost of the right to use the system, while the budget is driven by configuration, integrations and archive migration. Costs are worth calculating over the system's whole life, at least three to five years ahead.

Vendors publish license prices themselves, and two examples give a sense of the lower bound. Both were taken from vendor websites on September 29, 2026:

• ELMA365, Standard edition. This low-code platform also runs the vendor's document management solution, ELMA365 ECM. A named cloud license costs 10,000 rubles a year, or 17,000 rubles one-time on your own server, with a minimum purchase of 20 licenses (ELMA365 pricing). If 50 employees will work in the system, the cloud option will cost 500,000 rubles a year just for the right to use it.
• 1C:Document Management 8. The electronic delivery of the PROF edition costs 63,100 rubles, and the CORP edition 327,100 rubles. To work on several computers, 1C:Enterprise 8 licenses are purchased in addition (price on the 1C website).

Both figures cover only the right to use the system. Route configuration, integrations, archive migration and training are paid for separately: to the vendor's partner, to a contractor, or to your own IT department in staff time. The full budget breaks down like this:

The difference between companies of the same size comes from the number of flows, exceptions and integrations, so nobody can honestly name a budget without an assessment. The cloud has a lower entry cost, but the subscription is paid every year. With an off-the-shelf system, support and updates come on top of the license, and customizations pile up over time. A custom system costs more at the start, but it is built around your procedures and changes along with them. Many companies come to an EDMS from spreadsheets and shared folders; the signs that spreadsheets can no longer cope are collected in the article “When a business should move off Excel”.

Where should documents containing personal data be stored?

In short: databases containing personal data must be located in Russia, and the cloud supplier needs a data processing agreement that includes security measures. A letter stating where the servers are is not enough for that.

Document flow almost always contains full names, passport details, addresses and phone numbers: in contracts, HR orders and customer forms. Part 5 of Article 18 of 152-FZ, as amended by Law No. 23-FZ of February 28, 2025, has been in force since July 1, 2025. It prohibits recording, accumulating, storing and retrieving personal data of Russian citizens using databases located outside Russia. Exceptions are limited to clauses 2, 3, 4 and 8 of Part 1 of Article 6 of the same law (152-FZ, Article 18, ConsultantPlus).

The storage location is a mandatory condition, but not the only one. A cloud EDMS supplier usually processes personal data on the company's behalf. Part 3 of Article 6 of the same law allows such an assignment on the basis of a contract and lists what it must contain: the data involved, the actions performed on it, the purposes of processing and security requirements under Article 19 (152-FZ, Article 6, ConsultantPlus). Article 19 requires legal, organizational and technical measures against unauthorized access, alteration, copying and destruction of data (152-FZ, Article 19, ConsultantPlus).

Under Part 5 of Article 6, the company, as the data operator, is responsible to the person whose data is in the system, and the supplier is responsible to the company. The practical takeaway for choosing a system: know where the servers, the archive and the backups physically sit, and read the supplier contract for the processing assignment and security measures. How to build an environment from which documents and personal data don't leave is covered in the article “Neural networks without data leaks”.

What does it take for a document management system to work?

In short: routes, the owner, measurement, storage and signatures are covered above. Before the project starts, what remains is data, integrations, access rights and ongoing support.

1. Access to data. The counterparty list from 1C, the org structure and employees from HR records, deals from the CRM. Without data exchange, record cards are filled in by hand and drift out of sync with the books.
2. List of integrations. 1C, CRM, EDI operator, email, archive. Each link has its own job and its own owner; ways to connect systems are covered in the piece on system integration.
3. Access control. HR orders, contracts with amounts, and documents containing personal data are visible only to those whose role entitles them.
4. Ongoing support. Who inside the company adjusts routes and adds new document types, and who outside handles support and customization.

These are the items that most often end up in the right-hand column of the off-the-shelf table, and they are also what the budget is made of.

Off-the-shelf or a system built around your process?

In short: an off-the-shelf system covers standard document management, while exceptions and links to your accounting systems fall to customization or manual work.

Every company has its own procedures, reference data, access rights and approval order. In one, a secretary registers incoming letters; in another, the head of unit does it directly. In one, a request's route depends only on the amount; in another, also on the project and legal entity. An off-the-shelf system moves documents according to someone else's model, and the company makes up the difference by hand or pays for customization on top of someone else's architecture. The right-hand column of the table above shows how many such mismatches you have.

The second argument is connectedness. A document lives alongside a counterparty, an employee and an amount, and those live in 1C, the CRM and HR records. In our logistics case we started from the other end: requests, contract-requests, invoices and completion certificates for a trip are assembled from the dispatch system's own data. Documents for a trip used to take days to assemble; now they are ready on the day the trip is closed. We covered the choice between a ready-made solution and a system built around your process separately — custom system or off-the-shelf.

At INCUBE AI we build document management as custom development: approval routes built around your procedures, electronic signatures, statuses and a register, deadline reminders. Contracts, invoices and completion certificates are generated from system data using templates, and the system itself is connected to 1C, CRM, email and Telegram. We work under a contract, the data stays in Russia, and after launch we refine the system based on feedback and provide ongoing support. How it works is described on the “Document flow” page. If your routes are already described, or you're ready to describe them, tell us about your task: we'll run a measurement on your documents, identify the integrations and estimate the scope of work from them.

Sources and links

• ComNews, May 15, 2026: VK WorkSpace and Hi-Tech Mail survey on searching for information at work — 4,000 Russians; 42% sometimes spend more time looking for a file or message thread than working with it
• Lenta.ru, Alena Shevchenko, July 1, 2026: Weeek survey — 1,140 specialists at Russian companies: about an hour and fifty minutes a day on average searching for information, 17% spend four hours or more
• CNews, February 26, 2026: hh.ru survey — survey of May 5–12, 2025, 3,283 respondents: 38% spend more than six hours a week getting documents, requests and queries approved, 46% among HR staff
• “Only 10% of companies have fully switched to EDI”, CNews, July 1, 2026 — Moe Delo survey, June 2026, 2,200 respondents from small and medium-sized businesses: documents stalling without the manager, signatures tied to a token, shares of paper documents, staff resistance, comment by Evgenia Samarova
• CNews, August 24, 2026: Directum implementation at Right line — according to the vendor, contract approval time fell from three to five business days to one or two, and labor spent on searching for documents, forwarding versions and tracking approvals dropped by about 40%
• ELMA365 pricing, vendor website, viewed September 29, 2026 — Standard edition: named cloud license 10,000 rubles a year, 17,000 rubles one-time on your own server, minimum 20 licenses
• 1C:Document Management 8 price, 1C website, viewed September 29, 2026 — electronic delivery: PROF 63,100 rubles, CORP 327,100 rubles, additional 1C:Enterprise 8 licenses for several computers
• GOST R 7.0.8-2025 “Records management and archiving. Terms and definitions” — approved by Rosstandart Order No. 30-st of January 28, 2025, in force since March 1, 2025: definitions of document flow, electronic document management system and document registration
• Ministry of Finance of Russia Order No. 14n of February 5, 2021, ConsultantPlus — issuing and receiving VAT invoices electronically through EDI operators with a qualified signature
• 63-FZ “On Electronic Signature” of April 6, 2011, Article 17.2, ConsultantPlus — signing a document with a representative's qualified signature and the machine-readable power of attorney
• 152-FZ “On Personal Data” of July 27, 2006, Article 18, ConsultantPlus — Part 5 as amended by Law No. 23-FZ of February 28, 2025, in force since July 1, 2025
• 152-FZ “On Personal Data”, Article 6, ConsultantPlus — assigning personal data processing to another party (Part 3) and the operator's liability (Part 5)
• 152-FZ “On Personal Data”, Article 19, ConsultantPlus — measures to ensure the security of personal data during processing