XML 39 R10.htm IDEA: XBRL DOCUMENT v2.4.0.6
Summary of Significant Accounting Policies (Policies)
3 Months Ended
Mar. 31, 2013
Accounting Policies [Abstract]  
Deferred Revenue and Unbilled Receivables [Policy Text Block]

Deferred revenue and unbilled receivables

Software license and implementation services that have been performed, but for which the Company has not invoiced the customer, are recorded as unbilled receivables, and invoices that have been issued before the software license and implementation services have been performed are recorded as deferred revenue in the accompanying unaudited condensed consolidated balance sheets. The Company generally invoices for maintenance and support services on a monthly, a quarterly or an annual basis through the maintenance and support peri
Basis of presentation
Basis of presentation

The accompanying unaudited condensed consolidated financial statements of the Company have been prepared in accordance with accounting principles generally accepted in the United States of America (“GAAP”) for interim financial reporting and applicable quarterly reporting regulations of the Securities and Exchange Commission (“SEC”). In management’s opinion, the accompanying interim unaudited condensed consolidated financial statements include all adjustments necessary for a fair statement of the financial position of the Company as of March 31, 2013, the results of operations for the three months ended March 31, 2013 and cash flows for the three months ended March 31, 2013. Certain information and disclosures normally included in the notes to the annual financial statements prepared in accordance with GAAP have been omitted from these interim unaudited condensed consolidated financial statements pursuant to the rules and regulations of the SEC. Accordingly, these unaudited condensed consolidated financial statements should be read in conjunction with the consolidated financial statements in the Company’s Annual Report on Form 10-K for the fiscal year ended December 31, 2012 (“Annual Report”) filed with the SEC. The condensed consolidated balance sheet as of December 31, 2012 was derived from the Company’s audited consolidated financial statements, but does not include all disclosures required by GAAP.

Basis of consolidation
Basis of consolidation

The unaudited condensed consolidated financial statements include the accounts of the Company and its wholly-owned subsidiaries. All intercompany transactions and balances have been eliminated in consolidation.

Dollar amounts
Dollar amounts

The dollar amounts presented in the tabular data within these footnote disclosures are stated in thousands of dollars, except per unit amounts, or as noted within the context of each footnote disclosure.
Use of estimates
Use of estimates

The Company’s management prepares the unaudited condensed consolidated financial statements in accordance with GAAP. The Company makes estimates and assumptions in the preparation of its unaudited condensed consolidated financial statements, and its estimates and assumptions may affect the reported amounts of assets and liabilities and the disclosure of contingent assets and liabilities at the date of the unaudited condensed consolidated financial statements, and the reported amounts of revenue and expenses during the reporting periods. Actual results could differ from those estimates. The complexity and judgment required in the Company’s estimation process and issues related to the assumptions, risks and uncertainties inherent in the application of the percentage-of-completion method of accounting affect the amounts of revenue, expenses, unbilled receivables and deferred revenue. Estimates are also used for, but not limited to, receivables, allowance for doubtful accounts, useful lives of assets, depreciation, income taxes and deferred tax asset valuation, valuation of stock options, other current liabilities and accrued liabilities. Numerous internal and external factors can affect estimates. The critical accounting policies related to the estimates and judgments are discussed in the Company’s Annual Report on Form 10-K for the year ended December 31, 2012 under management’s discussion and analysis of financial condition and results of operations. There have been no significant changes to the Company’s critical accounting policies as described in the Company’s Annual Report.
Revenue recognition
Revenue recognition

The Company derives its revenue from the licensing and implementation of software solutions and associated software maintenance and support. To a lesser extent, the Company's revenue includes nonsoftware related hosting services. The Company's arrangements with customers typically include: (a) license fees paid for the use of our solutions either in perpetuity or over a specified term and implementation fees for configuration, implementation and training services and (b) maintenance and support fees related to technical support and software updates. If there is significant uncertainty about contract completion or collectability is not reasonably assured, revenue is deferred until the uncertainty is sufficiently resolved or collectability is reasonably assured. In addition, revenue is recognized when persuasive evidence of an arrangement exists and fees are fixed or determinable. For certain arrangements, we engage independent contractors to assist in the implementation of our software solutions. These arrangements are analyzed based on numerous factors to determine the amount of revenue to be recognized.

In determining whether implementation services revenue should be accounted for separately from license revenue, the Company evaluates whether the professional services are considered essential to the functionality of the software using factors such as: the nature of its software products; whether they are ready for use by the customer upon receipt; the nature of its implementation services; the availability of services from other vendors; whether the timing of payments for license revenue is coincident with performance of services; and whether milestones or acceptance criteria exist that affect the realizability of the software license fee.

