XML 26 R7.htm IDEA: XBRL DOCUMENT
v3.19.1

Basis of Presentation | 3 Months Ended
--- | ---
Mar. 31, 2019
Basis of Presentation |
Basis of Presentation | Note 1 — Basis of Presentation The accompanying unaudited Consolidated Financial Statements of Veeco have been prepared in accordance with U.S. GAAP as defined in Financial Accounting Standards Board (“FASB”) Accounting Standards Codification 270 for interim financial information and with the instructions to Rule 10-01 of Securities and Exchange Commission Regulation S-X. Accordingly, they do not include all of the information and footnotes required by U.S. GAAP for complete financial statements as the interim information is an update of the information that was presented in Veeco’s most recent annual financial statements. For further information, refer to Veeco’s Consolidated Financial Statements and Notes thereto included in the Annual Report on Form 10-K for the year ended December 31, 2018 (“2018 Form 10-K”). In the opinion of management, all adjustments considered necessary for a fair presentation have been included. All such adjustments are of a normal, recurring nature. Veeco reports interim quarters on a 13-week basis ending on the last Sunday of each quarter. The fourth quarter always ends on the last day of the calendar year, December 31. The 2019 interim quarters end on March 31, June 30, and September 29, and the 2018 interim quarters ended on April 1, July 1, and September 30. These interim quarters are reported as March 31, June 30, and September 30 in Veeco’s interim consolidated financial statements. Revenue Recognition Revenue is recognized upon the transfer of control of the promised product or service to the customer in an amount that reflects the consideration the Company expects to receive in exchange for such product or service. The Company’s contracts with customers generally do not contain variable consideration. In the rare instances where variable consideration is included, the Company estimates the amount of variable consideration and determines what portion of that, if any, has a high probability of significant subsequent revenue reversal, and if so, that amount is excluded from the transaction price. The Company’s contracts with customers frequently contain multiple deliverables, such as systems, upgrades, components, spare parts, installation, maintenance, and service plans. Judgment is required to properly identify the performance obligations within a contract and to determine how the revenue should be allocated among the performance obligations. The Company also evaluates whether multiple transactions with the same customer or related parties should be considered part of a single contract based on an assessment of whether the contracts or agreements are negotiated or executed within a short time frame of each other or if there are indicators that the contracts are negotiated in contemplation of one another. When there are separate units of accounting, the Company allocates revenue to each performance obligation on a relative stand-alone selling price basis. The stand-alone selling prices are determined based on the prices at which the Company separately sells the systems, upgrades, components, spare parts, installation, maintenance, and service plans. For items that are not sold separately, the Company estimates stand-alone selling prices generally using an expected cost plus margin approach. Most of the Company’s revenue is recognized at a point in time when the performance obligation is satisfied. The Company considers many facts when evaluating each of its sales arrangements to determine the timing of revenue recognition, including its contractual obligations and the nature of the customer’s post-delivery acceptance provisions. The Company’s system sales arrangements, including certain upgrades, generally include field acceptance provisions that may include functional or mechanical test procedures. For many of these arrangements, a customer source inspection of the system is performed in the Company’s facility, test data is sent to the customer documenting that the system is functioning to the agreed upon specifications prior to delivery, or other quality assurance testing is performed internally to ensure system functionality prior to shipment. Historically, such source inspection or test data replicates the field acceptance provisions that are performed at the customer’s site prior to final acceptance of the system. When the Company objectively demonstrates that the criteria specified in the contractual acceptance provisions are achieved prior to delivery either through customer testing or the Company’s historical experience of its tools meeting specifications, transfer of control of the product to the customer is considered to have occurred and revenue is recognized upon system delivery since there is no substantive contingency remaining related to the acceptance provisions at that date. For new products, new applications of existing products, or for products with substantive customer acceptance provisions where the Company cannot objectively demonstrate that the criteria specified in the contractual acceptance provisions have been achieved prior to delivery, revenue and the associated costs are deferred. The Company recognizes such revenue and costs upon obtaining objective evidence that the acceptance provisions can be achieved, assuming all other revenue recognition criteria have been met. In certain cases the Company’s contracts with customers contain a billing retention, typically 10% of the sales price, which is billed by the Company and payable by the customer when field acceptance provisions are completed. Revenue recognized in advance of the amount that has been billed is recorded as a contract asset on the Consolidated Balance Sheets. The Company recognizes revenue related to maintenance and service contracts over time based upon the respective contract term. Installation revenue is recognized over time as the installation services are performed. The Company recognizes revenue from the sales of components, spare parts, and specified service engagements at a point in time, which is typically consistent with the time of delivery in accordance with the terms of the applicable sales arrangement. The Company may receive customer deposits on system transactions. The timing of the transfer of goods or services related to the deposits is either at the discretion of the customer or expected to be within one year from the deposit receipt. As such, the Company does not adjust transaction prices for the time value of money. Incremental direct costs incurred related to the acquisition of a customer contract, such as sales commissions, are expensed as incurred since the expected amortization period is one year or less. The Company has elected to treat shipping and handling costs as a fulfillment activity, and the Company includes such costs in cost of services when the Company recognizes revenue for the related goods. Taxes assessed by governmental authorities that are collected by the Company from a customer are excluded from revenue. Leases At contract inception, the Company determines if an arrangement is a lease, or contains a lease, of an identified asset for which the Company has the right to obtain substantially all of the economic benefits from its use and the right to direct its use. Right-of-use (“ROU”) assets represent the Company’s right to use an underlying asset for the lease term, while lease liabilities represent the Company’s obligation to make lease payments arising from the lease. Operating lease ROU assets and liabilities are recognized at lease commencement date based on the present value of lease payments over the lease term. The implicit discount rate in the Company’s leases generally cannot readily be determined, and therefore the Company uses its incremental borrowing rate based on information available at lease commencement date in determining the present value of future payments. The Company has options to renew or terminate certain leases. These options are included in the determination of lease term when it is reasonably certain that the Company will exercise such options. The Company does not separate lease and non-lease components in determining ROU assets or lease liabilities for real estate leases. Additionally, the Company does not recognize ROU assets or lease liabilities for leases with original terms or renewals of one year or less. Recently Adopted Accounting Standards In February 2016, the FASB issued ASU 2016-02: Leases, which, along with subsequent ASUs related to this topic, has been codified as Accounting Standards Codification 842 (“ASC 842”). ASC 842 generally requires operating lessee rights and obligations to be recognized as assets and liabilities on the balance sheet. The new standard, which the Company adopted effective January 1, 2019, offers a transition option whereby companies can recognize a cumulative-effect adjustment to the opening balance of retained earnings in the period of adoption rather than in the earliest period presented. The Company has adopted using this transition method, and therefore prior period balances have not been adjusted. In addition, ASC 842 provides for a number of optional exemptions in transition. The Company has elected certain exemptions whereby prior conclusions regarding lease identification, lease classification, and initial direct costs were not reassessed under the new standard. The adoption of the standard impacted the Company’s Consolidated Balance Sheets through the recognition of ROU assets and lease liabilities of approximately $14.2 million each as of January 1, 2019, but did not have an impact on the Consolidated Statements of Operations, Statements of Comprehensive Income, or Statements of Cash Flows.

X
- Definition The entire disclosure for the basis of presentation and significant accounting policies concepts. Basis of presentation describes the underlying basis used to prepare the financial statements (for example, US Generally Accepted Accounting Principles, Other Comprehensive Basis of Accounting, IFRS). Accounting policies describe all significant accounting policies of the reporting entity. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_BasisOfPresentationAndSignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- References No definition available. + Details
Name: | us-gaap_OrganizationConsolidationAndPresentationOfFinancialStatementsAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration