Can ERP implementation costs be capitalized? Often some of them can, but rarely all of them. The answer depends on three things: which accounting framework you report under, whether the ERP is software you control or a cloud service you subscribe to, and what each cost actually paid for. Build work tends to qualify. Selection, training and most data clean-up do not.
I have sat in the room when a CFO asked, six months after go-live, how much of the programme could go on the balance sheet. Nobody could answer quickly, because the costs had never been recorded in a way that matched the rules. This article explains the rules in plain English, so you can set the budget up properly from day one.
CAPEX vs OPEX: what capitalising actually means
Capital expenditure (CAPEX) is spending recorded as an asset and spread over several years through amortisation. Operating expenditure (OPEX) hits the profit and loss account in the period you spend it. Capitalising does not make a programme cheaper. It changes when the cost shows up in your results.
Usually capitalised (CAPEX)
- Configuring and coding software you will control
- Building interfaces and conversion programs
- Installing and testing the new system
- Time of people working directly on the build
Usually expensed (OPEX)
- Choosing the vendor and writing the business case
- Training end users
- Cleansing and purging old data
- General overhead and post go-live support
How US GAAP treats it: the three stages of ASC 350-40
Under US GAAP, software built or bought for your own use falls under ASC 350-40, Internal-Use Software. Today it splits a project into three stages, and the stage decides the treatment.
- Preliminary project stageOptions, vendor selection, business case. Expensed.
- Application development stageDesign, configuration, coding, installation, testing. Generally capitalised once the project is approved and funded and completion is probable.
- Post-implementation stageTraining, maintenance, support. Expensed.
Training, general administration and overhead stay in OPEX, even during the middle stage.
One change is coming. In September 2025 the FASB issued ASU 2025-06, which removes the three stages and replaces them with a principles-based test: capitalise once management has authorised and committed to funding the project and it is probable the software will be completed and used as intended. It applies to annual periods beginning after 15 December 2027, with early adoption allowed. Deloitte has a summary of ASU 2025-06. Ask your auditor which model you will use for your programme.
Cloud ERP: how ASU 2018-15 handles SaaS implementation costs
Most new ERP programmes are cloud subscriptions. The accounting term is a cloud computing arrangement (CCA). If the contract does not give you a software licence, it is a service contract, and the subscription fee is an operating cost.
ASU 2018-15, issued in August 2018, says you apply the same ASC 350-40 test to the implementation costs of a cloud service contract. Qualifying costs are capitalised, then expensed over the term of the hosting arrangement, in the same line of the income statement as the subscription fee. They sit on the balance sheet like a prepayment, not as a software asset. Deloitte explains this in its Heads Up on ASU 2018-15.
How IFRS treats it: IAS 38 and the April 2021 IFRIC decision
Under IFRS, the standard is IAS 38, Intangible Assets. For software you control, development costs can be capitalised if the IAS 38 criteria are met. Cloud is different, and stricter than US GAAP.
In 2019 the IFRS Interpretations Committee said a typical SaaS contract gives you a service, not an asset. In its agenda decision on configuration or customisation costs in a cloud computing arrangement, finalised in April 2021, it went further. Those costs are usually expensed. They create an intangible asset only when the work produces something you control, such as separate code you own. If the SaaS supplier does the work and it is not distinct from your access to the software, you expense it over the contract term. Otherwise you expense it when the work is done. BDO gives a clear summary of the IFRIC decision.
Can data migration be capitalized? Are project manager costs capitalized?
I hear these two most. Both answers start with it depends.
- Data migration. Under ASC 350-40, the cost of software that converts old data for the new system can be capitalised. Manual conversion, cleansing, purging and reconciling data are expensed. So the extraction and load programs may qualify, while the weeks your business users spend fixing records will not. The RIT controller guide shows how one organisation applies this.
- Project manager costs. Payroll for people directly working on the build during development can be capitalised, for the time they spend on it. A programme manager running design and build may partly qualify. PMO overhead, general administration and steering time usually do not.
- Under IFRS for SaaS. Most of this is expensed anyway, because the configuration itself is usually expensed.
If you want to see how long a migration really runs, and where the effort goes, read how long data migration takes.
Why tagging costs by phase in the budget makes this easier
Auditors ask for evidence. They want to see which costs belong to which stage and what work each one paid for. If your budget only shows one line per vendor, finance has to rebuild that trail from invoices and timesheets after the fact. That is slow, and the mistakes go both ways.
Set the budget up for capitalisation on day one
- Agree the policy early
Ask finance and the auditor which framework and model apply before the first invoice arrives.
- Split costs by phase
Separate selection, build, data, training and support so each line maps to a stage.
- Link costs to the work
Tie each cost to the plan task or workstream it paid for, so the trail exists without detective work.
- Record people time properly
Track time spent directly on build apart from management and overhead time.
- Review each quarter
Let finance confirm the split while the facts are fresh, not after go-live.
Phase tagging also helps you control the budget itself. You can see when data or testing is drifting, which is one of the main reasons projects go over budget.
How ProjectCAPEX helps
ProjectCAPEX does not decide what is capital. Your finance team and auditor do. What it gives you is a clean trail. Every line in the cost log carries a category and a workstream, can be linked to a task in the plan, and sits beside budget versus actual and forecast at completion. Payroll, contractors and fixed-fee contracts are tracked in the same place. See it in the demo or start free.