Accounting for Software Development Costs

Code into Capital: The Definitive Guide to Accounting for Software Development Costs

In the digital age, software is no longer just a tool; for many businesses, it is the business. Whether you are a SaaS startup in Dubai Internet City building the next unicorn, a bank in Abu Dhabi developing a proprietary trading algorithm, or a retail giant launching a new e-commerce app, you are investing millions in code. But here is the critical question that keeps CFOs awake at night: Is that code an expense that burns your profit today, or is it an asset that builds your balance sheet for tomorrow?

The answer determines your profitability, your tax liability, your valuation, and your ability to raise capital. Accounting for software development is one of the most complex, nuanced, and high-stakes areas of modern finance. It sits at the intersection of rigid accounting standards (IFRS) and fluid, agile engineering methodologies.

Get it wrong, and you could either massively overstate your profits (inviting auditor wrath and tax penalties) or massively understate your assets (scaring away investors). In the UAE, with the new Corporate Tax regime relying on accurate financial statements, this distinction is now a matter of legal compliance.

This guide is the definitive manual for UAE business leaders. We will strip away the accounting jargon to reveal the strategic logic of IAS 38 (Intangible Assets). We will explore the “Capitalization vs. Expense” debate, how to handle Agile development, the specific rules for Cloud Computing, and how to build the internal controls necessary to turn your code into capital.

The Core Conflict: Expense vs. Capitalize

Before diving into the rules, we must understand the stakes. Every dirham you spend on a developer’s salary can go one of two ways in your books:

Option A: Expense It (The Income Statement)

You treat the salary as a cost of doing business, just like rent or electricity.
Impact:

• Profit: Lowers your Net Profit immediately.
• Tax: Lowers your Taxable Income immediately (you pay less tax now).
• Assets: No asset is created on the Balance Sheet.
• EBITDA: Lowers your EBITDA.

Option B: Capitalize It (The Balance Sheet)

You treat the salary as an investment in creating an asset (Intangible Asset: Software).
Impact:

• Profit: Increases your Net Profit immediately (because the cost is removed from the P&L).
• Tax: Increases your Taxable Income immediately (you pay more tax now).
• Assets: Adds a valuable asset to your Balance Sheet, increasing your Net Worth.
• Future Impact: The cost is slowly released to the P&L over 3-5 years via “Amortization.”

The Strategic Choice: A startup looking for investors usually wants to Capitalize to show higher assets and EBITDA. A profitable mature company might prefer to Expense to lower their tax bill. However, under IFRS, this is not a choice. It is a rule-based determination.

The Regulatory Framework: IAS 38 (Intangible Assets)

In the UAE, businesses generally follow International Financial Reporting Standards (IFRS). The relevant standard for software is IAS 38. This standard divides the life of a software project into two distinct phases:

Phase 1: The Research Phase (Always Expense)

This is the “idea” stage. It includes:

• Brainstorming and conceptualization.
• Evaluating different technologies.
• Market research and feasibility studies.
• Searching for alternatives.

The Rule: You cannot capitalize research. Why? Because there is no certainty that an asset will ever be created. All costs in this phase must be expensed as incurred.

Phase 2: The Development Phase (Capitalize if…)

This is the “building” stage. It includes:

• Coding and programming.
• Designing the user interface (UI/UX).
• Testing and debugging (before launch).
• Building the technical infrastructure.

The Rule: You *must* capitalize these costs, BUT only if the project meets the 6 Strict Criteria of IAS 38.

The 6 Criteria for Capitalization (The “PIRATE” Criteria)

To move a cost from the P&L to the Balance Sheet, you must prove all six:

1. Technical Feasibility: Can we actually build this? (Proven by a prototype or technical plan).
2. Intention: Do we intend to complete it? (Proven by board minutes or budget approval).
3. Ability: Can we use it or sell it? (Is there a market or internal use?).
4. Resources: Do we have the money and people to finish it? (Proven by cash flow forecasts).
5. Future Economic Benefits: Will it make money or save money? (Proven by a financial model).
6. Measurement: Can we reliably track the costs? (Proven by timesheets and project accounting).

