Midwestern Gas Transmission Company

Third Revised Volume No. 1

Effective Date: 07/01/2003, Docket: RP03-400-000, Status: Effective

Second Revised Sheet No. 234 Second Revised Sheet No. 234 : Effective

Superseding: First Revised Sheet No. 234

GENERAL TERMS AND CONDITIONS

5. INVOICING (Continued)

5.3 Separate Invoices

Company may render separate invoices for demand charges, for commodity charges,

for cash-out charges, and for other charges.

5.4 Format and Content of Invoices

Subject to regulatory and/or contractual consideration for standardizing

billing units on invoices, Company shall use Dekatherms only on invoices to be

consistent with standards proposed for nominations. [3.3.3/v1.0]

Unless otherwise agreed, transportation invoices shall state the net billing

rate, rather than the maximum discount Tariff rate and the discount amount.

[3.3.4/v1.0]

Company shall differentiate between sales, transportation and storage

transactions through charge codes. Sales, transportation and storage invoices

shall use the same electronic format. [3.3.5/v1.0]

Transactions at pooling points shall not be consolidated for billing purposes.

[3.3.6/v1.0]

Transfer imbalances shall be clearly identified as separate charge types.

[3.3.7/v1.0]

The statement of account is separate from the invoice as a transaction type.

[3.3.20/v1.0]

Invoices shall be based on actuals (if available) or best available data.

Quantities at points where OBAs exist shall be invoiced based on scheduled

quantities. [3.3.9/v1.0]

Required invoice backup data shall accompany or precede the invoice.

[3.3.10/v1.0]

Information provided with invoices shall be consistent with information

previously provided by the billing party, as updated for changes for

settlement. [3.3.11/v1.0]

All statements shall be standardized to the same level of detail. The specific

minimum level of detail on invoice, remittance and statement of account shall

be guided by the development of the data elements. [3.3.12/v1.0]

Regarding inadequate detail supporting documentation, supporting documentation

shall be provided upon request, with timing of supporting documentation to

follow the timing of the flowing gas transactions. [3.3.13/v1.0]

Electronic invoicing functions shall use common codes as identified by the

NAESB WGQ Common Codes Task Force. [3.3.1/1.0]