Developer ToolsFree generatorPDF, Excel, Word export

X12 ISA/GS Envelope Skeleton Generator

Setting up a new EDI partner usually starts with an empty envelope to test connectivity. This generator builds the ISA, GS, ST, SE, GE and IEA segments with matching control numbers so you can drop in the body of any transaction set.

Fill in

ISA05 sender qualifier

ISA06 sender ID (pad to 15 characters)

Exactly 15 characters, trailing spaces included.

ISA07 receiver qualifier

ISA08 receiver ID (pad to 15 characters)

Exactly 15 characters, trailing spaces included.

ISA09 date (YYMMDD)

ISA10 time (HHMM)

ISA12 envelope version

ISA13 interchange control number (9 digits)

ISA15 usage indicator

GS01 functional identifier

GS02 application sender

GS03 application receiver

GS04 date (CCYYMMDD)

GS06 group control number

GS08 version

ST01 transaction set

ST02 set control number

Generated code

Download:

Envelope (one set, with a placeholder body)

ISA*00*          *00*          *ZZ*ACMEMFG        *01*123456789      *261020*0915*U*00401*000000101*0*T*>~
GS*PO*ACMEMFG*BIGRETAIL*20261020*0915*101*X*004010~
ST*850*0001~
[replace this line with the body segments of the transaction set]
SE*[segment count including ST and SE]*0001~
GE*1*101~
IEA*1*000000101~

Check before sending

ISA06 and ISA08 must be exactly 15 characters. ISA13 must equal IEA02. GS06 must equal GE02. ST02 must equal SE02. SE01 counts ST through SE inclusive. ISA11 is shown as U (standards identifier) for version 00401. For 00501 use the repetition separator character the partner specifies, usually ^.

This is a skeleton for testing translators and partner connections, not a production map. Replace the bracketed line with real segments. Confirm separators, qualifiers, usage indicator and version in the partner guide, and keep ISA15 at T until the partner approves production.

Generate envelopes from your partner register

An optional review of how partner envelope data could be kept in one managed source.

Optional. The tool and every export work without this. No spam.

How to use it

Enter the qualifiers and IDs exactly as the partner gave them, including padding to 15 characters. Set the transaction set and version, pick T for test, and copy the generated lines into your translator or test harness. Replace the placeholder with the body segments, then count the segments from ST through SE and fill in SE01.

Use unique control numbers for each test file.
Keep ISA15 at T until the partner confirms production.
Match GS08 to the version in the partner guide.
Save the generated file with a name that includes ISA13.

Why the envelope matters

A gateway reads the ISA first. If the sender qualifier and ID do not match a configured trading partner, the file is dropped before any mapping runs, and you may never get a 997. That is why many connection problems that look like mapping errors are envelope problems, and why this part is worth testing before the first real document.

Common mistakes

Trimming trailing spaces in a text editor changes the ISA length, so edit with a tool that does not strip whitespace. Copying a production ISA13 into a test file also causes duplicate checks to fire. Another mistake is using the same GS06 across groups in one interchange. Counters should increase automatically in the translator.

Frequently Asked Questions

Do I need a GS segment?

Yes for X12. Each interchange contains at least one functional group, and each group has a GS and a GE. The group carries the functional identifier and the version used for the sets.

What does U in ISA11 mean?

In version 00401 and earlier ISA11 holds the interchange control standards identifier, with U meaning U.S. EDI Community of ASC X12. From 00402 it is the repetition separator, commonly ^.

How do I count SE01?

Count every segment from ST to SE inclusive. For ST, BAK, N1, PO1, ACK, CTT and SE the count is 7.

Can I use this for production?

The output is a starting skeleton. In production the envelope is built by your translator with managed counters. Use this for testing and for comparing against what your translator produces.

If you maintain many trading partner profiles, Netray can help build a partner profile register that generates correct envelopes from one source.

Talk to an Expert Explore More Free Tools

Related Tools

Supply Chain & Inventory

More Developer Tools tools

See all

Back to All Tools