Summary of Significant Accounting Policies
|9 Months Ended|
Sep. 30, 2016
|Basis of Presentation/Summary of Significant Accounting Policies [Abstract]|
|Summary of Significant Accounting Policies||
Note 3 - Summary of Significant Accounting Policies
Significant Accounting Policies
The Company's complete accounting policies are described in Note 2 to the Company's audited financial statements and footnotes for the years ended December 31, 2015 and 2014.
Use of Estimates
The preparation of financial statements in conformity with GAAP 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 each of the reporting periods. Actual results could differ from those estimates. The Company’s significant estimates consist of:
The Company provides IT solutions and services to customers and derives revenues primarily from the sale of third-party hardware and software products, software, assurance, licenses and other consulting services, including maintenance services and recognizes revenue once the following four criteria are met: (1) persuasive evidence of an arrangement exists, (2) the price is fixed and determinable, (3) shipment (software and hardware) or fulfillment (maintenance) has occurred, and (4) there is reasonable assurance of collection of the sales proceeds (the “Revenue Recognition Criteria”). In addition, the Company also records revenues in accordance with Accounting Standards Codification (“ASC”) Topic 605-45 “Principal Agent Consideration” (“ASC 605-45”). The Company evaluates the sales of products and services on a case by case basis to determine whether the transaction should be recorded gross or net, including, but not limited to, assessing whether or not the Company: 1) is the primary obligor in the transaction; 2) has inventory risk with respect to the products and/or services sold; 3) has latitude in pricing; and 4) changes the product or performs part of the services sold. The Company evaluates whether revenues received from the sale of hardware and software products, licenses, and services, including maintenance and professional consulting services, should be recognized on a gross or net basis on a transaction by transaction basis. As of September 30, 2016, the Company has determined that all revenues received should be recognized on a gross basis in accordance with applicable standards.
Cooperative reimbursements from vendors, which are earned and available, are recorded during the period the related transaction has occurred. Cooperative reimbursements are recorded as a reduction of cost of sales in accordance with ASC Topic 605-50 “Accounting by a Customer (including reseller) for Certain Consideration Received from a Vendor.” Provisions for returns are estimated based on historical collections and credit memo analysis for the period. The Company receives Marketing Development Funds (MDF) from vendors based on quarterly or annual sales performance to promote the marketing of vendor products and services. The Company must file claims with vendors for these cooperative reimbursements by providing invoices and receipts for marketing expenses. Reimbursements are recorded as a reduction of marketing expenses and other applicable selling general and administrative expenses ratably over the period in which the expenses are expected to occur. The Company receives vendor rebates which are recorded to cost of sales.
The Company also enters into sales transactions whereby customer orders contain multiple deliverables, and reports its multiple deliverable arrangements under ASC 605-25 “Revenue Arrangements with Multiple Deliverables” (“ASC-605-25”). These multiple deliverable arrangements primarily consist of the following deliverables: the Company’s design, configuration, installation, integration, warranty/maintenance and consulting services; and third-party computer hardware, software and warranty maintenance services. In situations where the Company bundles all or a portion of the separate elements, Vendor Specific Objective Evidence (“VSOE”) is determined based on prices when sold separately. For the three months ended September 30, 2016 and 2015 revenues recognized as a result of customer contracts requiring the delivery of multiple elements was $3.7 million and $7.4 million, respectively. For the nine months ended September 30, 2016 and 2015 revenues recognized as a result of customer contracts requiring the delivery of multiple elements was $15.4 million and $24.3 million, respectively.
Hardware, Software and Licensing Revenue Recognition
Generally, the Revenue Recognition Criteria are met with respect to the sales of hardware and software products when they are shipped to the customer. The delivery of products to our customers occurs in a variety of ways, including (i) as a physical product shipped from the Company’s warehouse, (ii) via drop-shipment by a third-party vendor, or (iii) via electronic delivery with respect to software licenses. The Company leverages drop-ship arrangements with many of its vendors and suppliers to deliver products to customers without having to physically hold the inventory at its warehouse. In such arrangements, the Company negotiates the sale price with the customer, pays the supplier directly for the product shipped, bears credit risk of collecting payment from its customers and is ultimately responsible for the acceptability of the product and ensuring that such product meets the standards and requirements of the customer. As a result, the Company recognizes the sale of the product and the cost of such upon receiving notification from the supplier that the product has shipped. Vendor rebates and price protection are recorded when earned as a reduction to cost of sales or merchandise inventory, as applicable. Vendor product price discounts are recorded when earned as a reduction to cost of sales.
Maintenance and Professional Services Revenue Recognition
With respect to sales of our maintenance, consulting and other service agreements including our digital advertising and electronic services, the Revenue Recognition Criteria is met once the service has been provided. Revenue on time and material contracts is recognized based on a fixed hourly rate as direct labor hours are expended. The fixed rate includes direct labor, indirect expenses, and profits. Materials, or other specified direct costs, are reimbursed as actual costs and may include markup. Anticipated losses are recognized as soon as they become known. For the three and nine months ended September 30, 2016 and 2015, the Company did not incur any such losses. These amounts are based on known and estimated factors. Revenues from time and material or firm fixed price long-term and short-term contracts are derived principally with various United States Government agencies and commercial customers.
The Company recognizes revenue for sales of all services billed as a fixed fee ratably over the term of the arrangement as such services are provided. Billings for such services that are made in advance of the related revenue recognized are recorded as deferred revenue and recognized as revenue ratably over the billing coverage period. Amounts received as prepayments for services to be rendered are recognized as deferred revenue. Revenue from such prepayments is recognized when the services are provided.
The Company’s storage and computing segment maintenance services agreements permit customers to obtain technical support from the Company and/or the manufacturer and to update, at no additional cost, to the latest technology when new software updates are introduced and available during the period that the maintenance agreement is in effect. Since the Company assumes certain responsibility for product staging, configuration, installation, modification, and integration with other client systems, or retains general inventory risk upon customer return or rejection and is most familiar with the customer and its required specifications, it generally serves as the initial contact with the customer with respect to any storage and computing maintenance services required and therefore will perform all or part of the required service.
Typically, the Company sells maintenance contracts for a separate fee with initial contractual periods ranging from one to three years with renewal for additional periods thereafter. The Company generally bills maintenance fees in advance and records the amounts received as deferred revenue with respect to any portion of the fee for which services have not yet been provided. The Company recognizes the related revenue ratably over the term of the maintenance agreement as services are provided. In situations where the Company bundles all or a portion of the maintenance fee with products, VSOE for maintenance is determined based on prices when sold separately.
Customers that have purchased maintenance/warranty services have a right to cancel and receive a refund of the amounts paid for unused services at any time during the service period upon advance written notice to the Company. Cancellation and refund privileges with respect to maintenance/warranty services lapse as to any period during the term of the agreement for which such services have already been provided. Customers do not have the right to a refund of paid fees for maintenance/warranty services that the Company has earned and recognized as revenue. Invoices issued for maintenance/warranty services not yet rendered are recorded as deferred revenue and then recognized as revenue ratably over the service period. As a result (1) the warranty and maintenance service fees payable by each customer are separately accounted for in each customer purchase order as a separate line item, and (2) upon the Company’s receipt and acceptance of a request for refund of maintenance/warranty services not yet provided, the Company’s obligation to perform any additional maintenance/warranty services will end. Sales are recorded net of discounts and returns.
The Company accounts for options granted to employees by measuring the cost of services received in exchange for the award of equity instruments based upon the fair value of the award on the date of grant. The fair value of that award is then ratably recognized as expense over the period during which the recipient is required to provide services in exchange for that award.
Options and warrants granted to consultants and other non-employees are recorded at fair value as of the grant date and subsequently adjusted to fair value at the end of each reporting period until such options and warrants vest, and the fair value of such instruments, as adjusted, is expensed over the related vesting period.
The Company incurred stock-based compensation charges, net of estimated forfeitures of $344,000 and $391,000 for the three months ended September 30, 2016 and 2015, and $1,055,000 and $885,000 for the nine month period ended September 30, 2016 and 2015, respectively. The following table summarizes the nature of such charges for the periods then ended (in thousands):
Net Loss Per Share
The Company computes basic and diluted earnings per share by dividing net loss by the weighted average number of common shares outstanding during the period. Basic and diluted net loss per common share were the same since the inclusion of common shares issuable pursuant to the exercise of options and warrants in the calculation of diluted net loss per common shares would have been anti-dilutive.
The following table summarizes the number of common shares and common share equivalents excluded from the calculation of diluted net loss per common share for the nine months ended September 30, 2016 and 2015:
The Company applies the accounting standards for distinguishing liabilities from equity under U.S. GAAP when determining the classification and measurement of its convertible preferred stock. Preferred shares subject to mandatory redemption are classified as liability instruments and are measured at fair value. Conditionally redeemable preferred shares (including preferred shares that feature redemption rights that are either within the control of the holder or subject to redemption upon the occurrence of uncertain events not solely within the Company’s control) are classified as temporary equity. At all other times, preferred shares are classified as permanent equity.
As of the issuance date, the carrying amount of the preferred stock was less than the redemption value. If the Company were to determine that redemption was probable, the carrying value would be increased by periodic accretions so that the carrying value would equal the redemption amount at the earliest redemption date. Such accretion would be recorded as a preferred stock dividend.
During the nine months ended September 30, 2016, the Company issued a convertible debenture that included reset provisions considered to be down-round protection. The Company determined that the conversion feature is a derivative instrument pursuant to FASB ASC 815 “Derivatives and Hedging.” The accounting treatment of derivative financial instruments requires that the Company bifurcate the conversion feature and record it as a liability at the fair value and mark-to-market the instrument at fair value as of each balance sheet date. Any change in fair value is recorded as a change in the fair value of derivative liabilities for each reporting period. The fair value of the conversion feature was determined using the Binomial Lattice model. The Company reassesses the classification at each balance sheet date. If the classification changes as a result of events during the period, the contract is reclassified as of the date of the event that caused the reclassification.
Recent Accounting Pronouncements
In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) No. 2014-09, “Revenue from Contracts with Customers,” (“ASU 2014-09”). ASU 2014-09 supersedes the revenue recognition requirements in ASC 605 - Revenue Recognition and most industry-specific guidance throughout the ASC. The standard requires that an entity recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the company expects to be entitled in exchange for those goods or services. ASU 2014-09 should be applied retrospectively to each prior reporting period presented or retrospectively with the cumulative effect of initially applying ASU 2014-09 recognized at the date of initial application. To allow entities additional time to implement systems, gather data and resolve implementation questions, the FASB issued ASU No. 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date, in August 2015, to defer the effective date of ASU No. 2014-09 for one year, which is fiscal years beginning after December 15, 2017. The Company is currently evaluating the impact of the adoption of ASU 2014-09 on its financial statements or disclosures. In addition, the FASB issued ASU 2016-08 in March 2016, to help provide interpretive clarifications on the new guidance in ASC Topic 606. The Company is currently evaluating the accounting, transition, and disclosure requirements of the standard to determine the impact, if any, on its financial statements or disclosures.
In March 2016, the FASB issued ASU No. 2016-08, “Revenue from Contracts with Customers - Principal versus Agent Considerations.” This update provides clarifying guidance regarding the application of ASU No. 2014-09 - Revenue From Contracts with Customers when another party, along with the reporting entity, is involved in providing a good or a service to a customer. In these circumstances, an entity is required to determine whether the nature of its promise is to provide that good or service to the customer (that is, the entity is a principal) or to arrange for the good or service to be provided to the customer by the other party (that is, the entity is an agent). The amendments in the Update clarify the implementation guidance on principal versus agent considerations. The update is effective, along with ASU 2014-09, for annual and interim periods beginning after December 15, 2017. The adoption of ASU 2016-08 is not expected to have a material impact on its financial statements or disclosures.
In March 2016, the FASB issued ASU No. 2016-09, “Compensation – Stock Compensation (Topic 718)” (“ASU 2016-09”). ASU 2016-09 requires an entity to simplify several aspects of the accounting for share-based payment transactions, including the income tax consequences, classification of awards as either equity or liabilities, and classification on the statement of cash flows. ASU 2016-09 is effective for fiscal years beginning after December 15, 2016, with early adoption permitted. The Company is currently evaluating ASU 2016-09 and its impact on its financial statements or disclosures.
On May 9, 2016, the FASB issued ASU No. 2016-12, “Revenue from Contracts with Customers (Topic 606)” (“ASU 2016-12”). ASU 2016-12 provides clarifying guidance in a few narrow areas and adds some practical expedients to the guidance. The effective date and transition requirements for this ASU are the same as the effective date and transition requirements for ASU 2014-09. The Company is evaluating the effect of ASU 2014-09, if any, on its financial statements or disclosures.
The FASB and the SEC have issued certain accounting standards updates and regulations that will become effective in subsequent periods; however, management of the Company does not believe that any of those updates would have significantly affected the Company’s financial accounting measures or disclosures had they been in effect during 2016 or 2015, and does not believe that any of those pronouncements will have a significant impact on the Company’s consolidated financial statements at the time they become effective.
The Company evaluates events and/or transactions occurring after the balance sheet date and before the issue date of the condensed consolidated financial statements to determine if any of those events and/or transactions requires adjustment to or disclosure in the condensed consolidated financial statements.
No definition available.
The entire disclosure for all significant accounting policies of the reporting entity.
Reference 1: http://www.xbrl.org/2003/role/presentationRef