An ISA ID is the identifier that names the sender and receiver of an X12 EDI file. It lives in the ISA segment, the Interchange Control Header at the very start of every X12 interchange: ISA06 is the sender's ID and ISA08 is the receiver's ID, each paired with a two-character qualifier (ISA05 and ISA07) that says what kind of ID it is, such as a phone number, a DUNS number, or a mutually defined code. Your trading partner's system reads these fields before anything else and uses them to decide whether the file is for them and who sent it.

No central registry assigns ISA IDs. You choose yours, make sure it is unique on the networks you trade over, and give it to each partner during setup. Your partner gives you theirs, usually in their implementation guide.

The 16 elements of the ISA segment

The ISA is the only X12 segment with fixed-length elements. Every element is padded to its exact length, so the whole segment is always 106 characters, including the segment terminator. That fixed length is how a receiving system finds the delimiters before it can read anything else.

A correctly padded ISA example

ISA*00*          *00*          *12*8005551212     *ZZ*RETAILERID     *261005*1200*U*00401*000000001*0*P*>~

Reading it left to right: no authorization or security information (00 followed by ten spaces, twice); the sender uses qualifier 12, a phone number, padded to 15 characters; the receiver uses ZZ, a mutually defined ID, also padded to 15; the file was created October 5, 2026, at 12:00; it is version 4010; the control number is 1; no TA1 is requested; it is production data; and the component separator is >. The segment ends with the terminator ~.

The most common ISA mistake is dropping the padding. ISA06 and ISA08 must be exactly 15 characters, so a 10-digit phone number needs five trailing spaces.

ISA qualifier codes

The qualifier tells the receiver how to interpret the ID that follows. These are the ones you will see most in retail and logistics:

The full code list (X12 data element I05) includes dozens more, mostly for healthcare, government, and international networks. Use the qualifier your partner's guide expects for their side, and pick one for yours that you can keep for the life of the relationship.

How to choose your ISA ID

• Pick something stable. Changing your ISA ID later means every trading partner has to update their setup, and some will treat it as a new vendor connection. A main company phone number or DUNS number works well because it rarely changes.

• Make it unique. Because no registry exists, uniqueness only matters on the networks you trade over, but VANs and partners will reject an ID that collides with another sender. A mutually defined (ZZ) ID based on your company name, such as SURPASSBRAND01, is usually safe.

• Use uppercase letters and numbers. Avoid spaces inside the ID and special characters that could be mistaken for delimiters.

• Decide on test and production. Most partners use the same ID for both and rely on ISA15 (T or P) to tell them apart. Some retailers publish separate test and production IDs for their own side; check the guide.

• If a provider is involved, ask whose ID you are using. Some EDI providers and VANs send under their own ID by default. That makes switching providers harder, so prefer an ID you own.

The GS segment and your GS ID

Inside the ISA envelope, each group of documents of the same type sits in a GS (functional group) header. GS02 is the Application Sender's Code and GS03 is the Application Receiver's Code. Many partners set these to the same values as ISA06 and ISA08, without the padding, but some use different codes to route documents to a specific division or system. GS01 carries the functional identifier code for the group, such as PO for 850 purchase orders, IN for 810 invoices, SH for 856 ship notices, and FA for 997 acknowledgments.

Control numbers: ISA13, GS06, and ST02

Three control numbers tie an interchange together, and each must match its trailer:

• ISA13 must match IEA02 at the end of the interchange.

• GS06 must match GE02 at the end of the functional group.

• ST02 must match SE02 at the end of each transaction set.

The ISA13 interchange control number should increase with every file you send to a partner. Partners often reject a file that reuses a recent control number as a duplicate, which is a common problem after a system migration that resets the counter.

Troubleshooting ISA errors

A TA1 interchange acknowledgment (requested with ISA14 = 1) reports problems with the envelope itself, and the 997 functional acknowledgment reports on the documents inside. For the full testing process, see our EDI testing guide, and for transport-level IDs (which are separate from ISA IDs), see the AS2 guide.

Where to find your trading partner's ISA ID

Retailers publish their ISA qualifier and ID in their EDI implementation guide or onboarding packet, sometimes with separate values for test and production or for different business units. If you cannot find it, ask the partner's EDI team before you send anything. Our trading partner directory lists setup requirements for retailers like Walmart, Target, and Kroger.

ISA IDs are one part of a new partner setup. The EDI ERP integration readiness checklist covers the rest, and the EDI standards guide explains how X12 versions affect fields like ISA11 and ISA12.

Frequently asked questions

What is an ISA ID?

An ISA ID is the identifier for the sender (ISA06) or receiver (ISA08) of an X12 EDI interchange. It is paired with a qualifier (ISA05 or ISA07) that says what type of ID it is.

What does ISA stand for in EDI?

ISA is the Interchange Control Header, the first segment of every X12 interchange. It carries the sender and receiver IDs, the date and time, the version, and the interchange control number.

What is an ISA qualifier?

The ISA qualifier (ISA05 for the sender, ISA07 for the receiver) is a two-character code that identifies the type of ID used, such as 01 for a DUNS number, 12 for a phone number, or ZZ for a mutually defined ID.

How do I get an ISA ID?

You choose it. There is no registry. Most companies use a main phone number (qualifier 12), a DUNS number (01), or a mutually defined ID (ZZ), then share it with each trading partner during setup.

Is the ISA ID the same as the GS ID?

Often, but not always. Many partners set GS02 and GS03 to the same values as ISA06 and ISA08, while some use different GS codes to route documents to a specific division.

How long is the ISA segment?

Always 106 characters, including the segment terminator. Every element is fixed-length, and ISA06 and ISA08 are padded to 15 characters each.

What is the ISA control number?

ISA13 is a nine-digit number that identifies the interchange. It must match IEA02 in the trailer and should not be reused, or the partner may reject the file as a duplicate.

Can I change my ISA ID?

Yes, but every trading partner has to update their setup and usually retest. Choose an ID you can keep.

Let us handle partner setup

Surpass configures ISA and GS IDs, connections, and control numbers for every trading partner you add, and monitors acknowledgments so envelope errors get caught the same day. See our integrations or talk to our team.