Note 3 - Revenue

Financial Statement Impact of Adopting ASC 606, "Revenue from Contracts with Customers"

On July 1, 2020, we adopted ASC 606 using the modified retrospective transition method and applied this method to all contracts that were not complete as of the date of adoption. The reported results as of December 31, 2021 and December 31, 2020, and for the year ended December 31, 2021 and the six months ended December 31, 2020 in the accompanying consolidated financial statements are presented under ASC 606, while the year ended June 30, 2020 has not been adjusted and is reported in accordance with historical accounting guidance in effect for that period.

The most significant impacts of this standard relate to the timing of revenue recognition of fixed fees under our contracts, as well as the accounting for costs to obtain contracts. Under ASC 606, revenue recognition for subscription and implementation fees begins on the launch date and is recognized over time through the term of the contract. We then recognized the remaining balance of the fixed fees ratably over the remaining term of the contract. Additionally, under ASC 606, we now defer recognition of expense for sales commissions ("contract costs"). These contract costs are amortized to expense over the expected period of benefit. Before the adoption of ASC 606, we expensed these contract costs as incurred.

The adoption of ASC 606 under the modified retrospective transition method resulted in a net adjustment reducing the accumulated deficit by $0.2 million at July 1, 2020 and an increase to capitalized commissions, which  are included in prepaid expenses and other current assets on the  accompanying balance sheet. The adjustment consisted of $0.2 million related to the deferral of contract costs that were historically expensed as incurred

Revenue Recognition Policies for the year ended December 31, 2021 and the six months ended December 31, 2020  

In accordance with ASC 606, revenue is recognized when a customer obtains the benefit of promised services, in an amount that reflects the consideration the Company expects to be entitled to receive in exchange for those services. In determining the amount of revenue to be recognized, the Company performs the following steps: (i) identification of the contract with a customer; (ii) identification of the promised services in the contract and determination of whether the promised services are performance obligations, including whether they are distinct in the context of the contract; (iii) determination of the transaction price; (iv) allocation of the transaction price to the performance obligations based on estimated selling prices; and (v) recognition of revenue when (or as) the Company satisfies each performance obligation. 

Software Revenue. Our software revenue is generated from subscriptions and services related to the use of our commercial software platforms, MJ Platform®, Ample, Trellis, Viridian, 365 Cannabis, and our government regulatory platform, Leaf Data Systems, and the sale of business intelligence, data analytics and other software related services. Software contracts are annual or multi-year contracts paid monthly in advance of service and typically cancellable upon 30 days’ notice after the end of the contract period. Leaf Data Systems contracts are generally multi-year contracts payable annually or quarterly in advance of service. Commercial software and Leaf Data Systems contracts generally may only be terminated early for breach of contract as defined in the respective agreements. Amounts that have been invoiced are initially recorded as deferred revenue or contract liabilities. Subscription revenue is recognized on a straight-line basis over the service term of the arrangement beginning on the date that our solution is made available to the customer and ending at the expiration of the subscription term. We typically invoice customers at the beginning of the term, in multi-year, annual, quarterly, or monthly installments. When a collection of fees occurs in advance of service delivery, revenue recognition is deferred until such services commence. Revenue for implementation fees is recognized ratably over the expected term of the contract, including expected renewals.

We include service level commitments to customers warranting certain levels of uptime reliability and performance and permitting those customers to receive credits if those levels are not met. In addition, customer contracts often include: specific obligations that require us to maintain the availability of the customer’s data through the service and that customer content is secured against unauthorized access or loss, and indemnity provisions whereby we indemnify customers from third-party claims asserted against them that result from our failure to maintain the availability of their content or securing the same from unauthorized access or loss. To date, we have not incurred any material costs as a result of such commitments. Any such credits or payments made to customers under these arrangements are recorded as a reduction of revenue.

Consulting Revenue. Consulting services revenue is generated by providing solutions for operators in the pre-application of licensures and pre-operational phases of development and consists of contracts with fixed terms and fee structures based upon the volume and activity or fixed-price contracts for consulting and strategic services. These services include application and business plan preparation as they seek licenses to be granted. Consulting projects completed during the pre-application phase generally solidify us as the software vendor of choice for subsequent operational phases once the operator is granted the license. As a result, our consulting revenue is driven as new emerging states pass legislation, and as our client-operators gain licenses. Accordingly, we expect our consulting services to continue to grow as more states emerge with legalization reform. Consulting services revenue  When these services are not combined with subscription revenues as a single unit of account, these revenues are recognized as services are rendered and accepted by the customer. 

Other Revenue. Our other revenue is derived primarily from point-of-sale hardware and other non-recurring revenue. We sell solo*TAG^™ s and solo*CODE^™s to customers by the roll of printed labels or as a digital code that allows customers to print directly their packing. When customers active a solo*TAG^™ or solo*CODE^™, we receive an activation fee, which is recognized upon activation by the customer. From time to time, we may purchase equipment for resale to customers. Such equipment is generally drop-shipped to our customers. We recognize revenue as these products are delivered.

Cost of Revenue.  Cost of revenue consists primarily of costs related to providing subscription and other services to our customers, including employee compensation and related expenses for data center operations, customer support and professional services personnel, payments to outside technology service providers, security services, and other tools.

Unbilled Receivables. Unbilled receivables are booked when services are delivered to our customers but not yet invoiced. Once invoiced, the unbilled receivables are reclassified to accounts receivable.  

Revenue Recognition Policies for the year ended June 30, 2020

We derive our revenues primarily from the following sources: software revenues, which are primarily comprised of subscription fees from government and commercial customers accessing our enterprise cloud computing services and from customers paying for additional support beyond the standard support that is included in the basic subscription fees; and consulting services provided to operators interested in integrating our platform into their respective operations, such services include: assessing compliance requirements, monitoring systems and readiness; assisting with the application process; and evaluating the operator’s inspection readiness and business plan.

We commence revenue recognition when there is persuasive evidence of an arrangement, the service has been or is being provided to the customer, the collection of the fees is reasonably assured, and the amount of fees to be paid by the customer is fixed or determinable.

Deferred Revenue  

Deferred revenue consists of payments received in advance of revenue recognition from subscription services. The deferred revenue balance is influenced by several factors, including seasonality, the compounding effects of renewals, contract duration, and invoice frequency. Deferred revenue that will be recognized during the succeeding twelve-month period is recorded as deferred revenue, which is a current liability on the accompanying consolidated balance sheets.

Disaggregation of Revenue 

The Company derives the majority of its revenue from subscription fees paid for access to and usage of its SaaS solutions for a specified period of time, typically one to three years. In addition to subscription fees, contracts with customers may include implementation fees for launch assistance and training. Fixed subscription and implementation fees are billed in advance of the subscription term and are due in accordance with contract terms, which generally provide for payment within 30 days. The Company's contracts typically have a one to three year term. The Company's contractual arrangements include performance, termination and cancellation provisions, but do not provide for refunds. Customers do not have the contractual right to take possession of the Company's software at any time.

Sales taxes collected from customers and remitted to government authorities are excluded from revenue.