TA1 Interchange Acknowledgment: Codes and Examples

The TA1 answers the first question in any EDI exchange: could the receiver open the envelope at all? Before a translator looks at a single purchase order or invoice, it reads the ISA header and IEA trailer. If the control numbers do not match, the receiver ID is unknown or the separators are wrong, nothing inside gets processed, and no 997 or 999 can follow. The TA1 is how the receiver tells you that, and which part of the envelope was at fault.

This guide covers what the TA1 is (and why it is not a transaction set), each of its five elements, the full TA105 note code list, how ISA14 requests it, two examples, and how the TA1 fits with the 997, 999 and 824.

What Is a TA1 Interchange Acknowledgment?

A TA1 is the Interchange Acknowledgment segment defined in X12.5, the X12 Interchange Control Structures standard, used by the receiver of an interchange to report the status of its ISA/IEA envelope. It is one of three basic interchange segments: X12 states, citing section 4.4.1 of X12.5, that "the basic interchange segments consist of the ISA, the IEA, and the TA1 segments."

That makes the TA1 different from the 997 and 999:

• It is a segment, not a transaction set. There is no ST, SE, GS or GE around it. It sits directly inside an ISA/IEA envelope, after the ISA and before any GS.
• It travels in its own interchange, or alongside groups. A receiver can send an interchange containing only TA1 segments, with IEA01 = 0 (no functional groups), or place TA1s at the start of an interchange that also carries 997s or other documents.
• It must be enveloped. X12 has confirmed that a file containing only a bare TA1, with no ISA and IEA around it, is not correct, and that no GS should come before the TA1.

Authoritative references for TA1 work:

• X12's requests for interpretation on TA1 packaging and its connection to ISA14, which point to X12.5 and the X12 Acknowledgment Reference Model
• Microsoft's X12 TA1 reference, which maps each TA1 element to the ISA field it echoes and lists the TA105 note codes
• HIPAA companion guides, such as the Indiana Health Coverage Programs TA1/999 guide, which describe when a payer returns a TA1 in practice

Who sends it? The receiver of an interchange: your trading partner, its VAN, or a clearinghouse.

When is it sent? When the sender requests one with ISA14 = 1, or whenever the trading partner agreement says so. Many healthcare payers and clearinghouses send a TA1 only when the envelope has errors.

Why does it matter? A rejected envelope means nothing inside it was processed. If you are waiting for a 997 that never comes, a TA1 is often the explanation.

How the TA1 Is Requested: ISA14

ISA14 is the Acknowledgment Requested flag in your outbound ISA. In the X12 standard it has two values:

Setting ISA14 to 1 asks for a TA1. It does not ask for a 997 or 999, and setting it to 0 does not switch those off; functional and implementation acknowledgments are set by the trading partner agreement. Some partners also return TA1s for rejected interchanges whatever ISA14 says, and some EDI platforms add their own settings (for example, "send a TA1 only on errors") that are configuration choices, not X12 codes.

An interchange that carries only TA1s is normally sent with ISA14 = 0, so the acknowledgment does not itself ask to be acknowledged.

TA1 Examples

The TA1 is not a transaction set, so it is shown here as raw X12 rather than as an interactive sample. To decode a TA1 you received, paste it into the free EDI rejection explainer, which translates TA104 and TA105 and, with your original file, shows where the envelope problem is.

Accepted interchange

A grocery chain acknowledges a supplier's interchange 000000894, sent on November 3, 2026 at 06:12. The envelope was fine.

ISA*00*          *00*          *ZZ*HARBORGROCER   *ZZ*SUMMITBEV      *261103*0614*U*00401*000004512*0*P*:~
TA1*000000894*261103*0612*A*000~
IEA*0*000004512~

The TA1 travels in the grocer's own interchange, with its own control number (000004512). TA101 to TA103 echo the supplier's ISA13, ISA09 and ISA10. IEA01 is 0 because the interchange contains no functional groups.

Rejected interchange

The supplier's next interchange, 000000895, ended with an IEA whose control number did not match its ISA.

ISA*00*          *00*          *ZZ*HARBORGROCER   *ZZ*SUMMITBEV      *261103*0614*U*00401*000004513*0*P*:~
TA1*000000895*261103*0612*R*001~
IEA*0*000004513~

TA104 = R rejects the interchange, and TA105 = 001 says why: the interchange control number in the header and trailer do not match. Nothing inside was processed, so no 997 will follow for it. The fix is in the supplier's translator: correct the IEA and resend under a new interchange control number.

TA1 Structure

The element layout is the same in 004010 and 005010. What changes between those releases is the ISA it reports on: in 004010, ISA11 is the interchange control standards identifier (U), while in 005010 it carries the repetition separator.

TA104: the verdict

Which conditions a receiver treats as E and which as R varies by translator. A duplicate control number, for example, is a rejection on some systems and accepted with a note on others.

TA105: interchange note codes

Later X12 releases add codes beyond 031. If you receive one, check the release in the acknowledging ISA and your partner's guide.

Fixing the Most Common TA1 Rejections

The free EDI inspector checks the envelope of the interchange you sent: ISA width, ISA and IEA control numbers, the IEA group count and duplicate control numbers. Running the original file through it usually finds the cause of a TA1 rejection in seconds.

TA1 vs 997 vs 999 vs 824

The TA1 is the outermost of four acknowledgment layers. Each checks something different, and our 997 guide and 999 guide use the same breakdown.

How they interact in practice:

• TA1 rejected (R). The receiver stopped at the envelope. No 997 or 999 will arrive for any group in that interchange.
• TA1 accepted (A) or accepted with errors (E). The receiver went on to the groups. A 997 or 999 follows if the agreement calls for one.
• No TA1 at all. Either you did not request one, or the partner only sends TA1s on errors. Absence is not proof the envelope was fine; the 997 or 999 is.
• Healthcare. HIPAA trading partners commonly return a TA1 for envelope errors and a 999 for each functional group, then a business response such as a 277CA claim acknowledgment or 835.

The EDIFACT counterpart is the CONTRL message, which reports interchange-level results in its UCI segment and can also report on messages.

Common TA1 Mistakes

TA1 Implementation Checklist

• Ask each partner whether it sends TA1s always, only on errors, or never, and whether it wants ISA14 = 1
• Store every outbound ISA13 with its date, time and partner
• Match inbound TA1s on TA101, and alert on any R
• Alert when neither a TA1 nor a 997/999 arrives within the partner's window
• Decide whether you send TA1s for inbound interchanges, and configure your translator to match
• Never reuse an interchange control number, including for resends
• Test with an accepted interchange, a mismatched IEA, an unknown receiver ID and a duplicate control number

Where OrderSync Fits

Envelope errors are configuration problems: once the translator builds the ISA and IEA correctly, they stop. The errors that keep coming are in the documents themselves, and many of them start when an order is keyed by hand. OrderSync reads inbound orders in any format, from EDI 850s and 875s to emails, PDFs and spreadsheets, matches customers, items and units to your catalog, and outputs valid X12 or clean data for your ERP, sending a 997 for every inbound EDI transaction it receives.

Paste the interchange a TA1 rejected into the free EDI inspector to check its envelope and contents, decode the acknowledgment itself with the EDI rejection explainer, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions