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
AK9 — Functional Group Response Trailer
X12 AK9 segment in 997 acknowledgements: functional group disposition — accepted, partially accepted, or rejected.
AK9 segment facts
- AK901 P (partially accepted) means some transaction sets in the group failed — resend only the rejected ST control numbers.
- AK903 vs AK902 mismatch indicates the partner received fewer sets than you claimed in GE01.
- SignalEDI classifies AK9 disposition in webhook payloads so operators see group status without reading raw 997.
What the AK9 segment does
AK9 summarizes the entire functional group's disposition after all AK2 loops. AK901 A/E/P/R tells integrators whether any transaction set in the group failed.
Loop: Once per 997, after AK2 loops
Common transaction sets: 997
Key elements
| Element | Name | Description |
|---|---|---|
| AK901 | Functional group acknowledgement code | A=accepted, E=accepted but errors, P=partially accepted, R=rejected. |
| AK902 | Number of transaction sets included | Count of ST sets acknowledged in the group. |
| AK903 | Number received | How many sets the partner actually received. |
| AK904 | Number accepted | Sets accepted without fatal errors. |
Example AK9 segment
AK9*A*1*1*1~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common AK9 errors
- P partial acceptance ignored — some sets still need resend
- R with no AK2 detail parsed
Related reference
FAQ
Frequently asked questions
Scan AK9 for group-level failure, then drill into AK5/AK4 for transaction and element detail.
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.”