Intangible Assets Accounting IFRS: IAS 38 for Students

What is intangible assets accounting IFRS under IAS 38?

Intangible assets accounting IFRS can feel strange at first because the asset is valuable but invisible. IAS 38 starts with a narrow definition: an [intangible asset](/glossary#intangible-asset) is identifiable, non-monetary, and has no physical substance. In plain language, the company must be able to point to a controlled right or separable resource, not just a good reputation or a skilled team.

For Saudi and Gulf students, this matters because SOCPA-endorsed [IFRS](/glossary#ifrs) is the reporting language for many entities, and IAS 38 is often tested through short scenarios. A purchased software licence, a trademark bought from another company, a patent, or a franchise right may qualify. Staff training, internally generated customer loyalty, and most advertising campaigns usually do not.

The easiest mental test is this: can the company control the expected benefits, restrict others from using them, and measure the cost reliably? If yes, continue to recognition. If no, expense the spending unless another standard applies. This is why IAS 38 is stricter than everyday business language. Management may say a brand is an asset, but accounting only recognizes it when the standard's criteria are met.

A useful comparison is [PPE capitalization under IAS 16](/learn/ppe-capitalization-ias-16). Both standards ask whether future benefits are probable and costs are reliable, but IAS 38 adds pressure around identifiability and control because there is no physical item to inspect.

How does intangible assets accounting IFRS decide what to capitalize?

IAS 38 separates three questions: does the item meet the definition, does it pass the recognition criteria, and how was it obtained? Purchased intangible assets are usually the cleanest. The cost includes the purchase price and directly attributable costs needed to prepare the asset for use. That may include non-refundable taxes, legal registration fees, or implementation work that brings software to the condition intended by management.

Internally generated assets are harder. Research spending is expensed as incurred because the project is still exploratory. Development spending is capitalized only after the entity can demonstrate all the required conditions: technical feasibility, intention to complete, ability to use or sell, probable future economic benefits, enough resources to finish, and reliable measurement of attributable expenditure.

The timing point is where many students lose marks. If Al-Nakhil Apps spent SAR 90,000 exploring an idea in January and February, then met the development criteria on March 1, the January-February spending remains an expense. IAS 38 does not allow a company to bring back past expenses into the asset later.

For a quick decision table, use this structure:

How do you record a purchased intangible asset?

Start with the acquisition date and build the cost carefully. Suppose Riyadh Cloud Services buys a three-year logistics-routing software licence for SAR 240,000. It also pays SAR 30,000 to configure the software so it can run with the company's warehouse system. Both amounts are necessary to prepare the asset for use, so the initial cost is SAR 270,000.

The [journal entry](/glossary#journal-entry) is straightforward:

The entry increases non-current assets and decreases cash or increases liabilities. It does not hit profit or loss on day one because the company has acquired a resource that will benefit future periods. The expense pattern comes later through amortization if the asset has a finite useful life.

What should not be included? Training staff to use the software is normally expensed because it develops people, not the controlled software asset. General administration, wasted implementation effort, and launch marketing are also expensed. This separation is not just technical. It keeps the asset balance from becoming a storage place for every cost connected to a project.

In practice, the invoice coding should match the company's [chart of accounts design](/learn/chart-of-accounts-design). A separate software intangible asset account and accumulated amortization account make later review much easier.

Worked example 1: software licence and annual amortization

Riyadh Cloud Services can use the software for exactly three years under the licence agreement. There is no residual value. Because the useful life is finite, IAS 38 requires the asset to be amortized over the period the benefits are consumed. If the benefits are even, straight-line amortization is usually acceptable.

Cost is SAR 270,000. Useful life is three years. Annual [amortization](/glossary#amortization) is SAR 90,000.

At year-end, the entry is:

After one year, the carrying amount is SAR 180,000. After two years, it is SAR 90,000. After three years, it is zero unless the licence is renewed or replaced by a new asset that meets recognition criteria.

Notice the difference from cash. The cash went out when the software was bought, but expense recognition follows the benefit period. This is the [matching principle](/glossary#matching-principle) in action: the cost is recognized while the software supports revenue, not all at the purchase date.

If usage is heavier in year one than later years, straight-line may not be best. IAS 38 says the amortization method should reflect the pattern of expected benefits. The company should review the useful life and method at least at each financial year-end, especially when the software becomes obsolete faster than expected.

Worked example 2: internal development costs under IAS 38

Jeddah EduTech is building an exam-preparation platform. During the research phase, it spends SAR 120,000 comparing product ideas and testing whether students would pay for the service. That amount is expensed. On April 1, management approves a detailed design, technical feasibility is documented, funding is committed, and future subscription benefits are supported by signed pilot contracts. From that date, the team spends SAR 360,000 on directly attributable development work.

The correct treatment is not to capitalize all SAR 480,000. The SAR 120,000 research cost stays in profit or loss. Only SAR 360,000 after the development criteria are met is capitalized.

If the platform is ready for use on October 1 and has a four-year useful life, amortization begins when it is available for use, not when the first customer invoice is sent. That is a common exam trap.

Also remember the impairment angle. If the launch performs badly and expected cash flows fall, the company may need an [IAS 36 impairment review](/learn/impairment-of-assets-ias-36). Capitalization is not a permanent shield; the carrying amount must remain recoverable.

What happens after recognition: cost model, revaluation, impairment?

After recognition, IAS 38 allows either the cost model or the revaluation model. In student scenarios, the cost model is usually the practical answer: cost less accumulated amortization and accumulated impairment losses. The revaluation model is permitted only when fair value can be measured by reference to an active market, which is rare for patents, trademarks, software, and brand rights because each asset is often unique.

Useful life drives the next step. A finite-life asset is amortized. An indefinite-life asset is not amortized, but it must be tested for impairment annually and whenever there is an impairment indicator. Indefinite does not mean infinite; it means there is no foreseeable limit to the period of cash inflows based on current evidence.

A simple checklist helps:

• Is the useful life finite? Amortize over that life.
• Is the useful life indefinite? Do not amortize, but test for impairment annually.
• Has the market, technology, regulation, or customer behavior changed? Reassess useful life and impairment.
• Is there an active market for the class of asset? Only then consider revaluation.

For a Saudi software company, technology obsolescence is often the key risk. A platform may legally last five years, but if a new ZATCA integration or payment standard makes it obsolete after three years, the accounting estimate should change. IAS 38 is not a set-and-forget standard; it requires active review.

Common mistakes in intangible assets accounting IFRS

Most mistakes come from treating business value and accounting value as the same thing. They are not. IAS 38 recognizes only assets that pass its definition and recognition tests.

Common mistakes include:

• Capitalizing research costs because the project later succeeds.
• Capitalizing training, advertising, or staff knowledge as if the company controls people.
• Treating internally generated brands or customer lists as recognized assets.
• Forgetting to start amortization when the asset is available for use.
• Using depreciation language for intangible assets instead of amortization.
• Ignoring impairment indicators after a product launch underperforms.
• Posting every technology invoice to one account without enough detail in the [general ledger](/glossary#general-ledger).

The clean approach is to document the recognition date, the evidence supporting development criteria, the useful life, the amortization method, and the accounts used. This documentation protects the entry when an instructor, auditor, or manager asks why one cost was capitalized while another was expensed.

For exams, write your answer in decision order: definition, recognition, measurement, journal entry, subsequent treatment. For work, use the same order in the accounting memo. A balanced entry is not enough if the classification is wrong. IAS 38 is mainly about classification discipline before the debit and credit are even posted.

How should students practice IAS 38 entries?

The best practice routine is to turn every scenario into a short decision memo before writing numbers. First, identify the asset or spending item. Second, decide whether it is purchased, internally generated research, or internally generated development. Third, choose expense or capitalization. Fourth, calculate amortization or impairment if the asset remains on the books.

Try this mini-case. Dammam HealthTech pays SAR 80,000 for a patent, SAR 12,000 in legal registration fees, and SAR 20,000 training sales staff to explain the product. The patent and legal registration fee are capitalized at SAR 92,000. Training is expensed. If the patent's useful life is eight years with no residual value, annual amortization is SAR 11,500.

That one scenario tests recognition, cost measurement, and subsequent expense. It also shows why intangible asset accounting is not memorization. You need to read the facts carefully and defend each classification.

On Accountery, this topic works well as a mixed exercise: one tab for classification, one tab for entries, and one tab for a year-end review. Practice with software licences, development projects, franchise rights, and patents. Then compare your entries with explanations so you can see whether the issue was the standard, the calculation, or the debit-credit mechanics. That feedback loop is how IAS 38 becomes practical instead of abstract.