Capitalizing Code: How IT Companies Can Secure Software Rights and Account for Intangible Assets under FSBU 14/2022
The value of an IT product lies not in servers, but in rights to code, architecture, and algorithms. Without legal confirmation of exclusive rights and proper accounting, software remains just lines in a repository—not a company asset. We explore how to move development into the balance sheet, mitigate risks with contractors, and apply the new FSBU 14/2022 standard correctly during investment audits.
Criteria for Recognizing Software as an Intangible Asset
In IT businesses, the core value resides in intellectual output. For code, databases, or architectural solutions to become full-fledged assets on the balance sheet, they must meet strict criteria. FSBU 14/2022 requires all of the following conditions to be met simultaneously. The object must lack physical form—legal control over rights matters more than the physical medium. The asset must be identifiable and separable from other company resources. The organization must demonstrate real control: the ability to restrict third-party access and monetize the product.
A key indicator is the ability to generate economic benefits through licensing fees or reduced operational costs. The cost of creation or acquisition must be reliably measurable, and the useful life must exceed twelve months or the operating cycle. These criteria cover exclusive rights to software, structured databases, interface solutions, technical specifications, and trade secrets. Trademarks and registered domains are also recognized as intangible assets. However, unregistered company names and internal logos are not accepted on the balance sheet.
Accounting Boundaries: What Cannot Be Capitalized
Not every digital asset or expense item becomes an asset. Incorrect capitalization distorts financial reporting and triggers scrutiny during tax audits or investment reviews. The standard clearly defines exclusions. Cloud subscriptions and rental-model services are treated as expenses: the company gains access to functionality but does not control the source code. Domain names themselves are not intellectual property; registration costs are either capitalized as website investments or recorded as current operating expenses. Marketing campaigns, advertising activities, and internally developed reputation do not create transferable assets and are expensed in the period incurred.
Special attention is given to stages of R&D. The research phase—when no prototype exists and commercial viability is unproven—is not eligible for capitalization. Costs related to searching for solutions, testing hypotheses, and analyzing technologies are considered current expenses. Capitalization begins only at the development stage, when technical feasibility has been proven. Physical media with pre-installed software are accounted for separately: if equipment cost is significant, it’s recorded as fixed assets, while software rights are treated as intangible assets. This approach must be documented in the accounting policy.
Legal Framework: Transferring Rights from Developers
Paying a developer does not automatically transfer exclusive rights to the client. Non-proprietary authorship rights are non-transferable and remain with the individual creator. Businesses must legally secure exclusive rights to use, modify, and sell the product. For in-house employees, the framework of work-made-for-hire applies. By default, rights belong to the employer—but this only holds if there is a documented technical specification, acceptance acts, and actual implementation within three years. Additional compensation beyond base salary is also mandatory for proper documentation. Missing any part of this chain nullifies the possibility of recognizing the asset.
Working with external contractors and freelancers increases risk significantly. Exclusive rights pass to the client only if the contract explicitly includes full assignment. Phrases like "performing work to develop code" or "providing a license" are insufficient for capitalization. In practice, investors frequently freeze deals due to broken chains of rights succession. If the contractor hasn’t formally transferred rights, they retain the right to block commercial use or grant similar solutions to competitors. Closing legal gaps during due diligence often requires buying back rights at market value—substantially increasing project costs.
Transition to FSBU 14/2022: Key Changes for IT
The new standard significantly modernizes the approach to intellectual property accounting, shifting focus from formal protective documents to economic substance and control. Companies can now set their own threshold for recognizing intangible assets in the accounting policy. Assets below the threshold are expensed but must still be tracked on off-balance sheet accounts to maintain control. Useful life is now a mandatory parameter. If it cannot be determined, the asset is not amortized but tested annually for impairment. The standard allows subsequent revaluation based on fair value, enabling recognition of market value for mature IT products.
Control over an asset no longer requires a patent or certificate. A commercially confidential regime, restricted repository access, and internal policies are sufficient. The concept of liquidation value—what the company expects to receive upon disposal—is introduced. For most software products, this is set to zero, adjusting the amortization base. Low-value assets are no longer invisible to accountants: off-balance sheet tracking ensures audit transparency.
Mechanics of Balance Sheet Placement and Amortization
After legal rights are secured, the product moves into the financial domain. Initial cost includes all documented expenses up to the point of readiness for use. This includes payments to contractors, government fees, payroll for in-house developers including insurance contributions, and costs for code review and testing. Administrative expenses, marketing, and post-launch support are excluded from capitalization and charged to financial results of the period.
The accumulated cost is compared against the established threshold. To align book and tax accounting, setting the threshold at 100,000 rubles is advisable—it matches Tax Code norms and minimizes temporary differences. Next, useful life is determined. It’s calculated based on expected revenue generation period, license or patent duration, and the technology lifecycle of the stack. Amortization is applied using the straight-line method or reducing balance method, starting from the month of asset recognition. The chosen method must be economically justified and documented in the accounting policy. Correct capitalization not only cleans up the balance sheet but also boosts investment appeal by showcasing the true value of the company’s intellectual capital.
Key Takeaways
- Exclusive rights to code do not transfer automatically upon payment; explicit assignment clauses in contracts with contractors are required.
- Work-made-for-hire requires documented technical specs, acceptance acts, additional compensation, and actual use within three years.
- FSBU 14/2022 allows companies to set their own cost threshold and recognize control without patents via a commercial secrecy regime.
- The research phase of R&D and cloud subscriptions are not capitalized and are treated as current expenses.
- Aligning the accounting threshold with the tax threshold of 100,000 rubles eliminates discrepancies and simplifies closing of reporting periods.
— Editorial Team
No comments yet.