If you fail even one of these, you must expense the cost. This is why a robust accounting system is vital—to prove criterion #6 (Measurement).

Phase 3: The Post-Implementation Phase (Expense)

Once the software is “ready for use” (launched), capitalization stops.

• Training staff to use it: Expense.
• Routine maintenance and bug fixes: Expense.
• Marketing the software: Expense.
• Major Upgrades (Version 2.0): Capitalize (if they add new functionality).

The Modern Challenge: Agile Development & DevOps

IAS 38 was written in an era of “Waterfall” development (where you design, then build, then launch). Modern software uses “Agile” (continuous iteration, sprints, CI/CD). This makes accounting difficult.

The Problem with Agile

In a two-week sprint, a developer might spend 2 days fixing a bug (Maintenance – Expense), 3 days researching a new idea (Research – Expense), and 5 days coding a new feature (Development – Capitalize). How do you account for their salary?

The Solution: Task-Based Time Tracking

You cannot just capitalize 50% of the engineering department. You need a granular tracking system.
The Workflow: 1. Developers log time in Jira/Asana/Monday.com. 2. Each “Ticket” or “Task” is tagged: “New Feature,” “Bug Fix,” “Research,” or “Maintenance.” 3. At month-end, the finance team exports the time logs. 4. Calculate: `(Hours on “New Feature” / Total Hours) * Salary`. 5. Capitalize that specific amount.

Without this level of detail, an auditor (or the FTA) will likely reject your capitalization and force you to expense everything, crushing your net profit.

Special Case: Cloud Computing & SaaS (IFRIC Agenda Decision)

What if you aren’t building software to sell, but buying/implementing a cloud ERP like SAP, Oracle, or Zoho? Can you capitalize the implementation costs (consultants, configuration)?

This changed recently. The IFRS Interpretations Committee (IFRIC) issued a decision that makes capitalizing cloud implementation much harder.
The Rule: If you do not control the underlying code (which is true for SaaS), implementation costs are generally treated as a service contract and Expensed as incurred.
The Exception: You can still capitalize code that you *own* and *control*, such as a custom API bridge or an on-premise module that talks to the cloud.

The Life of the Asset: Amortization and Impairment

Once you capitalize the software, it sits on your Balance Sheet as an Intangible Asset. But it doesn’t stay there forever.

Amortization (The Slow Expense)

You must expense the asset over its “Useful Life.” For software, technology moves fast, so useful life is typically short (3 to 5 years).
Example: You spent AED 1.2M building an app. Useful life is 3 years.
Entry: Every month, you record an Amortization Expense of AED 33,333 (`1.2M / 36 months`). This gradually moves the cost from the Balance Sheet to the P&L.

Impairment (The Reality Check)

What if the software fails? What if a competitor launches something better, and your app becomes obsolete in Year 1?
The Rule: You must test for “Impairment.” If the software’s value (future cash flows) is less than its Book Value (what’s on the Balance Sheet), you must write it down immediately. This is a massive “one-time hit” to your profit.

The UAE Tax Context: Why This Matters Now

Before Corporate Tax, this was mostly about valuation. Now, it’s about cash tax payments.

The Tax Trade-Off

• Aggressive Capitalization: You capitalize AED 1M of salaries.
  Result: Your P&L expenses are lower. Your Profit is higher. Your Tax Bill is Higher.
• Aggressive Expensing: You expense AED 1M of salaries.
  Result: Your P&L expenses are higher. Your Profit is lower. Your Tax Bill is Lower.

The Trap: You might be tempted to expense everything to save tax. But if you are a startup planning an exit, you want to capitalize to show higher EBITDA. Also, the FTA requires you to follow accounting standards. If you expense something that *should* be capitalized (just to save tax), that is tax evasion. You need a Corporate Tax advisor to navigate this line.