Significant Accounting Policies - Revenue Recognition

General

The Company commences revenue recognition when persuasive evidence of an arrangement exists, delivery has occurred, the sales price is fixed or determinable and collection is reasonably assured. Generally, the products the Company sells do not require significant production, modification or customization. Installation of the Company’s products is generally routine, consists of implementation and configuration and does not have to be performed by the Company.

At the time of a sales transaction, the Company makes an assessment of the collectability of the amount due from the customer. Revenues are recognized only if it is reasonably assured that collection will occur. When making this assessment, the Company considers customer credit-worthiness and historical payment experience. If it is determined from the outset of the arrangement that collection is not reasonably assured, revenues are recognized on a cash basis, provided that all other revenue recognition criteria are satisfied. At the outset of the arrangement, the Company also assesses whether the fee associated with the order is fixed or determinable and free of contingencies or significant uncertainties. When assessing whether the fee is fixed or determinable, the Company considers the payment terms of the transaction, the Company’s collection experience in similar transactions without making concessions, and the Company’s involvement, if any, in third-party financing transactions, among other factors. If the fee is not fixed or determinable, revenues are recognized only as payments become due from the customer, provided that all other revenue recognition criteria are met. If a significant portion of the fee is due after the Company’s normal payment terms, the Company evaluates whether the Company has sufficient history of successfully collecting past transactions with similar terms without offering concessions. If that collection history is sufficient, revenue recognition commences, upon delivery of the products, assuming all other revenue recognition criteria are satisfied. If the Company was to make different judgments or assumptions about any of these matters, it could cause a material increase or decrease in the amount of revenues reported in a particular period.

The Company often receives multiple purchase orders or contracts from a single customer or a group of related customers that are evaluated to determine if they are, in effect, part of a single arrangement. In situations when the Company has concluded that two or more orders with the same customer are so closely related that they are, in effect, parts of a single arrangement, the Company accounts for those orders as a single arrangement for revenue recognition purposes. In other circumstances, when the Company has concluded that two or more orders with the same customer are independent buying decisions, such as an earlier purchase of a product and a subsequent purchase of a software upgrade or maintenance contract, the Company accounts for those orders as separate arrangements for revenue recognition purposes.

For many of the Company’s products, there has been an ongoing practice of Avid making available at no charge to customers minor feature and compatibility enhancements as well as bug fixes on a when-and-if-available basis (collectively “Software Updates”), for a period of time after initial sales to end users. The implicit obligation to make such Software Updates available to customers over a period of time represents implied post-contract customer support, which is deemed to be a deliverable in each arrangement and is accounted for as a separate element (“Implied Maintenance Release PCS”).

Over the course of the last 18 months, in connection with a strategic initiative to increase support and other recurring revenue streams, the Company has taken a number of steps to eliminate the longstanding practice of providing Implied Maintenance Release PCS for the Media Composer, Pro Tools and Sibelius product lines. On Media Composer 8.0 in particular, which was released in May 2014, management has (i) clearly communicated a policy of no longer providing any Software Updates or other support to customers that are not covered under a paid support plan and (ii) implemented robust digital rights management tools to enforce the policy. With the new policy and technology for Media Composer 8.0 in place, combined with management’s intent to continue to adhere to the policy, management concluded in the third quarter of 2015 that Implied Maintenance Release PCS for Media Composer 8.0 transactions no longer exists. As a result of the conclusion that Implied Maintenance Release PCS on Media Composer 8.0 has ended, revenue and net income for the three and nine months ended September 30, 2015 increased by approximately $13.0 million, reflecting the recognition of orders received over the last 18 months that would have qualified for earlier recognition using the residual method of accounting. In addition, as the elimination of Implied Maintenance Release PCS also resulted in the accelerated recognition of maintenance and product revenues that were previously being recognized over the expected period of Implied Maintenance Release PCS rather than the contractual maintenance period, the change in the estimated amortization period of transactions being recognized on a ratable basis resulted in an additional $2.5 million of revenue during the three and nine months ended September 30, 2015. Management will continue to evaluate the judgment of whether Implied Maintenance Release PCS exists on each product line and version. If and when management concludes Implied Maintenance Release PCS no longer exists for other product lines or versions in future quarters, software revenue related to orders affected will be accelerated and prospective revenue recognition on new product orders will be recognized upfront, assuming all other revenue recognition criteria are met and VSOE of fair value exists for all undelivered elements.

The Company enters into certain contractual arrangements that have multiple elements, one or more of which may be delivered subsequent to the delivery of other elements. These multiple-deliverable arrangements may include products, support, training, professional services and Implied Maintenance Release PCS. For these multiple-element arrangements, the Company allocates revenue to each deliverable of the arrangement based on the relative selling prices of the deliverables. In such circumstances, the Company first determines the selling price of each deliverable based on (i) VSOE of fair value if that exists; (ii) third-party evidence of selling price (“TPE”), when VSOE does not exist; or (iii) best estimate of the selling price (“BESP”), when neither VSOE nor TPE exists. Revenue is then allocated to the non-software deliverables as a group and to the software deliverables as a group using the relative selling prices of each of the deliverables in the arrangement based on the selling price hierarchy. The Company’s process for determining BESP for deliverables for which VSOE or TPE does not exist involves significant management judgment. In determining BESP, the Company considers a number of data points, including:


•	the pricing established by management when setting prices for deliverables that are intended to be sold on a standalone basis;


•	contractually stated prices for deliverables that are intended to be sold on a standalone basis;


•	the pricing of standalone sales that may not qualify as VSOE of fair value due to limited volumes or variation in prices; and


