XML 112 R10.htm IDEA: XBRL DOCUMENT v2.4.0.6
Basis of Presentation, Nature of Operations and Summary of Significant Accounting Policies
12 Months Ended
Dec. 29, 2012
Organization, Consolidation and Presentation of Financial Statements [Abstract]  
Organization, Consolidation and Presentation of Financial Statements Disclosure and Significant Accounting Policies [Text Block]
Basis of Presentation, Nature of Operations and Summary of Significant Accounting Policies

Basis of Presentation

The consolidated financial statements include all the accounts of Cerner Corporation and its subsidiaries. All significant intercompany transactions have been eliminated in consolidation.

The consolidated financial statements were prepared using accounting principles generally accepted in the United States. These principles require us to make estimates and assumptions that affect the reported amounts of assets and liabilities, the disclosure of contingent assets and liabilities and the reported amounts of revenues and expenses. Actual results could differ from those estimates.

Our fiscal year ends on the Saturday closest to December 31. Fiscal years 2012, 2011 and 2010 consisted of 52 weeks and ended on December 29, 2012, December 31, 2011 and January 1, 2011, respectively. All references to years in these notes to consolidated financial statements represent fiscal years unless otherwise noted.

Nature of Operations

We design, develop, market, install, host and support health care information technology, health care devices, hardware and content solutions for health care organizations and consumers. We also provide a wide range of value-added services, including implementation and training, remote hosting, operational management services, revenue cycle services, support and maintenance, health care data analysis, clinical process optimization, transaction processing, employer health centers, employee wellness programs and third party administrator services for employer-based health plans.

Summary of Significant Accounting Policies

(a) Revenue Recognition - We recognize software related revenue in accordance with the provisions of Accounting Standards Codification (ASC) 985-605, Software – Revenue Recognition and non-software related revenue in accordance with ASC 605, Revenue Recognition. In general, revenue is recognized when all of the following criteria have been met:

Persuasive evidence of an arrangement exists;
Delivery has occurred or services have been rendered;
Our fee is fixed or determinable; and
Collection of the revenue is reasonably assured.

The following are our major components of revenue:

System sales – includes the licensing of computer software, software as a service, deployment period upgrades, installation, content subscriptions, transaction processing and the sale of computer hardware and sublicensed software;
Support, maintenance and service – includes software support and hardware maintenance, remote hosting and managed services, training, consulting and implementation services; and
Reimbursed travel – includes reimbursable out-of-pocket expenses (primarily travel) incurred in connection with our client service activities.

We provide for several models of procurement of our information systems and related services. The predominant model involves multiple deliverables and includes a perpetual software license agreement, project-related installation services, implementation and consulting services, software support and either hosting services or computer hardware and sublicensed software, which requires that we allocate revenue to each of these elements.

Allocation of Revenue to Multiple Element Arrangements
 
For multiple element arrangements that contain software and non-software elements, we allocate revenue to software and software-related elements as a group and any non-software element separately. After the arrangement consideration has been allocated to the non-software elements, revenue is recognized when the basic revenue recognition criteria are met for each element. For the group of software and software-related elements, revenue is recognized under the guidance applicable to software transactions.

Since we do not have vendor specific objective evidence (VSOE) of fair value on software licenses within our multiple element arrangements, we recognize revenue on our software and software-related elements using the residual method. Under the residual method, license revenue is recognized in a multiple-element arrangement when vendor-specific objective evidence of fair value exists for all of the undelivered elements in the arrangement, when software is installed and all other conditions to revenue recognition are met. We allocate revenue to each undelivered element in a multiple-element arrangement based on the element’s respective fair value, with the fair value determined by the price charged when that element is sold separately. Specifically, we determine the fair value of the software support, hardware maintenance, sublicensed software support, remote hosting, subscriptions and software as a service portions of the arrangement based on the substantive renewal price for these services charged to clients; professional services (including training and consulting) portion of the arrangement, other than installation services, based on hourly rates which we charge for these services when sold apart from a software license; and sublicensed software based on its price when sold separately from the software. The residual amount of the fee after allocating revenue to the fair value of the undelivered elements is attributed to the licenses for software solutions, including project-related installation services. If evidence of the fair value cannot be established for the undelivered elements of a license agreement using VSOE, the entire amount of revenue under the arrangement is deferred until these elements have been delivered or VSOE of fair value can be established.

We also enter into arrangements that include multiple non-software deliverables. For each element in a multiple element arrangement that does not contain software-related elements to be accounted for as a separate unit of accounting, the following must be met: the delivered products or services have value to the client on a stand-alone basis; and for an arrangement that includes a general right of return relative to the delivered products or services, delivery or performance of the undelivered product or service is considered probable and is substantially controlled by the Company. We allocate the arrangement consideration to each element based on the selling price hierarchy of VSOE of fair value, if it exists, or third-party evidence (TPE) of selling price. If neither VSOE nor TPE are available, we use estimated selling price. After the arrangement consideration has been allocated to the elements, we account for each respective element in the arrangement as described below.

For certain arrangements, revenue for software, implementation services and, in certain cases, support services for which VSOE of fair value cannot be established are accounted for as a single unit of accounting. The revenue recognized from single units of accounting are typically allocated and classified as system sales and support, maintenance and services. If available, the VSOE of fair value of the services provides the basis for support, maintenance and services allocation, and the remaining residual consideration provides the basis for system sales revenue allocations. In cases where VSOE cannot be established, revenue is classified based on the nature of related costs incurred. The following table details the classification allocations for arrangements accounted for as a single unit of accounting:

 
 
For the Years Ended
(In millions)
 
2012
 
2011
 
2010
 
 
 
 
 
 
 
System sales
 
$
17.7

 
$
23.3

 
$
17.5

Support, maintenance and services
 
140.7

 
97.5

 
88.1


Revenue Recognition Policies for Each Element

We provide project-related installation services when licensing our software solutions, which include project-scoping services, conducting pre-installation audits and creating initial environments. We have deemed installation services to be essential to the functionality of the software and, therefore, recognize the software license over the software installation period using the percentage-of-completion method. We measure the percentage-of-completion based on output measures that reflect direct labor hours incurred, beginning at software delivery and culminating at completion of installation. Installation generally occurs in the same period the contracts are executed but in the past has been extended over a longer period of time depending on client specific factors.

We provide implementation and consulting services. These services vary depending on the scope and complexity of the engagement. Examples of such services may include database consulting, system configuration, project management, testing assistance, network consulting, post conversion review and application management services. Except for limited arrangements where our software requires significant modifications or customization, implementation and consulting services generally are not deemed to be essential to the functionality of the software and, thus, do not impact the timing of the software license recognition. However, if software license fees are tied to implementation milestones, then the portion of the software license fee tied to implementation milestones is deferred until the related milestone is accomplished and related fees become due and payable and non-forfeitable. Implementation fees are recognized over the service period, which may extend from nine months to three years for multi-phased projects.

Remote hosting and managed services are marketed under long-term arrangements generally over periods of five to 10 years. These services are typically provided to clients that have acquired a perpetual license for licensed software and have contracted with us to host the software in our data center. Under these arrangements, the client generally has the contractual right to take possession of the licensed software at any time during the hosting period without significant penalty and it is feasible for the client to either run the software on its own equipment or contract with another party unrelated to us to host the software. Additionally, these services are not deemed to be essential to the functionality of the licensed software or other elements of the arrangement and as such, we allocate a portion of the services fee to the software and recognize it once the client has the ability to take possession of the software. The remaining services fee in these arrangements, as well as the services fee for arrangements where the client does not have the contractual right or the ability to take possession of the software at any time, is generally recognized ratably over the hosting service period.

We also offer our solutions on a software as a service model, providing time-based licenses for our software solutions available within an environment that we manage from our data centers. The data centers provide system and administrative support as well as processing services. Revenue on these services is combined and recognized on a monthly basis over the term of the contract. We capitalize related pre-contract direct set-up costs consisting of third party costs and direct software installation and implementation costs associated with the initial set up of a software as a service client. These costs are amortized over the term of the arrangement.

Software support fees are marketed under annual and multi-year arrangements and are recognized as revenue ratably over the contractual support term. Hardware and sublicensed software maintenance revenues are recognized ratably over the contractual maintenance term.

Subscription and content fees are generally marketed under annual and multi-year agreements and are recognized ratably over the contractual terms.

Hardware and sublicensed software sales are generally recognized when title and risk of loss have transferred to the client.

The sale of equipment under sales-type leases is recorded as system sales revenue at the inception of the lease. Sales-type leases also produce financing income, which is included in system sales revenue and is recognized at consistent rates of return over the lease term.

Where we have contractually agreed to develop new or customized software code for a client as a single element arrangement, we utilize percentage-of-completion accounting, labor-hours method.

Revenue generally is recognized net of any taxes collected from clients and subsequently remitted to governmental authorities.

Payment Arrangements

Our payment arrangements with clients typically include an initial payment due upon contract signing and date-based licensed software payment terms and payments based upon delivery for services, hardware and sublicensed software. Revenue recognition on support payments received in advance of the services being performed are deferred and classified as either current or long term deferred revenue depending on whether the revenue will be earned within one year.

We have periodically provided long-term financing options to creditworthy clients through third party financing institutions and have directly provided extended payment terms to clients from contract date. These extended payment term arrangements typically provide for date based payments over periods ranging from 12 months up to seven years. As a significant portion of the fee is due beyond one year, we have analyzed our history with these types of arrangements and have concluded that we have a standard business practice of using extended payment term arrangements and a long history of successfully collecting under the original payment terms for arrangements with similar clients, product offerings, and economics without granting concessions. Accordingly, we consider the fee to be fixed and determinable in these extended payment term arrangements and, thus, the timing of revenue is not impacted by the existence of extended payments.

Some of these payment streams have been assigned on a non-recourse basis to third party financing institutions. We account for the assignment of these receivables as sales of financial assets. Provided all revenue recognition criteria have been met, we recognize revenue for these arrangements under our normal revenue recognition criteria, and if appropriate, net of any payment discounts from financing transactions.

(b) Cash Equivalents - Cash equivalents consist of short-term marketable securities with original maturities less than 90 days.

(c) Investments – Our short-term investments are primarily invested in time deposits, commercial paper, government and corporate bonds. Our long-term investments are primarily invested in government and corporate bonds with maturities of less than two years.

Effective April 1, 2012, we began reporting all securities in our investment portfolio as available-for-sale. The change resulted in the transfer of investments with an aggregate carrying amount of $1.0 billion from held-to-maturity to available-for-sale, with gross unrealized gains of $0.7 million and gross unrealized losses of $0.7 million. The unrealized gains and losses, net of the related tax effects, were recorded to accumulated other comprehensive income. The decision to transfer the securities to available-for-sale is intended to provide us with financial flexibility in determining whether to hold our investment securities to maturity. Such change contemplates the possibility that securities may be liquidated prior to maturity as we manage through changing market conditions.

Available-for-sale securities are recorded at fair value with the unrealized gains and losses reflected in accumulated other comprehensive income until realized. Realized gains and losses from the sale of available-for-sale securities, if any, are determined on a specific identification basis.

We regularly review investment securities for impairment based on both quantitative and qualitative criteria that include the extent to which cost exceeds fair value, the duration of any market decline, and the financial health of and specific prospects for the issuer. Unrealized losses that are other than temporary are recognized in earnings.
 
Premiums are amortized and discounts are accreted over the life of the security as adjustments to interest income for our investments. Interest income is recognized when earned.

Refer to Note (3) and Note (4) for further description of these assets and their fair value.

(d) Concentrations - Substantially all of our cash and cash equivalents are held at four major financial institutions. The majority of our cash equivalents consist of money market funds. Deposits held with banks may exceed the amount of insurance provided on such deposits. Generally these deposits may be redeemed upon demand.

As of the end of 2012, we had significant concentration of receivables owed to us by Fujitsu Services Limited, which are currently in dispute. Refer to Note (5) for additional information.

(e) Inventory - Inventory consists primarily of computer hardware and sublicensed software, held for resale. Inventory is recorded at the lower of cost (first-in, first-out) or market.

(f) Property and Equipment - We account for property and equipment in accordance with ASC 360, Property, Plant, and Equipment. Property, equipment and leasehold improvements are stated at cost. Depreciation of property and equipment is computed using the straight-line method over periods of one to 50 years. Amortization of leasehold improvements is computed using a straight-line method over the shorter of the lease terms or the useful lives, which range from periods of one to 15 years.

(g) Software Development Costs - Software development costs are accounted for in accordance with ASC 985-20, Costs of Software to be Sold, Leased or Marketed. Software development costs incurred internally in creating computer software products are expensed until technological feasibility has been established upon completion of a detailed program design. Thereafter, all software development costs incurred through the software’s general release date are capitalized and subsequently reported at the lower of amortized cost or net realizable value. Capitalized costs are amortized based on current and expected future revenue for each software solution with minimum annual amortization equal to the straight-line amortization over the estimated economic life of the solution. We amortize capitalized software development costs over five years.

(h) Goodwill - We account for goodwill under the provisions of ASC 350, Intangibles – Goodwill and Other. Goodwill is not amortized but is evaluated for impairment annually or whenever there is an impairment indicator. All goodwill is assigned to a reporting unit, where it is subject to an annual impairment assessment. Based on these evaluations, there was no impairment of goodwill in 2012, 2011 or 2010. Refer to Note (7) for more information of Goodwill and other intangible assets.

(i) Contingencies - We accrue estimates for resolution of any legal and other contingencies when losses are probable and estimable, in accordance with ASC 450, Contingencies. We currently have no material pending litigation.

The terms of our software license agreements with our clients generally provide for a limited indemnification of such clients against losses, expenses and liabilities arising from third party claims based on alleged infringement by our solutions of an intellectual property right of such third party. The terms of such indemnification often limit the scope of and remedies for such indemnification obligations and generally include a right to replace or modify an infringing solution. To date, we have not had to reimburse any of our clients for any losses related to these indemnification provisions pertaining to third party intellectual property infringement claims. For several reasons, including the lack of prior indemnification claims and the lack of a monetary liability limit for certain infringement cases under the terms of the corresponding agreements with our clients, we cannot determine the maximum amount of potential future payments, if any, related to such indemnification provisions.

