972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Communications

EDI 814 General Request, Response or Confirmation

The X12 document used to request actions, respond to requests, or confirm actions performed, widely used in deregulated energy markets.

Sent by
Energy supplier, utility or other market participant
Received by
Utility, supplier or other market participant
Standard
ANSI ASC X12

What is an EDI 814?

The EDI 814 General Request, Response or Confirmation is the ANSI X12 transaction set used to request actions to be performed, to respond to such requests, or to confirm information about actions performed.

Its best-known use is in deregulated retail energy markets in the United States, where competitive suppliers and utilities exchange 814s to enroll customers, drop them, change account details and confirm switches. Each market publishes its own implementation guides, so the same transaction set carries different rules from state to state. Usage data then follows in the 867 and billing in the 810.

How the EDI 814 worksDiagram of the EDI 814 General Request, Response or Confirmation. Energy supplier, utility or other market participant sends it to utility, supplier or other market participant. It usually starts the exchange. It is usually followed by 867, 810 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 5 optional loops are listed by their first segment.How the EDI 814 worksGeneral Request, Response or Confirmation: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 814SENDEREnergy supplier, utilityor other marketparticipantRECEIVERUtility, supplier orother marketparticipant997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY867Product Transfer andResale Report810Invoice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code GEGS … GETransaction set 814ST … SEHEADINGBGNBeginning Segment+ 3 optional loops, starting with:FA1N1LMDETAIL+ 1 optional loop, starting with:LINSUMMARY+ 1 optional loop, starting with:AWDBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 814. Your trading partner's implementation guide adds its own requirements.
How the EDI 814 worksDiagram of the EDI 814 General Request, Response or Confirmation. Energy supplier, utility or other market participant sends it to utility, supplier or other market participant. It usually starts the exchange. It is usually followed by 867, 810 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 5 optional loops are listed by their first segment.How the EDI 814 worksGeneral Request, Response or Confirmation:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 814SENDEREnergy supplier,utility or othermarketparticipantRECEIVERUtility, supplieror other marketparticipant997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY867Product Transfer and Resale Report810Invoice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code GE (GS … GE)Transaction set 814 (ST … SE)HEADINGBGNBeginning Segment+ 3 optional loops, starting with:FA1N1LMDETAIL+ 1 optional loop, starting with:LINSUMMARY+ 1 optional loop, starting with:AWDBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 814. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 814, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 814 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Enrolling a customer with a competitive energy supplier
  • Dropping a customer or changing account details
  • Responding to and confirming enrollment requests

Where it fits in the document flow

This document 814 General Request, Response or Confirmation
Usually followed by 867 Product Transfer and Resale Report810 Invoice997 Functional Acknowledgment

Structure

Mandatory segments in the 814 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • FA1
  • FA2
  • AMT
  • N1
  • LM
  • LQ
  • LIN
  • NM1
  • AWD
  • SE

Practical example

The 814 in practice

A homeowner signs up with a competitive electricity supplier. The supplier sends the local utility an 814 enrollment request with the customer's account number and requested start date. The utility validates the account, replies with an 814 accepting the enrollment and the switch date, and later sends usage data with the 867.

Implementation

Implementation considerations for the 814

  • Follow the implementation guide of each state market, which differ significantly.
  • Meet market timelines for enrollment and drop processing.
  • Validate account numbers and customer details before sending.
  • Track every request until a response or rejection is received.

How ECOM helps

Automate the 814 with ECOM

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related communications documents

All 16 communications documents

Need help with the EDI 814?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us