FASB Brings Clarity to Internal-Use Software Accounting

For years, accountants have been stuck in a war over a deceptively simple question: when a company builds or customizes its own software, what counts as a capitalizable asset and what gets expensed? Think of it like trying to play Monopoly with missing rules; every CFO, controller, and auditor had their own interpretation. The Financial Accounting Standards Board (FASB) has issued a new “software patch” to address the issue. Enter ASU 2025-06, a targeted update to ASC 350-40 that modernizes internal-use software accounting. And this one’s a big deal.

No More Playing Hopscotch with Stages

Old GAAP required firms to track software costs by rigid project stages: planning, development, and implementation. That sounded neat on paper, but in the real world of agile and iterative builds, those lines got blurry fast. The new standard scraps the stage-by-stage hopscotch. Now, costs can be capitalized once two conditions are met:

• Management has approved and committed to funding the project.
• It’s probable that the project will be completed, and the software will work as intended.

In other words, once leadership signs the check and there’s a clear path forward, those costs hit the balance sheet. No more endless debates over whether coding belongs in Stage A or Stage B.

Cutting Through the Noise

Here’s the new litmus test: if there’s significant development uncertainty, costs stay off the books until that risk is resolved. FASB narrowed this down to just two scenarios:

• Unproven tech: Software with novel or untested features that haven’t cleared coding and testing.
• Undefined performance: Projects where the core functions or requirements are still fuzzy or constantly changing.

“Probable” now officially means “likely to occur,” giving auditors and preparers a more concrete threshold. As Allison Henry of the Pennsylvania Institute of CPAs put it, “Moving from rigid stages to a probability-based approach is a positive step, but auditors will face a challenge in evaluating management’s judgment calls.”

One Rulebook for All

Another headache FASB cleared up: website development costs. These used to sit in their own quirky bucket under separate guidance. Now, they’re folded into the same internal-use software rules. Whether it’s an ERP system, a proprietary AI platform, or a website revamp, the recognition framework is unified. Disclosures also get streamlined. Instead of special reporting rules, firms just follow the property, plant, and equipment (PP&E) model for all capitalised internal-use software. Simple, consistent, and no extra busywork.

From ERP to AI

Picture a multinational rolling out a new ERP system. Before, tailoring modules for internal workflows was murky, some capitalized, others expensed. Now, if the customization directly enhances functionality, it goes on the balance sheet. Or think about a financial services firm developing a proprietary AI tool. Previously, deciding which coding and testing costs counted was subjective. Now, research costs are expensed, but work that creates usable features gets capitalised. Less wrangling, more clarity.

Ben Wempe of Armanino LLP flagged where the next wave of challenges may land: AI. “A lot of AI development involves trainers, not just engineers, and much of that isn’t currently recognized as an asset because refining an AI model is often like fixing bugs,” he noted. The debate isn’t over, but the new framework is a strong start. The new standard kicks in for fiscal years starting after December 15, 2027 (a year later than earlier drafts suggested), with early adoption allowed. Companies can choose between prospective, retroactive, or a modified approach to transition.

No More Fire Drills

Here’s what this update means in plain terms for professionals on the front lines:

• Controllers: No more late-night battles deciding whether coding tweaks are capitalized or expensed. The rules now offer a straighter line from cost to classification.
• Auditors: Instead of acting as referees in boardroom showdowns, they’ll lean on a clearer framework that reduces judgment calls and audit disputes.
• CFOs: Gain better apples-to-apples comparability when benchmarking technology investments across industries, helping them present cleaner stories to boards and investors.
• Tax Professionals: Deferred tax calculations get smoother thanks to a more predictable baseline for capitalized costs.
• Analysts & Investors: With clearer reporting, they’ll get a more reliable read on whether billion-dollar ERP rollouts or AI investments are building long-term value.

In short: fewer grey areas, fewer disputes, and way more trust in the numbers.

A Win for Clarity

FASB doesn’t always hand out easy wins. But this one feels different. By cutting out clutter, aligning disclosures with PP&E, and addressing modern development methods, the board delivered clarity without unnecessary complexity. As one CFO quipped, “It feels less like a new rulebook and more like someone finally turned the lights on in the room.” For accountants, auditors, and analysts, that light means less arguing and more consistency. For investors, it means clearer insight into where tech dollars are actually building long-term value. Accounting evolves best when standards catch up to business reality. With ASU 2025-06, FASB finally caught up to the way companies actually build software. And that’s not just an update, it’s a revolution.