DLALISA INSIGHTS / GRAP 31 / INTANGIBLE ASSETS

GRAP 31: Turnkey Development of Intangible Assets — Separately Acquired or Internally Generated?

Orange and charcoal illustration of bespoke software architecture, contractual milestones and transfer of intangible asset ownership

Does commissioning an independent contractor to develop a bespoke intangible asset necessarily mean that the resulting asset is internally generated?

Introduction

Public-sector entities frequently engage external service providers to develop bespoke software systems and other intangible assets tailored to their operational requirements. These projects can involve substantial financial commitments, extended development periods and contractual arrangements under which the service provider assumes responsibility for designing, developing and delivering the required asset.

In certain arrangements, the service provider undertakes the development independently, manages its own technical personnel and assumes contractual responsibility for delivering an asset that meets agreed specifications. The commissioning entity, in turn, inspects and accepts completed milestones, with ownership of the accepted work transferring to the entity.

Such arrangements raise an interesting question under the Standard of Generally Recognised Accounting Practice on Intangible Assets (GRAP 31).

The central question

Where a public-sector entity commissions an independent contractor to develop an intangible asset on its behalf, should the resulting asset necessarily be regarded as internally generated, or could the arrangement constitute a separate acquisition?

Although GRAP 31 provides recognition and measurement requirements for both internally generated and separately acquired intangible assets, determining which requirements apply to commissioned turnkey development arrangements may warrant closer examination.

The distinction is particularly important because an inappropriate classification could affect whether development expenditure is recognised as an asset or expensed, with potentially significant implications for the entity’s financial statements.

A practical scenario: Commissioning a bespoke software system

Consider a municipality that requires a specialised revenue management system to support its operations.

Rather than developing the system internally, the municipality appoints an independent software development company under a turnkey contract to design, develop, test and deliver a complete system meeting its operational requirements.

The arrangement has the following characteristics:

The municipality pays the contractor upon acceptance of each contractual milestone. The completed system will only become operational after the remaining development and implementation requirements have been satisfied.

Under these circumstances, what exactly is the municipality acquiring? Is it purchasing development services that contribute to an internally generated intangible asset? Or is it progressively acquiring an intangible asset developed by an independent contractor?

The distinction may have significant implications for the recognition and measurement of the expenditure incurred.

What does GRAP 31 tell us?

Separately acquired intangible assets

Paragraphs .28 to .35 of GRAP 31 address the separate acquisition of intangible assets. These provisions deal with the recognition and initial measurement of intangible assets purchased by an entity, including the purchase price and directly attributable costs of preparing the asset for its intended use.

Paragraph .28 explains why the probability recognition criterion is considered satisfied for separately acquired intangible assets, while paragraph .29 addresses the reliability of measuring their cost.

In a conventional acquisition, where an entity purchases an existing software system from a supplier, the application of these provisions may be relatively straightforward. But what happens when the software system does not exist when the contract is signed?

Does the fact that the asset must first be developed mean that its acquisition cannot fall within paragraphs .28 to .35? Alternatively, could an entity contract to purchase a bespoke intangible asset that will only come into existence through the supplier’s subsequent development activities?

GRAP 31 does not expressly restrict separate acquisition to intangible assets that already exist when a purchase agreement is concluded. This raises the possibility that the timing of development and the fact that an asset is bespoke may not, on their own, resolve its accounting classification.

Internally generated intangible assets

Paragraphs .46 to .65 of GRAP 31 address internally generated intangible assets. Paragraph .46 acknowledges the difficulties associated with identifying an intangible asset during its generation and reliably determining its cost.

Paragraph .52 establishes recognition conditions for intangible assets arising from development. These include demonstrating technical feasibility, the intention and ability to complete and use or sell the asset, probable future economic benefits or service potential, adequate resources and reliable measurement of attributable expenditure.

Furthermore, paragraph .63 limits the recognised cost of an internally generated intangible asset to expenditure incurred from the date the relevant recognition criteria are first met.

These requirements are particularly important where an entity undertakes a project to develop its own intangible asset. However, could their application become less straightforward where the entity is not undertaking the development itself, but has instead contracted with an independent supplier to deliver an asset for an agreed consideration?

