Transaction / Document Title/
Purpose / Document Flow /

Scenario(s) Used

650_01 / Service Order Request /

CR to TDSP

/ I
To initiate the original Service Order, Cancel or Change (Update) Request.
650_02 / Service Order Complete, Complete Unexecutable, Reject Response, or Notification of Permit Required /

TDSP to CR

/ I
To send a Completed, Complete Unexecutable, Reject Response or Notification of Permit Required response to the original Service Order.
650_04 / Suspension of Delivery Service Notification or Cancellation /

TDSP to CR

/ K
To notify the CR of a suspension of delivery service or to cancel the notification of suspension of delivery service.
650_05 / Suspension of Delivery Service Reject Response /

CR to TDSP

/ K
To notify the TDSP of a reject of a Suspension of Delivery Service notification or cancellation.
810_02 / TDSP to CR Invoice /

TDSP to CR

/ J
An invoice for monthly wires charges, Delivery Charges, Discretionary Service charges and any Service Order charges for the current billing period. This transaction set will be paired with an 867_03 (Monthly Usage) to trigger the Customer billing process. From the TDSP to the CR, is an invoice for Late Payment Charges.
810_03 / Muni/Co-op Invoice /

CR to MCTDSP

/ J
An invoice for monthly energy charges, discretionary charges, and service charges for the current billing period. For use in the Muni/Coop market only. This transaction set will be preceded by an 867_03 (Monthly Usage) to trigger the Customer billing process.
814_PC / Maintain Customer Information Request /

CR to TDSP

/ H
To provide TDSPs with the information needed to verify CR customer's identity (name, address, and home phone number) for a particular Point of Delivery served by CR, and to continually provide TDSP updates of such information. For use by CRs choosing Option 2 or 3 or those participating in the Muni/Coop market only.
814_PD / Maintain Customer Information Response /

TDSP to CR

/

H

To acknowledge receipt of the 814_PC Maintain Customer Information Request.
814_01 / Enrollment Request /

New CR to ERCOT

/ A, E
To begin the Customer enrollment process for a switch.
814_02 / Enrollment Reject Response /

ERCOT to New CR

/ A, E
To reject an enrollment request on the basis of incomplete or invalid information. This is a conditional transaction and will only be used as a negative response. If an 814_02 Enrollment Reject Response is not received from ERCOT, the CR will receive a transaction 814_05 (Premise Information and Enrollment Response).
814_03 / Switch CR Notification Request /

ERCOT to TDSP

/ A, C, D, E
To pass information from the 814_01, 814_10, 814_16, or 814_24 (move-out where CSA exists) to the TDSP, with the addition of two data elements: (1) the TDSP associated with this Premise and (2) the available switch date.
Transaction / Document Title/
Purpose / Document Flow /

Scenario(s) Used

814_04 / Switch CR Notification Response /

TDSP to ERCOT

/ A, C, D, E
To provide the scheduled switch date that the TDSP has calculated and pertinent Customer and Premise information. The historical usage, if requested, will be sent using the transaction 867_02.
814_05 / Premise Information and Enrollment Response /

ERCOT to New CR

/ A, C, D, E
A pass through of the TDSP’s 814_04 information. This transaction will complete the New CR’s enrollment request.
814_06 / Drop Due to Switch Request / ERCOT to Current CR / A, C, D, E
To notify a Current CR of a drop.
814_07 / Drop Due to Switch Response / Current CR to ERCOT / A, C, D, E
To accept or reject a drop. If rejected, this transaction will trigger the CR objection process, as allowed by PUCT rules.
814_08 /

Cancel Switch Request

/ See Below / A, B, C, E
  • ERCOT to Current CR, TDSP, and New CR - To reinstate the Customer to the prior CR of record when the Switch, Move-In or Move-Out has been canceled by the Customer.
  • Current CR to ERCOT - To cancel a Move-In or Move-Out request.
  • New CR to ERCOT - To cancel a pending switch.
  • ERCOT to Current CR and TDSP - To cancel a Drop to AREP. Only ERCOT can cancel a Drop to AREP.
  • ERCOT to Current CR - To reinstate the Customer when the Switch or Move-In that caused a forced Move-Out/Drop Due to Switch has been canceled by the end use Customer.

814_09 / Cancel Switch Response / See Below / A, B, C, E
  • TDSP, Current CR, or New CR, to ERCOT - To accept or reject the 814_08 cancel switch request and return the Premise to the prior CR of record.
  • ERCOT to Current CR - To respond to the Customer cancel of a Move-Out request.

