We Make EDI Integration Easy


Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

Let's Chat Start Planning
 
What is a 842 - Nonconformance Report document?

The 842 EDI document type is an electronic version of a paper Nonconformance Report. Standard EDI formats include X12, ANSI, EDIFACT and its subsets. The 842 EDI document type is used to report products or processes that do not fulfill requirements or specifications, and to report the nonconformance at the level of detail required. It can be used to report the nonconformances of a component or part while identifying the assembly, and to report, initiate, or request actions related to the nonconformance being reported.

What makes up the 842 - Nonconformance Report document?

An EDI 842 - Nonconformance Report document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. Data elements can include part type, assembly, type of nonconformance, and recommended action, identical to a paper nonconformance report. There are an infinite number of possibilities available for a company to include data on an 842 Nonconformance Report. There are an infinite number of possibilities available for a company to include data on an 842 - Nonconformance Report.

How is a 842 - Nonconformance Report used?

The 842 EDI document is sent when a part, process, or other item is found to be nonconformant, and is a notification and request to repair. After the 842 Nonconformance Report is received, a 997 Functional Acknowledgment is sent back from the receiver indicating that the 842 Nonconformance Report was successfully received.

How is a 842 - Nonconformance Report processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.