The Company's software license arrangements typically include implementation services that can be considered essential to the customer's usability of the licensed software solutions and accordingly do not qualify for separate accounting treatment. The license and implementation services revenues and software license revenues are generally recognized together with the implementation services using the percentage-of-completion method or completed contract method. The completed contract method is used for contracts where there is a risk over final acceptance by the customer or for contracts that are short term in nature.

The percentage-of-completion computation is measured by the percentage of man-days incurred during the reporting period as compared to the estimated total man-days necessary for each contract for implementation of the software solutions. The Company measures performance under the percentage-of-completion method using total man-day method based on current estimates of man-days to complete the project. The Company believes that for each such project, man-days expended in proportion to total estimated man-days at completion represents the most reliable and meaningful measure for determining a project's progress toward completion. Under our fixed-fee arrangements, should a loss be anticipated on a contract, the full amount is recorded when the loss is determinable.

The Company also licenses software solutions under term license agreements that typically include maintenance during the license term. When maintenance is included for the entire term of the license, there is no renewal rate and the Company has not established vendor specific objective evidence (“VSOE”) of fair value for the maintenance on term licenses. For term license agreements, revenue and the associated costs are deferred until the delivery of the solution and recognized ratably over the remaining license term.

For arrangements that include hosting services we allocate the arrangement consideration between the hosting service and other elements and recognize the hosting fee ratably beginning on the date the customer commences use of our services and continuing through the end of the customer term.

The Company's customer arrangements typically contain multiple elements that include software license, implementation services and post-implementation maintenance and support. In October 2009, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) 2009-13, Multiple-Deliverable Revenue Arrangements, (amendments to FASB Accounting Standards Codification (“ASC”)) Topic 605, Revenue Recognition), which amended the accounting standards for certain multiple deliverable revenue arrangements that contain nonsoftware related elements to:

provide updated guidance on whether multiple deliverables exist, how the deliverables in an arrangement should be separated, and how the consideration should be allocated;
require an entity to allocate revenue in an arrangement using best estimated selling price, (“BESP”) of deliverables if a vendor does not have VSOE of selling price; and
eliminate the use of the residual method and require an entity to allocate revenue using the relative selling price method.

For multiple element arrangements containing our nonsoftware services, the Company must (1) determine whether and when each element has been delivered; (2) determine fair value of each element using the selling price hierarchy of VSOE of fair value, third party evidence (“TPE”), or BESP, as applicable, and (3) allocate the total price among the various elements based on the relative selling price method.

For multiple-element arrangements that contain software and nonsoftware elements such as the Company's hosting service offerings, we allocate revenue between the software and software related elements as a group and any nonsoftware elements based on a relative fair value allocation.  We determine fair value for each deliverable using this hierarchy and utilize VSOE of fair value if it exists.

In certain instances, the Company may not be able to establish VSOE for all deliverables in an arrangement with multiple elements. This may be due to infrequently selling each element separately, not pricing solutions or services within a narrow range, or only having a limited sales history. In addition, TPE may not be available. When the Company is unable to establish selling prices using VSOE or TPE, it uses BESP in the allocation of arrangement consideration. The objective of BESP is to determine the price at which the Company would transact a sale if the product or service were sold on a stand-alone basis. For transactions that only include software and software-related elements, the Company continues to account for such arrangements under the software revenue recognition standards which require it to establish VSOE of fair value to allocate arrangement consideration to multiple deliverables.

Maintenance and support revenue includes post-implementation customer support and the right to unspecified software updates and enhancements on a when and if available basis. The Company generally invoices for maintenance and support services on a monthly, quarterly or on an annual basis through the maintenance and support period. The Company recognizes revenue from maintenance arrangements ratably over the period in which the services are provided.

Software license and implementation revenue that has been recognized, but for which the Company has not invoiced the customer, is recorded as unbilled receivables. Invoices that have been issued before software license, implementation and maintenance and support revenue has been recognized are recorded as deferred revenue in the accompanying unaudited condensed consolidated balance sheets.

Internal-use software
Internal-use software

