EDI Envelope — ISA, GS, GE, IEA

EDI Envelope Segments — ISA, GS, GE, IEA

Overview

Every EDI transaction is wrapped in envelope segments. These are consistent across all transaction types (846, 850, 856, 810).

code
ISA ─── Interchange Header (outermost envelope)
 GS ─── Functional Group Header
  ST ─── Transaction Set Header
  ... transaction content ...
  SE ─── Transaction Set Trailer
 GE ─── Functional Group Trailer
IEA ─── Interchange Control Trailer

ISA - Interchange Header

ElementNameLengthM/OValue/Notes
ISA01Authorization Info Qualifier2 IDRequired00 (No authorization info present)
ISA02Authorization Information10 ANRequiredNot Used (space-filled)
ISA03Security Info Qualifier2 IDRequired00 (No security info present)
ISA04Security Information10 ANRequiredNot Used (space-filled)
ISA05Interchange ID Qualifier2 IDRequiredZZ (Mutually Defined) or 01 (DUNS)
ISA06Interchange Sender ID15 ANRequiredIf sender is FLX → FLXPOINT. If sender is Vendor → vendor's ISA ID number. Right-padded with spaces to 15 chars
ISA07Interchange ID Qualifier2 IDRequiredZZ (Mutually Defined)
ISA08Interchange Receiver ID15 ANRequiredIf receiver is FLX → FLXPOINT. Right-padded to 15 chars
ISA09Date6 DTRequiredYYMMDD format
ISA10Time4 TMRequiredHHMM format
ISA11Interchange Control Standards ID1 IDRequiredU (US EDI Community of X12, TDCC, UCS)
ISA12Interchange Control Version5 ANRequired00401
ISA13Interchange Control Number9 NRequiredSequential number starting with 1, incremented by 1 per transmission
ISA14Acknowledgment Requested1 IDRequired0 (No Interchange Acknowledgment TA1 requested)
ISA15Test Indicator1 IDRequiredP (Production) or T (Test)
ISA16Sub-element Separator1 ANRequired> (standard) or : — must be consistent throughout the file. 992 support emails in 6 months mention delimiter/separator issues.

Delimiter Troubleshooting

  • Standard delimiters: segment terminator ~, element separator *, sub-element separator > (ISA16)
  • Common issue: files have line breaks (CR/LF) before ~ — Flxpoint's parser handles this, but be aware
  • Unusual delimiters: if a vendor uses | instead of *, the ISA header must declare it correctly at the fixed position
  • Data containing delimiters: if product names or descriptions contain *, ~, or >, this will break the parser. These characters must be escaped or removed from data fields.

ISA ID Qualifier Codes (ISA05/ISA07)

CodeDescription
01DUNS (Dun & Bradstreet)
14DUNS Plus Suffix
30U.S. Federal Tax ID
32U.S. Federal Employer ID (FEIN)
ZZMutually Defined (default)

X12 defines 30+ qualifier codes but FLX typically uses ZZ.


GS - Functional Group Header

ElementNameLengthM/OValue/Notes
GS01Functional Identifier Code2 IDRequiredSee table below
GS02Application Sender's Code15 ANRequiredSender's ID
GS03Application Receiver's Code15 ANRequiredReceiver's ID
GS04Date8 DTRequiredCCYYMMDD format
GS05Time4 TMRequiredHHMM format
GS06Group Control Number9 NRequiredControl number, starting with 1, incremented by 1
GS07Responsible Agency Code2 IDRequiredX (Accredited Standards Committee X12)
GS08Version12 ANRequired004010VICS

GS01 Functional Identifier Codes

Authoritative code table confirmed with Faiyaz Ahmed (Integrations) 2026-04-16. See Flxpoint Parser Rules for envelope-layer behavior.

CodeTransactionNotes
IB846 Inventory Inquiry/Advice
PO850 Purchase Order
AD855 PO AcknowledgementCanonical Flxpoint code
PR855 PO AcknowledgementLegacy alias — still accepted by the parser
SH856 Ship Notice/Manifest
IN810 Invoice
PI832 Price/Sales Catalog
FA997 Functional Acknowledgment

Accepted Versions (GS08)

Flxpoint accepts three variants:

  • 004010VICSpreferred (matches VICS-specific segments)
  • 004010 — accepted with a warning (not hard-rejected even if VICS-specific segments are present)
  • 005010 — accepted

ISA15 Usage Indicator — Test Mode

  • P = Production
  • T = Test — both are processed by Flxpoint, but the UI (and Flxpector) badges test files with a "Test Mode" pill so they are not mistaken for live orders.

GE - Functional Group Trailer

ElementNameLengthM/OValue/Notes
GE01Number of Included Transaction Sets6 NRequiredCount of ST segments within the group
GE02Group Control Number9 ANRequiredMust match GS06

IEA - Interchange Control Trailer

ElementNameLengthM/OValue/Notes
IEA01Number of Included Functional Groups5 NRequiredCount of GS segments within the interchange
IEA02Interchange Control Number9 NRequiredMust match ISA13

Control Number Matching Rules

Trailer FieldMust MatchDescription
SE02ST02Transaction Set Control Number
GE02GS06Group Control Number
IEA02ISA13Interchange Control Number

FLX Envelope Requirements vs Generic X12

AspectFLX SpecGeneric X12 004010
ISA05ZZ or 0130+ qualifier codes supported
ISA13 uniquenessNot required by FLX (best practice)Some validators enforce
ISA date formatYYMMDDYYMMDD (match)
GS date formatCCYYMMDDCCYYMMDD (match)
GS time formatsHHMMHHMM, HHMMSS, HHMMSSD, HHMMSSDD

Something unclear?

Ask our AI assistant — it knows this spec and can explain any segment, error, or rule in plain English.