| Significant Accounting Policies [Text Block] | 5. Summary of Significant Accounting Policies The preparation of financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions. Such estimates and assumptions 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. Actual results could differ from estimated amounts. Significant estimates and assumptions include valuation allowances related to receivables, the recoverability of long-term assets, depreciable lives of property and equipment, deferred taxes and related valuation allowances. The Company’s management monitors these risks and assesses its business and financial risks on a quarterly basis. The Company maintains its cash with high credit quality financial institutions. At times, the Company’s cash and cash equivalents may be uninsured or in deposit accounts that exceed the Federal Deposit Insurance Corporation insurance limit. The number of customers that comprise the Company’s customer base, along with the different industries, governmental entities and geographic regions, in which the Company’s customers operate, limits concentrations of credit risk with respect to accounts receivable. The Company does not generally require collateral or other security to support customer receivables; however, the Company may require its customers to provide retainers, up-front deposits or irrevocable letters-of-credit when considered necessary to mitigate credit risks. The Company has established an allowance for doubtful accounts based upon facts surrounding the credit risk of specific customers and past collections history. Credit losses have been within management’s expectations. At September 30, 2016 and December 31, 2015, the Company allowance for doubtful accounts was $ 17,919 23,786 Property, equipment and leasehold improvements are stated at cost less accumulated depreciation and amortization. Depreciation and amortization is computed over the estimated useful lives of the related assets on a straight-line basis. Furniture and fixtures, computer hardware and purchased software are depreciated over three to seven years. Leasehold improvements are amortized over the life of the lease or the asset, whichever is shorter, generally seven to ten years. Upon retirement or other disposition of these assets, the cost and related accumulated depreciation and amortization of these assets are removed from the accounts and the resulting gains and losses are reflected in the results of operations. The Company accounts for the impairment and disposition of long-lived assets in accordance with Accounting Standards Codification (“ASC”) Topic 360, “Property, Plant, and Equipment.” The Company tests long-lived assets or asset groups, such as property and equipment, for recoverability when events or changes in circumstances indicate that their carrying amount may not be recoverable. Circumstances which could trigger a review include, but are not limited to: significant adverse changes in the business climate or legal factors; current period cash flow or operating losses combined with a history of losses or a forecast of continuing losses associated with the use of the asset; and a current expectation that the asset will more likely than not be sold or disposed of before the end of its estimated useful life. Recoverability is assessed based on comparing the carrying amount of the asset to the aggregate pre-tax undiscounted cash flows expected to result from the use and eventual disposal of the asset or asset group. Impairment is recognized when the carrying amount is not recoverable and exceeds the fair value of the asset or asset group. The impairment loss, if any, is measured as the amount by which the carrying amount exceeds fair value, which for this purpose is based upon the discounted projected future cash flows of the asset or asset group. The Company accounts for stock-based payments to employees in accordance with ASC 718, “Stock Compensation.” Stock-based payments to employees include grants of stock that are recognized in the consolidated statement of operations based on their fair values at the date of grant. The Company accounts for stock-based payments to non-employees in accordance with ASC 718 and ASC 505-50, “Equity-Based Payments to Non-Employees,” which requires that such equity instruments are recorded at their fair value on the measurement date, with the measurement of such compensation being subject to periodic adjustment as the underlying equity instruments vest. The grant date fair value of stock option awards is recognized in earnings as share-based compensation cost over the requisite service period of the award using the straight-line attribution method. The Company estimates the fair value of the stock option awards using the Black-Scholes-Merton option pricing model. The exercise price of options is specified in the stock option agreements. The expected volatility is based on the historical volatility of the Company’s stock for the previous period equal to the expected term of the options. The expected term of options granted is based on the midpoint between the vesting date and the end of the contractual term. The risk-free interest rate is based upon a U.S. Treasury instrument with a life that is similar to the expected term of the options. The expected dividend yield is based upon the yield expected on date of grant to occur over the term of the option. On January 1, 2016, the Company granted employees stock options to purchase 250,000 0.90 196,250 12,226 85,820 On February 10, 2016, the Company granted employees stock options to purchase 210,000 0.96 174,748 11,012 27,769 On January 2, 2016, the Company issued 69,433 62,500 Software development costs for software to be sold or otherwise marketed incurred prior to the establishment of technological feasibility are expensed as incurred. The Company defines establishment of technological feasibility as the completion of a working model. Software development costs incurred subsequent to the establishment of technological feasibility through the period of general market availability of the product are capitalized, if material. To date, all software development costs for software to be sold or otherwise marketed have been expensed as incurred. In accordance with ASC 350-40, “Internal-Use Software,” the Company capitalizes purchase and implementation costs of internal use software. No such costs were capitalized during the periods presented. Stock Compensation In March 2016, the FASB issued ASU No. 2016-09, Compensation Stock Compensation (Topic 718): Improvements to Employee Share-Based Payment Accounting (“ASU 2016-09”), which simplified certain aspects of the accounting for share-based payment transactions, including income taxes, classification of awards and classification on the statement of cash flows. ASU 2016-09 will be effective for the Company beginning in its first quarter of 2018. The Company is currently evaluating the impact of adopting ASU 2016-09 on its consolidated financial statements. Leases In February 2016, the FASB issued ASU No. 2016-02, Leases (Topic 842) (“ASU 2016-02”), which modified lease accounting for both lessees and lessors to increase transparency and comparability by recognizing lease assets and lease liabilities by lessees for those leases classified as operating leases under previous accounting standards and disclosing key information about leasing arrangements. ASU 2016-02 will be effective for the Company beginning in its first quarter of 2020, and early adoption is permitted. The Company is currently evaluating the timing of its adoption and the impact of adopting ASU 2016-02 on its consolidated financial statements. Debt Issuance Costs In April 2015, the FASB issued ASU No. 2015-03, “Simplifying the Presentation of Debt Issuance Costs,” which requires that debt issuance costs related to a recognized debt liability be presented in the balance sheet as a direct deduction from the carrying amount of that debt liability rather than as an asset. The recognition and measurement guidance for debt issuance costs are not affected by ASU 2015-03. The guidance is effective for public business entities for fiscal years beginning after December 15, 2015, and interim periods within those fiscal years. The guidance is required to be applied retrospectively and early adoption is permitted. The Company adopted the new guidance effective January 1, 2016. Debt issuance costs that are now presented as a direct reduction from the carrying amount of the associated debt liability amounted to $ 2,131 4,255 Revenue Recognition In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) No. 2014-09, Revenue from Contracts with Customers. The core principle of ASU 2014-09 is built on the contract between a vendor and a customer for the provision of goods and services. It attempts to depict the exchange of rights and obligations between the parties in the pattern of revenue recognition based on the consideration to which the vendor is entitled. To accomplish this objective, ASU 2014-09 requires five basic steps: (i) identify the contract with the customer, (ii) identify the performance obligations in the contract, (iii) determine the transaction price, (iv) allocate the transaction price to the performance obligations in the contract, and (v) recognize revenue when (or as) the entity satisfies a performance obligation. Entities will generally be required to make more estimates and use more judgment than under current guidance, which will be highlighted for users through increased disclosure requirements. Subsequently, the FASB has issued the following standards related to ASU 2014-09: ASU No. 2016-08, Revenue from Contracts with Customers (Topic 606): Principal versus Agent Considerations (“ASU 2016-08”); ASU No. 2016-10, Revenue from Contracts with Customers (Topic 606): Identifying Performance Obligations and Licensing (“ASU 2016-10”); and ASU No. 2016-12, Revenue from Contracts with Customers (Topic 606): Narrow-Scope Improvements and Practical Expedients (“ASU 2016-12”). The Company must adopt ASU 2016-08, ASU 2016-10 and ASU 2016-12 with ASU 2014-09 (collectively, the “new revenue standards”). In July 2015, the FASB deferred the effective date of the new revenue standards for one year beyond the originally specified effective date. The update is now effective for public entities for annual periods beginning after December 15, 2017, including interim periods therein. Earlier application is permitted only as of annual reporting periods beginning after December 15, 2016, including interim reporting periods within that reporting period. Three basic transition methods are available full retrospective, retrospective with certain practical expedients, and a cumulative effect approach. Management is in the process of evaluating the impact that adoption of the new revenue standards will have on the consolidated financial statements and has not yet determined the method by which the Company will adopt the standard. a) Sale of Software The Company recognizes revenues in accordance with ASC Topic 985-605, “Software Revenue Recognition.” The Company records revenues from the sale of software licenses when persuasive evidence of an arrangement exists, the software product has been installed, there are no significant uncertainties surrounding product acceptance by the customer, the fees are fixed and determinable, and collection is considered probable. Revenues included in this classification typically include sales of additional software licenses to existing customers and sales of software to the Company’s Resellers (See section h) Reseller Agreements, below). The Company assesses whether payment terms are customary or extended in accordance with normal practice relative to the market in which the sale is occurring. The Company’s sales arrangements generally include standard payment terms. These terms effectively relate to all customers, products, and arrangements regardless of customer type, product mix or arrangement size. If an undelivered element for the arrangement exists under the license arrangement, revenues related to the undelivered element are deferred based on Vendor Specific Objective Evidence (“VSOE”) of the fair value of the undelivered element. Often, multiple-element sales arrangements include arrangements where software licenses and the associated post-contract customer support (“PCS”) are sold together. The Company has established VSOE of the fair value of the undelivered PCS element based on the contracted price for renewal PCS included in the original multiple element sales arrangement, as substantiated by contractual terms and the Company’s significant PCS renewal experience, from the Company’s existing customer base. The Company records the revenues for the sales of software with professional services as prescribed by ASC 985-605, in accordance with the contract accounting guidelines in ASC 605-35, “Revenue Recognition: Construction-Type and Production-Type Contracts,” after evaluating for separation of any non-ASC 605-35 elements in accordance with the provisions of ASC 605-25, “Revenue Recognition: Multiple-Element Arrangements,” as updated. The Company accounts for these contracts on a percentage of completion basis, measured by the percentage of labor hours incurred to date to estimated total labor hours for each contract, or on a completed contract basis when dependable estimates are not available. The fair value of any undelivered elements in multiple-element arrangements in connection with the sales of software licenses with professional services are deferred based upon VSOE. b) Sale of Software as a Service Sale of software as a service (“SaaS”) consists of revenues from arrangements that provide customers the use of the Company’s software applications, as a service, typically billed on a monthly or annual basis. Advance billings of these services are not recorded to the extent that the term of the arrangement has not commenced and payment has not been received. Revenue on these services is recognized ratably over the term of the underlying arrangement. c) Sale of Software Maintenance Services Software maintenance services revenues consist of revenues derived from arrangements that provide PCS to the Company’s software license holders. These revenues are recognized ratably over the term of the contract. Advance billings of PCS are not recorded to the extent that the term of the PCS has not commenced and payment has not been received. d) Sales of Professional Services Professional services consist principally of revenues from consulting, advisory services, training and customer assistance with management and uploading of data into the Company’s applications. When these services are provided on a time and material basis, the Company records the revenue as the services are rendered, since the revenues from services rendered through any point in time during the performance period are not contingent upon the completion of any further services. Where the services are provided under a fixed priced arrangement, the Company records the revenue on a proportional performance method, since the revenues from services rendered through any point in time during the performance period are not contingent upon the completion of any further services. e) Sale of Third Party Services Sale of third party services consist principally of third party software and/or equipment as a pass through of software and equipment purchased from third parties at the request of customers. f) Deferred revenues The Company records deferred revenue primarily related to software maintenance support agreements, when the customer pays for the contract prior to the time the services are performed. Substantially all maintenance agreements have a one-year term that commences immediately following the delivery of the maintained products or on the date of the applicable renewal period. g) Rights of return and other incentives The Company does not generally offer rights of return or any other incentives such as concessions, product rotation, or price protection and, therefore, does not provide for or make estimates of rights of return and similar incentives. The Company, from time to time, may discount bundled software sales with PCS services. Such discounts are recorded as a component of the software sale and any revenue related to PCS is deferred over the PCS period based upon appropriate VSOE of fair value. h) Reseller agreements The Company executes certain sales contracts through resellers and distributors (collectively, “Resellers”). The Company recognizes revenues relating to sales through Resellers when all the recognition criteria have been metin other words, persuasive evidence of an arrangement exists, delivery has occurred in the reporting period, the fee is fixed and determinable, and collectability is probable. In addition, the Company assesses the credit-worthiness of each Reseller, and if the Reseller is undercapitalized or in financial difficulty, any revenues expected to emanate from such Resellers are deferred and recognized only when cash is received and all other revenue recognition criteria are met. The Company expenses the cost of advertising as incurred. Advertising expense for the three and nine months ended September 30, 2016 and 2015 amounted to approximately $ 641 1,587 12 1,879 Basic earnings per share is computed by dividing net income by the weighted average number of shares of common stock outstanding during the period. The Company has outstanding stock options which have not been included in the calculation of diluted net loss per share because to do so would be anti-dilutive. As such, the numerator and the denominator used in computing both basic and diluted net loss per share for each period are the same. The Company and its subsidiary file a consolidated federal income tax return. The provision for income taxes is computed by applying statutory rates to income before taxes. Deferred income taxes are recognized for the tax consequences in future years of temporary differences between the financial reporting and tax bases of assets and liabilities as of each period-end based on enacted tax laws and statutory rates. Valuation allowances are established when necessary to reduce deferred tax assets to the amount expected to be realized. A 100 The Company accounts for uncertainty in income taxes in its financial statements as required under ASC 740, “Accounting for Uncertainty in Income Taxes . For purposes of reporting cash flows, cash includes cash on hand and demand deposits held by banks. |
