Principles of Consolidation

The consolidated financial statements include the accounts of the Company and our wholly owned subsidiaries Ondas Networks and FS Partners and our majority owned subsidiaries, Full Spectrum Holding and Ondas Network Limited. All significant inter-company accounts and transactions between these entities have been eliminated in these historical consolidated financial statements.

Use of Estimates

The process of preparing financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of assets and liabilities at the date of the financial statements. Such management estimates include those relating to revenue recognition, inventory write-downs to reflect net realizable value, assumptions used in the valuation of stock-based awards and warrants, and valuation allowances against deferred tax assets. Actual results could differ from those estimates.

Trade Accounts Receivable

Accounts receivable are stated at a gross invoice amount less an allowance for doubtful accounts. We estimate allowance for doubtful accounts by evaluating specific accounts where information indicates our customers may have an inability to meet financial obligations, such as customer payment history, credit worthiness and receivable amounts outstanding for an extended period beyond contractual terms. We use assumptions and judgment, based on the best available facts and circumstances, to record an allowance to reduce the receivable to the amount expected to be collected. These allowances are evaluated and adjusted as additional information is received. We had no allowance for doubtful accounts as of December 31, 2019 and 2018.

Property and Equipment

All additions, including improvements to existing facilities, are recorded at cost. Maintenance and repairs are charged to expense as incurred. Depreciation of property and equipment is principally recorded using the straight-line method over the estimated useful lives of the assets. The estimated useful lives typically are (i) three years for equipment and software, and (ii) five years for vehicles and furniture and fixtures. Leasehold improvements are amortized on a straight-line basis over the shorter of the lease term or the estimated useful life of the asset. Upon the disposal of property, the asset and related accumulated depreciation accounts are relieved of the amounts recorded therein for such items, and any resulting gain or loss is recorded in operating expenses in the year of disposition.

Impairment of Long-Lived Assets

Long-lived assets are evaluated whenever events or changes in circumstances indicate that the carrying amount may not be recoverable or the useful life has changed. Such indicators include significant technological changes, adverse changes in market conditions and/or poor operating results. The carrying value of a long-lived asset group is considered impaired when the projected undiscounted future cash flows is less than its carrying value. The amount of impairment loss recognized is the difference between the estimated fair value and the carrying value of the asset or asset group. Fair market value is determined primarily using the projected future cash flows discounted at a rate commensurate with the risk involved. Based upon our evaluation, there were no impairments of long-lived assets required during the years ended December 31, 2019 and 2018.

Research and Development

Costs for research and development are expensed as incurred. Research and development expense consists primarily of salaries, salary related expenses and costs of contractors and materials.

Income Taxes

Income taxes are accounted for under the asset and liability method. Deferred tax assets and liabilities are recognized for the estimated future tax consequences attributable to differences between the financial statement carrying amounts of existing assets and liabilities and their respective tax basis. Deferred tax assets and liabilities are measured using enacted tax rates expected to apply to taxable income in the years in which the related temporary differences are expected to be recovered or settled. The effect on deferred tax assets and liabilities of a change in tax rates is recognized when the rate change is enacted. Valuation allowances are recorded to reduce deferred tax assets to the amount that will more likely than not be realized. In accordance with GAAP, we recognize the effect of uncertain income tax positions only if the positions are more likely than not of being sustained in an audit, based on the technical merits of the position. Recognized uncertain income tax positions are measured at the largest amount that is greater than 50% likely of being realized. Changes in recognition or measurement are reflected in the period in which those changes in judgment occur. We recognize both interest and penalties related to uncertain tax positions as part of the income tax provision.

Deferred Offering Costs

The Company capitalizes certain legal, professional accounting and other third-party fees that are directly associated with in-process equity financings as deferred offering costs until such financings are consummated. After consummation of the equity financing, these costs are recorded in stockholders' deficit as a reduction of additional paid-in capital generated as a result of the offering. Should the planned equity financing be abandoned, the deferred offering costs will be expensed immediately as a charge to operating expenses in the consolidated statement of operations. In accordance with this policy, for the years ended December 31, 2019 and 2018, the Company expensed financing costs of $919,950 and $0, respectively.

ASC 606, Revenue from Contracts with Customers

