ASC 605 was the U.S. GAAP standard that governed revenue recognition before 2018, and it worked as an all-or-nothing test: a company could record revenue only when four conditions were satisfied at the same time. Those conditions were persuasive evidence of an arrangement, delivery or performance, a fixed or determinable price, and reasonable assurance of collection. If any one of them failed, the entire revenue amount was deferred until the gap closed. The SEC translated the framework into practical enforcement terms through Staff Accounting Bulletin (SAB) Topic 13, which became the benchmark for public company reporting.
ASC 606 replaced this framework for public company fiscal years beginning after December 15, 2017, and for private companies one year later. The four-criteria model still matters for anyone reading pre-2018 statements, restating historical periods, or working on forensic reviews.
The Four Criteria
Persuasive Evidence of an Arrangement
A company needed documented proof the deal existed. In practice that meant a signed contract, a purchase order, or another written agreement executed by both parties. Oral commitments almost never qualified.
The SEC was strict about timing. If a company’s normal practice for a given class of customer required a written agreement, booking revenue before the customer signed was improper. A signature that landed after a reporting period closed pushed the transaction into the next period. Side agreements that quietly modified the master contract, granting cancellation rights or return privileges that weren’t in the primary document, could also break this criterion.
Delivery or Performance
The second criterion asked whether the seller had actually done its part. For goods, delivery generally tracked the transfer of the risks and rewards of ownership, which often lined up with the shipping point. If the seller still owed meaningful work after shipment, such as installation or testing that affected functionality, delivery wasn’t complete.
For services, revenue accrued as work was performed, measured by percentage of completion or by the passage of time depending on the arrangement. The principle didn’t change: the seller had to have substantially fulfilled its side.
Fixed or Determinable Price
The amount owed had to be either stated as a dollar figure or reliably calculable from the contract’s own terms without guessing about future events. Refund rights, return clauses, and cancellation privileges pushed against this criterion, because the price wasn’t truly fixed while those contingencies were open. Extended payment terms that resembled financing more than a normal sale created similar problems, as did undisclosed concessions offered on the side. Any of these could force deferral until the uncertainty cleared.
Collectibility Reasonably Assured
The seller had to evaluate the buyer’s creditworthiness at the time the arrangement was struck. “Reasonably assured” was a meaningful threshold, not a formality. Real doubts about the buyer’s ability to pay blocked recognition even when the other three criteria were satisfied. Sellers without a reliable collection history for a customer class, or dealing with buyers whose finances had deteriorated, often waited for cash before recording revenue.
Bill-and-Hold Arrangements
Bill-and-hold deals, where the seller invoiced the customer but kept the goods in its warehouse, created obvious friction with the delivery criterion. The SEC allowed revenue recognition on these transactions only when a demanding list of conditions was met:
- The buyer, not the seller, requested the arrangement, and had a genuine business reason for it.
- Risks of ownership had passed to the buyer even though the goods remained on site.
- A specific and reasonable delivery date was set, consistent with the buyer’s business purpose.
- The seller had no significant unfulfilled performance obligations tied to the goods.
- The ordered goods were physically segregated from the seller’s own inventory and couldn’t be used to fill other orders.
- The product was complete and ready for shipment.
The rules were tight because bill-and-hold was a favorite vehicle for revenue manipulation. A seller under quarterly pressure could invoice a customer for goods that were never truly ordered on a hold basis and record revenue on what amounted to a fictitious sale. Auditors and SEC examiners treated these transactions with heavy skepticism.
Multiple-Element Arrangements
Many contracts bundled several deliverables together: software with a maintenance plan, equipment with installation and training, and similar combinations. ASC 605 required sellers to break the bundle apart into “units of accounting” and assign a share of the contract price to each. Revenue for a single unit could only be recognized once all four criteria were met for that specific element.
A delivered item counted as a separate unit of accounting if it had standalone value to the customer, meaning any vendor sold it separately or the customer could resell it. Items without standalone value got combined with undelivered items and recognized later.
The Selling Price Hierarchy
Accounting Standards Update (ASU) 2009-13 changed how sellers allocated the total contract value across the pieces. It established a three-tier hierarchy and required the relative selling price method:
- Vendor-Specific Objective Evidence (VSOE): the price the seller charged when it sold the same item separately to other customers. This tier required consistent, documented standalone pricing.
- Third-Party Evidence (TPE): prices charged by unrelated vendors for substantially similar deliverables. TPE was rarely usable in practice because finding truly comparable third-party transactions was difficult.
- Best Estimate of Selling Price (ESP): the seller’s own estimate of what the deliverable would sell for on a standalone basis. ASU 2009-13 introduced this third tier so companies had a path forward when neither VSOE nor TPE existed.
ASU 2009-13 also eliminated the older Residual Method, which had let companies assign VSOE values to known elements and dump whatever was left over onto the element without VSOE. The relative selling price method required a proportional allocation across all deliverables. The Residual Method had sometimes produced distorted results, particularly when the residual element was the most valuable part of the deal.
Allocation was where many companies stumbled. Splitting the price incorrectly meant recognizing too much revenue too early on delivered items and too little on undelivered ones, or the reverse. For software firms, VSOE was often the single biggest obstacle to timely recognition, because it required a history of standalone sales at consistent prices that many companies didn’t have.
Industry-Specific Layers
The four-criteria framework was general, but some industries had transaction structures the general rules couldn’t handle cleanly, so specialized guidance sat on top. Software companies operated under SOP 97-2 with its strict VSOE requirements. Long-term construction contracts fell under ASC 605-35, which offered percentage-of-completion and completed-contract methods; GAAP generally favored percentage-of-completion when reliable estimates were possible. Real estate and telecommunications had their own rules as well, and economically similar transactions could be treated differently depending on which industry the seller was in. That inconsistency was one of the reasons FASB eventually replaced the framework.
Where Companies Got Into Trouble
Revenue recognition under ASC 605 was one of the most common causes of financial restatements and SEC enforcement actions. The pressure to hit quarterly earnings targets combined with the framework’s pressure points to produce recurring patterns of manipulation.
Companies recognized revenue before contracts were fully executed, sometimes on verbal commitments or unsigned purchase orders. Side agreements granted hidden return rights or cancellation privileges that never appeared in the primary contract file. Bill-and-hold transactions were booked without meeting the SEC’s conditions. And sellers occasionally shipped products the customer hadn’t ordered, recognized the revenue, and then characterized the inevitable return as a shipping error the following quarter.
The SEC emphasized that companies needed robust internal controls to catch these issues, including an independent contracts function housed within accounting rather than sales, and primary responsibility inside the accounting department for reviewing transactions before they were booked. Companies that let sales teams control documentation without independent oversight were setting themselves up for restatements.
What Replaced ASC 605
FASB replaced ASC 605 with ASC 606 through ASU 2014-09. Public companies adopted for fiscal years beginning after December 15, 2017; private companies followed for fiscal years beginning after December 15, 2018. The new standard runs on a single principles-based, five-step model: identify the contract, identify the performance obligations within it, determine the transaction price, allocate that price across the performance obligations, and recognize revenue as each obligation is satisfied. Most of the industry-specific guidance that had fragmented ASC 605 was eliminated.
For current reporting, ASC 605 is closed. It still matters when reading financial statements from before 2018, when auditors or forensic accountants revisit historical periods, and when interpreting concepts like completed delivery and assured collection that carry forward into ASC 606 even though the mechanics changed.