Accounting standards
Implementing a new cloud ERP? Which costs you can capitalize
November 18, 2026 · 9 min read

Quick answer
If your new cloud ERP is a subscription (a hosting arrangement that's a service contract), the subscription fee is an expense, but under ASU 2018-15 you capitalize the implementation costs that the internal-use software rules (ASC 350-40) would capitalize, mainly configuration, integration, coding and testing. Training, data conversion and planning are expensed. The capitalized costs sit with your prepaid expenses, are amortized straight-line over the subscription term (including renewals you're reasonably certain to take), and show up in the same income statement and cash flow lines as the subscription fee.
The ERP project is signed. The subscription is $96,000 a year, and the implementation partner's estimate came in at more than double that, before you count the weeks your controller will spend testing. Your first question as the owner is how much cash this burns. Your accountant's question is different: how much of it hits this year's profit, and how much goes on the balance sheet?
For cloud software, the answer comes from ASU 2018-15, which sits in ASC 350-40. It's been in force for private companies since 2021, but plenty of businesses are implementing their first real cloud ERP now and expensing the whole thing by default. That understates profit in the implementation year and overstates it later.
Here's what qualifies, where it goes, how long to spread it, and a worked example for a mid-sized distributor.
Is your cloud ERP a license or a service contract?
Start here, because it decides which rules apply.
Most cloud ERPs (NetSuite, Sage Intacct, Acumatica, Dynamics 365 Business Central in the cloud) are service contracts. You get access to software running on the vendor's servers. You don't own a copy and can't take one home.
The software counts as a license only if you have a contractual right to take possession of it during the term without a significant penalty, and it's feasible for you to run it on your own hardware or with another hosting provider. That's rare for a modern subscription ERP. If you do have a license, you'd record an internal-use software intangible asset, and the rest of this post doesn't apply.
For a service contract, two things are true at once:
- The subscription fee is an expense, recognized as you receive the service. Paying a year upfront creates a prepaid expense, not an asset you amortize over five years.
- Certain implementation costs are capitalized under ASU 2018-15, using the same rules you'd use for internal-use software.
Which implementation costs can you capitalize?
ASU 2018-15 tells you to look at each cost as if you were implementing internal-use software. Under the current model (before ASU 2025-06, more on that below), that means sorting costs by project stage:
Application development work
Capitalize
- Configuring the system for your processes
- Coding integrations and interfaces (bank feeds, e-commerce, CRM, payroll)
- Customizations: reports, workflows, scripts
- Testing, including parallel runs
- Partner fees for that work
- Payroll for employees directly working on it, for the time they spend
Everything around it
Expense as incurred
- Vendor selection, demos and requirements gathering
- Training your team
- Cleaning and converting old data
- General project management and overhead
- Post go-live support and fixes
- The subscription fee itself
The two that trip people up are training and data conversion. They're expensed whenever they happen, even if they fall in the middle of the build. Training is never capitalized. Data conversion is expensed too, with one narrow exception: software you develop or buy specifically to move old data into the new system can qualify. Paying staff to clean up the customer list doesn't.
Watch the partner's statement of work. A single "implementation services" fee usually covers several of these buckets. Ask the partner to split hours by activity, or you'll have nothing to support the split your reviewer asks for.
A worked example: a distributor moves to a cloud ERP
Say you run a 60-person wholesale distributor. You sign a three-year cloud ERP subscription with a two-year renewal option, and you're reasonably certain you'll renew because you'd never rip out the system after three years. So the hosting term for accounting is five years. The project costs:
| Cost | Amount | Treatment |
|---|---|---|
| Vendor selection and demos | $15,000 | Expense |
| Partner configuration and setup | $120,000 | Capitalize |
| Integrations (e-commerce, bank, payroll) | $45,000 | Capitalize |
| Testing and parallel runs | $20,000 | Capitalize |
| Internal staff time on configuration and testing | $31,000 | Capitalize |
| Data cleanup and conversion | $25,000 | Expense |
| Training | $18,000 | Expense |
| Post go-live support (first 60 days) | $12,000 | Expense |
| Total project cost | $286,000 | $216,000 capitalized, $70,000 expensed |
From total project cost to the capitalized asset
Cloud ERP implementation, wholesale distributor
- Increase
- Expensed
- Total
Hypothetical example. The $96,000 annual subscription is expensed separately and isn't included.
Show the numbers
| Total project cost | $286,000 |
| Vendor selection | −$15,000 |
| Data conversion | −$25,000 |
| Training | −$18,000 |
| Go-live support | −$12,000 |
| Capitalized asset | $216,000 |
The $216,000 is amortized straight-line over 60 months from go-live: $3,600 a month, or $43,200 a year. Meanwhile the $96,000 subscription is expensed at $8,000 a month as usual.
Capitalized implementation costs left on the balance sheet
Balance at the end of each year after go-live
Hypothetical example: $216,000 amortized at $43,200 a year over a five-year hosting term.
Show the numbers
| Unamortized balance | |
|---|---|
| Go-live | $216,000 |
| Year 1 | $172,800 |
| Year 2 | $129,600 |
| Year 3 | $86,400 |
| Year 4 | $43,200 |
| Year 5 | $0 |
In the implementation year, profit is up to $216,000 higher than if you'd expensed everything (less whatever amortization falls in that year). That's not a trick. It matches the cost to the five years you'll use the system, which is the whole point.
How long do you amortize, and when do you start?
The amortization period is the hosting arrangement's term: the noncancellable period, plus renewal periods you're reasonably certain to exercise, plus any renewals the vendor controls. If you have a termination option, the term ends where you could walk away without a meaningful penalty. If you've used ASC 842 for leases, the "reasonably certain" test will feel familiar.
Amortization starts when the module or component is ready for its intended use, even if other modules are still being built. If finance goes live in March and warehouse management in July, the finance module's costs start amortizing in March.
Reassess the term when facts change. Decide to replace the ERP in year three, and the remaining balance has to be expensed over the shorter period. Capitalized costs are also tested for impairment as if they were long-lived assets, so an abandoned project or module gets written off.
Where do the costs show up in your financial statements?
This is the part most small companies get wrong, even when they capitalize correctly. ASU 2018-15 says the capitalized costs follow the subscription fee, not your fixed assets:
| Statement | Where capitalized implementation costs go | Where they don't go |
|---|---|---|
| Balance sheet | Same line as prepaid hosting fees (prepaid expenses or other assets, split current and noncurrent) | Property and equipment, or intangible assets |
| Income statement | Amortization in the same line as the subscription fee (software or IT expense in operating expenses) | Depreciation and amortization |
| Cash flow statement | Payments in the same category as subscription payments, normally operating activities | Investing activities (capital expenditures) |
In the example, at go-live the balance sheet shows $43,200 as a current prepaid and $172,800 as noncurrent.
One consequence owners don't expect: because the amortization lands in operating expenses rather than the amortization line, it reduces EBITDA. If your bank covenant or a buyer's valuation uses EBITDA, a cloud ERP costs you about $43,200 of EBITDA a year in this example, where an on-premises license would have been added back. Know which number your lender uses before the covenant test, not after. Our EBITDA calculator shows the effect.
What changes with ASU 2025-06?
ASU 2025-06 rewrites the capitalization trigger in ASC 350-40. It drops the project stages and replaces them with a threshold: you capitalize once management has authorized and committed to funding the project and it's probable the project will be completed and used as intended. It's effective for fiscal years beginning after December 15, 2027 (calendar 2028 for most companies), and you can adopt it early.
Because cloud implementation costs follow ASC 350-40's capitalization rules, the trigger changes for them too. For a typical ERP rollout using the vendor's existing product, Forvis Mazars notes the probable-to-complete threshold may be met without a long analysis of development uncertainty. The cost types don't change: training is still expensed, and the presentation rules above stay as they are.
We've covered the new model in detail in our post on ASU 2025-06 and internal-use software, so we won't repeat it here.
Common mistakes
Expensing the whole implementation. It's the default in many small company books, and it buries a real asset. Your statements show a terrible implementation year and flattering years after.
Booking it as a fixed asset. The opposite error. The costs sit in prepaid or other assets, and the expense sits next to the subscription fee, not in depreciation.
Capitalizing training and data cleanup. They're often the biggest line on the partner's invoice, and they're always expensed.
Using the noncancellable term only. A three-year contract you'll obviously renew for five gets amortized too fast.
Starting amortization at signing. Start when the module is ready for its intended use, not when the contract or the first invoice arrives.
No support for the split. If the partner bills one lump sum, ask for hours by activity before the work starts. Reconstructing it later is painful.
When should you get help?
If your books are tax-basis or cash-basis only, and no lender or investor reads GAAP statements, the capitalization question may not matter much for you. Your CPA will handle the tax treatment, which follows its own rules.
It matters when you issue GAAP statements, when a lender tests covenants on EBITDA, or when you're preparing for a sale and a buyer will scrutinize the quality of earnings. Get the policy, the cost split and the amortization schedule set up before go-live, while the invoices are fresh. Monthly schedules for long-lived assets and a reviewed close every month are part of the accounting service at Fintrix Consulting; the capitalization policy itself is one for your CPA or auditor to sign off.
Frequently asked questions
Can I capitalize my cloud software subscription?
No. If the arrangement is a service contract, the subscription fee is an operating expense recognized as you receive the service. Only qualifying implementation costs are capitalized under ASU 2018-15.
Is training ever capitalized?
No. Training costs are expensed as incurred, whatever stage of the project they fall in. The same goes for most data cleanup and conversion work.
What amortization period should I use?
The term of the hosting arrangement: the noncancellable period plus renewals you're reasonably certain to take and renewals the vendor controls. Use straight-line unless another pattern clearly fits better.
Do capitalized cloud implementation costs count in depreciation and amortization?
No. The amortization goes in the same income statement line as the hosting fee, usually operating expenses. That's why it reduces EBITDA, unlike amortization of a software license.
Does ASU 2025-06 change which costs I can capitalize?
It changes when capitalization starts, replacing the project stages with a probable-to-complete threshold, effective for fiscal years beginning after December 15, 2027. It doesn't make training or the subscription fee capitalizable.
The bottom line
A cloud ERP subscription is an expense, but the work to set it up often isn't. Capitalize configuration, integration, coding and testing; expense planning, training, data conversion and support. Put the asset with your prepaid expenses, amortize it over the realistic subscription term from go-live, and keep the expense next to the subscription fee. Split the partner's bill by activity before the project starts, and the year-end entry takes an hour instead of a week.
Sources
- Defining Issues 18-19: FASB clarifies accounting for cloud computing implementation costs (KPMG)
- Handbook: Software and website costs (KPMG)
- New accounting guidance regarding cloud computing arrangements (BNN)
- FASB's improvements to accounting for internal-use software (Forvis Mazars)
- ASU 2025-06 (Eide Bailly)
- Improvements to accounting for internal-use software (Grant Thornton)
This article is general information, not advice for your situation. Rules change and details matter, so talk to us or your CPA before acting on it.
More articles
- Found a mistake in last year's books? Errors vs changes in estimate
November 18, 2026
- Buying a business: the ASC 805 accounting checklist
November 18, 2026
- CECL isn't just for banks: the bad-debt allowance for your receivables
November 18, 2026
Have a question about this article?
Ask us. A real person will reply by email within one business day. Your question isn’t published.
Ready for books you can trust?
Book a free 30-minute consultation. We'll review where your finances stand today and show you exactly how we'd help.