Summary Of Significant Accounting Policies | 3 Months Ended |
Mar. 31, 2014 |
Accounting Policies [Abstract] | ' |
Summary Of Significant Accounting Policies | ' |
Summary of significant accounting policies |
Unaudited interim consolidated financial statements |
The accompanying interim consolidated financial statements have been prepared pursuant to the rules and regulations of the United States Securities and Exchange Commission (“SEC”) for interim financial reporting. These consolidated statements are unaudited and, in the opinion of management, include all adjustments (consisting of normal recurring adjustments and accruals) necessary to state fairly the consolidated balance sheets, consolidated statements of comprehensive income, consolidated statements of cash flows and consolidated statements of stockholders’ equity, for the periods presented in accordance with accounting principles generally accepted in the United States (“GAAP”). The consolidated balance sheet at December 31, 2013, has been derived from the audited consolidated financial statements at that date. Operating results and cash flows for the three months ended March 31, 2014 are not necessarily indicative of the results that may be expected for the fiscal year ending December 31, 2014, or any other future period. Certain information and footnote disclosures normally included in annual financial statements prepared in accordance with GAAP have been omitted in accordance with the rules and regulations for interim reporting of the SEC. These interim consolidated financial statements should be read in conjunction with the consolidated financial statements and notes thereto included in our Annual Report on Form 10-K for the year ended December 31, 2013, and other forms filed with the SEC from time to time. |
In order to provide comparability between periods presented, amortization of software development costs and amortization of deferred financing costs and discount have been separated from other non-cash adjustments in the previously reported consolidated statements of cash flows to conform to the consolidated statement of cash flow presentation of the current period. After this change in presentation, amounts related to the amortization of software development costs are included in depreciation and amortization and amounts related to the amortization of deferred financing costs and discount are presented separately within cash flows from operating activities. Similarly, restructuring costs have been separated from general and administrative expense in the previously reported consolidated statements of comprehensive income to conform to the consolidated statement of comprehensive income presentation of the current period. After this change in presentation, restructuring costs are presented separately within operating expenses. |
Basis of consolidation |
The consolidated financial statements include the accounts of Blackbaud, Inc. and its wholly-owned subsidiaries. All significant intercompany balances and transactions have been eliminated in consolidation. |
Use of estimates |
The preparation of financial statements in conformity with GAAP requires management to make estimates and assumptions. These estimates and assumptions affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the date of the financial statements, as well as the reported amounts of revenues and expenses during the reporting periods. On an ongoing basis, we reconsider and evaluate our estimates and assumptions, including those that impact revenue recognition, long-lived and intangible assets and goodwill, stock-based compensation, the provision for income taxes, capitalization of software development costs, our allowance for sales returns and doubtful accounts, deferred sales commissions and professional services costs, valuation of derivative instruments, accounting for business combinations and loss contingencies. Changes in the facts or circumstances underlying these estimates could result in material changes and actual results could materially differ from these estimates. |
Revenue recognition |
Our revenue is primarily generated from the following sources: (i) charging for the use of our software products in a hosted environment; (ii) selling perpetual licenses of our software products; (iii) providing professional services including implementation, training, consulting, analytic, hosting and other services; and (iv) providing software maintenance and support services. |
We recognize revenue when all of the following conditions are met: |
•Persuasive evidence of an arrangement exists; |
•The products or services have been delivered; |
•The fee is fixed or determinable; and |
•Collection of the resulting receivable is probable. |
Determining whether and when these criteria have been met can require significant judgment and estimates. We deem acceptance of an agreement to be evidence of an arrangement. Delivery of our services occurs when the services have been performed. Delivery of our products occurs when the product is shipped or transmitted, and title and risk of loss have transferred to the customers. Our typical agreements do not include customer acceptance provisions; however, if acceptance provisions are provided, delivery is deemed to occur upon acceptance. We consider the fee to be fixed or determinable unless the fee is subject to refund or adjustment or is not payable within our standard payment terms. Payment terms greater than 90 days are considered to be beyond our customary payment terms. Collection is deemed probable if we expect that the customer will be able to pay amounts under the arrangement as they become due. If we determine that collection is not probable, we defer revenue recognition until collection. Revenue is recognized net of sales returns and allowances. |
We follow guidance provided in ASC 605-45, Principal Agent Considerations, which states that determining whether a company should recognize revenue based on the gross amount billed to a customer or the net amount retained is a matter of judgment that depends on the facts and circumstances of the arrangement and that certain factors should be considered in the evaluation. |
Subscriptions |
We provide hosting services to customers who have purchased perpetual rights to certain of our software products (“hosting services”). Revenue from hosting services, as well as data enrichment services, data management services and online training programs, is recognized ratably beginning on the activation date over the term of the agreement, which generally ranges from one to three years. Any related set-up fees are recognized ratably over the estimated period that the customer benefits from the related hosting service. The estimated period of benefit is evaluated on an annual basis using historical customer retention information by product or service. |
We make certain of our software products available for use in hosted application arrangements without licensing perpetual rights to the software (“hosted applications”). Revenue from hosted applications is recognized ratably beginning on the activation date over the term of the agreement, which generally ranges from one to three years. Any revenue related to upfront activation, set-up or implementation fees is recognized ratably over the estimated period that the customer benefits from the related hosted application. Direct and incremental costs relating to upfront activation, set-up and implementation for hosted applications are capitalized until the hosted application is deployed and in use, and then expensed ratably over the estimated period that the customer benefits from the related hosted application. |
For arrangements that have multiple elements and do not include software licenses, we allocate arrangement consideration at the inception of the arrangement to those elements that qualify as separate units of accounting. The arrangement consideration is allocated to the separate units of accounting based on relative selling price method in accordance with the selling price hierarchy, which includes: (i) vendor specific objective evidence (“VSOE”) of fair value if available; (ii) third-party evidence (“TPE”) if VSOE is not available; and (iii) best estimate of selling price (“BESP”) if neither VSOE nor TPE is available. In general, we use VSOE to allocate the selling price to subscription and service deliverables. |
We offer certain payment processing services with the assistance of third-party vendors. In general, when we are the principal in a transaction based on the predominant weighting of factors identified in ASC 605-45, we record the revenue and related costs on a gross basis. Otherwise, we net the cost of revenue associated with the service against the gross amount billed to the customer and record the net amount as revenue. |
Revenue from transaction processing services is recognized when the service is provided and the amounts are determinable. Revenue directly associated with processing donations for customers are included in subscriptions revenue. |
License fees |
We sell perpetual software licenses with maintenance, varying levels of professional services and, in certain instances, with hosting services. We allocate revenue to each of the elements in these arrangements using the residual method under which we first allocate revenue to the undelivered elements, typically the non-software license components, based on VSOE of fair value of the various elements. We determine VSOE of fair value of the various elements using different methods. VSOE of fair value for maintenance services associated with software licenses is based upon renewal rates stated in the agreements with customers, which demonstrate a consistent relationship of maintenance pricing as a percentage of the contractual license fee. VSOE of fair value of professional services and other products and services is based on the average selling price of these same products and services to other customers when sold on a stand-alone basis. Any remaining revenue is allocated to the delivered elements, which is normally the software license in the arrangement. In general, revenue is recognized for software licenses upon delivery to our customers. |
When a software license is sold with software customization services, generally the services are to provide the customer assistance in creating special reports and other enhancements that will improve operational efficiency and/or help to support business process improvements. These services are generally not essential to the functionality of the software and the related revenues are recognized either as the services are delivered or upon completion. However, when software customization services are considered essential to the functionality of the software, we recognize revenue for both the software license and the services using the percentage-of-completion method. |
Services |
We generally bill consulting, installation and implementation services based on hourly rates plus reimbursable travel-related expenses. Revenue is recognized for these services over the period the services are delivered. |
We recognize analytic services revenue from donor prospect research engagements, the sale of lists of potential donors, benchmarking studies and data modeling service engagements upon delivery. In arrangements where we provide customers the right to updates to the lists during the contract period, revenue is recognized ratably over the contract period. |
We sell training at a fixed rate for each specific class at a per attendee price or at a packaged price for several attendees, and recognize the related revenue upon the customer attending and completing training. Additionally, we sell fixed-rate programs, which permit customers to attend unlimited training over a specified contract period, typically one year, subject to certain restrictions, and revenue is recognized ratably over the contract period. |
Maintenance |
We recognize revenue from maintenance services ratably over the contract term, typically one year. Maintenance contracts are at rates that vary according to the level of the maintenance program associated with the software product and are generally renewable annually. Maintenance contracts may also include the right to unspecified product upgrades on an if-and-when available basis. Certain support services are sold in prepaid units of time and recognized as revenue upon their usage. |
Deferred revenue |
To the extent that our customers are billed for the above described services in advance of delivery, we record such amounts in deferred revenue. |
Fair value measurements |
We measure certain financial assets and liabilities at fair value on a recurring basis, including derivative instruments. Fair value is defined as the exchange price that would be received upon purchase of an asset or paid to transfer a liability (an exit price) in an orderly transaction between market participants at the measurement date. We use a three-tier fair value hierarchy to measure fair value. This hierarchy prioritizes the inputs into three broad levels as follows: |
| |
• | Level 1 - Quoted prices for identical assets or liabilities in active markets; |
| |
• | Level 2 - Quoted prices for similar assets and liabilities in active markets, quoted prices for identical or similar assets in markets that are not active, and model-derived valuations in which all significant inputs and significant value drivers are observable in active markets; and |
| |
• | Level 3 - Valuations derived from valuation techniques in which one or more significant inputs are unobservable. |
Our financial assets and liabilities are classified in their entirety within the hierarchy based on the lowest level of input that is significant to fair value measurement. Changes to a financial asset's or liability's level within the fair value hierarchy are determined as of the end of a reporting period. All methods of assessing fair value result in a general approximation of value, and such value may never actually be realized. |
Recently adopted accounting pronouncements |
Effective January 1, 2014, we adopted ASU 2013-11, Income Taxes (Topic 740), Presentation of an Unrecognized Tax Benefit When a Net Operating Loss Carryforward, a Similar Tax Loss, or a Tax Credit Carryforward Exists. Under ASU 2013-11, an unrecognized tax benefit, or a portion of an unrecognized tax benefit, should be presented in the financial statements as a reduction to a deferred tax asset for a net operating loss carryforward or a similar tax loss, or a tax credit carryforward, except as follows. To the extent a net operating loss carryforward, a similar tax loss, or a tax credit carryforward is not available at the reporting date under the tax law of the applicable jurisdiction to settle any additional income taxes that would result from the disallowance of a tax position or the tax law of the applicable jurisdiction does not require the entity to use, and the entity does not intend to use, the deferred tax asset for such purpose, the unrecognized tax benefit should be presented in the financial statements as a liability and should not be combined with deferred tax assets. The adoption of ASU 2013-11 did not have a material impact on our consolidated financial statements. |