An entity may enter into two or more contracts with the same customer at or near the same time. While multiple legal contracts exist under this type of situation, Accounting Standards Codification (ASC) 606, Revenue from Contracts with Customers, may require these contracts to be combined for the purposes of revenue recognition. For example, if a software company enters into two contracts with the same customer at about the same time (1) for software and (2) for customized implementation of the software, the company may be required to combine these contracts under ASC 606.
A set of contracts should be evaluated for combination in accordance with ASC 606-10-25-9 when the following indicators exist:
- The contracts were entered into at or about the same time, and
- The contracts were entered into with the same customer or with a related party of the customer.
The above indicators signal a potential issue: revenue recognition patterns may differ when multiple contracts are accounted for separately instead of collectively, when in reality, the economics of the set of contracts are interrelated. The Financial Accounting Standards Board (FASB) states that judgment should be used in determining if a contract is entered into “at or near the same time,” noting the importance of the economic circumstances affecting negotiations and that these circumstances are likely to change as time passes between contracts.
The FASB also notes that “related party” in the context of ASC 606 is consistent with the definition included in current related party guidance found at ASC 850, Related Party Disclosures. The existence of these indicators does not automatically require that the set of contracts must be combined. Rather, the indicators signal that further analysis is required. Combination of contracts is required when one or more of the following criteria are met (see ASC 606-10-25-9):
a) The contracts are negotiated as a single bundle or package with a single business objective.
b) Consideration in one contract is tied to the price or performance of the other contract(s).
c) Promised goods or services in the contracts represent a single performance obligation.
Practitioners should look for evidence of a single business objective. For example, one contract is in a loss position when analyzed without the consideration from one or more separate contracts negotiated as a bundle. Other facts and circumstances may provide evidence of one business purpose or objective, and judgment should be used in making this determination.
Company A, a manufacturer of specialized construction equipment, enters into a contract with Customer B to manufacture and deliver a customized boom lift for $95,000. The total cost to Company A of designing, manufacturing, and delivering the boom lift is estimated to be $70,000. Two days later, Company A enters into another contract with Customer B to deliver four boom lift tires that Customer B will use on the customized boom lift in the future after the original tires deteriorate. The contract price per tire is $800; however, the cost of each tire is estimated at $900.
Analysis: In the facts above, Company A enters into two contracts with the same party at about the same time (within two days), which indicates the need for further analysis. Upon further analysis, Company A determines that criterion A for combining contracts is met because the two contracts are negotiated as a bundle with one business objective. Specifically, Company A would be taking a loss of $400 [($900 – $800) * 4 = $400] on the second contract when considered without the first contract. Therefore, Company A is required to combine the two contracts for revenue recognition.
This criterion deals with the relationship between consideration and contract price or performance of two or more contracts. The criterion is met when the consideration received for one contract depends on the price or performance of another. For example, no payment is required on a later contract if certain deadlines specified in previous contracts are not reached by the entity.
Company M, a full service dealer of fleet vehicles, recently entered into a contract with Customer P for the sale of 50 used pick-up trucks at a price of $23,500 per vehicle. Two days later Company M enters into a second contract with Customer P for five years of fleet vehicle maintenance at a price of $1,200 per vehicle. Further, this contract stipulates that Company M must concede a 50 percent discount in the per vehicle maintenance price for each of the 50 trucks that does not pass Customer P’s performance tests.
Analysis: In the facts above, Company M enters into two contracts with the same party at about the same time which indicates that combination of contracts may be required. In this case, criterion B is met because the consideration to be received in the second contract is tied to the performance in the first contract. Specifically, Company M must reduce the per vehicle maintenance price if the used fleet vehicles do not meet the customer’s required quality specifications. Therefore, Company M is required to combine the contracts for revenue recognition.
In applying criterion C, practitioners should follow the guidance for identifying performance obligations in step 2 of the five-step process. Specifically, to be distinct, a good or service must be (1) capable of being distinct and (2) separately identifiable or “distinct within the context of the contract.” The following factors may indicate a good or service is not “distinct within the context of the contract”:
- The entity provides a significant service of integrating the good or service with other goods or services in the contract.
- The good or service significantly modifies or customizes another good or service in the contract.
- The good or service is highly dependent on, or highly interrelated with, other goods or services in the contract.
In essence, practitioners should evaluate the set of contracts as if one contract exists to determine if the goods or services promised within the set are a single performance obligation. If the goods or services promised are not distinct, the contracts must be combined. (For more on distinct performance obligations, see our article on Distinct within the Context of the Contract.)
Company X sells learning management systems (LMS). LMS is provided as a web-based application for customers to manage organizational training. Among other offerings, Company X provides (1) basic access to a unique portal that is customizable by the customer and (2) a range of implementation services.
Company X enters into a contract with Customer Y for access to its LMS application for a period of 36 months at a total price of $18,000. The following day, Company X negotiates a second contract with Customer Y for implementation services for $3,500. Under the second contract, Customer Y will receive a significantly customized portal that is beyond Company X’s common implementation services that use pre-designed templates. The implementation will require the professional services department’s involvement to be completed.
Analysis: In the facts above, Company X enters into two contracts with the same party at about the same time which indicates that combination of contracts may be required. In this case, criterion C is met because the implementation services “significantly modify or customize” the service provided in the first contract. As such, the two services are not distinct within the context of the combined contract. Therefore, Company X is required to combine the contracts for revenue recognition.
Comparison to 605
ASC 606 is relatively consistent with and conceptually similar to ASC 605, Revenue Recognition, for contract combination. Under ASC 605, separate contracts entered into at or near the same time with the same party (or a related party) are presumed to be one contract unless evidence exists to the contrary (ASC 605-25-25-3). In contrast, ASC 606 does not contain a similar rebuttable presumption. Rather, contracts are not combined unless certain criteria, discussed above, are met.
ASC 606 also removes industry-specific guidance for combining contracts. For example, ASC 605 allows for combining contracts for certain construction- and production-type arrangements, given certain criteria are met. Additionally, ASC 985-605, Software—Revenue Recognition, provides six factors that may indicate software vendors should combine contracts into a single multi-element arrangement. However, ASC 606 provides guidance for combination of contracts that applies to all contracts, thus removing industry-specific guidance.
A set of contracts entered into at or about the same time with the same or related party may indicate the need to combine contracts. Practitioners should evaluate the contracts in question using the three criteria set out in ASC 606. When one or more of the criteria are met, the contracts must be combined for revenue recognition.