Acknowledgments

Acknowledgments for X12 documents fall into three categories.

• Delivery Acknowledgments

• Syntactic Response Acknowledgments

• Business Application Acknowledgments

You must have an agreement with your trading partner to use acknowledgments.

Delivery Acknowledgments

Two interchange delivery acknowledgments exist for X12 documents.

• Interchange acknowledgment segment (TA1)
  An interchange acknowledge segment (TA1) reports the receipt of the contents of one interchange control header and trailer envelope, in which the envelope surrounds one or more functional groups. The TA1 reports the results of the syntactical analysis of the interchange control header and trailer. Each interchange exchanged between trading partners might contain interchange-level control segments (TA1s) related to prior interchanges.

Interchange delivery notice segment (TA3)
An interchange delivery notice (TA3) reports the delivery status of a document, when an intermediary is used to transfer documents between an interchange sender and interchange receiver.

Syntactic Response Acknowledgments

Two syntactic response acknowledgments exist for X12 documents.

•

Functional acknowledgment (997) The functional acknowledgment (997) describes the syntax-level acknowledgment of the receipt of an X12 functional group.

•

Implementation acknowledgment (999) The implementation acknowledgment (999) is first available in the X12 004061 sub release. It is used for reporting the status of implementation guide syntax edits.

Business Application Acknowledgments

Business application acknowledgments includes two different types.

•

Application advice (824)

The application advice (824) reports the results of an application system's data content edits on a transaction set. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format.

The 824 is designed to report the following information for a transaction set:

— Acceptance

— Rejection

— Acceptance with change

•

Specific response transaction (Example: 271 response to a 270)

The status of a transaction set can also be reported by using a specific response transaction set as a response to the original transaction set.

The following information are examples of transaction set pairs where the status of the original transaction set is indicated in the response transaction set:

— 271 response to a 270

— 855 response to an 850

— 870 response to an 869