XML 23 R8.htm IDEA: XBRL DOCUMENT v2.4.0.8
Revenue Recognition
3 Months Ended
Mar. 31, 2014
Text Block [Abstract]  
Revenue Recognition

3. REVENUE RECOGNITION:

Our Company recognizes revenue primarily through the provision of consulting services and the resale of third-party, off-the-shelf software and maintenance.

We generate revenue by providing consulting services under written service contracts with our customers. The service contracts we enter into generally fall into three specific categories: time and materials, fixed-price and retainer.

We consider amounts to be earned once evidence of an arrangement has been obtained, services are delivered, fees are fixed or determinable and collectability is reasonably assured. We establish billing terms at the time at which the project deliverables and milestones are agreed. Our standard payment terms are 30 days from invoice date. Out-of-pocket reimbursable expenses charged to customers are reflected as revenue.

When a customer enters into a time and materials, fixed-price or a periodic retainer-based contract, the Company recognizes revenue in accordance with its evaluation of the deliverables in each contract. If the deliverables represent separate units of accounting, the Company then measures and allocates the consideration from the arrangement to the separate units, based on vendor specific objective evidence (“VSOE”) of the value for each deliverable.

The revenue under time and materials contracts is recognized as services are rendered and performed at contractually agreed upon rates. Revenue pursuant to fixed-price contracts is recognized under the proportional performance method of accounting. We routinely evaluate whether revenue and profitability should be recognized in the current period. We estimate the proportional performance on our fixed-price contracts on a monthly basis utilizing hours incurred to date as a percentage of total estimated hours to complete the project. This method is used because reasonably dependable estimates of costs and revenue earned can be made, based on historical experience and milestones identified in any particular contract. If we do not have a sufficient basis to measure progress toward completion, revenue is recognized upon completion of performance, subject to any warranty provisions or other project management assessments as to the status of work performed.

Estimates of total project costs are continuously monitored during the term of an engagement. There are situations where the number of hours to complete projects may exceed our original estimate, as a result of an increase in project scope, unforeseen events that arise, or the inability of the client or the delivery team to fulfill their responsibilities. Accordingly, recorded revenues and costs are subject to revision throughout the life of a project based on current information and historical trends. Such revisions may result in increases or decreases to revenue and income and are reflected in the consolidated financial statements in the periods in which they are first identified.

If our initial estimates of the resources required or the scope of work to be performed on a contract are inaccurate, or we do not manage the project properly within the planned time period, a provision for estimated losses on incomplete projects is made. Any known or probable losses on projects are charged to operations in the period in which such losses are determined. A formal project review process takes place quarterly, although projects are continuously evaluated throughout the period. Management reviews the estimated total direct costs on each contract to determine if the estimated amounts are accurate, and estimates are adjusted as needed in the period identified. No losses were recognized on contracts during the three-month periods ended March 31, 2014 or 2013.

We also perform services on a periodic retainer basis under infrastructure service contracts, which include monthly hosting and support services. Revenue under periodic retainer-based contracts is recognized ratably over the contract period, as outlined within the respective contract. In the event additional services are required, above the minimum retained or contracted amount, then such services are billed on a time and materials basis.

Typically, the Company provides warranty services on its fixed-price contracts related to providing customers with the ability to have any “design flaws” remedied and/or have our Company “fix” routine defects. The warranty services, as outlined in the respective contracts, are provided for a specific period of time after a project is complete. The Company values the warranty services based upon historical labor hours incurred for similar services at standard billing rates. Revenue related to the warranty provisions within our fixed-price contracts is recognized as the services are performed or the revenue is earned. The warranty period is typically for a 30-60 day period after the project is complete.

Customer prepayments, even if nonrefundable, are deferred (classified as deferred revenue on the condensed consolidated balance sheets) and recognized over future periods as services are performed.

Software revenue represents the resale of certain third-party off-the-shelf software and maintenance and is recorded on a gross basis provided we act as a principal in the transaction, which we have determined based upon several factors, including, but not limited to, the fact that we have credit risk and we set the price to the end user. In the event we do not meet the requirements to be considered a principal in the software sale transaction and act as an agent, software revenue is recorded on a net basis.

Prior to the second quarter of 2013, we recorded substantially all of our software resale revenue on a gross basis (reporting the revenue and cost from the transaction in our consolidated statement of comprehensive income (loss)). However, beginning in the second quarter of 2013, due to changes in the nature of the terms of certain of our Microsoft Dynamics AX software resale arrangements (primarily related to the risk of credit loss and ability to establish pricing), we began to recognize a portion of our software resale revenue on a net basis (reporting only the net profit from the transaction as revenue in our consolidated statement of comprehensive income (loss)). We expect this trend to continue and also anticipate that the number of new software resale arrangements subject to these terms may increase in future periods. Additionally, the changes in the terms of the resale arrangements may, in certain situations, extend the timing of the recognition period (from full, immediate recognition of the gross margin on the transaction to recognition of the gross margin on the transaction over a three-year period) due to payment terms being spread over a multiple year period. This would reduce the amount of the software revenue and associated gross margin to be recognized by the Company in the initial period of the sale.

 

The majority of the software sold by the Company is delivered electronically. For software that is delivered electronically, we consider delivery to have occurred when the customer either (a) takes possession of the software via a download (that is, when the customer takes possession of the electronic data on its hardware), or (b) has been provided with access codes that allow the customer to take immediate possession of the software on its hardware pursuant to an agreement or purchase order for the software.

The Company enters into multiple element arrangements which typically include software, post-contract support (or maintenance), and consulting services. Consistent with the software described above, maintenance that is in the form of a pass through transaction is recognized upon delivery of the software, as all related warranty and maintenance is performed by the primary software vendor and not the Company. Maintenance fee revenue for the Company’s software products, which is inconsequential in all years presented, is recognized ratably over the term of the arrangements, which are generally for a one-year period. The Company has established VSOE with respect to the services and maintenance provided based on the price charged when the services are sold separately and the stated renewal rate.

A significant amount of our 2013 software revenue is associated with the recognition of PI2 license revenue. In June 2012, Microsoft purchased the Company’s internally developed PI2 software and intellectual property (the “PI2 Solution”) for an aggregate purchase price of $3.25 million. The sale of the PI2 Solution was a significant multiple element contract. This contract included $3.25 million of license consideration and subsequent development and training services. At the time of the sale, we determined that the license did not have stand-alone value without the services, and accordingly we accounted for the license and related services as one unit. The Company recognized $460 thousand of PI2-related software revenue in the three-month period ended March 31, 2013. No PI2-related revenue was recognized in the three-months ended March 31, 2014.