SIC 32 Intangible Assets: Website Costs and Capitalisation Logic
Author
Sai Manikanta Pedamallu
Published
Reading Time
17 min read
Table of Contents
SIC 32 Intangible Assets: Website Costs and Capitalisation Logic
By Sai Manikanta Pedamallu (ACCA, CMA US, CSCA US, CGMA, ACMA, Dip IFRS, M.Com, MBA, MA)
Lead Instructor, Global Fin X | www.globalfinx.in/manikanta
Two Indian companies each spend Rs. 4 crore building a website in the same year, using the same development agency and the same technology.
One capitalises most of it. The other expenses all of it.
Both are correct, and the difference has nothing to do with how much was spent, how sophisticated the site is, or how long it took to build. It turns entirely on what the website is for.
SIC-32 is a short interpretation issued in March 2002, and it remains the operative guidance for website costs under IFRS. It is not a separate standard. It is an application guide for IAS 38, and its logic follows directly from the internally generated intangible framework covered in Posts 36 and 37.
The Starting Point: A Website Is an Internally Generated Intangible
A website developed by an entity using internal expenditure, whether for internal or external access, is an internally generated intangible asset subject to IAS 38.
That classification determines everything. Because the website is internally generated rather than separately acquired, the presumption in IAS 38 that separately acquired intangibles satisfy the probability recognition criterion does not apply. The entity must satisfy the development phase criteria in full.
A website is recognised as an intangible asset if, and only if, in addition to complying with the general requirements of IAS 38 for recognition and initial measurement, the entity can demonstrate how the website will generate probable future economic benefits.
That final requirement is where SIC-32 does its real work.
The Decisive Question: What Is the Website For?
An entity can demonstrate probable future economic benefits where, for example, the website is capable of generating revenues, including by enabling orders to be placed.
Where the website is solely or primarily for promoting and advertising the entity's own products and services, the entity is not able to demonstrate how it will generate probable future economic benefits.
All expenditure on developing such a website is recognised as an expense when incurred.
This is the rule that produces the divergent outcomes in the opening example.
A brochure website that describes the company, lists its products, and provides contact details generates no directly attributable future economic benefit that can be demonstrated. It may well support sales, but so does advertising generally, and IAS 38 prohibits capitalising advertising and promotional expenditure regardless of how effective it is. The website is a marketing channel, and marketing spend is expensed.
An e-commerce platform on which customers place orders and pay generates revenue directly through the site. The future economic benefit is demonstrable and attributable. Subject to the remaining criteria, development costs may be capitalised.
The dividing line is not technical sophistication. A visually elaborate, expensively built brochure site is fully expensed. A functionally plain site that takes orders may support capitalisation.
The Four Stages
SIC-32 divides website development into stages and maps each onto the IAS 38 research and development framework.
Planning
The planning stage involves undertaking feasibility studies, defining objectives and specifications, evaluating alternatives, and selecting preferences.
This stage is similar in nature to the research phase under IAS 38. Expenditure incurred in the planning stage is recognised as an expense when incurred, without exception.
This is not a matter of whether the criteria are met. Research phase expenditure is never capitalised, and planning is research.
Application and Infrastructure Development
This stage involves obtaining a domain name, purchasing and developing hardware and operating software, installing developed applications, and stress testing.
This stage is similar in nature to the development phase. Expenditure is included in the cost of the website recognised as an intangible asset when the expenditure can be directly attributed and is necessary to creating, producing, or preparing the website for it to be capable of operating in the manner intended by management.
Both conditions apply: directly attributable, and necessary. General overhead allocated on an arbitrary basis satisfies neither.
Graphical Design Development
This stage involves designing the appearance of the web pages.
Also similar in nature to the development phase, and capitalisable on the same directly attributable and necessary basis.
Note the implication: design costs for a revenue-generating site are capitalisable, while design costs for a promotional site are not, because the promotional site fails the threshold test before the stage analysis is ever reached.
Content Development
This stage involves creating, purchasing, preparing, and uploading information onto the website before development is complete.
This is where SIC-32 draws its sharpest distinction, and it is the point most often stated incorrectly.
Content development is similar in nature to the development phase, and is capitalisable, to the extent that content is developed for purposes other than to advertise and promote the entity's own products and services.
Content developed to advertise and promote the entity's own products and services is recognised as an expense when incurred.
Two categories of content, in the same stage, with opposite treatments.
The interpretation gives a concrete illustration. Where an entity incurs expenditure on professional services for taking digital photographs of its own products and for enhancing their display, that expenditure is recognised as an expense as the professional services are received during the process, not when the photographs are eventually displayed on the website.
The timing point in that example is worth noting separately. The expense arises as the service is received, not at some later point when the output goes live.
Purchased content that is not promotional, such as a licensed database, market data, or a technical reference library made available through the site, is capitalisable where it is directly attributable and necessary to preparing the website for its intended use.
Operating
The operating stage begins once development of the website is complete. During this stage the entity maintains and enhances the applications, infrastructure, graphical design, and content.
Subsequent expenditure to enhance or maintain the website is recognised as an expense when incurred, unless it meets the recognition criteria in IAS 38.
IAS 38 explains that most subsequent expenditures are likely to maintain the future economic benefits embodied in an existing intangible asset rather than meet the definition of an intangible asset and the recognition criteria, and that it is often difficult to attribute subsequent expenditure directly to a particular intangible asset rather than to the business as a whole.
In practice, this means routine updates, bug fixes, content refreshes, security patching, and design tweaks are expensed. A genuinely new module adding functionality the site did not previously have may qualify, but it is assessed on its own merits against the full criteria.
Stage Summary
| Stage | Nature under IAS 38 | Treatment |
|---|---|---|
| Planning | Research phase | Expense, always |
| Application and infrastructure development | Development phase | Capitalise where directly attributable, necessary, and the site is not solely or primarily promotional |
| Graphical design development | Development phase | Capitalise on the same basis |
| Content development, non-promotional | Development phase | Capitalise on the same basis |
| Content development, promotional | Advertising and promotion | Expense, always |
| Operating | Subsequent expenditure | Expense, unless it meets the IAS 38 recognition criteria |
The threshold question sits above the entire table. Where the website is solely or primarily promotional, everything is expensed and the stage analysis does not arise.
What SIC-32 Does Not Cover
Four categories fall outside the interpretation, and each is accounted for elsewhere.
Hardware. Expenditure on purchasing, developing, and operating hardware, including web servers, staging servers, production servers, and internet connections, is accounted for under IAS 16 as property, plant and equipment. SIC-32 addresses the intangible layer only.
Hosting services. Where an internet service provider hosts the entity's website, that expenditure is recognised as an expense as the services are received.
Websites for sale. IAS 38 does not apply to intangible assets held for sale in the ordinary course of business. A website or website software developed for sale to another entity falls under IAS 2 or IFRS 15 rather than SIC-32. A development agency building sites for clients is delivering a service, not creating its own intangible asset.
Leased websites. Website arrangements accounted for under IFRS 16 are outside scope.
The Outsourcing Question
A practical question arises frequently and is worth addressing directly: does SIC-32 apply where the entity pays a third party to build the website rather than developing it in-house?
The wording of the interpretation refers to internal expenditure, which has led some preparers to assume that outsourced development sits outside its scope and is simply a separately acquired intangible.
The better view, and the one generally applied in practice, is that an outsourced website is still an internally generated intangible asset. The entity has not purchased a completed asset from a market; it has commissioned the construction of an asset to its own specification. The development phase criteria apply equally to internal and external costs, and the same directly attributable and necessary test governs which costs enter the carrying amount.
The distinction that matters is between acquiring an existing asset and constructing an asset, not between doing the construction with employees or with contractors. A company that buys an established e-commerce platform from another business has acquired an intangible asset. A company that pays an agency to build a platform to its brief has developed one.
Expensed Costs Cannot Be Reinstated
IAS 38 is explicit and SIC-32 repeats it: expenditure on an intangible item that was initially recognised as an expense in previous financial statements shall not be recognised as part of the cost of an intangible asset at a later date.
The consequence for websites is direct. An entity that expenses development costs during a year in which it cannot demonstrate probable future economic benefits, and then adds a payment gateway in the following year that transforms the site into a revenue-generating platform, cannot go back and capitalise the earlier costs.
Only costs incurred from the point the criteria are met can be capitalised.
This creates a genuine practical incentive to assess the criteria contemporaneously rather than retrospectively, because the assessment cannot be revisited to the entity's benefit.
Useful Life and Subsequent Measurement
A website recognised as an intangible asset is measured after initial recognition by applying the ordinary IAS 38 requirements, meaning the cost model or, where an active market exists, the revaluation model. In practice an active market for a website does not exist, so the cost model applies.
The best estimate of a website's useful life is short. SIC-32 says so directly, and the commercial reality supports it: technology stacks change, design conventions date quickly, and functionality is superseded.
Amortisation periods of two to five years are common in practice, and an entity asserting a ten-year useful life for a website should expect to justify it.
The website is also within the scope of IAS 36 and is tested for impairment where indicators exist, as covered in Post 39.
Worked Example
An Indian consumer brand incurs the following costs during the year on a new website:
| Item | Rs. lakh | Treatment |
|---|---|---|
| Feasibility study and vendor selection | 12 | Expense: planning stage |
| Domain registration and hosting setup | 6 | Expense: hosting is a service received; domain registration capitalisable if directly attributable |
| Web servers purchased | 40 | IAS 16: property, plant and equipment, outside SIC-32 |
| Platform development and integration with inventory system | 180 | Capitalise if criteria met |
| Payment gateway integration | 45 | Capitalise if criteria met |
| Graphical design of the storefront | 60 | Capitalise if criteria met |
| Product photography and promotional copy | 55 | Expense: content promoting own products |
| Licensed size-guide and materials database | 20 | Capitalise if criteria met: non-promotional content |
| Stress testing before launch | 15 | Capitalise if criteria met |
| Post-launch bug fixes and content updates | 30 | Expense: operating stage |
Scenario A: the site is a transactional e-commerce platform.
The entity can demonstrate probable future economic benefits, because customers place and pay for orders through the site. The development phase criteria are assessed and met.
Capitalised: Rs. 320 lakh, comprising platform development, payment gateway, graphical design, licensed database, and stress testing.
Expensed: Rs. 97 lakh, comprising planning, hosting, product photography and promotional copy, and post-launch maintenance.
Recognised under IAS 16: Rs. 40 lakh of servers.
Scenario B: the site is a brand showcase with no transactional capability, directing visitors to retail partners.
The site is solely or primarily for promoting and advertising the entity's own products and services. Probable future economic benefits cannot be demonstrated.
Capitalised: nil.
Expensed: Rs. 417 lakh, being everything other than the servers.
Recognised under IAS 16: Rs. 40 lakh of servers.
Identical spending. Identical vendors. A difference of Rs. 320 crore in capitalised intangibles arises purely from the addition of transactional functionality.
Mobile Applications and Digital Platforms
SIC-32 addresses websites specifically. It predates the mobile application economy entirely, having been issued in 2002.
In practice, the same analytical framework is applied by analogy to mobile applications and digital platforms, because the underlying question is identical: is this an internally generated intangible asset from which probable future economic benefits can be demonstrated, and which costs are directly attributable and necessary to preparing it for its intended use?
The same distinction applies. An app through which customers transact is analytically different from an app that displays the company's catalogue and directs users elsewhere.
Entities should be explicit in their accounting policy about how they apply the framework to applications and platforms, since SIC-32 does not do so by its own terms.
The Indian Application
The distinction SIC-32 draws has become commercially significant in India as digital spend has grown.
E-commerce and direct-to-consumer brands. Indian D2C brands operating transactional websites and apps face the capitalisation question directly, and the answer materially affects reported profitability in the launch and scale-up years. Development costs capitalised and amortised over three years present very differently from the same costs expensed in a single year.
Companies with brochure sites. A manufacturer, professional services firm, or B2B business whose website exists to describe the business and generate enquiries is squarely within the promotional exclusion. All development costs are expensed, however substantial.
Digital transformation programmes. Where a traditional business builds a customer portal, a dealer platform, or an internal knowledge system, the analysis depends on the specific function. An internal-access site storing policies and customer details is within SIC-32's scope, since the interpretation covers websites for internal as well as external access, and the probable future economic benefit test is applied to cost savings and operational benefit rather than revenue.
Startups and the audit consequence. Early-stage Indian companies frequently capitalise substantial platform development costs, and this is one of the more common areas where auditors challenge the demonstration of probable future economic benefits and the six IAS 38 development criteria, particularly technical feasibility and the intention and ability to complete.
What Big 4 Auditors Focus On
The threshold assessment. Auditors test first whether the website is solely or primarily promotional. Where it is, capitalisation of any development cost is an error regardless of how the stage analysis has been performed.
Separation of promotional content from other development costs. Auditors test whether product photography, marketing copy, brand messaging, and campaign content have been separated out and expensed, since these frequently sit within the same vendor invoice as capitalisable development work.
Directly attributable and necessary. Auditors test the composition of capitalised costs for general overhead, employee time allocated on an arbitrary basis, and internal management time, none of which meet the test.
The planning and operating boundaries. Auditors test that pre-development planning costs have been expensed and that the point at which the site became available for its intended use has been correctly identified, since costs after that point are operating stage expenditure.
Retrospective capitalisation. Auditors specifically test whether costs expensed in an earlier period have been reinstated as part of the asset in a later period, which IAS 38 prohibits absolutely.
Useful life. Auditors challenge amortisation periods that appear long relative to the pace of technological change and the entity's own history of redeveloping its digital assets.
Hardware classification. Auditors verify that server and infrastructure hardware has been recognised under IAS 16 rather than absorbed into the intangible.
Dip IFRS Exam Angle
SIC-32 produces clean classification questions with a clear decision structure.
Most tested areas:
Identifying that a website solely or primarily for advertising and promoting the entity's own products and services results in all development expenditure being expensed.
Mapping the four stages onto the IAS 38 research and development framework.
Distinguishing promotional content development, which is expensed, from other content development, which may be capitalised.
Recognising that hardware falls under IAS 16 and hosting services are expensed as received.
Recognising that operating stage expenditure is expensed unless it meets the IAS 38 recognition criteria.
Common traps:
Capitalising development costs for a promotional website because the stage analysis appears to permit it. The threshold test fails first.
Capitalising all content development. Promotional content is expensed regardless of stage.
Capitalising planning stage costs. Planning is research and is always expensed.
Including server hardware in the intangible asset. Hardware is IAS 16 property, plant and equipment.
Reinstating previously expensed costs once the site becomes revenue-generating. IAS 38 prohibits this.
Assuming outsourced development takes the website outside SIC-32. A commissioned website is still internally generated.
Applying a long useful life. SIC-32 states that the best estimate of a website's useful life is short.
FAQ
Can a company capitalise the cost of its corporate website?
Only if it is not solely or primarily for promoting and advertising the entity's own products and services, and the entity can demonstrate how the site will generate probable future economic benefits. A conventional corporate brochure site does not meet this, and all its development costs are expensed.
Why is a promotional website treated differently from a transactional one?
Because the entity cannot demonstrate probable future economic benefits attributable to a promotional site specifically, as distinct from its marketing activity generally. IAS 38 prohibits capitalising advertising and promotional expenditure, and a promotional website is a form of that expenditure.
Are product photographs for an e-commerce site capitalised?
No, where they advertise and promote the entity's own products. SIC-32 gives professional photography of an entity's own products as its explicit example of content development that is expensed, and the expense arises as the services are received rather than when the images go live.
Does SIC-32 apply to a website built by an external agency?
Yes, in the generally applied view. Commissioning construction of a website to the entity's own specification produces an internally generated intangible asset, not a separately acquired one, and the development phase criteria apply to external costs as they do to internal ones.
Where does the server hardware go?
Under IAS 16 as property, plant and equipment. SIC-32 explicitly excludes expenditure on purchasing, developing, and operating hardware from its scope.
Can costs expensed in year one be capitalised in year two once the site starts generating revenue?
No. IAS 38 prohibits recognising as part of the cost of an intangible asset any expenditure that was previously recognised as an expense. Only costs incurred from the date the criteria are met can be capitalised.
Enroll with Global Fin X
SIC-32 is one of the shortest pieces of guidance in IFRS and one of the most frequently misapplied, because the threshold question about what the website is for sits above the stage analysis and is regularly skipped. Our programme covers SIC-32 alongside the full IAS 38 framework with detailed lectures, worked classification examples, exam-style MCQs, and a dedicated LMS for working professionals.
Enroll Now: Dip IFRS Programme
Faculty profile: www.globalfinx.in/manikanta
This is Post 89 of the Global Fin X IFRS Series. Previous: IFRIC 23 Uncertainty Over Income Tax Treatments. Next: Post 90: IFRIC 21 Levies in Indian Context: GST Prepayments and Regulatory Fees.