Revenue recognition
The Company recognizes revenue when control of the promised products or services are transferred to customers, in an amount that reflects the consideration that the Company expects to receive in exchange for those products and services. Revenue is recognized through the application of the following steps: (i) identification of the contract, or contracts, with a customer; (ii) identification of the performance obligations in the contract; (iii) determination of the transaction price; (iv) allocation of the transaction price to the performance obligations in the contract; and (v) recognition of revenue when (or as) the Company satisfies a performance obligation.
A contract exists with a customer when both parties have approved the contract, commitments to performance and rights of each party (including payment terms) are identified, the contract has commercial substance and collection of substantially all consideration is probable for goods and services that are transferred.
Performance obligations promised in a contract are identified based on the goods and services that will be transferred to the customer that are both capable of being distinct, whereby the customer can benefit from the good or service either on its own or together with other available resources, and are distinct in the context of the contract, whereby the transfer of the good or service is separately identifiable from other promises in the contract. If these criteria are not met, the promised goods and services are accounted for as a combined performance obligation.
The transaction price is determined based on the consideration the Company expects to be entitled to in exchange for transferring promised goods and services to the customer, excluding amounts collected on behalf of third parties such as sales taxes. Determining the transaction price requires significant judgment. To the extent the transaction price includes variable consideration, the Company estimates the amount of variable consideration that should be included in the transaction price utilizing either the expected value method or the most likely amount method depending on the nature of the variable consideration.
Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative SSP. The Company’s method for allocation of consideration to be received and its method of estimation of SSP are described below under “Significant judgments”.
For each of the Company’s major categories of revenue, the following paragraphs describe the applicable specific revenue recognition policy, and when the Company satisfies its performance obligations.
Nature of products and services
The Company is organized and managed as three reportable operating segments. The Company has multiple products and services from which it derives revenue, which are structured in three groups: QNX, Secure Communications and Licensing.
QNX
QNX consists of BlackBerry® QNX®, BlackBerry Radar®, BlackBerry® Certicom®, and other QNX applications. QNX revenue is generated predominantly through software licenses, commonly bundled with support, maintenance and professional services and through volume-based royalties.
QNX software license revenue from both term subscription and perpetual contracts is recognized at a point in time when the software is made available to the customer for use, as the software has standalone functionality and the license is distinct in the context of the contract. The licenses for certain software embedded into hardware such as automotive digital cockpit systems and advanced driver-assistance systems are sold as a sales-based royalty where intellectual property is the predominant item to which the royalty relates, and are recognized based on actual volumes and underlying sales by the customer of the hardware with the embedded software shipped by the customer, except in cases where the customer contractually commits to a certain volume or makes a non-refundable prepayment related to its future royalties, in which case consideration is fixed and recognized immediately.
Revenue from technical support is recognized over the support period. Revenue from professional services is recognized as the customer simultaneously receives and consumes the benefits provided by the Company’s performance as the services are provided. This can be on a proportional performance basis, or over the term of the contract. Revenue from software maintenance services is recognized over the length of the maintenance period, with an average term of one year.
Secure Communications
The Secure Communications business consists of BlackBerry unified endpoint management (“UEM”) solutions, BlackBerry® SecuSUITE® and BlackBerry® AtHoc® .
BlackBerry UEM
The Company’s endpoint management platform includes BlackBerry® UEM, BlackBerry® Dynamics™, and BlackBerry® Workspaces solutions. BlackBerry UEM employs a containerized approach to manage and secure devices, third party and custom applications, identity, content and endpoints. The Company generates software license revenue from term subscription contracts, which are commonly bundled with support, maintenance and professional services.
If the licensed software in a contract requires access to the Company’s proprietary secure network infrastructure in order to function, revenue from term subscription contracts is recognized over time, ratably over the term. If access to the Company’s proprietary network infrastructure is not required for the software to function, revenue associated with both term subscription and perpetual licenses contracts is recognized at a point in time upon delivery of the software. Generally, most of the Company’s UEM software products sold require access to the Company’s proprietary secure network infrastructure to function, and therefore the associated revenue is recognized over time, ratably over either the subscription term or expected customer life as described above.
BlackBerry SecuSUITE
SecuSUITE revenue is generated from software license products associated with secure communications and any associated hardware. Like BlackBerry UEM products, if the licensed software requires access to the Company’s proprietary secure network infrastructure, revenue from the contract is recognized over time, ratably over the expected term or over the customer life, if licensed on a perpetual basis. If access to the Company’s proprietary network infrastructure is not required, revenue associated with the license is recognized at a point in time upon delivery of the
software. Revenue from hardware is recognized once title and the significant risks and rewards of ownership of the products are transferred to the customer, which occurs when control transfers at date of shipment.
BlackBerry AtHoc
BlackBerry AtHoc generates revenue from networked critical event management solutions through perpetual and term subscriptions which include technical support, as well as associated professional services. The licensed software in most contracts requires access to the Company’s proprietary secure network infrastructure to function, specifically through AtHoc’s secure platform which is included within the Company’s data center. The Company recognizes the license revenue over the term of the contract beginning on the commencement date of each contract, the date that services are made available to customers.
Licensing
Licensing includes revenue from the Company’s intellectual property licensing arrangements and settlement awards.
The Company’s outbound patent licensing agreements provide for license fees that may be a single upfront payment or multiple payments representing all or a majority of the licensing revenue that will be payable to the Company. These agreements may be perpetual or term in nature and grant (i) a limited non-exclusive, non-transferable license to certain of the Company’s patents, (ii) a covenant not to enforce patent rights against the licensee, and (iii) the release of the licensee from certain claims.
The Company examines intellectual property agreements on a case-by-case basis to determine whether the intellectual property contains distinct performance obligations with standalone functionality and whether the Company is the principal or agent in the transaction. Significant judgment is applied in assessing contractual terms which could impact the timing and amount of revenue recognition. Revenue from patent licensing agreements is often recognized for the transaction price either when the license has been transferred to the customer or based upon subsequent sales by the customer in the case of sales-based royalty licenses where the license of intellectual property is the predominant item to which the royalty relates. As part of these agreements the Company may also recognize revenue relating to the sale and assignment of patents.
The Company recognizes revenue related to consideration that may result from a negotiated agreement with a licensee that utilized the Company’s IP prior to signing a patent license agreement with the Company or from the resolution of a disagreement or arbitration with a licensee over the specific terms of an existing license agreement. The Company may also recognize revenue related to consideration for past patent royalties in connection with the settlement of patent litigation where there was no prior patent license agreement.
See Note 13 for further information, including revenue by major product and service types.
Significant judgments in revenue recognition
The Company’s contracts with customers often include promises to transfer multiple products and services. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment.
Variable consideration is included in the transaction price if, in the Company’s judgment, it is probable that a significant future reversal of cumulative revenue recognized under the contract will not occur. Any estimates, including any constraints on variable consideration, are evaluated at each reporting period. To the extent the transaction price in a contract with a customer includes variable consideration, the Company estimates the amount of variable consideration that should be included in the price utilizing either the expected value method or the most likely amount method, depending on the nature of the variable consideration. The Company also estimates whether and how much variable consideration is subject to constraint if it cannot conclude it is probable that a significant reversal in revenue will not occur, due to factors such as: the consideration being highly susceptible to factors outside the Company’s influence, the period of time before the variable consideration is resolved, the Company’s previous experience with similar contracts, the Company’s history of price concessions or changing of payment terms, and whether there is a large number and broad range of possible variable consideration amounts.
Judgment is required to determine the SSP for each distinct performance obligation. The Company’s products and services often have observable SSP when the Company sells a promised product or service separately to similar customers. A contractually stated price or list price for a good or service may be the SSP of that good or service. However, in instances where SSP is not directly observable, the Company determines the SSP by maximizing observable
inputs and using an adjusted market assessment approach using information that may include market conditions and other observable inputs from the Company’s pricing team, including historical SSP.
Judgment is required to determine in certain agreements if the Company is the principal or agent in the arrangement. The Company considers factors such as, but not limited to, which party can direct the usage of the product or service, which party obtains substantially all the remaining benefits and which party has the ability to establish the selling price.
Revenue contract balances
Timing of revenue recognition may differ from the timing of invoicing to customers. Contract assets are generated when contractual billing schedules differ from revenue recognition timing. An unbilled receivable is recorded in instances when revenue is recognized prior to invoicing, and amounts collected in advance of services being provided are recorded as deferred revenue. Contract assets and liabilities are presented net as either a single contract asset or contract liability.
Certain sales commissions are considered incremental and recoverable costs of obtaining a contract with a customer. The Company’s capitalized commissions are recorded as other current assets and other long-term assets and are recognized immediately or amortized proportionally, based on the satisfaction of the related performance obligations, and are included in sales and marketing expenses. The Company has applied the practical expedient to expense sales commission as incurred if the amortization period would have been for one year or less. The practical expedient was applied to sales commissions allocated to professional services, as these contracts are generally for one year or less. See Note 13 for further information on the Company’s contract balances.
Payment terms and conditions vary by contract type and geography although standard billing terms are that payment is due upon receipt of invoice, generally payable within the agreed upon payment terms. In instances where the timing of revenue recognition differs from the timing of invoicing, the Company has determined that contracts generally do not include a significant financing component if the period between when the payment is received and when the Company transfers the promised goods or services to the customer will be one year or less. To the extent the Company determines that there is a significant financing component in a contract with a customer, it determines the impact of the time value of money in adjusting the transaction price to account for the income associated with the financing component by estimating the discount rate that would be reflected in a separate financing transaction between the customer and the Company at contract inception, based upon the credit characteristics of the customer receiving financing in the contract.

Historical Timeline

Fiscal YearFiled
2026Apr 9, 2026Showing above
2025Apr 2, 2025
2024Apr 4, 2024
2023Mar 31, 2023
2022Apr 1, 2022
2021Mar 31, 2021
2020Apr 7, 2020

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.