814_10 / Drop to AREP Request / Current CR to ERCOT / E
To drop the Customer to the Affiliate Retail Electric Provider (AREP).
814_11 / Drop to AREP Response / ERCOT to Current CR / E
To acknowledge receipt of the 814_10 or reject the Current CR’s request to drop the Customer to the Affiliate Retail Electric Provider (AREP).
814_12 / Date Change Request / See Below / B, C, D
  • New CR to ERCOT - To request a date change to the original Move-In request.
  • ERCOT to Current CR - To pass through the date change on the Move-In request from the New CR.
  • ERCOT to CSA CR - To notify of a date change on the Move-Out only.
  • ERCOT to TDSP - To notify of a Move-In or Move-Out date.
  • Current CR to ERCOT - To request a date change to the original Move-Out request.

Transaction / Document Title/
Purpose / Document Flow /

Scenario(s) Used

814_13 / Date Change Response / See Below / B, C, D
  • ERCOT to New CR - To acknowledge the requested date change to the original Move-In date on the 814_12 Date Change Request.
  • Current CR to ERCOT - To acknowledge the requested date change to the original Move-In date on the 814_12 Date Change Request.
  • CSA CR to ERCOT - To acknowledge the requested date change to the original Move-Out date on the 814_12 Date Change Request.
  • TDSP to ERCOT -To acknowledge the requested date change to the original Move-In or Move-Out date on the 814_12 Date Change Request.
  • ERCOT to Current CR - To acknowledge the requested date change to the original move out date on the 814_12 Date Change Request.

814_14 / Drop to AREP Enrollment Request /

ERCOT to AREP

/ E
To notify the Affiliate Retail Electric Provider (AREP) of pending Customer enrollment information.
814_15 / Drop to AREP Enrollment Response /

AREP to ERCOT

/ E
To acknowledge the pending Customer enrollment in response to the 814_14 Drop to the Affiliate Retail Electric Provider (AREP) Enrollment Request.
814_16 / Move-In Request /

New CR to ERCOT

/ C, D
To begin the Customer enrollment process for a Move-In.
814_17 / Move-In Reject Response /

ERCOT to New CR

/ C, D
To reject an enrollment request on the basis of incomplete or invalid information. This is a conditional transaction and will only be used as a negative response. If an 814_17 Move-In Reject Response is not received from ERCOT, the CR will receive a transaction 814_05 Premise Information and Enrollment Response.
814_18 / Establish/Delete Continuous Service Agreement (CSA) Request / See Below / D
  • New CSA CR to ERCOT - To establish the landlords new CSA CR in the registration system.
  • Current CSA CR to ERCOT - To remove an existing CSA CR from the registration system.
  • ERCOT to Current CSA CR - To notify of deletion of CSA.

814_19 / Establish/Delete Continuous Service Agreement (CSA) Response / See Below / D
  • ERCOT to the New CSA CR - To acknowledge receipt of the 814_18 Establish/Delete CSA CR Request enrolling the New CSA CR in the registration system.
  • ERCOT to Current CSA CR - To acknowledge the receipt of the 814_18 Establish/Delete CSA CR Request deleting the Current CR from the registration system.
  • Current CSA CR to ERCOT - To acknowledge the receipt of the 814_18 Establish/Delete CSA CR Request notifying the Current CSA CR that the landlord has selected a New CSA CR.

Transaction / Document Title/
Purpose / Document Flow /

Scenario(s) Used

814_20 / Create/Maintain/Retire ESI ID Request / See Below / F, I
  • TDSP to ERCOT - To initially populate the registration system for conversion/opt-in.
  • TDSP to ERCOT - To communicate the addition of a new ESI ID, changes to information associated with an existing ESI ID, or retirement of an existing ESI ID.
  • ERCOT to Current CR, New CR, or CSA CR - To pass through the TDSP’s change of an existing ESI ID.

814_21 / Create/Maintain/Retire ESI ID Response / See Below / F, I
  • ERCOT to TDSP - To acknowledge receipt of the 814_20 Create/Maintain/Retire ESI ID Request.
  • Current CR, New CR or CSA CR to ERCOT - To acknowledge receipt of the 814_20 Create/Maintain/Retire ESI ID Request.

814_22 / Continuous Service Agreement (CSA) CR Move In Request /

ERCOT to CSA CR

/ D
This transaction set, from ERCOT to CSA CR, is used to start CSA service of the ESI ID.
814_23 / Continuous Service Agreement (CSA) CR Move In Response /

CSA CR to ERCOT

/ D
This transaction set, from the CSA CR to ERCOT is used to acknowledge the receipt of the 814_22 CSA Move-In Request.
814_24 /

Move-Out Request

/ See Below / B, C, D
  • Current CR to ERCOT - To notify of a Customer’s Move-Out request.
  • ERCOT to TDSP - To pass through the Customer’s Move-Out request.

