Internal-Use Software — Preliminary Project Stage (All Costs Expensed)
Expensing all costs incurred during the preliminary project stage of internal-use software development — before management commits to the project and technological feasibility is established.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| R&D / Technology Expense — Preliminary Stage (Software Evaluation) | Expense (+) | 850,000.00 | - |
| Salaries Payable / Cash (Engineer Time — Pre-Feasibility) | Liability (+) / Asset (-) | - | 850,000.00 |
💡 Accountant's Note
Under ASC 350-40, internal-use software development follows a three-stage model with dramatically different accounting at each stage. PRELIMINARY PROJECT STAGE (expense all costs): conceptual formulation, evaluation of alternatives, determination of existence of needed technology, final selection of alternatives. This stage includes: evaluating cloud platforms (AWS vs. Azure vs. GCP for a new system), reviewing competing software packages, proof-of-concept prototypes, feasibility studies. For a technology company building its own internal data platform: all costs before the engineering team commits to a specific architecture and begins detailed design are expensed. This stage ends when management AUTHORIZES AND COMMITS RESOURCES to developing a specific software solution. Duration: weeks to months depending on complexity.
Practitioner & Systems Framework
💻 ERP Architecture
Time tracking is essential — developers must code their time to preliminary vs. application development project codes. Many technology companies have formal 'project kickoff' documents that mark the transition from preliminary to application development. Without this documentation, auditors cannot verify the stage boundary. For agile development: the preliminary stage corresponds to 'discovery' sprints before the team commits to the project's build phase.
⚠️ Audit Flags
The preliminary vs. application development boundary is the most commonly incorrect assumption in software capitalization. Companies often capitalize costs from the very beginning of a project — before management has committed — overstating intangible assets. Auditors test the management authorization documentation at the claimed start of capitalization. 'Management commitment' requires actual resource allocation and approval of a build plan — not just a decision to explore the project.
📄 Required Documentation
Project authorization documentation (management sign-off, budget approval, resource allocation), project timeline with stage boundary identification, developer time tracking records by stage, time-coding policy documentation, and preliminary stage cost summary by project.
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.
Related Journal Entries
Technology (Hardware, Software & Platforms)
Hardware + Embedded Software Bundle — Distinct vs. Not Distinct Performance Obligation Analysis
Technology (Hardware, Software & Platforms)
Hardware + Future Software Updates + Services Bundle (Apple iPhone Revenue Model)
Technology (Hardware, Software & Platforms)