The question is not whether development activities occurred. Clearly, they did. Rather, the question is whether those activities should be treated as the commissioning entity’s own internally generated development activities, or as activities undertaken by a supplier to produce an asset for sale to the entity.

Does using an external contractor make the asset internally generated?

Paragraph .64(a) of GRAP 31 recognises the cost of materials and services consumed in generating an internally generated intangible asset as potentially directly attributable costs. This indicates that development activities do not necessarily have to be performed exclusively by an entity’s own employees.

The Accounting Standards Board (ASB), in its September 2021 commentary concerning software licences, also acknowledges that an entity may develop its software itself or through consultants. The commentary reflects ASB staff views, rather than a formal interpretation issued by the Board.

These observations suggest that outsourcing development activities does not automatically result in separate acquisition accounting.

Consider an entity that initiates and directs its own software development programme but appoints external consultants to provide programming, testing and systems development services. The entity retains responsibility for managing the development activities and bears the economic consequences of unsuccessful development.

Such an arrangement may reasonably be viewed as an internally generated intangible asset, notwithstanding the use of external specialists.

But should the same interpretation necessarily apply to a different arrangement in which an independent contractor assumes responsibility for developing and delivering an agreed asset?

In the latter arrangement, the entity may be purchasing contractual outputs rather than directing and consuming development services. Could the distinction therefore lie less in who physically performs the development activities and more in the substance of the contractual obligations and the economic relationship between the parties?

An arrangement may be described as turnkey while substantively involving the procurement of development services. Equally, a bespoke commissioning arrangement may contain features associated with the purchase of an identifiable asset. Neither the use of an external contractor nor the description of the contract necessarily settles the question.

The role of contractual responsibility and development risk

In considering the distinction, several contractual characteristics may warrant examination. For example, who has substantive responsibility for directing the technical development process? Who bears the economic consequences if the development is unsuccessful? Is the contractor remunerated for the development effort expended, or is its entitlement to payment linked to the delivery of accepted outputs?

Similarly, does the contractor retain control of the work in progress until an agreed milestone is accepted? What rights does the commissioning entity obtain upon acceptance? Can the contractor use or commercialise the resulting work for another customer?

Paragraph .68 of GRAP 31 also distinguishes the receipt of goods from the receipt of services and refers to a right to access goods constructed by a supplier under a supply contract. Might this distinction help frame the question of whether particular milestones involve the delivery of an acquired resource or the receipt of development services?

These questions may help distinguish an arrangement involving the purchase of development services from one involving the delivery of an intangible asset. Nevertheless, these characteristics should not be regarded as definitive classification criteria prescribed by GRAP 31.

An internally generated development project may also involve fixed-price contractors, milestone payments, contractual warranties and outsourced technical project management. The issue is therefore whether the combined contractual rights, obligations and economic substance support one interpretation over the other.

Could a separately acquired intangible asset be recognised as work in progress?

A further consideration arises where development occurs progressively and the commissioning entity accepts completed milestones before the overall system becomes operational.

Paragraph .119(a) of GRAP 31 requires disclosure of cumulative expenditure recognised in intangible assets that are still being developed, distinguishing between internally generated and other intangible assets.

This distinction is particularly interesting. It indicates that GRAP 31 contemplates recognised intangible assets under development that are not necessarily internally generated.

Although paragraph .119 is a disclosure requirement rather than an independent basis for asset recognition, could it support the view that a separately acquired intangible asset may remain under construction or development after recognition?

Returning to our municipality example, suppose the contractor delivers three milestones, each representing an accepted component of the commissioned software system.

Where the municipality obtains control of the relevant intangible resource upon acceptance, and the applicable recognition requirements are met, could the expenditure associated with each milestone be recognised progressively as part of the cost of an intangible asset under construction?

Such an approach would not necessarily require each milestone to constitute a separate, independently operational intangible asset. The accepted work could form part of a single intangible resource being assembled progressively.

However, milestone acceptance alone would not establish that an intangible asset exists. An invoice and signed milestone certificate may provide evidence of contractual performance and the amount payable. They may not, without further evidence, demonstrate that the municipality controls an identifiable intangible resource.

