What Is a Revenue Contract? Criteria, Recognition, and Section 451

A revenue contract is an agreement between a seller and a customer that, once it satisfies five specific conditions under ASC 606, sets the schedule for when and how the seller records income from the deal. The label is not marketing shorthand. It is an accounting classification, and it carries real consequences: money you have collected from a customer is not revenue until the underlying agreement qualifies as a revenue contract and the promised goods or services have been delivered on the terms the standard requires. Misjudging that line has produced SEC enforcement actions, restatements, and penalties.¹

ASC 606 (Revenue from Contracts with Customers) replaced a patchwork of industry-specific rules with a single standard that applies to virtually every business. So the definition below is not niche. It is the rulebook used whether the seller is a construction firm, a software company, a hospital, or a consultant.

The Five Criteria an Agreement Must Meet

Before any revenue gets recorded, the arrangement has to satisfy all five of these conditions under ASC 606-10-25-1. If even one is missing, it is not a revenue contract, and cash received sits on the balance sheet as a liability until things change.²

Both parties have approved the contract and committed to their obligations. Approval can be written, oral, or implied by customary business practice.
Each party’s rights regarding the goods or services being transferred are identifiable.
Payment terms are clear enough that both sides understand when and how much money changes hands.
The arrangement has commercial substance, meaning it actually changes the risk, timing, or amount of the seller’s future cash flows. This requirement blocks sham transactions that look like revenue on paper but move no real economic value.
Collection is probable. The seller has a reasonable basis for believing the customer will pay, based on the customer’s ability and intent, not on optimism.

These criteria apply regardless of industry, contract size, or whether the deal was papered by a corporate legal team or sealed by handshake and past practice. A one-page purchase order and a hundred-page master services agreement are evaluated against the same list.

When an Arrangement Does Not Qualify

Failing the criteria does not mean you get to ignore what happened. Cash you have taken from the customer becomes a liability on your books, representing either a future obligation to deliver goods and services or an obligation to refund the money. You can move that liability into revenue only when one of three things happens:²

You have finished delivering everything promised, the customer has paid all or substantially all of the consideration, and the payment is nonrefundable.
The contract has been terminated and whatever consideration you received is nonrefundable.
You have transferred control of the goods or services related to the payment received, you have stopped performing, you have no remaining delivery obligations, and the payment is nonrefundable.

This is where many businesses trip. A cash payment in hand is not revenue on its own. Until the five criteria are met or one of these exits applies, calling that cash income is a misstatement.

How a Revenue Contract Turns Into Recognized Revenue

Once an agreement qualifies, ASC 606 walks you through four more steps: identifying the separate promises, pricing them collectively, splitting that price among them, and recording revenue as each promise is fulfilled.

Identifying Performance Obligations

Each distinct promise in the contract is a performance obligation, and each one gets its own slice of the transaction price and its own timing for recognition. A good or service is a separate obligation when both of these are true: the customer can benefit from it on its own or with resources they already have, and the promise to deliver it is separately identifiable from the other promises in the contract.²

A software license bundled with a year of technical support illustrates the point. If the software works without the support and comparable support is available from other vendors, those are two obligations, tracked and recognized independently. If the seller heavily customizes and integrates the software so that the license and support only deliver value as a combined package, they collapse into one obligation. The distinction directly affects when revenue hits the income statement.

Determining the Transaction Price

The transaction price is the total amount you expect to receive for transferring the promised goods or services. That is often not the sticker number. Discounts, rebates, refunds, performance bonuses, and penalty clauses all produce what the standard calls variable consideration, and you have to estimate those adjustments up front.²

ASC 606 provides two estimation methods. The expected value method suits a large portfolio of similar contracts where historical data can predict the average outcome. The most likely amount method suits a contract with only two or three possible outcomes, such as a bonus that either pays out in full or not at all.

You cannot simply plug in the best-case number. The standard imposes a constraint: variable consideration is included only to the extent that a significant reversal of cumulative recognized revenue is unlikely once the uncertainty resolves. That assessment is qualitative and looks at both the likelihood and the magnitude of a potential reversal. A $10 million contract with a $50,000 variable bonus warrants less scrutiny than one where $3 million of the price turns on a milestone the customer has never hit before.

If the payment timeline gives either side a meaningful financing benefit, you also adjust the transaction price for the time value of money. Payment two years before delivery, or two years after, changes the economics. When the gap between delivery and payment is one year or less, a practical expedient lets you skip this adjustment.²

Allocating the Price Across Obligations

With the total price set and the obligations identified, you divide the money based on relative standalone selling prices. Where you actually sell the item on its own, the price is observable and the split is straightforward. Where you do not, ASC 606 offers three estimation approaches:²

