XML 23 R16.htm IDEA: XBRL DOCUMENT v3.7.0.1
NOTE 1 - FINANCIAL STATEMENT PREPARATION (Policies)
6 Months Ended
Jun. 30, 2017
Note 1 - Financial Statement Preparation Policies  
Revenue Recognition

We recognize revenue at the time the product is shipped. We have determined that our programming equipment has reached a point of maturity and stability such that product acceptance can be assured by testing at the factory prior to shipment and that the installation meets the criteria to be considered a separate element. These systems are standard products with published product specifications and are configurable with standard options. The evidence that these systems could be deemed as accepted was based upon having standardized factory production of the units, results from batteries of tests of product performance to our published specifications, quality inspections and installation standardization, as well as past product operation validation with the customer and the history provided by our installed base of products upon which the current versions were based.

 

The revenue related to products requiring installation that is perfunctory is recognized at the time of shipment. Installation that is considered perfunctory includes any installation that can be performed by other parties, such as distributors, other vendors, or in most cases the customers themselves. This takes into account the complexity, skill and training needed as well as customer expectations regarding installation.

 

We enter into multiple deliverable arrangements that arise during the sale of a system that includes an installation component, a service and support component and a software maintenance component. We allocate the value of each element based on relative selling prices. Relative selling price is based on the selling price of the standalone system. For the installation and service and support components, we use the value of the discount given to distributors who perform these components. For software maintenance components, we use what we charge for annual software maintenance renewals after the initial year the system is sold. Revenue is recognized on the system sale based on shipping terms, installation revenue is recognized after the installation is performed, and hardware service and support and software maintenance revenue is recognized ratably over the term of the agreement, typically one year.

 

When we sell software separately, we recognize software revenue upon shipment, provided that only inconsequential obligations remain on our part and substantive acceptance conditions, if any, have been met.

 

We recognize revenue when persuasive evidence of an arrangement exists, shipment has occurred, the price is fixed or determinable, the buyer has paid or is obligated to pay, collectability is reasonably assured, substantive acceptance conditions, if any, have been met, the obligation is not contingent on resale of the product, the buyer’s obligation would not be changed in the event of theft, physical destruction or damage to the product, the buyer acquiring the product for resale has economic substance apart from us and we do not have significant obligations for future performance to directly bring about the resale of the product by the buyer. We establish a reserve for sales returns based on historical trends in product returns and estimates for new items.

 

We transfer certain products out of service from their internal use and make them available for sale. The products transferred are our standard products in one of the following areas: service loaners, rental or test units; engineering test units; or sales demonstration equipment. Once transferred, the equipment is sold by our regular sales channels as used equipment inventory. These product units often involve refurbishing and an equipment warranty, and are conducted as sales in our normal and ordinary course of business. The transfer amount is the product unit’s net book value and the sale transaction is accounted for as revenue and cost of goods sold.

Stock-Based Compensation Expense

We measure and recognize compensation expense as required for all share-based payment awards, including employee stock options and restricted stock unit awards, based on estimated fair values and estimated forfeiture rate on the grant dates.

 

Income Tax

Historically, when accounting for uncertainty in income taxes, we have not incurred any interest or penalties associated with tax matters and no interest or penalties were recognized during the three and six months ended June 30, 2017. However, we have adopted a policy whereby amounts related to penalties associated with tax matters are classified as general and administrative expense when incurred and amounts related to interest associated with tax matters are classified as interest income or interest expense.

 

We have incurred net operating losses in certain past years.  We continue to maintain a valuation allowance for the full amount of the net deferred tax asset balance associated with our net operating losses and credit carryforwards, as sufficient uncertainty exists regarding our ability to realize such tax assets in the future. There were $234,000 and $226,000 of unrecognized tax benefits related to uncertain tax positions and related valuation allowance as of June 30, 2017 and December 31, 2016, respectively.

 

Tax years that remain open for examination include 2013, 2014, 2015 and 2016 in the United States of America. In addition, tax years from 2000 to 2012 may be subject to examination in the event that we utilize the net operating losses and credit carryforwards from those years in our current or future year tax returns.

Recent Accounting Pronouncements

In March 2016, the FASB issued ASU 2016-09, Compensation-Stock Compensation (ASU 2016-09), “Improvements to Employee Share-Based Payment Accounting”. ASU 2016-09 requires excess tax benefits to be recognized in the statement of operations as an income tax expense and is applied prospectively by means of a cumulative-effect adjustment of excess tax benefits from equity in the period of adoption. The standard establishes an alternative practical expedient for estimating the expected term of an award by recognizing the effects of forfeitures in compensation cost when the forfeitures occur. Adoption of the alternative practical expedient is applied prospectively on an entity-wide basis. The standard requires that amounts paid to a taxing authority on the employee’s behalf as a result of directly withholding shares for tax-withholding purposes are to be presented on a retrospective basis as a financing activity on the statement of cash flows. The standard became effective beginning January 1, 2017. The adoption of ASU 2016-09 was not material to our consolidated financial statements.

 

In February 2016, the FASB issued ASU 2016-02, “Leases” (ASU 2016-02).  ASU 2016-02 requires lessees to recognize almost all leases on the balance sheet as a right-of-use asset and a lease liability and requires leases to be classified as either an operating or a finance type lease. The standard excludes leases of intangible assets or inventory. Early adoption of the standard is allowed. The standard becomes effective beginning January 1, 2019. We are in the process of evaluating the impact of adoption on our consolidated financial statements.

 

In May 2014, the FASB issued ASU 2014-09, “Revenue from Contracts with Customers” (ASU 2014-09).  ASU 2014-09 provides companies with a single model for accounting for revenue arising from contracts with customers and supersedes current revenue recognition guidance, including industry-specific revenue guidance. The core principle of the model is to recognize revenue when control of the goods or services transfers to the customer, as opposed to recognizing revenue when the risks and rewards transfer to the customer under the existing revenue guidance. 

 

In August 2015, the FASB issued ASU 2015-14, “Revenue from Contracts with Customers” (ASU 2015-14), deferring the effective date of the new revenue recognition standard by one year and it now takes effect for public entities in fiscal years beginning after December 15, 2017. We plan to adopt the revenue standards as of January 1, 2018, utilizing the modified retrospective transition method. The Company is currently evaluating the potential impact of the adoption on our consolidated financial statements. As part of this process, the Company has identified its revenue streams and a preliminary analysis of how we currently account for revenue transactions compared to the revenue accounting required under the new standard. We intend to complete our adoption plan in fiscal year 2017.  Because of the nature of the work that remains, at this time, we are unable to reasonably estimate the impact of adoption on our consolidated financial statements. We will continue our evaluation of revenue from our contracts with customers, and we will update our expectations of the impact of adoption of the new revenue standards on our consolidated financial statements in future filings.