Company: VLDXW
Filing Date: 2025-08-07
Form Type: S-1
Source: 0001641172-25-022475
Chunk: 219

Company: Velo3D, Inc.
Filing Date: 2025-08-07
Form: S-1
Chunk 219
---
 of expected credit losses on certain financial instruments. This guidance is effective for the Company for the fiscal year beginning after December 15, 2022. Early adoption is permitted. The Company adopted the new guidance in the first quarter of fiscal year 2023. The effect on the consolidated financial statements and related disclosures was not material.

In November 2023, the FASB issued ASU 2023-07, Segment Reporting (ASC Topic 280): Improvements to Reportable Segment Disclosures, which requires public entities to disclose information about their reportable segments’ significant expenses and other segment items on an interim and annual basis. Public entities with a single reportable segment are required to apply the disclosure requirements in ASU 2023-07, as well as all existing segment disclosures and reconciliation requirements in ASC Topic 280 on an interim and annual basis. The Company adoptedASU 2023-07 during the year ended December 31, 2024. The Company applied ASU 2023-07 retrospectively to the earliest period presented.

Recently Issued Accounting Pronouncements

In December 2023, the FASB issued ASU No. 2023-09 (“ASU 2023-09”), Income Taxes (Topic 740): Improvement to Income Tax Disclosures to enhance the transparency and decision usefulness of income tax disclosures. Two primary enhancements related to this ASU include disaggregating existing income tax disclosures relating to the effective tax rate reconciliation and income taxes paid. ASU 2023-09 is effective for annual periods beginning after December 15, 2024 on a prospective basis. Early adoption is permitted. The Company is currently evaluating the impact of this accounting standard update on the Company’s consolidated financial statements and related disclosures.

Licensing Revenue

Our revenue is partially derived from the licensing of computer software products and from their related maintenance contracts. We enter into contracts that include combinations of products, maintenance and services, which are accounted for as separate performance obligations with differing revenue recognition patterns.

Revenue from perpetual licenses is classified as software license revenue. Software license revenue is recognized up front upon delivery of the licensed product and/or the utility that enables the customer to access authorization keys, provided that an enforceable contract has been received. Typically, our perpetual licenses are sold with post-contract support (“PCS”), which includes unspecified technical enhancements and customer support. We allocate value in bundled perpetual and PCS arrangements based on the standalone selling prices of the perpetual license and PCS. Revenue from PCS is classified as maintenance revenue and is recognized