We spent significant internal engineering hours building an AI-driven workflow engine, and our internal books capitalized these costs. The buyer's QofE auditor is trying to reclassify this as an operational expense, which slashes our EBITDA. How do we fight this?

Question

Tyler Smith · Accepted Answer

This is a classic battle in technology-driven businesses. The buy-side Quality of Earnings auditor wants to move your software development costs from the balance sheet to the income statement because reducing your EBITDA by even fifty thousand dollars can wipe out hundreds of thousands in enterprise value.

To defeat this adjustment, you must provide documented, auditable proof that your development work meets the strict criteria for capitalization under GAAP, specifically ASC 350-40 for internal-use software. You must show that the development of your AI-driven workflow engine was in the application development stage, not the preliminary project stage.

This is where your Accountability Chart and operational discipline come into play. Pull your software development logs, project management tickets, and time-tracking sheets. Show exactly which engineers worked on specific features, proving their hours were spent writing code and testing the platform, rather than performing routine maintenance or administration.

By presenting a clean audit trail that links employee hours directly to the creation of a long-term capital asset, you neutralize the auditor's argument. Frame this AI platform not as a recurring operational headache, but as a proprietary asset that drives permanent operating leverage. Proving this under GAAP keeps the capitalized costs off your income statement, protects your EBITDA, and preserves your premium multiple.