On January 1, 2018, we adopted ASC 606, Revenue from Contracts with Customers ("ASC 606"), using the modified retrospective method with respect to all non-completed contracts. Revenues and contract assets and liabilities for contracts completed prior to January 1, 2018 are presented in accordance with ASC 605, Revenue Recognition. ASC 606 outlines a single comprehensive model for entities to use in accounting for revenue arising from contracts with customers and supersedes nearly all existing revenue recognition guidance, including industry-specific guidance. The new guidance is based on the principle that an entity should recognize revenue to depict the transfer of products or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those products or services. The new guidance also requires additional disclosure about the nature, amount, timing and uncertainty of revenue and cash flows arising from customer contracts, including significant judgment and changes in judgments and assets recognized from costs incurred to fulfill a contract. The adoption of ASC 606 did not have a material effect on our financial position, results of operations, or internal controls over financial reporting.

Under ASC 606, the Company recognizes revenue when the customer obtains control of promised products or services, in an amount that reflects the consideration which is expected to be received in exchange for those products or services. The Company recognizes revenue following the five-step model prescribed under ASC 606: (i) identify contract(s) with a customer; (ii) identify the performance obligation(s) in the contract; (iii) determine the transaction price; (iv) allocate the transaction price to the performance obligation(s) in the contract; and (v) recognize revenue when (or as) the Company satisfies a performance obligation. The Company only applies the five-step model to contracts when it is probable that the entity will collect the consideration it is entitled to in exchange for the products or services it transfers to the customer.

At contract inception, once the contract is determined to be within the scope of ASC 606, the Company assesses the products or services promised within each contract and determines those that are performance obligations and assesses whether each promised product or service is distinct. The Company then recognizes as revenue the amount of the transaction price that is allocated to the respective performance obligation when (or as) the performance obligation is satisfied. To the extent the transaction price includes variable consideration, we estimate the amount of variable consideration that should be included in the transaction price utilizing the expected value method. Variable consideration is included in the transaction price if, in our judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur. Estimates of variable consideration and determination of whether to include estimated amounts in the transaction price are based largely on an assessment of our anticipated performance and all information (historical, current and forecasted) that is reasonably available. Sales, value add, and other taxes collected on behalf of third parties are excluded from revenue. For the years ended December 31, 2019 and 2018, none of our contracts with customers included variable consideration.

Contracts that are modified to account for changes in contract specifications and requirements are assessed to determine if the modification either creates new or changes the existing enforceable rights and obligations. Generally, contract modifications are for products or services that are not distinct from the existing contract due to the inability to use, consume or sell the products or services on their own to generate economic benefits and are accounted for as if they were part of that existing contract. The effect of a contract modification on the transaction price and measure of progress for the performance obligation to which it relates, is recognized as an adjustment to revenue (either as an increase in or a reduction of revenue) on a cumulative catch-up basis. For the years ended December 31, 2019 and 2018, there were no modifications to contract specifications.

The Company is engaged in the development, marketing and sale of wireless radio systems for secure, wide area mission-critical business-to-business networks. We generate revenue primarily from the sale of the FullMAX System and the delivery of related services.

Product revenue is comprised of sales of the Company's software defined base station and remote radios, its network management and monitoring system, and accessories. The Company's software and hardware is sold with a limited one-year basic warranty included in the price. The limited one-year basic warranty is an assurance-type warranty, is not a separate performance obligation, and thus no transaction price is allocated to it. The nature of tasks under the limited one-year basic warranty only provide for remedying defective product(s) covered by the warranty. Product revenue is generally recognized when the customer obtains control of our product, which occurs at a point in time, and may be upon shipment or upon delivery based on the contractual shipping terms of a contract, or upon installation when the combined performance obligation is not distinct within the context of the contract.

Service revenue is comprised of separately priced extended warranty sales, network support and maintenance, remote monitoring, as well as ancillary services directly related to the sale of the Company's wireless communications products including wireless network design, systems engineering, radio frequency planning, software configuration, product training, installation, and onsite support. The extended warranty sold by the Company provides a level of assurance beyond the coverage for defects that existed at the time of a sale or against certain types of covered damage. The extended warranty includes 1) factory hardware repair or replacement, at our election, of the base station and remote radios, 2) software upgrades, bug fixes and new features of the radio software and NMS, 3) deployment and network architecture support, and 4) technical support by phone and email. Extended warranty, network support and maintenance, and remote monitoring revenues are recognized ratably over the term of the service contract. Ancillary service revenues are recognized at the point in time when those services have been provided to the customer and the performance obligation has been satisfied. With respect to extended warranty sales and remote monitoring, the Company applies the input method using straight-line recognition.

