XML 35 R24.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Summary of Significant Accounting Policies (Policies) | 9 Months Ended
--- | ---
Sep. 30, 2018
Accounting Policies [Abstract] |
Revenue Recognition | Revenue Recognition The Company recognizes revenue in accordance with Accounting Standards Codification (ASC) 606, “Revenue from Contracts with Customers.” The core principle of ASC 606 is to recognize revenue in a manner that depicts the transfer of promised goods or services to customers in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those goods or services. The framework in support of this core principle includes: (1) identifying the contract with the customer; (2) identifying the performance obligations in the contract; (3) determining the transaction price; (4) allocating the transaction price to the performance obligations; and (5) recognizing revenue when (or as) the performance obligations are satisfied. Identifying the Contract with the Customer The Company identifies contracts with customers as agreements that create enforceable rights and obligations, which typically take the form of customer contracts or purchase orders. Identifying the Performance Obligations in the Contract The Company identifies performance obligations as promises in contracts to transfer distinct goods or services. Standard products and services that the Company regularly sells separately are accounted for as distinct performance obligations. Application-specific customer solutions that are comprised of a combination of products and services are accounted for as one performance obligation to deliver a total solution to the customer. On-site support services that are provided to the customer after the solution is deployed are accounted for as a separate performance obligation. These solutions are provided to customers in a variety of industries, including the consumer electronics, logistics, and automotive industries. Shipping and handling activities for which the Company is responsible under the terms and conditions of the sale are not accounted for as performance obligations but as fulfillment costs. These activities are required to fulfill the Company’s promise to transfer the goods and are expensed when revenue is recognized. The Company does not assess whether promised goods or services are performance obligations if they are immaterial in the context of the contract. If revenue is recognized before immaterial promises have been completed, then the costs related to such immaterial promises are accrued at the time of sale. Determining the Transaction Price The Company determines the transaction price as the amount of consideration it expects to receive in exchange for transferring promised goods or services to the customer. Amounts collected from customers for sales taxes are excluded from the transaction price. If a contract includes a variable amount, such as a rebate, then the Company estimates the transaction price using either the expected value or the most likely amount of consideration to be received, depending upon the specific facts and circumstances. The Company includes estimated variable consideration in the transaction price only to the extent it is probable that a significant reversal of revenue will not occur when the uncertainty is resolved. The Company updates its estimate of variable consideration at the end of each reporting period to reflect changes in facts and circumstances. Allocating the Transaction Price to the Performance Obligations The Company allocates the transaction price to each performance obligation at contract inception based on a relative stand-alone selling price basis, or the price at which the Company would sell the good or service separately to similar customers in similar circumstances. Recognizing Revenue When (or As) the Performance Obligations are Satisfied The Company recognizes revenue when it transfers the promised goods or services to the customer. Revenue for standard products is recognized at the point in time when the customer obtains control of the goods, which is typically upon delivery when the customer has legal title, physical possession, the risks and rewards of ownership, and an enforceable obligation to pay for the products. Revenue for services, which are not material, is typically recognized over the time the service is provided. Revenue for application-specific customer solutions is recognized at the point in time when the solution is validated, which is the point in time when the Company can objectively determine that the agreed-upon specifications in the contract have been met and the customer will accept the performance obligations in the arrangement. Although the customer may have taken legal title and physical possession of the goods when they arrived at the customer’s designated site, the significant risks and rewards of ownership transfer to the customer only upon validation. Revenue for on-site support services related to these solutions is recognized over the time the service is provided. In certain instances, an arrangement may include customer-specified acceptance provisions or performance guarantees that allow the customer to accept or reject delivered products that do not meet the customer’s specifications. If the Company can objectively determine that control of a good or service has been transferred to the customer in accordance with the agreed-upon specifications in the contract, then customer acceptance is a formality. If acceptance provisions are presumed to be substantive, then revenue is deferred until customer acceptance. For the Company’s standard products and services, revenue recognition and billing typically occur at the same time. For application-specific customer solutions, however, the agreement with the customer may provide for billing terms which differ from revenue recognition criteria, resulting in either deferred revenue or unbilled revenue. Credit assessments are performed to determine payment terms, which vary by region, industry, and customer. Prepayment terms result in contract liabilities for customer deposits. When credit is granted to customers, payment is typically due 30 to 90 days from billing. The Company's contracts have an original expected duration of less than one year, and therefore as a practical expedient, the Company has elected to ignore the impact of the time value of money on a contract and to expense sales commissions. The Company recognizes an asset for costs to fulfill a contract if the costs relate directly to the contract and to future performance, and the costs are expected to be recovered. Management exercises judgment when determining the amount of revenue to be recognized each period. Such judgments include, but are not limited to, assessing the customer’s ability and intention to pay substantially all of the contract consideration when due, determining when two or more contracts should be combined and accounted for as a single contract, determining whether a contract modification has occurred, assessing whether promises are immaterial in the context of the contract, determining whether material promises in a contract represent distinct performance obligations, estimating the transaction price for a contract that contains variable consideration, determining the stand-alone selling price of each performance obligation, determining whether control is transferred over time or at a point in time for performance obligations, and assessing whether formal customer acceptance provisions are substantive.
New Pronouncements | Accounting Standards Update (ASU) 2016-02 and 2018-11, "Leases" ASU 2016-02 creates Topic 842, Leases. The objective of this ASU is to increase transparency and comparability among organizations by recognizing lease assets and lease liabilities on the balance sheet, and disclosing key information about leasing arrangements. This ASU applies to any entity that enters into a lease, although lessees will see the most significant changes. The main difference between current GAAP and Topic 842 is the recognition of lease assets and lease liabilities on the balance sheet for those leases classified as operating leases under current GAAP. Topic 842 distinguishes between finance leases and operating leases, which are substantially similar to the classification criteria for distinguishing between capital leases and operating leases under current GAAP. For public companies, the guidance in ASU 2016-02 is effective for annual periods beginning after December 15, 2018, and interim periods within those fiscal years. In July 2018, the Financial Accounting Standards Board issued ASU 2018-11 to amend ASU 2016-02 and provided an additional (and optional) transition method to adopt the new lease standard. This transition method allows entities to apply the new lease standard at the adoption date and recognize a cumulative-effect adjustment to the opening balance of retained earnings in the period of adoption instead of using the original modified retrospective transition method of adoption which required the restatement of all prior period financial statements. Under this new transition method, the comparative periods presented in the financial statements will continue to be in accordance with current GAAP (Topic 840, Leases). Management will adopt the new lease standard using this new transition method under ASU 2018-11. As of the date of this report, management has determined the scope of leases subject to the new accounting requirements, has selected a software package to assist with compliance, and has reviewed all leases in scope. Management is in the process of completing the implementation of the lease accounting software, training relevant employees, and finalizing the internal lease accounting policy and the related processes, internal controls, and disclosures. Accounting Standards Update (ASU) 2016-13, "Financial Instruments - Measurement of Credit Losses" ASU 2016-13 applies to all reporting entities holding financial assets that are not accounted for at fair value through net income (debt securities). The amendments in this ASU eliminate the probable initial recognition threshold to recognize a credit loss under current GAAP and, instead, reflect an entity’s current estimate of all expected credit losses. In addition, this ASU broadens the information an entity must consider in developing the credit loss estimate, including the use of reasonable and supportable forecasted information. The amendments in this ASU require that credit losses on available-for-sale debt securities be presented as an allowance rather than as a write-down and an entity will be able to record reversals of credit losses in current period net income. For public companies, the guidance in ASU 2016-13 is effective for annual periods beginning after December 15, 2019, and interim periods within those fiscal years. This ASU should be applied through a cumulative-effect adjustment to retained earnings as of the beginning of the first reporting period in which the guidance is effective. Management does not expect ASU 2016-13 to have a material impact on the Company's financial statements and disclosures. Accounting Standards Update (ASU) 2017-08, "Receivables - Nonrefundable Fees and Other Costs - Premium Amortization on Purchased Callable Debt Securities" ASU 2017-08 applies to all reporting entities that hold investments in callable debt securities that have an amortized cost basis in excess of the amount that is repayable by the issuer at the earliest call date (that is, at a premium). The amendments in this ASU shorten the amortization period for certain callable debt securities held at a premium. Specifically, the amendments require the premium to be amortized to the earliest call date. The amendments do not require an accounting change for securities held at a discount; the discount continues to be amortized to maturity. Under current GAAP, premiums and discounts on callable debt securities generally are amortized to the maturity date. If that callable debt security is subsequently called, the entity records a loss equal to the unamortized premium. The amendments in this ASU more closely align the amortization period of premiums and discounts to expectations incorporated in market pricing on the underlying securities. For public companies, the amendments in ASU 2017-08 are effective for annual periods beginning after December 15, 2019, and interim reporting periods within fiscal years beginning after December 15, 2020. This ASU should be applied on a modified retrospective basis through a cumulative-effect adjustment directly to retained earnings as of the beginning of the period of adoption, and, in the period of adoption, the entity is required to provide disclosures about the change in accounting principle. Early adoption is permitted, including adoption in an interim period. Management does not expect ASU 2017-08 to have a material impact on the Company's financial statements and disclosures. Accounting Standards Update (ASU) 2017-12, "Derivatives and Hedging - Targeted Improvements to Accounting for Hedging Activities" ASU 2017-12 applies to all reporting entities that elect to apply hedge accounting. The hedge accounting requirements under current GAAP sometimes do not permit an entity to properly recognize the economic results of the hedging strategy in the financial statements, and they are difficult to understand and interpret. The amendments in this ASU make certain targeted improvements to simplify the application of the hedge accounting guidance. Also, they better align the risk management activities and financial reporting for hedging relationships through changes to both 1) the designation and measurement guidance for qualifying hedging relationships and 2) the presentation of hedge results. For public companies, the amendments in ASU 2017-12 are effective for annual reporting periods beginning after December 15, 2018, and interim reporting periods within those fiscal years. Early adoption is permitted including adoption in any interim period after issuance of the ASU. All transition requirements and elections should be applied to hedging relationships existing on the date of adoption. The entity should apply a cumulative-effect adjustment related to eliminating the separate measurement of ineffectiveness to accumulated other comprehensive income with a corresponding adjustment to the opening balance of retained earnings as of the beginning of the fiscal year that an entity adopts the amendments in this ASU. The amended presentation and disclosure guidance is required only prospectively. Management does not expect ASU 2017-12 to have a material impact on the Company's financial statements and disclosures. Accounting Standards Update (ASU) 2018-01, "Land Easement Practical Expedient for Transition to Topic 842" ASU 2018-01 applies to entities with land easements that exist or expired before an entity’s adoption of Topic 842, provided that the entity does not account for those land easements as leases under Topic 840. The amendments in this ASU permit an entity to elect an optional transition practical expedient to not evaluate under Topic 842 land easements that exist or expired before the entity’s adoption of Topic 842 and that were not previously accounted for as leases under Topic 840. An entity that elects this practical expedient should apply the practical expedient consistently to all of its existing or expired land easements that were not previously accounted for as leases under Topic 840. Once an entity adopts Topic 842, it should apply that Topic prospectively to all new (or modified) land easements to determine whether the arrangement should be accounted for as a lease. An entity that does not elect this practical expedient should evaluate all existing or expired land easements in connection with the adoption of the new lease requirements in Topic 842 to assess whether they meet the definition of a lease. The amendments in this ASU affect the amendments in ASU 2016-02, which are not yet effective but may be early adopted. The effective date and transition requirements for the amendments are the same as the effective date and transition requirements in ASU 2016-02, which is for annual periods beginning after December 15, 2018, and interim periods within those fiscal years. Management does not expect ASU 2018-01 to have a material impact on the Company's financial statements and disclosures. Accounting Standards Update (ASU) 2018-02, "Income Statement - Reporting Comprehensive Income" ASU 2018-02 applies to entities required to apply the provisions of Topic 220, Income Statement - Reporting Comprehensive Income, and has items of other comprehensive income for which the related tax effects are presented in other comprehensive income as required by GAAP. The amendments in this ASU allow a reclassification from accumulated other comprehensive income to retained earnings for stranded tax effects resulting from the Tax Cuts and Jobs Act of 2017 (the "Tax Act"). Consequently, the amendments eliminate the stranded tax effects resulting from the Tax Act and will improve the usefulness of information reported to financial statement users. However, because the amendments only relate to the reclassification of the income tax effects of the Tax Act, the underlying guidance that requires the effect of a change in tax laws or rates to be included in income from continuing operations is not affected. The amendments in this ASU also require certain disclosures about stranded tax effects. The amendments in this ASU are effective for all entities for fiscal years beginning after December 15, 2018, and interim periods within those fiscal years. Early adoption of the amendments in this ASU is permitted, including adoption in any interim period. The amendments in this ASU should be applied either in the period of adoption or retrospectively to each period (or periods) in which the effect of the change in the U.S. federal corporate income tax rate in the Tax Act is recognized. Management does not expect ASU 2018-02 to have a material impact on the Company's financial statements and disclosures. Accounting Standards Update (ASU) 2018-07, "Compensation - Stock Compensation - Improvements to Nonemployee Share-Based Payment Accounting" ASU 2018-07 applies to all entities that enter into share-based payment transactions for acquiring goods and services from nonemployees. The amendments in this ASU expand the scope of Topic 718, Compensation - Stock Compensation, to include share-based payments transactions to nonemployees. Changes to the accounting for nonemployee awards as a result of this ASU include: 1) equity-classified nonemployee share-based payment awards are measured at the grant date, instead of the previous requirement to remeasure the awards through the performance completion date, 2) for awards with performance conditions, compensation cost is recognized when the achievement of the performance condition is probable, rather than upon achievement, and 3) the current requirement to reassess the classification (equity or liability) for nonemployee awards upon vesting is eliminated. This ASU clarifies that Topic 718 does not apply to financing transactions or awards granted to customers as part of a contract accounted for under Topic 606, Revenue from Contracts with Customers. The amendments in this ASU are effective for public business entities for fiscal years beginning after December 15, 2018, and interim periods within those fiscal years. An entity should only remeasure liability-classified awards that have not been settled by the date of adoption and equity-classified awards for which the measurement date has not been established through a cumulative-effect adjustment to retained earnings as of the beginning of the fiscal year of adoption. Management does not expect ASU 2018-07 to have a material impact on the Company's financial statements and disclosures. Accounting Standards Update (ASU) 2018-15, "Intangibles - Goodwill and Other - Internal-Use Software" ASU 2018-15 applies to entities that are a customer in a hosting arrangement that is a service contract. The amendments in this ASU align the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal-use software. Accordingly, the amendments in this ASU require an entity in a hosting arrangement that is a service contract to follow the guidance in Subtopic 350-40 to determine which implementation costs to capitalize as an asset related to the service contract and which costs to expense. Further, it requires the entity to expense the capitalized implementation costs over the term of the hosting arrangement. In addition, it requires the presentation of the expenses related to the capitalized implementation costs in the same line item in the statement of income as the fees associated with the hosting element of the arrangement and the classification of the payments for the capitalized implementation costs in the statement of cash flows in the same manner as the payments made for the fees associated with the hosting element. The amendments in this ASU are effective for public entities for fiscal years beginning after December 15, 2019, and interim periods within those fiscal years, with early adoption permitted. Management does not expect ASU 2018-15 to have a material impact on the Company's financial statement and disclosures.

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

X
- Definition Disclosure of accounting policy pertaining to new accounting pronouncements that may impact the entity's financial reporting. Includes, but is not limited to, quantification of the expected or actual impact. + References No definition available. + Details
Name: | us-gaap_NewAccountingPronouncementsPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for revenue recognition. If the entity has different policies for different types of revenue transactions, the policy for each material type of transaction is generally disclosed. If a sales transaction has multiple element arrangements (for example, delivery of multiple products, services or the rights to use assets) the disclosure may indicate the accounting policy for each unit of accounting as well as how units of accounting are determined and valued. The disclosure may encompass important judgment as to appropriateness of principles related to recognition of revenue. The disclosure also may indicate the entity's treatment of any unearned or deferred revenue that arises from the transaction. + References Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 605 -SubTopic 10 -Section S99 -Paragraph 1 -Subparagraph (SAB Topic 13.B.Q1) -URI http://asc.fasb.org/extlink&oid=65893310&loc=d3e214044-122780 Reference 3: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 3 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18780-107790 Reference 4: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 1 -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18726-107790 + Details
Name: | us-gaap_RevenueRecognitionPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration