Company: LRHC
Filing Date: 2025-11-19
Form Type: 10-Q
Source: 0001213900-25-112656
Chunk: 149

Company: La Rosa Holdings Corp.
Filing Date: 2025-11-19
Form: 10-Q
Item: Item 8
Chunk 149
---
 and other disclosures. ASU No. 2023-07 does not change how a public entity identifies its operating segments, aggregates those
operating segments or applies the quantitative thresholds to determine its reportable segments. The Company adopted ASU No. 2023-07 effective
December 31, 2024.

Recently
Issued Accounting Standards Not Yet Adopted 

In
September 2025, the FASB issued ASU 2025-7, Derivatives and Hedging (Topic 815) and Revenue from Contracts with Customers (Topic 606).
The amendments in this Update exclude from derivative accounting non-exchange-traded contracts with underlyings that are based on
operations or activities specific to one of the parties to the contract. However, this scope exception does not apply to (1) variables
based on a market rate, market price, or market index, (2) variables based on the price or performance of a financial asset or financial
liability of one of the parties to the contract, (3) contracts (or features) involving the issuer’s own equity that are evaluated
under the guidance in Subtopic 815-40, Derivatives and Hedging—Contracts in Entity’s Own Equity, and (4) call options and
put options on debt instruments. The amendments in this Update are effective for all entities for annual reporting periods beginning
after December 15, 2027, and interim reporting periods within those annual reporting periods. Early adoption is permitted as of the beginning
of an annual reporting period. The Company is currently evaluating the impact that the adoption of this new standard will have on its
consolidated financial statements.

9

La
                                            Rosa Holdings Corp. and Subsidiaries

Notes
to the Unaudited Condensed Consolidated Financial Statements

In
September 2025, the FASB issued ASU 2025-06, Intangibles—Goodwill and Other— Internal-Use Software (Subtopic 350-40).
The amendments in this Update remove all references to prescriptive and sequential software development stages (referred to as “project
stages”) throughout Subtopic 350-40. Therefore, an entity is required to start capitalizing software costs when both of the following
occur: 1. Management has authorized and committed to funding the software project. 2. It is probable that the project will be completed
and the software will be used to perform the function intended (referred to as the