By Glenn Hopper ·
Your AI Project Code Won't Settle the Accounting

An invoice labeled "AI implementation" arrives just before close, covering a prototype, production integration, employee training and the first year of a hosted service. Procurement has the signed contract, IT has the project plan, and Finance has one line in the ledger. Someone suggests capitalizing the implementation because the system should deliver benefits for years. The controller still needs to establish what the company bought, which work was performed and when it qualified for the proposed treatment. Nobody gets into finance for the pleasure of asking a vendor what "enablement" means, but somebody has to.
For a U.S. GAAP reporter that hasn't early adopted the amendment, the existing internal-use software model still distinguishes preliminary activities from application development. Capitalization of eligible costs begins after the preliminary stage is complete, management commits funding, and completion and intended use are probable. FASB's ASU 2025-06 removes the stage references and expressly evaluates significant development uncertainty. It generally applies to annual periods beginning after December 15, 2027, including interim periods within those years, with early adoption permitted from the beginning of an annual reporting period. Finance needs to establish its adoption status before borrowing a rule from a presentation about the update.
Under the amendment, funding authorization and probable completion remain requirements. Unresolved novel functionality or significant requirements that are still being determined or substantially revised can prevent capitalization from starting. A demo that produces an attractive reconciliation explanation won't establish whether the intended system can reliably retrieve evidence, enforce access rights and support the review process. Those are questions for the project team and controller to resolve against the agreed requirements. FASB also explicitly declined to resolve AI-specific development questions, including model-training costs, in this update. Employee training and training a model need separate analysis; the shared word doesn't settle either treatment.
Cloud arrangements need their own assessment. ASU 2018-15 already requires customers in hosting arrangements that are service contracts to assess implementation costs under the internal-use software guidance. Qualifying costs can be deferred, while the hosting service retains its service accounting. Employee training and certain data-conversion activities are expensed, and deferred implementation costs are recognized over the applicable hosting term. That makes the contract and its components useful evidence. A vendor's bundle can combine several activities, and Finance needs support for separating them before applying the relevant accounting policy. The result won't necessarily be a software intangible simply because the project team calls it a platform.
If your company is building a reconciliation assistant, start a cost record while the work is happening. Give each work package an owner and connect invoices and employee time to specific activities: evaluating options, designing interfaces, developing software, testing, converting records or teaching staff to use the finished workflow. Capture dates, deliverables and the basis for allocating mixed charges. Ask vendors for that detail in the SOW and invoice, and agree with Engineering on how internal time will be recorded. The controller can then document the applicable guidance, the capitalization start date and supporting evidence, along with the point at which the software or component is ready for intended use. An approved budget supports the funding decision; it doesn't explain every hour charged against it.
AI could help assemble this record by extracting proposed activity descriptions from approved contracts, tickets, time records and invoices, linking each field to its source. The reviewer should see the underlying wording and date, along with unresolved questions and conflicting records. If the invoice says configuration and the ticket describes exploring three approaches, flag the difference for the people who know what happened. Keep the accounting approval with Finance, and apply its approved rules through controlled calculations and workflows. The agent harness should preserve the evidence and reviewer decisions, including corrections to the assistant's proposed classifications.
Keep the investment case connected to the cash spent across the whole project. Deferring eligible costs changes when expense is recognized; it doesn't reduce the supplier payment or recover the team's time. For a PE operating team comparing portfolio-company projects, a larger capitalized balance also doesn't establish stronger operating performance. Show implementation spending, ongoing service charges, maintenance and review effort alongside the benefits being measured, using consistent definitions. The cost per accepted finance output can help explain what the workflow costs to run after launch. The controller's accounting conclusion and management's investment decision should each have enough support to stand on their own.
Before next quarter's AI projects begin, Finance can update SOW templates, project codes and time-record instructions so the supporting detail arrives before close. Build the first example with the controller, engineering lead and procurement owner, then use it to show vendors and internal teams what a usable cost record looks like. Keep model training, fine-tuning and ambiguous service charges visible for specific analysis instead of forcing them into a convenient category. When requirements change or work stops, bring that information back into the review. Next month's controller should be able to follow what happened without reconstructing the project from somebody's calendar.