Significant Accounting Policies (Policies)

3 Months Ended

Mar. 31, 2019

Accounting Policies [Abstract]

Basis of Presentation

Basis of Presentation

The accompanying consolidated financial statements are prepared in accordance with the instructions to Form 10-Q, are unaudited, and do not include all the information and disclosures required by GAAP for complete financial statements. All adjustments that, in the opinion of management, are necessary for a fair presentation of the results of operations for the interim periods have been made and are of a recurring nature unless otherwise disclosed herein. The results of operations for such interim periods are not necessarily indicative of results of operations for a full year. These consolidated financial statements should be read in conjunction with the consolidated financial statements and accompanying notes included in our Annual Report on Form 10-K for the year endedDecember 31, 2018. All significant intercompany balances and transactions have been eliminated in consolidation.

Revenue Recognition

Revenue Recognition

Minimum Volume Commitments and Firm Transportation Contracts

Certain of our gathering and processing agreements provide for quarterly or annual MVCs. Under these agreements, our customers or suppliers agree to ship and/or process a minimum volume of product on our systems over an agreed time period. If a customer or supplier under such an agreement fails to meet its MVC for a specified period, the customer is obligated to pay a contractually-determined fee based upon the shortfall between actual product volumes and the MVC for that period. Some of these agreements also contain make-up right provisions that allow a customer or supplier to utilize gathering or processing fees in excess of the MVC in subsequent periods to offset shortfall amounts in previous periods. We record revenue under MVC contracts during periods of shortfall when it is known that the customer cannot, or will not, make up the deficiency in subsequent periods. Deficiency fee revenue is included in midstream services revenue.

For our firm transportation contracts, we transport commodities owned by others for a stated monthly fee for a specified monthly quantity with an additional fee based on actual volumes. We include transportation fees from firm transportation contracts in our midstream services revenue.

The following table summarizes the contractually committed fees that we expect to recognize in our consolidated statements of operations, in either revenue or reductions to cost of sales, from MVC and firm transportation contractual provisions. All amounts in the table below are determined using the contractually-stated MVC or firm transportation volumes specified for each period multiplied by the relevant deficiency or reservation fee. Actual amounts could differ due to the timing of revenue recognition or reductions to cost of sales resulting from make-up right provisions included in our agreements, as well as due to nonpayment or nonperformance by our customers. These fees do not represent the shortfall amounts we expect to collect under our MVC contracts, as we generally do not expect volume shortfalls to equal the full amount of the contractual MVCs during these periods. For example, for the three months endedMarch 31, 2019, we had contractual commitments of $38.5 millionunder our MVC contracts and recorded$3.8 millionof revenue due to volume shortfalls.

Accounting Standards to be Adopted in Future Periods and Adopted Accounting Standards

Accounting Standards to be Adopted in Future Periods

On August 29, 2018, the FASB issued ASU 2018-15, Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract (“ASU 2018-15”), which amends ASC 350-40, Internal-Use Software (“ASC 350-40”) to address a customer’s accounting for implementation costs incurred in a cloud computing arrangement that is a service contract. ASU 2018-15 aligns the accounting for costs incurred to implement a cloud computing arrangement that is a service arrangement with the guidance on capitalizing costs associated with developing or obtaining internal-use software. Specifically, the ASU amends ASC 350-40 to include in its scope implementation costs of a cloud computing arrangement that is a service contract and clarifies that a customer should apply ASC 350-40 to determine which implementation costs should be capitalized in a cloud computing arrangement that is considered a service contract. To the extent costs incurred in a cloud computing arrangement are capitalizable, the corresponding amortization will be included in “Operating expenses” or “General and administrative” in the consolidated statement of operations, rather than “Depreciation and amortization.” We are currently evaluating the impact of ASU 2018-15 on our consolidated financial statements and will adopt ASU 2018-15 effective January 1, 2020.

(d) Adopted Accounting Standards

Effective January 1, 2019, we adopted ASC 842, Leases, using the modified retrospective approach whereby we recognized leases on our consolidated balance sheet by recording a right-of-use asset and lease liability. We applied certain practical expedients that were allowed in the adoption of ASC 842, including not reassessing existing contracts for lease arrangements, not reassessing existing lease classification, not recording a right-of-use asset or lease liability for leases of twelve months or less, and not separating lease and non-lease components of a lease arrangement. In connection with the adoption of ASC 842 in January 2019, we recorded a lease liability of $96.5 million, a right-of-use asset of $73.6 million, and a reduction of$22.6 millionin other liabilities previously recorded related to lease incentives.For additional information about our adoption of ASC 842, refer to “Note 5—Leases.”