XML 24 R14.htm IDEA: XBRL DOCUMENT v3.19.2
REVENUE RECOGNITION
6 Months Ended
Jun. 30, 2019
Revenue from Contract with Customer [Abstract]  
REVENUE RECOGNITION REVENUE RECOGNITION
Revenue Recognition
On January 1, 2018, the Company adopted Accounting Standard Update (ASU) 2014-09, “Revenue from Contracts with Customers (ASC 606),” using the modified retrospective method. The Company elected to evaluate all contracts at the date of initial application. There was no impact to the opening balance of retained earnings as a result of the adoption.
The following table presents a disaggregation of the Company’s midstream services revenue by service type.
 
 
Three Months Ended June 30,
 
Six Months Ended June 30,
 
 
2019
 
2018
 
2019
 
2018
 
 
(In thousands)
MIDSTREAM SERVICES REVENUE — AFFILIATE:
 
 
 
 
 
 
 
 
Gas gathering
 
$
2,697

 
$
1,406

 
$
6,310

 
$
2,015

Gas processing
 
18,395

 
7,802

 
43,679

 
15,507

Transmission
 
2,977

 
3,300

 
7,831

 
7,085

NGL transmission
 
70

 
9

 
165

 
9

 
 
$
24,139

 
$
12,517

 
$
57,985

 
$
24,616


The Company currently generates all its revenues by providing the above services, pursuant to separate midstream service agreements entered into with Apache. These midstream service agreements have no minimum volume commitments or firm transportation commitments, instead they are underpinned by acreage dedications covering Alpine High. Pursuant to these agreements, Altus Midstream is obligated to perform services on all volumes produced from the dedicated acreage, so long as Apache has the right to market such gas. In exchange for the above services and in accordance with the terms of the midstream service agreements, the Company charges a fixed fee on a per unit basis.
These performance obligations are satisfied over time as Apache simultaneously receives and consumes the benefits of the services performed. Service revenues are recognized when the right to invoice has been met, since the amount that the Company has the right to invoice (based upon the fixed fee and throughput volumes) corresponds directly with the value received by Apache.
Pursuant to the terms of the Contribution Agreement, all accounts receivable from Apache (including revenue receivable) on or prior to September 30, 2018, are for the account of Apache. No cash settlement of such balances was contemplated prior to September 30, 2018 and as such, revenue receivables generated prior to this date were treated as a reduction to additional paid-in capital within equity. Following the Business Combination, service revenue invoices are provided to Apache on a monthly basis, pursuant to the terms of the COMA. Amounts owing to Apache under the terms of the COMA are reduced by the amounts of these invoices. Net cash settlement is performed on a monthly basis. The net amount of receivable from Apache as of June 30, 2019 relating to revenue earned and invoiced was $7.8 million. Additionally, the Company recognized services revenue earned but not yet invoiced to Apache of $9.0 million as of June 30, 2019.