If the customer contract contains a single performance obligation, the entire transaction price is allocated to the single performance obligation. We enter into certain contracts that have multiple performance obligations, one or more of which may be delivered subsequent to the delivery of other performance obligations. We allocate the transaction price based on the estimated relative standalone selling prices of the promised products or services underlying each performance obligation. We determine standalone selling prices based on the price at which the performance obligation is sold separately. If the standalone selling price is not observable through past transactions, we estimate the standalone selling price considering available information such as market conditions and internally approved pricing guidelines related to the performance obligations. Revenue is then allocated to the performance obligations using the relative selling prices of each of the performance obligations in the contract.

Our payment terms vary and range from Net 15 to Net 30 days from the date of the invoices.

Disaggregation of Revenue

The following tables present our disaggregated revenues by Type of Revenue and Timing of Revenue.

Contract Assets and Liabilities

We recognize a receivable or contract asset when we perform a service or transfer a good in advance of receiving consideration. A receivable is recorded when our right to consideration is unconditional and only the passage of time is required before payment of that consideration is due. A contract asset is recorded when our right to consideration in exchange for good or services that we have transferred to a customer is conditional on something other than the passage of time. We did not have any contract assets recorded at December 31, 2019 and 2018.

We recognize a contract liability when we receive consideration, or if we have the unconditional right to receive consideration, in advance of satisfying the performance obligation. A contract liability is our obligation to transfer goods or services to a customer for which we have received consideration, or an amount of consideration is due from the customer. The table below details the activity in our contract liabilities during the years ended December 31, 2019 and 2018, and the balance at the end of each year is reported as deferred revenue in the Company's consolidated balance sheet.

Warranty Reserve

We provide a limited one-year assurance-type warranty on our software and hardware products. The assurance-type warranty covers defects in material and wordsmanship only. If a warranted software or hardware component is determined to be defective after being tested by the Company, the Company will repair, replace or refund the price of the covered hardware and/or software to the customer (not including any shipping, handling, delivery or installation charges). We estimate, based upon a review of historical warranty claim experience, the costs that may be incurred under our warranties and record a liability in the amount of such estimate at the time a product is sold. Factors that affect our warranty liability include the number of units sold, historical and anticipated rates of warranty claims, and cost per claim. We periodically assess the adequacy of our recorded warranty liability and adjust the accrual as claims data and historical experience warrants. The Company has assessed the costs of fulfilling its existing assurance-type warranties and has determined that the estimated outstanding warranty obligation at December 31, 2019 and 2018 is immaterial to the Company's financial statements.

Net Loss Per Common Share

Net loss per share for all periods presented is based on the equity structure of the legal acquirer, which assumes common stock is outstanding and is reflected on a retrospective basis for all periods presented. Basic net loss per share is computed by dividing net loss by the weighted average shares of common stock outstanding for each period. Diluted net loss per share is the same as basic net loss per share since the Company has net losses for each period presented.

The following potentially dilutive securities for the years ended December 31, 2019 and 2018 have been excluded from the computation of diluted net loss per share because the effect of their inclusion would have been anti-dilutive.

Concentrations of Credit Risk

Financial instruments that potentially subject us to concentrations of credit risk consist of cash and accounts receivable. Cash is deposited with a limited number of financial institutions. The balances held at any one financial institution may be in excess of Federal Deposit Insurance Corporation (FDIC) insurance limits.

Credit is extended to customers based on an evaluation of their financial condition and other factors. We generally do not require collateral or other security to support accounts receivable. We perform ongoing credit evaluations of our customers and maintain an allowance for doubtful accounts and sales credits.

Recently Adopted Accounting Pronouncements

In June 2018, the FASB issued ASU 2018-07, Compensation - Stock Compensation (Topic 718): Improvements to Nonemployee Share-Based Payment Accounting ("ASU 2018-07"). The amendments in ASU 2018-07 expand the scope of Topic 718 to include share-based payment transactions for acquiring goods and services from nonemployees. ASU 2018-07 is effective for fiscal years beginning after December 15, 2018, and interim periods within those fiscal years. Early adoption is permitted. The Company has elected to early adopt ASU 2018-07. The adoption of this pronouncement had no impact on our accompanying consolidated financial statements.

