Summary of Significant Accounting Policies

9 Months Ended

Oct. 31, 2012

Summary of Significant Accounting Policies [Abstract]

SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES

NOTE B – SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES

A summary of our significant accounting policies is presented in “Note B – Significant Accounting Policies” in the fiscal year 2011 Annual Report on Form 10-K. Users of financial information for interim periods are encouraged to refer to the footnotes contained in the Annual Report on Form 10-K when reviewing interim financial results.

Acquisitions

On December 7, 2011, we completed the acquisition of substantially all of the assets of Interpoint Partners, LLC (“Interpoint”). The net acquired assets and liabilities, and related revenue and expense since December 7, 2011 are included in our condensed consolidated financial statements.

On August 16, 2012, we completed the acquisition of Meta Health Technology, Inc. (“Meta”), please see Note C for further details.

Fair Value of Financial Instruments

The FASB’s authoritative guidance on fair value measurements establishes a framework for measuring fair value, and expands disclosure about fair value measurements. This guidance enables the reader of the financial statements to assess the inputs used to develop those measurements by establishing a hierarchy for ranking the quality and reliability of the information used to determine fair values. Under this guidance, assets and liabilities carried at fair value must be classified and disclosed in one of the following three categories:

Level 1: Quoted market prices in active markets for identical assets or liabilities.

Level 2: Observable market based inputs or unobservable inputs that are corroborated by market data.

Level 3: Unobservable inputs that are not corroborated by market data.

The carrying amounts of cash and cash equivalents, accounts receivable, accounts payable and accrued expenses approximate fair value based on the short-term maturity of these instruments. Cash and cash equivalents are classified as Level 1. The carrying amount of the Company’s long-term debt approximates fair value since the interest rates being paid on the amounts approximate the market interest rate. Long-term debt is classified as Level 2. The fair value of contingent consideration for earn-out and warrants liability is determined by management with the assistance of an independent third party valuation specialist. The Company used a binomial model to estimate the fair value of the contingent consideration for earn-out and warrants liability. The contingent consideration for earn-out and warrants liability are classified as Level 3.

Revenue Recognition

We derive revenue from the sale of internally developed software either by licensing or by software as a service (SaaS), through our direct sales force or through third-party resellers. Clients with locally-installed software utilize our support and maintenance services for a separate fee, whereas SaaS fees include support and maintenance. We also derive revenue from professional services that support the implementation, configuration, training, and optimization of our applications. Additional revenues are also derived from reselling third-party software and hardware components.

We recognize revenue in accordance with ASC 985-605, Software-Revenue Recognition and ASC 605-25 Revenue Recognition – Multiple-element arrangements. Revenue recognition typically commences when the following criteria have all been met:

• Persuasive evidence of an arrangement exists,

• Delivery has occurred or services have been rendered,

• The arrangement fees are fixed or determinable, and

• Collection is considered probable.

If we determine that any of the above criteria has not been met, we will defer recognition of the revenue until all the criteria have been met. Maintenance and support, term license and SaaS agreements entered into are generally non-cancelable, or contain significant penalties for early cancellation, although clients typically have the right to terminate their contracts for cause if we fail to perform material obligations. However, if non-standard acceptance periods or non-standard performance criteria, cancellation or right of refund terms are required, revenue is recognized upon the satisfaction of such criteria, as applicable. Revenues from resellers are recognized gross of royalty payments to resellers.

Revenue Recognition – Multiple-Deliverable Revenue Arrangements

We recognize revenue in accordance with Accounting Standards Update No. 2009-13, Revenue Recognition (Topic 605), “Multiple-Deliverable Revenue Arrangements — a consensus of the FASB Emerging Issues Task Force” (“ASU 2009-13”). ASU 2009-13 amends the accounting standards for revenue recognition for multiple deliverable revenue arrangements to:

• Provide updated guidance on how deliverables of an arrangement are separated, and how consideration is allocated;

• Eliminate the residual method and require entities to allocate revenue using the relative selling price method; and;

• Require entities to allocate revenue to an arrangement using the estimated selling price (“ESP”) of deliverables if it does not have vendor specific objective evidence (“VSOE”) or third party evidence (“TPE”) of selling price.

Terms used in evaluation are as follows:

• VSOE — the price at which an element is sold as a separate stand-alone transaction.

