McKesson 2005 Annual Report Download - page 61

Download and view the complete annual report

Please find page 61 of the 2005 McKesson 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 340

  • 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
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340

McKESSON CORPORATION
FINANCIAL NOTES (Continued)
Software systems are marketed under information systems agreements as well as service agreements. Perpetual software arrangements are
recognized at the time of delivery or under the percentage-of-completion method in accordance with Statement of Position (“SOP”) 97-2,
“Software Revenue Recognition,” and SOP 81-1, “Accounting for Performance of Construction-Type and Certain Production-Type Contracts,
based on the terms and conditions in the contract. Contracts accounted for under the percentage-of-completion method are generally measured
based on the ratio of labor costs incurred to date to total estimated labor costs to be incurred. Changes in estimates to complete and revisions in
overall profit estimates on these contracts are charged to earnings in the period in which they are determined. We accrue for contract losses if
and when the current estimate of total contract costs exceeds total contract revenue.
Hardware revenues are generally recognized upon delivery. Revenue from multi-year software license agreements is recognized ratably
over the term of the agreement. Software implementation fees are recognized as the work is performed or under the percentage-of-completion
contract method. Maintenance and support agreements are marketed under annual or multiyear agreements and are recognized ratably over the
period covered by the agreements. Remote processing service fees are recognized monthly as the service is performed. Outsourcing service
revenues are recognized as the service is performed.
We also offer our products on an application service provider (“ASP”) basis, making available our software functionality on a remote
hosting basis from our data centers. The data centers provide system and administrative support as well as hosting services. Revenue on
products sold on an ASP basis is recognized on a monthly basis over the term of the contract starting when the hosting services begin.
This segment also engages in multiple-element arrangements, which may contain any combination of software, hardware, implementation
or consulting services, or maintenance services. When some elements are delivered prior to others in an arrangement and vendor-specific
objective evidence of fair value (“VSOE”) exists for the undelivered elements, revenue for the delivered elements is recognized upon delivery
of such items. The segment establishes VSOE for hardware and implementation and consulting services based on the price charged when sold
separately, and for maintenance services, based on renewal rates offered to customers. Revenue for the software element is recognized under
the residual method only when fair value has been established for all of the undelivered elements in an arrangement. If fair value cannot be
established for any undelivered element, all of the arrangement’s revenue is deferred until the delivery of the last element or until the fair value
of the undelivered element is determinable.
Income Taxes. We account for income taxes under the asset and liability method, which requires the recognition of deferred tax assets and
liabilities for the expected future tax consequences of events that have been included in the financial statements. Under this method, deferred
tax assets and liabilities are determined based on the difference between the financial statements and tax basis of assets and liabilities using
enacted tax rates in effect for the year in which the differences are expected to reverse.
Foreign Currency Translation. Assets and liabilities of international subsidiaries are translated into U.S. dollars at year-end exchange rates,
and revenues and expenses are translated at average exchange rates during the year. Cumulative currency translation adjustments are included
in accumulated other comprehensive losses in the stockholders’ equity section of the consolidated balance sheets. Realized gains and losses
from currency exchange transactions are recorded in operating expenses in the consolidated statements of operations and were not material to
our consolidated results of operations in 2005, 2004 or 2003.
Derivative Financial Instruments. Derivative financial instruments are used principally in the management of our foreign currency and
interest rate exposures and are recorded on the balance sheet at fair value. If the derivative is designated as a fair value hedge, the changes in
the fair value of the derivative and of the hedged item attributable to the hedged risk are recognized as a charge or credit to earnings. If the
derivative is designated as a cash flow hedge, the effective portions of changes in the fair value of the derivative are recorded in accumulated
other comprehensive losses and are recognized in the consolidated statement of earnings when the hedged item affects earnings. Ineffective
portions of changes in the fair value of cash flow hedges are recognized as a charge or credit to earnings. Derivative instruments not designated
as hedges are marked-to-market at the end of each accounting period with the results included in earnings.
60