This guide is for CFOs and controllers who sign software renewals and wonder why the line keeps growing faster than revenue. It covers how per-seat SaaS reaches your P&L, when software you build for your own use can be capitalized, and what renting costs beyond the invoice.
We're engineers, and this isn't accounting advice. At Kaprin we practice forward deployed engineering (FDE): senior engineers work inside a client's team and build in the client's own cloud. Use the accounting below to prepare for a conversation with your auditor.
Why is per-seat SaaS pure operating expense, and what does it do to EBITDA?
A per-seat subscription is typically a service contract: you pay for access to software you don't control. The fee is expensed over the term, so every seat sits in operating expenses and reduces EBITDA dollar for dollar. Because the fee scales with users, each hire adds to the expense line.
Two consequences follow. Nothing lands on the balance sheet, so after three years of renewals you've paid for a service and own no asset. And the bill follows headcount. A team that doubles in size doubles its bill even if it uses the same handful of features.
We call that second effect the seat tax. Our post on the SaaS seat tax diagnostic shows how to tell whether a given vendor is worth replacing.
Can software you build for your own use be capitalized?
Sometimes. Under US GAAP (ASC 350-40) and IFRS (IAS 38), qualifying development costs for software built for internal use can be recorded as an asset and amortized over its useful life, instead of being expensed immediately. Both frameworks set criteria, and neither lets you capitalize everything.
The two frameworks reach the idea differently.
- Under IFRS (IAS 38), research-phase costs are expensed. Development-phase costs are capitalized only when the entity can demonstrate criteria such as technical feasibility, the intention and ability to complete and use the asset, probable future economic benefit, adequate resources, and the ability to measure the spend reliably.
- Under US GAAP (ASC 350-40), costs of internal-use software are capitalized once the recognition conditions are met, and the amount is then amortized. Activities such as training and ongoing maintenance are generally expensed as incurred.
Capitalization covers software you use internally. Software you sell falls under different guidance. You also have to track the spend: time records, project boundaries and a clear line between building and maintaining.
What changed in the US rules recently?
FASB issued ASU 2025-06 on 18 September 2025, as the AICPA and CIMA notes. It targets how internal-use software costs are accounted for under ASC 350-40. According to RSM's summary, it removes the project-stage model.
RSM describes the new test this way. Capitalization begins when management has authorized and committed to funding the project, and it is probable the project will be completed and the software used for its intended function. Capitalization is blocked while significant development uncertainty exists, for example unresolved technological innovation or performance requirements that are unidentified or still being substantially revised.
Per RSM, the amendments take effect for annual periods beginning after 15 December 2027, early adoption is permitted, and entities can choose a prospective, modified or retrospective transition. We haven't read the standard line by line, and your auditor should confirm which method applies to you. Treat this section as a pointer to the primary sources.
What are the hidden costs of seat-based rent?
The invoice is the visible cost. The rest sits in the contract and in daily operations. Price uplift clauses compound. Data scattered across vendors gets reconciled by hand. Switching costs weaken your position at every renewal.
Price uplift clauses
Many multi-year contracts include an annual uplift, and renewal pricing is set after you are already dependent on the tool. A modest percentage compounds, so the same seat costs noticeably more in year three than in year one without any new feature.
Fragmented data and manual reconciliation
Each vendor holds a slice of your operational data in its own schema. Finance and operations end up exporting spreadsheets and reconciling them by hand. That labor doesn't show in the software line. It appears as analyst time, month-end delay and reports that disagree.
Lock-in
The longer you rent, the more workflows and integrations get built around the vendor's model, and the more people are trained on it. Export formats vary, and rebuilding processes costs more than the license ever did. Lock-in is rarely a single clause. It accumulates, and it shows up as a weak negotiating position at renewal.
What does a three-year comparison look like?
The table below is an illustrative model with stated assumptions. It isn't a quote or a Kaprin price. The numbers are round placeholders so you can swap in your own, and the arithmetic is shown in each row.
Assumptions (placeholders, replace with your own):
| Input | Assumed value |
|---|---|
| Seats | 150 |
| Per-seat price | $100 per seat per month, so 150 x $100 x 12 = $180,000 in year 1 |
| Annual price uplift | 7%: year 2 = $180,000 x 1.07 = $192,600; year 3 = $192,600 x 1.07 = $206,082 |
| One-time build cost | $300,000, of which 80% ($240,000) assumed to qualify for capitalization |
| Annual hosting and maintenance | $60,000 per year, expensed |
| Amortization | Capitalized amount over 3 years, straight line: $240,000 / 3 = $80,000 per year |
Result (all figures in USD):
| Line | Year 1 | Year 2 | Year 3 | 3-year total |
|---|---|---|---|---|
| Rent: cash cost, equal to EBITDA and EBIT impact | 180,000 | 192,600 | 206,082 | 578,682 |
| Build: cash cost ($300,000 build in year 1, plus $60,000 per year) | 360,000 | 60,000 | 60,000 | 480,000 |
| Build: EBITDA impact (expensed $60,000 of build in year 1, plus $60,000 per year) | 120,000 | 60,000 | 60,000 | 240,000 |
| Build: EBIT impact (EBITDA impact plus $80,000 amortization) | 200,000 | 140,000 | 140,000 | 480,000 |
How to read it. On cash, renting is cheaper through year two (cumulative $372,600 against $420,000) and building is ahead by year three ($480,000 against $578,682, a gap of $98,682). On EBITDA the gap is wider ($240,000 against $578,682), but part of that is classification: capitalization moves cost below the EBITDA line. EBIT over three years equals cash for the build case.
The model leaves out migration and any overlap while you pay for both systems, internal staff time, seat growth or shrinkage, the useful life you and your auditor agree, and the risk that a build overruns. Each could move the answer in either direction. Swap in your own seat count and price to rerun the arithmetic.
Confirm with your auditor before you rely on any of this
Capitalization is a judgment your auditors must accept, and it depends on your reporting framework, your facts and the transition rules in force for your fiscal year. The statements in this article describe general principles and say nothing about your position. Before you build a business case around capitalization:
- Ask your auditor which standard applies and which transition method you would use for ASU 2025-06.
- Agree what counts as qualifying cost and what must be expensed, such as training and maintenance.
- Set up time tracking and project boundaries before work starts, since adding them afterward is much harder to defend.
- Agree the useful life and amortization method in advance.
- Check whether covenants or compensation plans define EBITDA in a way that changes the benefit.
What questions should you ask before the next SaaS renewal?
Ask these before you sign, ideally 90 days ahead, while you still have room to walk away.
- How many seats are actively used, and what share of features does each role touch?
- What is the uplift clause, and what does the price look like in year three at that rate?
- What does an exit look like: export formats, data completeness, notice periods and fees?
- Which spreadsheets and manual reconciliations exist only because this tool's data doesn't match another system?
- If headcount grows 30%, what does this contract cost?
- Could a small, owned tool replace the features you actually use, and what would it cost to build and run?
Where does Kaprin fit?
When the numbers point toward replacing a tool, we build the replacement inside your team and cloud account. You own 100% of the code, database and IP, so there is no per-seat fee. Our SaaS replacement work starts with a scoped sprint and weekly live demos, and our forward deployed engineering model is built to hand the system over by day 45. For the engineering side of the same argument, see our earlier post on the SaaS seat tax and internal software.
If you want a second pair of eyes on a renewal you're weighing, talk to us. If renting is the right answer, we'll say so.
