XML 50 R8.htm IDEA: XBRL DOCUMENT v2.4.0.6
Significant Accounting Policies
9 Months Ended
Dec. 31, 2012
Significant Accounting Policies [Abstract]  
Significant Accounting Policies
(2) SIGNIFICANT ACCOUNTING POLICIES
Revenue Recognition
We evaluate revenue recognition based on the criteria set forth in Financial Accounting Standards Board (“FASB”) Accounting Standards Codification (“ASC”) 605, Revenue Recognition and ASC 985-605, Software: Revenue Recognition. We classify our revenue as either product revenue or service and other revenue.

Product revenue. Our product revenue includes revenue associated with the sale of software games or related content, whether delivered via a physical disc (e.g., packaged goods) or via the Internet (e.g., full-game downloads, micro-transactions), and licensing of game software to third-parties. Product revenue also includes revenue from mobile full game downloads that do not require our hosting support, and sales of tangible products such as hardware, peripherals, or collectors' items.

Service and other revenue. Our service revenue includes revenue recognized from time-based subscriptions and games or related content that requires our hosting support in order to utilize the game or related content (i.e., cannot be played without an Internet connection). This includes (1) entitlements to content that are accessed through hosting services (e.g., micro-transactions for Internet-based, social network and mobile games), (2) massively multi-player online (“MMO”) games (both software game and subscription sales), (3) subscriptions for our Pogo-branded online game services, and (4) allocated service revenue from sales of software games with an online service element (i.e., “matchmaking” service). Our other revenue includes advertising and non-software licensing revenue.

With respect to the allocated service revenue from sales of software games with a matchmaking service mentioned above, our allocation of proceeds between product and service revenue for presentation purposes is based on management's best estimate of the selling price of the matchmaking service with the residual value allocated to product revenue. Our estimate of the selling price of the matchmaking service is comprised of several factors including, but not limited to, prior selling prices for the matchmaking service, prices charged separately by other third party vendors for similar service offerings, and a cost-plus-margin approach. We review the estimated selling price of the online matchmaking service on a regular basis and use this methodology consistently to allocate revenue between product and service for software game sales with a matchmaking service.

We evaluate and recognize revenue when all four of the following criteria are met:

Evidence of an arrangement. Evidence of an agreement with the customer that reflects the terms and conditions to deliver the related products or services must be present.

Fixed or determinable fee. If a portion of the arrangement fee is not fixed or determinable, we recognize revenue as the amount becomes fixed or determinable.

Collection is deemed probable. Collection is deemed probable if we expect the customer to be able to pay amounts under the arrangement as those amounts become due. If we determine that collection is not probable as the amounts become due, we generally conclude that collection becomes probable upon cash collection.

Delivery. Delivery is considered to occur when a product is shipped and the risk of loss and rewards of ownership have transferred to the customer. For digital downloads, delivery is considered to occur when the software is made available to the customer for download. For services and other, delivery is generally considered to occur as the service is delivered, which is determined based on the underlying service obligation.

Online-Enabled Games

The majority of our software games can be connected to the Internet whereby a consumer may be able to download unspecified content or updates on a when-and-if-available basis (“unspecified updates”) for use with the original game software. In addition, we may also offer an online matchmaking service that permits consumers to play against each other via the Internet. Accounting principles generally accepted in the United States (“U.S. GAAP”) requires us to account for the consumer’s right to receive unspecified updates or the matchmaking service for no additional fee as a “bundled” sale, or multiple-element arrangement.

We have an established historical pattern of providing unspecified updates to online-enabled software games (e.g., player roster updates to Madden NFL 13) at no additional charge to the consumer. We do not have vendor specific objective evidence of fair value (“VSOE”) for these unspecified updates, and thus, as required by U.S. GAAP, we recognize revenue from the sale of these online-enabled games over the period we expect to offer the unspecified updates to the consumer (“estimated offering period”).

Estimated Offering Period

The offering period is not an explicitly defined period and thus, we recognize revenue over an estimated offering period, which is generally estimated to be six months beginning in the month after delivery.

