XML 21 R8.htm IDEA: XBRL DOCUMENT
v3.22.2

BASIS OF PRESENTATION AND SIGNIFICANT ACCOUNTING POLICIES | 3 Months Ended
--- | ---
Jun. 30, 2022
Accounting Policies [Abstract] |
BASIS OF PRESENTATION AND SIGNIFICANT ACCOUNTING POLICIES | BASIS OF PRESENTATION AND SIGNIFICANT ACCOUNTING POLICIES Take-Two Interactive Software, Inc. (the "Company," "we," "us," or similar pronouns) was incorporated in the state of Delaware in 1993. We are a leading developer, publisher, and marketer of interactive entertainment for consumers around the globe. We develop and publish products principally through Rockstar Games, 2K, Private Division, and Zynga. Our products are designed for console gaming systems, personal computers ("PC"), and mobile including smart phones and tablets ("Mobile"), and are delivered through physical retail, digital download, online platforms, and cloud streaming services. Acquisition of Zynga On May 23, 2022, we completed our acquisition of Zynga Inc. ("Zynga"), a leading developer of mobile games. Refer to Note 1 4 - A cquisitions for additional information. Basis of Presentation The accompanying Condensed Consolidated Financial Statements are unaudited and include the accounts of the Company and its wholly-owned subsidiaries and, in our opinion, reflect all normal and recurring adjustments necessary for the fair presentation of our financial position, results of operations, and cash flows. Interim results may not be indicative of the results that may be expected for the full fiscal year. All intercompany accounts and transactions have been eliminated in consolidation. The preparation of these Condensed Consolidated Financial Statements in accordance with accounting principles generally accepted in the United States ("U.S. GAAP") requires management to make estimates and assumptions that affect the amounts reported in these Condensed Consolidated Financial Statements and accompanying notes. As permitted under U.S. GAAP, interim accounting for certain expenses, including income taxes, are based on full year assumptions when appropriate. Actual results could differ materially from those estimates, including as a result of the COVID-19 pandemic, which may affect economic conditions in a number of different ways and result in uncertainty and risk. Certain information and footnote disclosures normally included in financial statements prepared in accordance with U.S. GAAP have been omitted pursuant to the rules and regulations of the Securities and Exchange Commission ("SEC"), although we believe that the disclosures are adequate to make the information presented not misleading. These Condensed Consolidated Financial Statements and accompanying notes should be read in conjunction with our annual Consolidated Financial Statements and the notes thereto, included in our Annual Report on Form 10-K for the fiscal year ended March 31, 2022. Certain immaterial reclassifications have been made to prior period amounts to conform to the current period presentation. We are reiterating our significant accounting policy on revenue recognition included in our Annual Report on Form 10-K for the fiscal year ended March 31, 2022, including certain revenue policies applied upon the close of the Zynga acquisition. Revenue Recognition We derive revenue primarily from the sale of our interactive entertainment content, principally for console gaming systems, personal computers, and Mobile. We also generate revenue from advertising within our software products. Game. Our interactive entertainment content consists of full game software products that may contain offline gameplay, online gameplay, or a combination of offline and online gameplay. We may also sell separate downloadable add-on content to supplement our full game software products. Certain of our software products provide customers with the option to acquire virtual currency or make in-game purchases. We determine revenue recognition by: •identifying the contract, or contracts, with the customer; •identifying the performance obligations in the contract; •determining the transaction price; •allocating the transaction price to performance obligations in the contract; and •recognizing revenue when, or as, we satisfy performance obligations by transferring the promised goods or services. We recognize revenue in the amount that reflects the consideration we expect to receive in exchange for the sales of software products and game related services when control of the promised products and services is transferred to our customers and our performance obligations under the contract have been satisfied. Revenue is recorded net of transaction taxes assessed by governmental authorities such as sales, value-added and other similar taxes. Our software products are sold as full games, which typically provide access to the main game content, primarily for console and PC. Generally, our full game software products deliver a license of our intellectual property that provides a functional offline gaming experience (i.e., one that does not require an Internet connection to access the main game content or other significant game related services). We recognize revenue related to the license of our intellectual property that provides offline functionality at the time control of the products has been transferred to our customers (i.e. upon delivery of the software product). In addition, some of our full game software products that provide a functional offline gaming experience may also include significant game related services delivered over time, such as online functionality that is dependent upon online support services and/or additional free content updates. For full game sales that offer offline functionality and significant game related services we evaluate whether the license of our intellectual property and the game related services are distinct and separable. This evaluation is performed for each software product sold. If we determine that our software products contain a license of intellectual property separate from the game related services (i.e. multiple performance obligations), we estimate a standalone selling price for each identified performance obligation. We allocate the transaction price to each performance obligation using a relative standalone selling price method (the transaction price is allocated to a performance obligation based on the proportion of the standalone selling price of each performance obligation to the sum of the standalone selling prices for all performance obligations in the contract). For the portion of the transaction price allocable to the license, revenue is recognized when the customer takes control of the product. For the portion of the transaction price allocated to game related services, revenue is recognized ratably over an estimated service period for the related software product. We also defer related product costs and recognize the costs as the revenues are recognized. Certain of our full game software products are delivered primarily as an online gaming experience with substantially all gameplay requiring online access to our game related services. We recognize revenue for full game software products that are dependent on our game related services over an estimated service period. For our full game online software products, we also defer related product costs and recognize the costs as the revenue is recognized. We also sell separate downloadable add-on content to supplement our full game software products. Revenue from the sale of separate downloadable add-on content is evaluated for revenue recognition on the same basis as our full game software products. In addition to sales of our full game software products, we also offer free-to-play software products, both of which may provide customers with the option to acquire virtual currency or make in-game purchases. For virtual currency and in-game purchases the satisfaction of our performance obligation is dependent on the nature of the virtual item purchased and as a result, we categorize our virtual items as follows: •Consumable: Consumable virtual items represent items that can be consumed by a specific player action. Consumable virtual items do not result in a direct benefit that the player keeps or provide the player any continuing benefit following consumption, and they often enable a player to perform an in-game action immediately. For the sale of consumable virtual items, we recognize revenue as the items are consumed (i.e., over time), which approximates less than one month. •Durable: Durable virtual items represent items that are accessible to the player over an extended period of time. We recognize revenue from the sale of durable virtual items ratably over the estimated service period for the applicable game (i.e., over time), which represents our best estimate of the average life of the durable virtual item. Certain software products are sold to customers with a “street date” (the earliest date these products may be sold by these retailers). For the transaction price related to the license for these products that also provide a functional offline gaming experience, we recognize revenue on the later of the street date or the sale date as this is generally when we have transferred control of this performance obligation. For the sale of physical software products, recognition of revenue allocated to game related services does not begin until the product is sold-through by our customer to the end user. We currently estimate sell-through to the end user for all our titles to be approximately two months after we have sold-in the software products to retailers. Determining the estimated sell-through period requires management judgment and estimates. In addition, some of our software products are sold as digital downloads. Revenue from digital downloads generally commences when the download is made available to the end user by a third-party digital storefront. In certain countries, we use third-party licensees to distribute and host our games in accordance with license agreements, for which the licensees typically pay us a fixed minimum guarantee and sales-based royalties. These arrangements typically include multiple performance obligations, such as an upfront license of intellectual property and rights to future updates. Based on the allocated transaction price, we recognize revenue associated with the minimum guarantee when we transfer control of the upfront license of intellectual property (generally upon commercial launch) and the remaining portion ratably over the contractual term in which we provide the licensee with future update rights. Royalty payments in excess of the minimum guarantee are generally recognized when the licensed product is sold by the licensee. Advertising. We have contractual relationships with advertising networks, agencies, advertising brokers, and directly with advertisers to display advertisements in our games. For our in-game advertising arrangements, our performance obligation is to provide the inventory for advertisements to be displayed in our games. For contracts made directly with advertisers, we are also obligated to serve the advertisements in our games. However, for those direct advertising arrangements, providing the advertising inventory and serving the advertisement is considered a single performance obligation, as the advertiser cannot benefit from the advertising space without its advertisements being displayed. For in-game display advertisements, in-game offers, engagement advertisements, and other advertisements, our performance obligation is satisfied over the life of the contract, with revenue being recognized as advertising units are delivered. Contract Balances We generally record a receivable related to revenue when we have an unconditional right to invoice and receive payment, and we record deferred revenue when cash payments are received or due in advance of satisfying our performance obligations, even if amounts are refundable. Contract assets generally consist of arrangements for which we have recognized revenue to the extent it is probable that significant reversal will not occur but do not have a right to invoice as of the reporting date. Our allowances for doubtful accounts are typically immaterial and, if required, are based on our best estimate of expected credit losses inherent in our accounts receivable balance. Deferred revenue is comprised primarily of unsatisfied revenue related to the portion of the transaction price allocable to game related services of our full game software products and sales of virtual currency. These sales are typically invoiced at the beginning of the contract period, and revenue is recognized ratably over the estimated service period. Deferred revenue may also include amounts related to software products with future street dates. Refer to Note 2 - Revenue from Contracts with Customers for further information, including changes in deferred revenue during the period. Principal Agent Considerations We offer certain software products via third-party digital storefronts, such as Microsoft’s Xbox Live, Sony’s PlayStation Network, Valve's Steam, Epic Games Store, Apple's App Store, and the Google Play Store. For sales of our software products via third-party digital storefronts, we determine whether or not we are acting as the principal in the sale to the end user, which we consider in determining if revenue should be reported based on the gross transaction price to the end user or based on the transaction price net of fees retained by the third-party digital storefront. An entity is the principal if it controls a good or service before it is transferred to the customer. Key indicators that we use in evaluating these sales transactions include, but are not limited to, the following: •the underlying contract terms and conditions between the various parties to the transaction; •which party is primarily responsible for fulfilling the promise to provide the specified good or service; and •which party has discretion in establishing the price for the specified good or service. Based on our evaluation of the above indicators, for sales arrangements via Microsoft’s Xbox Live, Sony’s PlayStation Network, Valve's Steam, and Epic Games Store we have determined we are not the principal in the sales transaction to the end user and therefore we report revenue based on the consideration received from the digital storefront. For sales arrangements via Apple's App Store and the Google Play Store, we have determined that we are the principal to the end user and thus report revenue on a gross basis and mobile platform fees charged by these digital storefronts are expensed as incurred and reported within Cost of revenue. Shipping and Handling Shipping and handling costs are incurred to move physical software products to customers. We recognize all shipping and handling costs as an expense in Cost of revenue because we are responsible for delivery of the product to our customers prior to transfer of control to the customer. Estimated Service Period For certain performance obligations satisfied over time, we have determined that the estimated service period is the time period in which an average user plays our software products (“user life”) which most faithfully depicts the timing of satisfying our performance obligation. We consider a variety of data points when determining and subsequently reassessing the estimated service period for players of our software products. Primarily, we review the weighted average number of days between players’ first and last days played online. When a new game is launched and therefore no history of online player data is available, we consider other factors to determine the user life, such as the estimated service period of other games actively being sold with similar characteristics. We also consider known online trends, the service periods of our previously released software products, and, to the extent publicly available, the service periods of our competitors’ software products that are similar in nature to ours. We believe this provides a reasonable depiction of the transfer of our game related services to our customers, as it is the best representation of the period during which our customers play our software products. Determining the estimated service period is subjective and requires significant management judgment and estimates. Future usage patterns may differ from historical usage patterns, and therefore the estimated service period may change in the future. The estimated service periods for players of our current software products are generally between six and fifteen months depending on the software product. Revenue Arrangements with Multiple Performance Obligations Our contracts with customers often include promises to transfer multiple products and services. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together requires significant judgment. For software products in which the software license has offline functionality and benefits from meaningful game related services, which may include online functionality that is dependent on our online support services and/or additional free content updates, we believe we have separate performance obligations for the license of the intellectual property and the game related services. Additionally, because each of our product offerings has unique features and because we do not sell our game related services separately, we typically do not have observable standalone selling prices for each performance obligation. Significant judgment and estimates are also required to determine the standalone selling price for each distinct performance obligation and whether a discount needs to be allocated based on the relative standalone selling price of our products and services. To estimate the standalone selling price for each performance obligation, we consider, to the extent available, a variety of data points such as past selling prices of the product or other similar products, competitor pricing, and market data. If observable pricing is not available, we use an expected cost-plus margin approach taking into account relevant costs including product development, post-release support, marketing and licensing costs. This evaluation is performed on a product by product basis. Price Protection, Allowances for Returns, and Sales Incentives We grant price protection and accept returns in connection with our distribution arrangements. Following reductions in the price of our physical software products, we grant price protection to permit customers to take credits against amounts they owe us with respect to merchandise unsold by them. Our customers must satisfy certain conditions to entitle them to receive price protection or return products, including compliance with applicable payment terms and confirmation of field inventory levels. At contract inception and at each subsequent reporting period, we make estimates of price protection and product returns related to current period software product revenue. We estimate the amount of price protection and returns for software products based upon, among other factors, historical experience and performance of the titles in similar genres, historical performance of the hardware platform, customer inventory levels, analysis of sell-through rates, sales force and retail customer feedback, industry pricing, market conditions, and changes in demand and acceptance of our products by consumers. We enter into various sales incentive arrangements with our customers, such as rebates, discounts, and cooperative marketing. These incentives are considered adjustments to the transaction price of our software products and are reflected as reductions to revenue. Sales incentives incurred by us for distinct goods or services received, such as the appearance of our products in a customer’s national circular ad, are included in Selling and marketing expense if there is a separate identifiable benefit and the benefit’s fair value can be established. Otherwise, such sales incentives are reflected as a reduction to revenue. Revenue is recognized after deducting the estimated price protection, allowances for returns, and sales incentives, which are accounted for as variable consideration. Price protection, allowances for returns, and sales incentives are considered refund liabilities and are reported within Accrued expenses and other current liabilities on our Consolidated Balance Sheet. Significant Estimates Significant management judgment and estimates must be used in connection with many of the determinations described above, such as estimating the fair value allocation to distinct and separable performance obligations, the service period over which to defer recognition of revenue, and the amounts of price protection. We believe we can make reliable estimates. However, actual results may differ from initial estimates due to changes in circumstances, market conditions, and assumptions. Adjustments to estimates are recorded in the period in which they become known. Payment Terms Our payment terms and conditions vary by customer and typically provide net 30- to 60-day terms. In instances where the timing of revenue recognition differs from the timing of invoicing, we do not adjust the promised amount of consideration for the effects of a significant financing component when we expect, at contract inception, that the period between our transfer of a promised product or service to our customer and payment for that product or service will be one year or less. Recently Adopted Accounting Pronouncements Accounting for Government Assistance In November 2021, the FASB issued ASU 2021-10, Government Assistance (Topic 832): Disclosures by Business Entities about Government Assistance, which requires annual disclosures that increase the transparency of transactions involving government grants, including (1) the types of transactions, (2) the accounting for those transactions, and (3) the effect of those transactions on any entity's financial statements. The new guidance is effective for fiscal years beginning after December 15, 2021 with the new disclosures required on an annual basis, and can be applied either prospectively or retrospectively. The Company adopted the new guidance on April 1, 2022 and will include the disclosures as required in its annual reporting with respect to any government assistance or grants subject to the scope of the guidance to the extent material. Accounting for Contract Assets and Contract Liabilities In October 2021, the FASB issued ASU 2021-08, Business Combinations (Topic 805): Accounting for Contract Assets and Contract Liabilities from Contracts with Customers. Under this new standard, deferred revenue acquired in a business combination is measured pursuant to ASC 606, Revenue from Contracts with Customers, rather than its assumed acquisition date fair value under the current guidance. We adopted this effective April 1, 2022. The adoption of this update did not have an impact on our Condensed Consolidated Financial Statements and was applied to our acquisition of Zynga. Refer to Note 1 4 - Acquisitions. Accounting for Convertible Debt In August 2020, the FASB issued ASU 2020-06, Debt – Debt with Conversion and Other Options (Subtopic 470-20) and Derivatives and Hedging – Contracts in Entity’s Own Equity (Subtopic 815-40), which simplifies the accounting for convertible instruments by reducing the number of accounting models and generally requiring that a convertible instrument be accounted for as a single liability measured at amortized cost, with no conversion feature separately recorded in equity. Similarly, no portion of issuance costs will be allocated to equity under the ASU. Further, the ASU amends the earnings per share guidance by requiring the diluted earnings per share calculation for convertible instruments to follow the if-converted method, with use of the treasury stock method no longer permitted. We adopted this effective April 1, 2022. The adoption of this update did not have an impact on our Condensed Consolidated Financial Statements.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for the general note to the financial statements for the reporting entity which may include, descriptions of the basis of presentation, business description, significant accounting policies, consolidations, reclassifications, new pronouncements not yet adopted and changes in accounting principles. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 810 -URI https://asc.fasb.org/topic&trid=2197479 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -URI https://asc.fasb.org/topic&trid=2134479 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 250 -URI https://asc.fasb.org/topic&trid=2122394 Reference 4: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI https://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_OrganizationConsolidationBasisOfPresentationBusinessDescriptionAndAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration