When Do You Recognize Revenue in Accrual Accounting?

In accrual accounting, you recognize revenue when control of the promised good or service transfers to the customer, not when cash arrives. That transfer can happen at a single moment or gradually over a performance period, and the distinction drives when the entry hits your books. In the United States, the Financial Accounting Standards Board’s Accounting Standards Codification Topic 606 sets the rules; internationally, IFRS 15 applies the same logic across more than 140 jurisdictions.¹

The Moment Revenue Is Earned: Transfer of Control

Under ASC 606, revenue is recorded when the customer gains control of the good or service, meaning the buyer can direct its use and obtain substantially all its remaining benefits.² Cash timing is irrelevant. A deposit received before work starts doesn’t produce revenue, and an invoice sent after delivery doesn’t delay it.

Control transfers in one of two patterns, and every performance obligation in a contract falls into one of them.

Point-in-Time Recognition

Most product sales work this way. When a customer walks out of a store with a purchase, takes delivery of shipped goods, or downloads software, control has passed and the seller books the revenue. Practical indicators include transfer of legal title, physical possession, and the shift of risk. If the item is destroyed or lost after that moment, it is the customer’s problem.

Bill-and-hold arrangements are the notable exception. A customer sometimes buys a product but asks the seller to keep it physically, perhaps because their own warehouse is not ready. Revenue can still be recognized while the seller holds the goods, but only when four conditions are all met: the customer requested the arrangement for a real business reason, the product is specifically identified as belonging to that customer, the product is ready for physical transfer at any time, and the seller cannot use it or redirect it to someone else.

Over-Time Recognition

Service contracts, construction projects, and long-term consulting engagements typically recognize revenue over time, because the customer receives and consumes the benefit as work progresses. A firm managing building security does not deliver a single product at year end. The customer receives value every day the guards show up.

When revenue is recognized over time, the business needs a method to measure progress. Two broad approaches exist:

Output methods look at what has been transferred to the customer relative to what remains: units delivered, milestones reached, or surveys of work completed. Conceptually, this most accurately depicts performance because it measures the value the customer has actually received.
Input methods look at the resources consumed relative to total expected resources: labor hours worked, costs incurred, or materials used. This data is usually easier and cheaper to collect, which is why many businesses default to it.

Neither method is inherently preferred. A three-year consulting agreement worth $300,000 might use labor hours to recognize roughly $100,000 per year if effort is evenly distributed. A construction firm might use costs incurred because they closely track the percentage of building completed. The chosen method should faithfully reflect the pattern of control transfer. If it does not, the resulting statements will be misleading regardless of which approach you pick.

The Five Steps That Set the Timing

Before the transfer-of-control question can be answered, ASC 606 requires you to work through five sequential steps for each customer contract:²

Identify the contract with the customer.
Identify the performance obligations in the contract.
Determine the transaction price.
Allocate the transaction price to each performance obligation.
Recognize revenue when, or as, the business satisfies each obligation.

The framework replaced older, industry-specific guidance in 2018 and now applies to virtually every customer contract. Leases, insurance contracts, financial instruments, and guarantees each follow their own dedicated standards; everything else runs through these five steps.

Step 1: A Qualifying Contract Has to Exist

A valid contract requires both parties to approve the agreement and commit to their duties, identifiable payment terms and promised goods or services, commercial substance, and probable collection.² “Commercial substance” means the deal is expected to change the company’s future cash flows in some meaningful way. Until all these criteria are met, no revenue gets recorded, even if work has started or a deposit has already landed in the bank. Beginning a project on a handshake does not start the revenue clock.

When the terms of an existing contract change, the business has to evaluate whether the modification adds genuinely new goods or services at their fair value. If so, the change is treated as a separate contract. If not, the business either adjusts the existing contract going forward or treats the modification as a termination of the old deal and the start of a new one.

Step 2: Break the Contract Into Distinct Promises

A good or service is a separate performance obligation when the customer can benefit from it on its own (or with resources readily available to them) and it is separately identifiable from the other promises in the contract.²

A software company that sells a license bundled with a two-year maintenance plan has two obligations: the license itself and the ongoing support. Each gets its own timeline. License revenue may be recorded at delivery, while maintenance revenue is recognized month by month over the service period. Lumping them together would overstate income in the delivery quarter and understate it later.

This is where most accounting disputes start. A construction company that provides both design and build services under one contract might have a single obligation if the design work is so intertwined with construction that the customer cannot meaningfully use one without the other.

Step 3: Determine the Transaction Price

The transaction price is the total amount the business expects to collect. That is not always the number printed on the invoice. Volume discounts, rebates, performance bonuses, and late-delivery penalties are all variable components that force an estimate of what will actually be received.²