Determining the estimated offering period is inherently subjective and is subject to regular revision based on historical online usage. For example, in determining the estimated offering period for unspecified updates associated with our online-enabled games, we consider the period of time consumers are online as online connectivity is required. On an annual basis, we review consumers' online gameplay of all online-enabled games that have been released 12 to 24 months prior to the evaluation date. For example, if the evaluation date is April 1, 2012, we evaluate all online-enabled games released between April 1, 2010 and March 31, 2011. Based on this population of games, for all players that register the game online within the first six months of release of the game to the general public, we compute the weighted-average number of days for each online-enabled game, based on when a player initially registers the game online to when that player last plays the game online. We then compute the weighted-average number of days for all online-enabled games by multiplying the weighted-average number of days for each online-enabled game by its relative percentage of total units sold from these online-enabled games (i.e., a game with more units sold will have a higher weighting to the overall computation than a game with fewer units sold). Under a similar computation, we also consider the estimated period of time between the date a game unit is sold to a reseller and the date the reseller sells the game unit to an end consumer. Based on the sum of these two calculations, we then consider the results from prior years, known online gameplay trends, as well as disclosed service periods for competitors' games to determine the estimated offering period for unspecified updates. Similar computations are also made for the estimated service period related to our MMO games, which is generally estimated to be eighteen months.
 
While we consistently apply this methodology, inherent assumptions used in this methodology include which online-enabled games to sample, whether to use only units that have registered online, whether to weight the number of days for each game, whether to weight the days based on the units sold of each game, determining the period of time between the date of sale to reseller and the date of sale to the consumer and assessing online gameplay trends.

Other Multiple-Element Arrangements

In some of our multiple element arrangements, we sell tangible products with software and/or software-related offerings. These tangible products are generally either peripherals or ancillary collectors' items, such as figurines and comic books. Revenue for these arrangements is allocated to each separate unit of accounting for each deliverable using the relative selling prices of each deliverable in the arrangement based on the selling price hierarchy described below. If the arrangement contains more than one software deliverable, the arrangement consideration is allocated to the software deliverables as a group and then allocated to each software deliverable in accordance with ASC 985-605.

We determine the selling price for a tangible product deliverable based on the following selling price hierarchy: VSOE (i.e., the price we charge when the tangible product is sold separately) if available, third-party evidence (“TPE”) of fair value (i.e., the price charged by others for similar tangible products) if VSOE is not available, or our best estimate of selling price (“BESP”) if neither VSOE nor TPE is available. Determining the BESP is a subjective process that is based on multiple factors including, but not limited to, recent selling prices and related discounts, market conditions, customer classes, sales channels and other factors. In accordance with ASC 605, provided the other three revenue recognition criteria other than delivery have been met, we recognize revenue upon delivery to the customer as we have no further obligations.

We must make assumptions and judgments in order to (1) determine whether and when each element is delivered, (2) determine whether VSOE exists for each undelivered element, and (3) allocate the total price among the various elements, as applicable. Changes to any of these assumptions and judgments, or changes to the elements in the arrangement, could cause a material increase or decrease in the amount of revenue that we report in a particular period.
Sales Returns and Allowances and Bad Debt Reserves
We reduce revenue primarily for estimated future returns and price protection which may occur with our distributors and retailers (“channel partners”). Price protection represents our practice to provide our channel partners with a credit allowance to lower their wholesale price on a particular product in the channel. The amount of the price protection is generally the difference between the old wholesale price and the new reduced wholesale price. In certain countries for our PC and console packaged goods software products, we also have a practice of allowing channel partners to return older software products in the channel in exchange for a credit allowance. As a general practice, we do not give cash refunds.

When evaluating the adequacy of sales returns and price protection allowances, we analyze the following: historical credit allowances, current sell-through of our channel partner's inventory of our software products, current trends in retail and the video game industry, changes in customer demand, acceptance of our software products, and other related factors. In addition, we monitor the volume of sales to our channel partners and their inventories, as substantial overstocking in the distribution channel could result in high returns or higher price protection in subsequent periods.

In the future, actual returns and price protections may materially exceed our estimates as unsold software products in the distribution channels are exposed to rapid changes in consumer preferences, market conditions or technological obsolescence due to new platforms, product updates or competing software products. While we believe we can make reliable estimates regarding these matters, these estimates are inherently subjective. Accordingly, if our estimates change, our returns and price protection allowances would change and would impact the total net revenue, accounts receivable and deferred net revenue that we report.

We determine our allowance for doubtful accounts by evaluating the following: customer creditworthiness, current economic trends, historical experience, age of current accounts receivable balances, changes in financial condition or payment terms of our customers. Significant management judgment is required to estimate our allowance for doubtful accounts in any accounting period. The amount and timing of our bad debt expense and cash collection could change significantly as a result of a change in any of the evaluation factors mentioned above.