837P Electronic Claims Guide

999 Acknowledgment Guide

A 999 is an implementation acknowledgment. It can indicate whether the submitted transaction set was accepted, accepted with errors noted in some workflows, or rejected based on implementation/syntax edits.

Reviewed September 2026 · Educational reference — verify payer and program requirements.

What to look for

Start with AK1/AK2 context
Review IK3/IK4 for segment/data-element issues
Use IK5/AK9 for status
A 999 is not the same as claim adjudication

Important: a 999 is an implementation acknowledgment, not a payment or coverage decision. A transaction can pass syntax/implementation checks and still have claim-level issues later.

Practical workflow

Start by identifying the transaction, claim or service line that the segment belongs to. Then compare the value or status to the implementation guide, payer companion guide and the source claim. Avoid correcting a raw segment in isolation without understanding the surrounding loop and trading-partner requirement.

Common troubleshooting sequence

Confirm you are reading the correct interchange and transaction set.
Match control numbers, claim identifiers and provider/patient context.
Identify the segment, element or claim-level status that failed.
Correct the source data or file-generation rule rather than only patching the output text.
Regenerate, revalidate and resubmit according to the payer or clearinghouse process.

Open 837P Validator Open Response Reader

Official references

See the CMS Medicare FFS companion guides and Medicare Claims Processing Manual Chapter 24. Trading-partner requirements can differ.