•	other pricing factors, such as the geographical region in which the products are sold and expected discounts based on the customer size and type.

In determining a BESP for Implied Maintenance Release PCS, which the Company does not sell separately, the Company considers (i) the service period for the Implied Maintenance Release PCS, (ii) the differential in value of the Implied Maintenance Release PCS deliverable compared to a full support contract, (iii) the likely list price that would have resulted from the Company’s established pricing practices had the deliverable been offered separately, and (iv) the prices a customer would likely be willing to pay.

The Company estimates the service period of Implied Maintenance Release PCS based on the length of time the product version purchased by the customer is planned to be supported with Software Updates. If facts and circumstances indicate that the original service period of Implied Maintenance Release PCS for a product has changed significantly after original revenue recognition has commenced, the Company will modify the remaining estimated service period accordingly and recognize the then-remaining deferred revenue balance over the revised service period.

The Company has established VSOE of fair value for all professional services and training and for some of the Company’s support offerings. The Company’s policy for establishing VSOE of fair value consists of evaluating standalone sales, where available, to determine if a substantial portion of the transactions fall within a reasonable range. If a sufficient volume of standalone sales exist and the standalone pricing for a substantial portion of the transactions falls within a reasonable range, management concludes that VSOE of fair value exists.

In accordance with ASU No. 2009-14, the Company excludes from the scope of software revenue recognition requirements the Company’s sales of tangible products that contain both software and non-software components that function together to deliver the essential functionality of the tangible products. The Company adopted ASU No. 2009-13 and ASU No. 2009-14 prospectively on January 1, 2011 for new and materially modified arrangements originating after December 31, 2010.

Prior to the Company’s adoption of ASU No. 2009-14, the Company primarily recognized revenues using the revenue recognition criteria of Accounting Standards Codification, or ASC, Subtopic 985-605, Software-Revenue Recognition. As a result of the Company’s adoption of ASU No. 2009-14 on January 1, 2011, a majority of the Company’s products are now considered non-software elements under GAAP, which excludes them from the scope of ASC Subtopic 985-605 and includes them within the scope of ASC Topic 605, Revenue Recognition. Because the Company had not been able to establish VSOE of fair value for Implied Maintenance Release PCS, as described further below, substantially all revenue arrangements prior to January 1, 2011 were recognized on a ratable basis over the service period of Implied Maintenance Release PCS. Subsequent to January 1, 2011 and the adoption of ASU No. 2009-14, the Company determines a relative selling price for all elements of the arrangement through the use of BESP, as VSOE and TPE are typically not available, resulting in revenue recognition upon delivery of arrangement consideration attributable to product revenue, provided all other criteria for revenue recognition are met, and revenue recognition of Implied Maintenance Release PCS and other service and support elements over time as services are rendered.

Revenue Recognition of Non-Software Deliverables

Revenue from products that are considered non-software deliverables is recognized upon delivery of the product to the customer. Products are considered delivered to the customer once they have been shipped and title and risk of loss has been transferred. For most of the Company’s product sales, these criteria are met at the time the product is shipped. Revenue from support that is considered a non-software deliverable is initially deferred and is recognized ratably over the contractual period of the arrangement, which is generally 12 months. Professional services and training services are typically sold to customers on a time and materials basis. Revenue from professional services and training services that are considered non-software deliverables is recognized for these deliverables as services are provided to the customer. Revenue for Implied Maintenance Release PCS that is considered a non-software deliverable is recognized ratably over the service period of Implied Maintenance Release PCS, which ranges from 1 to 8 years.

Revenue Recognition of Software Deliverables

The Company recognizes the following types of elements sold using software revenue recognition guidance: (i) software products and software upgrades, when the software sold in a customer arrangement is more than incidental to the arrangement as a whole and the product does not contain hardware that functions with the software to provide essential functionality, (ii) initial support contracts where the underlying product being supported is considered to be a software deliverable, (iii) support contract renewals, and (iv) professional services and training that relate to deliverables considered to be software deliverables. Because the Company does not have VSOE of the fair value of its software products, the Company is permitted to account for its typical customer arrangements that include multiple elements using the residual method. Under the residual method, the VSOE of fair value of the undelivered elements (which could include support, professional services or training, or any combination thereof) is deferred and the remaining portion of the total arrangement fee is recognized as revenue for the delivered elements. If evidence of the VSOE of fair value of one or more undelivered elements does not exist, revenues are deferred and recognized when delivery of those elements occurs or when VSOE of fair value can be established. VSOE of fair value is typically based on the price charged when the element is sold separately to customers. The Company is unable to use the residual method to recognize revenues for many arrangements that include products that are software deliverables under GAAP since VSOE of fair value does not exist for Implied Maintenance Release PCS elements, which are included in a majority of the Company’s arrangements.

For software products that include Implied Maintenance Release PCS, an element for which VSOE of fair value does not exist, revenue for the entire arrangement fee, which could include combinations of product, professional services, training and support,

is recognized ratably as a group over the longest service period of any deliverable in the arrangement, with recognition commencing on the date delivery has occurred for all deliverables in the arrangement (or begins to occur in the case of professional services, training and support). Standalone sales of support contracts are recognized ratably over the service period of the product being supported.

From time to time, the Company offers certain customers free upgrades or specified future products or enhancements. When a software deliverable arrangement contains an Implied Maintenance Release PCS deliverable, revenue recognition of the entire arrangement will only commence when any free upgrades or specified future products or enhancements have been delivered, assuming all other products in the arrangement have been delivered and all services, if any, have commenced.