In July 2017, the FASB issued ASU 2017-11 ("ASU 2017-11"), Earnings Per Share ("Topic 260"), Distinguishing Liabilities from Equity ("Topic 480"), and Derivatives and Hedging ("Topic 815"). ASU 2017-11 is intended to simplify the accounting for financial instruments with characteristics of liabilities and equity. Among the issues addressed are: (i) determining whether an instrument (or embedded feature) is indexed to an entity's own stock; (ii) distinguishing liabilities from equity for mandatorily redeemable financial instruments of certain nonpublic entities; and (iii) identifying mandatorily redeemable non-controlling interests. ASU 2017-11 was effective for the Company on January 1, 2019. There was no material effect on the 2019 financial statements upon adoption.

In August 2016, the FASB issued ASU 2016-15, Statement of Cash Flows (Topic 230) ("ASU 2016-15"). ASU 2016-15 is intended to reduce the diversity in practice regarding how certain transactions are classified within the statement of cash flows. ASU 2016-15 is effective for public business entities for annual periods beginning after December 15, 2017, including interim periods within those fiscal years. There was no material effect on the 2019 and 2018 financial statements upon adoption.

In February 2016, the FASB issued ASU 2016-02, Leases. This guidance requires lessees to record most leases on their balance sheet while recognizing expenses on their income statements in a manner similar to current accounting. The guidance also eliminates current real estate-specific provisions for all entities. For lessors, the guidance modifies the classification criteria and the accounting for sales-type and direct financing leases. The standard is effective for public business entities for annual periods beginning after December 15, 2018, and interim periods within those years. Early adoption is permitted for all entities. In July 2018, the FASB amended the new leases standard and issued ASU 2018-11, Leases, (Topic 842): Targeted Improvements to give entities another option for transition and to provide lessors with practical expedient. We adopted ASU 2016-02 on January 1, 2019 utilizing the alternative transition method allowed for under ASU 2018-11. Comparative financial information was not adjusted and will continue to be reported under ASC 840. We also elected the transition relief package of practical expedients and as a result we did not assess (1) whether existing or expired contracts contain leases, (2) lease classification for any existing or expired leases, and (3) whether lease origination costs qualified as initial direct costs. We elected the short-term lease practical expedient by establishing an accounting policy to exclude leases with a term of 12 month or less. We elected not to separate lease components from non-lease components for our specified asset classes. Additionally, the adoption of the new standard resulted in increased disclosure requirements in our quarterly and annual filings.

In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606). The standard's core principle is that a company will recognize revenue when it transfers 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. In doing so, companies will need to use more judgment and make more estimates than under previous guidance. These may include identifying performance obligations in the contract, estimating the amount of variable consideration to include in the transaction price and allocating the transaction price to each separate performance obligation. In July 2015, the FASB approved the proposal to defer the effective date of ASU 2014-09 standard by one year. In 2016, the FASB issued final amendments to clarify the implementation guidance for principal versus agent considerations (ASU 2016-08), accounting for licenses of intellectual property and identifying performance obligations (ASU 2016-10), narrow-scope improvements and practical expedients (ASU 2016-12) and technical corrections and improvements to Topic 606 (ASU 2016-20) in its new revenue standard. The guidance is effective for public entities for annual reporting periods beginning after December 15, 2017 and interim periods therein. Our services are performed over the term of our contracts and customers are billed for those services as they are performed on a monthly basis. Revenue is recognized each month for the services that have been provided to our customers. Additionally, we do not have significant exposure related to uncollectible accounts. We have performed a review of the requirements of the new revenue standard and have performed our analysis of our customer contracts on a portfolio basis (by each hospital group) utilizing the five-step model of the new standard. We have compared the results of our analysis to our current accounting practices. We adopted Topic 606 on January 1, 2018 using the full retrospective transition method for recognizing revenue. The adoption of Topic 606 represents a change in accounting principle that will more closely align revenue recognition with the delivery of our services to our customers and will provide financial statement readers with enhanced disclosures. The adoption of this standard did not have a material effect on the timing and recognition of revenue for the services provided to our customers.