ASC 605, Revenue Recognition, contains ten Subtopics:
The principles guiding recognition of revenues for financial reporting purposes are central to GAAP and in most instances are unambiguous and straightforward.
However, while the currently effective basic principles are uncomplicated, it is nonetheless true that a large percentage of financial reporting frauds over the period beginning about 1995 were the result of misapplications, often deliberate, of revenue recognition practices prescribed under GAAP. Apart from outright fraud (e.g., recording nonexistent transactions), there were several factors contributing to this unfortunate state of affairs.
First, business practices have continued to grow increasingly complex, involving, among other things, a marked shift from manufacturing to a service-based economy, where the proper timing for revenue recognition is often more difficult to ascertain. Second, there has been an undeniable increase in the willingness of managers, whose compensation packages are often directly linked to the company's stock price and reported earnings, to “stretch” accounting rules to facilitate earnings management. This has particularly been the case where GAAP requirements have been vague, complex, or abstruse. And third, it has been well documented that, too often, independent auditors have been willing to accommodate managements' wishes, particularly in the absence of specific rules under GAAP to support a denial of such requests. These actions have often had disastrous consequences, if not immediately, then in the longer run.
Errors or deliberate distortions involving revenue recognition fall into two categories: situations in which revenue legitimately earned is reported in the incorrect fiscal (financial reporting) period, often referred to as “cutoff” errors, and situations in which revenue is recognized although never actually earned. Given the emphasis on periodic reporting (e.g., quarterly earnings announcements in the case of publicly held entities), even simple “cutoff” errors can have enormous impact, notwithstanding the fact that these should tend to offset over several periods. As a practical matter, all instances of improper revenue recognition constitute a challenge to all accountants attempting to properly interpret and apply GAAP, including independent auditors.
Revenue, whether from the sale of product or provision of services, is to be recognized only when it has been earned. According to CON 5, Recognition and Measurement in Financial Statements of Business Enterprises:
…An entity's revenue-earning activities involve delivering or producing goods, rendering services, or other activities that constitute its ongoing major or central operations, and revenues are considered to have been earned when the entity has substantially accomplished what it must do to be entitled to the benefits represented by the revenues. (Para. 83)
In other words, in order to be recognized revenue must be realized or realizable, and it must have been earned.
CON 5 notes that “the two conditions (being realized or realizable, and being earned) are usually met by the time product or merchandise is delivered or services are rendered to customers, and revenues from manufacturing and selling activities and gains and losses from sales of other assets are commonly recognized at time of sale (usually meaning delivery).” Moreover, “if services are rendered or rights to use assets extend continuously over time (for example, interest or rent), reliable measures based on contractual prices established in advance are commonly available, and revenues may be recognized as earned as time passes.” In other words, for most traditional and familiar types of transactions, the point at which it is appropriate to recognize revenue will be quite clear. (CON5, Para. 84a)
The SEC, reflecting on the conceptual foundation for revenue recognition, observed in Staff Accounting Bulletin (SAB) 104, that:
…revenue generally is realized or realizable and earned when all of the following criteria are met:
- There is persuasive evidence that an arrangement exists
- Delivery has occurred or services have been rendered
- The seller's price to the buyer is fixed or determinable, and
- Collectibility is reasonably assured.
Note that, while Securities and Exchange Commission (SEC) rules and “unofficial” guidance are not necessarily to be deemed GAAP for nonpublic companies, to the extent that these provide insights into the application of the Accounting Standards Codification (ASC), they should always be viewed as relevant guidance and followed, absent other, contradictory rules established under GAAP. In the absence of any other authoritative source, SEC pronouncements may represent the best thinking on the subject and would thus be considered authoritative for all reporting entities.
With regard to the four criteria set forth above, consideration should be directed at the following discussion, which is drawn partially from SAB 101 and SAB 104.
First, regarding persuasive evidence of an arrangement, attention must be paid to the customary manner in which the reporting entity engages in revenue-producing transactions with its customers or clients. Since these transactions are negotiated between the buyer and seller and can have unique or unusual terms, there are (and can be) no absolute standards. Thus, for an enterprise that traditionally obtains appropriate documentation (purchase orders, etc.) from its customers before concluding sales to them, advance deliveries to customers, even if later ratified by receipt of the proper paperwork, would not be deemed a valid basis for revenue recognition at the time of delivery.
When evaluating purported revenue transactions, the substance of the transactions must always be considered, and not merely their form. It has become increasingly commonplace to “paper over” transactions in ways that can create the basis for inappropriate revenue recognition. For example, transactions that are actually consignment arrangements might be described as “sales” or as “conditional sales,” but revenue recognition would not be appropriate until the consigned goods are later sold to a third-party purchaser.
Careful analysis of the rights and obligations of the parties and the risks borne by each at various stages of the transactions should reveal when and whether an actual sale has occurred and whether revenue recognition is warranted. In general, if the buyer has a right to return the product in question, coupled with a deferred or conditional payment obligation and/or significant remaining performance obligations by the seller, revenue will not be recognizable by the seller at the time of initial delivery. Similarly, if there is an implicit or explicit obligation by the seller to repurchase the item transferred, a real sales transaction has not occurred. The buyer must assume the risks of ownership in all cases if revenue is to be recognized.
With regard to whether delivery has occurred or services have been rendered, ownership and risk taking must have been transferred to the buyer if revenue is to be recognized by the seller. Thus, if the seller is holding goods for delivery to the buyer because the buyer's receiving dock workers are on strike and no deliveries are being accepted, revenue generally cannot be recognized in the reporting period, even if these delayed deliveries are made subsequent to period end. (There are limited exceptions to this general principle, typically involving a written request from the buyer for delayed delivery under a “bill-and-hold“ arrangement, having a valid business purpose.)
The SEC frowns upon bill-and-hold transactions. It will generally not allow revenue recognition in either of the following circumstances:
The SEC bases its opinion on the underlying concepts that revenue recognition does not occur until the customer takes title to the goods and assumes the risks and rewards of ownership. Consequently, the SEC uses all of the following criteria when determining whether revenue should be recognized:
The SEC further states that generally delivery has not occurred unless the product has been delivered to either the customer or another site specified by the customer. If the customer specifies delivery to a staging site but a substantial portion of the sales price is not payable until delivery is ultimately made to the customer, then revenue recognition must be delayed until final delivery to the customer has been completed.
Delivery, as used here, implies more than simply the physical relocation of the goods to the buyer's place of business. Rather, it means that the goods have actually been accepted by the customer, which, depending on the terms of the relevant contract, could be conditioned on whether inspection, testing, and/or installation have been completed, and the buyer has committed to pay for the items purchased. For revenue recognition to be justified, substantial performance of the terms of delivery must have occurred, and if any terms remain uncompleted, there should be a basis grounded on historical experience to assume that these matters will be satisfactorily attended to.
In some instances there are multiple “deliverables.” In such cases, revenue is not recognized for any given element if later deliverables are essential for the functionality of the already delivered element. In other situations, such as in various licensing arrangements, physical “delivery” may occur well before product usage by the buyer can take place (e.g., software for the future year's tax preparation delivered before the current year end), and revenue is not to be recognized prior to the initial date of expected use by the buyer.
The SEC holds that revenue should not be recognized until such time as any uncertainty about customer acceptance of goods or services has been eliminated. This requires an examination of customer acceptance provisions in the purchase agreement. For example, the agreement may allow the customer to test the product or require additional services subsequent to delivery, such as product installation. If these provisions exist, the SEC assumes that the customer specifically bargained for their inclusion in the agreement, which makes them substantive parts of the agreement. Consequently, revenue cannot be recognized until either the customer has accepted the goods or services, or the acceptance provisions have lapsed.
The SEC states that formal customer sign-off on a contractual customer acceptance provision is not always necessary. Instead, the seller can demonstrate that the criteria specified in the acceptance provisions are satisfied.
The SEC considers customer acceptance provisions to take one of four general forms, which are:
This is perhaps the most subjective of the four forms of customer acceptance, so the SEC states that it will not object to a determination that is well reasoned on the basis of the guidance just described.
In the case of many service transactions, large up-front fees are often charged, nominally in recognition of the selling of a membership, the signing of a contract, or for enrolling the customer in a program. (For example, initiation fees to join a health club where the terms of membership also obligate the member to pay ongoing fees.) Unless the services provided to the customer at inception are substantial, the presumption is that the revenue received has not been earned, but rather must be deferred and recognized, usually ratably, over the period that substantive services are provided. Thus, initiation fees are amortized over the membership period.
In cases where the seller is providing a service and requires an up-front fee, the SEC prefers that the fee be accounted for as revenue on a straight-line basis; this recognition shall be either over the term of the arrangement or the expected period during which services are to be performed, whichever is longer. The only situation where revenue is not recognized on a straight-line basis is when revenue is earned or obligations are fulfilled in a different pattern.
Even in cases where the seller's obligations to the buyer are inconsequential or perfunctory, the SEC believes that the substance of these transactions indicates that the buyer is paying for a service that is delivered over a period of time, which therefore calls for revenue recognition over the period of performance.
The seller's price to the buyer is fixed or determinable when a customer does not have the unilateral right to terminate or cancel the contract and receive a cash refund. Depending on customary practice, extended return privileges might imply that this condition has not been met in given circumstances. Prices that are conditional on the occurrence of future events are not fixed or determinable from the perspective of revenue recognition.
In theory, until the refund rights have expired, or the specified future events have occurred, revenue should not be recognized. As a practical matter, however, assuming that the amount of refunds can be reliably estimated (based on past experience, industry data, etc.), revenues, net of expected refunds, can be recognized on a pro rata basis. Absent this ability to reliably estimate, however, revenue recognition is deferred.
The final factor, reasonable assurance of collectibility, implies that the accrual for bad debts (uncollectible accounts receivable) can be estimated with reasonable accuracy, both to accomplish proper periodic matching of revenue and expenses, and to enable the presentation of receivables at net realizable value, as required under GAAP. An inability to accomplish this objective necessitates deferral of revenue recognition—generally until collection occurs, or at least until it becomes feasible to estimate the uncollectible portion with sufficient accuracy.
The SEC holds that revenue may be recognized in its entirety if the seller's remaining obligation is inconsequential or perfunctory. This means that the seller should have substantially completed the terms specified in the sales arrangement in order for delivery or performance to have occurred. Any remaining incomplete actions can only be considered inconsequential if the failure to complete them would not result in the customer receiving a refund or rejecting the products or services. Further, the seller should have a history of completing the remaining tasks in a timely manner, and of being able to estimate all remaining costs associated with those activities. If revenue is recognized prior to the completion of any inconsequential items, then the estimated cost of those inconsequential items should be accrued when the revenue is recognized.
An extreme situation, calling for not merely accrual of losses from estimated uncollectible receivables, is to defer revenue recognition entirely until collectibility is assured (or actually achieved). The most conservative accounting alternative, as set forth in CON 5, is to record revenue only as collected. It states: “(i)f collectibility of assets received for product, services, or other assets is doubtful, revenues and gains may be recognized on the basis of cash received” (emphasis added). The permissive language, which (it must be assumed) was deliberately selected in preference to a mandatory exhortation (e.g., “must”), suggests that even in such a situation this hyperconservative departure from accrual accounting is not truly prescriptive, but is a possible solution to a fact-specific set of circumstances.
Certain of the more attention-getting problems in applying the general principles of revenue recognition are discussed in the following paragraphs.
In general, it is well established that reporting on a “gross” basis is appropriate when the entity takes ownership of the goods being sold to its customers, with the risks and rewards of ownership accruing to it. For example, if the entity runs the risk of obsolescence or spoilage during the period it holds the merchandise, gross reporting would normally be appropriate. On the other hand, if the entity merely acts as an agent for the buyer or seller from whom it earns a commission, then “net” reporting would be more appropriate.
Enterprises may inflate the revenues reported in their income statements by reporting transactions on a “gross” basis, notwithstanding that the entity's real economic role is as an agent for buyer and/or seller. This distortion became widespread in the case of Internet commerce-based “dot-com companies” and other start-up and innovative businesses typically not reporting earnings, for which market valuations were heavily influenced by absolute levels of and trends in gross revenues. Reporting revenues “gross” rather than “net” often had an enormous impact on the perceived value of those enterprises.
Factors to consider in determining whether sales are properly reported “gross” or “net” include:
Most businesses must collect certain taxes which must subsequently be transmitted to governmental bodies, making the entity in effect an agent of the state. The most obvious example of this situation is the imposition of sales taxes, which are almost universally applicable to retail merchandise transactions and, increasingly, to service transactions as well. Historically accounting practice has varied, with some entities reporting gross revenue inclusive of taxes—which are then later reported as expenses when remitted—while other entities report revenue net of these taxes, treating them as purely a statement of financial position event. ASC 605-45-50-3 confirms that either methodology is acceptable, and if material, should be defined in the accounting policies note to the financial statements. As an elective accounting policy, accordingly, any change in method should be justified as being warranted as a means of improving financial reporting.
Barter transactions (nonmonetary exchanges, as described in ASC 845-10) are not a problem, assuming that they represent the culmination of an earnings process. However, in recent years there have been many reports of transactions that appear to have been concocted merely to create the illusion of revenue-generating activities. Examples include advertising swaps engaged in by some entities, most commonly “dot-com” enterprises, and the excess capacity swaps of fiber optic communications concerns under “indefeasible right to use” agreements. Both of these and many other situations involved immediate recognition of revenues coupled with deferred recognition of costs, and typically in aggregate were equal exchanges not providing profits to either party. Furthermore, these examples do not represent culminations of the normal earnings process (e.g., fiber optic networks were built in order to sell communications services to end users, not for the purpose of swapping capacity with other similar operations).
In hindsight, most observers can see why these and many other aggressive reporting practices deviated from established or implied GAAP; although there are still some who insist that because GAAP failed to explicitly address these precise scenarios, the accounting for the transactions was open to interpretation. Since GAAP (even the highly rules-based U.S. GAAP) cannot possibly hope to overtly address all the various innovative transaction structures that exist and will be invented, it is necessary to apply basic principles and reason by analogy to newly emerging circumstances. Of great importance to financial statement preparers (and internal and external auditors) is obtaining a thorough understanding of the nature and normal operations of the business enterprise being reported upon, application of “substance over form” reasoning, and the goal of faithfully representing the economics of transactions.
Many difficult issues of revenue recognition involve practices that may or may not involve GAAP departures, depending on the situation-specific facts and circumstances. Channel stuffing, a prime example of this issue, occurs when sales are actually made prior to the period-end cutoff but may have been stimulated by “side agreements,” such as a promise to customers of extended return privileges or more liberal credit terms. In such circumstances, there might be a greater likelihood that a substantial portion of these sales may be subsequently nullified, as unrealistically large orders inevitably lead to later large returns made for full credit.
For purposes of financial reporting under GAAP, valuation allowances should be established for expected sales returns and allowances. (In practice, however, this is rarely done because the amounts involved are immaterial, unlike the amounts of the more familiar allowances for uncollectible accounts.) The use of valuation accounts for anticipated returns and allowances is dictated by both the matching concept (recording returns and allowances in the same fiscal period in which the revenue is recognized) as well as by the requirement to present accounts receivable at net realizable value. When the potential product returns are not subject to reasonable estimation (as when a sales promotion effort of the type just described is first being attempted by the reporting entity) but could be material, it might not be permissible to recognize revenues at all, pending subsequent developments. (ASC 605-15-25) Furthermore, from the SEC's perspective, factors such as the following could require deferral of revenues at the time goods are shipped to customers, pending resolution of material uncertainties:
Not all revenue recognition errors and frauds involve questions of when or if revenue should be recognized. In some instances, classification in the income statement is of greater concern. While matters in this group often do not result in a distortion of net results of operations, they can seriously distort important indicators of performance trends. When this occurs, it most often involves reporting unusual or infrequent gains on sales of segments or specific assets as revenue from product or service transactions. A variation on this involves reporting unusual gains as offsets to one or more categories of operating expenses, similarly distorting key financial ratios and other indicators, again without necessarily invalidating the net income measure.
Transfers of inventory or other assets to a related entity typically defer gain or income recognition until subsequent transfer to an “arm's-length” party. In some cases, sales have been disguised as being to unrelated entities with gain being recognized, when in fact the “buyer” was a nominee of the seller, or the financing was provided or guaranteed by the seller, or the “buyer” was a “variable interest entity” that failed to meet the complex and changing requirements under GAAP required for gain recognition. Depending upon the facts of the situation, this can result in gains being improperly recognized, or the gross amount of the transaction being improperly recognized in the seller/transferor's financial statements.
This issue again ranges from deliberate but real economic transactions that have as a goal the inflation of reportable revenues or gains, to misrepresented events having no economic substance but the same objective. Among the former is the deliberate invasion of low-cost LIFO inventory “layers,” which boosts gross margins and net profits for the period, albeit at the cost of having to later replenish inventories with higher-cost goods. To the extent that this depletion of lower-cost inventory really occurs, there is no GAAP alternative to reflecting these excess profits currently, although the threat of full disclosure may prove to be somewhat of a deterrent.
Regarding the latter category, in some instances the ability to generate gains could indicate that errors occurred in recording a previous transaction. Thus, large gains flowing from the sale of assets recently acquired in a purchase business combination transaction could well mean the purchase price allocation process was flawed. If this is true, a reallocation of purchase price would be called for, and some or all of the apparent gains would be eliminated.
Related to the foregoing is the strategy of retiring outstanding debt to generate reportable gains. In periods of higher-than-historically-typical interest rates, lenders will often agree to early extinguishment of outstanding low-coupon obligations at a discount, hence creating accounting gains for the borrower, albeit replacement debt at current yields will result in higher interest costs over future years. To the extent the debt is really retired, however, this is a real economic event, and the consequent gain is reported in current earnings under GAAP.
Under ASC 605-35 (detailed later in this chapter), profits on certain long-term construction-type contracts are recognized ratably over the period of construction. An obvious and often easy way to distort periodic results of operations is to deliberately over- or understate the degree to which one or more discrete projects has been completed as of period end. This, coupled with the difficulty and importance of estimating remaining costs to be incurred to complete each project, makes profit recognition under this required method of accounting challenging to verify.
See the Appendix to this Chapter for information on ASU 2014-09.
Accounting for long-term construction contracts involves questions as to when revenue is to be recognized and how to measure the revenue to be recorded. The basic GAAP governing the recognition of long-term contract revenue is contained in ASC 605-35 and ASC 910.
The accounting for long-term construction contracts is complicated by the need to rely upon estimates of revenues, costs to be incurred, and progress toward completion.
In the process of codifying GAAP, the Financial Accounting Standards Board (FASB) made certain technical corrections to eliminate inconsistencies in the previously promulgated authoritative long-term contract literature.
The corrections clarify that:
Back Charges. Billings for work performed or costs incurred by one party (the biller) that, in accordance with the agreement, should have been performed or incurred by the party billed.
Change Order. A legal document executed by a contractor and customer (which can be initiated by either) that modifies selected terms of a contract (e.g., pricing, timing and scope of work) without the necessity of redrafting the entire contract.
Claims. Amounts in excess of the agreed contract price that a contractor seeks to collect from customers for customer-caused delays, errors in specifications and designs, unapproved change orders, or other causes of unanticipated costs. (ASC 605-35)
Combining Contracts. Grouping two or more contracts into a single profit center for accounting purposes.
Completed-Contract Method. A method of accounting that recognizes revenue only after the contract is complete.
Cost-to-Cost Method. A percentage-of-completion method used to determine the extent of progress toward completion on a contract. The ratio of costs incurred from project inception through the end of the current period (numerator) to the total estimated costs of the project (denominator) is applied to the contract price (as adjusted for change orders) to determine total contract revenue earned to date.
Estimated Cost to Complete. The anticipated additional cost of materials, labor, subcontracting costs, and indirect costs (overhead) required in order to complete a project at a scheduled time.
Percentage-of-Completion Method. A method of accounting that recognizes revenue on a contract as work progresses.
Precontract Costs. Costs incurred before a contract has been accepted (e.g., architectural designs, purchase of special equipment, engineering fees, and start-up costs).
Profit Center. A unit for the accumulation of revenues and costs for the measurement of contract performance.
Progress Billings on Long-Term Contracts. Requests for partial payments sent to the customer in accordance with the terms of the contract at agreed-upon intervals as various project milestones are reached.
Segmenting Contracts. Dividing a single contract or group of contracts into two or more profit centers for accounting purposes.
Subcontractor. A second-level contractor who enters into a contract with a prime (general) contractor to perform a specific part or phase of a construction project.
Substantial Completion. The point at which the major work on a contract is completed and only insignificant costs and potential risks remain.
Work-in-Progress ( WIP ). The accumulated construction costs of the project that have been incurred since project inception.
Long-term construction contract revenue is recognizable over time as construction progresses rather than at the completion of the contract. This “as earned” approach to revenue recognition is justified, because under most long-term construction contracts both the buyer and the seller (contractor) obtain legally enforceable rights. The buyer has the legal right to require specific performance from the contractor and, in effect, has an ownership claim to the contractor's work-in-progress. The contractor, under most long-term contracts, has the right to require the buyer to make progress payments during the construction period. The substance of this business activity is that revenue is earned continuously as the work progresses.
ASC 605-35 describes the two generally accepted methods of accounting for long-term construction contracts.
ASC 605-35 states that:
The percentage-of-completion method recognizes income as work on a contract (or group of closely related contracts) progresses. The recognition of revenues and profits is generally related to costs incurred in providing the services required under the contract.
Under this method, work-in-progress (WIP) is accumulated in the accounting records. At any point in time if the cumulative billings to date under the contract exceed the amount of the WIP plus the portion of the contract's estimated gross profit attributable to that WIP, then the contractor recognizes a current liability captioned “billings in excess of costs and estimated earnings.” This liability recognizes the remaining obligation of the contractor to complete additional work prior to recognizing the excess billing as revenue.
If the reverse is true, that is, the accumulated WIP and gross profit earned exceed billings to date, then the contractor recognizes a current asset captioned “costs and estimated earnings in excess of billings.” This asset represents the portion of the contractor's revenues under the contract that have been earned but not yet billed under the contract provisions. Where more than one contract exists, these assets and liabilities are determined on a project-by-project basis, with the accumulated assets and liabilities being separately stated on the statement of financial position. Assets and liabilities are not offset unless a right of offset exists. Thus, the net debit balances for certain contracts are not ordinarily offset against net credit balances for other contracts. An exception may exist if the balances relate to contracts that meet the criteria for combining described in ASC 605-35 and discussed later in this section.
Under the percentage-of-completion method, income is not based on cash collections or interim billings. Cash collections and interim billings are based upon contract terms that do not necessarily measure contract performance.
ASC 605-35 states that:
The completed-contract method recognizes income only when the contract is complete, or substantially complete.
Under this method, contract costs and related billings are accumulated in the accounting records and reported as deferred items on the statement of financial position until the project is complete or substantially complete. A contract is regarded as substantially complete if remaining costs of completion are immaterial. When the accumulated costs (WIP) exceed the related billings, the excess is presented as a current asset (inventory account). If billings exceed related costs, the difference is presented as a current liability. This determination is also made on a project-by-project basis with the accumulated assets and liabilities being separately stated on the statement of financial position. An excess of accumulated costs over related billings is presented as a current asset, and an excess of accumulated billings over related costs is presented in most cases as a current liability.
ASC 605-35 deems the percentage-of-completion method to be preferable when estimates are reasonably dependable and the following conditions exist:
ASC 605-35 presumes that contractors generally have the ability to produce estimates that are sufficiently dependable to justify the use of the percentage-of-completion method of accounting. Persuasive evidence to the contrary is necessary to overcome this presumption.
The principal advantage of the completed-contract method is that it is based on final results, whereas the percentage-of-completion method is dependent upon estimates for unperformed work. The principal disadvantage of the completed-contract method is that when the period of a contract extends into more than one accounting period, there will be an irregular recognition of income.
These two methods are not equally acceptable alternatives for the same set of circumstances. ASC 605-35 states that, in general, when estimates of costs to complete and extent of progress toward completion of long-term contracts are reasonably dependable, the percentage-of-completion method is preferable. When lack of dependable estimates or inherent hazards cause forecasts to be doubtful, the completed-contract method is preferable.
The completed-contract method may also be acceptable when a contractor has numerous relatively short-term contracts and when results of operations do not vary materially from those that would be reported under the percentage-of-completion method.
Based on the contractor's individual circumstances, a decision is made as to whether to apply completed-contract or percentage-of-completion accounting as the entity's basic accounting policy. If warranted by different facts and circumstances regarding a particular contract or group of contracts, that contract or group of contracts is to be accounted for under the other method with accompanying financial statement disclosures of this departure from the normal policy.
Precontract costs are costs incurred before a contract has been entered into, with the expectation of the contract being accepted and thereby recoverable through future billings. Precontract costs include architectural designs, costs of learning a new process, and any other costs that are expected to be recovered if the contract is accepted. ASC 720-15 requires that precontract costs be expensed as incurred, as they are the equivalent of start-up costs in other types of businesses. Consequently, precontract costs are not permitted to be included in WIP. Contract costs incurred after the acceptance of the contract are costs incurred toward the completion of the project and are accumulated in work-in-progress (WIP).
If precontract costs are incurred in connection with a current contract in anticipation of obtaining additional future contracts, those costs are nevertheless accounted for as costs of the current contract. If such costs are not incurred in connection with a current contract, then they must be expensed as incurred. There is no look-back provision permitted by this rule. A contractor may not retroactively record precontract costs as WIP if a contract is subsequently executed.
Contract costs are costs identifiable with or allocable to specific contracts. Generally, contract costs include all direct costs, such as direct materials, direct labor, and any indirect costs (overhead) allocable to the contracts. Contract costs can be broken down into two categories: costs incurred to date and estimated costs to complete.
The company may choose to defer costs related to producing excess goods in anticipation of future orders of the same item. Costs associated with excess production can be treated as inventory if the costs are considered recoverable.
These are the anticipated costs required to complete a project at a scheduled time. They are comprised of the same elements as the original total estimated contract costs and are based on prices expected to be in effect when the costs will be incurred.
The latest estimates are used to determine the progress toward completion. ASC 605-35 provides the practices to be followed when estimating costs to complete.
Systematic and consistent procedures are to be used. These procedures are to be correlated with the cost accounting system in order to facilitate a comparison between actual and estimated costs. Additionally, the determination of estimated total contract costs is to identify the significant cost elements.
Estimated costs are to reflect any expected price increases. These expected price increases are not “blanket provisions” for all contract costs, but rather specific provisions for each specific type of cost. Expected increases in each of the cost elements, such as wages, materials, and overhead items, are considered separately.
Finally, estimates of costs to complete are to be reviewed periodically to reflect new information. Estimates of costs are to be examined for price fluctuations and reviewed for possible future problems, such as labor strikes or direct material delivery delays.
Accounting for contract costs is similar to accounting for inventory. Costs necessary to ready the asset for sale (transfer of possession and occupancy by the customer) are recorded in WIP as incurred. WIP includes both direct and indirect costs but not general and administrative expenses or selling expenses, since by definition they are not identifiable with a particular contract and are therefore treated as period costs. However, general and administrative expenses may be included in contract costs under the completed contract method since this could result in better matching of revenues and costs, especially in years when no contracts were completed.
Since a contractor may not be able to perform all facets of a construction project, one or more subcontractors may be engaged. Amounts earned by the subcontractor are included in contract costs as the work is completed. These amounts are directly attributable to the project and included in WIP, similar to direct materials and direct labor.
Contract costs may require adjustment for back charges. A back charge is a billing by the contractor to a subcontractor (or a reduction in the amount due to that subcontractor under the subcontract) for costs incurred by the contractor to complete or correct work that the contract stipulated was to have been performed by the subcontractor. These charges are often disputed by the parties involved.
Four types of contracts are distinguished based on their pricing arrangements: (1) fixed-price or lump-sum contracts, (2) time-and-materials contracts, (3) cost-type contracts, and (4) unit-price contracts.
Fixed-price contracts are contracts for which the price is not usually subject to adjustment because of costs incurred by the contractor. The contractor bears the risks of cost overruns.
Time-and-materials contracts are contracts that provide for payments to the contractor based on direct labor hours at fixed rates and the contractor's cost of materials.
Cost-type contracts provide for reimbursement of allowable or otherwise defined costs incurred plus a fee representing profits. Some variations of cost-plus contracts are (1) cost-without-fee: no provision for a fee, (2) cost-plus-fixed-fee: contractor reimbursed for costs plus provision for a fixed fee, and (3) cost-plus-award-fee: same as (2) plus provision for an award based on performance. The contract price on a cost-type contract is determined by the sum of the reimbursable expenditures and a fee. The fee is the profit margin (revenue less direct expenses) to be earned on the contract.
Unit-price contracts are contracts under which the contractor is paid a specified amount for every unit of work performed.
Contract costs (incurred and estimated to complete) are used to compute the gross profit or loss recognized. Under the percentage-of-completion method, gross profit or loss is recognized each period. The revenue recognized is matched against the contract costs incurred (similar to cost of goods sold) to determine gross profit or loss. Under the completed contract method, the gross profit or loss is determined at the substantial completion of the contract, and no revenue or contract costs are recognized until this point.
Additionally, inventoriable costs (accumulated in WIP) are never to exceed the net realizable value (NRV) of the contract. When contract costs exceed their NRV, they must be written down, requiring a contract loss to be recognized in the current period (this will be discussed in greater detail later). This is similar to accounting for inventory.
In practice, various methods are used to measure the extent of progress toward completion. The most common methods are the cost-to-cost method, efforts-expended method, units-of-delivery method, and units-of-work-performed method. Each of these methods of measuring progress on a contract can be identified as either an input or output measure.
The input measures attempt to identify progress on a contract in terms of the efforts devoted to it. The cost-to-cost and efforts-expended methods are examples of input measures. Under the cost-to-cost method, the percentage of completion is estimated by comparing total costs incurred from the inception of the job to date (numerator) to total costs expected for the entire job (denominator).
Output measures are made in terms of results by attempting to identify progress toward completion by physical measures. The units-of-delivery and units-of-work-performed methods are examples of output measures. Under both of these methods, an estimate of completion is made in terms of achievements to date.
Both input and output measures have drawbacks in certain circumstances. A significant problem of input measures is that the relationship between input and productivity is only indirect; inefficiencies and other factors can cause this relationship to change. A particular drawback of the cost-to-cost method is that costs of uninstalled materials and other up-front costs may produce higher estimates of the percentage-of-completion because of their early incurrence. These costs are excluded from the cost-to-cost computation or allocated over the contract life when it appears that a better measure of contact progress will be obtained.
A significant problem of output measures is that the cost, time, and effort associated with one unit of output may not be comparable to that of another. For example, because of the cost of the foundation, the costs to complete the first story of a twenty-story office building can be expected to be greater than the costs of the remaining nineteen floors.
Because ASC 605-35 recommends that “recognized income [is to] be that percentage of estimated total income…that incurred costs to date bear to estimated total costs,” the cost-to-cost method has become one of the most popular measures used to determine the extent of progress toward completion.
Under the cost-to-cost method, the percentage of revenue to recognize can be determined by the following formula:
By slightly modifying this formula, current gross profit can also be determined:
Some contractors adopt an accounting policy of not recognizing any gross profit on a contract that is less than 10% complete. This election is usually made for two reasons:
The GAAP effect of such a policy is usually immaterial and the accountant normally need not be concerned about it being a departure from GAAP.
When the current estimate of total contract costs exceeds the current estimate of total contract revenues, a provision for the entire loss on the entire contract is made. Losses are recognized in the period in which they become evident under either the percentage-of-completion method or the completed-contract method. The loss is computed on the basis of the total estimated costs to complete the contract, including the contract costs incurred to date plus estimated costs (use the same elements as contract costs incurred) to complete. The loss is presented as a separately captioned current liability on the statement of financial position.
In any year when a percentage-of-completion contract has an expected loss, the amount of the loss reported in that year is computed as follows:
The profit center for accounting purposes is usually a single contract, but under some circumstances the profit center may be a combination of two or more contracts, a segment of a contract, or a group of combined contracts. The contracts must meet requirements in ASC 605-35 in order to combine, or segment; otherwise, each individual contract is presumed to be the profit center.
For accounting purposes, a group of contracts may be combined if they are so closely related that they are, in substance, parts of a single project with an overall profit margin. Per ASC 605-35, a group of contracts may be combined if the contracts:
Segmenting a contract is a process of breaking up a larger unit into smaller units for accounting purposes. If the project is segmented, revenues are assigned to the different elements or phases to achieve different rates of profitability based on the relative value of each element or phase to the estimated total contract revenue. According to ASC 605-35, a project may be segmented if all of the following steps were taken and are documented and verifiable:
A project that does not meet the above criteria may still be segmented if all of the following are applicable:
Note that the criteria for combining and segmenting are to be applied consistently to contracts with similar characteristics and in similar circumstances.
Especially large or risky contracts are sometimes shared by more than one contractor. When the owner of the contract requests competitive bids, many contractors will form syndicates or joint ventures in order to bid on and successfully obtain a contract that each contractor individually could not perform.
When this occurs, a separate set of accounting records is maintained for the joint venture. If the percentages of interest for each of the participants are identical in more than one contract, the joint venture might keep its records in the same manner as it would if it was simply another construction company. Usually, the joint venture is for a single contract and ends upon completion of that contract.
A joint venture is a type of partnership, organized for a limited purpose. An agreement of the parties and the terms of the contract successfully bid upon will determine the nature of the accounting records. Income statements are usually cumulative statements showing totals from date of contract inception until reporting date. Each participant records its share of the amount from the venture's income statement less its previously recorded portion of the venture's income as a single line item similar to the equity method for investments. Similarly, statements of financial position of each participant present a single line asset balance, “investment in and advances to joint ventures.” In most cases, footnote disclosure is similar to the equity method and presents condensed financial statements of material joint ventures.
A participant in a collaborative arrangement recognizes revenue earned and costs incurred in transactions with third parties (parties that are not participants to the collaborative arrangement) in its income statement based on whether the participant is serving as a principal or an agent in the transaction under ASC 605-45. If the transacting participant is considered a principal in the transaction, the revenues and costs are recorded gross. If the transacting participant is considered an agent in the transaction, the revenues and costs are recorded net. Under no circumstances is a participant in a collaborative arrangement permitted to use the equity method to account for its activities associated with the collaborative arrangement.
ASC 605-45 does not provide a “bright-line” test that definitively would characterize the role of a participant in a transaction. Rather, it provides a series of indicators of gross reporting and a series of indicators of net reporting, the purpose of which is to enable management to analyze the facts and circumstances associated with the transaction to make a well-reasoned determination.
In evaluating the income statement characterization of transactions between participants to a collaborative arrangement, management is to consider:
If no authoritative GAAP is identified that is relevant directly or by analogy, management elects a reasonable and rational accounting policy to be consistently applied to all such similar transactions.
Change orders are modifications of specifications or provisions of an original contract. Contract revenue and costs are adjusted to reflect change orders that are approved by the contractor and customer. According to ASC 605-35, accounting for a change order depends on the scope and price of the change.
If the scope and price have both been agreed to by the customer and contractor, contract revenue and cost are both adjusted to reflect the change order.
According to ASC 605-35, accounting for unpriced change orders depends on their characteristics and the circumstances in which they occur. Under the completed-contract method, costs attributable to unpriced change orders are deferred as contract costs if it is probable that total contract costs, including costs attributable to the change orders, will be recovered from contract revenues. Recovery is deemed probable if the future event or events are likely to occur.
Per ASC 605-35, the following guidelines apply when accounting for unpriced change orders under the percentage-of-completion method:
However, since the substantiation of the amount of future revenue is difficult, satisfaction of the condition of “realization beyond a reasonable doubt” should only be considered satisfied in circumstances in which an entity's historical experience provides such assurance or in which an entity has received a bona fide pricing offer from a customer and records only the amount of the offer as revenue.
Per ASC 605-35, an addition or option to an existing contract is treated as a separate contract if any of the following circumstances exist:
If the addition or option does not meet the above circumstances, the contracts are combined unless the addition or option does not meet the criteria for combining, in which case it is treated as a change order.
Claims represent amounts in excess of the agreed-upon contract price that a contractor seeks to collect from customers for unanticipated additional costs. The recognition of additional contract revenue relating to claims is appropriate if it is probable that the claim will result in additional revenue and if the amount can be reliably estimated. ASC 605-35 specifies that all of the following conditions must exist in order for the probable and estimable requirements to be satisfied:
When the above requirements are met, revenue from a claim is recorded only to the extent that contract costs relating to the claim have been incurred.
When the above requirements are not met, ASC 605-35 states that a contingent asset is disclosed in accordance with ASC 450.
ASC 250 requires retroactive restatement as the standard methodology to be used for accounting for changes in accounting principle, including changes in the accounting for long-term construction contracts. (See the chapter on ASC 205 for further discussion.)
Revisions in revenue, cost, and profit estimates or in measurements of the extent of progress toward completion are changes in accounting estimates. These changes are accounted for prospectively in order for the financial statements to fully reflect the effects of the latest available estimates.
Services represent over half of the transactions occurring in the US economy, but there is no official codification of accounting standards that provides specific accounting rules for them. Accounting for service transactions has evolved primarily through industry practice, and as a result, different accounting methods have developed to apply the fundamental principles of revenue and cost recognition. In fact, different accounting methods are used by similar entities for practically identical transactions.
The discussion in this section should still provide relevant guidance on service industry issues. In addition, the guidance provided by the SEC in Staff Accounting Bulletin 101 and its replacement, SAB 104, discussed in the introductory materials to this chapter, is highly relevant to accounting for service transactions and should be deemed pertinent to accounting even by nonpublic reporting entities, inasmuch as it reflects the current thinking by an authoritative source of GAAP.
Collection Method. A method that recognizes revenue when cash is collected.
Completed Performance Method. A method that recognizes revenue after the last significant act has been completed.
Direct Costs. Costs that are related specifically to the performance of services under a contract or other arrangement.
Indirect Costs. Costs that are incurred as a result of service activities that are not directly allocable to specific contracts or customer arrangements.
Initiation Fee. A onetime, up-front charge that gives the purchaser the privilege of using a service or facilities.
Installation Fee. A onetime, up-front charge for making equipment operational so that it functions as intended.
Out-of-pocket Costs. Costs incurred incidental to the performance of services that are often reimbursable to the service firm by the customer either at actual cost or at an agreed-upon rate (e.g., meals, lodging, airfare, taxi fares, etc.).
Precontract or Preengagement Costs. Costs incurred prior to execution of a service contract or engagement letter.
Product Transaction. A transaction between a seller and a purchaser in which the seller supplies tangible merchandise to the purchaser.
Proportional Performance Method. A method that recognizes revenue on the basis of the number of acts performed in relation to the total number of acts to be performed.
Service Transaction. A transaction between a seller and a purchaser in which the seller performs work, or agrees to maintain a readiness to perform work, for the purchaser.
Specific Performance Method. A method that recognizes revenue after one specific act has been performed.
Codification defines service transactions as follows:
…transactions between a seller and a purchaser in which, for a mutually agreed price, the seller performs, agrees to perform, agrees to perform at a later date, or agrees to maintain readiness to perform an act or acts, including permitting others to use enterprise resources that do not alone produce a tangible commodity or product as the principal intended result. (ASC 605-35-15-6j)
Generally accepted accounting principles require that revenue generally be recognized when (1) it is realized or realizable, and (2) it has been earned. With respect to service transactions:
…revenue from service transactions [is to] be based on performance, because performance determines the extent to which the earnings process is complete or virtually complete.
In practice, performance may involve the execution of a defined act, a set of similar or identical acts, or a set of related but not similar or identical acts. Performance may also occur with the passage of time. Accordingly, one of the following four methods can serve as a guideline for the recognition of revenue from service transactions:
Many transactions involve the sale of a tangible product and a service; therefore, for proper accounting treatment, it must be determined whether the transaction is primarily a service transaction accompanied by an incidental product, primarily a product transaction accompanied by an incidental service, or a sale in which both a service transaction and a product transaction occur. The following criteria apply:
Once a transaction is determined to be a service transaction, one of the following four methods is used to recognize revenue. The method chosen is to be based on the nature and extent of the service(s) to be performed.
Direct cost of individual act | × | Total revenues from complete transaction |
Total estimated direct costs of the transaction |
For example, a correspondence school that provides lessons, examinations, and grading would use this method. If the measurements suggested in the preceding equation are impractical or not objectively determinable, revenue is recognized on a systematic and rational basis that reasonably relates revenue recognition to service performance.
GAAP, in general, requires that costs be recognized as expense in the period that the revenue with which they are associated is recognized (the matching principle). Costs are deferred only when they are expected to be recoverable from future revenues. When applying these principles to service transactions, special consideration must be given to the different types of costs that might arise. The major classifications of costs arising from service transactions are as follows:
The costs listed above are accounted for as follows:
These are recognized when direct costs incurred to date plus estimated remaining direct costs of performance exceed the current estimated net realizable revenue from the contract. The loss (given as the Direct costs incurred to date + Estimated remaining direct costs − Estimated realizable revenue) is first applied to reduce any recorded deferred costs to zero, with any remaining loss recognized on the income statement and credited to an estimated liability.
Many service transactions also involve the charging of a nonrefundable initiation or activation fee with subsequent periodic payments for future services and/or a nonrefundable fee for installation of equipment essential to providing future services with subsequent periodic payments for the services. These nonrefundable fees may, in substance, be partly or wholly advance charges for future services.
If there is an objectively determinable value for the right or privilege granted by the fee, that value is recognized as revenue on the initiation date. Any related direct costs are recognized as expense on the initiation date. If the value of the right or privilege cannot be objectively determined, the fee is recorded as a liability for future services and recognized as revenue in accordance with one of the revenue recognition methods.
If the equipment and its installation costs are essential for the service to be provided and if customers cannot normally purchase the equipment in a separate transaction, the installation fee is considered an advance charge for future services. The fee is recognized as revenue over the estimated service period. The costs of installation and the installed equipment are amortized over the period the equipment is expected to generate revenue. If customers can normally purchase the equipment in a separate transaction, the installation fee is part of a product transaction that is accounted for separately as such.
Some elements of the accounting codification provide guidance to the accounting for service transactions. These are discussed in the following paragraphs.
ASC 605-20-25 addresses the manner in which revenue and expense pertaining to freight services in process as of the date of the statement of financial position are to be given financial statement recognition. It holds that recognition of revenue when freight is received from the shipper or when freight leaves the carrier's terminal, with expenses recognized as incurred, is not acceptable accounting.
While not limited to service providers, a common situation for many professional service providers is the incurrence of costs that are later billed to clients, with or without a mark-up over actual cost. Examples of out-of-pocket expenses include meals, lodging, airfares, taxi fares, etc. Prior practice had been varied, with many reporting entities showing reimbursements, implicitly as offsets to expenses; others reported such reimbursements as revenue. While the net effect on reported earnings was the same under either approach, certain key performance measures, such as gross revenue, could vary considerably depending on choice of accounting method. ASC 605-45-15 mandates that any billings for out-of-pocket costs are to be classified as revenue in the statement of income and not as a reduction in expenses. This guidance is equally applicable whether expenses are billed to clients (1) as a pass-through (i.e., at actual cost to the service firm without a markup), (2) at a marked-up amount, or (3) are included in the billing rate or negotiated price for the services.
Extended warranties provide additional protection beyond that of the manufacturer's original warranty, lengthen the period of coverage specified in the manufacturer's original warranty, or both. Similarly, a product maintenance contract is an agreement for services to maintain a product for a certain length of time. Clearly, revenue recognition at inception is not acceptable, and it is often impossible to estimate the actual pattern of service that will be provided to the customers over the terms of the contracts. ASC 605-20-25 directs that revenue from these contracts be deferred and recognized on a straight-line basis unless evidence exists that costs are incurred on some other basis. If so, revenue is allocated to each period using the ratio of the period's cost to estimated total cost.
Direct costs of obtaining extended warranty or maintenance contracts are to be capitalized and recognized as expense in the ratio that revenues recognized each period bear to total anticipated revenues from the respective contracts. Any other costs are charged to expense as incurred. Losses on these contracts are recognized immediately if the sum of the future costs and remaining unamortized direct acquisition costs exceed the related unearned revenue. When recognizing a loss, any unamortized acquisition costs are first charged to expense, and a liability for any remaining loss is then recorded.
Under GAAP, revenue recognition customarily does not depend upon the collection of cash. Accrual accounting techniques normally record revenue at the point of a credit sale by establishing a receivable. When uncertainty arises surrounding the collectibility of this amount, the receivable is appropriately adjusted by establishing a valuation allowance. In some cases, however, the collection of the sales price may be so uncertain that an objective measure of ultimate collectibility cannot be established. When such circumstances exist, the seller either uses the installment method or the cost recovery method to recognize the transaction. (ASC 605-10-25) Both of these methods allow for a deferral of gross profit until cash has been collected.
An installment transaction occurs when a seller delivers a product or performs a service and the buyer makes periodic payments over an extended period of time. Under the installment method, revenue recognition is deferred until the period(s) of cash collection. The seller recognizes both revenues and cost of sales at the time of the sale; however, the related gross profit is deferred to those periods in which cash is collected. Under the cost recovery method, both revenues and cost of sales are recognized at the time of the sale, but none of the related gross profit is recognized until the entire cost of sales has been recovered. Once the seller has recovered all cost of sales, any additional cash receipts are recognized as revenue. ASC 605-10-25 does not specify when one method is preferred over the other. However, the cost recovery method is more conservative than the installment method because gross profit is deferred until all costs have been recovered; therefore, it is appropriate for situations of extreme uncertainty.
Cost Recovery Method. The method of accounting for an installment basis sale whereby the gross profit is deferred until all cost of sales has been recovered.
Deferred Gross Profit. The gross profit from an installment basis sale that will be recognized in future periods.
Gross Profit Rate. The percentage computed by dividing gross profit by revenue from an installment sale.
Installment Method. The method of accounting for a sale whereby gross profit is recognized in each period in which cash from the sale is collected.
Installment Sale. A sales transaction for which the sales price is collected through the receipt of periodic payments over an extended period of time.
Net Realizable Value. The portion of the recorded amount of an asset expected to be realized in cash upon its liquidation in the ordinary course of business.
Realized Gross Profit. The gross profit recognized in the current period.
Repossessions. Merchandise sold by a seller under an installment arrangement that the seller physically takes back after the buyer defaults on the payments.
The installment method was developed in response to the increasing incidence of sales contracts that allowed buyers to make payments over several years. As the payment period becomes longer, the risk of loss resulting from uncollectible accounts increases; consequently, circumstances surrounding a receivable may lead to considerable uncertainty as to whether payments will actually be received. Under these circumstances, the uncertainty of cash collection dictates that revenue recognition be deferred until the actual receipt of cash.
The installment method can be used in most sales transactions for which payment is to be made through periodic installments over an extended period of time and the collectibility of the sales price cannot be reasonably estimated. This method is applicable to the sales of real estate (covered in the last section of this chapter), heavy equipment, home furnishings, and other merchandise sold on an installment basis. Installment method revenue recognition is not in accordance with accrual accounting, because revenue recognition is not normally based upon cash collection; however, its use is justified in certain circumstances on the grounds that accrual accounting may result in “front-end loading” (i.e., all of the revenue from a transaction being recognized at the point of sale with an improper matching of related costs). For example, the application of accrual accounting to transactions that provide for installment payments over periods of ten, twenty, or thirty years may underestimate losses from contract defaults and other future contract costs.
When a seller uses the installment method, both revenue and cost of sales are recognized at the point of sale, but the related gross profit is deferred to those periods during which cash will be collected. As receivables are collected, a portion of the deferred gross profit equal to the gross profit rate times the cash collected is recognized as income. When this method is used, the seller must compute each year's gross profit rate and also must maintain records of installment accounts receivable and deferred revenue that are separately identified by the year of sale. All general and administrative expenses are normally expensed in the period incurred.
The steps to use in accounting for sales under the installment method are as follows:
Alternatively, the gross profit rate can be computed as follows:
Gross profit rate | = | Installment sales revenue − Cost of installment sales |
Installment sales revenue |
Realized gross profit | = | Cash collections from the current year's installment sales | × | Current year's gross profit rate |
Realized gross profit | = | Cash collections from the previous years' installment sales | × | Previous years' gross profit rate |
Deferred gross profit (20X1) | = | Ending balance installment account receivable (20X1) | × | Gross profit rate (20X1) |
If installment sales transactions represent a significant portion of the company's total sales, the following three items of gross profit would, theoretically, be reported on the company's income statement:
The statement of financial position presentation of installment accounts receivable depends upon whether installment sales are a normal part of operations. If a company sells most of its products on an installment basis, installment accounts receivable are classified as a current asset because the operating cycle of the business (the length of which is to be disclosed in the notes to the financial statements) is the average period of time covered by its installment contracts. If installment sales are not a normal part of operations, installment accounts receivable that are not to be collected for more than a year (or the length of the company's operating cycle, if different than a year) are reported as noncurrent assets. In all cases, to avoid confusion, it is desirable to fully disclose the year of maturity next to each group of installment accounts receivable.
Accounting for deferred gross profit is addressed in CON 6 which states that deferred gross profit is not a liability. The reason is that the seller company is not obligated to pay cash or provide services to the customer. Rather, the deferral arose because of the uncertainty surrounding the collectibility of the sales price. CON 6 goes on to say, “deferred gross profit on installment sales is conceptually an asset valuation allowance (sometimes referred to as a ‘contra asset’)—that is, a reduction of an asset.” However, in practice, deferred gross profit is generally presented either as unearned revenue classified in the current liability section of the statement of financial position or as a deferred credit displayed between liabilities and equity.
The previous examples ignored interest, a major component of most installment sales contracts. It is customary for the seller to charge interest to the buyer on the unpaid installment receivable balance. Generally, installment contracts call for equal payments, each with an amount attributable to interest on the unpaid balance and the remainder to the installment receivable balance. As the maturity date nears, a smaller amount of each installment payment is attributable to interest and a larger amount is attributable to principal. Therefore, to determine the amount of gross profit to recognize, the interest must first be deducted from the installment payment and then the difference (representing the principal portion of the payment) is multiplied by the gross profit rate as follows:
The interest portion of the installment payment is recorded as interest revenue at the time of the cash receipt. Appropriate accounting entries are required to accrue interest revenue when the collection dates do not correspond with the period end.
The standard accounting treatment for uncollectible accounts is to accrue a bad debt loss in the year of sale by estimating the amount expected to be uncollectible. This treatment is consistent with the accrual and matching concepts. However, just as revenue recognition under the accrual basis is sometimes abandoned for certain installment basis sales, the accrual basis of recognizing bad debts is also sometimes abandoned.
When the installment method is used, it is usually appropriate to recognize bad debts by the direct write-off method (i.e., bad debts are not recognized until the receivable has been determined to be uncollectible). This practice is acceptable because most installment contracts contain a provision that allows the seller to repossess the merchandise when the buyer defaults on the installment payments. The loss on the account may be eliminated or reduced because the seller has the option of reselling the repossessed merchandise. To write off an uncollectible installment receivable, the following three steps are followed:
The cost recovery method does not recognize any income on a sale until the cost of the item sold has been fully recovered through cash receipts. Once the seller has recovered all costs, any subsequent cash receipts are included in income. The cost recovery method is used when the uncertainty of collection of the sales price is so great that even use of the installment method cannot be justified.
Under the cost recovery method, both revenues and cost of sales are recognized at the point of sale, but the related gross profit is deferred until all costs of sales have been recovered. Each installment must also be divided between principal and interest, but unlike the installment method where a portion of the principal recovers the cost of sales and the remainder is recognized as gross profit, all of the principal is first applied to recover the cost of the asset sold. After all costs of sales have been recovered, any subsequent cash receipts are realized as gross profit.
In some industries, it is common practice for customers to have the right to return a product to the seller for a credit or refund. However, for companies that experience a high ratio of returned merchandise to sales, the recognition of the original sale as revenue is questionable. In fact, certain industries have found it necessary to defer revenue recognition until the return privilege has substantially expired. Sometimes the return privilege expires soon after the sale, as in the newspaper and perishable food industries. In other cases, the return privilege may last over an extended period of time, as in magazine and textbook publishing and equipment manufacturing. The rate of return normally is directly related to the length of the return privilege. An accounting issue arises when the recognition of revenue occurs in one period while substantial returns occur in later periods.
ASC 605-15-25 reduced the diversity in the accounting for revenue recognition when such rights exist.
Deferred Gross Profit. The gross profit from a sale that is recognized in future periods because of the uncertainty surrounding the collection of the sales price.
Return Privilege. A right granted to a buyer by express agreement with a seller or by customary industry practice that allows the buyer to return merchandise to the seller within a stated period of time.
ASC 605-15-25 provides criteria for recognizing revenue on a sale in which a product may be returned (as a matter of contract or a matter of industry practice), either by the ultimate consumer or by a party who resells the product to others. Paragraph 25-1 states the following:
If an enterprise sells its product but gives the buyer the right to return the product, revenue from the sales transaction [is] recognized at time of sale only if all of the following conditions are met:
- The seller's price to the buyer is substantially fixed or determinable at the date of sale.
- The buyer has paid the seller, or the buyer is obligated to pay the seller and the obligation is not contingent on resale of the product.
- The buyer's obligation to the seller would not be changed in the event of theft or physical destruction or damage of the product.
- The buyer acquiring the product for resale has economic substance apart from that provided by the seller.
- The seller does not have significant obligations for future performance to directly bring about the resale of the product by the buyer.
- The amount of future returns can be reasonably estimated. For purposes of this statement “returns” do not include exchanges by ultimate customers of one item for another of the same kind, quality, and price.
If all of the above conditions are met, the seller recognizes revenue from the sales transaction at the time of the sale and any costs or losses expected in connection with returns are accrued in accordance with ASC 450, Contingencies. ASC 450 states that estimated losses from contingencies are accrued and charged to income when it is both probable that an asset has been impaired or a liability has been incurred, and the amount of loss can be reasonably estimated.
The interplay between ASC 605-15 and ASC 450 needs further explanation. Although ASC 605-15 requires under condition f. that the amount of returns be reasonably estimated, it does not reference the ASC 450 loss accrual criteria. Accordingly, a strict interpretation of both ASC 605-15 and ASC 450 would indicate that only when the conditions for loss accrual under ASC 450 are met (i.e., the loss is both probable and reasonably estimable) would the condition f. above under ASC 605-15 also be met, and both sales and estimated returns can be recognized. However, a more literal interpretation of ASC 605-15 indicates that, by not cross-referencing ASC 450, the FASB intended that the sole criterion for return accrual under ASC 605-15 be the “reasonably estimated” condition f. Then, whether losses are probable or reasonably possible, they would be accrued under ASC 605-15 and the sales would also be recognized. If the likelihood of losses is remote, no disclosure is required under ASC 450, and condition f. under ASC 605-15 would be achieved and revenue would be recognized with no need to record an allowance for estimated returns. Under this theory, only if returns cannot be reasonably estimated, would recognition of revenue be precluded under ASC 605-15, regardless of whether losses are probable or reasonably possible.
If all six of the requirements were met, the following journal entries would be appropriate:
12/1/X1 | Accounts receivable | 90,000 | |
Sales (2,000 units × $45 per unit) | 90,000 | ||
To record sale of 2,000 textbooks | |||
12/31/X1 | Cash (600 units × $45 per unit) | 27,000 | |
Accounts receivable | 27,000 | ||
To record cash receipts for the month | |||
Cost of sales | 60,000 | ||
Inventory (2,000 units × $30 per unit) | 60,000 | ||
To record cost of goods sold for the month | |||
Sales (15% × 2,000 units × $45 per unit) | 13,500 | ||
Cost of sales (15% × 2,000 units × $30 per unit) | 9,000 | ||
Deferred gross profit on estimated returns (15% × 2,000 units × $15 per unit) | 4,500 | ||
To record estimate of returns | |||
1/1/X2 | Cash | 54,000 | |
to | Accounts receivable | 54,000 | |
3/31/X2 | To record cash receipts | ||
Inventory (160 units × $30 per unit) | 4,800 | ||
Deferred gross profit on estimated returns | 2,400 | ||
Accounts receivable (160 units × $45 per unit) | 7,200 | ||
To record actual returns | |||
3/31/X2 | Cost of sales (140 units × $30 per unit) | 4,200 | |
Deferred gross profit on estimated returns | 2,100 | ||
Sales (140 units × $45 per unit) | 6,300 | ||
To record expiration of return privileges and adjust estimate to actual |
The revenue and cost of goods sold recognized in 20X1 are based on the number of units expected to be returned, 300 (15% × 2,000 units). The net revenue recognized is $76,500 (85% × 2,000 units × $45 per unit) and the cost of goods sold recognized is $51,000 (85% × 2,000 units × $30 per unit). The deferred gross profit balance is carried forward until either the textbooks are returned or the return privilege expires.
If all of the six conditions are not met, revenue and cost of sales from the sales transactions must be deferred until either the return privilege has substantially expired or the point when all the conditions are subsequently met is reached, whichever comes first.
If the facts in the Lipkis case were altered so that the bookstores were not required to pay Lipkis until the later of the date the books were actually sold, or the expiration date of the return privilege, condition b. would not be met until the store remitted payment. The following entries would be required. The return privilege is, of course, assumed to lapse when the books are sold to final customers.
12/1/X1 | Inventory on consignment | 60,000 | |
Inventory | 60,000 | ||
To record shipment of 2,000 units to retail bookstores on consignment (2,000 units × $30 = $60,000) | |||
12/31/X1 | Cash (600 units × $45 per unit) | 27,000 | |
Sales | 27,000 | ||
To record cash receipts for December | |||
Cost of sales (600 units × $30 per unit) | 18,000 | ||
Inventory on consignment | 18,000 | ||
To record cost of goods sold for December | |||
1/1/X2 | Cash | 54,000 | |
to | Sales (1,200* units × $45 per unit) | 54,000 | |
3/31/X2 | To record cash receipts | ||
Cost of sales (1,200 units × $30 per unit) | 36,000 | ||
Inventory on consignment | 36,000 | ||
To record cost of goods sold on cash receipts | |||
Inventory (160 units × $30 per unit) | 4,800 | ||
Inventory on consignment | 4,800 | ||
To record product returns | |||
3/31/X2 | Accounts receivable (40 units × $45 per unit) | 1,800 | |
Sales | 1,800 | ||
To record expiration of return privilege on remaining units | |||
Cost of sales (40** units × $30 per unit) | 1,200 | ||
Inventory on consignment | 1,200 | ||
To record cost of goods sold on products for which return privilege expired | |||
*1,800 units paid for − 600 units paid for in December | |||
**2,000 units sold − 160 units returned − 1,800 units paid for |
Future returns cannot be estimated. In the relatively unlikely situation where the reporting entity is unable to make a reasonable estimate of the amount of future returns, the sale cannot be recognized until the return privilege has expired or conditions permit the loss to be estimated, at which point it would become reportable. Examples of factors that might impair the ability to reasonably estimate a loss are:
Another longstanding difficulty has been identifying authoritative guidance germane to the accounting for revenue arrangements (product or service sales) having more than one “deliverable.” Many instances of aggressive accounting—where all or most of the total revenue was recognized at the time of delivery of the first of multiple deliverables—have come to light. ASC 605-25 comprehensively addressed these complex issues.
Vendors may offer customers many related and unrelated products and services sold together (“bundled”) or separately. The prices assigned to the various elements of a particular transaction or series of transactions on the seller's invoices and the timing of issuing those invoices are not always indicative of the actual earning of revenue on the various elements of these transactions. ASC 605-25 provides guidance on how to measure consideration received from complex, multi-element arrangements and how to allocate that consideration between the different deliverables contained in the arrangement.
The guidance provided in this Codification Topic is extensive and complex, due to the complex nature of the underlying revenue transactions. A number of key terms are used, defined as follows:
Arrangements between vendors and their customers often include the sale of multiple products and services (deliverables). A multiple deliverable arrangement (MDA) can be structured using fixed, variable, or contingent pricing or combinations thereof. Product delivery and service performance can occur at different times, and in different locations and customer acceptance can be subject to various return privileges, or performance guarantees.
ASC 605-25 provides guidance on:
In applying these rules, it is to be presumed that separate contracts, executed at or near the same time with the same entity or related parties, were negotiated as a package and are to be considered together in determining how many units of accounting are contained in an MDA. That presumption can be overcome by sufficient contradictory evidence.
ASC 605-25 collectively applies to all deliverables (i.e., products, services, and rights to use assets) covered by contractually binding written, oral, or implied arrangements.
Scope exceptions are provided for the following:
ASC 605-25 set forth three basic principles, the application of which is the subject of the discussion that follows:
The following table summarizes the criteria used in determining units of accounting for MDA within the scope of ASC 605-25 and is adapted from a decision diagram contained therein:
Criteria | Outcome | Result |
1. Does the delivered item have stand-alone value to the customer? | Yes | Go to criterion 2 |
No | Do not separate item | |
2. If the MDA includes a general right of return with respect to the delivered item, is delivery of the undelivered items probable and substantially controlled by the vendor? | Yes or Not Applicable | Delivered item is a separate unit of accounting |
No | Do not separate item |
This separability evaluation is to be applied consistently to MDA that arise under similar circumstances or that possess similar characteristics. The evaluation is to be performed at the inception of the MDA.
If consideration is allocated to a deliverable that does not qualify as a separate unit of accounting, then the reporting entity is required to:
The determination of whether total MDA consideration is fixed or determinable disregards the effects of refund rights or performance bonuses, if any.
After applying the decision criteria, the vendor may recognize an asset representing the cumulative difference, from inception of the MDA, between amounts recognized as revenue and amounts received or receivable from the customer (this is analogous to the asset “costs and estimated earnings in excess of billings” which is used in long-term construction accounting). The amount of such assets may not exceed the total amounts to which the vendor is legally entitled under the MDA, including fees that would be earned upon customer cancellation. The amount recognized as an asset would be further limited if the vendor did not intend to enforce its contractual rights to obtain such cancellation fees from the customer.
The financial statements of a vendor are to include the following disclosures, when applicable:
The major categories of revenue-generating transactions, for which specialized accounting standards have been developed, have been addressed in the earlier sections of this chapter. In the following paragraphs, various miscellaneous requirements are discussed.
A longstanding issue in financial reporting has been whether certain entities more accurately convey the nature of their operations by reporting as revenue only the “net” amount they retain when acting effectively as an agent for another entity. While in some situations the answer is obvious, in other cases it has been less clear. Historically this may not have been an urgent issue to be resolved, since users of financial statements were deemed capable of deriving correct inferences regardless of the manner of presentation of the income statement. However, in recent years an unfortunate trend developed, whereby analysts and others cited only revenue growth as an indicator of the entity's success, making the question of income statement presentation of revenue somewhat more important.
ASC 605-45 provides guidance on whether an entity is an agent for a vendor-manufacturer, and thus recognizes the net retainage (commission) for serving in that capacity, or whether that entity is a seller of goods (i.e., acting as a principal), and thus should recognize revenue for the gross amount billed to a customer and an expense for the amount paid to the vendor-manufacturer.
The codification identifies the following factors to be considered when determining whether revenue is to be reported as the net retainage (hereinafter, “net”) or the gross amount billed to a customer (“gross”). None of the indicators are presumptive or determinative, although the relative strength of each indicator is to be considered.
ASC 605-45 includes thirteen examples to assist in implementation.
The accounting for such equity issuances by the reporting entity is addressed by ASC 718. ASC 505-50 has resolved the proper accounting by the recipient of such payments.
In exchange for goods or services, an entity (the grantee) may receive equity instruments that have conversion or exercisability terms that vary based on future events, such as attainment of sales levels or a successful initial public offering. This issue describes the appropriate accounting if ASC 718 does not apply because the instruments received have underlyings based on either the grantee's or issuer's performance.
The grantee measures the fair value of the equity instruments received using the stock price and measurement assumptions as of the earlier of two dates. The first date is the date on which the grantee and the issuer reach a mutual understanding of both the terms of the equity-based compensation and the goods to be delivered (or services to be performed). The second date is the date at which the performance necessary to earn the equity is completed by the grantee, that is, the grantee's rights have vested.
If the terms of the equity agreement are dependent on the achievement of a market condition, the fair value of the instrument is to include the effects on fair value of the commitment to change the terms if the market condition is met. Pricing models are available to value path-dependent equity instruments.
If the terms of the equity agreement are dependent on the achievement of certain performance goals (beyond those that initially established the goods to be delivered or services to be performed), the fair value of the instrument is computed without the effects of the commitment to change the terms if the goals are met. If those goals are subsequently met, the fair value is adjusted to reflect the new terms and the adjustment is reported as additional revenue (as described in the Share-Based Payments section in Chapter 27).
ASC 605-50 provides guidance regarding the recognition, measurement, and income statement display of consideration given by a vendor to purchasers of the vendor's products. This consideration can be provided to a purchaser at any point along the distribution chain, irrespective of whether the purchaser receiving the consideration is a direct or indirect customer of the vendor. Examples of arrangements include, but are not limited to, sales incentive offers labeled as discounts, coupons, rebates, and “free” products or services as well as arrangements referred to as slotting fees, cooperative advertising, and buydowns. The issue does not apply to:
The issue also does not discuss the accounting for offers of free or discounted products or services that are exercisable after a customer has completed a specified cumulative level of revenue transactions or remained a customer for a specified time period (for example, “point” and loyalty programs).
ASC 605-50 contains the following separately addressed issues:
If the consideration is a “free” product or service or anything other than cash (including “credits” that the customer can apply against trade amounts owed to the vendor) or equity instruments, the cost of the consideration is characterized as an expense (as opposed to a reduction of revenue) when recognized in the vendor's income statement. ASC 605-50 contains fifteen examples of the application of this issue to various fact scenarios.
ASC 605-50 also addresses accounting issues from the standpoint of how the vendor's customer—either the end user or a reseller of the vendor's products or services—is to account for cash consideration it receives from its vendor.
In general, there is a rebuttable presumption that cash consideration received from a vendor is a purchase-price concession that should be recognized by the customer as a reduction of cost of goods sold (and/or the inventory of unsold units). This presumption is overcome if payment of the consideration is for either:
Any excess of cash consideration received by the customer over the fair value of the goods and/or services delivered to the vendor reduces the customer's cost of sales.
Vendors sometimes enter into binding arrangements that offer customers specified amounts of cash rebates or refunds payable in the future only if the customer remains a customer for a specified period of time, or purchases a specified cumulative dollar amount of goods or services from the vendor. In general, these arrangements are to be recorded by the customer as reductions of cost of sales by systematically allocating a portion of the benefits to be received to each transaction that results in progress toward meeting the target that results in earning the benefit. In order to use this pro rata accounting, however, the amount of the refund must be both probable and reasonably estimable (as those terms are defined in ASC 450). The codification provided indicators that, if present, may impair the customer's ability to determine that the refund is both probable and estimable:
If the rebate or refund is not considered both probable and estimable, it is not recognized by the customer until it is fully earned by reaching the specified milestone (e.g., the dollar amount of cumulative purchases is reached or the time period for remaining a customer has expired).
Changes in a customer's estimate of the amount of future rebates or refunds, and retroactive changes by a vendor to a previous offer are recognized using a “cumulative catch-up adjustment.” This is accomplished by the customer immediately charging or crediting cost of sales in an amount that will adjust the cumulative amounts recognized under the arrangement to the changed terms. Of course, if any portion of the adjustment impacts goods still in the customer's inventory, that portion would adjust the valuation of the inventory and not cost of sales.
The SEC observer cautioned registrants to consider whether certain transactions between vendors and customers (e.g., simultaneous agreements between the parties to purchase equal amounts of each other's goods) are covered by the provisions of ASC 845 regarding nonmonetary exchanges that are not the culmination of an earning process.
The rule described immediately above is applicable to situations in which cash consideration is received by a customer from a vendor, and is presumed to be a reduction of the prices of the vendor's products or services. Such incentives are to be characterized as a reduction of cost of sales when recognized in the customer's income statement. There are other instances, however, where consideration is a reimbursement for incentives offered to end users (e.g., retail customers) honored by the vendor's customer (retailer). The common example is coupons given to end users to be redeemed at the retailers offering the vendor's products for sale.
ASC 605-50-45-19 states that this guidance is limited to a vendor's incentive that meets all of the following criteria:
Sales incentives that do not meet all of the foregoing criteria are subject to the guidance in ASC 605-50-45-2 through 45-3, and ASC 605-50-45-12 through 45-14, as applicable.
There are cases, such as in the cell phone service industry, where companies provide services to their customers under arrangements that require the customers to purchase equipment in order to utilize those services. To spur demand, the companies provide incentives to the equipment manufacturers or resellers to reduce the selling price of the equipment. The accounting for this situation is addressed by ASC 605-50, which states that, if the consideration given by the service provider to the manufacturer or reseller can be linked contractually to the benefit received by the service provider's customers, then the service provider can use the guidance noted above in ASC 605-50 to properly characterize the consideration paid. If the form of consideration to be paid to the service provider's customers is not cash or the service provider does not control the type of consideration paid, then the service provider should record such payments as an expense. If the form of consideration to be paid to the service provider's customers is cash (such as a mail-in rebate), then the service provider should record such payments as a reduction of revenue. The service provider should disclose the nature of the incentive program and the amounts recognized in the statement of operations for the incentive program and their classification for each period presented.
The SEC has indicated in Accounting Standards Update (ASU) 2009-07 that it will not object if a registrant with vaccine manufacturing operations recognizes revenue from the sale of vaccines to federal government stockpile programs, even if product delivery and inventory segregation requirements have not been met. This exemption only applies to childhood disease vaccines, influenza vaccines, and other vaccines and countermeasures sold to a federal government stockpile program. A registrant using this exemption should disclose the transactions and their effect on the financial statements.
An arrangement may contain a performance-based incentive fee that will not be finalized until the end of a predetermined period of time; for example, a real estate management company may receive a bonus for attaining building occupancy above a specified level. The SEC has indicated in ASU 2010-04 that a registrant can either recognize such revenue at the end of the measurement period or the amount that would be due under the formula as if the contract were terminated at an interim date, though it prefers the first method. However, the SEC will object to measurements as of an interim period that are based on projected future results; it will only accept revenue recognition in an interim period that is based on management fees earned as of that date, as though the arrangement had been terminated at that time.
The milestone method can be used to recognize revenue related to research and development arrangements. A milestone is an event that occurs only due to vendor performance, and where there is substantive uncertainty that the event will be achieved. Also, the event will result in additional payments to the vendor. A milestone is not contingent solely upon the passage of time.
Under the milestone method, a vendor is allowed to recognize revenue that is contingent upon the achievement of a substantive milestone. Whether a milestone is considered achievable is decided at the beginning of the arrangement. To be substantive, the consideration a vendor earns by completing a milestone must be commensurate with either the vendor's performance to complete the milestone or the enhancement of value delivered. The consideration must also be related only to past performance, and be reasonable relative to the other deliverables and payments in the contract. It is acceptable if a vendor chooses to use some other method of revenue recognition that defers some portion of the consideration arising from a milestone.
The vendor must disclose its policy for the recognition of milestone payments as revenue, as well as a description of each arrangement involving milestone payments, and the amount of milestone consideration recognized during the period.
According to ASC 605-20-25-9, fees received for guaranteeing another entity's obligation are to be recognized as income over the guarantee period, rather than at the time of receipt, consistent with other standards governing service fee income recognition. The guarantor is to perform ongoing assessments of the probability of loss related to the guarantee and recognize a liability if the conditions in ASC 450 are met. Upon entering into a guarantee arrangement, the guarantor is required to recognize the stand-ready obligation under the guarantee. The contingent aspect of the guarantee would only be recognized if the conditions defined by ASC 450 are met.
The revenue recognition standard represents a major milestone in our efforts to improve and converge one of the most important areas of financial reporting. It will eliminate a major source of inconsistency in GAAP, which currently consists of numerous disparate, industry-specific pieces of revenue recognition guidance.
—Russell Golden, Chairman of the FASB
In May 2014, the Financial Accounting Standards Board (FASB) and the International Accounting Standards Board (IASB) jointly issued Revenue from Contracts with Customers, as respectively
Revenue recognition has often been a source of restatements and comments from regulators, such as the Securities and Exchange Commission (SEC). Revenue recognition guidance was initially found in FASB Concept Statement No. 5 which specifies that an entity should recognize revenue when realized or realizable and earned and Concept Statement No. 6 which defines revenues as inflows around flows or other enhancements of assets and/or settlements of liabilities from delivering goods or services as a result of the entity's ongoing major or central operations. In 1999, the SEC provided additional guidance to public, companies in SAB No. 101 (amended in 2003 by SAB No. 104 and codified in Topic 13). Additional U.S. guidance can be found in numerous industry-specific guidance, such as that for the software industry, construction contracts, real estate sales, and multiple-element arrangements. This industry guidance often addressed narrow issues and was not built on a common framework. This led to economically similar transactions accounted for differently. Even though there were two hundred separate pieces of guidance, there were still transactions where there was no guidance, specifically for service transactions.
Driven by the need to achieve simplification and consistency, the FASB and the IASB (the Boards) began a joint project in 2002. U.S. GAAP developed piecemeal and has broad concepts, but includes many industry-specific requirements and yet, there were some transactions for which there was no guidance. In some cases, the guidance resulted in different accounting for economically similar transactions.
The Boards issued an exposure draft in June 2010 that elicited over 1,000 comment letters. The Boards issued a revised ED in November 2011 and conducted numerous meetings and outreach activities before issuing the final standard. The basically converged, new standard is principles-based, eliminating the existing transaction- and industry-specific guidance. This move away from prescriptive guidance and bright lines increases the need for professional judgment, which in turn increases the need for expanded disclosures. To compensate for the lack of rules, the revenue standard provides significant application guidance.
ASU 2014-09:
ASU 2014-09 is over 700 pages long and was released in the following sections:
The FASB and the IASB believe the final documents meet two major goals— simplification of revenue recognition guidance and consistency globally and across entities, jurisdictions, markets and industries. According to FASB in Focus,3 the Boards believe that the standard meets their goals to:
(FASB in Focus, May 28, 2014)
The revenue standard provides a robust framework that is expected to simplify preparation of financial statements by reducing the sources of guidance and replacing them with a single source that users can understand. The revenue standard adds new guidance for contract modifications and consistent application for service contracts. The standard also provides guidance for related topics, such as warrantees, licenses, and when to capitalize the cost of obtaining a contract and some costs of fulfilling a contract.
In addition, the changes may affect customer loyalty programs. Companies will have to make new estimates. It is expected that entities will be reviewing their loyalty programs to evaluate their effects, if any, on revenue, and some companies may choose to amend contracts with customers.
The scope is wide, and the standard affects all public companies, nonpublic companies, and nonprofit organizations. The standard applies to contracts with customers and defines customer as:
…a party that has contracted with a company to obtain a good or service that is an output of the company's ordinary activities in exchange for consideration. (ASC 606-10-15-3)
Care should be taken to determine whether a contract is with a customer or if it is a collaborative effort. To make the recognition and measurement consistent with revenue transactions, the standard applies to transfers of nonfinancial assets, such as property and equipment that give rise to revenue. Revenue can be generated by contracts that are not with customers. Examples are alternative revenue programs of utilities and not-for-profit contributions. The standard is applicable to those transactions.
The following are outside the scope of the standard:
The guidance included in new subtopic ASC 340-40 applies only if the costs are incurred related to a contract under ASC 606. (ASC 606-10-5)
If a contract is partially within the scope of the standard and partially within the scope of other guidance, the entity should apply the other guidance first. That is, if the other standard specifies how to separate or initially measure parts of the contract, then the entity should apply those requirements first. The remaining portion is accounted for under the requirements of the new standard. If the other standard does not have applicable separate and/or initial measurement guidance, the entity should apply the revenue standard to separate and/or initially measure the contract. (ASC 606-10-15-4)
The objective of the standard is
…to establish the principles that an entity shall apply to report useful information to users of financial statements about the nature, amount, timing, and uncertainty of revenue and cash flows arising from a contract with a customer. (ASC 606-10-10-1)
In deciding on effective dates, the Boards wanted to strike the right balance between improving reporting standards as soon as possible and giving entities enough time to implement the broad and potentially significant changes. The Boards decided on a longer than usual implementation period because of the number of organizations and line items affected. Soon ofter the release of the standard, the Boards heard from many entities that they needed more time to implement the standard. The FASB issued ASU 2015–14, Revenue from Contracts with Customers (Topic 606): Deferral of Effective Dates. The ASU allows a one-year deferral for all entities from the original effective dates and for early adoption using the original adoption dates.
The ASU is effective as follows:
In effect, this means nonpublic entities have the following options:
Public entities include:
Entities have the option to implement the guidance through:
The full retrospective approach is transparent and may be effective for entities expecting to recognize revenue earlier. Under this method, all prior periods presented must be restated in equity in accordance with ASC 250. That is, entities must report the cumulative effect for the earliest year reported. The full retrospective approach can also be adopted using one or more of the optional practical expedients.
Using the modified retrospective approach, the entity recognizes the cumulative effect of initially adopting the standard as an adjustment to the opening balance of retained earnings in the annual period when the standard is adopted. If the entity issues comparative statements, then it reports revenue for prior years under the guidance in effect before adoption. Additional disclosures are required for entities using this approach.
Note: The standard includes practical expedients in other areas of the guidance for public and nonpublic entities.
The revenue standard articulates a core principle on which the new guidance is based:
…recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. (FASB ASC 606-10-05-3 et al)
To achieve this core principle, an entity should follow these five steps:
In reviewing a transaction, each of the five steps above may not be needed, and they may not always be applied sequentially. Note that the standard is not organized by these five steps, but the Boards believe the steps offer a methodology for entities to use when deciding the appropriate accounting for a transaction. The model is based on a control approach as opposed to the risk and rewards approach under current standards. However, risk and rewards are a factor when determining control for point in time revenue recognition. Each step encompasses new concepts, and entities will have to carefully analyze their contracts with customers as they transition to the new guidance.
Because there is a greater need to estimate, there is a greater need to disclose.
—Russell Golden, FASB Chairman, May 2014
Revenue is an extremely important metric, and the revenue standard requires all entities to make new disclosure requirements designed to provide better information to financial statement users about contracts with customers. The standard requires entities to disclose both quantitative and qualitative information that enables users of financial statements to understand the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers. The additional disclosures are partially driven by the increased judgment related to estimates required in the new guidance. The requirements are comprehensive and include quantitative and qualitative information. The ASU includes some exceptions for disclosure by nonpublic entities.
The SEC in SAB 74 (Topic 11M) requires public entities to provide disclosures regarding new authoritative guidance which has been issued, but not yet adopted, including:
In addition to the items mentioned above, the standard includes changes on contract costs, right of returns, warranties, principal vs. agent consideration, licenses, repurchase agreements, customer acceptance terms, and other areas.
The revenue standard does not supersede the SEC guidance. In the U.S., the SEC is currently considering the new guidance. It is expected to adopt the changes and significant changes are expected to Staff Accounting Bulletin (SAB) 13, Revenue Recognition. The SEC has indicated it will be keeping a close eye on implementation.
The SEC has offered early relief on revenue recognition implementation. Entities electing full retrospective adoption will not be held to a five-year presentation of restated revenue figures. Shelley Luisi of the SEC's Office of the Chief Accountant has stated that “they will not object if the retrospective application only applies in selected financial data to the years that are included in the audited financial statements. So any additional years included in selected financial data will not need to be retrospectively restated.” Ms. Luisi emphasized that disclosure will be critical to investors understanding the inconsistency.
The FASB and the IASB have established a joint Transition Resource Group (TRG) which aims to solicit, analyze, and discuss stakeholder issues and inform the Boards about potential implementation issues that could arise during the transition period. The Boards will then consider whether amendments or additional guidance are needed. The TRG will not issue guidance. The TRG consists of nineteen members, representing U.S. and international preparers, auditors, users from various industries, and public and private companies and organizations. The TRG, at its first meeting, defined its role as ensuring that comparability actually occurs upon implementation.
Dozens of issues have been brought by the Transition Resource Group (TRG) to the Boards' attention. The TRG decided that most of those did not need the action by the Boards. At a joint meeting of the Boards on February 18, 2015 two issues were discussed, and the Boards agreed to issue clarifying guidance on:
However, the Boards came to different conclusions on the substance of some of the changes and the methods to communicate those changes. The FASB issued an Exposure Draft in May 2015 on the two issues above—licenses and identifying performance obligations. On the latter, the Exposure Draft aims to reduce cost and complexity. For the former, the Exposure Draft seeks to increase the clarity and operability of the guidance.
The Boards held a second joint meeting on March 18, 2015 to discuss:
At the June 22, 2015 joint meeting of the FASB and IASB, principal versus agent issues were discussed. In August 2015, the FASB issued an Exposure Draft on principal versus agent considerations, with comments due October 15, 2015. In addition the FASB has directed its staff to draft an ASU on narrow scope improvements and practical expedients.
The issues and the actions being taken by the FASB are summarized below. For subsequent developments, readers should consult the FASB revenue recognition project page.
Issue | FASB Tentative Decisions |
Licenses and Identifying Performance Obligations | |
Determining the nature of an entity's promise in granting a license | Update the standard to include “Articulation B,” potentially requiring an entity to assess the utility of a license before characterizing it as functional (for example, software or a film) or symbolic (for example, a logo or a brand name). |
Determining when the entity should assess the nature of the entity's promise in granting a license | Update the standard to clarify that an entity many need to determine the nature of a license that is not a separate performance obligation in order to apply the guidance on whether a performance obligation is satisfied over time or at a point in time and the appropriate measure of progress. |
Determining when the sales-based and usage-based royalties constraint applies | Update the standard to clarify that rather than splitting a royalty (and applying both the royalty and general constraints to it), an entity would apply the royalty constraint if the license is the predominant feature to which the royalty relates. |
Contractual restrictions in license arrangements | Update the standard to clarify the contractual restrictions, such as those described in ASC 606-10-55-64, are attributes of the license and do not affect the identification of the promised goods or services. |
Identifying promised good or services | Update the standard to permit entities to evaluate the materiality of promises at the contract level and that, if the promises are immaterial, the entity would not need to evaluate such promises further. |
The concept of distinct within the context of the contract | Add illustrative examples and update the standard to define “separately identifiable,” reframe the separation criteria to focus on a bundle of goods or services. |
Shipping and handling services | Add guidance that clarifies that: shipping and handling activities that occur before control transfers to the customer are fulfillment: and allows entities to elect a policy to treat shipping and handling activities as fulfillment costs if they do not represent the predominant activity in the contract and they occur after control transfers. |
Narrow Scope Improvements and Practical Expedients | |
Contract modifications that occur prior to the date of initially applying the standard | Voted for the staff's Option C: Add guidance on a “use of hindsight” practical expedient that would permit an entity electing the full retrospective approach to account for a modified contract by determining the transaction price at the contract modification adjustment date and perform a single stand-alone selling price allocation (with the benefit of hindsight) to all satisfied and unsatisfied performance obligations in the contract from inception. FASB will also propose a technical correction to transition guidance to clarify that an entity using the full retrospective approach does not need to disclose the effect of the accounting change on affected financial statement line items in the period of adoption. The “use of hindsight” approach provides some relief, but entities will still be required to gather the data from contract inception for all performance obligations and determine stand-alone selling prices. |
Contracts completed prior to the earliest period presented under the full retrospective transition approach | Decided not to add a practical expedient because of concerns regarding comparability. The revenue standard currently includes a similar provision for entities that elect the modified retrospective approach. Clarify a completed contract is one for which substantially all of the revenue was recognized under revenue guidance in effect before the initial application of Topic 606. Update the guidance to allow an entity to apply the modified retrospective transition approach to all contracts. |
Gross versus net – presentation of sales taxes | Add a practical expedient for presentation of sales taxes. The practical expedient would allow an election for net reporting for all in-scope sales taxes with disclosure of the policy. FASB reporters must disclose if they opt for the policy election. |
Measurement date for determining the fair value of non-cash consideration | Clarify the guidance for determining the measurement date for noncash consideration, explaining that it is measured at contract inception. The FASB believes the clarification is consistent with the principles of the new standard. However, the FASB's decision will change practice significantly for equity instruments exchanged for goods or services. |
Application of the constraint on variable consideration to changes in the fair value of the non-cash consideration | Add guidance to apply the constraint on variable consideration only to transaction in which the fair value of noncash consideration might vary for reasons other than the form of the consideration. |
The application of the collectability criterion in Step 1 of the standard | Add guidance to clarify the guidance in ASC 606-10-25-7. Guidance will make clear that collectibility is not based on collecting all the consideration promised, but on what the entity will be entitled to in exchange for goods or services they will transfer to the customer. Add a criterion to the alternate recognition model that if collectibility is not probable, the entity should recognize revenue for the consideration received when the entity has control, has stopped transferring additional goods or services, and the consideration is nonrefundable. |
The requirements for when a contract does not meet that collectability criterion | Clarify the guidance on the collectibility threshold in Step 1. Clarify the objective of the threshold is to assess an entity's exposure to credit risk for the products transferred to the customer. The contract need not be legally terminated and the entity does not have to stop pursuing collection in order for the contract to be considered terminated for purposes of recognizing cash under the new standard. The modifications may better reflect the economic substance of the transactions. |
Implementation questions about the principal versus agent guidance in the standard | The Boards have requested additional research. FASB said that the new standard does not resolve some of the issues with the application of current guidance and may cause new issues. The FASB staff said that potential improvements might involve a broad clarification of principal vs. agent. |
Estimating the gross revenue if the entity is the principal but is unaware of amounts being charged directly by an intermediary to the transaction | No decision. The staff is performing additional outreach and research. |
Principal Versus Agent (Reporting Revenue Gross Versus Net) | |
Determining whether an entity's promise is to provide or to arrange | Reaffirmed the Topic 606 principle that an entity is the principal when it controls the promised good or service. The entity is an agent when it does not control the specified good or service before it is transferred. |
Unit of account for the principal versus agent evaluation | Update the standard to clarify that a specified good or service is a distinct good or service. And, depending on the circumstances, a good or service may be a right to an underlying good or service provided by another party. |
Application of the control principle | Update the guidance to clarify the application of the control principle for services. |
Control indicators | Update the guidance to clarify the role of the indicators in ASC 606-10-55-39, specifically that the indicators help the evaluation control, rather than override the evaluation; how each indicator relates to the control principle; and that one or more indicators may be more or less relevant depending on the contract. Also, update to clarify when the indicators indicate when an entity is a principal rather than an agent. |
Illustrative examples | Amend principal versus agent examples and add examples. |
Estimating gross revenue as a principal | The Board decided not to include the issue of estimating gross revenue as a principal in cases where the entity is a principal but does not know the price paid by the end customer to an agent. |
In addition to the ASU deferring the effective date, the FASB has responded to feedback by issuing two exposure drafts to amend ASU 2014-09:
As this book goes to press, the Board expects to issue an Exposure Draft on Narrow-Scope Improvements and Practical Expedients in the third quarter of 2015.
IASB Vice Chairman, Ian Mackintosh, and FASB Chairman Russell Golden both identified software, telecommunications, and real restate as industries that will be most affected.
May 2014 Announcement
Entities that currently apply industry-specific guidance will see the greatest impact and may face complex implementation challenges. Industries most affected include:
Vendor-specific objective evidence (VSOE) is no longer required for companies selling software. Entities can use it but if it is not available, estimates may be used. This is an area that will require a high degree of judgment.
For some, but not all, of the industries listed above, revenue recognition may be accelerated. For instance, revenue recognition in the telecommunications industry may be accelerated, but for asset management, revenue may generally be recognized later under the new requirements.
The AICPA has “formed sixteen industry-specific task forces to identify implementation issues and aid in the development of a new AICPA accounting guide on revenue recognition.” The industries included in the project are:
Comments submitted to the task forces can be viewed on aicpa.org.
ASC Section | Status |
905-605 Agriculture—Revenue Recognition | Retains a portion of the 905-605 guidance |
908-605 Airlines | Superseded |
910-605 Contractors—Construction | Superseded |
912-605 Contractors—Federal Government | Superseded |
920-605 Entertainment—Broadcasters | Superseded |
922-605 Entertainment—Cable Television | Superseded |
924-605 Entertainment—Casinos | Superseded |
926-605Entertainment—Films | Superseded |
928-605 Entertainment—Music | Superseded |
932-605 Extractive Activities—Oil and Gas | Superseded |
940-605 Financial Services—Brokers and Dealers | Superseded |
942-605 Financial Services—Depository and Lending | Superseded |
944-605 Financial Services—Insurance | Superseded |
946-605 Financial Services—Investment Companies | Superseded |
948-605 Financial Services—Mortgage Banking | Superseded |
952-605 Franchisors | Superseded |
954-605 Health Care Entities | Retains a portion of the 954-605 guidance |
958-605 Not-for-Profit Entities | Retains a portion of the 958-605 guidance |
970-605 Real Estate—General | Superseded |
972-605 Real Estate—Common Interest Realty Associations | Superseded |
974-605 Real Estate—Real Estate Investment Trusts | Superseded |
976-605 Real Estate—Retail Land | Superseded |
78-605 Real Estate—Time-Sharing Activities | Superseded |
980-605 Regulated Operations | Retains a portion of the 980-605 guidance |
985-605 Software | Superseded |
18.191.237.79