XML 18 R7.htm IDEA: XBRL DOCUMENT
v3.8.0.1

Summary of Significant Accounting Policies (Text Block) | 3 Months Ended
--- | ---
Mar. 31, 2018
Accounting Policies [Abstract] |
Significant Accounting Policies [Text Block] | Summary of Significant Accounting Policies Financial Statement Preparation The condensed consolidated financial statements presented in this Quarterly Report on Form 10-Q are unaudited and reflect entries necessary for the fair presentation of the Consolidated Statements of Operations and the Consolidated Statements of Comprehensive Income (Loss) for the three months ended March 31, 2018 and 2017, the Consolidated Balance Sheets as of March 31, 2018 and December 31, 2017, and the Consolidated Statements of Cash Flows for the three months ended March 31, 2018 and 2017 of Itron, Inc. and its subsidiaries. All entries required for the fair presentation of the financial statements are of a normal recurring nature, except as disclosed. The results of operations for the three months ended March 31, 2018 are not necessarily indicative of the results expected for the full year or for any other period. Certain information and notes normally included in financial statements prepared in accordance with U.S. generally accepted accounting principles (GAAP) have been condensed or omitted pursuant to the rules and regulations of the Securities and Exchange Commission (SEC) regarding interim results. These condensed consolidated financial statements should be read in conjunction with the audited financial statements and notes included in our 2017 Annual Report on Form 10-K filed with the SEC on February 28, 2018. There have been no significant changes in financial statement preparation or significant accounting policies since December 31, 2017, with the exception of the adoption of Accounting Standards Codification (ASC) 606, Revenue from Contracts with Customers (Topic 606). On January 1, 2018, we adopted Topic 606 using the modified retrospective method applied to those contracts that were not completed. Results for reporting periods beginning after January 1, 2018 are presented under Topic 606, while prior period amounts are not adjusted and continue to be reported in accordance with our historic accounting under ASC 605, Revenue Recognition. The cumulative impact of adoption was a net decrease to accumulated deficit of $10.9 million as of January 1, 2018, with the impact primarily related to multiple element arrangements that contain software and software related elements. As we had not established vendor specific objective evidence of fair value for certain of our software and software related elements, we historically combined them as one unit of account and recognized the combined unit of account using the combined services approach. Under Topic 606, these software and software related elements are generally determined to be distinct performance obligations. As such, we are able to recognize revenue as we satisfy the performance obligations, either at a point in time or over time. For contracts that were modified prior to January 1, 2018, we have reflected the aggregate effect of all modifications prior to the date of initial adoption in order to identify the satisfied and unsatisfied performance obligations, determine the transaction price, and allocate the transaction price to satisfied and unsatisfied performance obligations. The impact to revenues for the three months ended March 31, 2018 was immaterial as a result of applying Topic 606. Refer to the updated Revenue Recognition accounting policy described below and Note 16 for additional disclosures regarding our revenues from contracts with customers and the adoption of Topic 606. Reclassifications Certain reclassifications have been made to prior period consolidated financial statements to conform to classifications used in the current period. These reclassifications had no impact on net income (loss), shareholders' equity or cash flows as previously reported. Restricted Cash and Cash Equivalents Cash and cash equivalents that are contractually restricted from operating use are classified as restricted cash and cash equivalents. On December 22, 2017, we issued $300 million aggregate principal amount of 5.00% senior unsecured notes due in 2026 (December Notes). The proceeds of the December Notes plus payments for prepaid interest and a premium for a special mandatory redemption option were deposited into escrow, where the funds remained until all the escrow release conditions were satisfied, specifically the closing of the acquisition of Silver Spring Networks, Inc. (SSNI) on January 5, 2018. We recognized the balance in escrow as restricted cash in our consolidated financial statements as of December 31, 2017. The following table provides a reconciliation of cash, cash equivalents, and restricted cash reported within the Consolidated Balance Sheets that sum to the total of the same such amounts shown in the Consolidated Statements of Cash Flows:
| Three months ended March 31
| 2018 |  | 2017
| (in thousands)
Cash and cash equivalents | $ | 143,951 |  |  | $ | 187,928 |
Current restricted cash included in other current assets | 51 |  |  | — |
Long-term restricted cash | 1,466 |  |  | — |
Total cash, cash equivalents, and restricted cash | $ | 145,468 |  |  | $ | 187,928 |
Revenue Recognition The majority of our revenues consist primarily of hardware sales, but may also include the license of software, software implementation services, cloud services and software as a service ("Saas"), project management services, installation services, consulting services, post-sale maintenance support, and extended or noncustomary warranties. We account for a contract when it has approval and commitment from both parties, the rights of the parties are identified, payment terms are identified, the contract has commercial substance, and collectability of consideration is probable. In determining whether the definition of a contract has been met, we will consider whether the arrangement creates enforceable rights and obligations, which involves evaluation of agreement terms that would allow for the customer to terminate the agreement. If the customer is able to terminate the agreement without providing further consideration to us, the agreement would not be considered to meet the definition of a contract. Many of our revenue arrangements involve multiple performance obligations consisting of hardware, meter reading system software, installation, and/or project management services. Separate contracts entered into with the same customer (or related parties of the customer) at or near the same time are accounted for as a single contract where one or more of the following criteria are met:
• | The contracts are negotiated as a package with a single commercial objective;
• | The amount of consideration to be paid in one contract depends on the price or performance of the other contract; or
• | The goods or services promised in the contracts (or some goods or services promised in each of the contracts) are a single performance obligation.
Once the contract has been defined, we evaluate whether the promises in the contract should be accounted for as more than one performance obligation. This evaluation requires significant judgment, and the decision to separate the combined or single contract into multiple performance obligations could change the amount of revenue and profit recognized in a given period. For some of our contracts, the customer contracts with us to provide a significant service of integrating, customizing or modifying goods or services in the contract in which case the goods or services would be combined into a single performance obligation. It is common that we may promise to provide multiple distinct goods or services within a contract in which case we separate the contract into more than one performance obligation. If a contract is separated into more than one performance obligation, we allocate the total transaction price to each performance obligation in an amount based on the estimated relative standalone selling prices of the promised goods or services underlying each performance obligation. If applicable, for goods or services where we have observable standalone sales, the observable standalone sales are used to determine the standalone selling price. For the majority of our goods and services, we do not have observable standalone sales. As a result, we estimate the standalone selling price using either the adjusted market assessment approach or the expected cost plus a margin approach. Approaches used to estimate the standalone selling price for a given good or service will maximize the use of observable inputs and considers several factors, including our pricing practices, costs to provide a good or service, the type of good or service, and availability of other transactional data, among others. We determine the estimated standalone selling prices of goods or services used in our allocation of arrangement consideration on an annual basis or more frequently if there is a significant change in our business or if we experience significant variances in our transaction prices. Many of our contracts with customers include variable consideration, which can include liquidated damage provisions, rebates and volume and early payment discounts. Some of our contracts with customers contain clauses for liquidated damages related to the timing of delivery or milestone accomplishments, which could become material in an event of failure to meet the contractual deadlines. At the inception of the arrangement and on an ongoing basis, we evaluate the probability and magnitude of having to pay liquidated damages. We estimate variable consideration using the expected value method, taking into consideration contract terms, historical customer behavior and historical sales. In the case of liquidated damages, we also take into consideration progress towards meeting contractual milestones, including whether milestones have not been achieved, specified rates, if applicable, stated in the contract, and history of paying liquidated damages to the customer or similar customers. Variable consideration is included in the transaction price if, in our judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur. In the normal course of business, we do not accept product returns unless the item is defective as manufactured. We establish provisions for estimated returns and warranties. In addition, we do not typically provide customers with the right to a refund. Hardware revenues are recognized at a point in time. Transfer of control is typically at the time of shipment, receipt by the customer, or, if applicable, upon receipt of customer acceptance provisions. We will recognize revenue prior to receipt of customer acceptance for hardware in cases where the customer acceptance provision is determined to be a formality. Transfer of control would not occur until receipt of customer acceptance in hardware arrangements where such provisions are subjective or where we do not have history of meeting the acceptance criteria. Perpetual software licenses are considered to be a right to use intellectual property and are recognized at a point in time. Transfer of control is considered to be at the point at which it is available to the customer to download and use or upon receipt of customer acceptance. In certain contracts, software licenses may be sold with professional services that include implementation services that include a significant service of integrating, customizing or modifying the software. In these instances, the software license is combined into single performance obligation with the implementation services and recognized over time as the implementation services are performed. Hardware and software licenses (when not combined with professional services) are typically billed when shipped and revenue recognized at a point-in-time. As a result, the timing of revenue recognition and invoicing does not have a significant impact on contract assets and liabilities. Professional services, which include implementation, project management, installation, and consulting services are recognized over time. We measure progress towards satisfying these performance obligations using input methods, most commonly based on the costs incurred in relation to the total expected costs to provide the service. We expect this method to best depict our performance in transferring control of services promised to the customer or represents a reasonable proxy for measuring progress. The estimate of expected costs to provide services requires judgment. Cost estimates take into consideration past history and the specific scope requested by the customer and are updated quarterly. We may also offer professional services on a stand-ready basis over a specified period of time, in which case revenue would be recognized ratably over the term. Invoicing of these services is commensurate with performance and occurs on a monthly basis. As such, these services do not have a significant impact on contract assets and contract liabilities. Cloud services and SaaS arrangements where customers have access to certain of our software within a cloud-based IT environment that we manage, host and support are offered to customers on a subscription basis. Revenue for the cloud services and SaaS offerings are generally recognized over time, ratably over the contact term commencing with the date the services are made available to the customer. Services, including professional services, cloud services and SaaS arrangements, are commonly billed on a monthly basis in arrears and typically result in an unbilled receivable, which is not considered a contract asset as our right to consideration is unconditional. Certain of our revenue arrangements include an extended or noncustomary warranty provisions that covers all or a portion of a customer's replacement or repair costs beyond the standard or customary warranty period. Whether or not the extended warranty is separately priced in the arrangement, such warranties are considered to be a separate good or service, and a portion of the transaction price is allocated to this extended warranty performance obligation. This revenue is recognized, ratably over the extended warranty coverage period. Hardware and software post-sale maintenance support fees are recognized over time, ratably over the life of the related service contract. Shipping and handling costs and incidental expenses billed to customers are recognized as revenue, with the associated cost charged to cost of revenues. We recognize sales, use, and value added taxes billed to our customers on a net basis. Support fees are typically billed on an annual basis, resulting in a contract liability. Payment terms with customers can vary by customer; however, amounts billed are typically payable within 30 to 90 days, depending on the destination country. We do not make a practice of offering financing as part of our contracts with customers. We incur certain incremental costs to obtain contracts with customers, primarily in the form of sales commissions. Where the amortization period is one year or less, we have elected to apply the practical expedient and recognize the related commissions expense as incurred. Otherwise, such incremental costs are capitalized and amortized over the contract period. Capitalized incremental costs are not material. New Accounting Pronouncements In February 2016, the Financial Accounting Standards Board (FASB) issued Accounting Standards Update (ASU) 2016-02, Leases (Topic 842), which requires substantially all leases be recognized by lessees on their balance sheet as a right-of-use asset and corresponding lease liability, including leases currently accounted for as operating leases. The new standard also will result in enhanced quantitative and qualitative disclosures, including significant judgments made by management, to provide greater insight into the extent of revenue and expense recognized and expected to be recognized from existing leases. The standard requires modified retrospective adoption and will be effective for annual reporting periods beginning after December 15, 2018, with early adoption permitted. We currently believe the most significant impact relates to our real estate leases and the increased financial statement disclosures, but are continuing to evaluate the effect that the updated standard will have on our consolidated results of operations, financial position, cash flows, and related financial statement disclosures. In October 2016, the FASB issued ASU 2016-16, Income Taxes: Intra-Entity Transfers of Assets Other Than Inventory (Topic 740) (ASU 2016-16), which removes the prohibition in Topic 740 against the immediate recognition of the current and deferred income tax effects of intra-entity transfers of assets other than inventory. Under ASU 2016-16, the selling entity is required to recognize a current tax expense or benefit upon transfer of the asset. Similarly, the purchasing entity is required to recognize a deferred tax asset or deferred tax liability, as well as the related deferred tax benefit or expense, upon receipt of the asset. The resulting deferred tax asset or deferred tax liability is measured by computing the difference between the tax basis of the asset in the buyer's jurisdiction and its financial reporting carrying value in the consolidated financial statements and multiplying such difference by the enacted tax rate in the buyer's jurisdiction. ASU 2016-16 is effective for fiscal years beginning after December 15, 2017 with early adoption permitted. We adopted this standard effective January 1, 2018 using a modified retrospective transition method, recognizing a $0.9 million one-time decrease to accumulated deficit. In March 2017, the FASB issued ASU 2017-07, Improving the Presentation of Net Periodic Pension Cost and Net Periodic Postretirement Benefit Cost (ASU 2017-07), which provides additional guidance on the presentation of net benefit costs in the income statement. ASU 2017-07 requires an employer disaggregate the service cost component from the other components of net benefit cost and to disclose other components outside of a subtotal of income from operations. It also allows only the service cost component of net benefit costs to be eligible for capitalization. ASU 2017-07 is effective for fiscal years beginning after December 15, 2017 with early adoption permitted. We adopted this standard on January 1, 2018 retrospectively for the presentation of the service cost component of net periodic pension cost in the statement of operations, and prospectively for the capitalization of the service cost component of net periodic pension cost. For applying the retrospective presentation requirements, we elected to utilize amounts previously disclosed in our defined benefit pension plan footnote for the prior comparative periods as the estimation basis for applying the retrospective presentation. This resulted in a reclassification of an immaterial amount of net periodic pension benefit costs from operating income to other income (expense) in all periods presented on the Consolidated Statements of Operations. In August 2017, the FASB issued ASU 2017-12, Targeted Improvements to Accounting for Hedging Activities (ASU 2017-12), which amends and simplifies existing guidance in order to allow companies to more accurately present the economic effects of risk management activities in the financial statements. This update expands and refines hedge accounting for both nonfinancial and financial risk components and aligns the recognition and presentation of the effects of the hedging instrument and the hedged item in the financial statements. Additionally, the amendments in ASU 2017-12 provide new guidance about income statement classification and eliminates the requirement to separately measure and report hedge ineffectiveness. ASU 2017-12 is effective for fiscal years beginning after December 15, 2018, with early adoption permitted. We are currently assessing the impact of adoption on our consolidated results of operations, financial position, cash flows, and related financial statement 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 The entire disclosure for all significant accounting policies of the reporting entity. + References Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration