Accounting Standards
ASC 606 and IFRS 15 Revenue Recognition for Underwriters
ASC 606 and IFRS 15 require revenue to be recognized when control of promised goods or services transfers to the customer, in an amount reflecting the consideration expected. The five steps are: identify the contract, identify performance obligations, determine the price, allocate it, and recognize revenue as obligations are satisfied. Judgment in each step can shift revenue between periods.
What do ASC 606 and IFRS 15 require?
ASC 606 under US GAAP and IFRS 15 under international standards share a single principle: recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the company expects to be entitled to. The standards replaced a patchwork of industry-specific rules with one framework that applies across industries. The two are substantially converged, although some differences remain in areas such as collectability thresholds, licensing and certain practical expedients. Disclosures under both standards are extensive and are often the best source of insight.
For underwriters, the importance of these standards is that revenue is the starting point for nearly every valuation and credit metric. Two companies with identical contracts and cash flows can report different revenue timing depending on how they apply judgment within the framework. Understanding where that judgment sits helps an analyst determine whether reported revenue and margins reflect the economics of the business or the accounting choices of management, and whether those choices have changed over time in ways that flatter recent results.
What is the five-step model?
The framework proceeds in five steps. First, identify the contract with a customer, which requires enforceable rights and obligations and probable collection. Second, identify the performance obligations, the distinct goods or services promised. Third, determine the transaction price, including estimates of variable consideration such as rebates, discounts, bonuses or usage fees, constrained so that a significant reversal is not probable. Fourth, allocate the price to each performance obligation based on relative standalone selling prices. Fifth, recognize revenue when or as each obligation is satisfied.
Each step involves judgment. Whether an implementation service is distinct from software, how much variable consideration to estimate, what standalone selling price to assign when items are never sold separately, and whether control transfers over time or at a point in time can all change the timing of revenue. These are the areas where diligence should focus, because they are where reported revenue is most sensitive to assumptions rather than to underlying commercial activity. Disclosures of significant judgments in the revenue note identify which of these matter most for a given company and should be read before any testing begins.
- Step 1: identify the contract
- Step 2: identify distinct performance obligations
- Step 3: determine the transaction price, including constrained variable consideration
- Step 4: allocate the price using relative standalone selling prices
- Step 5: recognize revenue as each obligation is satisfied
When is revenue recognized over time versus at a point in time?
Revenue is recognized over time if the customer simultaneously receives and consumes the benefit as the company performs, if the company's work creates or enhances an asset the customer controls, or if the work creates an asset with no alternative use and the company has an enforceable right to payment for performance to date. Otherwise, revenue is recognized at the point in time when control transfers, using indicators such as legal title, physical possession, acceptance and transfer of risks and rewards.
Over-time recognition requires a method to measure progress, either an output method such as units delivered or milestones reached, or an input method such as costs incurred relative to total expected costs. Cost-based input methods are common in construction and custom manufacturing, and they rely heavily on estimates of total cost to complete. If those estimates are optimistic, revenue and margin are front-loaded. Underwriters should review estimate revisions over time and look for patterns of cumulative catch-up adjustments that reduce profit late in projects.
Which revenue recognition judgments create underwriting risk?
Several areas deserve particular attention. Variable consideration estimates can inflate revenue if rebates, returns or price concessions are underestimated. Principal versus agent determinations decide whether revenue is reported gross or net of amounts paid to third parties; reporting gross raises revenue but not profit, which can distort revenue multiples and growth rates. Bill-and-hold arrangements, consignment, and contract modifications can shift revenue between periods. Capitalized costs to obtain contracts, such as sales commissions, are amortized and can lift near-term margins. Each of these items can move reported revenue or margin without any change in the underlying cash economics of the contracts.
Contract assets and liabilities on the balance sheet also provide signals. Growing contract assets, unbilled revenue recognized ahead of invoicing, mean revenue is outpacing billing and cash collection. Growing contract liabilities, deferred revenue, mean billing is ahead of revenue, which is generally a sign of healthy demand. The trend in each relative to revenue is a useful diagnostic and can be compared with industry norms to identify outliers worth further investigation. Sharp changes in either balance from one period to the next deserve an explanation from management supported by contract-level detail.
What should underwriters test in diligence?
Start with the revenue policy note and compare it with the business model described by management. Then sample large contracts and trace them through the five steps to see whether the policy is applied consistently. Review contract asset and receivable aging, the history of variable consideration estimates against actual outcomes, and any changes in policies or estimates. Analyze revenue by month to look for quarter-end or year-end spikes that could indicate pressure to accelerate recognition. Credit memos issued after period end are another useful test of whether recorded revenue held up once customers reviewed their invoices.
Where revenue is recognized over time, compare estimated margins on open projects with realized margins on completed projects. Persistent margin erosion at completion suggests optimistic estimates. For companies that recently changed their accounting framework or are moving from cash basis or tax basis to GAAP, quantify the effect on historical revenue so that trends are not distorted by the transition itself. Each finding should be mapped to its effect on EBITDA and on the projections that support valuation and debt capacity.
Allocating a bundled contract and measuring first-quarter revenue
- Contract price = $150,000 for a software license, one year of support and implementation services. Standalone selling prices: license $100,000, support $40,000, implementation $20,000. Total SSP = $160,000.
- Allocation ratio = 150,000 / 160,000 = 0.9375. Allocated amounts: license 100,000 x 0.9375 = $93,750; support 40,000 x 0.9375 = $37,500; implementation 20,000 x 0.9375 = $18,750.
- The license is recognized at the point in time it is delivered at contract start: $93,750.
- Support is recognized ratably over twelve months: 37,500 / 12 = $3,125 per month, so $9,375 in the first quarter.
- Implementation is 50% complete at quarter end on a cost input basis: 18,750 x 0.50 = $9,375.
- First-quarter revenue = 93,750 + 9,375 + 9,375 = $112,500, while the remaining $37,500 is recognized over the following three quarters.
How underwriters apply this
- Map revenue policies to the actual contract terms and test a sample of large contracts through the five steps.
- Track contract assets relative to revenue; rising unbilled balances signal revenue ahead of cash.
- Compare variable consideration estimates and percentage-of-completion margins with actual outcomes.
- Identify gross versus net presentation before applying revenue multiples or growth comparisons.
- Quantify any policy change or framework transition so trend analysis is not distorted.
Frequently asked questions
Are ASC 606 and IFRS 15 the same?
They were developed jointly and share the same five-step model and core principle, so most outcomes are identical. Differences exist in specific areas, including the collectability threshold, accounting for certain licenses, some practical expedients and disclosure requirements. For most underwriting purposes, the analysis is the same, but cross-border comparisons should check for these differences.
Why does gross versus net revenue matter to lenders?
When a company acts as principal it reports the full amount billed as revenue; as agent it reports only its fee. Profit is the same either way, but revenue and margins differ greatly. Lenders using revenue-based metrics, growth rates or margin comparisons must know which presentation applies, or they may misjudge scale and profitability.
What is a contract asset?
A contract asset arises when a company has satisfied a performance obligation and recognized revenue but its right to payment depends on something other than the passage of time, such as completing another milestone. It differs from a receivable, which is an unconditional right to payment. Growing contract assets warrant review because they represent revenue not yet billable.
Keep reading
Underwrite your next deal in minutes
Drop a deck or data room. Underridge returns a verdict, investment memo, term sheet and a live model, with every headline figure traced to a page, a formula or a labeled assumption. Ten underwrites free.
Try Underridge freeEducational content written by practitioners. Not investment, accounting, legal or tax advice.