Electronic Document Management — A Tool for Savings

In practical activity, it is important to clearly separate direct cash savings, expanding employees' time capacity, and reducing the risks of violating record-keeping requirements. Automatically applying computer systems on top of outdated or contradictory regulations only leads to duplicating procedures in two formats. Proper process organization requires a preliminary study of document delay points and agreeing on new routing rules before technical tools are deployed.

Three distinct types of economic effect

When analyzing the financial consequences of implementing specialized software, expected changes should be classified into three separate categories:

• Direct cash savings: reduction in purchases of office paper, cartridges, toner, folders, as well as a decrease in actual expenses for postal shipments and courier services due to eliminating repeated courier dispatches.
• Freed staff time: saving staff minutes during registration, approval, and file searches, which creates an additional time reserve for performing primary functional duties, but does not mean an automatic reduction in the payroll fund.
• Reduction of operational risks: lowering the likelihood of losing important papers, losing the current version of a contract, or missing task deadlines, the consequences of which must be evaluated based on your own data.

The expected reduction in errors should be shown separately from confirmed monetary savings. Evaluating potential losses requires internal data on the frequency and consequences of errors. The viability of a project is evaluated over a selected period by comparing implementation and support costs with expenses that can truly be avoided.

What to measure before implementation

To form an objective benchmark prior to starting a project, baseline metrics should be recorded for the selected business process over one calendar month. Subject to measurement are the total number of processed documents, number of sheets, duplicate volumes, number of routing stages, active staff working duration, and the time a document waits in queue. Additionally, the number of returns for rework and actual expenses from paper and postal service supplier invoices are recorded.

Before automation, the process owner reviews the approval route: which checks are necessary, and where employees duplicate work. Only those stages are changed for which it is permissible given the law and internal rules. Network folders may have access restrictions, but by themselves do not provide an agreed route, deadlines, or a unified execution history. It is these functions that should be checked in the selected system.

Hypothetical calculation of time savings

Let us consider an exclusively illustrative calculation that is not a description of a specific implemented IQusion project, but clearly demonstrates the mechanics of resource release. Suppose an organization processes 500 incoming or internal documents monthly. If the average duration of active staff work with one document (including search, checking details, and transfer) before system implementation was 10 minutes, and after optimization and automation is 6 minutes, the difference is 4 minutes per document.

Calculation: 500 × (10 − 6) = 2000 minutes, or 33 hours 20 minutes per month. This is a possible reserve of working time, provided that the pilot confirms the initial assumptions. It is not equal to reducing the total approval time: waiting time between stages is measured separately. To count these hours toward monetary savings, one must show which real expenses were avoided, such as paid overtime work.

Full budget for implementation and support

Forming an automation budget requires taking into account not only the cost of purchasing basic software licenses, but also all associated one-time and recurring costs. The full initial budget includes process configuration, integration with the existing accounting system, local server databases, hardware for backup storage, data migration, procurement of scanners, and initial staff training.

Recurring expenses include administration, support, backups, updates, and, if necessary, maintenance of electronic digital signature (EDS) certificates. For the transition period, parallel paper operations are factored in. An existing server can be used after checking its resources, compatibility, and reliability; its operation also has a cost. For comparison, the period and start date of the calculation are agreed upon, accounting for one-time investments and regular payments. The payback period will depend on actual conditions, not on a vendor's universal promise.

Legal terms and document retention

The legal validity of electronic documents is regulated by Laws No. 851-IV and the Law of Ukraine "On Electronic Digital Signature" No. 852-IV. An electronic document is an original only if all required details and an applied electronic digital signature (EDS) are present. Before starting exchange with counterparties, it is necessary to verify their authority, technical compatibility of formats, and confirm sending and receiving procedures. A scanned paper copy in the system remains merely a working copy and does not acquire the status of a legal original.

According to the norms of Order of the Main Archival Administration No. 41 dated July 20, 1998, established retention periods for paper primary documents are mandatory to follow. Software implementation does not grant the right to immediately dispose of the paper archive. For state-owned enterprises, additional strict office work instructions apply, so the ability to abandon paper for a specific type of contract requires detailed legal review. Data protection and information recovery procedures are developed taking into account voluntary international methodological recommendations, such as NIST SP 800-34 (2002), without giving them the status of mandatory state standards of Ukraine.

How to evaluate pilot results

It is advisable to conduct a pilot on one process, such as approving a procurement request or preparing a response to an incoming letter. Before starting, record document volume, operation duration, desired results, budget, and observation period. The regulations define actions in case of approval delays, absent assignees, and system failures. Restoration from a backup and temporary manual record-keeping procedures are tested separately.

To verify pilot project efficiency, it is recommended to follow this sequence of actions:

1. Compare actual cash payments for physical media before and after the test period for an equivalent document volume.
2. Evaluate changes in staff time capacity and the quality of compliance with established processing deadlines without compromising the completeness of control.
3. Make decisions on expanding the system to other departments only after confirming its value in practice.

A properly planned electronic document management implementation allows a manager to transparently see process bottlenecks, the financial department to control the forecast budget, and employees to spend less time searching for papers and respond faster to client requests.

Questions and answers

Does EDMS implementation mean an immediate rejection of paper?

No. The possibility of an electronic original depends on the document type and proper execution. Existing paper originals are retained according to established rules; scanning does not cancel retention periods.

How do you calculate time savings from routing automation?

Active staff work time per document is measured in advance before and after changing the process. The difference multiplied by volume gives a potential time reserve, which does not equal direct money.

What costs should be included in the full implementation budget?

Besides base licenses, the budget includes configuration, integration with accounting systems, servers, scanner procurement, EDS, staff training, and transition period support.

Sources

• Law No. 851-IV "On Electronic Documents and Electronic Document Flow", revision of 24.06.2005
• Law No. 852-IV "On Electronic Digital Signature", original 2003 edition
• List of typical documents under Order No. 41 dated 20.07.1998, revision of 26.04.2008
• NIST SP 800-34, Contingency Planning Guide for Information Technology Systems, 2002