XML 26 R11.htm IDEA: XBRL DOCUMENT v2.4.0.6
Nature of Business and Summary of Significant Accounting Policies (Policies)
3 Months Ended
Mar. 31, 2013
Accounting Policies [Abstract]  
Use of Estimates, Policy [Policy Text Block]

Use of Estimates

 

The preparation of financial statements in conformity with U.S. generally accepted accounting principles requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the date of the financial statements and the reported amounts of revenues and expenses during the reporting period. Actual results could differ from those estimates.

Revenue Recognition, Policy [Policy Text Block]

Revenue Recognition

 

The Company derives revenues from the sales of systems, licenses and maintenance fees, and services.

 

System Sales

 

Revenue from systems that have been demonstrated to meet customer specifications during installation is recognized when evidence of an arrangement exists, the product has been installed, title and risk of loss have transferred to the customer and collection of the resulting receivable is reasonably assured. System sales, which are accounted for as multiple-element arrangements, include multiple products and/or services. For multiple-element arrangements, the Company allocates the revenue to each element based on their relative fair estimated value based on vendor specific objective evidence (VSOE) and recognizes the associated revenue when all revenue recognition criteria have been met for each element. If there are contracts the Company does not have VSOE of fair value of all elements, revenue is deferred until the earlier of VSOE being determined or when all elements have been delivered.

 

The Company does offer its customers contracts with extended payment terms.  The Company must evaluate if any extended payment terms in the contract is an indicator of the revenue not being fixed or determinable.  Provided all other revenue recognition criteria have been satisfied, the Company recognizes the revenue if payment of a significant portion of the systems sales is due within 12 months of the delivery of the product.  The Company also analyzes its standard business practice of using long-term contracts and the history of collecting on extended payment term contracts without making concessions for determining if revenue should be recognized.  Revenue and associated set-up costs are deferred if contract terms exceed historical collection results or if a substantial portion of the contract is not due within 12 months after delivery of the product.  The Company analyzes each contract for proper revenue recognition based on that contracts facts and circumstances.  Interest is recorded upon receipt to “other income” on the statements of operations. 

 

Maintenance revenue

 

Maintenance revenue is recognized ratably over the contract period. The VSOE for maintenance is based upon the renewal rate for contracted services.

 

Service revenue

 

Service revenue is recognized after the services are performed and collection of the resulting receivable is reasonably assured. The VSOE for service revenue is established based upon prices for the services.

 

Rental revenue

 

The Company offers certain new customers a rental contract.  Revenues are billed monthly based on a per-game per-day basis.  There is an option to purchase the system after the rental agreement at a pre-determined residual value.

Trade and Other Accounts Receivable, Policy [Policy Text Block]

Accounts Receivable / Allowance for Doubtful Accounts

 

Accounts receivable are recorded at the invoiced amount. Accounts receivable include regular customer receivables and amounts from financed contracts coming due within 12 months. Amounts from financed contracts due beyond 12 months are recorded as "Long-term accounts receivable – financed contracts."  Interest is recorded upon receipt to other income on the statements of operations. An allowance for doubtful accounts is recorded when the Company believes the amounts may not be collected. Management believes that receivables, net of the allowance for doubtful accounts, are fully collectible. While the ultimate result may differ, management believes that any write-off not allowed for will not have a material impact on the Company's financial position.

 

Major Customers

 

The following tables summarize significant customer information for the three months ended March 31, 2013 and 2012:

 

    For the Three Months Ended March 31  
    2013     2012  
      % Sales       % AR       % Sales       % AR  
A     41.1 %     21.0 %     7.8 %     1.3 %
B     4.7 %     19.6 %     1.4 %     0.6 %
C     8.3 %     10.2 %     7.8 %     19.2 %
D     0.0 %     5.6 %     21.6 %     35.1 %
E     0.6 %     1.4 %     22.8 %     4.7 %
F     14.4 %     21.7 %     0.0 %     0.0 %
All Others     30.9 %     20.5 %     38.6 %     39.1 %
Total     100.0 %     100.0 %     100.0 %     100.0 %
Inventory, Policy [Policy Text Block]

Inventory

 

Inventory, consisting of finished goods, is stated at the lower of cost or market. The average cost method is used to value inventory. Inventory is reviewed annually for the lower of cost or market and obsolescence. Any material cost found to be above market value or considered obsolete is written down accordingly. The Company had no obsolescence reserve at March 31, 2013 and December 31, 2012.

Research and Development Expense, Policy [Policy Text Block]

Research and Development

 

The Company expenses all costs related to research and development as incurred. Research and development expense was $2,303 and $152,906 for the three months ended March 31, 2013 and 2012, respectively. Research and development expenses are included in selling, general and administrative expenses on the statements of operations.

Deferred System Sales Costs [Policy Text Block]

Deferred System Sales Costs

 

Deferred system sales costs consist of installed system costs incurred on participation-based contracts. These costs are recognized on a straight-line basis over the term of the contract which is generally 18-48 months beginning when revenues are generated. At the end of the contract period, the customer will typically receive title to the system.