The buy-side Quality of Earnings auditor is trying to reclassify our software development team's salaries from capital expenditures back to operating expenses, which slashes our reported EBITDA by several hundred thousand dollars. How do we defend our capitalization policy and protect our enterprise value?

Question

Tyler Smith · Accepted Answer

This is a high-stakes battle because every dollar reclassified from CapEx to OpEx reduces your EBITDA, which is then multiplied by your transaction multiple, costing you millions at the closing table. To win this, you must back up your accounting with detailed operational documentation.

Auditors will try to claim that software development was merely routine maintenance, which must be expensed as an operating cost. To defeat this claim, pull your software engineering team's task-tracking records, sprint history, and project roadmaps. Cross-reference these engineering sprints with your quarterly EOS Rocks and annual V/TO goals to prove that the team was building new, proprietary features and automated pipelines that expand your capacity, rather than fixing bugs.

Align your defense with GAAP and IVS 105 guidelines, which explicitly permit the capitalization of internal-use software development costs when they are associated with creating new capabilities. Show that these software tools cut your service delivery time, which is a clear future economic benefit.

When you present a clean trail of project-specific time allocation mapped directly to your company's strategic growth plan, the auditor will lack the technical grounds to reclassify those development salaries to OpEx.