XML 34 R25.htm IDEA: XBRL DOCUMENT  v2.3.0.11
Summary of Significant Accounting Policies (Policies)
9 Months Ended
Jun. 30, 2011
Accounting for collaboration agreements
Accounting for collaboration agreements
 
In June 2011, we entered into an agreement with a large healthcare provider to acquire certain data to be used in a joint development project in exchange for $10 million, $3.5 million of which was due on June 30, 2011. In addition, under the terms of the arrangement we will be reimbursed for certain research and development costs related to specified product development projects with the objective of commercializing the resulting products. All intellectual property derived from these research and development efforts will be owned by us. Upon product introduction, we will pay royalties to this party based on the actual sales. At the end of 5 years, the party can elect to continue with the arrangement, receiving royalties on future sales, or receive a buy-out payment from us and forego future royalties. The buy-out payment is calculated based on a number of factors including the net cash flows received and paid by the parties, as well as a minimum return on those net cash flows.
 
As of the execution of the above arrangement, we have other arrangements where we have sold and will continue to sell our products and services to this party. As a result, under the guidance of ASC 605, “Revenue Recognition,” we are required to reduce the revenue recognized by the amount we pay to this customer, up to our historical revenue recorded from them. We have therefore reduced reported revenue by $3.5 million for the three months ended June 30, 2011.
 
The above development arrangement will be accounted for in accordance with ASC 730, “Research and Development.” Accordingly, any buy-out obligation will be recorded as a liability and any reimbursement of the research and development costs in excess of the buy-out obligation will be recorded as an offset to research and development costs. Royalties paid to this party upon commercialization of any products from these development efforts will be recorded as a reduction to revenue in accordance with ASC 605. During the quarter ended June 30, 2011, $4.6 million of expense reimbursement has been recorded as a reduction in research and development expense.
Adoption of new accounting standards
Adoption of new accounting standards
 
Effective October 1, 2010, we adopted the provisions in the Financial Accounting Standards Board (“FASB”) Accounting Standards Update (“ASU”) No. 2009-13, Revenue Recognition (Topic 605): Multiple-Deliverable Revenue Arrangements (“ASU 2009-13”) and ASU 2009-14. Software (Topic 985): Certain Revenue Arrangements that Include Software Elements (“ASU 2009-14”). The provisions of ASU 2009-13 apply to arrangements that are outside the scope of software revenue recognition guidance and amend Accounting Standards Codification (“ASC”) Topic 605 to (1) provide updated guidance on whether multiple deliverables exist, how the deliverables in an arrangement should be separated, and the consideration allocated; (2) require an entity to allocate revenue in an arrangement using the best estimated selling prices (“BESP”) of deliverables if a vendor does not have vendor-specific objective evidence (“VSOE”) or third-party evidence (“TPE”) of selling price; and (3) eliminate the use of the residual method and require an entity to allocate revenue using the relative selling price method. ASU 2009-14 modifies the scope of ASC Topic 985 to remove industry specific revenue accounting guidance for software and software related transactions, tangible products containing software components and non-software components that function together to deliver the product’s essential functionality. The adoption of these provisions did not have a material impact on our consolidated financial statements.
 
ASU 2009-13 does not generally change the units of accounting for our revenue transactions. For multiple-element arrangements that contain both software and non-software elements such as our hosted offerings, we allocate revenue to software or software related elements and any non-software elements separately based on the selling price hierarchy. We determine the selling price for each deliverable using VSOE of selling price, if it exists, or TPE of selling price. If neither VSOE nor TPE of selling price exist for a deliverable, we use our BESP for that deliverable. Revenue allocated to each element is then recognized when the basic revenue recognition criteria are met for each element.
 
To determine the selling price in multiple-element arrangements, we establish VSOE of fair value for the majority of our post-contract customer support, professional services, and training based on historical stand-alone sales to third-parties. Typically, we are unable to determine TPE of selling price and therefore when neither VSOE nor TPE of selling price exist, we use BESP for the purposes of allocating the arrangement consideration. We determine BESP for a product or service by considering multiple factors including, but not limited to, major product groupings, market conditions, competitive landscape, price list and discounting practice.
Recently Issued Accounting Standards
Recently Issued Accounting Standards
 
In June 2011, the FASB issued ASU No. 2011-05, “Comprehensive Income.” This ASU intends to enhance comparability and transparency of other comprehensive income components. The guidance provides an option to present total comprehensive income, the components of net income and the components of other comprehensive income in a single continuous statement or two separate but consecutive statements. This ASU eliminates the option to present other comprehensive income components as part of the statement of changes in shareowners’ equity. The provisions of this ASU will be applied retrospectively for interim and annual periods beginning after December 15, 2011. Early application is permitted. ASU 2011-05 impacts disclosure only and therefore, is not expected to, have a material impact on our financial statements.
 
In January 2010, the FASB issued ASU No. 2010-06, Improving Disclosures about Fair Value Measurements (Topic 820) — Fair Value Measurements and Disclosures to add additional disclosures about the different classes of assets and liabilities measured at fair value, the valuation techniques and inputs used, the activity in Level 3 fair value measurements, and transfers between Levels 1, 2, and 3. Levels 1, 2 and 3 of fair value measurements are defined in Note 8 below. ASU 2010-06 was effective for us for the interim reporting period beginning January 1, 2010, except for the provisions related to activity in Level 3 fair value measurements. Those provisions are effective for fiscal years beginning after December 15, 2010, and for interim periods within those fiscal years. ASU 2010-06 impacts disclosure only and therefore, did not, and is not expected to, have a material impact on our financial statements.
 
In December 2010, the FASB issued ASU No. 2010-28, Intangibles — Goodwill and Other (Topic 350): “When to Perform Step 2 of the Goodwill Impairment Test for Reporting Units with Zero or Negative Carrying Amounts. ASU 2010-28 is effective for fiscal years beginning after December 15, 2010 and amends the criteria for performing Step 2 of the goodwill impairment test for reporting units with zero or negative carrying amounts and requires performing Step 2 if qualitative factors indicate that it is more likely than not that a goodwill impairment exists. We do not believe that this will have a material impact on our consolidated financial statements.