Ukrainian IT companies operating under national accounting standards - known as P(S)BO (Polozhennya (Standarty) Bukhhalterskoho Obliku) - often discover significant gaps when they begin preparing financial statements under International Financial Reporting Standards. These gaps are not merely cosmetic. They reflect fundamentally different philosophies about what financial statements should communicate and to whom.

With Ukraine's IT sector generating $6.66 billion in exports in 2025 and M&A activity reaching $496 million across 41 deals in 2024, understanding these differences is not an academic exercise. It is a practical necessity for any technology company with international ambitions.

Philosophical foundations

The most important difference between P(S)BO and IFRS is not any single accounting rule - it is the underlying philosophy. P(S)BO is fundamentally tax-driven. Its primary purpose is to calculate taxable income and ensure compliance with Ukrainian tax legislation. Financial statements prepared under P(S)BO are designed to satisfy the State Tax Service, not to inform investors or lenders about the economic reality of the business.

IFRS, by contrast, is investor-driven. The conceptual framework explicitly states that general-purpose financial statements are prepared for existing and potential investors, lenders, and other creditors. The overriding objective is to present a "true and fair view" of the entity's financial position and performance. When tax rules and economic reality diverge, IFRS follows economic substance over legal form.

This philosophical difference cascades through every area of accounting. In P(S)BO, the question is often "What does the Tax Code require?" Under IFRS, the question is "What best reflects the economic reality of this transaction?"

Revenue recognition

Revenue recognition is arguably the area where the differences matter most for IT companies. Under P(S)BO 15, revenue is recognized when the risks and rewards of ownership are transferred to the buyer. For service contracts, revenue is recognized based on the degree of completion. The rules are relatively straightforward and leave significant room for management discretion.

IFRS 15 replaces this with a rigorous five-step model:

  1. Identify the contract. Determine whether a legally enforceable agreement exists with commercial substance.
  2. Identify performance obligations. Break the contract into distinct goods or services promised to the customer.
  3. Determine the transaction price. Calculate the total consideration expected, including variable components like bonuses or penalties.
  4. Allocate the transaction price. Distribute the total price across each performance obligation based on standalone selling prices.
  5. Recognize revenue. Record revenue as each performance obligation is satisfied, either at a point in time or over time.

For a software company that sells a bundled package of software licenses, implementation services, and three years of support, P(S)BO might allow recognizing the entire license fee upfront. Under IFRS 15, the company must identify each distinct performance obligation, determine standalone selling prices, allocate the transaction price accordingly, and recognize revenue as each obligation is fulfilled. The timing and amount of recognized revenue can differ substantially.

Consider a Ukrainian outsourcing firm with a $2 million fixed-price project spanning 18 months. Under P(S)BO, the company might recognize revenue based on a simple percentage-of-completion calculation using costs incurred. Under IFRS 15, the company must first determine whether it satisfies the performance obligation over time (which requires meeting specific criteria), then select an appropriate method for measuring progress that faithfully depicts the transfer of value to the customer.

Intangible assets and development costs

IT companies invest heavily in research and development. The treatment of these costs differs significantly between the two frameworks.

P(S)BO 8 permits capitalization of intangible assets at cost but provides limited guidance on distinguishing research from development activities. In practice, many Ukrainian IT companies expense all R&D costs as incurred, partly because the tax benefit of immediate expensing is more attractive than capitalization.

IAS 38 draws a sharp line between research and development. Research costs must always be expensed. Development costs must be capitalized if - and only if - the entity can demonstrate all six criteria simultaneously:

  • Technical feasibility of completing the asset
  • Intention to complete and use or sell it
  • Ability to use or sell the asset
  • How it will generate probable future economic benefits
  • Availability of adequate resources to complete development
  • Ability to reliably measure the expenditure

For a software company developing a new SaaS platform, this means tracking project costs by phase and capitalizing only those costs incurred after all six criteria are met. The capitalized asset is then amortized over its useful life and tested for impairment annually. This creates a more accurate picture of the company's investment in its technology but requires significantly more detailed record-keeping than P(S)BO demands.

Asset valuation: historical cost vs fair value

P(S)BO generally relies on historical cost accounting. Assets are recorded at their original purchase price and depreciated over time. Revaluation is permitted but rarely practiced outside of real estate. This approach is simple and verifiable but can result in balance sheets that bear little resemblance to economic reality.

IFRS offers a choice between historical cost and fair value measurement for many categories of assets. More importantly, certain items must be measured at fair value. Financial instruments under IFRS 9, investment property under IAS 40, and biological assets under IAS 41 all require fair value measurement. For IT companies, the most significant impact typically comes from financial instruments (including foreign currency derivatives) and the fair value measurement requirements for business combinations under IFRS 3.

When an IT company acquires another business - common in a market that saw $496 million in tech M&A in 2024 - IFRS 3 requires identifying and measuring at fair value all identifiable assets and liabilities, including intangible assets that may never have appeared on the target's P(S)BO balance sheet: customer relationships, proprietary technology, brand names, and non-compete agreements. Any excess of the purchase price over the net fair value of identifiable assets is recorded as goodwill, which is then tested for impairment annually rather than being amortized.

Provisions and contingent liabilities

P(S)BO 11 addresses provisions in general terms, requiring entities to recognize provisions for obligations when the amount can be reliably estimated. However, the guidance on measurement is limited, and discount rates are not typically applied to long-term provisions.

IAS 37 provides much more detailed guidance. Provisions must be recognized when there is a present obligation arising from a past event, it is probable that an outflow of resources will be required, and a reliable estimate can be made. Crucially, long-term provisions must be discounted to present value. For IT companies, this affects warranty provisions, onerous contract provisions (when contract costs exceed expected benefits), and restructuring provisions.

IAS 37 also requires disclosure of contingent liabilities - possible obligations that depend on uncertain future events. For an IT company involved in intellectual property disputes or regulatory proceedings, these disclosure requirements can reveal risk exposures that P(S)BO financial statements would not capture.

Practical implications for IT companies

The cumulative effect of these differences means that a Ukrainian IT company's financial performance can look materially different under P(S)BO versus IFRS. Revenue timing changes, asset values shift, new assets and liabilities appear on the balance sheet, and the notes to the financial statements expand significantly.

For a company with $10 million in annual revenue, the differences in net income between P(S)BO and IFRS can range from 5% to 25%, depending on the nature of its contracts, the extent of its R&D activities, and the complexity of its employee compensation arrangements. These are not rounding differences - they are material variances that affect valuations, debt covenants, and management decisions.

Understanding these differences is the essential first step in any IFRS transformation project. A thorough gap analysis, mapping every significant P(S)BO accounting policy to its IFRS equivalent, provides the roadmap for the work ahead. Without this foundation, transformation efforts risk being incomplete, inconsistent, or - worst of all - requiring costly rework when the auditors arrive.