Welcome to Revenue Recognition!

Hello future CPAs! Today, we are diving into one of the most important chapters in the FAR exam: Revenue Recognition (ASC 606). Why is this so important? Because revenue is the "top line" of the income statement. If the revenue is wrong, almost everything else is wrong too! Don't worry if this seems a bit overwhelming at first—we are going to break it down using a simple 5-step process that you can apply to any scenario the exam throws at you.

The Core Principle

The main goal of revenue recognition is to record revenue when a company transfers control of goods or services to a customer. The amount recorded should reflect the payment the company expects to receive in exchange for those goods or services.

The "ISTAR" Mnemonic

To remember the five steps of revenue recognition, just remember ISTAR:

I – Identify the contract with the customer.
S – Separate the performance obligations.
T – determine the Transaction price.
A – Allocate the transaction price.
R – Recognize revenue when/as obligations are satisfied.

Step 1: Identify the Contract

A contract is an agreement between two or more parties that creates enforceable rights and obligations. For a contract to exist under ASC 606, it must meet these criteria:

  • All parties have approved the deal.
  • Each party’s rights regarding the goods/services are identifiable.
  • Payment terms are identified.
  • The contract has commercial substance (it will change the company's future cash flows).
  • Collection is probable (it is likely the customer will pay).

Quick Review: If these criteria aren't met, you generally cannot recognize revenue yet, even if cash is received! That cash would likely be recorded as a liability (Unearned Revenue).

Step 2: Identify the Performance Obligations (POs)

Think of a Performance Obligation as a promise to provide a "distinct" good or service. A good or service is distinct if:

  1. The customer can benefit from it on its own (or with other readily available resources).
  2. The promise to transfer it is separately identifiable from other promises in the contract.

Example: If you buy a laptop and a 3-year tech support plan, those are two separate POs. You can use the laptop without the support, and they are not "highly integrated." However, if you hire a contractor to build a custom house, the bricks, wood, and labor are NOT separate POs—they are all inputs into one single PO: the completed house.

Key Takeaway:

If goods or services are highly interrelated or integrated, they are combined into a single performance obligation.

Step 3: Determine the Transaction Price

The transaction price is the amount of money the company expects to be entitled to. It's not always just a flat fee!

Variable Consideration

Sometimes the price depends on future events (like bonuses for early completion or penalties for being late). You must estimate this using either:

  • Expected Value: A weighted average of all possible amounts (good for many similar contracts).
  • Most Likely Amount: The single most likely outcome (good if there are only two possibilities, like "bonus" or "no bonus").

Significant Financing Component

If the customer pays much earlier or much later than the goods are delivered, the "time value of money" matters. If the period is more than one year, you must adjust the price for interest.

Did you know? If the time between payment and delivery is less than one year, the FASB gives you a "practical expedient"—you can ignore the interest component!

Step 4: Allocate the Transaction Price

If a contract has more than one Performance Obligation, we need to split the total price between them. We do this based on their Standalone Selling Prices (SSP).

The Allocation Formula:
\( \text{Allocated Price} = \left( \frac{\text{SSP of the Individual Item}}{\text{Total SSP of all Items}} \right) \times \text{Total Transaction Price} \)

Example: A bundle costs \$120. It includes a Phone (SSP \$100) and a Case (SSP \$50). Total SSP is \$150.
Phone Allocation: \( (\$100 / \$150) \times \$120 = \$80 \)
Case Allocation: \( (\$50 / \$150) \times \$120 = \$40 \)

Step 5: Recognize Revenue

This is the "finish line." Revenue is recognized when the customer gains control of the asset. This can happen in two ways:

1. Over Time

Revenue is recognized over time if any of these are true:

  • The customer consumes the benefit as the seller performs (e.g., cleaning services).
  • The seller creates an asset that the customer controls (e.g., building an extension on the customer's land).
  • The asset has no alternative use to the seller AND the seller has a right to payment for work done so far (e.g., a highly customized specialized piece of equipment).

2. At a Point in Time

If it doesn't meet the "over time" criteria, recognize revenue when control transfers. Indicators of control include:

  • Seller has a right to payment.
  • Customer has legal title.
  • Customer has physical possession.
  • Customer has the significant risks and rewards of ownership.

Special Accounting Scenarios

Principal vs. Agent

  • Principal: Controls the good before it's transferred. Revenue = Gross amount billed.
  • Agent: Arranges for the other party to provide the good. Revenue = Net (the commission earned).

Warranties

  • Assurance-type: A guarantee the product works as promised. This is NOT a separate PO. (Accrue a warranty liability).
  • Service-type: An "extended warranty" sold separately. This IS a separate PO. (Defer revenue and recognize over the service period).

Right of Return

When a customer can return a product, the seller should recognize:

  1. Revenue for the amount they expect to keep.
  2. A Refund Liability for the amount they expect to pay back.
  3. An Asset for the inventory they expect to get back.

Quick Review: Common Mistakes to Avoid

- Don't recognize revenue just because you received cash. Check Step 1 and Step 5!
- Don't allocate based on the price the company "usually" charges if there is a specific SSP.
- Watch out for collectibility. If you don't think you'll get paid, you can't have a valid contract under Step 1.

Final Summary Key Takeaway:

Revenue Recognition is all about the transfer of control. Use ISTAR to navigate the 5-step process: identify the contract and obligations, determine and allocate the price, and recognize revenue only when control passes to the buyer.