SOBR Safe, Inc. Revenue Disclosure
The Company enters contracts with customers and generates revenue through various combinations of software products and services which include the sale of cloud-based software solutions, tracking, and data collection hardware devices, and cloud-based data reporting and analysis services. Depending on the combination of products and services detailed in the respective customer contract, the identifiable components may be highly interdependent and interrelated with each other such that each is required to provide the substance of the value of the Company’s offering and accounted for as a combined performance obligation, or the specific components may be generally distinct and accounted for as separate performance obligations. Revenue is recognized when control of these software products and/or services are transferred to the customer in an amount that reflects the consideration the Company expects to be entitled to in exchange for respective services and devices.
The Company determines revenue recognition through five steps which include: (1) identification of the contract or contracts with a customer; (2) identification of individual or combined performance obligations contained in the contract; (3) determination of the transaction price detailed within the contract; (4) allocation of the transaction price to the specific performance obligations; (5) recognition of revenue as the Company’s performance obligations are satisfied according to the terms of the contract.
Contracts with a Single License/Service Performance Obligation
For contracts with a single performance obligation consisting of a license and/or data services, the entire transaction price is allocated to the single performance obligation. Where the Company provides a performance obligation as licensed software or data services, revenue is recognized upon delivery of the software or services ratably over the respective term of the contract.
Contracts for Purchase of Hardware Devices Only
Where hardware devices are sold separately by the Company, the entire transaction price is allocated to the device as an individual performance obligation and revenue recognized at a point in time when either legal title, physical possession, or the risks and rewards of ownership have transferred to the customer. Generally, these requirements are satisfied at the point in time the Company ships the product, as this is when the customer obtains control of the asset under SOBR’s standard terms and conditions of the purchase.
Contracts with Multiple Performance Obligations
Where a Company’s contract with a respective customer contains multiple performance obligations and due to the interdependent and interrelated nature of the licensed software, hardware devices and data reporting services, the Company accounts for the individual performance obligations if they are distinct in nature and the transaction price is allocated to each distinct performance obligation(s) on a directly observable standalone sales price basis. Determining whether products and services are distinct performance obligations that should be accounted for separately or combined as one unit of accounting may require significant judgment. Standalone selling prices are primarily based upon the price at which the performance obligation is sold separately. The Company may be able to establish a standalone sales price based upon observable products or services sold or priced separately in comparable circumstances, competitor pricing or similar customers. Where the performance obligations are either not distinct or directly observable, the Company estimates the standalone sales price of the performance obligations based upon the overall pricing objectives taking into consideration the value of the contract arrangement, number of licenses, number and types of hardware devices and the length of term of the contract. Professional judgement may be required to determine the standalone sales price for each performance obligation where not directly observable. Revenue for contracts with multiple performance obligations is recognized on a ratable basis for each respective performance obligation as allocated under the prescribed Transaction Price identification model applied.
The Company requires customers to make payments related to subscribed software licenses and data services on a monthly basis via authorized bank account ACH withdrawal or an automatic credit card charge during the approved term of the respective agreement. The collectability of future cash flows are reasonably assured with any potential non-payment easily identified with future services being discontinued or suspended due to non-payment.
The Company’s contracts are generally three to twelve months in duration, billed monthly, and non-cancelable. The timing of revenue recognition may differ from the timing of invoicing to customers. The Company generally has an unconditional right to consideration when customers are invoiced, and a receivable is recorded. A contract asset (unbilled revenue) is recognized when revenue is recognized prior to invoicing, or a contract liability (deferred revenue) when revenue will be recognized subsequent to invoicing.
The Company has elected to charge shipping, freight, and delivery costs to customers as a source of revenue to offset respective costs when control has transferred to the customer.
The Company reports revenue net of sales and other taxes collected from customers to be remitted to government authorities.
Estimated costs for the Company’s standard one-year warranty are charged to cost of goods and services when revenue is recorded for the related product. Royalties are also charged to cost of goods and services.
Historical Timeline
| Fiscal Year | Filed | |
|---|---|---|
| 2025 | Apr 10, 2026 | Showing above |
| 2024 | Apr 15, 2025 | |
| 2023 | Apr 1, 2024 | |
About Revenue Disclosures
Revenue disclosures under ASC 606 explain how a company identifies performance obligations, allocates transaction prices, and determines when revenue is recognized. This section is essential for understanding whether reported revenue reflects genuine economic activity or aggressive accounting choices. Analysts examine the mix of point-in-time versus over-time recognition, which directly affects revenue timing and comparability.
Key signals: rising contract liabilities (deferred revenue) suggest strong future revenue visibility, while declining contract assets may indicate slowing project milestones. Watch for variable consideration estimates — rebates, returns, and performance bonuses that require management judgment. Significant changes in disaggregated revenue by geography or product line can reveal shifting business mix before it appears in headline numbers. Compare revenue growth against contract liability growth to assess sustainability, and scrutinize any changes in the timing of recognition that coincide with earnings pressure.