XML 25 R14.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Revenue from Contracts with Customers | 3 Months Ended
--- | ---
Dec. 31, 2018
Revenue from Contract with Customer [Abstract] |
Revenue from Contract with Customer | Revenue from Contracts with Customers 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. Disaggregation of Revenue The following table provides information about disaggregated revenue by primary geographical market, and timing of revenue recognition, and includes a reconciliation of the disaggregated revenue with reportable segments:
| Reportable Segments
| Quarter Ended December 31, 2018 |  | Quarter Ended December 31, 2017 (As Adjusted)
| Applications | Scores | Decision Management Software | Total |  | Applications | Scores | Decision Management Software | Total
| (In thousands)
Primary Geographical Markets |  |  |  |  |  |  |  |  |
North America | $ | 80,949 |  | $ | 82,073 |  | $ | 13,824 |  | $ | 176,846 |  |  | $ | 83,739 |  | $ | 66,613 |  | $ | 13,066 |  | $ | 163,418 |
Latin America | 18,253 |  | 514 |  | 5,225 |  | 23,992 |  |  | 5,633 |  | 709 |  | 1,344 |  | 7,686 |
Europe, Middle East and Africa | 32,562 |  | 1,534 |  | 6,124 |  | 40,220 |  |  | 36,216 |  | 858 |  | 5,722 |  | 42,796 |
Asia Pacific | 15,895 |  | 1,562 |  | 3,741 |  | 21,198 |  |  | 14,586 |  | 251 |  | 3,624 |  | 18,461 |
Total | $ | 147,659 |  | $ | 85,683 |  | $ | 28,914 |  | $ | 262,256 |  |  | $ | 140,174 |  | $ | 68,431 |  | $ | 23,756 |  | $ | 232,361 |
| Reportable Segments
| Quarter Ended December 31, 2018 |  | Quarter Ended December 31, 2017 (As Adjusted)
| Applications | Scores | Decision Management Software | Total |  | Applications | Scores | Decision Management Software | Total
| (In thousands)
Timing of revenue recognition |  |  |  |  |  |  |  |  |
Products and services transferred over time* | $ | 128,627 |  | $ | 85,522 |  | $ | 20,852 |  | $ | 235,001 |  |  | $ | 126,500 |  | $ | 68,293 |  | $ | 18,738 |  | $ | 213,531 |
Products and services transferred at a point in time | 19,032 |  | 161 |  | 8,062 |  | 27,255 |  |  | 13,674 |  | 138 |  | 5,018 |  | 18,830 |
Total | $ | 147,659 |  | $ | 85,683 |  | $ | 28,914 |  | $ | 262,256 |  |  | $ | 140,174 |  | $ | 68,431 |  | $ | 23,756 |  | $ | 232,361 |
* Includes license to intellectual property (“IP”) where right to functional IP transfers at a point in time but royalty revenue is only recognized upon subsequent sales or usage (i.e., guaranteed minimums excluded from this line). 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. The following table provides information about receivables and deferred revenue from contracts with customers.
| December 31, 2018 |  | September 30, 2018
|  |  | (As Adjusted)
| (In thousands)
Receivables, which are included in “Accounts receivable, net” | $ | 250,960 |  |  | $ | 270,181 |
Deferred revenue* | $ | 108,167 |  |  | $ | 108,118 |
* Included in both deferred revenue and other liabilities on our condensed balance sheet at December 31, 2018 and September 30, 2018. Impairment loss recognized on receivables from contracts with customers during the quarter ended December 31, 2018 and 2017 was immaterial. Contract assets balance at December 31, 2018 and September 30, 2018 was immaterial. Deferred revenue primarily relates to our maintenance and SaaS contracts billed annually in advance and generally recognized ratably over the term of the service period. Significant changes in the deferred revenues balances during the quarter ended December 31, 2018 are as follows:
| Quarter Ended December 31, 2018
| (In thousands)
Deferred revenues, beginning balance | $ | 108,118 |
Revenue recognized that was included in the deferred revenues balance at the beginning of the period | (53,339 | )
Increases due to billings, excluding amounts recognized as revenue during the period | 53,388 |
Deferred revenues, ending balance | $ | 108,167 |
Revenue recognized in the quarter ended December 31, 2018 from performance obligations satisfied in previous periods was immaterial. Payment terms and conditions vary by contract type, although terms generally include a requirement of payment within 30 to 60 days. 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. Performance Obligations The following table includes estimated revenue expected to be recognized in the future related to performance obligations that are unsatisfied (or partially unsatisfied) at the end of the reporting period:
| Remaining of Fiscal 2019 |  | Fiscal 2020 |  | Fiscal 2021 |  | Fiscal 2022 |  | Thereafter |  | Total
| (In thousands)
Applications | $ | 53,507 |  |  | $ | 42,951 |  |  | $ | 20,902 |  |  | $ | 8,203 |  |  | $ | 7,535 |  |  | $ | 133,098 |
Decision Management Software | 10,116 |  |  | 7,363 |  |  | 4,787 |  |  | 2,978 |  |  | 1,818 |  |  | 27,062 |
Total | $ | 63,623 |  |  | $ | 50,314 |  |  | $ | 25,689 |  |  | $ | 11,181 |  |  | $ | 9,353 |  |  | $ | 160,160 |
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 $28.5 million and $27.1 million at December 31, 2018 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.2 million and $1.1 million during the quarters ended December 31, 2018 and 2017, respectively, and 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.

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

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration