ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 842 — Nonconformance Report

The 842 describes a nonconformance — product, process, or service — at a level of detail sufficient to trigger root-cause analysis and corrective actions at the relevant partner.

Purpose

The 842 documents a defect detected at receiving, during assembly, or in the field, and attributes it to a product (part number, serial, lot) or to a process (manufacturing step, QC checkpoint). It carries the nonconformance code, affected quantity, description, severity, attached evidence (photos, measurements, reference lot), and the requested action — 8D analysis, supplier return, deviation, recall.

The 842 is central to aerospace (AS9100), automotive (IATF 16949) and medical-device quality programs: it traces defects per lot and industrially triggers the RCA → CAPA cascade. It complements the 861 (Receiving Advice), which carries the receiving event but not the quality detail.

Envelope structure

The 842 travels in a functional group NC (Nonconformance). Didactic example in release 004010:

x12 example-842.x12 
ISA*00*          *00*          *ZZ*ACMEBUYER     *ZZ*ACMESUPPLIER  *260514*1015*U*00401*000000842*0*P*>~
GS*NC*ACMEBUYER*ACMESUPPLIER*20260514*1015*1*X*004010~
ST*842*0001~
BNR*00*NCR-2026-0091*20260514~
N1*BY*ACME RETAIL CO*92*0001~
N1*VN*ACME SUPPLIER INC*92*V-9087~
LM*UT*NC~
NCD*A*Cosmetic defect on housing~
LIN*1*UP*012345678905~
PID*F****PLASTIC INSTRUMENT CASE~
QTY*47*5*EA~
REF*PO*PO78901~
SE*11*0001~
GE*1*1~
IEA*1*000000842~

The BNR (Beginning Segment for Nonconformance Report) opens with: function code (00 = Original, 04 = Change…), NCR number, issue date. The LM/LQ loop carries classification codes, the NCD (Nonconformance Description) the natural-language description. The LIN loop identifies the affected item; QTY the affected quantity, and REF*PO binds the nonconformance to the originating order.

Common segments

  • Header — ST, BNR (Beginning Segment for Nonconformance Report), DTM (detection date).
  • Parties — N1 loop (BY, VN, IF = Inspector).
  • Nonconformance classification — LM/LQ loop with industry-specific code list (AIAG, Boeing…).
  • Description — NCD (Nonconformance Description), repeated.
  • Affected item — LIN loop with PID, QTY, REF (PO, lot, serial), MEA (out-of-tolerance measurements).
  • Attachment — PWK (Paperwork) for external photo or report.
  • Summary — SE.

Common pitfalls

  • Industry-specific codes: AIAG (auto) and SAE / Boeing (aerospace) require distinct code lists for LQ: use the quality-program code book, not a generic code.
  • Missing lot / serial: without REF*LT (Lot) or REF*SE (Serial), traceability is broken and a recall cannot target the affected lot.
  • Attachment by URL: pre-8010, the 842 references external documents; do not encode binary content in EDI, host photos and measurements separately and point via PWK.

Documentation

The code 842 and the name Nonconformance Report are public and listed on x12.org/products/transaction-sets. AIAG (automotive) and aerospace code books, alongside the full loop structure, are distributed by the relevant industry associations and by DISA via the TR3.