XML 27 R7.htm IDEA: XBRL DOCUMENT  v2.3.0.11
Financial Statement Preparation
6 Months Ended
Jun. 30, 2011
Financial Statement Preparation

NOTE 1 - FINANCIAL STATEMENT PREPARATION

 

Data I/O prepared the financial statements as of June 30, 2011 and June 30, 2010 according to the rules and regulations of the Securities and Exchange Commission ("SEC"). These statements are unaudited but, in the opinion of management, include all adjustments (consisting of normal recurring adjustments and accruals) necessary to present fairly the results for the periods presented. The balance sheet at December 31, 2010 has been derived from the audited financial statements at that date. We have condensed or omitted certain information and footnote disclosures normally included in financial statements prepared in accordance with accounting principles generally accepted in the United States of America according to such SEC rules and regulations. Operating results for the three and six months ended June 30, 2011 are not necessarily indicative of the results that may be expected for the year ending December 31, 2011. These financial statements should be read in conjunction with the annual audited financial statements and the accompanying notes included in the Company's Form 10-K for the year ended December 31, 2010.

 

Revenue Recognition

 

Data I/O recognizes revenue at the time of shipment. When arrangements include multiple elements, we use objective evidence of selling price to allocate revenue to the elements and recognize revenue when the criteria for revenue recognition have been met for each element. The amount of revenue recognized is affected by our judgments as to the collectability of the transaction or whether an arrangement includes multiple elements and if so, whether specific objective evidence of selling price exists for those elements.

 

The revenue related to products requiring installation that is perfunctory is recognized at the time of shipment provided that persuasive evidence of an arrangement exists, shipment has occurred, the price is fixed or determinable, and collectability is reasonably assured. 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 measure the standalone selling price of the product versus the service installation value component by the amount paid to independent representative service groups or the amount of additional discount given to independent distributors to provide the service installation.

 

We record revenue from the sale of service and update contracts as deferred revenue and we recognize it on a straight-line basis over the contractual period, which is typically one year. Service revenue from time and materials contracts and training services are recognized as services are performed. We establish a reserve for sales returns based on historical trends in product returns and estimates for new items. We have a stated return policy that customers can return standard products for any reason within 30 days after delivery, provided that the returned product is received in its original condition, including all packaging materials, for a refund of the price paid less a restocking charge of 30% of the total amount invoiced for the product returned, unless such restocking charge is waived by Data I/O.

 

On those occasions when we sell software separately, we recognize software revenue upon shipment provided that no significant obligations remain on our part, substantive acceptance conditions, if any, have been met and when the fee is fixed and determinable and when collection is deemed probable.

 

Certain fixed-price engineering services contracts that require significant production, modification, or customization of software, are accounted for using the percentage-of-completion method. We use the percentage-of-completion method of accounting because it is the most accurate method to recognize revenue based on the nature and scope of certain of our fixed-price engineering services contracts; it is a better measure of periodic income results than other methods and it better matches revenue recognized with the cost incurred. Percentage-of-completion is measured based primarily on input measures such as hours incurred to date compared to total estimated hours at completion, with consideration given to output measures, such as contract milestones, when applicable. Significant judgment is required when estimating total hours and progress to completion on these arrangements, which determines the amount of revenue we recognize as well as whether a loss is recognized, if expected to be incurred upon project completion. Revisions to hour and cost estimates are incorporated in the period in which the facts that give rise to the revision become known.

 

 Stock-Based Compensation Expense

 

Data I/O measures and recognizes compensation expense as required for all share-based payment awards, including employee stock options and restricted stock awards, based on estimated fair values on the grant dates. Total share-based compensation for the three and six months ended June 30, 2011 was $122,788 and $209,900, respectively. Total share-based compensation for the three and six months ended June 30, 2010 was $82,000 and $157,000, respectively.

 

Income Tax

 

Historically when accounting for uncertainty in income taxes, Data I/O has 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, 2011. However, the Company has adopted a policy whereby amounts related to interest and penalties associated with tax matters are classified as general and administrative expense when incurred.

 

Data I/O has 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, as sufficient uncertainty exists regarding our ability to realize such tax assets in the future. There was $102,000 of unrecognized tax benefits related to uncertain tax positions and related valuation allowance as of June 30, 2011.

 

Tax years that remain open for examination include 2007, 2008, 2009 and 2010 in the United States of America. In addition, tax years from 1999 to 2006 may be subject to examination in the event that the Company utilizes the NOL’s or other carry forwards from those years in its current or future year tax return.

 

Recent Accounting Pronouncements

 

In June 2011, the FASB issued ASU No. 2011-05, Comprehensive Income (Topic 220): Presentation of Comprehensive Income (“ASU 2011-05”). This ASU amends requirements for the presentation of other comprehensive income (OCI), requiring presentation of comprehensive income in either a single, continuous statement of comprehensive income or on separate but consecutive statements, the statement of operations and the statement of OCI. The amendment is effective for the Company at the beginning of fiscal year 2013 with early adoption permitted. The adoption of this guidance will not impact the Company's financial position, results of operations or cash flows and will only impact the presentation of OCI on the financial statements.

 

In May 2011, the FASB issued ASU No. 2011-04, Fair Value Measurement (Topic 820): Amendments to Achieve Common Fair Value Measurement and Disclosure Requirements in US GAAP and International Reporting Standards (“ASU No. 2011-04”) which amended the guidance regarding fair value measurement and disclosure. The amended guidance clarifies the application of existing fair value measurement and disclosure requirements. The amendment is effective for the Company at the beginning of January 2012, with early adoption prohibited. The adoption of this amendment is not expected to materially affect the Company's financial statements.

 

In October 2009, the FASB issued ASU No. 2009-13, Revenue Recognition (Topic 605): Multiple-Deliverable Revenue Arrangements (“ASU 2009-13”). It amends the criteria for separating consideration in multiple-deliverable arrangements. This standard establishes a selling price hierarchy for determining the selling price of a deliverable. The selling price used for each deliverable will be based on vendor-specific objective evidence if available, third-party evidence if vendor-specific objective evidence is not available, or estimated selling price if neither vendor-specific objective evidence nor third-party evidence is available. This standard also replaces the term fair value in the revenue allocation guidance with selling price to clarify that the allocation of revenue is based on entity-specific assumptions rather than assumptions of a market participant. It also eliminates the residual method of allocation and requires that arrangement consideration be allocated at the inception of the arrangements to all deliverables using the relative selling price method. This standard is effective prospectively for revenue arrangements entered into or materially modified in fiscal years beginning on or after June 15, 2010. The impact of adoption of this standard had no material effect on the accompanying condensed consolidated financial statements.

 

In October 2009, the FASB issued ASU No. 2009-14, Software (Topic 985): Certain Revenue Arrangements That Include Software Elements (“ASU 2009-14”). According to this update, tangible products containing software components and non-software components that function together to deliver the tangible product’s essential functionality are no longer within the scope of the software revenue guidance. It provides additional guidance on how to determine which software, if any, relating to the tangible product also would be excluded from the scope of the software revenue guidance. This standard shall be adopted in the same period using the same transition method as indicated in the update to revenue arrangements with multiple deliverables. The impact of adoption of this standard had no material effect on the accompanying condensed consolidated financial statements.