100% Offline Reference 106-Byte ISA Fix

Fixing ISA Segment Must Be 106 Characters (Exact Byte-Offset Map 0..105)

Strict X12 parsers like Java StAEDI, Python pyx12, BizTalk, and clearinghouse gateways read delimiters from hard-coded byte indices 3, 104, and 105 — causing instant crashes whenever chat tools collapse whitespace inside ISA-02, ISA-04, ISA-06, or ISA-08.

Exact 106-Byte ISA Fixed-Width Offset Table (0..105)

FieldByte Indices (0-Based)Exact WidthPadding / Format Rule
ISA Tag + Elem Sep0..33 + 1 bytesLiteral ISA + element separator at index 3 (e.g. *)
ISA-01 Auth Info Qual4..5 (+ sep 6)2 chars00 (No Auth Info Present) or 03
ISA-02 Auth Information7..16 (+ sep 17)10 charsRight-padded with spaces (10 spaces when ISA-01=00)
ISA-03 Security Qual18..19 (+ sep 20)2 chars00 or 01
ISA-04 Security Info21..30 (+ sep 31)10 charsRight-padded with spaces (10 spaces when ISA-03=00)
ISA-05 Sender ID Qual32..33 (+ sep 34)2 charsZZ, 01 (DUNS), 14, 30 (TIN)
ISA-06 Interchange Sender ID35..49 (+ sep 50)15 charsLeft-aligned ID, right-padded with spaces to exactly 15 chars
ISA-07 Receiver ID Qual51..52 (+ sep 53)2 charsZZ, 01, 14, 30
ISA-08 Interchange Receiver ID54..68 (+ sep 69)15 charsLeft-aligned ID, right-padded with spaces to exactly 15 chars
ISA-09 Interchange Date70..75 (+ sep 76)6 charsYYMMDD
ISA-10 Interchange Time77..80 (+ sep 81)4 charsHHMM
ISA-11 Repetition Sep / Std ID82 (+ sep 83)1 char^ or U (5010 repetition separator; U in 4010)
ISA-12 Control Version84..88 (+ sep 89)5 chars00501 or 00401
ISA-13 Interchange Control #90..98 (+ sep 99)9 digitsZero-prefixed 9-digit integer (must match IEA-02)
ISA-14 Ack Requested100 (+ sep 101)1 char0 (None) or 1 (TA1 Requested)
ISA-15 Usage Indicator102 (+ sep 103)1 charP (Production), T (Test), or I
ISA-16 + Seg Terminator104 + 1051 + 1 bytesComponent separator (:) at 104; Segment terminator (~) at 105

Before & After: Collapsed Slack Snippet vs. Repaired 106-Byte ISA

// BROKEN (78 bytes — Slack collapsed spaces in ISA-02, ISA-04, ISA-06, ISA-08):
ISA*00* *00* *ZZ*SENDER*ZZ*PAYER*261112*1430*^*00501*000000001*0*T*:~

// REPAIRED BY EDIPRISM FREE TIER (106 bytes exact):
ISA*00*          *00*          *ZZ*SENDER         *ZZ*PAYER          *261112*1430*^*00501*000000001*0*T*:~
EdiPrism Offline Inspector — Zero Network Calls
Fixing 'ISA Segment Must Be 106 Characters' After Slack, Jira & Teams Copy-Paste — EdiPrism inside JetBrains IDE with EdiPrism

Frequently Asked Engineering Questions

Do CRLF line breaks after ~ affect the 106-byte ISA rule?

No. The 106-byte count runs from 'I' (byte 0) through the segment terminator character '~' (byte 105). Optional CR or LF formatting characters after byte 105 follow the segment terminator, though production VAN streams typically omit line breaks altogether.

Inspect, Diff, Validate & Scrub This Payload Offline in Your JetBrains IDE

Never paste regulated healthcare PHI (837/835/271) or supply-chain payloads (850/ORDERS) into browser parsers. EdiPrism X12 EDIFACT runs 100% air-gapped inside IntelliJ IDEA, PyCharm, DataGrip, Rider, GoLand, and WebStorm with a free core tier and a 14-day [Pro] trial.

Install Free from JetBrains Marketplace → Read Air-Gap Security Architecture