Software projects can consume millions of dollars before a new system produces its first useful report. ERP implementations, data platforms, workflow tools, custom integrations and cloud subscriptions often combine licenses, configuration, coding, conversion, training and support in a single vendor statement of work. Treating the entire invoice as either an asset or an expense is rarely a sound accounting policy.
For financial controllers, the challenge is to identify what the company has acquired or created, which accounting framework applies, when capitalization criteria are met, and which costs are directly attributable. The answer can differ materially under US GAAP, IFRS Accounting Standards and Canadian Accounting Standards for Private Enterprises (ASPE). The differences matter even more as software teams use agile delivery and cloud-based services.
1. Classify the arrangement before reviewing the invoice
Start by identifying the nature of the software arrangement. At a minimum, distinguish:
- Software developed internally for the company’s own use.
- A software license or product acquired from a vendor.
- Software developed to be sold, leased or marketed to customers.
- A software-as-a-service (SaaS) or other hosting service where the supplier controls the application.
- Implementation, configuration, customization, integration, data migration, training, maintenance and support services.
These categories may fall under different guidance. For example, US GAAP separates internal-use software under ASC 350-40 from software to be sold, leased or marketed under ASC 985-20. The FASB’s ASU 2025-06 expressly leaves software within ASC 985-20 outside its amendments. Do not apply the internal-use software model to every technology invoice.
2. Establish the project boundary and reporting framework
Give each material software initiative a defined project scope, business owner, technical owner, approved budget, expected functionality, delivery method and intended users. Separate major modules or components when their functionality, readiness, funding decisions or useful lives differ. A broad label such as “digital transformation” is not a sufficiently precise unit for cost tracking.
Identify the reporting framework of each legal entity and the purpose of the financial statements. A Canadian private enterprise applying ASPE may reach a different accounting result from a Canadian publicly accountable enterprise applying IFRS or a US registrant applying US GAAP. A common group project code does not make the accounting policies interchangeable.
3. Apply the current US GAAP model carefully
For internal-use software under current ASC 350-40, the traditional model distinguishes the preliminary project stage, the application development stage and the post-implementation stage. Preliminary project costs and post-implementation activities such as training and maintenance are generally expensed. Eligible direct costs incurred during the application development stage are capitalized. The nature of the work—not the vendor’s invoice label—determines the accounting.
Eligible costs can include direct third-party development services and payroll for employees directly associated with the project, based on the time they spend on it. General and administrative overhead is not capitalized. Training is expensed. Most data conversion activities, such as cleansing, reconciling and balancing old and new data, are also expensed; the specific software developed or obtained to allow access to or conversion of old data is treated separately under ASC 350-40.
For a cloud computing arrangement that is a service contract, ASU 2018-15 requires the customer to use the internal-use software guidance to determine which implementation costs are capitalized. The accounting for the hosting service itself remains separate. This is why the controller must first establish whether the arrangement includes a software license or is simply a service contract.
4. Apply IAS 38’s research and development test under IFRS
Under IAS 38, research expenditure is expensed as incurred. Development expenditure is recognized as an intangible asset only when the entity can demonstrate all six criteria: technical feasibility of completion; intention to complete and use or sell the asset; ability to use or sell it; how it will generate probable future economic benefits; availability of adequate technical, financial and other resources; and reliable measurement of attributable expenditure.
If the entity cannot distinguish the research phase from the development phase, the expenditure is treated as research. Capitalization begins only from the date all recognition criteria are met; costs previously expensed cannot simply be reinstated later. Directly attributable costs may be included, but training, general administration and identified inefficiencies are not automatically part of the asset.
Cloud configuration and customization require a separate control assessment. In its April 2021 agenda decision, the IFRS Interpretations Committee explained that a customer often does not recognize an intangible asset for configuration or customization of a supplier-controlled SaaS application because the customer does not control a separate resource. The costs are generally expensed as the supplier performs the service, unless identifiable additional code is controlled by the customer and meets IAS 38. A prepayment remains an asset until the related service is received. See the IFRIC decision on cloud configuration and customization costs.
5. Understand the ASPE policy choice
Canadian ASPE Section 3064, Goodwill and Intangible Assets, also requires research expenditures to be expensed. A published MNP summary of Section 3064 (March 2021) describes a policy choice for development-phase expenditures: an entity may expense them as incurred or capitalize them when all specified criteria can be demonstrated. The selected policy is applied consistently to expenditures on all internal projects in the development phase. The summary also describes direct attribution and reliable measurement requirements.
This is not the same as IAS 38’s requirement to capitalize development expenditure once the criteria are met. Before approving an ASPE policy, consult the current CPA Canada Handbook and document the election and its consistent application. CPA Canada’s May 2023 Board of Examiners’ report also illustrates the Section 3064 treatment of training costs as expenses.
6. Track time and cost at a level that supports the accounting
Set up project codes and time-recording rules before development begins. Require employees and vendors to distinguish qualifying development work from discovery, project administration, data cleansing, training, support and maintenance. Reconcile payroll and vendor invoices to project records each month. A high-level percentage estimate from the project manager is not a substitute for supportable cost attribution.
For an agile project, retain sprint goals, backlog items, design decisions, testing results, release notes and approvals. These records help demonstrate when functionality became sufficiently defined, whether the work created or enhanced a controlled asset, and which costs relate to eligible development rather than ongoing operations.
7. Prepare now for the FASB’s 2025 software-cost update
On September 18, 2025, the FASB issued ASU 2025-06, which removes the prescriptive project-stage references in ASC 350-40. Under the amended model, capitalization begins when management has authorized and committed to funding the project and it is probable that the project will be completed and the software will be used for its intended function. The assessment must consider significant development uncertainty, including unresolved novel or unproven functionality and significant performance requirements that have not been identified or continue to be substantially revised.
The amendments are effective for annual reporting periods beginning after December 15, 2027, and interim periods within those annual periods. Early adoption is permitted at the beginning of an annual reporting period. As of November 17, 2026, this is not yet the mandatory model for entities that have not early adopted it. Controllers should document whether the company plans to early adopt, assess the available prospective, modified or retrospective transition approaches, and avoid applying the new threshold to periods still governed by the existing model.
IFRS is also reviewing IAS 38. The IASB’s project page records that on October 27, 2026, the Board discussed possible options using agile software development as a test case but made no decisions. That discussion is not a change to IAS 38. Continue applying the existing recognition criteria unless and until an amendment is issued and becomes effective. See the IASB Intangible Assets project update.
8. Separate SaaS services from customer-controlled code
For each cloud contract, obtain the statement of work, architecture description, intellectual-property clauses and acceptance terms. Ask whether the customer receives a software license, access to supplier-controlled software, a distinct deliverable, or additional code that the customer controls. Ask who can access, modify, reuse and restrict access to the code after implementation.
Do not capitalize configuration simply because it is expensive or necessary to go live. Under IFRS, the IFRIC agenda decision makes control of a separate resource central to the analysis. Under US GAAP, a hosting service contract has its own implementation-cost guidance. For ASPE, assess the definition and recognition criteria in Section 3064 and the entity’s established development-cost policy. The same vendor deliverable can therefore produce different accounting outcomes across group entities.
9. Build the project accounting trail in SAP
In SAP S/4HANA, use an approved project structure, WBS element or internal order to collect costs by initiative and cost type. Restrict postings to valid project codes, require time and invoice support, and reconcile project actuals to the general ledger. Where the design uses assets under construction and settlement, validate the settlement rules, asset class, receiver and ledger treatment before the first capitalization run.
SAP’s Assets Under Construction: Management and Settlement documentation describes collecting investment-project costs on WBS elements and settling qualifying amounts to assets under construction and completed assets. That is a system capability, not an accounting conclusion: Finance must decide which costs qualify under the entity’s reporting framework and configure the accounting accordingly.
10. Review capitalization, amortization and impairment at each close
At every month-end, reconcile the software cost subledger or project ledger to the general ledger. Review capitalization start dates, eligible cost categories, paused or abandoned projects, budget overruns, project completion evidence and costs posted after the asset is available for use. Under IAS 38, amortization begins when the asset is available for use. Under US GAAP and ASPE, apply the relevant useful-life and amortization requirements for the recognized asset.
Require a documented technical and finance review when a project is delayed, redesigned, replaced or no longer expected to deliver its intended function. Reassess whether capitalization criteria continue to be met and whether existing balances require impairment. Retain the approval, project status, recoverability analysis, useful-life rationale and journal entry support.
Controller’s implementation checklist
- Classify each arrangement as internal-use software, external-use software, license, SaaS service or implementation service.
- Identify the applicable reporting framework for every entity and document the accounting policy.
- Approve project scope, funding, functionality, ownership and capitalization criteria before costs are accumulated.
- Separate research, development, configuration, data conversion, training, support and maintenance costs.
- Capture direct labor and vendor costs with project-level evidence and monthly reconciliation.
- Document the capitalization date and the criteria met under the applicable framework.
- Assess the effect of FASB ASU 2025-06 and monitor IASB developments without prematurely applying proposals.
- Review project status, asset availability for use, amortization and impairment at each close.
Conclusion
Software capitalization is a finance-control process, not merely a project-accounting exercise. A disciplined controller distinguishes the asset or service being acquired, applies the correct jurisdictional framework, tracks eligible costs from the appropriate date and reassesses projects as facts change. With FASB’s new internal-use software guidance approaching and the IASB reviewing IAS 38, maintaining a clear project-level audit trail now will make future accounting decisions more consistent and defensible.
Disclaimer: This article is for general informational purposes only and is not accounting, audit, tax, legal or implementation advice. Consult the current authoritative accounting standards and qualified advisers for entity-specific conclusions.
Sources and further reading
- FASB ASU 2025-06 — Targeted Improvements to the Accounting for Internal-Use Software, issued September 18, 2025; effective for annual periods beginning after December 15, 2027.
- FASB ASU 2018-15 — Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract, issued August 29, 2018.
- IFRS Foundation — IAS 38 Intangible Assets, standard overview accessed November 17, 2026.
- IFRS Interpretations Committee — Configuration or Customisation Costs in a Cloud Computing Arrangement, agenda decision published April 2021.
- IFRS Foundation — Intangible Assets project, IASB update following its October 27, 2026 meeting.
- MNP — ASPE 3064 Goodwill and Intangible Assets, March 2021 summary.
- CPA Canada — May 2023 Board of Examiners’ Report, illustrative ASPE 3064 application.
- SAP Help Portal — Assets Under Construction: Management and Settlement.