From time to time we are involved in routine litigation incidental to the conduct of our business, including for example, employment disputes and litigation alleging solution defects, personal injury, intellectual property infringement, violations of law and breaches of contract and warranties. We believe that no such routine litigation currently pending against us, if adversely determined, would have a material adverse effect on our consolidated financial position, results of operations or cash flows.

(j) Derivative Instruments and Hedging Activities - We account for our hedging activities in accordance with ASC 815, Derivatives and Hedging. Historically, our use of hedging instruments has primarily been to hedge foreign currency denominated assets and liabilities. We record all hedging instruments on our consolidated balance sheets at fair value. For hedging instruments that are designated and qualify as a net investment hedge, the effective portion of the gain or loss on the hedging instrument is reported in the foreign currency translation component of other comprehensive income (loss). Any ineffective portion of the gain or loss on the hedging instrument is recorded in the results of operations immediately. Refer to Note (10) for more information on our hedging activities.

(k) Income Taxes - Income taxes are accounted for in accordance with ASC 740, Income Taxes. Deferred tax assets and liabilities are recognized for the future tax consequences attributable to differences between the financial statement carrying amounts of existing assets and liabilities and their respective tax bases. Deferred tax assets and liabilities are measured using enacted tax rates expected to apply to taxable income in the years in which those temporary differences are expected to be recovered or settled. Refer to Note (12) for additional information regarding income taxes.

(l) Earnings per Common Share - Basic earnings per share (EPS) excludes dilution and is computed, in accordance with ASC 260, Earnings Per Share, by dividing income available to common shareholders by the weighted-average number of common shares outstanding for the period. Diluted EPS reflects the potential dilution that could occur if securities or other contracts to issue stock were exercised or converted into common stock or resulted in the issuance of common stock that then shared in our earnings. Refer to Note (13) for additional details of our earnings per share computations.
 
(m) Accounting for Share-based Payments - We recognize all share-based payments to associates, directors and consultants, including grants of stock options, restricted stock and performance shares, in the financial statements as compensation cost based on their fair value on the date of grant, in accordance with ASC 718, Compensation-Stock Compensation. This compensation cost is recognized over the vesting period on a straight-line basis for the fair value of awards that actually vest. Refer to Note (14) for a detailed discussion of share-based payments.

(n) Foreign Currency - In accordance with ASC 830, Foreign Currency Matters, assets and liabilities of non-U.S. subsidiaries whose functional currency is the local currency are translated into U.S. dollars at exchange rates prevailing at the balance sheet date. Revenues and expenses are translated at average exchange rates during the year. The net exchange differences resulting from these translations are reported in accumulated other comprehensive income. Gains and losses resulting from foreign currency transactions are included in the consolidated statements of operations.

(o) Collaborative Arrangements - In accordance with ASC 808, Collaborative Arrangements, third party costs incurred and revenues generated by arrangements involving joint operating activities of two or more parties that are each actively involved and exposed to risks and rewards of the activities are classified in the consolidated statements of operations on a gross basis only if we are determined to be the principal participant in the arrangement. Otherwise, third party revenues and costs generated by collaborative arrangements are presented on a net basis. Payments between participants are recorded and classified based on the nature of the payments.

(p) Recently Adopted Accounting Pronouncements
Comprehensive Income. On January 1, 2012, we adopted Financial Accounting Standards Board (FASB) Accounting Standards Update (ASU) 2011-05, Presentation of Comprehensive Income. ASU 2011-05 requires an entity to present the total of comprehensive income, the components of net income, and the components of other comprehensive income either in a single continuous statement of comprehensive income or in two separate but consecutive statements. ASU 2011-05 eliminates the option to present the components of other comprehensive income as part of the statement of changes in equity. These consolidated financial statements include separate consolidated statements of comprehensive income.
Goodwill Impairment. On January 1, 2012, we adopted FASB ASU 2011-08, Testing for Goodwill Impairment. ASU 2011-08 amends existing guidance by giving an entity the option to first assess qualitative factors to determine whether it is more likely than not that the fair value of a reporting unit is less than the carrying amount. The more-likely-than-not threshold is defined as having a likelihood of more than 50 percent. If an entity determines that it is more likely than not that the fair value of a reporting unit is less than its carrying amount, then it is necessary to perform the two-step goodwill impairment test, as currently prescribed by FASB Accounting Standards Codification Topic 350. Otherwise, the two-step goodwill impairment test is not required. The adoption of this standard did not have a material effect on our consolidated financial statements.