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 868 — Electronic Form Structure

The 868 transmits the structure of an electronic form: fields, validations, layout, between systems or for archive.

Purpose

The 868 documents the definition of an electronic form: list of fields, their types, validations, layout. It serves as a schema exchanged between systems for flows where transactions are not X12-predefined but must follow a specific application template.

It is used in legacy form-based EDI contexts, in interoperability with archival (records management) systems, and in some government environments for federal forms. Acknowledged by 997.

Envelope structure

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

x12 example-868.x12 
ISA*00*          *00*          *ZZ*FORMOWNER     *ZZ*FORMUSER       *260514*1500*U*00401*000000868*0*P*>~
GS*FT*FORMOWNER*FORMUSER*20260514*1500*1*X*004010~
ST*868*0001~
BGN*00*FT-2026-0042*20260514~
REF*ZZ*FORM-ID-VENDOR-INFO-2026~
LX*1~
REF*ZZ*FIELD-VENDOR-NAME~
REF*ZZ*FIELD-TYPE-STRING-100~
LX*2~
REF*ZZ*FIELD-TAX-ID~
REF*ZZ*FIELD-TYPE-EIN-9DIGIT~
SE*9*0001~
GE*1*1~
IEA*1*000000868~

Common segments

  • Header — ST, BGN.
  • Form identification — REF*ZZ (form ID, version).
  • Fields — repeated LX loop per field: REF*ZZ (field name), REF*ZZ (type + constraint), REF*ZZ (validation rule).
  • Layout — MSG or REF*ZZ for positional layout if applicable.
  • Summary — SE.

Common pitfalls

  • Versioning: a form evolves; an 868 without an explicit version leaves consumers unsure whether their parser is current — always qualify REF*ZZ version.
  • Legacy modernization: the 868 is a legacy instrument; for new integrations, prefer JSON Schema, XSD, or OpenAPI over 868.
  • Field encoding: X12 types (AN, N0, R, ID) do not cover all modern cases (UUID, JSON object); a modern 868 often forces extra extensions out-of-spec.

Documentation

The code 868 and the name Electronic Form Structure 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.