Electronic Data Interchange

EDI is the exchange of business data in a standardized format between business computer systems.

EDI represents a fundamental change in the way companies transact business. It replaces paper-intensive functions with efficient electronic transactions and eliminates the need for printing and mailing business information. By using standard formats and languages, the computerized data can be electronically transmitted between two companies and interpreted automatically.

The process of sending data via EDI requires a series of steps on the part of the sending and receiving partners (known as Trading Partners). Once the foundation of your EDI message is defined, most of these steps will be either automated or proceduralized.

Pacific Gas and Electric Company presently utilizes Value Added Networks (VAN's) for EDI Outbound 810 billing transactions. We also have the ability to utilize EDI over the internet connectivity for EDI Outbound and Inbound 814 and 867 transactions to Energy Service Providers.

The 810 transaction set is used to provide established PG&E billing data in an electronic format to its customers. The billing data provided electronically reflects the same information that appears on a traditional paper bill and is consistent with national standards for EDI.

• 810 Checklist (PDF, 27 KB)
• Trading Partner Agreement (PDF, 179 KB)
• EDI Trading Partner Setup Form (PDF, 10 KB)
• 810 v. 4010 Bundled Service Document (PDF, 932 KB)
• 810 v. 4010 Bundled Service and Direct Access Test Samples (PDF, 399 KB)

The 820 transaction set is used to make a payment and send remittance advices. This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. PG&E's application requires that the 820 go through a financial institution.

• 820 v. 4010 Guide (PDF, 446 KB)

This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.

• 997 - Functional Acknowledgement (PDF, 150 KB)

The 248 transaction set is sent between the Utility and Energy Service Providers (ESPs) for confirming that billing charges and adjustments have posted to the customer's account.

• 248 v. 4010 Guide (PDF, 342 KB)

The 810 transaction set is used to provide established PG&E billing data in an electronic format to its customers. The billing data provided electronically reflects the same information that appears on a traditional paper bill and is consistent with national standards for EDI.

• 810 Checklist (PDF, 27 KB)
• Trading Partner Agreement (PDF, 179 KB)
• EDI Trading Partner Setup Form (PDF, 10 KB)
• 810 v. 4010 Bundled Service Document (PDF, 932 KB)
• 810 v. 4010 Bundled Service and Direct Access Test Samples (PDF, 399 KB)

The 814 transaction set or DASR is sent between the Utility and Energy Service Providers (ESPs) for purposes such as connecting a customer (i.e. Connect Request), updating a significant customer event (i.e. Update Request/Notification), or disconnecting a customer (i.e. Disconnect Request).*

• 814 Implementation Checklist (PDF, 39 KB)
• Data Exchange Server Access for EDI 867 and 814 Test Data (PDF, 11 KB)
• Downloadable Programs for Data Transfer
• 814 v. 4010 Guide (PDF, 802 KB)
• 814 v. 4010 Tutorial (PDF, 540 KB)

*An ESP that exchanges 814 EDI data with PG&E must also be able to receive 867 EDI. The 867 is used to pass the required 12 months of usage history for the customer to the ESP.

The 820 transaction set is used to make a payment and send a remittance advice. This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. PG&E's application requires that the 820 go through a financial institution.

• 820 v. 4010 Guide (PDF 446 KB)

The 824 acknowledges whether an inbound 810 transaction is accepted into our billing system or has been rejected.

• 824, Version 4010, Outbound Application Advice (PDF 398 KB)

The 867 transaction set is used to transfer meter usage data. Where the ESP is the MDMA the 867 will be sent to PG&E as in inbound file. Where PG&E is the MDMA the 867 will be sent as an outbound file to the ESP. Refer to the implementation checklists below for both the 867 inbound and outbound requirements.

• 867 Inbound Implementation Checklist (PDF, 37 KB)
• 867 Outbound Implementation Checklist (PDF, 18 KB)
• Data Exchange Server Access for EDI 867 and 814 Test Data (PDF, 11 KB)
• Downloadable Programs for Data Transfer
• 867 v. 4010 Guide (PDF, 450 KB)
• 867 v. 4010 Tutorial (PDF, 426 KB)

This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.

• 997 - Functional Acknowledgement (PDF, 150 KB)

• Your company needs the EDI implementation conventions and ANSI ASC X12 compliant EDI translation software. EDI uses a standard electronic format approved by the American National Standards Institute (ANSI) and the Utility Industry Group (UIG). This ensures that electronic data can be exchanged easily and correctly.
• Have access to a Value Added Network (VAN) for EDI 810 invoices and EDI 820 Payment/Remittance Orders. A VAN for EDI 810 invoices and EDI 820 Payment/Remittance Orders is a third party service provider that permits many different trading partners to communicate through a central clearing house.
• The EDI 814 and EDI 867 require you to have an internet browser and utilize HTTP PUT and HTTP GET. PG&E will establish a directory and password on our server.

Direct Access Frequently Asked Questions

• Have access to a Value Added Network (VAN). A VAN is a third party service provider that permits many different trading partners to communicate through a central clearing house.