Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
ST — Transaction Set Header
The ST segment identifies the X12 transaction set (850, 856, 810, 997) and assigns the ST control number used in acknowledgements.
ST segment facts
- ST01 identifies the business document type — parsers route 850 traffic differently from 856 or 810.
- ST02 control numbers must be unique within each GS functional group to keep 997 acknowledgements unambiguous.
- HIPAA transaction sets add ST03 implementation convention references that retail-only guides often omit.
What the ST segment does
ST opens each transaction set inside a functional group. ST01 is the transaction set identifier; ST02 is the control number partners reference in 997 AK2 loops.
Loop: Once per transaction set
Key elements
| Element | Name | Description |
|---|---|---|
| ST01 | Transaction set identifier | 850, 856, 810, 997, etc. |
| ST02 | Transaction set control number | Must be unique within the GS group; echoed in 997 AK2. |
| ST03 | Implementation convention | Optional for retail; required for HIPAA (e.g. 005010X222A1). |
Example ST segment
ST*850*0001~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Related reference
FAQ
Frequently asked questions
Partners correlate AK2 acknowledgement loops to ST02 control numbers from your outbound document.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”