What is 824? What is 864? Why the two transaction sets were developed to manifest rejection details? Definitely these basic questions arise for a newbie in b2b arena. This is bit confusing, why EDI companies use both 824 and 864 to report an error for a transmission. Let’s go in detail to understand it clearly.
824 and 864 are Draft Standards which establishes the data contents of the Application Advice Transaction Set (824) and Test Message (864) for use within the context of an Electronic Data Interchange (EDI) environment.
Definition of 824:
The transaction set is intended to provide the necessary edits of the transaction sets for which it generated from the receiver end. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. It should not be confused with the 997 acknowledgements, it is specified for different purpose.
Definition of 864:
“This transaction set is intended for human reading, not for machine processing“. The use of the Text Message transaction set demands of the sender certain detailed information about the recipient. The transaction set’s purpose is to provide communication to the recipient in some human-readable form. The recipient’s network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission
In simple words both of these are intended to provide some rejection details of a particular transaction set. You might have noticed a perfect difference between 824 and 864 from the words marked in italic style( see in definition of 864 ). 864 is intended for human reader where as 824 is designed for machine processing. If one understand this specific difference between 864 and 824, some more questions knock you mind. What is the reason behind developing an 864 transaction set, while 824 already addressing rejection causes and also what is the necessity for human to read although EDI transaction sets are intended for machine processing? Why it is not intended for machine processing? The answer for these questions is simple, a machine cannot address all the errors, it is limited to the set of errors embedded in its programming logic, when ever a new error occurs it cannot understand and it cannot generate a remedy or cause for rejection related to that error. In such cases, 864 show its best part by manually keying the error details with this transaction set.
We request you to share this page and spread our efforts to all b2b geeks
