Accordingly, for accounting purposes, the financial statements of the Company represent a continuation of the financial statements of KORE with the acquisition being treated as the equivalent of KORE issuing stock for the net assets of CTAC, accompanied by a recapitalization. The net assets of CTAC were stated at historical cost, with no goodwill or other intangible assets recorded. KORE was deemed to be the predecessor and the consolidated assets and liabilities and results of operations prior to September 30, 2021 are those of KORE. Reported shares and earnings per share available to common stockholders, prior to the Business Combination, have been retroactively restated to reflect the exchange ratio established in the merger agreement. The number of shares of preferred stock was also retroactively restated based on the exchange ratio.

The guidance provides that an entity should apply the following steps: (1) identify the contract with a customer; (2) identify the performance obligations in the contract; (3) determine the transaction price; (4) allocate the transaction price to the performance obligations in the contract; and (5) recognize revenue when, or as, the entity satisfies a performance obligation. Payments are generally due and received within days from the point of billing customers.

The Company derives revenues primarily from IoT Connectivity and IoT Solutions. Connectivity arrangements provide customers with secure and reliable wireless connectivity to mobile and fixed devices through various mobile network carriers. Revenue from IoT Connectivity consists of monthly recurring charges (“MRC’s”) and overage/usage charges, and contracts are generally short-term in nature (i.e., arrangements). Revenue for MRC’s and overage/usage charges are recognized over time as the Company satisfies the performance obligation (generally starting when an enrolled device is activated on the Company’s platform). MRC’s are billed monthly in advance (generally in the last week of a month); any amounts billed for which the service has not been provided as of the balance sheet dates are reported as a contract liability and components of deferred revenue. Overage/usage charges are billed in arrears on a monthly cycle. Overage/usage charges are evaluated on a monthly basis, and any overage/usage charges determined by management as unlikely to be collected due to a customer disputing the charge or due to a concession are reserved. Reserved items are written off when deemed uncollectible or recognized as revenue if collected. Certain IoT Connectivity customers also have the option to purchase products and/or equipment (e.g. subscriber identification module or “SIM” cards, routers, phones, or tablets) from the Company on an as needed basis. Product sales to IoT Connectivity customers are recognized when control is transferred to the customer, which is typically upon shipment of the product.

IoT Solutions arrangements includes device solutions (including connectivity), deployment services, and/or technology-related professional services. Management evaluates each IoT Solutions arrangement to determine the contract for accounting purposes. If a contract contains more than one performance obligation, consideration is allocated to each performance obligation based on standalone selling prices. Device and other hardware sales in IoT Solutions arrangements are generally accounted for as separate contracts since the customer is not obligated to purchase additional services when committing to the purchase of any products. Such sales are typically recognized upon shipment to the customer. However, in certain contracts, the customer has requested the Company to hold the products ordered for later shipment to the customer’s remote location or to the customer’s end user as a part of a vendor managed inventory model. In these situations, management has concluded that transfer of control to the customer occurs prior to shipment. In these arrangements, the right to invoice, transfer of legal title and transfer of the risk and rewards associated with the products occurs when the Company receives the hardware from a third-party vendor and has deemed it to be functional. Additionally, the products are identified both physically and systematically as belonging to a specific customer, are usable by the customer, and are only shipped, used, or disposed as directed by the specific customer. Based on these factors, management recognizes revenue on hardware when the hardware is received by the Company and deemed functional. As part of the arrangements, the Company performs a service related to the storage of the hardware. The Company has determined that any storage fee related to inventory is immaterial to the consolidated financial statements taken as a whole.

The carrying amount of accounts receivable is reduced by a valuation allowance that reflects management’s best estimate of the amounts that will not be collected. Management reviews all accounts receivable balances that exceed terms from the invoice date individually, and based on an assessment of current creditworthiness, past payment history, and historical loss experience, and provides an allowance for the portion, if any, of the balance not expected to be collected. All accounts or portions thereof considered uncollectible or require excessive collection costs are written off to the allowance for doubtful accounts and recorded under selling, general and administrative expense in the consolidated statements of operations. The Company incurred bad debt expense of $0.3 million, $0.6 million and $0.9 million for the years ended December 31, 2021, 2020 and 2019, respectively. As of December 31, 2021 and 2020, the Company reduced accounts receivable for a valuation allowance for bad debt expense of $0.5

Company records its inventory, which primarily consists of finished goods such as SIM cards, other hardware and packaging materials, using the first-in, first-out method (“FIFO”). Certain items in inventory require limited assembly procedures to be performed before shipping the items to customers. Due to the insignificant nature and cost associated with the assembly procedures, the Company classifies these items as finished goods. Inventories are stated at the lower of cost or net realizable value. The Company performs ongoing evaluations and maintains a reserve if necessary for slow-moving and obsolete items, based upon factors surrounding the inventory age, amount of inventory on hand and projected sales.

The Company applies the provisions of ASC 820, Fair Value Measurements, for fair value measurements of financial assets and financial liabilities and for fair value measurements of items that are recognized or disclosed at fair value in the financial statements on a recurring basis. The Company also applied the provisions of the subtopic to fair value measurements of assets and liabilities that are recognized or disclosed at fair value in the financial statements on a basis. The subtopic defines fair value as the price that would be received to sell an asset or paid to transfer a liability in an orderly transaction between market participants at the measurement date. The subtopic also establishes a framework for measuring fair value and expands disclosures about fair value measurements. The fair value framework requires the Company to categorize certain assets and liabilities into three levels, based upon the assumptions used to price those assets or liabilities. The three levels are defined as follows:

In periods of net income, the Company allocates net income to the common shares under the method for the Series C Preferred shares and unvested share-based payment awards that contain participating rights to dividends or dividend equivalents (whether paid or unpaid). Because the Series C Preferred share and share-based payment awards do not have an obligation to fund losses, they are not included in the calculation during periods of losses because their effect would be antidilutive.

In December 2019, the FASB issued Accounting Standards Update (“ASU”) . ASU simplifies the accounting for income taxes by removing certain exceptions to the general principles in Topic 740. The amendments also improve consistent application of and simplify GAAP for other areas of Topic 740 by clarifying and amending existing guidance. ASU is effective for public business entities for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2020. The Company adopted this standard as of January 1, 2021, and depending on the amendment, adoption was applied on a retrospective, modified retrospective, or prospective basis. The adoption of the standard did not have a material impact on the Company’s consolidated financial statements and related disclosures.

In August 2018, the FASB issued ASU , which requires a customer in a hosting arrangement that is a service contract to apply the guidance on software to determine which implementation costs to recognize as an asset and which costs to expense. Costs to develop or obtain software that cannot be capitalized under Subtopic , such as training costs and certain data conversion costs, also cannot be capitalized for a hosting arrangement that is a service contract. The amendments require a customer in a hosting arrangement that is a service contract to determine whether an implementation activity relates to the preliminary project stage, the application development stage, or the post-implementation stage. Costs for implementation activities in the application development stage will be capitalized depending on the nature of the costs, while costs incurred during the preliminary project and post-implementation stages will be expensed immediately. The ASU is effective for the Company for annual reporting periods beginning after December 15, 2020, and interim periods within annual periods beginning after December 15, 2021. Early adoption is permitted, including adoption in any interim period, for all entities. The Company adopted this standard as of January 1, 2021. The adoption of the standard did not have a material impact on the Company’s consolidated financial statements and related disclosures.

In February 2016, the FASB issued ASU , to increase transparency and comparability among organizations by recognizing lease assets and lease liabilities on the balance sheet and disclosing key information about leasing arrangements. In July 2018, ASU , was issued to provide more detailed guidance and additional clarification for implementing ASU Furthermore, in July 2018, the FASB issued ASU , which provides an optional transition method in addition to the existing modified retrospective transition method by allowing a cumulative effect adjustment to the opening balance of retained earnings in the period of adoption. Furthermore, on June 3, 2020, the FASB deferred by one year the effective date of the new leases standard for private companies, private and public that have not yet issued (or made available for issuance) financial statements reflecting the new standard. Additionally, in March 2020, ASU , was issued to provide more detailed guidance and additional clarification for implementing ASU Furthermore, in June 2020, ASU , was issued to defer effective dates of adoption of the new leasing standard beginning after December 15, 2021, and interim periods within fiscal years beginning after December 15, 2022. These new leasing standards (collectively “ASC 842” or “the new standard”) are effective for the Company beginning after December 15, 2021, and interim periods within fiscal years beginning after December 15, 2022, with early adoption permitted.

The new standard also provides practical expedients for an entity’s ongoing accounting. We currently expect to elect the short-term lease recognition exemption for all leases that qualify. This means, for those leases that qualify, we will not recognize ROU assets or lease liabilities, and this includes not recognizing ROU assets or lease liabilities for existing short-term leases of those assets in transition. We also currently expect to elect the practical expedient to not separate lease and components for all of our leases.

In June 2016, the FASB issued ASU , which requires the use of a new current expected credit loss (“CECL”) model in estimating allowances for doubtful accounts with respect to accounts receivable and notes receivable. Receivables from revenue transactions, or trade receivables, are recognized when the corresponding revenue is recognized under ASC 606, . The CECL model requires that the Company estimate its lifetime expected credit loss with respect to these receivables and record allowances when deducted from the balance of the receivables, which represent the estimated net amounts expected to be collected. Given the generally short-term nature of trade receivables, the Company does not expect to apply a discounted cash flow methodology. However, the Company will consider whether historical loss rates are consistent with expectations of forward-looking estimates for its trade receivables. In November 2018, the FASB issued ASU Codto clarify that operating lease receivables recorded by lessors are explicitly excluded from the scope of ASU This ASU (collectively “ASC 326”) is effective for fiscal years beginning after December 15, 2023, and interim periods within those fiscal years. The Company is still evaluating the impact of the adoption of this ASU.

In March 2020, the FASB issued ASU , to provide guidance on easing the potential burden in accounting for reference rate reform on financial reporting. ASU is effective from March 12, 2020 and may be applied prospectively through December 31, 2022. The Company is still evaluating the impact of the adoption of this ASU.

In March 2020, the FASB issued ASU , which clarifies specific issues raised by stakeholders. Specifically, the ASU:

The amendments in the ASU have various effective dates and transition requirements, some depending on whether an entity has previously adopted ASU about measurement of expected credit losses. The Company will adopt the guidance in ASU as it adopts the related ASU effected by these codification improvements.

In May 2021, the FASB issued ASU ,which provides guidance on modifications or exchanges of a freestanding equity-classified written call option that is not within the scope of another Topic. An entity should treat a