| 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 our two wholly-owned labels Rockstar Games and 2K, as well as our Private Division label and Social Point, a leading developer of mobile games. Our products are designed for console systems and personal computers, including smart phones and tablets, and are delivered through physical retail, digital download, online platforms and cloud streaming services. 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. 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, 2018 . Certain immaterial reclassifications have been made to prior period amounts to conform to the current period presentation. Recently Adopted Accounting Pronouncements Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement In August 2018, the Financial Accounting Standards Board ("FASB") issued Accounting Standards Update ("ASU") 2018-15: Intangibles - Goodwill and Other - Internal-Use Software - (Subtopic 350-40): Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract. This ASU aligns the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal-use software. The standard is effective for fiscal years beginning December 15, 2019 (April 1, 2020 for the Company), with early adoption permitted. ASU 2018-15 is required to be applied either retrospectively or prospectively to all implementation costs after the date of adoption. We early adopted this update effective July 1, 2018 as the standard aligns with how we are currently accounting for implementation costs incurred in a cloud computing arrangement. The adoption did not have an impact on our Condensed Consolidated Financial Statements. Accounting for Restricted Cash In November 2016, the FASB issued ASU 2016-18, Statement of Cash Flows (Topic 230): Restricted Cash . This ASU amends the presentation of restricted cash within the statement of cash flows by requiring that restricted cash and restricted cash equivalents be included within cash and cash equivalents when reconciling the beginning-of-period and end-of-period total amounts. This standard is effective for fiscal years beginning after December 15, 2017 (April 1, 2018 for the Company), including interim periods within those fiscal years. We adopted the new standard during the first quarter of fiscal 2019 and applied the standard retrospectively for all periods presented. The application of this new standard resulted in a decrease of net cash from operating activities of $66,651 and an increase of net cash from operating activities of $131,283 on our Condensed Consolidated Statements of Cash Flows for the six months ended September 30, 2018 and 2017 , respectively. In our Annual Report on Form 10-K for the year ending March 31, 2018, the impact would have been an increase in net cash from operating activities of $99,580 and $76,649 for the fiscal years ended March 31, 2018 and 2017 , respectively. Accounting for Stock Compensation In June 2018, the FASB issued ASU 2018-07, Compensation - Stock Compensation (Topic 718): Improvements to Non-employee Share-Based Accounting . This guidance aligns the accounting for share-based payment transactions with non-employees to accounting for share-based payment transactions with employees. Companies are required to record a cumulative-effect adjustment (net of tax) to retained earnings as of the beginning of the fiscal year of the adoption. Upon transition, non-employee awards are required to be measured at fair value as of the adoption date. This standard will be effective for fiscal years beginning December 15, 2018 (April 1, 2019 for the Company), including interim periods within those fiscal years. Early adoption is permitted. We early adopted this update effective April 1, 2018 to simplify the accounting for non-employee stock-based awards so that it is better aligned with the current guidance for employee stock-based awards. The application of this new standard did not have a significant impact to our Condensed Consolidated Financial Statements for the three and six months ended September 30, 2018 , as our last re-measurement date for non-employee awards was March 31, 2018. The adoption of this ASU results in a change to our accounting policy for non-employee stock-based awards. Accounting for Goodwill In January 2017, the FASB issued ASU 2017-04, Intangibles - Goodwill and Other (Topic 350) . This ASU eliminates Step 2 from the goodwill impairment test. Under the new guidance, an entity should perform its annual or interim goodwill impairment test by comparing the fair value of a reporting unit with its carrying amount and recognize an impairment charge for the amount by which the carrying amount exceeds the reporting unit’s fair value. Additionally, this ASU eliminates the requirements for any reporting unit with a zero or negative carrying amount to perform a qualitative assessment and, if it fails that qualitative test, to perform Step 2 of the goodwill impairment test. The amendments in this ASU are effective for fiscal years beginning after December 15, 2019 (April 1, 2020 for the Company), including interim periods within those fiscal years, and are applied on a prospective basis. Early adoption is permitted for interim or annual goodwill impairment tests performed on testing dates after January 1, 2017. We early adopted this update effective April 1, 2018. The adoption did not have an impact on our Condensed Consolidated Financial Statements. Revenue from Contracts with Customers In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606) . Under the new standard, revenue is recognized when a customer obtains control of promised goods or services and is recognized in an amount that reflects the consideration that the entity expects to receive in exchange for those goods or services. On April 1, 2018, we adopted the new accounting standard and related amendments (the “New Revenue Accounting Standard”) using the modified retrospective method. As a result, we have updated our significant accounting policy disclosure for revenue recognition herein. Impact of Adopting New Revenue Accounting Standard We elected to apply the New Revenue Accounting Standard only to contracts not completed as of the adoption date. For contracts that were modified before the date of adoption, we elected to reflect the aggregate effect of all modifications when (i) identifying the satisfied and unsatisfied performance obligations, (ii) determining the transaction price, and (iii) allocating the transaction price to the satisfied and unsatisfied performance obligations. We recognized the cumulative effect of initially applying the New Revenue Accounting Standard as an adjustment to the opening balance of retained earnings, net of tax. The comparative information has not been restated and continues to be reported under the accounting standards in effect for those periods. The cumulative effect adjustment recorded to our retained earnings was $470,273 , net of tax. The most significant impacts of adopting the New Revenue Accounting Standard are: • The elimination of the requirement for vendor-specific objective evidence (“VSOE”) of fair value for software products that offer offline gameplay functionality and benefit from meaningful game related services which may include online functionality that is dependent on our online support services and/or additional free content updates. Under the prior revenue accounting guidance, for software products with multiple deliverables for which we did not have VSOE for our game related service deliverables, we recognized revenue ratably over the estimated service period. Under the New Revenue Accounting Standard, we allocate the sales price and recognize revenue for the offline software upon delivery and the remainder over the estimated service period. This difference in accounting primarily affects revenue recognition from Grand Theft Auto V and our NBA 2K franchise, where the majority of the sales price will be allocated to the offline software and recognized upon transfer of control to our customers, and the remaining amounts allocated to the game related service performance obligation and recognized over the estimated service period. • For performance obligations that are 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 faithfully depicts the timing of satisfying our performance obligation. Previously, our estimated service period was based on the economic game life. • Under the New Revenue Accounting Standard, we are able to recognize revenue to the extent it is probable that a significant reversal will not occur even if we do not have a right to invoice as of the reporting date. Contract assets are classified within Prepaid expenses and other on the Condensed Consolidated Balance Sheet. • The classification of allowances for estimated price protection, reserves for returns and other allowances as refund liabilities. Such allowances were previously recorded as contra-Accounts receivable and now are classified within Accrued expenses and other current liabilities on the Consolidated Balance Sheet. As a result of adopting the New Revenue Accounting Standard the following adjustments were made to our Consolidated Balance Sheet at April 1, 2018, which also reflect the changes related to income tax accounts included in Prepaid expenses and other, Other assets, Accrued expenses and other current liabilities, and Other long-term liabilities: March 31, 2018 Adjustments April 1, 2018 ASSETS Accounts receivable, net $ 247,649 $ 53,940 $ 301,589 Software development costs and licenses 33,284 (11,096 ) 22,188 Deferred cost of goods sold 117,851 (89,867 ) 27,984 Prepaid expenses and other 133,454 33,620 167,074 Deferred cost of goods sold, net of current portion 26,719 (25,687 ) 1,032 Other assets 56,887 51,430 108,317 LIABILITIES AND STOCKHOLDERS' EQUITY Accrued expenses and other current liabilities $ 914,748 $ 69,678 $ 984,426 Deferred revenue 777,152 (230,144 ) 547,008 Non-current deferred revenue 355,589 (336,456 ) 19,133 Other long-term liabilities 158,285 34,336 192,621 Retained earnings 73,516 470,273 543,789 Accumulated other comprehensive loss (15,732 ) 4,653 (11,079 ) Recently Issued Accounting Pronouncements Accounting for Fair Value Measurement In August 2018, the FASB issued ASU 2018-13, Fair Value Measurement (Topic 820): Disclosure Framework - Changes to the Disclosure Requirements for Fair Value Measurement , which modifies the disclosure requirements on fair value measurements by removing, modifying, or adding certain disclosures. ASU 2018-13 is effective for fiscal years, and interim periods within those fiscal years, beginning December 15, 2019 (April 1, 2020 for the Company), with early adoption permitted. Certain disclosures in ASU 2018-13 are required to be applied on a retrospective basis and others on a prospective basis. We are currently evaluating the potential impact of adopting this guidance on our Consolidated Financial Statements. Accounting for Leases In February 2016, the FASB issued ASU 2016-02, Leases . This new guidance requires lessees to recognize a right-of-use asset and a lease liability for virtually all leases (other than leases that meet the definition of a short-term lease). The liability will be equal to the present value of lease payments. The asset will be based on the liability, subject to adjustment, such as for initial direct costs. For income statement purposes, the FASB retained a dual model, requiring leases to be classified as either operating or finance. Operating leases will result in straight-line expense (similar to current operating leases) while finance leases will result in a front-loaded expense pattern (similar to current capital leases). Classification will be based on criteria that are largely similar to those applied in current lease accounting. This update is effective for annual periods, and interim periods within those years, beginning after December 15, 2018 (April 1, 2019 for the Company). This new guidance must be adopted using a modified retrospective approach whereby lessees and lessors are required to recognize and measure leases at the beginning of the earliest period presented using a modified retrospective approach. Early adoption is permitted. We are currently evaluating the impact of adopting this update on our Consolidated Financial Statements, which will consist primarily of a balance sheet gross up of our operating leases, mostly for office space. Revenue Recognition Refer to Note 1 to our Consolidated Financial Statements in our Annual Report on Form 10-K for the fiscal year ended March 31, 2018 for our revenue recognition accounting policy as it relates to revenue transactions prior to April 1, 2018. The revenue recognition accounting policy described below relates to revenue transactions from April 1, 2018 and thereafter, which are accounted for in accordance with Topic 606 . We derive revenue primarily from the sale of our interactive entertainment content, principally for console gaming systems such as the Sony Computer Entertainment, Inc. ("Sony") PlayStation®4 ("PS4") and PlayStation®3 ("PS3"), Microsoft Corporation ("Microsoft") Xbox One® ("Xbox One") and Xbox 360® ("Xbox 360"), the Nintendo Switch, and personal computers ("PC"), including smartphones and tablets. 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 have been transferred to our customers. 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 the 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. In addition to sales of our full game software products, certain of our software products provide customers with the option to acquire virtual currency or make in-game purchases. Revenue from the sale of virtual currency and in-game purchases is deferred and recognized ratably over the estimated service period, which is the user life. 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. Certain software products are sold to customers with a “street date” (the earliest date these products may be sold by retailers). For these products, we recognize revenue on the later of the street date or the sale date as this is generally when we have transferred control of our software products. In addition, some of our software products are sold as digital downloads. Revenue from digital downloads is generally recognized when the download is made available to the end user by a third-party digital storefront. For the sale of physical software products, the 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 our retailers. Determining the estimated sell-through period is subjective and requires significant management judgment and estimates. 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. 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. 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 our performance, 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. Contract assets are recorded within Prepaid expenses and other on our Consolidated Balance Sheet. Our allowance for doubtful accounts are typically immaterial and, if required, are based on our best estimate of probable 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. 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, 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, and Valve's Steam, 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 are reported within Cost of goods sold. 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 goods sold because we are responsible for delivery of the product to our customers prior to transfer of control to the customer. Estimated Service Period For 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 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. 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 9 and 15 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 as we typically do not have observable standalone selling prices for our game related service performance obligations. 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. 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 our 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 and Allowances for Returns 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 future price protection and product returns related to current period software product revenue. We estimate the amount of future 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. Revenue is recognized after deducting the estimated price protection and allowances for returns, which are accounted for as variable consideration. Price protection and allowances for returns are considered refund liabilities and are reported within Accrued expenses and other current liabilities on our Consolidated Balance Sheet. Sales Incentives 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 and are considered refund liabilities, which are reported within Accrued expenses and other current liabilities in 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, the time it takes our physical products to sell-through to end users, and the amounts of future price protection and allowance for returns. 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. |