Costs incurred to develop internal-use software during the application development stage are capitalized, stated at cost, and depreciated using the straight-line method over the estimated useful lives of the assets. Application development stage costs generally include salaries and personnel costs and third party contractor expenses associated with internal-use software configuration, coding, installation and testing. During the three months ended March 31, 2013 and 2012, the Company capitalized internal-use software development costs of $0.9 million and $0.3 million, respectively, related to its cloud-based offerings. Capitalized software for internal use is included in property and equipment, net in the unaudited condensed consolidated balance sheets.

Nonc
Noncash share-based compensation
h share-based compensation

The Company measures all share-based payments to its employees based on the grant date fair value of the awards and recognizes expense in the Company’s unaudited consolidated statement of comprehensive income on a straight-line basis over the period during which the recipient is required to perform service (generally over the vesting period of the awards). To date, the Company has granted Stock Options, Stock Appreciation Rights (“SARs”), Restricted Stock Units (“RSUs”) and Market Stock Units (“MSUs”). The MSUs are performance-based awards that vest based upon the Company’s relative shareholder return.

The following table presents the number of shares or units outstanding for each award type as of March 31, 2013 and December 31, 2012, respectively.
 
Award type
 
March 31, 2013

 
December 31, 2012

Stock options
 
1,343,710

 
1,474,828

Restricted stock units
 
1,662,751

 
1,182,726

Stock appreciation rights
 
746,225

 
789,637

Market share units
 
456,000

 
205,000

    
Stock options, SARs and RSUs vest ratably between three and four years. The actual number of MSUs that will be eligible to vest is based on the total shareholder return of the Company relative to the total shareholder return of the Russell 2000 Index (“Index”) over the Performance Period, as defined by each awards plan documents.

The fair value of the RSUs is based on the closing price of the Company’s stock on the date of grant.

The Company estimates the fair value of MSUs on the date of grant using a Monte Carlo simulation model. The determination of fair value of the MSUs is affected by the Company’s stock price and a number of assumptions including the expected volatilities of the Company’s stock and the Index, its risk-free interest rate and expected dividends. The Company’s expected volatility at the date of grant was based on the historical volatilities of the Company and the Index over the Performance Period. The Company did not estimate a forfeiture rate for the MSUs due to the limited size, the vesting period, nature of the grantee population and the lack of history of granting this type of award.

The assumptions used to value the MSUs granted during the three months ended March 31, 2013 were as follows:
 
 
 
For the three months ended March 31, 2013
Volatility
 
57%
Risk-free interest rate
 
0.35%
Expected option life in years
 
2.84
Dividend yield
 


Earnings per
Earnings per share


Earnings per share

The Company computes basic earnings per share by dividing net income by the weighted average number of common shares outstanding. Diluted earnings per share is computed by dividing net income by the weighted average number of common shares and dilutive potential common shares then outstanding. Potential common shares consist of shares issuable upon the exercise of stock options and SARs or the vesting of share-based awards. Diluted earnings per share reflect the assumed conversion of all dilutive share-based awards using the treasury stock meth
Fair value measurement
.

Fair value measurement

The Company’s financial assets that are measured at fair value on a recurring basis consisted of $58.0 million invested in treasury money market funds at both March 31, 2013 and December 31, 2012, respectively. The fair value of these accounts is determined based on quoted market prices, which represents level 1 in the fair value hierarchy as defined by ASC 820, “Fair Value Measurement and Disclosure.
Income taxes
.

Credit Facility

As of March 31, 2013, $0.2 million of unamortized debt issuance costs related to the revolving credit facility ("Revolver") is included in other long term assets in the unaudited condensed consolidated balance sheets. For the three months ended March 31, 2013, $13,000 of debt issuance cost amortization is included in interest expense in the unaudited condensed consolidated statements of comprehensive income.

As of March 31, 2013, the Company had no outstanding borrowings under the Revolver.




Income taxes

At the end of each interim reporting period, the Company estimates its annual effective tax rate to calculate its income tax provision. The estimated effective tax rate includes U.S. federal, state and foreign income taxes and is based on the application of an estimated annual income tax rate applied to the current quarter’s year-to-date pre-tax income. This estimated effective tax rate is used in providing for income taxes on a year-to-date basis and may change in subsequent interim reporting periods.

The effective tax rate (benefit) for the three months ended March 31, 2013 and 2012 was (196)% and 45%, respectively. The difference between the effective tax rate and the federal statutory rate of 34% for the three months ended March 31, 2013 was due primarily to a $1.4 million discrete benefit attributed to the 2012 Research and Experimentations ("R&E") tax credit that was retroactively reinstated in the first quarter of 2013, partially offset by a rate increase attributable to nondeductible share-based compensation expense.