Accounting Policies, by Policy (Policies) |
9 Months Ended |
|---|---|
Sep. 30, 2025 | |
| Significant Accounting Policies [Abstract] | |
| Basic and diluted loss per share |
Basic and diluted loss per share Basic earnings (loss) per share is computed by dividing net earnings (loss) available to common shareholders by the weighted average number of shares outstanding during the reporting periods. Diluted earnings (loss) per share is computed similar to basic earnings (loss) per share, except that the weighted average shares outstanding are increased to include additional shares for the assumed exercise of stock options and warrants, if dilutive. The number of additional shares is calculated by assuming that outstanding stock options and warrants were exercised and that the proceeds from such exercises were used to acquire common stock at the average market price during the reporting periods. Potentially dilutive options as of September 30, 2025 totaled 401,557 (September 30, 2024 – 15,130) and warrants excluded from diluted loss per share as of September 30, 2025 totaled 1,733,741 (September 30, 2024 – 896,645). |
| Revenue recognition |
Revenue recognition The Company recognizes revenue when its customer obtains control of promised goods or services, in an amount that reflects the consideration which the entity expects to receive in exchange for those goods or services. To determine revenue recognition for arrangements that an entity determines are within the scope of Accounting Standards Codification ASC 606, Revenue from Contracts with Customers (“ASC 606”), the entity performs the following five steps: (i) identify the contract(s) with a customer; (ii) identify the performance obligations in the contract; (iii) determine the transaction price; (iv) allocate the transaction price to the performance obligations in the contract; and (v) recognize revenue when (or as) the entity satisfies a performance obligation. The Company only recognizes revenue from contracts when it is probable that the entity will collect substantially all the consideration it is entitled to in exchange for the goods or services it transfers to the customer. The Company earns revenue in two primary ways: 1) the sales of software-as-a-service (SAAS) from its interactive production software platform or 2) development and maintenance of custom-built software or other professional services. The Company recognizes SAAS revenues from its interactive production sales over the life of the contract as its performance obligations are satisfied. Payment terms vary by contract and can be periodic or one-time payments. The Company determines that the customer receives and consumes the benefits of the service simultaneously as the service is provided. The transaction price is allocated to the contractual performance obligations and recognized ratably over the contract term. The Company recognizes revenues received from the development and maintenance of custom-built software and other professional services provided upon the satisfaction of its performance obligation in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those services. Performance obligations can be satisfied either at a single point in time or over time. For those performance obligations that are satisfied at a single point in time, the revenue is recognized at that time. For each performance obligation satisfied over time, the Company recognizes revenue by measuring the progress toward complete satisfaction of that performance obligation. The Company generally measures progress comparing hours incurred to total estimated hours. For revenues received from the sales of advertising, the Company is deemed the agent in its revenue agreements. The Company does not own or obtain control of the digital advertising inventory. The Company recognizes revenues upon the achievement of agreed-upon performance criteria for the advertising inventory, such as a number of views, or clicks. As the Company is acting as an agent in the transaction, the Company recognizes revenue from sales of advertising on a net basis, which excludes amounts payable to partners under the Company’s revenue sharing agreements. The Company’s contracts with customers may include promises to transfer multiple products and services. For these contracts, the Company accounts for individual performance obligations separately if they are capable of being distinct and distinct within the context of the contract. Determining whether products and services are considered distinct performance obligations may require significant judgment. Judgment is also required to determine the stand-alone selling price, for each distinct performance obligation. During the nine months ended September 30, 2025 the Company recognized $176,000 attributed to professional services. No revenue was recognized attributed to professional services for the three months ended September 30, 2025. License Revenue – Related Party On April 30, 2025, pursuant to the Technology License and Software Development Agreement (the “License Agreement”) with ASPIS Cyber Technologies, Inc. (“ASPIS”), the Company delivered a functional license for its gamification, engagement, and QR code technology. ASPIS is an affiliate of the Company’s largest shareholder—Cronus Equity Capital Group, LLC (“CECG”)—which holds approximately 20.20% of the outstanding common shares of the Company as of September 30, 2025. Under the License Agreement, as amended by a side letter executed on August 11, 2025 and supported by a legal opinion and confirmation, the Initial Term is non-cancellable for twelve (12) months commencing April 30, 2025, with monthly license fees of $165,000 payable regardless of use. ASPIS will pay for any required technology modifications, improvements, and developments to Versus’ technology in addition to the license fee. The Company retains ownership of the technology, and ASPIS holds an exclusive license to use it in the cybersecurity industry so long as ASPIS continues to pay the monthly license fee. Since the license is a functional license and the performance obligation was satisfied upon delivery on April 30, 2025, the Company recognized the entire transaction price of $1,980,000 as revenue in the quarter ended June 30, 2025. The unbilled amounts will be invoiced and collected over the remaining term in accordance with the contract’s billing schedule. The Company invoices ASPIS on a monthly basis with 30 day payment terms. For the nine months ended September 30, 2025 the Company has collected $1,001,000 from ASPIS. The Company has elected the practical expedient under ASC 606-10-32-18 and does not adjust the consideration for the effects of a significant financing component if the Company expects that the period between when the Company transfers a promised good or service to a customer and when the customer pays for that good or service will be one year or less. |
| Accounts Receivable, net – Related Party |
Accounts Receivable, net – Related Party Accounts receivable are typically unsecured and are derived from revenue earned from customers. They are stated at invoice value less estimated allowances for credit losses. The Company performs ongoing credit evaluations of its customers to determine allowances for potential credit losses and doubtful accounts. The company has confidence in its ability to collect on all contracted revenues earned from customers. |
| Contract Assets – Related Party |
Contract Assets – Related Party Contract assets arise when the Company has earned revenue on a contract with a customer prior to billing. As of September 30, 2025, contract assets related to ASPIS totaled $1,166,000, representing the unbilled portion of the twelve-month non-cancellable Initial Term under the License Agreement. Contract assets are recorded on the Company’s consolidated balance sheets net of an allowance for credit losses. |
| Capitalized software development costs |
Capitalized Software Development Costs The Company capitalizes the costs of software developed or obtained for internal use in accordance with FASB ASC 350-40, Internal Use Software. Capitalized software development costs consist of costs incurred during the application development stage and include consulting costs for projects that qualify for capitalization. These costs relate to major new functionality. All other costs, primarily related to maintenance and minor software fixes, are expensed as incurred. The Company will amortize the capitalized software development costs on a straight-line basis over the estimated useful life of the software, which is generally three years, beginning when the asset is substantially ready for use. The amortization of capitalized software development costs will be reflected in cost of revenue. |
| Recent accounting pronouncements not yet adopted |
Recent accounting pronouncements not yet adopted New accounting pronouncements In November 2024, the FASB issued ASU No. 2024-03, Income Statement-Reporting Comprehensive Income-Expense Disaggregation Disclosures (“Subtopic 220-40”). This ASU improves financial reporting by requiring that public business entities disclose additional information about specific expense categories in the notes to the condensed consolidated financial statements at interim and annual reporting periods. This ASU will be effective for annual periods beginning after December 15, 2026, for interim reporting periods beginning after December 15, 2027, with early adoption is permitted. We are evaluating the potential impact of this guidance on our condensed consolidated financial statements and related disclosures. Recent adopted accounting pronouncements In December 2023, the FASB issued ASU 2023-09, Income Taxes (“Topic 740”): Improvements to Income Tax Disclosures. This ASU enhances the transparency and decision usefulness of income tax disclosures. It is designed to provide more detailed information about an entity’s income tax expenses, liabilities, and deferred tax items, potentially affecting how companies report and disclose their income tax-related information. The ASU is effective for public business entities for annual periods beginning after December 15, 2024, including interim periods within those fiscal years. The adoption of the guidance in the second quarter of 2025 did not have a material impact on our condensed consolidated financial statements and related disclosures. Management does not believe any other recently issued but not yet effective accounting pronouncement, if adopted, would have a material effect on the Company’s present or future condensed consolidated financial statements. |