TA1 005 / 006: wrong ISA qualifier, or a SCAC that isn't padded
Your files are rejected at the envelope, or silently dropped, because the partner can't match your sender ID to a trading partner profile. In trucking, this is usually a 02 vs ZZ qualifier mix-up or an ISA06 that isn't padded to 15 characters.
What you see
TA1*000000417*261021*1430*R*006~
Related TA105 note codes: 005 Invalid Interchange ID Qualifier for Sender, 006 Invalid Interchange Sender ID, 007/008 the same for the receiver, 009 Unknown Interchange Receiver ID, 022 Invalid Control Structure. Some partners send no TA1 at all, and you only notice because no 997 ever arrives.
What it means
ISA05/ISA07(element I05) say what kind of ID follows. Common values in trucking:02= SCAC,ZZ= Mutually Defined,01= DUNS,08= UCC EDI Communications ID,12= Phone.- The partner set up your profile with one exact qualifier and ID pair, for example
02+XMPL.ZZ+XMPLis a different identity to their translator. - The ISA is a fixed-length segment. ISA06 and ISA08 are always exactly 15 characters, padded on the right with spaces, so the whole ISA is 106 characters including the terminator. An unpadded SCAC shifts every element after it.
Why it happens
- A new partner was set up by copying another partner's profile that used ZZ.
- A tool or script trims trailing spaces from the file.
- The receiver ID (ISA08) is typed differently from the partner's spec (case, spaces, or a test ID used in production).
- ISA15 is
T(test) when sending to production, orPwhen sending to a test endpoint.
The exact fix
- Get the exact sender and receiver qualifier and ID pairs from your partner's EDI setup sheet or implementation guide.
- Set ISA05/ISA06 and ISA07/ISA08 to those values, and pad ISA06 and ISA08 with spaces to 15 characters.
- Check that the ISA is exactly 106 characters and that ISA16 (the component separator) is followed directly by the segment terminator.
- GS02/GS03 are not padded. Use your partner's application codes there, which are often the SCAC.
Before and after
ISA*00* *00* *ZZ*XMPL*ZZ*BROKERX *261021*1430*U*00401*000000417*0*P*>~ISA*00* *00* *02*XMPL *ZZ*BROKERX *261021*1430*U*00401*000000417*0*P*>~The receiver ZZ*BROKERX is a made-up example. Use the exact qualifier and ID from your partner's setup sheet.
Not sure this is your error?
Paste your 997, TA1, rejected file, or the broker's error email into the free EDI Reject Checker. It decodes every AK3/AK4/AK5/AK9 and TA1 code and checks counts, control numbers, and dates in seconds. It runs in your browser, so nothing is uploaded.
Fix reports are paid up front; if we can't find the cause, the refund is automatic.
References
- ISA Interchange Control Header, 004010 (element lengths)
- Element I05, Interchange ID Qualifier (01, 02, 08, 12, ZZ)
- Element I18, Interchange Note Code (005 to 009, 022)
- X12, Transaction Sets