IAS 38 Development Costs: When Capitalization Starts

Build a dated evidence file, separate eligible spending, and reconcile two development projects from invoice to year-end.

What makes IAS 38 development costs a timing problem?

IAS 38 development costs become easier to handle when you draw a dated project timeline before calculating the asset. A successful product can contain research spending, early development spending that failed the recognition tests, qualifying development expenditure, and later operating expenses. These amounts can sit in the same project budget while receiving different accounting treatment.

This guide focuses on internally developed assets within IAS 38. It assumes the company controls an identifiable resource and applies full IFRS Accounting Standards. Purchased assets and acquisitions of businesses need their own analysis. For the broader background, start with our [intangible-assets guide](/learn/intangible-assets-ias-38). Both company cases below are fictional Saudi businesses, and every amount is in SAR. They exclude tax, financing costs and impairment losses unless stated otherwise.

The [IFRS Foundation’s IAS 38 overview](https://www.ifrs.org/issued-standards/list-of-standards/ias-38-intangible-assets/) distinguishes research expenditure, which is expensed, from development expenditure meeting the recognition criteria. The practical question is when the evidence first supports recognition of the particular [intangible asset](/glossary#intangible-asset).

Keep three dates visible: when the project begins, when all recognition requirements are demonstrably met, and when the asset becomes available for use. A board presentation, a supplier payment and a public launch can happen on different dates. None should automatically replace the accounting assessment. Your working paper should explain what changed at each date, who supplied the evidence, and which expenditure belongs on each side of the cutoff.

What evidence supports IAS 38 development costs capitalization?

Paragraph 57 requires all six development conditions to be demonstrated. Translate those conditions into questions that the project owner can answer with records. Can the asset be completed technically? Does management intend to complete it? Can the entity use or sell it? Are future economic benefits probable? Are sufficient resources available? Can attributable expenditure be measured reliably? The [equivalent standard text published by XRB](https://standards.xrb.govt.nz/standards-navigator/nz-ias-38/) sets out these conditions in paragraphs 57–62.

For a small software team, useful evidence might include successful technical testing, a documented completion plan, legal rights over the code, a supported internal-use case, committed funding and time records. These are examples of evidence, rather than a mandatory document list. One signed form cannot substitute for facts that remain unresolved.

Imagine that engineers resolve the main technical uncertainty in May, but the company cannot demonstrate resources to finish until July. If the other requirements are satisfied by July, the evidence supports July as the starting point. Technical progress in May does not bring all conditions forward to May.

Make a six-row assessment with a separate evidence reference and date for each condition. Then record the earliest date at which the whole assessment passes. A reviewer should be able to trace that conclusion without interviewing everyone again. When evidence is missing, identify the missing fact explicitly. A hopeful sales forecast and an approved budget serve different purposes, and neither establishes technical feasibility on its own.

How do you build the cost cutoff worksheet?

Use one row per invoice, payroll allocation or service period. Suggested columns are project, activity, service date, amount, evidence reference, eligibility and posting account. Add a reason for every excluded item so that the same question does not return at the next close. For invoices spanning the recognition date, seek a supported split of the underlying work; the payment date alone does not describe when the work occurred.

IAS 38 paragraphs 65–67 tie asset cost to eligible expenditure from the recognition date and directly attributable preparation activities. Training and identified inefficiencies are excluded. Paragraph 71 prevents later success from reinstating amounts previously recognized as expenses. These requirements are available in the [AASB compilation incorporating IAS 38](https://standards.aasb.gov.au/aasb-138-dec-2022-0), applicable there to annual periods beginning from July 2026 and before January 2027. Its Australian-specific provisions do not establish Saudi requirements.

A practical worksheet separates four buckets: pre-recognition spending, qualifying development costs, excluded costs during development, and costs after availability for use. The last bucket still needs assessment of the actual activity; routine support should not be confused with a separately qualifying enhancement.

Reconcile the four buckets to the total project ledger. This catches omissions as well as excessive capitalization. If a developer worked on two projects, retain the time allocation that explains the split. Avoid applying a convenient percentage to every salary simply because the business calls itself a technology company. Your allocation should follow the work performed and the asset being prepared.

Worked example 1: Riyadh Route Systems reaches the recognition date

Riyadh Route Systems develops routing software for its own operations. It controls the resulting code and can restrict others’ access. The project begins in January. All recognition requirements are first met on 1 July, supported by technical testing, committed resources, a documented internal-use benefit and reliable cost records. The software is available for its intended use on 1 November. Assume a four-year useful life, zero residual value and straight-line amortization reflecting consumption.

The asset costs 200,000: developer payroll of 160,000 plus testing of 40,000. Other project expenditure is 180,000. All spending is paid in cash in this simplified example. The following summarized [journal entry](/glossary#journal-entry) groups transactions that would normally be posted as incurred:

Notice that the April–June work remains an expense even though it helped produce the finished software. The evidence did not support recognition during those months. The company’s later success does not change that history. Also, training is excluded despite occurring around implementation. A date test and a cost-nature test must both be passed; being inside the development period satisfies only the first.

Worked example 2: Jeddah Process Design separates mixed spending

Jeddah Process Design develops a controlled manufacturing process. All recognition requirements are first met on 1 September. Before that date it incurs 140,000 of research and development expenditure. From September through December it incurs qualifying engineering payroll of 120,000 and necessary prototype testing services of 30,000. Identified wasted work costs 15,000, while general head-office administration unrelated to preparing the process costs 25,000. The process remains unavailable for use on 31 December.

Total spending is 330,000. Of that, 150,000 qualifies as development asset cost and 180,000 is expensed. Assume the company pays 300,000 and still owes 30,000 to the testing supplier. There is no impairment loss under the stated assumptions; in practice the required impairment assessment must still be performed.

The unpaid testing invoice belongs in the asset because the qualifying service has been received. Cash settlement does not decide eligibility. Conversely, paid head-office spending remains an expense because it does not prepare this asset for use.

For a separate practice variation, assume 10,000 of the existing 25,000 administrative cost was demonstrably and directly attributable to preparing the asset, with all other facts unchanged. Transfer that amount from the expense bucket to the asset bucket: asset cost becomes 160,000 and expenses become 170,000. Total expenditure remains 330,000. This variation changes the underlying evidence, rather than granting permission to capitalize all administration.

When do amortization and impairment enter the schedule?

The availability-for-use date controls the start of [amortization](/glossary#amortization) for a finite-life asset. IAS 38 paragraph 97 links that date to the asset’s condition for its intended operation. A delayed marketing event does not, by itself, defer the accounting start. The recognition date and availability date therefore belong in separate fields in your register.

For Riyadh Route Systems, annual amortization is 200,000 divided by four years, or 50,000. Using the stated monthly convention, November and December create an expense of 50,000 × 2 ÷ 12 = 8,333.33. Debit amortization expense and credit accumulated amortization for that amount. The 31 December carrying amount is 191,666.67, before any impairment. Total project-related expense for the year is 188,333.33: the earlier 180,000 plus amortization.

For Jeddah Process Design, no amortization starts by year-end because the process is not yet available for use. Its 150,000 carrying amount remains subject to the impairment requirements. IAS 36 requires annual impairment testing for an intangible asset not yet available for use, in addition to testing when impairment indications arise. The [IFRS Foundation’s IAS 36 overview](https://www.ifrs.org/issued-standards/list-of-standards/ias-36-impairment-of-assets/) explains this annual testing requirement; our [impairment guide](/learn/impairment-of-assets-ias-36) develops the calculation.

Keep impairment evidence alongside the development schedule. A forecast used to support the original project decision can become outdated. Review changed costs, delays and demand assumptions, and document how they affect the recoverable amount. A balance that has not yet started amortizing still needs review.

Which common mistakes change the asset and profit?

The most useful review asks which fact would have to be true for a posting to be correct. That makes errors visible before you focus on account codes.

  • Using the project approval date automatically. Check whether every recognition condition was demonstrable then. Approval documents can support the assessment but cannot decide it alone.
  • Capitalizing the whole year after a successful launch. Keep costs incurred before the qualifying date outside the asset. Preserve the original expense history.
  • Treating capitalization as a profit target. Start with evidence and eligible costs. The desired margin has no place in the worksheet.
  • Capitalizing all costs after the cutoff. Review training, promotion, waste and unrelated administration individually. A development project code does not make every invoice eligible.
  • Waiting for payment before recording a qualifying service. Recognize the received service and its payable under the stated accrual facts, then record settlement separately.
  • Starting amortization on the first sale. Establish when the asset was ready for its intended use. That can precede revenue.

Apply a numerical reasonableness check to the Riyadh case. If the company incorrectly capitalized all 380,000 and amortized that amount over four years for two months, it would record amortization of 15,833.33 and a closing asset of 364,166.67. Compared with the correct asset of 191,666.67, assets and pre-tax profit would each be overstated by 172,500. The total cash paid would still be correct. That is why a balanced entry and a reconciled bank payment cannot establish correct expense recognition.

Finally, keep the case assumptions visible when discussing results with a colleague. A different useful life, readiness date or impairment outcome changes the schedule and should be recalculated explicitly.

How can you practise the recognition-date decision?

Start with a blank timeline and cover the answers in the two cases. Write the recognition date and availability date first, then assign every spending line to an asset or expense bucket with one sentence of reasoning. Only after that should you prepare the entries and year-end reconciliation. This sequence makes your explanation reviewable even when the arithmetic is simple.

Use a separate Riyadh variation to test your cutoff reasoning. Move the recognition date to 1 August, leaving availability on 1 November unchanged. Assume July contained 40,000 of the developer payroll and none of the testing expense. Eligible cost falls to 160,000, while project expenses before amortization rise to 220,000. Two months of straight-line amortization over four years become 6,666.67, leaving a carrying amount of 153,333.33. Explain why the later recognition date changes cost without changing the amortization start.

For Jeddah, ask which document would justify moving the start date earlier. A convincing answer identifies evidence for the last outstanding recognition condition at that earlier date. A larger total budget alone is insufficient. Then repeat the original reconciliation: 150,000 asset cost plus 180,000 expense equals 330,000 spending, funded by 300,000 cash and 30,000 payables.

Use Accountery’s [accounting practice workspace](/practice) alongside your course to practise recording and reviewing entries. Keep this article’s worksheet nearby, and explain each classification before submitting an answer. The useful next step is a fresh scenario with a changed date or cost type, followed by a review of why your treatment changed. The aim is a defensible accounting decision that another person can follow from evidence to posting.