X12 segment reference
AK1 — Functional Group Response Header
X12 AK1 in EDI 997 functional acknowledgements: which functional group is being accepted or rejected.
AK1 segment facts
- AK102 group control numbers tie a 997 back to the GS06 you assigned on the original outbound functional group.
- AK101 functional ID must align with the document family you transmitted — PO acks for 850 groups, SH for 856.
- SignalEDI surfaces AK1 correlation fields on webhook payloads so you can match acks to queued API submissions.
What the AK1 segment does
AK1 in a 997 identifies the functional group (GS) being acknowledged. AK102 echoes GS06 so you can correlate responses to outbound batches.
Loop: Once per acknowledged group
Common transaction sets: 997
Key elements
| Element | Name | Description |
|---|---|---|
| AK101 | Functional ID code | PO, SH, IN — mirrors GS01 from the original interchange. |
| AK102 | Group control number | Must match GS06 from the document you sent. |
Example AK1 segment
AK1*PO*1~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Related reference
FAQ
Frequently asked questions
The acknowledgement may be malformed; treat as a parser error and request a resend from the partner.