Acknowledgements
Handle 997 and 999 acknowledgements
Understand 997 functional and 999 implementation acknowledgements — webhook delivery, status lifecycle, and remediation.
Quick answer
How fast do acknowledgements arrive?
Depends on partner mailbox processing. Webhooks fire as soon as SignalEDI parses the inbound ack.
997 vs 999
A 997 confirms syntactic acceptance at the functional group level. A 999 reports richer implementation status — treat them as separate lifecycle checkpoints.
Webhook delivery
Subscribe to document.partner_ack for asynchronous delivery. Payloads include accepted, rejected, or pending states with segment context translated to plain-language hints.
- Self-healing engine surfaces repeatable mapping fixes
- Never reuse ISA/GS control numbers after a hard reject
Retry and exception handling
On reject, update partner mappings or payload fields, then resubmit with fresh control numbers. Keep sandbox and production partners isolated.
FAQ
Common questions
Depends on partner mailbox processing. Webhooks fire as soon as SignalEDI parses the inbound ack.
Branch on the normalized status field in document.partner_ack. Drill into segment detail only when status is rejected.