The underlying deliverables, contractual rights and substance of the work accepted would remain important.

Furthermore, paragraph .97 provides that amortisation of an intangible asset with a finite useful life begins when it is available for use. Accordingly, an incomplete software system would not necessarily be amortised merely because individual milestones have been accepted and capitalised.

Could the capitalisation of accepted milestones be appropriate under either classification, while the basis for determining which expenditure qualifies for capitalisation differs?

What about the acquisition of an unfinished development project?

Paragraphs .36 and .37 of GRAP 31 address subsequent research or development expenditure relating to an in-process research or development project that has been separately acquired and recognised as an intangible asset.

These paragraphs require subsequent expenditure incurred after acquisition to be assessed under the relevant research and development requirements.

Their application to commissioned turnkey development arrangements deserves consideration. There may be a distinction between an entity acquiring an existing, unfinished development project and subsequently incurring expenditure to complete it, and an entity contracting from the outset for an independent contractor to develop and deliver an agreed intangible asset.

In the latter case, is the entity acquiring an in-process development project that it subsequently continues to develop, or is it receiving progressive delivery of an asset under an existing purchase arrangement?

The answer may depend on the point at which control transfers, the nature of each milestone and whether subsequent payments represent further development expenditure or additional acquisition consideration.

Could an incorrect classification result in development costs being unnecessarily expensed?

Perhaps one of the most significant implications of this discussion concerns the possibility that expenditure on a commissioned intangible asset could be incorrectly expensed because the underlying arrangement has not been appropriately classified.

Paragraph .52 of GRAP 31 requires an entity to demonstrate that all the prescribed development recognition conditions have been met before recognising an internally generated intangible asset arising from development.

Paragraph .63 further provides that the cost of an internally generated intangible asset comprises expenditure incurred from the date the applicable recognition requirements are first satisfied.

Why the initial classification matters

Paragraph .70 prohibits expenditure on an intangible item that was initially recognised as an expense under GRAP 31 from subsequently being recognised as part of the cost of an intangible asset.

These provisions raise a potentially significant concern where a commissioned turnkey project is classified as internally generated without sufficient consideration of the substance of the arrangement.

ILLUSTRATIVE ACCOUNTING SCENARIO

A R30 million turnkey software contract

A municipality commissions an independent contractor to develop a bespoke software system for R30 million, payable in three milestones of R10 million each. The contractor completes the first milestone, which the municipality inspects and formally accepts. Under the contract, ownership and exclusive control of the accepted work transfer to the municipality.

However, suppose the project is classified as internally generated and the municipality concludes that it cannot yet demonstrate all the recognition conditions in paragraph .52.

Consequently, the first R10 million is recognised as an expense rather than capitalised as intangible asset work in progress.

During subsequent stages, the municipality obtains sufficient evidence to demonstrate compliance with paragraph .52, and expenditure incurred from that point onwards is capitalised.

Under the internally generated model, expenditure correctly expensed before the recognition criteria were met would not subsequently be reinstated as part of the asset’s cost, even if the development project is ultimately successful.

But what if the underlying project had, in substance, constituted a separate acquisition from the outset?

What if the first R10 million represented consideration for an identifiable intangible resource acquired from the contractor, over which the municipality had obtained control, and the separate acquisition recognition requirements had already been satisfied?

Would applying the internally generated development criteria to that acquisition have resulted in expenditure being expensed unnecessarily? And could the inappropriate application of paragraph .52 have materially understated the value of intangible assets under construction while overstating expenditure in the municipality’s statement of financial performance?

These are consequential questions.

The example also highlights an important distinction between expenditure correctly expensed under GRAP 31 and expenditure expensed because of an accounting error.

Where expenditure was appropriately recognised as an expense because the relevant recognition criteria had not been met, paragraph .70 generally prevents its subsequent capitalisation.

However, where expenditure was incorrectly expensed because an entity applied the wrong accounting requirements, the matter may constitute an accounting error requiring correction under GRAP 3, Accounting Policies, Changes in Accounting Estimates and Errors.