If a contract carries a $50,000 base fee plus a $5,000 bonus for early completion, the company estimates the likelihood of earning the bonus using either the most likely amount or an expected value calculation. Variable consideration only enters the transaction price when it is highly probable that a significant reversal of revenue will not happen later. Aggressive estimates are one of the fastest routes to a restatement.

Two other adjustments show up at this step. When payment is spaced out more than a year from delivery, the transaction price generally has to be adjusted for the time value of money, essentially treating part of the arrangement as a loan. If the gap between delivery and payment is one year or less, no financing adjustment is needed. When customers can return products or cancel services, the business recognizes revenue only for the portion it expects to keep; the rest is booked as a refund liability. A retailer selling 100 units at $50 with a historical 5% return rate books $4,750 in revenue and a $250 refund liability, which sits on the books until the return window closes or returns come in.

Step 4: Allocate the Price Across Obligations

Once the total transaction price is set, split it among the performance obligations based on each item’s standalone selling price. For a bundled deal priced at $5,000 combining a product with a $4,000 standalone value and a service plan with a $2,000 standalone value, the allocation is roughly $3,333 to the product and $1,667 to the service plan.² The proportional split prevents front-loading revenue onto whatever gets delivered first.

Step 5: Recognize as Each Obligation Is Satisfied

Only now does the transfer-of-control question above answer itself, obligation by obligation. Point-in-time obligations produce a single entry; over-time obligations produce a series of entries as measured progress accumulates.

When Cash and Revenue Don’t Line Up

Cash and revenue recognition rarely coincide, and the balance sheet has to carry the gap.

When a customer pays before the business delivers, the payment is recorded as a contract liability, commonly called deferred or unearned revenue. A software company that collects $12,000 upfront for a one-year subscription does not book $12,000 in revenue on day one. It records a $12,000 contract liability and shifts $1,000 per month into revenue as it provides the service. Skipping this step is a textbook way to overstate income.

The reverse also happens. When a business has earned revenue but does not yet have an unconditional right to payment, it records a contract asset, sometimes called an unbilled receivable. A contractor who has completed phase one of a two-phase project but cannot bill until both phases are done has earned the phase-one revenue, but the right to payment depends on completing phase two, so it sits as a contract asset. Once the remaining condition is satisfied, the contract asset converts to a standard receivable.

Book-Tax Timing Differences

Even businesses using accrual accounting for both financial reporting and taxes will find that GAAP and the Internal Revenue Code do not always agree on when revenue is earned. A company might recognize revenue under ASC 606 when a performance obligation is satisfied, while the IRS requires or allows different timing under its own rules. Temporary differences are common in long-term contracts, deferred revenue arrangements, and situations where a business uses one method for tax returns and another for financial statements.

Partnerships and S corporations report these gaps on Schedule M-3, which reconciles financial statement income to taxable income line by line, including dedicated lines for unearned or deferred revenue, accrual-to-cash adjustments, and long-term contract income.³ The differences themselves are expected. Failing to track and disclose them properly can raise red flags on a return.

What Happens When the Timing Is Wrong

Federal tax law requires every taxpayer to compute taxable income under the accounting method it regularly uses to keep its books.⁴ Misapplying revenue recognition, whether by booking income too early, too late, or in the wrong amounts, can produce an underpayment of tax with its own penalty structure.

For negligence or careless disregard of the rules, the IRS imposes an accuracy-related penalty equal to 20% of the underpayment.⁵ If the IRS proves the underpayment was due to fraud, the penalty rises to 75% of the portion attributable to fraud.⁶

Public company officers carry an added layer of risk under the Sarbanes-Oxley Act. CEOs and CFOs must personally certify that periodic financial reports comply with securities law and fairly present the company’s financial condition. An officer who certifies a report knowing it fails those requirements faces up to $1 million in fines and 10 years in prison. Willful certification, meaning the officer acted deliberately rather than recklessly, raises the maximum penalty to $5 million and 20 years.⁷

Beyond regulatory penalties, earnings restatements traced to revenue recognition errors tend to hit stock prices hard and frequently trigger shareholder litigation. The resulting lawsuits can cost far more than the original tax penalty.

1
IFRS. IFRS 15 Revenue from Contracts with Customers
2
SEC.gov. ASC 606: Revenue from Contracts with Customers
3
Internal Revenue Service. Instructions for Schedule M-3 (Form 1065)
4
Internal Revenue Service. 4.11.6 Changes in Accounting Methods
5
Office of the Law Revision Counsel. 26 U.S. Code 6662 – Imposition of Accuracy-Related Penalty on Underpayments
6
Office of the Law Revision Counsel. 26 U.S. Code 6663 – Imposition of Fraud Penalty
7
Office of the Law Revision Counsel. 18 USC 1350 – Failure of Corporate Officers to Certify Financial Reports