Adjusted market assessment: reference what the market would bear for a similar good or service, adjusted for your costs and margins.
Expected cost plus margin: forecast the costs to fulfill the obligation and add an appropriate profit margin.
Residual approach: subtract the known standalone prices of the other obligations from the total, and assign the remainder to the one with the uncertain price. This method is only permitted when the selling price is highly variable across customers or when the good or service has never been sold on a standalone basis.

Different obligations within the same contract can be priced using different methods. The point is a defensible allocation that reflects what each component is actually worth, not a split that conveniently front-loads revenue.

Recognizing Revenue: Over Time or at a Point in Time

Revenue is recorded when a performance obligation is satisfied by transferring control of the promised good or service. Control means the customer can direct the use of the item and obtain substantially all of its remaining benefits. The pivotal question is whether that transfer happens at a moment or gradually.²

You recognize revenue over time if any one of three conditions holds. First, the customer simultaneously receives and consumes the benefit as you perform, as with routine cleaning or ongoing managed IT support. Second, your work creates or enhances an asset the customer controls throughout the process, like construction on the customer’s land. Third, what you are creating has no alternative use to you and you have an enforceable right to payment for work completed to date, which frequently covers custom manufacturing.

If none of those conditions applies, control shifts at a point in time. ASC 606 lists five indicators to help pinpoint that moment: the seller has a present right to payment, the customer has legal title, physical possession has transferred, the customer bears the significant risks and rewards of ownership, and the customer has accepted the asset. No single indicator settles the question. Physical possession, for example, can mislead in consignment arrangements, where the goods sit on the customer’s shelves but the seller still controls them. Bill-and-hold arrangements run the other way: the customer can control an asset still sitting in the seller’s warehouse if the arrangement has a substantive business reason, the product is separately identified as belonging to the customer, the product is ready for transfer, and the seller cannot use the product or redirect it to another buyer.

Modifications After Signing

Contracts change. Customers add scope, reduce quantities, renegotiate pricing, or extend timelines. ASC 606 treats a modification as an approved change in scope or price, whether the approval is written, oral, or reflected in customary business practice.²

A modification is accounted for as an entirely separate contract when both of these are true: the added goods or services are distinct, and the price increase reflects their standalone selling prices (adjusted for any contract-specific discounts the customer receives because no new selling costs are incurred). In that case, the modification is essentially a new deal running alongside the original, and each is accounted for independently.

When the modification does not qualify as a separate contract, the original contract is adjusted. If the remaining undelivered goods or services are distinct from what has already been transferred, the change is treated as a termination of the old contract and the creation of a new one, applied prospectively. If the remaining goods or services are not distinct, revenue is recalculated with a cumulative catch-up adjustment that trues up the numbers from inception through the modification date. That catch-up approach shows up often in long-term construction and engineering contracts where a change order reshapes a single integrated deliverable.

One point catches people off guard: a modification can exist even while the parties are still disputing the price change. If the scope change has been approved but the corresponding price adjustment has not been settled, you estimate the price change using the same variable consideration rules that apply to the original transaction price.

Tax Alignment Under Section 451

The accounting treatment does not stay confined to the accounting department. Under 26 U.S.C. § 451, accrual-method taxpayers cannot defer taxable income beyond the point at which they recognize that income in their financial statements. Added by the Tax Cuts and Jobs Act, this rule ties the “all events test” for tax purposes to the applicable financial statement, so ASC 606 timing becomes a floor for when taxable income must be reported.³

For contracts with multiple performance obligations, the tax code goes further. The transaction price allocated to each obligation for tax purposes must match the allocation used in the financial statements. Two sets of books, one for investors and one for the IRS, is not an option.³

Advance payments get their own treatment. When an accrual-method taxpayer receives payment before delivering goods or services, the default is full inclusion in gross income in the year of receipt. Section 451(c) offers a one-year deferral election: include the portion your financial statement recognizes in the current year, and defer the remaining portion to the following taxable year. The deferral cannot extend past that second year, no matter when delivery actually happens. Once elected, the treatment applies to all advance payments in the chosen category and continues in future years unless the IRS approves a change.³

A revenue contract, in short, is not just a piece of paper. It is a defined accounting object with entry criteria, a recognition schedule, and tax consequences that follow the accounting. Get the five criteria right at the front end, keep the obligations and pricing clean through any modifications, and the rest of the framework has something solid to work with.

1
U.S. Securities and Exchange Commission. SEC Charges Amyris with Improper Revenue Recognition
2
Financial Accounting Standards Board. Accounting Standards Update 2014-09 – Revenue from Contracts with Customers
3
Office of the Law Revision Counsel. 26 USC 451 – General Rule for Taxable Year of Inclusion