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 102 — Associated Data

The 102 conveys technical data (files, references, indicators) linked to other X12 transactions in the same envelope.

Purpose

Support transaction: carries supplementary data (justification PDF, audit log, reference file) attached to another transaction in the same functional group. Heavily used in US banking/healthcare for justification propagation.

Envelope structure

The 102 travels inside the three X12 envelope levels (ISA/IEA, GS/GE with functional group AD, and ST/SE). Didactic example in 004010:

x12 example-102.x12 
ISA*00*          *00*          *ZZ*ACMESENDER    *ZZ*ACMERCVR      *260516*1030*U*00401*000000102*0*P*>~
GS*AD*ACMESENDER*ACMERCVR*20260516*1030*1*X*004010~
ST*102*0001~
BHT*0001*00*REF102*20260516*1030~
REF*BM*PARENT-TX-12345~
BIN*512*[binary blob omitted]~
SE*5*0001~
GE*1*1~
IEA*1*000000102~

Common segments

  • Header — ST, BHT (Beginning of Hierarchical Transaction).
  • Reference — REF pointant la transaction parente.
  • Payload — BIN (Binary Data) ou BDS (Binary Data Structure).
  • Summary — SE.

Common pitfalls

  • BIN without parent REF: data is orphaned, impossible to correlate.
  • Oversized BIN: some gateways cap at 1 MB.
  • Encoding not specified: no Content-Type — receiver must guess if PDF, XML, image.

Documentation

The 102 code and the Associated Data name are public and listed at x12.org/products/transaction-sets. The full loops/qualifiers/code-lists structure is distributed by DISA via proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.