• TPE — the price of an element, charged by another company that is largely interchangeable in any particular transaction.

• ESP — our best estimate of the selling price of an element of the transaction.

We follow accounting guidance for revenue recognition of multiple-element arrangements to determine whether such arrangements contain more than one unit of accounting. Multiple-element arrangements require the delivery or performance of multiple solutions, services and/or rights to use assets. To qualify as a separate unit of accounting, the delivered item must have value to the client on a stand-alone basis. Stand-alone value to a client is defined in the guidance as those that can be sold separately by any vendor or the client could resell the item on a stand-alone basis. Additionally, if the arrangement includes a general right of return relative to the delivered item, delivery or performance of the undelivered item or items must be considered probable and substantially in the control of the vendor.

We have developed a pricing methodology for all elements of the arrangement and proper review of pricing to ensure adherence to our policies. Pricing decisions include cross-functional teams of senior management, which uses market conditions, expected contribution margin, size of the client’s organization, and pricing history for similar solutions when establishing the selling price.

Software as a Service

We use ESP to determine the value of SaaS arrangements because we cannot establish VSOE, and TPE is not a practical alternative due to differences in functionality from our competitors. Similar to proprietary license sales, pricing decisions rely on the relative size of the client purchasing the solution, and include calculating the equivalent value of maintenance and support on a present value basis over the term of the initial agreement period. Typically revenue recognition commences once the client goes live on the system, and is recognized ratably over the contract term. The software portion of SaaS for our HIM (“Health Information Management”) products do not require material modification to achieve their contracted function. The software portion of SaaS for our PFS (“Patient Financial Services”) products require material customization and setup processes to achieve their contracted function.

System Sales

We use the residual method to determine fair value for a proprietary software license sold in a multi-element arrangement because we can establish fair value for all of the undelivered elements. Typically pricing decisions for proprietary software rely on the relative size and complexity of the client purchasing the solution. Third party components are resold at prices based on a cost plus margin analysis. The proprietary software and third party components do not need any significant modification to achieve their intended use. When these revenues meet all criteria for revenue recognition, and are determined to be separate units of accounting, revenue is recognized. Typically this is upon shipment of components or electronic download of software. Proprietary licenses are perpetual in nature, and license fees do not include rights to version upgrades, fixes or service packs.

Term Licenses

We use ESP to determine the value of term license arrangements because we cannot establish VSOE, and TPE is not a practical alternative due to differences in functionality from our competitors. Similar to proprietary license sales, pricing decisions rely on the relative size of the client purchasing the solution. Typically revenue recognition commences once the client goes live on the system, and is recognized ratably over the contract term. The software portion of our CAC (“Computer Aided Coding”) products generally do not require material modification to achieve their contracted function.

Maintenance and Support Services

The maintenance and support components are not essential to the functionality of the software and clients renew maintenance contracts separately from software purchases at renewal rates materially similar to the initial rate charged for maintenance on the initial purchase of software. We use VSOE of fair value to determine fair value of maintenance and support services. Rates are set based on market rates for these types of services, and these rates are comparable to rates charged by our competitors, which are based on the knowledge of the marketplace by senior management. Generally, maintenance and support is calculated as a percentage of the list price of the proprietary license being purchased by a client. Clients have the option of purchasing additional annual maintenance service renewals each year for which rates are not materially different from the initial rate, but typically include a nominal rate increase based on the consumer price index. Annual maintenance and support agreements entitle clients to technology support, upgrades, bug fixes and service packs.

Professional Services

Professional services components that are not essential to the functionality of the software, from time to time, are sold separately by us. Similar services are sold by other vendors, and clients can elect to perform similar services in-house. When professional services revenues are a separate unit of accounting, revenues are recognized as the services are performed.

Professional services components that are essential to the functionality of the software, and are not considered a separate unit of accounting, are recognized in revenue ratably over the life of the client, which we approximate as the duration of the initial contract term. We defer the associated direct costs for salaries and benefits expense for PFS contracts. As of October 31, 2012 we have deferred approximately $239,000. These deferred costs will be amortized over the identical term as the associated SaaS revenues.

We use VSOE of fair value based on the hourly rate charged when services are sold separately, to determine fair value of professional services. We typically sell professional services on a fixed fee basis. We monitor projects to assure that the expected and historical rate earned remains within a reasonable range to the established selling price.