XML 31 R20.htm IDEA: XBRL DOCUMENT
v3.19.2

Nature of Business (Policies) | 9 Months Ended
--- | ---
Jun. 30, 2019
Accounting Policies [Abstract] |
Fair Isaac Corporation | 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 this Quarterly Report on Form 10-Q, Fair Isaac Corporation is referred to as “FICO,” “we,” “us,” “our,” or “the Company.”
Principles of Consolidation and Basis of Presentation | 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 fiscal year ended September 30, 2018. 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. Effective October 1, 2018, we adopted Accounting Standards Update (“ASU”) No. 2014-09, “Revenue from Contracts with Customers (Topic 606)” (“ASU 2014-09”) using the full retrospective method. In connection with this adoption, the results and related disclosures for the comparative fiscal 2018 periods presented in this Form 10-Q were adjusted to be presented as if ASU 2014‑09 had been in effect during such fiscal 2018 periods. See “New Accounting Pronouncements” below and Note 8. All amounts and disclosures set forth in this Form 10-Q reflect these changes. The condensed consolidated financial statements include the accounts of FICO and its subsidiaries. All intercompany accounts and transactions have been eliminated.
Use of Estimates | 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.
Revenue Recognition | Revenue Recognition Revenue is recognized when control of the promised goods or services is transferred to our customers, in an amount that reflects the consideration to which we expect to be entitled to in exchange for those goods or services. See Note 8 for further discussion on revenues. Contract Balances We record a receivable when we satisfy a performance obligation prior to invoicing if only the passage of time is required before payment is due or if we have an unconditional right to consideration before we satisfy a performance obligation. We record a contract asset when we satisfy a performance obligation prior to invoicing but our right to consideration is conditional. We record deferred revenue when the payment is made or due before we satisfy a performance obligation. We apply the optional exemption that permits the omission of information about remaining performance obligations that have original expected durations of one year or less. We also applied the transition practical expedient that permits the omission of prior-period information about our performance obligations. Significant Judgments Our contracts with customers often include promises to transfer multiple products and services to a customer. Determining whether products and services are considered distinct and should be accounted for separately may require significant judgment. Specifically, when implementation service is included in the original software or SaaS offerings, judgment is required to determine if the implementation service significantly modifies or customizes the software or SaaS service in such a way that the risks of providing it and the customization service are inseparable. In rare instances, contracts may include significant modification or customization of the software of SaaS service and will result in the combination of software or SaaS service and implementation service as one performance obligation. We determine the SSPs using data from our historical standalone sales, or, in instances where such information is not available (such as when we do not sell the product or service separately), we consider factors such as the stated contract prices, our overall pricing practices and objectives, go-to-market strategy, size and type of the transactions, and effects of the geographic area on pricing, among others. When the selling price of a product or service is highly variable, we may use the residual approach to determine the SSP of that product or service. Significant judgment may be required to determine the SSP for each distinct performance obligation when it involves the consideration of many market conditions and entity-specific factors discussed above. Significant judgement may be required to determine the timing of satisfaction of a performance obligation in certain professional services contracts with a fixed consideration, in which we measure progress using an input method based on labor hours expended. In order to estimate the total hours of the project, we make assumptions about labor utilization, efficiency of processes, the customer’s specification and IT environment, among others. For certain complex projects, due to the risks and uncertainties inherent with the estimation process and factors relating to the assumptions, actual progress may differ due to the change in estimated total hours. Adjustments to estimates are made in the period in which the facts requiring such revisions become known and, accordingly, recognized revenues are subject to revisions as the contract progresses to completion. Capitalized Commission Costs We capitalize incremental commission fees paid as a result of obtaining customer contracts. Capitalized commission costs, which are recorded in other assets within the accompanying condensed consolidated balance sheets, were $31.7 million and $27.1 million at June 30, 2019 and September 30, 2018, respectively. Capitalized commission costs are amortized on a straight-line basis over ten years — determined using a portfolio approach — based on the transfer of goods or services to which the assets relate, taking into consideration both the initial and future contracts as we do not typically pay a commission on a contract renewal. The amortization costs are included in selling, general, and administrative expenses of our condensed consolidated statements of income and comprehensive income. The amount of amortization was $1.3 million and $1.1 million during the quarters ended June 30, 2019 and 2018, respectively, and $3.7 million and $3.3 million during the nine months ended June 30, 2019 and 2018, respectively. There was no impairment loss in relation to the costs capitalized. We apply a practical expedient to recognize the incremental costs of obtaining contracts as an expense when incurred if the amortization period of the assets that we otherwise would have recognized is one year or less. These costs are recorded within selling, general, and administrative expenses. In instances where the timing of revenue recognition differs from the timing of invoicing, we have determined our contracts generally do not include a significant financing component. The primary purpose of our invoicing terms is to provide customers with simplified and predictable ways of purchasing our products and services, not to provide customers with financing or to receive financing from our customers. Examples include multi-year on-premises licenses that are invoiced annually with revenue recognized upfront, and invoicing at the beginning of a subscription term with revenue recognized ratably over the contract period. Contracts with Customers Our revenue is primarily derived from term-based or perpetual licensing of software and scoring products and solutions, and associated maintenance; SaaS subscription services; scoring and credit monitoring services for consumers; and professional services. For contracts with customers that contain various combinations of products and services, we evaluate whether the products or services are distinct — distinct products or services will be accounted for as separate performance obligations, while non-distinct products or services are combined with others to form a single performance obligation. For contracts with multiple performance obligations, the transaction price is allocated to each performance obligation on a relative standalone selling price (“SSP”) basis. Revenue is recognized when control of the promised goods or services is transferred to our customers. License revenue is derived from contracts in which we grant our direct customers or distributors the right to deploy or resell our software and scoring products and solutions on-premises. Our software offerings often include a perpetual or term-based license and post-contract support or maintenance, both of which generally represent distinct performance obligations and are accounted for separately. The transaction price is either in the form of a fixed consideration with separate stated prices for license and maintenance, or a sales or usage-based royalty — sometimes subject to a guaranteed minimum — for the license and maintenance bundle. When the amount is in the form of a fixed consideration, including the guaranteed minimum in sales or usage-based royalty, license revenue from distinct on-premises license is recognized at the point in time when the software or scoring solution is made available to the customer or distributor. Any royalties not subject to the guaranteed minimum or earned in excess of the minimum amount are recognized as transactional revenue when the subsequent sales or usage occurs. Revenue allocated to maintenance is generally recognized ratably over the contract period as customers simultaneously consume and receive benefits. In addition to sales or usage-based royalty on our software and scoring products, transactional revenue is also derived from SaaS contracts in which we provide customers with access to and standard support for our software application either in the FICO® Analytic Cloud or Amazon Web Services (“AWS”), our primary cloud infrastructure provider, on a subscription basis. The transaction price typically includes a fixed consideration in the form of a guaranteed minimum that allows up to a certain level of usage and a variable consideration in the form of usage or transaction-based fees in excess of the minimum threshold; or usage or transaction-based variable amount not subject to a minimum threshold. We determined the nature of our SaaS arrangements is to provide continuous access to our hosted application in the cloud, i.e., a stand-ready obligation that comprises a series of distinct service periods (e.g., a series of distinct daily, monthly or annual periods of service). We estimate the total variable consideration at contract inception — subject to any constraints that may apply — and update the estimates as new information becomes available and recognize the amount ratably over the SaaS service period, unless we determine it is appropriate to allocate the variable amount to each distinct service period and recognize revenue as each distinct service period is performed. We also derive transactional revenue from credit scoring and monitoring services that provide consumers access to their credit reports and enable them to monitor their credit. These are provided as either a one-time or ongoing subscription service renewed monthly or annually, all with a fixed consideration. We determined the nature of the subscription service is a stand-ready obligation to generate credit reports, provide credit monitoring and other services for our customers, which comprises a series of distinct service periods (e.g., a series of distinct daily, monthly or annual periods of service). Revenue from one-time or monthly subscription services is recognized during the period when service is performed. Revenue from annual subscription services is recognized ratably over the subscription period. Professional services include software or SaaS implementation, consulting, model development, training services and premium cloud support. They are sold either standalone, or together with other products or services and generally represent distinct performance obligations. The transaction price can be a fixed amount or on a time and materials basis. Revenue on fixed-price services is recognized using an input method based on labor hours expended which we believe provides a faithful depiction of the transfer of services. Revenue on services provided on a time and materials basis is recognized applying the “right-to-invoice” practical expedient as the amount to which we have a right to invoice the customer corresponds directly with the value of our performance to the customer. In addition, we sell premium cloud support on a subscription basis for a fixed amount, and revenue is recognized ratably over the contract term.
New Accounting Pronouncements | New Accounting Pronouncements Recently Adopted Accounting Pronouncements In May 2014, the Financial Accounting Standards Board (“FASB”) issued ASU 2014-09. The standard’s core principle is that a reporting entity will recognize revenue when it transfers promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. In addition, the standard requires disclosure of the nature, amount, timing, and uncertainty of revenue and cash flows arising from the contracts with customers. The guidance permits two methods of adoption: retrospectively to each prior reporting period presented (“full retrospective method”), or retrospectively with the cumulative effect of initially applying the guidance recognized at the date of initial application (“modified retrospective method”). We adopted ASU 2014-09 in the first quarter of our fiscal 2019 using the full retrospective method which required us to adjust each prior reporting period presented. This adoption primarily affected 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 recognize revenue when control of the license is transferred to the customer, rather than at the date payments become due and payable when there are extended payment terms, or ratably over the term of the contract as required under the previous standard. In addition, revenue attributable to a software license renewal is recognized at the beginning of the applicable renewal period rather than at the signing of the renewal agreement as required under the previous standard. Additionally, under the new standard, when we enter into noncancellable contracts that provide unconditional rights to payment from our customers for services we have not yet completed or services we will provide in the near future, we present receivables — our unconditional rights to payments — and deferred revenues on a gross basis, rather than on a net basis. Finally, under the new standard we capitalize and amortize contract acquisition costs such as commissions paid for software-as-a-service (“SaaS”) cloud services contracts in excess of one year. Following the adoption of ASU 2014-09, the revenue recognition for our other sales arrangements remained materially consistent with our historical practice. Upon adoption of ASU 2014-09, we applied the standard’s practical expedients that permit the omission of prior-period information about our performance obligations. Adoption of the standard impacted our previously reported results as follows: Condensed Consolidated Balance Sheets
| September 30, 2018
| As Previously Reported |  | Adjustment |  | As Adjusted
| (In thousands)
Accounts receivable, net | $ | 208,865 |  |  | $ | 57,877 |  |  | $ | 266,742 |
Deferred income taxes | 20,117 |  |  | (6,312 | ) |  | 13,805 |
Other assets | 12,431 |  |  | 23,823 |  |  | 36,254 |
Other accrued liabilities | 30,457 |  |  | 568 |  |  | 31,025 |
Deferred revenue | 52,215 |  |  | 51,120 |  |  | 103,335 |
Stockholders’ equity | 263,737 |  |  | 23,700 |  |  | 287,437 |
Condensed Consolidated Statements of Income and Comprehensive Income
| Quarter Ended June 30, 2018 |  | Nine Months Ended June 30, 2018
| As Previously Reported |  | Adjustment |  | As Adjusted |  | As Previously Reported |  | Adjustment |  | As Adjusted
| (In thousands, except per share amounts)
Revenues | $ | 259,505 |  |  | $ | (4,512 | ) |  | $ | 254,993 |  |  | $ | 752,684 |  |  | $ | (9,070 | ) |  | $ | 743,614 |
Cost of revenues | 78,390 |  |  | 621 |  |  | 79,011 |  |  | 231,268 |  |  | 1,668 |  |  | 232,936 |
Selling, general and administrative | 98,685 |  |  | (1,294 | ) |  | 97,391 |  |  | 286,038 |  |  | (2,180 | ) |  | 283,858 |
Provision for income taxes | 9,380 |  |  | (1,199 | ) |  | 8,181 |  |  | 24,565 |  |  | (10,392 | ) |  | 14,173 |
Net income | 32,361 |  |  | (2,640 | ) |  | 29,721 |  |  | 91,935 |  |  | 1,834 |  |  | 93,769 |
Comprehensive income | 13,565 |  |  | (2,640 | ) |  | 10,925 |  |  | 85,335 |  |  | 1,834 |  |  | 87,169 |
Basic earnings per share | 1.09 |  |  | (0.09 | ) |  | 1.00 |  |  | 3.07 |  |  | 0.06 |  |  | 3.13 |
Diluted earnings per share | 1.04 |  |  | (0.09 | ) |  | 0.95 |  |  | 2.93 |  |  | 0.06 |  |  | 2.99 |
Condensed Consolidated Statement of Cash Flows
| Nine Months Ended June 30, 2018
| As Previously Reported |  | Adjustment |  | As Adjusted
| (In thousands)
Cash flows from operating activities: |  |  |  |  |
Net income | $ | 91,935 |  |  | $ | 1,834 |  |  | $ | 93,769 |
Deferred income taxes | 6,749 |  |  | (10,392 | ) |  | (3,643 | )
Changes in operating assets and liabilities | (12,489 | ) |  | 8,558 |  |  | (3,931 | )
Recent Accounting Pronouncements Not Yet Adopted In June 2016, the FASB issued ASU No. 2016-13, “Financial Instruments—Credit Losses (Topic 326): Measurement of Credit Losses on Financial Instruments” and subsequent amendments to the initial guidance: ASU 2018-19, ASU 2019-04 and ASU 2019-05 (collectively, “Topic 326”). Topic 326 requires measurement and recognition of expected credit losses for financial assets held. Topic 326 is effective for fiscal years and interim periods within those fiscal years beginning after December 15, 2019, which means it will be effective for our fiscal year beginning October 1, 2020. Early adoption is permitted. We are currently evaluating the impact of our pending adoption of Topic 326 on our consolidated financial statements. In February 2016, the FASB issued ASU No. 2016-02, “Leases (Topic 842)” and subsequent amendments to the initial guidance: ASU 2017-13, ASU 2018-10, ASU 2018-11, ASU 2018-20 and ASU 2019-01 (collectively, “Topic 842”). Topic 842 requires companies to generally recognize on the balance sheet operating and financing lease liabilities and corresponding right-of-use assets. Topic 842 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 impact of our pending adoption of Topic 842 on our consolidated financial statements. We expect that most of our operating leases will be recognized as right-of-use assets and corresponding lease liabilities on our consolidated balance sheets, which will increase our total assets and total liabilities upon adoption. We do not expect that any other recently issued accounting pronouncements will have a significant effect on our financial statements.

X
- Definition Nature of Operations, Policy [Policy Text Block] + References No definition available. + Details
Name: | fico_NatureOfOperationsPolicyPolicyTextBlock
Namespace Prefix: | fico_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

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 Disclosure of accounting policy for basis of accounting, or basis of presentation, used to prepare the financial statements (for example, US Generally Accepted Accounting Principles, Other Comprehensive Basis of Accounting, IFRS). + References No definition available. + Details
Name: | us-gaap_BasisOfAccountingPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy pertaining to new accounting pronouncements that may impact the entity's financial reporting. Includes, but is not limited to, quantification of the expected or actual impact. + References No definition available. + Details
Name: | us-gaap_NewAccountingPronouncementsPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for revenue from contract with customer. + References Reference 1: http://www.xbrl.org/2003/role/exampleRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (e) -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 + Details
Name: | us-gaap_RevenueFromContractWithCustomerPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for the use of estimates in the preparation of financial statements in conformity with generally accepted accounting principles. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 12 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6191-108592 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 11 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6161-108592 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 9 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6143-108592 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (b) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 Reference 5: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6061-108592 Reference 6: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 8 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6132-108592 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (c) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 + Details
Name: | us-gaap_UseOfEstimates
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration