Cloud ERP programs can generate large costs long before a system goes live: configuration, custom code, integrations, data migration, testing, training, process redesign and ongoing subscription fees. Treating the entire project budget as one capital asset—or expensing everything because the software is hosted in the cloud—can produce the wrong result.
Financial controllers need a repeatable way to identify what the company has purchased, what services it receives, which costs qualify for capitalization under its reporting framework, when amortization or expense recognition begins, and how project changes affect the conclusion. This is especially important as US GAAP changes its internal-use software guidance in the coming years.
1. Start with the contract, not the project name
Determine whether the company has obtained a software license or a right to access a supplier-controlled application as a service. Review contract terms, hosting rights, termination provisions, the ability to take possession of software, and any separately identifiable licenses or deliverables. “Cloud ERP,” “implementation,” and “subscription” are commercial labels; they do not by themselves settle the accounting.
Under US GAAP, FASB ASU 2018-15 addresses implementation costs incurred by a customer in a cloud computing arrangement that is a service contract. It aligns the analysis of those implementation costs with the internal-use software guidance in ASC 350-40; it does not change the accounting for the hosting service itself. Have Technical Accounting document the arrangement’s scope and the policy applied to each material component.
2. Separate the project into cost components
A vendor statement of work may bundle many different activities into one fixed fee. Ask for a detailed breakdown, supported by milestones, resource records or other reasonable allocation evidence. At a minimum, identify:
- Software license or subscription and hosting fees;
- Configuration and customization;
- Development of interfaces, reports, workflows or other code;
- Data cleansing, conversion and migration;
- Testing and quality assurance;
- Training, change management and process redesign;
- Project management and internal employee time;
- Post-go-live support, maintenance and routine operations.
Do not capitalize an entire invoice simply because some activities may qualify. Define a documented allocation method for mixed invoices, apply it consistently and review significant changes in the scope of work. Training and data conversion are common examples of costs that require careful analysis rather than automatic inclusion in a software asset.
3. Use the right US GAAP model for the reporting period
For US GAAP arrangements currently within ASC 350-40, the existing model evaluates costs by project stage. Under the guidance for a hosting arrangement that is a service contract, qualifying implementation costs are assessed using the internal-use software model; eligible application-development-stage costs may be capitalized, while preliminary-project and post-implementation operating costs are generally expensed as the activities are performed.
FASB issued ASU 2025-06, Targeted Improvements to the Accounting for Internal-Use Software, in September 2025. The update removes the prescribed project-stage references and changes the recognition threshold. Capitalization begins when management has authorized and committed to funding the project and it is probable the project will be completed and the software will be used for its intended function. The assessment of whether completion is probable includes consideration of significant development uncertainty.
The amendments are effective for annual reporting periods beginning after December 15, 2027, including interim periods within those annual periods. Early adoption is permitted at the beginning of an annual reporting period. The update also provides transition approaches. Controllers should confirm the entity’s adoption plan and chosen transition method with Technical Accounting rather than applying the future model prematurely to current-period reporting.
4. Apply IFRS based on control of the software or code
IFRS does not simply import the US GAAP project-stage model. In its April 2021 agenda decision on configuration or customisation costs in a cloud computing arrangement, the IFRS Interpretations Committee explained that access to supplier-controlled SaaS software is generally a service rather than a software asset for the customer. Configuration or customization of that application often does not create a separate intangible asset because the customer does not control the underlying software.
There can be exceptions. For example, additional code may qualify as an intangible asset if it is identifiable and the customer controls it and meets IAS 38’s recognition criteria. If no intangible asset is recognized, the timing of expense recognition depends on when the configuration or customization services are received. If the customer pays before receiving the services, a prepayment may be appropriate.
The IASB continued discussing potential improvements to IAS 38 in September 2026 but made no decisions at that meeting. See the September 2026 IASB Update. Keep the accounting conclusion tied to the requirements applicable to the reporting period, not to a possible future change.
5. Do not assume Canadian ASPE is identical
For a Canadian private enterprise reporting under ASPE, assess the applicable requirements in the current CPA Canada Handbook, including Section 3064 where relevant, together with the facts and contractual rights. Do not assume that either ASC 350-40 or the IFRS Interpretations Committee’s SaaS agenda decision can be copied across without analysis. Document the reporting framework, policy, key judgments and any differences from group reporting instructions.
For a multinational group, maintain a framework-specific accounting memo and a controlled consolidation adjustment where local books and group reporting use different policies. Make sure the adjustment is supported, reviewed and reversed or carried forward correctly in subsequent periods.
6. Establish a capitalization decision record
For every material workstream, maintain a short decision record that identifies the contract, deliverable, nature of the cost, relevant guidance, recognition conclusion, start date, useful life or amortization period where applicable, and the evidence supporting the conclusion. A decision record should also explain why similar costs are treated consistently across workstreams.
For US GAAP projects preparing for ASU 2025-06, capture the date management authorized and committed to funding, evidence supporting probable completion, unresolved technical risks and the status of required functionality. For IFRS, document whether the customer controls a software asset or separately identifiable code and when contracted services are delivered.
7. Reconcile vendor invoices, purchase orders and project records
Build a monthly reconciliation between the approved project budget, purchase orders, vendor invoices, time records, accounts payable and the software-cost schedule. Check that invoice lines are coded to the correct project and cost category, duplicate charges are identified, credits are recorded, and unapproved scope changes are not automatically capitalized.
In SAP or another ERP, use project/WBS identifiers, internal orders or equivalent coding consistently. Restrict who can change project status and cost classifications. Reconcile capitalized additions and expenses to the general ledger, and investigate differences between project-management reports and financial records before close sign-off.
8. Control the go-live date and amortization or expense pattern
Do not use a single overall go-live date without considering the relevant accounting requirements and the actual readiness of components. For capitalized assets, document when each component is ready for its intended use and how the applicable useful life or amortization period was determined. Under the US GAAP hosting-arrangement guidance, capitalized implementation costs are amortized over the term of the hosting arrangement; assess contract terms and renewal options under the applicable guidance.
Maintain a schedule by module or component, with links to acceptance evidence, deployment approvals and the general ledger. If a module is delayed, abandoned or replaced, assess whether the existing cost treatment remains appropriate and whether impairment, abandonment or write-off guidance is triggered.
9. Monitor scope changes and project uncertainty
Cloud implementations evolve. A new interface, a major redesign, an unsuccessful pilot or a vendor change can affect both the nature of costs and the support for capitalization. Require finance review when a change order materially changes deliverables, development uncertainty, project funding, expected completion or the contract term.
For the future US GAAP model under ASU 2025-06, build evidence around significant development uncertainty, including unresolved technological innovations or novel features and significant changes to performance requirements. Keep the accounting analysis connected to project governance so that Finance receives updates before the quarter-end close.
10. Make the close review substantive
The reviewer should challenge the largest additions, new workstreams, manual reclassifications, cost allocations, changes in expected completion, amortization starts, and any project paused or discontinued. Retain the question raised, evidence inspected, conclusion and remediation—not only an electronic approval.
Coordinate the review across controllership, IT, procurement, legal, project management and tax where relevant. For public-company reporters, assess whether the process is part of the relevant internal-control-over-financial-reporting framework and whether controls over source reports, spreadsheets and manual journals are appropriately designed.
Month-end controller checklist
- Contract and hosting/licensing conclusion documented.
- Vendor invoices split into defensible cost components.
- Capitalization assessment aligned to the reporting framework and period.
- Current US GAAP policy distinguished from the future ASU 2025-06 model.
- IFRS or ASPE conclusions documented separately where applicable.
- Project costs reconciled to AP, project records and the general ledger.
- Go-live, component readiness, amortization and abandonment reviewed.
- Material scope changes and development uncertainty escalated.
- Reviewer challenge and supporting evidence retained.
Conclusion
Cloud ERP accounting is strongest when contract analysis, project governance and close controls work together. Separate services from software-related deliverables, allocate bundled costs transparently, apply the correct framework for the reporting period and maintain evidence as the project changes. With FASB’s ASU 2025-06 effective for annual periods beginning after December 15, 2027, US GAAP reporters should also plan ahead—without applying the new recognition model before adoption.
Informational only: This article is a general finance-control overview, not accounting, audit or legal advice. Confirm the authoritative requirements applicable to your entity, reporting framework and reporting period.
