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 · Government and regulatory

EDI 280 Voter Registration Information

The X12 document used to submit voter registration applications and to transmit information about registered voters and changes.

Sent by
Registration agency or election office
Received by
Election office or another agency
Standard
ANSI ASC X12

What is an EDI 280?

The EDI 280 Voter Registration Information is the ANSI X12 transaction set used to submit voter registration application information and to transmit information about previously registered voters and changes to it.

Voters may register through agencies other than election offices, such as motor vehicle departments, and move between jurisdictions. Exchanging registrations and changes electronically keeps voter rolls current and avoids duplicate registrations. Election systems are governed by state laws that define the formats and processes used. Changes include new addresses and names.

How the EDI 280 worksDiagram of the EDI 280 Voter Registration Information. Registration agency or election office sends it to election office or another agency. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 2 optional loops are listed by their first segment.How the EDI 280 worksVoter Registration Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 280SENDERRegistration agency orelection officeRECEIVERElection office oranother agency997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VIGS … GETransaction set 280ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:N1DETAIL+ 1 optional loop, starting with:PWKBlue 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 280. Your trading partner's implementation guide adds its own requirements.
How the EDI 280 worksDiagram of the EDI 280 Voter Registration Information. Registration agency or election office sends it to election office or another agency. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 2 optional loops are listed by their first segment.How the EDI 280 worksVoter Registration Information: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 280SENDERRegistrationagency orelection officeRECEIVERElection officeor anotheragency997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code VI (GS … GE)Transaction set 280 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:N1DETAIL+ 1 optional loop, starting with:PWKBlue 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 280. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 280, 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 280 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

  • Transmitting registrations from other agencies
  • Reporting changes of address or name
  • Transferring registrations between jurisdictions

Where it fits in the document flow

This document 280 Voter Registration Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 280 (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
  • N1
  • PWK
  • IN1
  • NX1
  • EFI
  • SE

Practical example

The 280 in practice

A resident registers to vote while renewing a driver's license. The motor vehicle department transmits the registration to the county election office, which checks eligibility, adds the voter to the roll and confirms the registration.

Implementation

Implementation considerations for the 280

  • Follow state election laws and data standards.
  • Protect voters' personal data under election law.
  • Check for duplicate registrations across jurisdictions.
  • Track confirmations and rejections for each registration.

How ECOM helps

Automate the 280 with ECOM

Solution

Enterprise Integration

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

Solution

EDI Integration

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

Solution

B2B Integration

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

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

Need help with the EDI 280?

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

Request a Demo Contact us