Read and understand a 999 file

Information

After importing a 999, you may get a rejection and a list of errors.

The first 3 columns tell you where specifically in the file the errors occurred. You will need to open the 837 file in a text editor assuring that you line break for each segment. After you have inserted your line breaks, remove the ISA and GS Segments. From there, use your text editor's Go To feature to go to the line number representing the "Segment Position" number in the error report. Then view the "Position in Segment" number to indicate which position to look at. Segment positions are broken by the *

You'll then need to view the errors returned in the "Segment Error Description" and "Data Error Code" columns. Below is a list of all you may receive what what they generally mean. 

Segment Error Descriptions

• 1 = Unrecognized segment ID
• 2 = Unexpected segment
• 3 = Required segment missing
• 4 = Loop occurs over maximum times
• 5 = Segment exceeds maximum use
• 6 = Segment not in defined transaction set
• 7 = Segment not in proper sequence
• 8 = Segment has data element errors
• I4 = Implementation “Not Used” segment present
• I6 = Implementation dependent segment missing
• I7 = Implementation loop occurs under minimum times
• I8 = Implementation segment below minimum use
• I9 = Implementation dependent “Not Used” segment present

Data Error Codes

• 1 = Required Data Element Missing
• 2 = Conditional Required Data Element Missing
• 3 = Too many data elements
• 4 = Data Element Too Short
• 5 = Data Element Too Long
• 6 = Invalid Character in Data Element
• 7 = Invalid Code Value
• 8 = Invalid Date
• 9 = Invalid Time
• 10 = Exclusion Condition Violated
• 12 = Too many repetitions
• 13 = Too many components
• I11 = Implementation too few repetitions
• I12 = Implementation Pattern Match Failure
• I13 = Implementation Dependent "Not Used" Data Element Present
• I6 = Code Value Not Used in Implementation
• I9 = Implementation Dependent Data Element Missing