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 242 — Data Status Tracking

The 242 transmits a data tracking status between systems: ack, processing, completed, failed — to orchestrate multi-step EDI chains.

Purpose

The 242 documents the status of a dataset or file in an EDI processing chain: received, in validation, validated, queued, failed. It differs from the 997 (syntactic transactional ack) in that it carries a fine-grained application status on dataset-level data.

It is used in contexts where several processing steps exist between transaction reception and business consumption (e.g., load, validate, enrich, queue for downstream). Acknowledged by 997. Multiple 242s may be issued on the same file as processing progresses.

Envelope structure

The 242 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group DS, and ST/SE). Didactic example in release 004010:

x12 example-242.x12 
ISA*00*          *00*          *ZZ*UPSTREAMSYS   *ZZ*DOWNSTREAMSYS  *260514*1200*U*00401*000000242*0*P*>~
GS*DS*UPSTREAMSYS*DOWNSTREAMSYS*20260514*1200*1*X*004010~
ST*242*0001~
BGN*00*DS-2026-0042*20260514~
REF*ZZ*FILE-204-2026-05-14-001~
MSG*VALIDATED - QUEUED FOR DOWNSTREAM~
DTM*009*20260514~
SE*7*0001~
GE*1*1~
IEA*1*000000242~

Common segments

  • Header — ST, BGN.
  • Dataset reference — REF*ZZ (file / dataset identifier).
  • Status — MSG or qualified LQ: RECEIVED, VALIDATING, VALIDATED, QUEUED, FAILED, COMPLETED.
  • Timing — DTM*009 (status datetime).
  • Summary — SE.

Common pitfalls

  • 242 vs 997: confusing both makes a 997 ACK look like business processing confirmation; the 997 only confirms syntax — the 242 carries the application status.
  • Status ordering: a 242 FAILED after a 242 COMPLETED indicates either re-processing or corruption — always timestamp precisely with DTM*009 to the second.
  • Stable reference: REF*ZZ must be idempotent on a single dataset; without it, multiple systems tracing the same file produce uncorrelatable status trees.

Documentation

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