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).

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

Delimiter Troubleshooting

• Flxpoint's 850: segment terminator ~, element separator *, and the sub-element separator set on your connection in ISA16 (: when none is set; older copies of the Flxpoint spec show >). Exception: the 997 reuses the delimiters of the file it acknowledges, terminator and trailing whitespace included.
• Invalid terminator (Flxpector TOK-003): if the character after ISA16 is the replacement character U+FFFD (shown as � in some editors) or a raw control byte such as 0x85, the file went through an encoding conversion that corrupted it. Every segment ends with it and most receivers reject the file. Flxpector's "Apply fix" rewrites the terminator to ~. If the file is a Flxpoint-generated 997, contact support@flxpoint.com with the file attached so it can be re-issued, and switch your own outbound terminator to ~ so the next 997 does not inherit the problem.
• 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)

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

GS - Functional Group Header

GS01 Functional Identifier Codes

Accepted Versions (GS08)

Flxpoint accepts three variants:

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

ISA15 Usage Indicator

• P = Production, T = Test.
• Flxpoint does not read ISA15 on the files you send. A file with T is processed exactly like a file with P: a test 846 updates real stock, and a test 855, 856 or 810 updates the order whose PO number it carries. During testing, send documents only for the test orders Flxpoint sends you.
• On Flxpoint's own 850s, ISA15 is P unless Flxpoint has set your connection to test, in which case the 850s carry T.
• Flxpector shows a "Test Mode" pill on a file whose ISA15 is T, so you can see which value a file carries before you upload it. That pill is Flxpector only; it does not change how Flxpoint processes the file.

GE - Functional Group Trailer

IEA - Interchange Control Trailer

Control Number Matching Rules

FLX Envelope Requirements vs Generic X12

Test vs. Production traffic

Two levers distinguish test from production interchanges:

Go-live checklist: flip ISA15 T→P; make sure no test file is still waiting in the inbound folder, because Flxpoint does not tell test files from production files; switch to the production IDs on BOTH sides at the same time (a one-sided switch means a translator stops matching the other side's files); keep ISA13 incrementing — never reuse control numbers across the cutover; send one small production file and confirm it processes before full volume. A "missing trading partner profile" notice from a VAN after the switch means the production IDs aren't provisioned on the receiving side yet.