XML 18 R7.htm IDEA: XBRL DOCUMENT
v3.8.0.1

Nature of Business | 6 Months Ended
--- | ---
Mar. 31, 2018
Accounting Policies [Abstract] |
Nature of Business | Nature of Business Fair Isaac Corporation Incorporated under the laws of the State of Delaware, Fair Isaac Corporation (“FICO”) is a provider of analytic, software and data management products and services that enable businesses to automate, improve and connect decisions. FICO provides a range of analytical solutions, credit scoring and credit account management products and services to banks, credit reporting agencies, credit card processing agencies, insurers, retailers, telecommunications providers, pharmaceutical companies, healthcare organizations, public agencies and organizations in other industries. In these condensed consolidated financial statements, Fair Isaac Corporation is referred to as “FICO,” “we,” “us,” “our,” or “the Company.” Principles of Consolidation and Basis of Presentation We have prepared the accompanying unaudited interim condensed consolidated financial statements in accordance with the instructions to Form 10-Q and the applicable accounting guidance. Consequently, we have not necessarily included all information and footnotes required for audited financial statements. In our opinion, the accompanying unaudited interim condensed consolidated financial statements reflect all adjustments (consisting only of normal recurring adjustments, except as otherwise indicated) necessary for a fair presentation of our financial position and results of operations. These unaudited condensed consolidated financial statements and notes thereto should be read in conjunction with our audited consolidated financial statements and notes thereto presented in our Annual Report on Form 10-K for the year ended September 30, 2017. The interim financial information contained in this report is not necessarily indicative of the results to be expected for any other interim period or for the entire fiscal year. The condensed consolidated financial statements include the accounts of FICO and its subsidiaries. All intercompany accounts and transactions have been eliminated. Use of Estimates We make estimates and assumptions that affect the amounts reported in the financial statements and the disclosures made in the accompanying notes. For example, we use estimates in determining the collectability of accounts receivable; the appropriate levels of various accruals; labor hours in connection with fixed-fee service contracts; the amount of our tax provision and the realizability of deferred tax assets. We also use estimates in determining the remaining economic lives and carrying values of acquired intangible assets, property and equipment, and other long-lived assets. In addition, we use assumptions to estimate the fair value of reporting units and share-based compensation. Actual results may differ from our estimates. New Accounting Pronouncements In May 2014, the Financial Accounting Standards Board (“FASB”) issued ASU No. 2014-09, “Revenue from Contracts with Customers (Topic 606)” (“ASU 2014-09”). ASU 2014-09 requires an entity to recognize the amount of revenue to which it expects to be entitled for the transfer of promised goods or services to customers. ASU 2014-09 will replace most existing revenue recognition guidance in U.S. Generally Accepted Accounting Principles when it becomes effective and permits the use of either the retrospective or cumulative effect transition method. The guidance also requires additional disclosure about the nature, amount, timing and uncertainty of revenue and cash flows arising from customer contracts. In August 2015, the FASB issued ASU No 2015-14, “Deferral of the Effective Date” (“ASU 2015-14”), which defers the effective date for ASU 2014-09 by one year. For public entities, the guidance in ASU 2014-09 will be effective for annual reporting periods beginning after December 15, 2017 (including interim reporting periods within those periods), which means it will be effective for our fiscal year beginning October 1, 2018. Early adoption is permitted to the original effective date of December 15, 2016 (including interim reporting periods within those periods). In March 2016, the FASB issued ASU No. 2016-08, “Principal versus Agent Considerations (Reporting Revenue versus Net)” (“ASU 2016-08”), which clarifies the implementation guidance on principal versus agent considerations in the new revenue recognition standard. In April 2016, the FASB issued ASU No. 2016-10, “Identifying Performance Obligations and Licensing” (“ASU 2016-10”), which reduces the complexity when applying the guidance for identifying performance obligations and improves the operability and understandability of the license implementation guidance. In May 2016, the FASB issued ASU No. 2016-12 “Narrow-Scope Improvements and Practical Expedients” (“ASU 2016-12”), which amends the guidance on transition, collectability, noncash consideration and the presentation of sales and other similar taxes. In December 2016, the FASB further issued ASU 2016-20, “Technical Corrections and Improvements to Topic 606, Revenue from Contracts with Customers” (“ASU 2016-20”), which makes minor corrections or minor improvements to the Codification that are not expected to have a significant effect on current accounting practice or create a significant administrative cost to most entities. The amendments are intended to address implementation issues that were raised by stakeholders and provide additional practical expedients to reduce the cost and complexity of applying the new revenue standard. These amendments have the same effective date as the new revenue standard. We have established a cross-functional implementation team consisting of representatives across the organization to address the scope of work required to implement the recognition and disclosure requirements under the new standard. This cross-functional implementation team has developed a project plan, which includes evaluating customer contracts across the organization, developing policies, processes and tools to report financial results, and implementing and evaluating our internal controls over financial reporting that will be necessary under the new standard. We currently plan to adopt Topic 606 in the first quarter of our fiscal 2019 using the retrospective transition method. Our ability to adopt Topic 606 using the full retrospective method is dependent on system readiness, and the completion of our analysis of information necessary to restate prior period financial statements. As we continue to assess the new standard along with industry trends and additional interpretive guidance, we may adjust our implementation plan accordingly. We are continuing to assess the impact of adopting Topic 606 on our consolidated financial statements and believe the new standard will impact the following policies and disclosures:
• | Timing of revenue recognition of license revenue on term licenses and transactional revenue on guaranteed minimum fees related to our on-premises software products. Under the new standard, we expect to recognize revenue when control of the license is transferred to the customer, rather than at the date payments become due and payable or ratably over the term of the contract required under the current standard;
• | Presentation of contract balances. Under the new standard, when we enter into noncancellable contracts that provide unconditional rights to payment from our customers for services that we have not yet completed providing or services we will provide in the near future, we expect to present the unconditional rights as receivables, regardless of whether cash has been received from customers;
• | Required disclosures including information about remaining transaction price and when we expect to recognize revenue; and
• | Accounting for commissions under the new standard will result in the deferral of incremental commission costs for obtaining contracts.
We do not currently expect Topic 606 to have a significant effect on the timing of revenue recognition for our maintenance or professional services revenues, or SaaS contracts. In October 2016, the FASB issued ASU No. 2016-16, “Income Taxes (Topic 740): Intra-Entity Transfers of Assets Other Than Inventory” (“ASU 2016-16”). ASU 2016-16 requires an entity to recognize the income tax consequences of an intra-entity transfer of an asset, other than inventory, when the transfer occurs. The guidance is effective for fiscal years and interim periods beginning after December 15, 2017, which means it will be effective for our fiscal year beginning October 1, 2018. ASU 2016-16 should be applied on a modified retrospective basis through a cumulative-effect adjustment directly to retained earnings at the beginning of the period of adoption. Early adoption is permitted as of the beginning of an annual reporting period for which financial statements (interim or annual) have not been issued. We do not believe that adoption of ASU 2016-16 will have a significant impact on our consolidated financial statements. In February 2016, the FASB issued ASU No. 2016-02, “Leases (Topic 842)” (“ASU 2016-02”), which requires lessees to put most leases on their balance sheets but recognize the expenses on their income statements in a manner similar to current practice. ASU 2016-02 states that a lessee would recognize a lease liability for the obligation to make lease payments and a right-to-use asset for the right to use the underlying asset for the lease term. ASU 2016-02 is effective for fiscal years and interim periods within those fiscal years beginning after December 15, 2018, which means it will be effective for our fiscal year beginning October 1, 2019. Early adoption is permitted. We are currently evaluating the timing of our adoption and the impact that the updated standard will have on our 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 business description and accounting policies concepts. Business description describes the nature and type of organization including but not limited to organizational structure as may be applicable to holding companies, parent and subsidiary relationships, business divisions, business units, business segments, affiliates and information about significant ownership of the reporting entity. Accounting policies describe all significant accounting policies of the reporting entity. + References Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -URI http://asc.fasb.org/topic&trid=2134479 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_BusinessDescriptionAndAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration