IMPLEMENTATION GUIDE EDI TRANSACTION SET 810 VERSION 3070 UDC CONSOLIDATED BILLING

Transcription

1 IMPLEMENTATION GUIDE EDI TRANSACTION SET 810 VERSION 3070 UDC CONSOLIDATED BILLING Southern California Edison May 2007 Version 1.0

2 Table of Contents I. Introduction II. III. IV. Overview of the UDC Consolidated Billing Process UDC Consolidated Billing Compliance Requirements Compliance Testing Timeline V. EDI Transaction Set 810 version SCE Mapping Guide VI. VII. VIII. IX. 810 Transaction Mapping Structure Explanation - Domestic 810 Transaction Mapping Structure Explanation - Commercial EDI Transaction Set 824 version SCE Mapping Guide 824 Transaction Mapping Structure Explanation X. UDC Consolidated Billing Bill Sample Southern California Edison 1 May 2007

3 I. Introduction This implementation package contains information useful for Electric Service Providers (ESPs) in understanding the implementation and testing processes for Electronic Data Interchange (EDI) Transaction Set 810 version 3070 for Utility Distribution Company (UDC) Consolidated Billing. SCE intends to use standard EDI transactions developed and maintained by the Accredited Standards Committee X12 (ASC X12). This committee and its standard transaction formats are sanctioned and approved by the American National Standards Institute (ANSI). ASC X12 transactions have been adopted for EDI by the Utility Industry Group (UIG), an industry action group working in the interest of electric and combination utilities, their customers, and suppliers to improve the methods of exchanging business information through EDI. It is expected that ESPs will transmit inbound bill-ready data electronically to SCE by utilizing Transaction Set 810 version The 810 Mapping Guide used for this implementation has been developed by SCE and it meets ANSI X12 standards. The 810 Mapping Guide may be found in Chapter V of this implementation guide. Additional UIG EDI information and guidelines may be found at Southern California Edison 2 May 2007

4 II. Overview of the UDC Consolidated Billing Process ESPs participating in Direct Access (DA) may choose to participate in UDC Consolidated Billing. Under UDC Consolidated Billing, the ESPs method for transmitting information to SCE concerning ESP bill-ready charges must be done via EDI Transaction Set 810 version In return, Transaction Set 824 (Application Advice Outbound) version 3070, will be sent by SCE to the ESP as a response to UDC Consolidated Billing data transmitted by the ESP to SCE via EDI Transaction Set 810. The 824 transaction indicates an Acceptance or Rejection, and the error code and description of what field(s) of the bill data is incorrect. A Breakdown of the UDC Consolidated Billing Cycle Step 1 Retrieving Usage Information The first step in the billing cycle is for both SCE and the ESP to retrieve a single customer s usage information for the billing cycle. This information can be obtained by the ESP from the Meter Data Management Agent (MDMA). Additional information with regards to the MDMA may be obtained from the Meter Data Management Agent web page on SCE s website at: Step 2 Calculating Charges In Step 2, both the ESP and SCE must calculate their respective charges. The ESP and SCE have a set of specific charges each must calculate based on the same usage data for a single customer in a given billing period. Step 3 Consolidating the Bill After calculating its charges, the ESP must prepare and send the charges to SCE via EDI Transaction Set 810 version 3070 by 5:00 p.m. of the second business day, following the MDMA posting. SCE will consolidate the information from the ESP and its own charges to create a single bill to present to the end-use customer. The UDC Consolidated Bill will have the following format: Page 1 - Bill Summary: A summary of SCE and ESP charges Page 2 - SCE Bill Detail: A breakdown of all SCE charges Page 3 - ESP Bill Detail: A breakdown of ESP charges Step 4 Sending the Bill For Mandatory Statement plans, SCE allows a two-day window to wait for the ESP charges. Accounts that are Date Plan billed on a scheduled date each month will not Southern California Edison 3 May 2007

5 wait the two days if the scheduled date falls within the two-day window. In addition, accounts that have this plan can possibly bill beyond two days. Step 5 Collecting and Transferring Payments SCE will collect payment from customers, and forward funds associated with the ESP charges to the ESP. Funds received from a customer will be allocated first to the SCE charges for which delinquency may result in a disconnection of service, and then any balance will be prorated between the ESP and other SCE non-disconnectable charges. Payments and payment information will be sent to the ESP via a Value-Added Bank (VAB). This entity can arrange to send payment in a variety of ways to the ESP, usually within one to two business days. Southern California Edison 4 May 2007

6 UDC Consolidated Billing Cycle Process Flow Business Day 0 Both the ESP and SCE will retrieve the same usage information for the enduse customer from the MDMA Business Day 1 SCE calculates UDC charges, including applicable city tax ESP calculates energy charge, state tax, and applicable city tax Business Day 2 ESP sends its calculated charges to SCE via EDI. Charges must be received by 5:00 p.m. SCE creates a single bill, including SCE and ESP charges and required inserts SCE Billing Cycle Schedule SCE sends bills to customers + 1 or 2 Business Days after Receipt of Customer Payment SCE remits payment to ESP through Value-Added Bank (VAB) Southern California Edison 5 May 2007

7 III. UDC Consolidated Billing Compliance Requirements An ESP must meet SCE compliance requirements to participate in UDC Consolidated Billing. These compliance requirements are designed to ensure that the ESP and SCE are able to exchange and interpret each other s data. Practice testing will be available for any EDI capable ESP. The format of the data is illustrated in the 810 (inbound) and 824 (outbound) mapping structures included in this guide. The test data will consist of similar data as found in the mapping structures. Under UDC Consolidated Billing, the ESP will send bill-ready data via EDI to SCE in a test environment. SCE will use this data to consolidate and prepare an end-use customer bill. This bill will be sent to the ESP for review. The ESP must complete compliance testing requirements at least three business days prior to any scheduled ESP switch dates. For a testing timeline please refer to the Compliance Testing Timeline (section IV) of this implementation guide. Test transmissions for practice testing can be arranged by contacting SCE s Electronic Communications Coordinator: Phone: (626) Fax: (626) ESPSUPT@SCE.COM The SCE Electronic Communications Coordinator will function as the liaison between ESPs and SCE s Corporate EDI Group. Specifically, the Electronic Communications Coordinator will assist ESPs in understanding the requirements and protocols associated with establishing EDI with SCE and compile the necessary electronic transmission control information for EDI communications. Southern California Edison 6 May 2007

8 IV. Compliance Testing Timeline Timeline: The following testing timeline has been established among all areas of responsibility in regards to UDC Consolidated Billing. Day Zero The Electronic Communications Coordinator will receive a test request from the ESP and initiate bill testing. Day 1-2 The Electronic Communications Coordinator will provide the ESP with test data and will wait for the data to be submitted by the ESP. Upon receipt of the test data, the timeline begins as day 3 of 5. Day 3-5 SCE will process the test data and create EDI outbound response data for each test account which will be sent to the ESP. SCE will create and review three print bills based on the data provided by the ESP. If the EDI file format is non-compliant and fails translator processing the test will be considered a failure. The Electronic Communications Coordinator will notify the ESP of the test results. Southern California Edison 7 May 2007

9 V. EDI Transaction Set 810 version 3070 SCE Mapping Guide It is expected that ESPs will transmit inbound bill-ready data electronically to SCE by utilizing Transaction Set 810 version The 810 Mapping Guide used for this implementation has been developed by SCE and it meets ANSI X12 standards. Additional UIG EDI information and guidelines may be found at The 810 Mapping Guide contains the processing necessary for the exchange of electronic bill-ready data between ESPs and SCE. Contact SCE s Electronic Communications Coordinator should you have any questions. Southern California Edison 8 May 2007

10 ESP/UDC Consolidated Billing Conventions Mapping Guide Invoice Inbound ANSI X12 Version 3070 Southern California Edison 9 May 2007

11 810 EDI CUSTOMER BILLING CONVENTIONS Introduction: Functional Group ID=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided. Notes: GENERAL INVOICING NOTATIONS: This document contains the processing necessary for an exchange of Consolidated Billing data between Electric Service Providers (ESPs) and SCE as a Utility Distribution Company (UDC). The exchange is limited to SCE receiving (inbound) an 810 from an ESP and SCE sending (outbound) an 824 to Accept or Reject. Contact the SCE Electronic Communications Coordinator should you have any questions. Heading: Pos. No. Seg. ID Name Req. Des. Max. Use Must Use 010 ST Transaction Set Header M 1 Must Use 020 BIG Beginning Segment for Invoice M 1 Must Use 050 REF Reference Numbers M DTM Date/Time/Period M 10 Loop Repeat Notes and Comments Detail: Pos. No. Seg. ID Name Req. Des. Max. Use Must Use 010 IT1 Baseline Item Data M 1 Loop Repeat Notes and Comments Summary: Pos. No. Seg. ID Name Req. Des. Max. Use Must Use 010 TDS Total Monetary Value Summary M 1 Must Use 080 SE Transaction Set Trailer M 1 Loop Repeat Notes and Comments Southern California Edison 10 May 2007

12 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number. Syntax Notes: Semantic Notes: 1) Comments: The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g. 810 selects the Invoice Transaction Set). Data Element Summary Ref. Description Data Element Name Attributes ST Transaction Set Identifier Code M ID 3/3 The Transaction Set Identifier Code uniquely identifies a transaction set. This field describes the type of EDI record being sent. It should be populated with the value of 810 for UDC Consolidated Billing data sent from ESPs to SCE. This field will not display on the UDC Consolidated Bill. ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. This field will not display on the UDC Consolidated Bill. This number must match the value in SE02. Southern California Edison 11 May 2007

13 Segment: BIG Beginning Segment for Invoice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: Semantic Notes: Comments: 1) To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates. BIG07 is used only to further define the type of invoice when needed. The BIG segment is used to uniquely identify the transaction. Data Element Summary Ref. Description Data Element Name Attributes BIG Invoice Date M DT 6/ 6 Invoice Issue Date. This field will not display on the UDC Consolidated Bill. This date field should be populated with the run date in the form YYMMDD, where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. BIG02 76 Invoice Number M AN 1/22 Record ID uniquely identifying 810 record. This field will not display on the UDC Concolidated Bill. SCE recommends that the Record ID is composed of the run date + an ascending sequence number. The first part of the Record ID will be the run date and will consist of 8 characters. The run date will be in the form CCYYMMDD, where CC represents the century, YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. The second part of the Record ID will be an 8 digit number. It will be assigned as an ascending sequence number. (e.g ) BIG Date O DT 6/6 This field is not used. This field will not display on the UDC Consolidated Bill. BIG Purchase Order Number M AN 1/22 Purpose code used to identify the type of processing that must be performed on the inbound 810 record. This field will not display on the UDC Consolidated Bill. Currently, the only valid purpose code is OK. Southern California Edison 12 May 2007

14 Segment: REF Reference Number Position: 050 Loop: IT1 Level: Heading Usage: Mandatory Max Use: 12 Purpose: To specify identifying numbers. Syntax Notes: 1) At least one REF02 or REF03 is required. Semantic Notes: Comments: Data Element Summary Originating Company ID (Mandatory) - 1st REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record. This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier 8M indicates that the Reference Number will contain the Originating Company ID. This field should be populated with the value 8M. REF Reference Number O AN 1/30 The Originating Company ID. This field will not display on the UDC Consolidated Bill. The Originating Company ID field should be populated with the ESP's Dun & Bradstreet. Specifically, for the EDI 810 record sent from ESPs to SCE for UDC Consolidated Billing, this value should be populated with the ESP's Dun & Bradstreet. The relationship between the ESP and SCE's service account will be validated. REF Description O AN 1/80 The Originating Company Ticker ID. This field will not display on the UDC Consolidated Bill. The Originating Company Ticker ID will be provided by SCE. The size of the value entered may be 2, 3, or 4 characters in length. Data Element Summary Originating Company's Customer Account Number (Mandatory) - 2nd REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record. This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier 5B indicates that the Reference Number will contain the Originating Company's Customer Account Number. This value will not be validated. REF Reference Number O AN 1/30 The Originating Company's Customer Account Number. This field will not display on the UDC Consolidated Bill. This is the value of the ESP's customer account number and it should be populated. It will be inserted in the EDI 824 record which is sent from SCE to the ESP to accept or reject the 810 record sent from the ESP to SCE. REF Description O AN 1/80 This field is not used. Southern California Edison 13 May 2007

15 Data Element Summary Receiving Company ID (Mandatory) - 3rd REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record. This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier 8N indicates that the Reference Number will contain the Receiving Company ID. This field should be populated with the value 8N. REF Reference Number O AN 1/30 The Receiving Company ID. This field will not display on the UDC Consolidated Bill. The Receiving Company ID field should be populated with SCE's Dun & Bradstreet. Specifically, this field should be populated with a value of REF Description O AN 1/80 The Receiving Company Ticker ID. This field will not display on the UDC Consolidated Bill. SCE's Company Ticker ID is SCE. This field should be populated with a value of SCE. Data Element Summary Receiving Company's Customer Account Number (Mandatory) - 4th REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record. This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier 11 indicates that the Reference Number will contain the Receiving Company's Customer Account Number. This field should be populated with the value 11. REF Reference Number O AN 1/30 The Receiving Company's Customer Account Number. This field will appear on the UDC Consolidated Bill. The Receiving Company's Customer Account Number will be SCE's service account number for the selected account and it should be populated. This value will be validated. REF Description O AN 1/80 This field is not used. Data Element Summary Comment (Optional) - 5th through 10th REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier 2G indicates that the Reference Number will contain a Bill Message. This field should be populated with the value 2G. REF Reference Number O AN 1/30 This field is not used. Southern California Edison 14 May 2007

16 REF Description O AN 1/80 Bill Message. This field will appear on the UDC Consolidated Bill. Bill Messages may contain up to 64 characters. Any characters in excess of this number will not appear on the bill. Bill Message text must conform to the UDC-ESP service agreements. Text will appear on the bill as it is received from the ESP. Note that the Comment segment may be repeated 6 times. Specifically, up to 6 Bill Messages maybe sent from the ESP to the UDC for UDC Consolidated Billing. Data Element Summary Meter Number (Optional) - 11th REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record. This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier MG indicates that the Reference Number will contain a Meter Number. This field should be populated with the value MG. REF Reference Number O AN 1/30 Meter Number. This field will not display on the UDC Consolidated Bill. Currently, the Meter Number will not appear on the ESP detailed statement of charges on the UDC Consolidated Bill. Usage information will be displayed within the UDC detailed statement portion of the bill. The Meter Number may be sent in the form of XXX-XXXXXX. (e.g. XYZ ) REF Description O AN 1/80 This field is not used. Data Element Summary Change Meter Number (Optional) - 12th REF Segment Ref. Description Data Element Name Attributes REF Reference Number Qualifier M ID 2/3 Code indicating the type of Reference Record. This field will not display on the UDC Consolidated Bill. The Reference Number Qualifier 46 indicates that the Reference Number will contain a Change Meter Number. This field should be populated with the value 46. REF Reference Number O AN 1/30 The Change Meter Number. This field represents the meter number of the old meter in the event that a meter change occurred during the billing period. This field will not display on the UDC Consolidated Bill. Currently, the Change Meter Number will not appear on the ESP detailed statement of charges on the UDC Consolidated Bill. Usage information will be displayed within the UDC detailed statement portion of the bill. The Change Meter Number be sent in the form of XXX-XXXXXX. (e.g. XYZ ) REF Description O AN 1/80 This field is not used. Southern California Edison 15 May 2007

17 Segment: DTM Date/Time/Period Position: 140 Loop: Level: Heading Usage: Mandatory Max Use: 10 Purpose: To specify pertinent dates and times. Syntax Notes: 1) At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Data Element Summary Postmark Date (Mandatory) - 1st DTM Segment Ref. Description Data Element Name Attributes DTM Date/Time Qualifier M ID 3/3 The Date/Time Qualifier specifies the type of date or time values that will be contained within the segment. This field will not display on the UDC Consolidated Bill. The Date/Time Qualifier 108 indicates that the Date Segment will contain the Timestamp. Thus, this field should be populated with the value 108. DTM Date O DT 6/ 6 Timestamp Date. This field will not display on the UDC Consolidated Bill. The Timestamp Date should be populated in the form YYMMDD where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. This value should be populated based on a system timestamp. DTM Time O TM 4/ 8 Timestamp Time. This field will not display on the UDC Consolidated Bill. The Timestamp Time should be populated in the form HHMM where HH represents the hour of the timestamp (based on a 24-hour clock) and MM represents the minutes of the hour. This value should be populated based on a system timestamp. DTM Time Code O ID 2/2 Null field. DTM Century O N0 2/ 2 Timestamp Century. This field will not display on the UDC Consolidated Bill. The Timestamp Century should be populated in the form CC where CC represents the century of the timestamp. This field is necessary in order to maintain year compliance. This value should be populated based on a system timestamp. Southern California Edison 16 May 2007

18 Data Element Summary Bill Period Start Date (Mandatory) - 2nd DTM Segment Ref. Description Data Element Name Attributes DTM Date/Time Qualifier M ID 3/3 The Date/Time Qualifier specifies the type of date or time values that will be contained within the segment. This field will not display on the UDC Consolidated Bill. The Date/Time Qualifier 150 indicates that the Date segment will contain the Bill Period Start Date. This field should be populated with the value 150. DTM Date O DT 6/ 6 Bill Period Start Date. This field will appear on the UDC Consolidated Bill. The Bill Period Start Date should be populated in the from YYMMDD where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. This value should be populated based on the first day of the billing period which is represented in the 810 record sent from the ESP to SCE. Validation will be performed on this field to verify that the Bill Period Start Date is prior to the Bill Period End Date. DTM Time O TM 4/ 8 Null field. DTM Time Code O ID 2/2 Null field. DTM Century O N0 2/2 Bill Period Start Date Century. Currently, this field will not display on the UDC Consolidated Bill. The Bill Period Start Date Century should be populated in the form CC where CC represents the century of the timestamp. This field is necessary in order to perform date validations mentioned above. Data Element Summary Bill Period End Date (Mandatory) - 3rd DTM Segment Ref. Description Data Element Name Attributes DTM Date/Time Qualifier M ID 3/3 The Date/Time Qualifier specifies the type of date or time values that will be contained within the segment. This field will not display on the UDC Consolidated Bill. The Date/Time Qualifier 151 indicates that the Date segment will contain the Bill Period End Date. This field should be populated with the value 151. DTM Date O DT 6/ 6 Bill Period End Date. This field will appear on the UDC Consolidated Bill. The Bill Period End Date should be populated in the form YYMMDD where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. This value should be populated based on the last day of the billing period which is represented in the 810 record sent from the ESP to SCE. Validation will be performed on this field to verify that the Bill Period End Date is after the Bill Period Start Date. DTM Time O TM 4/ 8 Null field. DTM Time Code O ID 2/2 Null field. Southern California Edison 17 May 2007

19 DTM Century O N0 2/2 Bill Period End Date Century. Currently, this field will not display on the UDC Consolidated Bill. The Bill Period End Date Century should be populated in the form CC where CC represents the century of the timestamp. This field is necessary in order to perform date validations mentioned above. Data Element Summary Bill Period Meter Start Date (Optional) - 4th DTM Segment Ref. Description Data Element Name Attributes DTM Date/Time Qualifier M ID 3/3 The Date/Time Qualifier specifies the type of date or time values that will be contained within the segment. This field will not display on the UDC Consolidated Bill. The Date/Time Qualifier 196 indicates that the Date segment will contain the Bill Period Meter Start Date. This field should be populated with the value 196. DTM Date O DT 6/ 6 Bill Period Meter Start Date. This field will not display on the UDC Consolidated Bill. Currently, the Bill Period Meter Start Date will not appear on the ESP Detailed Statement of Charges on the UDC Consolidated Bill. Usage information will be displayed within the UDC Detailed Statement of Charges. The Bill Period Meter Start Date should be populated in the form YYMMDD where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. DTM Time O TM 4/ 8 Null field. DTM Time Code O ID 2/2 Null field. DTM Century O N0 2/ 2 Bill Period Meter Start Date Century. This field will not display on the UDC Consolidated Bill. Currently, the Bill Period Meter Start Date Century will not appear on the ESP Detailed Statement of Charges within the UDC Consolidated Bill. Usage information will be displayed within the UDC Detailed Statement of Charges. The Bill Period Meter Start Date Century should be populated in the form CC where CC represents the century of the timestamp. Data Element Summary Bill Period Meter End Date (Optional) - 5th DTM Segment Ref. Description Data Element Name Attributes DTM Date/Time Qualifier M ID 3/3 The Date/Time Qualifier specifies the type of date or time values that will be contained within the segment. This field will not display on the UDC Consolidated Bill. The Date/Time Qualifier 197 indicates that the Date segment will contain the Bill Period Meter End Date. This field should be populated with the value 197. Southern California Edison 18 May 2007

20 DTM Date O DT 6/ 6 Bill Period Meter End Date. This field will not display on the UDC Consolidated Bill. Currently, the Bill Period Meter End Date will not appear on the ESP Detailed Statement of Charges on the UDC Consolidated Bill. Usage information will be displayed within the UDC Detailed Statement of Charges. The Bill Period Meter End Date should be populated in the form YYMMDD where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. DTM Time O TM 4/ 8 Null field. DTM Time Code O ID 2/2 Null field. DTM Century O N0 2/ 2 Bill Period Meter End Date Century. This field will not display on the UDC Consolidated Bill. Currently, the Bill Period Meter End Date Century will not appear on the ESP Detailed Statement of Charges within the UDC Consolidated Bill. Usage information will be displayed within the UDC Detailed Statement of Charges. The Bill Period Meter Start Date Century should be populated in the form CC where CC represents the century of the timestamp. Note that up to two sets of 196/197 segments may be sent from ESP's to SCE. The additional set of records represents the dates of the Bill Period Meter Start and End Dates for Change Meters. That is, the additional 196/197 segments will represent the Bill Period Meter Start and End Dates for the old meter that was removed. Note that these fields will not be displayed on the ESP Detail Statement of the UDC Consolidated Bill. They will be generated by SCE and displayed in the SCE Detail Statement. Thus, like the Bill Period Meter Start and End Dates, the Bill Period Change Meter Start and End Dates will be an optional entry. Southern California Edison 19 May 2007

21 Segment: IT1 Baseline Item Data Position: 010 Loop: IT1 Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify the basic and most frequently used line item data for the invoice and released transactions. Syntax Notes: 1) If IT106 is present, then IT107 is required. 2) If IT108 is present, then IT109 is required. 3) If IT110 is present, then IT111 is required. 4) If IT112 is present, then IT113 is required. 5) If IT114 is present, then IT115 is required. 6) If IT116 is present, then IT117 is required. 7) If IT118 is present, then IT119 is required. 8) If IT120 is present, then IT121 is required. 9) If IT122 is present, then IT123 is required. 10) If IT124 is present, then IT1257 is required. Semantic Notes: 1) IT101 is the purchase order line item identification. Comments: 1) Element 235/234 combinations should be interpreted to include products and/or services. See the Data Dictionary for a complete list of IDs. 2) IT106 through IT125 provides for ten (10) different product/service IDs for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Data Element Summary Usage Data (Optional) Ref. Description Data Element Name Attributes IT Assigned Identification O AN 1/20 The Assigned Identification indicates the type of data that will be contained within the transaction set. This field will not display on the UDC Consolidated Bill. For Usage Data, the Assigned Identification should be populated with a value of USAGE. IT Quantity Invoiced O R 1/10 Usage Quantity. This field will not display on the UDC Consolidated Bill. The Usage Quantity sent from the ESP will not display on the ESP's Detailed Statement of Charges within the UDC Consolidated Bill. Usage data will appear in SCE's Detailed Statement of Charges. SCE allows for a 2 decimal place. Southern California Edison 20 May 2007

22 IT Unit or Basis for Measurement Code O ID 2/2 Usage Description Code. This field will not display on the UDC Consolidated Bill. The Usage Code sent from the ESP will not display on the ESP's Detailed Statement of Charges within the UDC Consolidated Bill. Usage data will appear in SCE's Detailed Statement of Charges. The codes that should be used to indicate the usage types are as follow: DAY(S) use DA KWH use KH KW use K1 KVARH use K3 KVARH use K4 KVAR use K5 GAL use GA THERM(S) use TD HP use HJ LAMP(S) use EA UNIT(S) use UN All others use EA IT Unit Price O R 1/17 Compliance field. For compliance reasons, this field should be populated with 0. Note that up to 20 entries of Usage Data may be received. Also note that no Usage Data sent from ESPs to SCE will be displayed on the UDC Consolidated Bill. The data may be contained within SCE's Detailed Statement of Charges, but usage information will not be displayed on the ESP Detailed Statement of Charges within the UDC Consolidated Bill. Billing Component Data (Mandatory) Ref. Description Data Element Name Attributes IT Assigned Identification O AN 1/20 The Assigned Identification indicates the type of data that will be contained within the transaction set. This field will not display on the UDC Consolidated Bill. For Billing Component Data, the Assigned Identification should be populated with a value of COMPONENT. IT Quantity Invoiced O R 1/10 Billing Component Dollar Amount. This field will appear on the UDC Consolidated Bill as a charge amount in a charge line item within the ESP Detailed Statement of Charges. Billing Component Dollar Amounts should be populated. The sum of all Billing Component Dollar Amounts for a selected service account will be validated against the Total Amount Due to ESP (please refer to the TDS01 element description) to ensure that the two amounts are identical. SCE allows for a 2 decimal place. (e.g. A dollar amount of 1 is 1.00) IT Unit or Basis for Measurement Code O ID 2/2 Compliance Field. The field will not display on the UDC Consolidated Bill. The value that should be entered for the Compliance Field is ZZ. Southern California Edison 21 May 2007

23 IT Unit Price O R 1/17 Compliance field. For compliance reasons, this field should be populated with 0. IT Basis of Unit Price Code O ID 2/2 Null field. IT Product/Service ID Qualifier O ID 2/2 Pair Classification Field. This field will not display on the UDC Consolidated Bill. For compliance reasons, this field should be populated with a value of CG. This code stands for Commodity Grouping. IT Product/Service ID O AN 1/48 Charge Type. This field will appear on the ESP Detailed Statement of Charges of the UDC Consolidated Bill in the form of a text associated to the charge amount entered in IT102 of this segment. The Charge Type value will be limited to one of the three following codes. The text that will appear in place of the charge type is listed with the charge type below: Charge Type Line Item Description on UDC Consolidated SPENERGY SPCITYTX SPOTHER Energy Charge City Tax Other Charge The Charge Type received will be validated to ensure that it is one of the predefined charge types. IT Product/Service ID Qualifier O ID 2/2 Pair Classification Field. This field will not display on the UDC Consolidated Bill. For compliance reasons, this field should be populated with a value of C3. IT Product/Service ID O AN 1/48 Arbitrary Text Associated to Charge Type. The Arbitrary Text Associated to a Billing Component will be displayed in the Message Section of the ESP Detailed Statement of Charges of the UDC Consolidated Bill. The first 22 characters of the Arbitrary Text will be displayed within the Bill Message section. Any characters after the first 22 will be truncated. This text will be displayed in message form as it is received from the ESP. In addition, if arbitrary text is entered to further describe the Billing Component, then a number will be displayed adjacent to the line item description to refer to the Arbitrary Text Message. See UDC Consolidated Billing bill samples for examples. Note that multiple entries of the IT1 Billing Component Data may be sent within one 810 record for a given service account. Specifically, the IT1 Billing Component segment may contain up to 30 entries of Billing Component Data. Southern California Edison 22 May 2007

24 Segment: TDS Total Monetary Value Summary Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 To specify the total invoice discounts and amounts. Purpose: Syntax Notes: Semantic Notes: Comments: 1) TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01. Ref. Description Data Element Data Element Summary Name Attributes TDS Total Invoice Amount M N2 1/15 Total Amount Due to ESP. This field will appear on the UDC Consolidated Bill. The Total Amount Due to the ESP will be validated to ensure that the sum of the Billing Component Dollar Amounts is identical to the Total Amount Due to the ESP. TDS Total Invoice Amount M N2 1/15 Previous Amount Due to ESP. This field will not display on the UDC Consolidated Bill. This field is optional. The total amount due will not be displayed as a separate line item within the bill. However, it may be displayed as a Bill Message. See the Comment segment in the REF section. Southern California Edison 23 May 2007

25 Segment: SE Transaction Set Trailer Position: 080 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: Semantic Notes: Comments: 1) To indicate the end of the transaction set and provide the count of the transmitted segments [including the beginning (ST) and ending (SE) segment]. SE is the last segment of each transaction set. Data Element Summary Ref. Description Data Element Name Attributes SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments. This field will not display on the UDC Consolidated Bill. This value is system generated. SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. This field will not display on the UDC Consolidated Bill. The Transaction Set Control Number must be the same as the ST02 value. Southern California Edison 24 May 2007

26 VI. 810 Transaction Mapping Structure Explanation - Domestic The following 810 transaction mapping structure explanation provides assistance in the submission of billing charges from the ESP to SCE. Each reference description and data element is followed by an explanation. Generic examples are used throughout the listings that can be cross-referenced with the Domestic UDC Consolidated Billing bill sample provided in Chapter X. Transaction Mapping Structure Explanation Header Area ST*810* ^ ST01 = ST02 = 810 is the Transaction Set is the Transaction Set Control Number BIG*061109* **OK^ BIG01 = is the Run Date in the format yymmdd BIG02 = The Record ID is the Run Date ( ) + the Ascending Sequence Number ( ) BIG04 = The Purpose Code (OK) REF*8M*ESP123456*ABC^ REF01 = 8M indicates the Originating Company ID will be in REF02 REF02 = The Originating Company's ID - Dun & Bradstreet (ESP123456) REF03 = The Originating Company's Ticker Symbol (ABC) REF*5B* ^ REF01 = REF02 = REF*8N* *SCE^ REF01 = 8N indicates the Receiving Company ID will be in REF02 REF02 = The Receiving Company's ID - Dun & Bradstreet ( ) REF03 = The Receiving Company's Ticker Symbol (SCE) REF*11* ^ REF01 = REF02 = 5B indicates the Originating Company's Customer Account Number The Originating Company s Customer Account Number ( ) 11 indicates the Receiving Company's Service Account Number will be in REF02 The Receiving Company's Service Account Number ( ) REF*2G**For ABC Provider Billing Inquiries Call REF# RE ^ REF01 = REF03 = 2G indicates Originating Company's Bill Message will be in REF03 The Originating Company's Bill Message (Bill Message) REF*MG*XYZ ^ REF01 = MG indicates the Meter Number will be in REF02 REF02 = The Meter Number (XYZ ) Southern California Edison 25 May 2007

27 DTM*108*061109*1630**20^ DTM*150*061007***20^ DTM*151*061108***20^ DTM*196*061007***20^ DTM*197*061108***20^ DTM01 = 108 indicates a Timestamp DTM02 = is the Timestamp's date in the format yymmdd DTM03 = 1630 is the Timestamp's time in the format hhmm DTM05 = 20 is the Timestamp's century in the format cc DTM01 = 150 indicates Bill Period Start Date DTM02 = The Bill Period Start Date's date (061007) in the format yymmdd DTM03 = The Bill Period Start Date's century (20) in the format cc DTM01 = 151 indicates Bill Period End Date DTM02 = The Bill Period End Date's date (061108) in the format yymmdd DTM03 = The Bill Period End Date's century (20) in the format cc DTM01 = 196 indicates Bill Period Meter Start Date DTM02 = The Bill Period Meter Start Date's date (061007) in the format yymmdd DTM03 = The Bill Period Meter Start Date's century (20) in the format cc DTM01 = 197 indicates Bill Period Meter End Date DTM02 = The Bill Period Meter End Date's date (061108) in the format yymmdd DTM03 = The Bill Period Meter End Date's century (20) in the format cc Detail Area IT1*USAGE* *KH*0^ IT101 = USAGE indicates usage IT102 = The USAGE Pair's Quantity ( ) IT103 = The USAGE Pair's Description (KH) DAY(S) = DA KWH = KH KW = K1 KVARH = K3 KVA = K4 KVAR = K5 GAL = GA THERM(S) = TD HP = HJ LAMP(S) = EA UNIT(S) = UN All Others = EA IT104 = 0 is used for compliance Southern California Edison 26 May 2007

28 IT1*COMPONENT*75.00*ZZ*0**CG*SPENERGY* IT101 = COMPONENT indicates Billing Component Data C3*ESP ENERGY CHARGE^ IT102 = The COMPONENT Pair's Dollar Amount (75.00) IT103 = ZZ is used for compliance IT104 = 0 is used for compliance IT106 = CG indicates Commodity Grouping IT107 = The COMPONENT Pair's Protocol Text (SPENERGY) Valid values are: SPENERGY SPCITYTX SPOTHER IT108 = C3 indicates Classification IT109 = COMPONENT Pair's Arbitrary Text (ESP Energy Charge) Note: Only the first 22 characters will be displayed on the bill IT1*COMPONENT*00.45*ZZ*0**CG*SPOTHER* IT101 = COMPONENT indicates Billing Component Data C3*ESP STATE TAX^ IT102 = The COMPONENT Pair's Dollar Amount (00.45) IT103 = ZZ is used for compliance IT104 = 0 is used for compliance IT106 = CG indicates Commodity Grouping IT107 = The COMPONENT Pair's Protocol Text (SPOTHER) Valid values are: SPENERGY SPCITYTX SPOTHER IT108 = C3 indicates Classification IT109 = COMPONENT Pair's Arbitrary Text (ESP State Tax) Note: Only the first 22 characters will be displayed on the bill Summary Area TDS*75.45*0.00^ TDS01 = The Bill Total (75.45) TDS02 = The Previous Balance (0.00) SE*18* ^ SE01 = Number of included segments including ST and SE segments (18) SE02 = is the Transaction Set Control Number (Note: Same as ST02) Southern California Edison 27 May 2007

29 VI. 810 Transaction Mapping Structure Explanation - Commercial The following 810 transaction mapping structure explanation provides assistance in the submission of billing charges from the ESP to SCE. Each reference description and data element is followed by an explanation. Generic examples are used throughout the listings that can be cross-referenced with the Commercial UDC Consolidated Billing bill sample provided in Chapter X. Transaction Mapping Structure Explanation (Commercial) Header Area ST*810* ^ ST01 = ST02 = 810 is the Transaction Set is the Transaction Set Control Number BIG*061109* **OK^ BIG01 = is the Run Date in the format yymmdd BIG02 = The Record ID is the Run Date ( ) + the Ascending Sequence Number ( ) BIG04 = The Purpose Code (OK) REF*8M*ESP123456*ABC^ REF01 = 8M indicates the Originating Company ID will be in REF02 REF02 = The Originating Company's ID - Dun & Bradstreet (ESP123456) REF03 = The Originating Company's Ticker Symbol (ABC) REF*5B* ^ REF01 = REF02 = REF*8N* *SCE^ REF01 = 8N indicates the Receiving Company ID will be in REF02 REF02 = The Receiving Company's ID - Dun & Bradstreet ( ) REF03 = The Receiving Company's Ticker Symbol (SCE) REF*11* ^ REF01 = REF02 = 5B indicates the Originating Company's Customer Account Number The Originating Company s Customer Account Number ( ) 11 indicates the Receiving Company's Service Account Number will be in REF02 The Receiving Company's Service Account Number ( ) REF*2G**For ABC Provider Billing Inquiries Call REF# RE ^ REF01 = 2G indicates Originating Company's Bill Message will be in REF03 REF03 = The Originating Company's Bill Message (Bill Message) REF*MG*XYZ ^ REF01 = MG indicates the Meter Number will be in REF02 REF02 = The Meter Number (XYZ ) Southern California Edison 28 May 2007

30 DTM*108*061109*1630**20^ DTM*150*061007***20^ DTM*151*061108***20^ DTM*196*061007***20^ DTM*197*061108***20^ DTM01 = 108 indicates a Timestamp DTM02 = is the Timestamp's date in the format yymmdd DTM03 = 1630 is the Timestamp's time in the format hhmm DTM05 = 20 is the Timestamp's century in the format cc DTM01 = 150 indicates Bill Period Start Date DTM02 = The Bill Period Start Date's date (061007) in the format yymmdd DTM03 = The Bill Period Start Date's century (20) in the format cc DTM01 = 151 indicates Bill Period End Date DTM02 = The Bill Period End Date's date (061108) in the format yymmdd DTM03 = The Bill Period End Date's century (20) in the format cc DTM01 = 196 indicates Bill Period Meter Start Date DTM02 = The Bill Period Meter Start Date's date (061007) in the format yymmdd DTM03 = The Bill Period Meter Start Date's century (20) in the format cc DTM01 = 197 indicates Bill Period Meter End Date DTM02 = The Bill Period Meter End Date's date (061108) in the format yymmdd DTM03 = The Bill Period Meter End Date's century (20) in the format cc Detail Area IT1*USAGE* *KH*0^ IT101 = USAGE indicates usage IT102 = The USAGE Pair's Quantity ( ) IT103 = The USAGE Pair's Description (KH) DAY(S) = DA KWH = KH KW = K1 KVARH = K3 KVA = K4 KVAR = K5 GAL = GA THERM(S) = TD HP = HJ LAMP(S) = EA UNIT(S) = UN All Others = EA IT104 = 0 is used for compliance Southern California Edison 29 May 2007

31 IT1*COMPONENT* *ZZ*0**CG*SPENERGY* IT101 = COMPONENT indicates Billing Component Data C3*ESP ENERGY CHARGE^ IT102 = The COMPONENT Pair's Dollar Amount ( ) IT103 = ZZ is used for compliance IT104 = 0 is used for compliance IT106 = CG indicates Commodity Grouping IT107 = The COMPONENT Pair's Protocol Text (SPENERGY) Valid values are: SPENERGY SPCITYTX SPOTHER IT108 = C3 indicates Classification IT109 = COMPONENT Pair's Arbitrary Text (ESP Energy Charge) Note: Only the first 22 characters will be displayed on the bill IT1*COMPONENT*15.86*ZZ*0**CG*SPOTHER* IT101 = COMPONENT indicates Billing Component Data C3*ESP STATE TAX^ IT102 = The COMPONENT Pair's Dollar Amount (15.86) IT103 = ZZ is used for compliance IT104 = 0 is used for compliance IT106 = CG indicates Commodity Grouping IT107 = The COMPONENT Pair's Protocol Text (SPOTHER) Valid values are: SPENERGY SPCITYTX SPOTHER IT108 = C3 indicates Classification IT109 = COMPONENT Pair's Arbitrary Text (ESP State Tax) Note: Only the first 22 characters will be displayed on the bill Summary Area TDS* *0.00^ TDS01 = The Bill Total ( ) TDS02 = The Previous Balance (0.00) SE*18* ^ SE01 = Number of included segments including ST and SE segments (18) SE02 = is the Transaction Set Control Number (Note: Same as ST02) Southern California Edison 30 May 2007

32 VII. EDI Transaction Set 824 version 3070 SCE Mapping Guide An EDI Transaction Set 824 version 3070, will be sent by SCE to the ESP as a response to the inbound bill-ready data transmitted by the ESP to SCE via EDI Transaction Set 810. The 824 transaction indicates an Acceptance or Rejection, and the error code and description of what field(s) of the account data is incorrect. The 824 Mapping Guide used for this implementation has been developed by SCE and it meets ANSI X12 standards. Additional UIG EDI information and guidelines may be found at SCE will use the 824 Application Advice version 3070 for all outbound bill-ready data responses. Contact SCE s Electronic Communications Coordinator should you have any questions. Southern California Edison 31 May 2007

33 UDC/ESP Application Advice Conventions Mapping Guide Application Advice Inbound/Outbound ANSI X12 Version 3070 Southern California Edison 32 May 2007

34 824 EDI APPLICATION ADVICE CONVENTIONS Functional Group ID = AG Introduction: This Mapping Guide contains the format and establishes the data contents of the Invoice Transaction Set (824) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for the acceptance or rejection of any transaction set. Notes: GENERAL INVOICING NOTATIONS: This document contains the processing necessary for an exchange of Application Advice (824) in response to the Consolidated Billing data (810) between SCE as a Utility Distribution Company (UDC) and Electric Service Provider (ESP). The exchange is limited to SCE receiving (inbound) an 810 from an ESP and SCE sending (outbound) an 824 to Accept or Reject. In addition, SCE will send the ESP an 810 outbound and will expect to receive an 824 inbound. Contact the SCE Electronic Communications Coordinator should you have any questions. Heading: Pos. No. Seg. ID Name Req. Des. Max. Use Must Use 010 ST Transaction Set Header M 1 Must Use 020 BIG Beginning Segment for Invoice M 1 Loop Repeat Notes and Comments Detail: Pos. No. Seg. ID Name Req. Des. Max. Use Must Use 010 OT1 Original Transaction ID M 1 Must Use 020 REF Reference Numbers M 12 Loop Repeat Notes and Comments Summary: Pos. No. Seg. ID Name Req. Des. Max. Use Must Use 080 SE Transaction Set Trailer M 1 Loop Repeat Notes and Comments Southern California Edison 33 May 2007

35 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number. Syntax Notes: Semantic Notes: 1) Comments: The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g. 824 selects the Invoice Transaction Set). Data Element Summary Ref. Description Data Element Name Attributes ST Transaction Set Identifier Code M ID 3/3 The Transaction Set Identifier Code uniquely identifies a Transaction Set. This field describes the type of EDI record being sent. It should be populated with the value of 824 for the Accept/Reject record sent to the ESP. The Transaction Set Identifier Code will have a value of 824 for Accept/Reject messages. ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. This number will match the value in SE02. Southern California Edison 34 May 2007

36 Segment: BGN Beginning Segment Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates. Syntax Notes: Semantic Notes: Comments: 1) BGN07 is used only to further define the type of invoice when needed. Data Element Summary Ref. Description Data Element Name Attributes BGN Transaction Purpose M ID 2/2 Transaction Purpose Code The Transaction Purpose field will be populated with a value of 11. This value indicates that the 824 record is a response. BGN Reference Identification M AN 1/30 Record ID uniquely identifying the 824 transaction. This value will be assigned by the sender. SCE recommends that the Record ID is composed of the Run Date + an Ascending Sequence Number. The first part of the Record ID will be the Run Date and will consist of 8 characters. The Run Date will be in the format CCYYMMDD, where CC represents the century, YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. It will be assigned as an Ascending Sequence Number. (e.g ) BGN Date M DT 6/6 Run Date. This value will be assigned by the sender. The Run Date will be in the format YYMMDD, where YY represents the last two digits of the year, MM represents the month, and DD represents the day of the month. (e.g ) Southern California Edison 35 May 2007