XML 21 R10.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Note 4 - Revenue Recognition | 3 Months Ended
--- | ---
Dec. 31, 2018
Notes to Financial Statements |
Revenue from Contract with Customer [Text Block] |
4. | REVENUE RECOGNITION
On October 1, 2018, the Company adopted the new accounting standard FASB Accounting Standards Codification (“ASC”) Topic 606, Revenue from Contracts with Customers (“ASC 606” ) for all contracts using the modified retrospective method. Based on the Company’s analysis of contracts with customers in prior periods, there was no cumulative effect adjustment to the opening balance of the Company’s accumulated deficit as a result of the adoption of this new standard. The Company derives its revenue from the sale of products to customers, contracts, license fees, other services and freight. The Company sells its products through its direct sales force and through authorized resellers and system integrators. The Company recognizes revenue for goods including software when all the significant risks and rewards have been transferred to the customer, no continuing managerial involvement usually associated with ownership of the goods is retained, no effective control over the goods sold is retained, the amount of revenue can be measured reliably, it is probable that the economic benefits associated with the transactions will flow to the Company and the costs incurred or to be incurred in respect of the transaction can be measured reliably. Software license revenue, maintenance and/or software development service fees may be bundled in one arrangement or may be sold separately. Product Revenue The Company sells its products to customers, including resellers and system integrators, and revenue is recognized in the period that products are shipped (free on board (“FOB”) shipping point) or received by customers (FOB destination), when the fee is fixed or determinable, when collection of resulting receivables is reasonably assured, and when there are no remaining obligations. Most revenues from resellers and system integrators are based on firm commitments from an end user, and as a result, resellers and system integrators carry little or no inventory. Our customers do not have the right to return product unless the product is found to be defective. Perpetual licensed software The sale and/or license of software products is deemed to have occurred when a customer either has taken possession of or has the ability to take immediate possession of the software and the software key. Perpetual software licenses can include one year maintenance and support services. In addition, the Company sells maintenance services on a stand-alone basis and is therefore capable of determining their fair value. On this basis, the amount of the embedded maintenance is separated from the fee for the perpetual license and is recognized on a straight-line basis over the period to which the maintenance relates. Time-based licensed software The time-based license agreements include the use of a software license for a fixed term, generally one -year, and maintenance and support services during the same period. The Company does not sell time-based licenses without maintenance and support services and therefore revenues for the entire arrangements are recognized on a straight-line basis over the term. Warranty, maintenance and services We offer extended warranty, maintenance and other services. Extended warranty and maintenance contracts are offered with terms ranging from one to several years, which provide repair and maintenance services after expiration of the original one -year warranty term. Revenues from separately priced extended warranty and maintenance contracts are recognized on a straight-line basis, over the contract period, and classified as contract and other revenues. Revenue from other services such as training or installation is recognized when the service is completed. Multiple element arrangements The Company has entered into a number of multiple element arrangements, such as the sale of a product or perpetual licenses that may include maintenance and support (included in price of perpetual licenses) and time-based licenses (that include embedded maintenance and support, both of which may be sold with software development services, training, and other product sales). In some cases, the Company delivers software development services bundled with the sale of the software. In multiple element arrangements, the Company uses either the stand-alone selling price or vendor specific objective evidence to determine the fair value of each element within the arrangement, including software and software-related services such as maintenance and support. In general, elements in such arrangements are also sold on a stand-alone basis and stand-alone selling prices are available. Revenue is allocated to each deliverable based on the fair value of each individual element and is recognized when the revenue recognition criteria described above are met, except for time-based licenses which are not unbundled. When software development services are performed and are considered essential to the functionality of the software, the Company recognizes revenue from the software development services on a stage of completion basis, and the revenue from the software when the related development services have been completed. We disaggregate revenue by reporting segment (Hardware (LRAD) and Software (Genasys)) and geographically to depict the nature of revenue in a manner consistent with our business operations and to be consistent with other communications and public filings. See Note 17, Segment Information and Note 18, Major Customers for additional details of revenues by reporting segment and disaggregation of revenue. Contract Assets and Liabilities We enter into contracts to sell products and provide services, and we recognize contract assets and liabilities that arise from these transactions. We recognize revenue and corresponding accounts receivable according to ASC 606 and, at times, recognize revenue in advance of the time when contracts give us the right to invoice a customer. We may also receive consideration, per terms of a contract, from customers prior to transferring goods to the customer. We record customer deposits as a contract liability. Additionally, we may receive payments, most typically for service and warranty contracts, at the onset of the contract and before the services have been performed. In such instances, we record a deferred revenue liability. We recognize these contract liabilities as revenue after all revenue recognition criteria are met. The table below shows the balance of contract assets and liabilities as of December 31, 2018 and September 30, 2018, including the change between the periods. The Company’s contract assets are as follows:
|  | Prepaid maintenance |
|  | agreement |
Balance at September 30, 2018 |  | $ | 93,750 |
New prepaid maintenance agreements |  |  | - |
Recognition of expense as a result of performing services |  |  | (46,875 | )
Balance at December 31, 2018 |  | $ | 46,875 |
Less: non-current portion |  |  | - |
Current portion at December 31, 2018 |  | $ | 46,875 |
The Company’s contract liabilities are as follows:
|  | Customer deposits |  |  | Deferred revenue |  |  | Total contract liabilities |
Balance at September 30, 2018 |  | $ | 199,596 |  |  | $ | 536,458 |  |  | $ | 736,054 |
New performance obligations |  |  | 137,431 |  |  |  | 159,907 |  |  |  | 297,338 |
Recognition of revenue as a result of satisfying performance obligations |  |  | (153,693 | ) |  |  | (270,461 | ) |  |  | (424,154 | )
Balance at December 31, 2018 |  | $ | 183,334 |  |  | $ | 425,904 |  |  | $ | 609,238 |
Less: non-current portion |  |  | - |  |  |  | (83,255 | ) |  |  | (83,255 | )
Current portion at December 31, 2018 |  | $ | 183,334 |  |  | $ | 342,649 |  |  | $ | 525,983 |
Remaining Performance Obligations Remaining performance obligations related to ASC 606 represent the aggregate transaction price allocated to performance obligations under an original contract with a term greater than one year which are fully or partially unsatisfied at the end of the period. As of December 31, 2018, the aggregate amount of the transaction price allocated to remaining performance obligations was approximately $609,238. We expect to recognize revenue on approximately $525,983 or 86% of the remaining performance obligations over the next 12 months, and the remainder is expected to be recognized thereafter. Practical Expedients In cases where we are responsible for shipping after the customer has obtained control of the goods, we have elected to treat these activities as fulfillment activities rather than as a separate performance obligation. Additionally, we have elected to capitalize the cost to obtain a contract only if the period of amortization would be longer than one year. We only give consideration to whether a customer agreement has a financing component if the period of time between transfer of goods and services and customer payment is greater than one year. We also utilize the “as invoiced” practical expedient in certain cases where performance obligations are satisfied over time and the invoiced amount corresponds directly with the value we are providing to the customer.

X
- References No definition available. + Details
Name: | us-gaap_DisclosureTextBlockAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration