999 acknowledgment

The 999 answers one narrow question: is this file built correctly? Medicare contractors use it to report the transaction-level errors their translators find, and to confirm receipt of files with no syntax errors unless the submitter has asked not to get those confirmations. Each transaction set in the file is accepted, accepted with errors noted, or rejected. Medicare calls the middle result a 999E: the set goes on, and the flagged claims come back later on the 277CA. A rejected set stops at the door, so none of the claims inside it reach the payer’s claims system. HIPAA does not require the 999, but Medicare uses it, in version 005010X231A1, alongside the TA1 and the 277CA¹.

Because it works at the file level, a clean 999 says nothing about whether each claim will pass the payer’s business edits. CMS describes the checks in order: errors against the basic HIPAA standard reject the whole batch, implementation guide errors reject individual claims, and coverage and payment policy edits come after that².

The costly mistake is never downloading it. Medicare contractors may purge an unretrieved 999 from the submitter’s mailbox after five business days, though they are encouraged to keep it for 30, and they do not have to recreate one once it is gone. If a 999 was missed, a claim status request shows whether the payer has the claim; a response with no record suggests a front-end rejection, and the claim can be resubmitted¹.