Computer Associates 2006 Annual Report Download - page 124

Download and view the complete annual report

Please find page 124 of the 2006 Computer Associates annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 172

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172

Note 1 — Significant Accounting Policies (Continued)
agreements combine the right to use the software products with maintenance for the term of the agreement. Under
these agreements, once all four of the above noted revenue recognition criteria are met, the Company is required to
recognize revenue ratably over the term of the license agreement. For license agreements signed prior to October
2000 (the prior business model), once all four of the above noted revenue recognition criteria were met, software
license fees were recognized as revenue up-front, and the maintenance fees were deferred and subsequently
recognized as revenue over the term of the license.
Maintenance revenue is derived from two primary sources: (1) combined license and maintenance agreements
recorded under the prior business model; and (2) stand-alone maintenance agreements.
Under the prior business model, maintenance and license fees were generally combined into a single license
agreement. The maintenance portion was deferred and amortized into revenue over the initial license agreement
term. Certain of these license agreements have not reached the end of their initial terms and, therefore, continue to
amortize. This amortization is recorded to the “Maintenance” line item in the Consolidated Statements of
Operations. The deferred maintenance portion, which was optional to the customer, was determined using its
fair value based on annual, fixed maintenance renewal rates stated in the agreement. For license agreements entered
into under the Company’s current business model, maintenance and license fees continue to be combined; however,
the maintenance is inclusive for the entire term of the arrangement. The Company reports such combined fees on the
“Subscription revenue” line item in the Consolidated Statements of Operations.
The Company also records stand-alone maintenance revenue earned from customers who elect optional
maintenance. Revenue from such renewals is recognized on the “Maintenance” line item in the Consolidated
Statements of Operations over the term of the renewal agreement.
The “Deferred maintenance revenue” line item on the Company’s Consolidated Balance Sheets principally
represents payments received in advance of maintenance services rendered.
Revenue from professional service arrangements is generally recognized as the services are performed. Revenues
from committed professional services arrangements that are sold as part of a software transaction are deferred and
recognized on a ratable basis over the life of the related software transaction. If it is not probable that a project will
be completed or the payment will be received, revenue is deferred until the uncertainty is removed.
Revenue from sales to distributors, resellers, and value-added resellers (VARs) is recognized when all four of the
SOP 97-2 revenue recognition criteria noted above are met and when these entities sell the software product to their
customers. This is commonly referred to as the sell-through method. Beginning July 1, 2004, a majority of sales of
products to distributors, resellers and VARs incorporate the right for the end-users to receive certain unspecified
future software upgrades and revenue from those contracts is therefore recognized on a ratable basis.
The Company has an established business practice of offering installment payment options to customers and has a
history of successfully collecting substantially all amounts due under such agreements. The Company assesses
collectibility based on a number of factors, including past transaction history with the customer and the
creditworthiness of the customer. If, in the Company’s judgment, collection of a fee is not probable, revenue
will not be recognized until the uncertainty is removed, which is generally through the receipt of cash payment.
The Company’s standard licensing agreements include a product warranty provision for all products. Such
warranties are accounted for in accordance with Statement of Financial Accounting Standards (SFAS) No. 5,
Accounting for Contingencies.” The likelihood that the Company would be required to make refunds to customers
under such provisions is considered remote.
Under the terms of substantially all of the Company’s license agreements, the Company has agreed to indemnify
customers for costs and damages arising from claims against such customers based on, among other things,
allegations that its software products infringe the intellectual property rights of a third party. In most cases, in the
event of an infringement claim, the Company retains the right to (i) procure for the customer the right to continue
using the software product; (ii) replace or modify the software product to eliminate the infringement while
providing substantially equivalent functionality; or (iii) if neither (i) nor (ii) can be reasonably achieved, the
Company may terminate the license agreement and refund to the customer a pro-rata portion of the fees paid. Such
104