AI Can Read Every Contract in Your Revenue Recognition Queue. It Still Can't Make the ASC 606 Call.

AI can read every contract in your revenue recognition queue faster than your best senior accountant could read one of them, and that's simply what large language models are genuinely good at, no hype required. What it still can't do is decide whether two promises in a bundled contract are distinct performance obligations or one combined obligation, because that call depends on judgment about the customer relationship and the deal's intent, not on pattern-matching language across a thousand contracts. ASC 606 was built as a five-step judgment framework on purpose, and the judgment part is exactly the part that doesn't automate away just because the reading got faster.

What the five steps actually ask of you

Identify the contract, identify the performance obligations, determine the transaction price, allocate that price across the obligations based on standalone selling price, and recognize revenue as each obligation gets satisfied. Say it fast and it sounds mechanical. It isn't. Deciding whether a service and a software license are "distinct" or need to be combined is a judgment call. Estimating variable consideration, like a rebate or a performance bonus that might or might not hit, is a judgment call. Figuring out standalone selling price when you don't sell that component on its own is, again, a judgment call, usually backed by an estimate you have to be ready to defend. Every one of those steps has a mechanical part, extracting the terms, doing the math, and a judgment part, deciding what the terms actually mean for this specific deal. AI is genuinely great at the first part and shouldn't be trusted alone with the second.

Where AI already earns its keep

Contract abstraction is the unglamorous grind at the front of every revenue recognition close, someone has to read the master service agreement, the order form, and the three amendments, and pull out the term, the renewal language, the discount structure, and every clause that might affect the numbers. It's the same pattern we found writing about AI earning its keep on journal entry review: the grunt work shrinks, the judgment work doesn't. A 2025 industry report from CPA.com's AI in Accounting research found LLM-based tools cutting document analysis time by 50 percent or more in audit and advisory work, and revenue recognition contract review is exactly the kind of document-heavy task that stat describes. Hand the model the contract stack and ask it to flag every non-standard clause, every embedded lease, every "material right" hiding in a renewal option, and you get a first pass in minutes that used to eat an afternoon. That's a real gift back to your close calendar, and there's no reason to feel weird about taking it.

Where it doesn't get to make the call

Here's where I'll push back on my own point a little, because even the companies building AI products are running into ASC 606's judgment wall on their own revenue. Deloitte's DART published a technology spotlight in June 2026 on how agentic AI SaaS vendors should account for their own subscription revenue, and the core question is whether the vendor's promise is a stand-ready obligation to provide continuous access to the agent, or an obligation to deliver a specific, successful outcome. That's a judgment-under-uncertainty call, the exact same kind your team makes every close, just applied to the AI vendor's own books instead of yours. If the people selling the automation still need a human to make that call on their own books, that should damn well tell you something about handing the same call to their tool without a review layer on yours.

The audit trail is the part people skip

The failure mode I'd actually worry about isn't the AI getting a judgment call wrong, it's a team moving fast enough that nobody documents why the human agreed with what the model suggested. Auditors don't just want the conclusion, they want to see the reasoning, the alternatives considered, the basis for the standalone selling price estimate. If your contract abstraction tool spits out a recommendation and someone rubber-stamps it into the workpaper without writing down why, that's a bullshit trade, you've swapped a slow process for a fast one that's harder to defend under review. That's a fixable problem, and it's honestly one of the more solvable parts of adopting AI in the close, the same discipline we pushed on in our piece about keeping SOX controls intact while AI touches the close, but it takes someone deciding the documentation step isn't optional just because the first-pass work got faster.

What I'd do

I'd run every new contract and amendment through an AI-assisted abstraction pass first, no debate, hell, there's no upside left to a human reading that stack manually when the time savings are this real. If your current revenue recognition tooling can't do that yet, it's worth a look at what's out there in our accounting software directory. I'd keep a human, ideally someone senior enough to have made a few of these calls before, reviewing every performance obligation determination, every SSP estimate, and every variable consideration judgment before it hits the workpapers, and I'd make writing down the "why" a required field, not an afterthought. And I'd watch which of your close-team folks get good at working this way, because six months from now that's the skill set that's going to be worth the most, and it's exactly the kind of accountant we see more employers actively hunting for in senior accountant roles built around close and technical accounting work.

Frequently asked questions

Can AI actually apply ASC 606 correctly on its own?

It can extract contract terms and flag issues accurately, which is most of the mechanical work. It shouldn't independently decide performance obligation distinctness, standalone selling price, or variable consideration estimates, those need a human who can defend the judgment.

What part of revenue recognition should AI handle first?

Contract abstraction: reading agreements, order forms, and amendments to pull out terms, renewal language, and non-standard clauses. It's the highest-volume, most mechanical part of the process and the part with the clearest time savings.

Does using AI for contract review create audit risk?

Only if the documentation trail disappears. Auditors want the reasoning behind a judgment call, not just the conclusion, so the discipline of writing down why a determination was made matters more, not less, once AI speeds up the first pass.

What's the actual five-step ASC 606 model?

Identify the contract, identify the performance obligations, determine the transaction price, allocate the price to each obligation based on standalone selling price, and recognize revenue as each obligation is satisfied.

Where can I read the actual FASB standard?

The Codification lives at FASB's ASC Codification under Topic 606, and the original standard-setting update, ASU 2014-09, is publicly available without a login.

Build the review layer at the same time you build the speed, and you get both: a faster close and a defensible one. The teams that figure out how to move fast on abstraction while staying careful on judgment are going to pull ahead of everyone still doing this by hand, and that combination is worth building toward now, before someone else proves it out first.