814_25 / Move-Out Response / See Below / B, C, D
  • TDSP to ERCOT - To acknowledge the receipt of the 814_24 Move-Out Request.
  • ERCOT to Current CR - To acknowledge the receipt of the 814_24 Move-Out Request.

814_26 / Ad-Hoc Historical Usage Request / See Below / G
  • CR to ERCOT - To request the historical usage for an ESI ID.
  • ERCOT to TDSP - To pass through the CR’s 814_26 Ad-hoc Historical Usage Request.

814_27 / Ad-Hoc Historical Usage Response / See Below / G
  • TDSP to ERCOT - To respond to the 814_26 Ad-hoc Historical Usage Request.
  • ERCOT to CR - To respond to the 814_26 Ad-hoc Historical Usage Request. It is a pass through of the TDSP’s response.

814_28 / Completed Unexecutable or Permit Required / See Below / B, C
  • TDSP to ERCOT - On a move out, to notify the Current CR that the Move-Out was Completed Unexecutable.
  • ERCOT to Current CR - To pass through the TDSP’s notification that the Move-Out was Completed Unexecutable.
  • TDSP to ERCOT – On a move in, to notify the CR that the work was Completed Unexecutable, or that a permit is required.
  • ERCOT to New CR - To notify the CR that the work was Completed Unexecutable, or that a permit is required. A pass through of the TDSP’s 814_28.
  • ERCOT to Current CR (if the Move-In was into an energized account) - To notify the CR that the work was Completed Unexecutable, or that a permit is required. A pass through of the TDSP’s 814_28.

814_29 / Response to Completed Unexecutable or Permit Required / See Below / B, C
  • Current CR to ERCOT – On a move out, to notify the TDSP that the CR received the 814_28, or to Reject the 814_28 based on invalid data. The CR is not allowed to Reject the 814_28 for any other reason.
  • New CR to ERCOT – On a move in, to notify the TDSP that the CR received the 814_28, or to Reject the 814_28 based on invalid data. The CR is not allowed to Reject the 814_28 for any other reason.
  • ERCOT to TDSP - To notify the TDSP that the CR received the 814_28, or to Reject the 814_28 based on invalid data. The CR is not allowed to Reject the 814_28 for any other reason. A pass through of the CR’s 814_29.
  • ERCOT to Current CR (for a Move-In on an energized account) - To notify the Current CR that the New CR received the 814_28, or to Reject the 814_28 based on invalid data. The CR is not allowed to Reject the 814_28 for any other reason.

820_02 / Remittance Advice / CR to TDSP / J
To notify the TDSP of payment details related to a specific invoice if the remittance detail is separate from the payment. If payment and remittance travel together through a financial institution, this implementation guide can be used as a baseline discussion with your financial institution. All “must use” fields in this Implementation Guide (820_02) must be forwarded to the Financial Institution.
820_03 / Muni/Co-Op Remittance Advice / MCTDSP to CR / J
To notify the CR of payment details related to a specific CR Customer Account Number / invoice if the remittance detail is separate from the payment. If payment and remittance travel together through a financial institution, this implementation guide can be used as a baseline discussion with your financial institution. All “must use” fields in this Implementation Guide (820_03) must be forwarded to the Financial Institution.
824 / Application Advice / See Below / J
  • CR to TDSP - To reject the 810 Invoice sent by the TDSP for Non-bypassable Charges (NBC), Discretionary Service Charges (DSC) and Construction Services (CS).
  • MC TDSP to CR (Muni/Coop only) - To reject the 810 Invoice sent by the CR.
  • ERCOT to TDSP - To reject the 867 Usage sent by the TDSP.
  • CR to ERCOT - To reject the 867 Usage sent by the ERCOT.

867_02 / Historical Usage / See Below / A, C, E, G
  • TDSP to ERCOT - To report historical usage.
  • ERCOT to CR - To report TDSP’s 867_02 Historical Usage.

867_03 / Monthly Usage / See Below / A, B, C, D, E, J
  • TDSP to ERCOT - To report monthly usage.
  • ERCOT to CR - To report TDSP’s 867_03 Monthly Usage.
  • ERCOT to TDSP or CR - To report usage for ERCOT Polled Services (EPS)

867_04 / Initial Meter Read Notification / See Below / A, C, D, E
  • TDSP to ERCOT - To report the initial read associated with a Switch and/or a Move-In.
  • ERCOT to CR - To report the initial read associated with a Switch and/or a Move-In.

Transaction / Document Title/
Purpose / Document Flow /

Scenario(s) Used

997 / Functional Acknowledgement / Receiver to Sender / All
To acknowledge the receipt of the originating transaction and indicate whether the transaction passed ANSI X12 validation. This acknowledgement does not imply that the originating transaction passed Texas SET validation.

TX SET v1.5Revised 9/27/02

- 1 -