Internal-Use Software - Capitalization During Application Development Stage (ASC 350-40)
Capitalizing the direct costs of developing the startup's core SaaS platform — programmer salaries, cloud architecture design, and directly attributable costs — after the preliminary project stage and during the application development phase.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Internal-Use Software - Capitalized Development Costs (Intangible Asset) | Asset (+) | 285,000.00 | - |
| Salaries Payable / Cash (Capitalizable Engineer Salaries) | Liability (+) / Asset (-) | - | 285,000.00 |
💡 Accountant's Note
ASC 350-40 applies to software developed for internal use (including SaaS platforms where the software is NOT sold, but the access to it is licensed). Three stages: (1) PRELIMINARY PROJECT STAGE: feasibility determination, conceptual formulation — ALL COSTS EXPENSED; (2) APPLICATION DEVELOPMENT STAGE: designing the chosen path, coding, testing — CAPITALIZE direct costs; (3) POST-IMPLEMENTATION/OPERATION: training, maintenance — ALL COSTS EXPENSED. For a SaaS startup: once the engineering team commits to building a specific feature or product and moves from 'should we build X?' to 'we are building X,' capitalization begins. The capitalized amount includes: direct coding labor + directly attributable overhead. Indirect overhead, G&A, and training are excluded.
Practitioner & Systems Framework
💻 ERP Architecture
Many early-stage startups elect to expense ALL software development costs (treating all engineering as R&D) rather than going through the phase determination process. This is simpler and acceptable under GAAP (it is conservative). However, Series B+ companies with auditors increasingly face pressure to capitalize software development if material. The decision affects: P&L (capitalization reduces current expense), balance sheet (intangible asset appears), and future amortization (creates expense in later periods).
⚠️ Audit Flags
Auditors verify: (1) The preliminary vs. application development stage boundary is properly documented (when did the team commit to building?), (2) Only direct costs are capitalized (no allocation of C-suite salaries), (3) The capitalized amount is reasonable relative to the engineering hours spent on post-feasibility development, (4) Amortization has begun once the software is placed in service (typically when first deployed to production customers).
📄 Required Documentation
Project approval documentation (committing to build), time tracking records for engineers by project and phase, application development stage start date, capitalization policy, amortization period determination (typically 2–5 years for SaaS software), post-implementation date documentation.
Professional Excel Template
Get the automated version of this entry. Includes built-in IFRS checks, VAT calculators, and SAP-ready upload formats.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.