Revenue is recognized when a business has delivered the good or service it promised and earned the right to be paid. Under accrual accounting, that moment arrives on delivery or performance, regardless of when cash changes hands. Under cash basis accounting, it arrives when payment actually lands in the account. For public companies and most larger private ones, the precise timing follows a five-step framework called ASC 606, published by the Financial Accounting Standards Board.
Cash Basis and Accrual Basis Trigger Different Moments
Cash basis accounting records revenue the moment payment arrives, whether by check, wire, or card. It tracks what’s in the bank but can distort profitability when large invoices straddle year-end.
Accrual accounting shifts the focus to economic activity. Revenue posts when it is earned, even if the customer hasn’t paid. Ship $50,000 of product in December and receive the check in January, and accrual accounting places the revenue in December, because that’s when the obligation was fulfilled. The IRS frames this as the “all events test”: all events have occurred that fix the right to the income, and the amount can be determined with reasonable accuracy.1Office of the Law Revision Counsel. 26 U.S. Code 451 – General Rule for Taxable Year of Inclusion
Not every business gets to pick. Under Section 448 of the Internal Revenue Code, C corporations, partnerships with a C corporation as a partner, and tax shelters generally must use the accrual method.2Office of the Law Revision Counsel. 26 U.S. Code 448 – Limitation on Use of Cash Method of Accounting Smaller businesses get an exception: a corporation or partnership with average annual gross receipts of $32 million or less over the prior three tax years can still use the cash method for tax years beginning in 2026.3Internal Revenue Service. Revenue Procedure 2025-32 – 2026 Adjusted Items S corporations, sole proprietors, and most small partnerships fall well below that line and generally have a free choice. If the IRS decides that the chosen method does not clearly reflect income, it can force a change.4Office of the Law Revision Counsel. 26 U.S. Code 446 – General Rule for Methods of Accounting
The ASC 606 Five-Step Model
For financial reporting purposes, the dominant framework is ASC 606, issued by FASB with its international counterpart in 2014.5Financial Accounting Standards Board (FASB). Revenue Recognition It replaced a patchwork of industry-specific rules with a single model that applies across virtually every sector. The process runs in five steps:
- Identify the contract. A valid contract creates enforceable rights and obligations on both sides. It can be written, oral, or implied by customary business practice, as long as collectability is probable.
- Identify the performance obligations. Each distinct promise to deliver a good or service is a separate obligation. A software company selling a license bundled with two years of updates has at least two obligations, not one.
- Determine the transaction price. This is the total amount the business expects to receive, accounting for discounts, rebates, refunds, bonuses, and any other variable elements.
- Allocate the price. When a contract has multiple performance obligations, the total price is divided among them based on standalone selling prices.
- Recognize the revenue. Revenue is recorded as each obligation is satisfied, either at a point in time or over a period of time.
The framework determines the timing and the amount of revenue that lands on the income statement. Steps 1 through 4 build up to Step 5, and Step 5 is the moment the reader is asking about.
Point-in-Time Recognition
The simplest pattern is a one-time transfer. A customer walks into a store, buys a laptop, and walks out with it. Control shifts the moment the buyer takes possession: they bear the risk of damage, they decide what to do with it, and the seller has a right to payment. The full sale amount is recorded immediately.
For shipped goods, the shipping terms pin down the exact moment control passes. Under “FOB shipping point,” control passes when the product leaves the seller’s dock. Under “FOB destination,” it passes when the product arrives at the buyer’s location. That distinction can shift revenue into a different reporting period, which is why auditors look closely at shipping terms at quarter-end.
Point-in-time recognition also fits one-off services where the whole benefit is delivered at once. A photographer who shoots a wedding and hands over the photos has satisfied the obligation in a single event. The controlling question is always whether the customer has obtained control: the ability to direct the use of, and obtain substantially all the remaining benefits from, the good or service.
Over-Time Recognition
Some obligations are satisfied gradually. ASC 606 requires over-time recognition when any one of three conditions is met: the customer receives and consumes the benefit as the work is performed; the work creates or enhances an asset the customer controls; or the work produces something with no alternative use to the seller and the seller has a right to payment for work completed to date.6Financial Accounting Standards Board (FASB). Revenue from Contracts with Customers (Topic 606) – ASU 2014-09
Monthly cleaning contracts and gym memberships fit the first condition; the customer benefits from each day of service as it happens. Construction typically meets the second, because the building belongs to the customer as it rises on their land. Custom manufacturing with no resale value to the maker often qualifies under the third.
When revenue is recognized over time, the business needs a way to measure progress. Input methods look at costs incurred or labor hours expended against total expected inputs. Output methods look at units delivered, milestones reached, or surveys of work performed. The chosen method should reflect the actual transfer of value to the customer, and it must be applied consistently across the contract. A construction company might use costs incurred as a percentage of total estimated costs. A software development firm might use milestones.
When Cash Arrives Before the Obligation Is Satisfied
Payment received in advance does not count as revenue yet. It sits on the balance sheet as a contract liability, often labeled deferred revenue. An annual software subscription paid on January 1 gives the company cash but leaves it owing the customer twelve months of access, so revenue is recognized ratably as each month of service is delivered.
Gift cards work the same way. The retailer collects money at the register but has not delivered anything. Revenue is recognized when the card is redeemed. For cards that are never redeemed, called “breakage,” the company can recognize that portion of revenue over time in proportion to the pattern of actual redemptions, provided it can reasonably estimate breakage rates.
The reverse case, where delivery precedes payment, is the standard accrual scenario: revenue is recorded on delivery, and the amount owed shows up as accounts receivable.
Variable Price and Return Rights
Many contracts do not have a fixed price. Performance bonuses, volume discounts, rebates, penalties, and refund rights all make the transaction price variable. ASC 606 requires businesses to estimate variable consideration and include it in the transaction price, but only to the extent that a significant reversal of revenue is unlikely once the uncertainty resolves.
Two estimation approaches are available. The expected value approach uses a probability-weighted average across possible outcomes and works well when a company has many similar contracts. The most likely amount approach picks the single most probable outcome and fits better when the result is binary, such as earning a bonus or not. Whichever approach is chosen must be applied consistently through the contract.
Return rights get their own treatment. When a seller transfers a product but grants the customer a right to return it, revenue is not recognized on the units expected to come back. At the time of sale, the company records three things: revenue for the products expected to stay sold, a refund liability for the expected returns, and an asset representing the right to recover the returned goods.6Financial Accounting Standards Board (FASB). Revenue from Contracts with Customers (Topic 606) – ASU 2014-09
A worked example: a company sells 100 units at $100 each (cost of $60 per unit) and estimates that 3 will be returned. It records $9,700 in revenue (97 units × $100), a $300 refund liability (3 units × $100), a $180 asset for the right to recover returned inventory (3 units × $60), and cost of sales of $5,820 (97 units × $60). Those estimates are updated at the end of each reporting period, with adjustments flowing through revenue.6Financial Accounting Standards Board (FASB). Revenue from Contracts with Customers (Topic 606) – ASU 2014-09
Warranties and Contract Changes Can Shift the Timing
Two situations commonly move revenue out of the period a seller might expect. A service-type warranty (extended coverage, accidental damage protection, or maintenance beyond the original product specification) counts as a separate performance obligation, so a portion of the transaction price is allocated to it and recognized over the warranty period rather than at the point of sale. A basic assurance-type warranty that only guarantees the product works as promised is not a separate obligation; the estimated cost is accrued as a liability at sale, and revenue on the underlying product is recognized normally.6Financial Accounting Standards Board (FASB). Revenue from Contracts with Customers (Topic 606) – ASU 2014-09
Contract modifications can also reopen prior recognition. A modification is treated as a separate new contract only when the added goods or services are distinct and the price increase reflects their standalone selling prices. Otherwise, the modification is folded into the existing contract, and the company may need to make a cumulative catch-up adjustment to revenue already recognized. Price reductions without new deliverables are a common example.