Every document the Texas retail market speaks in.
Texas SET is the EDI standard the ERCOT retail market runs on. Every enrollment, meter read, delivery invoice and service order between a retailer, ERCOT and a wires company is one of these documents.
The inventory is not large, but it is unevenly distributed: the 814 family alone carries most of the market's business logic, while several families are a single document. That shape is worth internalising early, because it tells you where the complexity actually lives.
Three properties matter more than people expect when you first read the standard. Routing says whether a document travels directly between two market participants or passes through ERCOT — which determines who can reject it, and where it disappears when something goes wrong. Direction is written from the retailer's point of view, and a handful of documents are market-internal: they never reach you, but they decide what does. Pairing is the request/response relationship, and it is what lets a stream of files be read as a conversation rather than a log.
Read this first
Four things the standard does not say loudly enough.
A 997 is not an acceptance
The functional acknowledgement confirms that a file parsed as valid X12. It says nothing about whether the transaction was accepted in business terms — that comes back separately, and a rejection at that level arrives as an 824.
The initial read sets the start date, not the acceptance
An 814_05 tells you the enrollment was accepted and when it is scheduled. The date service actually began is established by the 867_04 initial meter read. Treating the scheduled date as the real one is a recurring source of billing disputes.
Rejections come in two different shapes
A switch rejected by ERCOT's front-end returns an 814_02 and never reaches the wires company. A move-in rejected the same way returns an 814_17. Neither is the same as the TDSP later reporting that the work cannot be executed, which is an 814_28.
A loss notification is a relationship event
The 814_06 tells a losing retailer it is losing the ESI ID. It is not the final bill — final usage arrives separately as the final form of the 867_03, which is what closes out the billing period.
3 documents
650Service orders & outages
Discretionary field and meter work: disconnects, reconnects, meter exchanges, out-of-cycle reads, switch-hold actions and outage notifications.
Service Order Request
Request discretionary field/service work — disconnect/reconnect, meter work, out-of-cycle reads, switch-hold actions, lighting, and technical/environmental work.
- Process
- Service orders
- Role
- Request
- Routing
- Point to point
- Pairs with
- 650_02
Service Order Response
Acknowledge, schedule, complete, reject, or report an unexecutable result for a 650_01 service order.
- Process
- Service orders
- Role
- Response
- Routing
- Point to point
- Pairs with
- 650_01
Planned or Unplanned Outage Notification
Notify the CR of planned or unplanned outage information (separate from Option 1 T-series traffic).
- Process
- Outages
- Role
- Notification
- Routing
- Point to point
- Pairs with
- —
2 documents
810Invoices
Delivery-charge invoicing between the TDSP and the retailer, including the reverse MOU/EC direction.
TDSP Invoice
Invoice a CR for delivery-service and discretionary/non-discretionary TDSP charges.
- Process
- Billing
- Role
- Invoice
- Routing
- Point to point
- Pairs with
- 820_02
MOU/EC TDSP Invoice
Send the MOU/EC consolidated-billing invoice from the CR to the MOU/EC TDSP (reverse of the normal 810_02 flow).
- Process
- MOU/EC billing
- Role
- Invoice
- Routing
- Point to point
- Pairs with
- 820_03
27 documents
814Enrollment & ESI ID
The largest family by far. Switches, move-ins, move-outs, cancels, date changes, CSAs, mass transition, and the ESI ID attribute maintenance that underpins all of them.
Maintain Customer Information Request
Request maintenance of customer/contact information without changing the REP-of-record relationship.
- Process
- Customer maintenance
- Role
- Request
- Routing
- Point to point
- Pairs with
- 814_PD
Maintain Customer Information Response
Respond to an 814_PC customer-information maintenance request.
- Process
- Customer maintenance
- Role
- Response
- Routing
- Point to point
- Pairs with
- 814_PC
Switch Request
Request a change of REP of Record for an existing customer/ESI ID. ERCOT may reject with 814_02 or forward an 814_03 to the TDSP.
- Process
- Switch
- Role
- Initiating request
- Routing
- ERCOT routed
- Pairs with
- 814_05
Switch Reject Response
Return an ERCOT front-end/business-rule rejection of a switch request. The switch does not progress to the TDSP.
- Process
- Switch
- Role
- Reject response
- Routing
- ERCOT routed
- Pairs with
- 814_01
Enrollment Notification Request
Tell the TDSP to establish/change an enrollment relationship for a switch, move-in, CSA, acquisition, or mass-transition process.
- Process
- Enrollment
- Role
- Market request
- Routing
- ERCOT routed
- Pairs with
- 814_04
Enrollment Notification Response
Return TDSP scheduling, acceptance, rejection, premise attributes, and enrollment status to ERCOT.
- Process
- Enrollment
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_03
CR Enrollment Notification Response
Notify the gaining CR of the enrollment result and TDSP-provided premise/scheduling attributes. Actual start is set by 867_04.
- Process
- Enrollment
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_04
Loss Notification
Notify the current/losing CR that it is losing the ESI ID relationship (a relationship event; final usage follows in 867_03F).
- Process
- Enrollment loss
- Role
- Notification
- Routing
- ERCOT routed
- Pairs with
- —
Cancel Request
Cancel a pending eligible market transaction such as a move-in, switch, or move-out.
- Process
- Enrollment changes
- Role
- Request/relay
- Routing
- ERCOT routed
- Pairs with
- 814_09
Cancel Response
Return the TDSP/ERCOT result of a cancel request.
- Process
- Enrollment changes
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_08
Drop Response
Notify a CR of the drop-side result in acquisition-transfer or mass-transition processing.
- Process
- Mass transition / acquisition
- Role
- Notification/response
- Routing
- ERCOT routed
- Pairs with
- 814_14
Date Change Request
Request a date change for an eligible pending move-in, switch, move-out, or related enrollment transaction.
- Process
- Enrollment changes
- Role
- Request/relay
- Routing
- ERCOT routed
- Pairs with
- 814_13
Date Change Response
Return the result of a date-change request.
- Process
- Enrollment changes
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_12
Drop Enrollment Request
Assign/drop enrollment to a POLR or designated CR during mass-transition/acquisition processing (not a normal move-out).
- Process
- Mass transition / acquisition
- Role
- ERCOT-initiated request
- Routing
- ERCOT routed
- Pairs with
- 814_11
Move In Request
Request service/enrollment in a customer's name at a new or existing premise. ERCOT may reject with 814_17 or send an 814_03 to the TDSP.
- Process
- Move-in
- Role
- Initiating request
- Routing
- ERCOT routed
- Pairs with
- 814_05
Move In Reject Response
Return an ERCOT front-end/business-rule rejection of a move-in request (reject-only).
- Process
- Move-in
- Role
- Reject response
- Routing
- ERCOT routed
- Pairs with
- 814_16
Establish/Delete CSA Request
Establish or delete a Continuous Service Agreement.
- Process
- Continuous Service Agreement
- Role
- Request/relay
- Routing
- ERCOT routed
- Pairs with
- 814_19
Establish/Delete CSA Response
Return the result of a CSA establish/delete request.
- Process
- Continuous Service Agreement
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_18
ESI ID Maintenance Request
Publish ESI ID, premise, meter, service, switch-hold, or other maintained attributes from the TDSP through ERCOT to the CR.
- Process
- ESI ID maintenance
- Role
- Notification/request
- Routing
- ERCOT routed
- Pairs with
- 814_21
ESI ID Maintenance Response
Return ERCOT's response to an ESI ID maintenance request (usually not delivered to the CR).
- Process
- ESI ID maintenance
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_20
CSA CR Move In Request
Notify/enroll the CSA CR when a customer moves out and service rolls to the CSA holder.
- Process
- Continuous Service Agreement
- Role
- ERCOT-initiated enrollment
- Routing
- ERCOT routed
- Pairs with
- —
Move Out Request
Request termination of the current customer's enrollment/service relationship.
- Process
- Move-out
- Role
- Initiating request/relay
- Routing
- ERCOT routed
- Pairs with
- 814_25
Move Out Response
Return acceptance, scheduling, completion, or rejection of a move-out request. Final end date/usage set by 867_03F.
- Process
- Move-out
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_24
Historical Usage Request
Request historical usage for an ESI ID (the actual data is delivered in 867_02).
- Process
- Historical usage
- Role
- Request/relay
- Routing
- ERCOT routed
- Pairs with
- 814_27
Historical Usage Response
Return the status/result of a historical-usage request (not the usage payload itself — consume the 867_02).
- Process
- Historical usage
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_26
Complete Unexecutable or Permit Required
Report a permit-required condition or that requested work/enrollment cannot be executed.
- Process
- Enrollment exception
- Role
- Exception notification
- Routing
- ERCOT routed
- Pairs with
- 814_29
Complete Unexecutable or Permit Required Response
Return ERCOT's response/acknowledgment to the TDSP's 814_28.
- Process
- Enrollment exception
- Role
- Response
- Routing
- ERCOT routed
- Pairs with
- 814_28
2 documents
820Remittance
Payment advice against an invoice — financial settlement rather than an enrollment event.
CR Remittance Advice
Advise the TDSP of payment/remittance from the CR (financial settlement, not an enrollment transaction).
- Process
- Payments
- Role
- Remittance advice
- Routing
- Point to point
- Pairs with
- 810_02
MOU/EC TDSP Remittance Advice
Advise the CR of payment/remittance from the MOU/EC TDSP.
- Process
- MOU/EC payments
- Role
- Remittance advice
- Routing
- Point to point
- Pairs with
- 810_03
1 document
824Application advice
Business-level rejection of an invoice or usage document. Distinct from a 997, which only speaks to X12 syntax.
Invoice or Usage Reject Notification
Reject an invoice (810) or usage (867) transaction at the application/business-content level. A 997 only acknowledges X12 syntax.
- Process
- Data rejection
- Role
- Application reject
- Routing
- Hybrid
- Pairs with
- —
3 documents
867Usage & meter reads
Historical usage, monthly and final usage, and the initial meter read that establishes when service actually started.
Historical Usage
Deliver historical usage and meter history.
- Process
- Usage
- Role
- Usage data
- Routing
- ERCOT routed
- Pairs with
- —
Monthly or Final Usage
Deliver periodic monthly usage or final usage. 867_03F is the final-usage form that establishes the actual end/final billing period.
- Process
- Usage
- Role
- Usage data
- Routing
- ERCOT routed
- Pairs with
- 810_02
Initial Meter Read
Deliver the effectuating initial meter read for a new enrollment — the operational source for the actual start date.
- Process
- Usage / enrollment completion
- Role
- Initial read
- Routing
- ERCOT routed
- Pairs with
- 814_05
1 document
997Functional acknowledgement
X12 syntax acknowledgement. A successful 997 means the file parsed — not that the transaction was accepted.
Functional Acknowledgement
Acknowledge X12 syntax/structural acceptance or rejection. NOT a business acceptance — a successful 997 does not mean the transaction was accepted.
- Process
- Transport control
- Role
- Syntax acknowledgement
- Routing
- Hybrid
- Pairs with
- —
5 documents
TOption 1 outages (T-series)
The Option 1 outage process: status requests, trouble reports, acknowledgements and completion.
Option 1 Outages: Outage Status Request
Request outage status from the TDSP under the Option 1 outage process.
- Process
- Option 1 outages
- Role
- Request
- Routing
- Point to point
- Pairs with
- T3
Option 1 Outages: Trouble Reporting Request
Submit a customer trouble/outage report to the TDSP. Expect T2 acknowledgment and later T4 completion; T3 may provide status.
- Process
- Option 1 outages
- Role
- Request
- Routing
- Point to point
- Pairs with
- T2
Option 1 Outages: Trouble Report Acknowledgement
Acknowledge receipt of an Option 1 trouble report (business ack, separate from 997).
- Process
- Option 1 outages
- Role
- Acknowledgement
- Routing
- Point to point
- Pairs with
- T1
Option 1 Outages: Status Response
Return current outage/trouble status.
- Process
- Option 1 outages
- Role
- Response
- Routing
- Point to point
- Pairs with
- T0
Option 1 Outages: Trouble Completion Report
Report completion/closure of the trouble report (terminal business outcome).
- Process
- Option 1 outages
- Role
- Completion
- Routing
- Point to point
- Pairs with
- T1
On authority
All 44types above are generated from the catalog our platform validates against, so this page and the software cannot disagree. It remains a transaction-level classification: ERCOT’s published Texas SET Implementation Guides are authoritative for segment-level detail, and nothing here replaces reading them.
How Conduit handles theseOr stop implementing this yourself.
Conduit sends and receives every document on this page, correlates the legs into chains, and posts what comes back against the customer record.