ASC 606
Metered pricing, resold model tokens, prepaid credits, and outcome-based agent fees collided with a standard written for fixed-price contracts. Here are the six judgment calls where finance teams actually spend their close, with the codification, the entries, and the fix for each.

By downloading you agree to hear from Hyphenate. Unsubscribe anytime.
6
judgment calls, each with a decision tree and journal entries
ASC 606
every conclusion cited to the subparagraph, not the section
2
Big-4 handbooks cross-checked for every position
100%
audit-ready: provenance and evidence on every output
The Six Questions
Each links straight into the full analysis: theory, a realistic scenario, a decision tree, and the operational fix.
A big upfront fee to fine-tune a custom model: its own deliverable, or spread over the usage term?
Billing per resolved ticket or successful action: how do you recognize revenue you only earn if the agent succeeds?
Reselling third-party model tokens and GPU compute with a markup: report the gross billing or just your margin?
Prepaid credit packs that expire: when do you recognize the credits customers never use?
Billing dates that don’t line up with month-end: do you recognize usage delivered but not yet invoiced?
Sales commissions on contracts with no committed term or volume: capitalize them, and over what period?
What’s Inside
This isn’t a summary of the standard. Each question is worked end-to-end in the same four-part structure, so you move from “what does the codification say” to “what do I book Monday” without leaving the page.
What ASC 606 actually requires, cited to the subparagraph: the recognition principle behind the question, in plain language.
A realistic AI-native contract with real numbers: the exact fact pattern that makes the call ambiguous in the first place.
The if/then logic your auditor will walk: which facts flip the answer, and where the judgment actually lives.
The fix: illustrative journal entries, the true-up mechanics, and how to keep the position audit-ready every close.
Where to Focus
Each question plotted on financial impact and operational effort; bubble size shows roughly how many metered, AI-native companies actually run into it. Cutoff and gross-versus-net touch nearly everyone; outcome-based pricing is far rarer today but carries the highest financial stakes.
Lower priority
HIGHER
Bubble size = share of companies affected
Fine-Tuning, Custom Models & Setup Fees ~45%
Outcome-Based & Agentic Pricing ~35%
Principal vs. Agent: Gross vs. Net ~80%
Prepaid Credits & Breakage ~65%
Period-End Unbilled Usage & Cutoff ~90%
Costs to Obtain a Contract ~55%
Prevalence figures are directional Hyphenate estimates for metered AI-native companies, not survey data. Read them as relative frequency.
Sources & Precision
Every reference points to the specific subparagraph that carries the conclusion, cross-checked against two Big-4 handbooks. Where a call is fact-dependent, the guide says so rather than overstate certainty.
The complete playbook: every question with codification references, journal entries, decision trees, and the operational fix.
All six questions, fully worked
Illustrative journal entries and true-ups
Cross-checked against 2 Big-4 handbooks

Talk to Hyphenate
Book a 60-minute Finance Transformation Audit. We’ll map your usage-based contracts to the right ASC 606 treatment, live.
Book a Call