Interpret file acknowledgements ACK

How to interpret file acknowledgements in EDI.

File acknowledgements are available in a formatted text version that is easy to read. The data file version of this file is intended to be imported into computers, although technical personnel may be able to view and interpret them.

File acknowledgements are delivered only when Availity rejected the transmission file in the first step of validation, usually due to an unacceptable file format.

  1. Open the negative file acknowledgement and look at line 1E for the error.
  2. See below for troubleshooting the error displayed in 1E.
  3. After successfully troubleshooting and correcting the problem, rebatch the entire transmission file in your PMS, HIS, or other system and resubmit it to Availity, using a new interchange control number. Be sure that all control segments adhere to Availity's requirements for X12 files, as specified in the section on Control segments/envelopes.
  4. If the error is not covered below or you are unable to resolve the problem, contact Availity Client Services for assistance.

Availity does not recognize the interchange data starting at position 0 as valid

Cause

This error is usually caused by one of the following conditions:

  • File does not begin with ISA.

  • Invalid ISA segment due to invalid numbers of spaces or characters in one or more data elements.

    Note: The ISA segment is the only fixed-length record in the X12 transaction. The total length of the ISA segment must be 106 characters, and all elements must have exactly the specified number of spaces or characters.

  • Incorrect control segment identifier; for example, specifying a GE segment where an SE segment is expected.

  • Missing control segments; for example, missing a trailer segment for an ISA, GS or ST segment.

  • Invalid paragraph returns inserted into the transaction file, particularly in the control segments.