Recognition over time – inputs or outputs?
Another area of concern relates to contracts that are satisfied over a period rather than at a single point in time. Examples include ongoing digital media and marketing planning services or long-running campaigns with multiple elements rather than a single component.
The first step is to determine if, in fact, the contract requires revenue recognition over time. According to paragraph 606-10-25-27 of the standard, a performance obligation is satisfied over time if one of the following conditions is met:
- The customer simultaneously receives and consumes the benefits provided by the entity’s performance as the entity performs.
- The entity’s performance creates or enhances an asset (for example, work in process) that the customer controls as the asset is created or enhanced.
- The entity’s performance does not create an asset with an alternative use to the entity, and the entity has an enforceable right to payment for performance completed to date.
The underlying principle of ASC 606 is that revenue is recognized only when a performance obligation is met – that is, when the promised goods or services are delivered – not necessarily when the sale is made. For contracts that involve multiple performance obligations, or for performance obligations that are completed over a period rather than a point in time, the company must recognize revenue in a way that corresponds to the value that is being transferred to the customer.
Thus, a company that provides ongoing digital media planning and management services on a long-term contract would need to measure progress toward completion of that contract in each reporting period to recognize the appropriate amount of revenue in the period.
It might seem that the simplest way to do this would be to allocate revenue in equal installments over the life of the contract, such as an annual contract in which revenue is recognized in 12 monthly increments. For contracts that are ongoing and consistent, with no significant variations in the way services are delivered, such time-based, straight-line revenue recognition might be appropriate.
In many cases, however, such an approach is insufficient, since the value associated with each performance obligation is not delivered evenly across the life of a contract. For example, in a long-term contract for managing website and e-commerce operations, the initial client onboarding, site design, and implementation are likely to require considerably more time, effort, and resources than the ongoing site operation, maintenance, and support phases that occur later.
The two broad methods that ASC 606 provides for allocating value over time are inputs and outputs. Using the input method, revenue is recognized using measures that correspond to either the level of staff effort expended to satisfy the performance obligation or the amount of other costs incurred. It often is the case that companies do not have sophisticated time-tracking mechanisms in place to determine the level of staff effort. Therefore, it is imperative that accounting and finance teams work closely with their operations personnel to capture the relevant inputs. This often includes project status meetings on a recurring basis or data input forms that can be completed by project-facing personnel.
Under the output method, on the other hand, revenue is recognized based on the relative value that is transferred to the customer as the performance obligation is delivered over time. Typically, this value allocation is linked to the completion of specific deliverables or contract phases. Like the input method already noted, the output method commonly requires interaction with project managers to determine the status of projects. Accounting and finance personnel should be interacting with the project managers on a frequent basis to determine the status of projects. The key to the output method is to analyze the actual progress of the project, as opposed to what the contract schedule might state.
In either case, it typically is not appropriate to simply recognize revenue in accordance with contract billing terms unless the company also can demonstrate input or output measurements that support such an approach. In other words, revenue must be recognized as it is earned, not necessarily as it is billed.
Lastly, accounting and finance personnel must work with their project managers and sales teams to identify any contract modifications or changes in statements of work. Often digital media and marketing companies are asked to update the original contracts or statements of work because of changes in the desired work product from the customer. Capturing these changes in the contracts is important to determining revenue recognition. For more guidance on accounting for contract modifications, see ASC 606-10-25-10 through 25-13.