The prohibition in paragraph .70 should therefore not be interpreted as preventing the correction of a genuine accounting error. Whether an adjustment is justified would depend on establishing that the original accounting treatment was incorrect, having regard to the information available at the relevant time.

Nevertheless, the need to revisit previous accounting treatments, establish the historical contractual substance and potentially correct prior-period financial statements illustrates why an appropriate classification at the outset is so important.

Could the failure to distinguish between commissioned acquisitions and internally generated development lead entities to expense expenditure that might otherwise have qualified for recognition as intangible assets under construction?

Equally, could an inappropriate separate acquisition classification result in expenditure being capitalised when the relevant recognition requirements have not been met?

Both possibilities suggest that the classification assessment warrants careful consideration before applying the associated recognition and measurement requirements.

Why does the distinction matter?

The classification could have consequences beyond the terminology used in the accounting records.

Where an intangible asset is internally generated, paragraphs .52 and .63 impose specific requirements concerning the demonstration of development recognition conditions and the point from which expenditure may be included in the asset’s cost.

Where an intangible asset is separately acquired, paragraphs .28 to .35 address the recognition and measurement of the acquisition cost.

These differences could affect the timing and amount of expenditure capitalised, particularly in projects involving significant expenditure before development milestones are achieved.

They may also affect the nature of the evidence required to support the carrying amount of intangible assets under construction.

For an internally generated project, demonstrating the recognition requirements for development expenditure is particularly relevant. For a separate acquisition, evidence of identifiable resources acquired, transfer of control, contractual consideration and the recognition criteria may be central.

However, both classifications require appropriate evidence that the entity controls an identifiable intangible resource and that the applicable recognition requirements are satisfied.

The distinction is therefore not simply an opportunity to capitalise expenditure that would otherwise be expensed. It is a question of applying the appropriate accounting principles to the substance of the transaction.

Concluding thoughts: Is there room for further interpretation?

The commissioning of bespoke intangible assets through turnkey development contracts presents an interesting area for consideration under GRAP 31.

On the one hand, the Standard recognises that internally generated intangible assets may incorporate externally supplied services. On the other hand, it provides a separate framework for intangible assets acquired through exchange transactions and acknowledges the existence of other intangible assets still under development.

However, GRAP 31 does not expressly provide a definitive test for distinguishing an outsourced internal development programme from a commissioned acquisition of an independently developed intangible asset.

This leaves several questions worth exploring.

Should the classification depend principally on who directs the development activities and bears the associated risks? Should greater weight be placed on the nature of the contractor’s obligation to deliver an asset rather than provide development services? And how should the progressive transfer of ownership and control through accepted milestones influence the assessment?

Perhaps the broader question is whether the commissioning of an intangible asset and the internal generation of an intangible asset should always be treated as equivalent activities.

More importantly, could the classification adopted at the outset determine whether substantial expenditure is capitalised as an intangible asset or recognised as an expense, with potentially significant consequences for the financial statements of public-sector entities?

Given the restrictions on the subsequent recognition of previously expensed development expenditure, the distinction deserves particular attention.

There may be merit in further discussion of these arrangements, particularly given the potential implications for the recognition, measurement and auditability of intangible assets under construction in the public sector.

Could further clarification from the Accounting Standards Board assist entities and practitioners in distinguishing between internally generated intangible assets and the separate acquisition of assets developed under turnkey contracts?

Sources and further reading

Accounting Standards Board — GRAP 31: Intangible Assets (1 April 2026 version). Relevant provisions include paragraphs .21–.35, .36–.37, .46–.65, .68–.70, .97 and .119.

Accounting Standards Board — “How should software licences be accounted for?” (23 September 2021). Commentary reflecting ASB staff views, not a formal interpretation of the Board.

Accounting Standards Board — GRAP 3: Accounting Policies, Changes in Accounting Estimates and Errors. Relevant when assessing potential correction of genuine accounting errors.

This Insight is intended to encourage technical discussion and consideration of the relevant provisions of GRAP 31, rather than prescribe a particular accounting treatment. The appropriate classification depends on the facts and circumstances of each arrangement.

← Browse all insights