Ukraine’s sleek digital front end still has a legacy back-office problem

Modern technology has a visual language: clean interfaces, instant services, cloud dashboards and products that feel as though they were built yesterday. Legacy technology has almost no visual language at all. It sits in accounting departments, payroll offices and databases that users never see. Ukraine’s 1C/BAS story is a reminder that the less visible layer can be the harder one to modernize.

The evidence is in job advertisements. Military Unit A5118 sought an accountant in March and listed 1C, 1C Accounting and BAS among required or desired skills. Military Unit A4640 looked for a leader in accounting and reporting with experience in the same software family. A Kyiv regional territorial recruitment and social support center also treated familiarity with 1C-style accounting systems as an advantage.

These are not glamorous technology roles. That is exactly why they matter. Accounting keeps institutions functioning: salaries are paid, assets are recorded, suppliers are reconciled and reports are filed. A country can field advanced drones and sophisticated digital services while still carrying old financial software because those systems are deeply woven into routine work.

Diia makes the contrast especially sharp. The Ukrainian app has become a symbol of digital government, yet a June vacancy in its finance and economics team expected candidates to be highly proficient in 1C, BAS or similar programs. It is tempting to turn that into a gotcha. The more accurate conclusion is more interesting.

The job was not for a mobile engineer. It concerned financial calculations. Diia separately hires DevOps engineers, system analysts, mobile specialists and security staff for the architecture citizens actually use. A modern digital product and a legacy financial back office can exist inside the same organization without being the same technology stack.

That distinction is important for leadership. Replacing a public interface is often a product project: define a user problem, build, test and release. Replacing an ERP is closer to changing the institution’s operating memory. It contains years of transactions, reporting rules, payroll logic, suppliers, permissions and integrations. The old system cannot simply disappear on launch day because the new one must first reproduce the numbers correctly.

Ukraine’s legal context now forces the transition. SSSCIP, the national authority responsible for special communications and information protection, explicitly discusses 1C and BAS in its prohibited-software guidance. It links their inclusion to the sanctioned rights holder, 1C LLC. The agency is careful to say that the list is sanctions-driven and is not a technical ranking that declares every version of every listed product vulnerable.

For sensitive government environments, however, the rule is operationally strict. Listed software cannot be used in covered systems processing state information resources, official data, state secrets or critical information infrastructure. Keeping a system offline does not create an exemption. Prohibited components can compromise the system’s ability to obtain or retain security authorization.

On July 17, the prohibited list grew from 1,079 to 1,341 entries. That scale changes the leadership challenge. It is no longer enough for a chief executive or public official to know a few politically sensitive brand names. Organizations need inventories, owners, compliance processes and a reliable route for replacing software when legal status changes.

There is also a market response. IT Ukraine and Germany’s GIZ announced a further voucher round on July 28 to help Ukrainian micro and small businesses replace 1C/BAS with modern ERP systems. The policy acknowledges a practical truth: migration costs money, and small organizations may need external support to move at the speed national security policy demands.

One claim in the original material does not meet the same evidentiary standard. It named Fire Point, a prominent Ukrainian defense-tech producer, as a user of 1C/BAS. MAIR reviewed Fire Point’s public DOU profile and indexed vacancies but found no independent company-specific evidence for that assertion. The claim therefore remains unverified.

The leadership lesson is broader than Ukraine. Innovation should not be measured only by the technology customers can touch. A resilient organization modernizes the invisible layer as deliberately as the visible one. Payroll, accounting and procurement may never make a glossy demo, but in wartime they can become part of national technology sovereignty.