Blogs

Home / Blogs / EDI 997 Functional Acknowledgment

Table of Content
The Automated, No-Code Data Stack

Learn how Astera Data Stack can simplify and streamline your enterprise’s data management.

    EDI 997 Functional Acknowledgment

    June 21st, 2023

    What is an EDI 997 Functional Acknowledgment?

    EDI 997, one of the ANSI X12 transaction sets, is the electronic version of a receipt that is sent in response to an EDI 850 Purchase Order, EDI 810 Invoice, or any other transaction set. The transaction set only notifies the sender that their document had arrived and was processed by the recipient. It does not indicate whether the receiver accepted the order placed or the prices proposed. In some instances, the EDI 997 functional acknowledgment document may indicate the acceptance or rejection of the document sent.

    An EDI 997 document has the following key data elements:

    • AK1 – This is the GS or Group Acknowledgement segment.
    • AK2 – This is the ST or Document Acknowledgment segment.
    • AK3 – This segment reports errors in specific segments of the document received.
    • AK4 – This segment reports errors in specific elements of the document received.
    • AK5 – This segment outlines the type of acknowledgment.
    • AK9 – This is the Group Response segment.

    EDI 997 Functional Acknowledgment Sample

    An EDI 997 transaction document is divided into functional groups that explain the transaction being conducted. A typical document looks like this:

    ST*997*000000001~
    
    AK1*HC*50~
    
    AK2*837*0001~
    
    AK3*PS1*000065**8~
    
    AK4*01*0127*1~
    
    AK3*NM1*000082**8~
    
    AK4*09*0067*2~
    
    AK3*NM1*000120**8~
    
    AK4*09*0067*4*2~
    
    AK3*SV1*000272**8~
    
    AK4*01>02*0234*1~
    
    AK5*R*5~
    
    AK9*R*000001*000001*000 00000001~
    
    SE*0000000012*000000001~

    Workflow for the Exchange of an EDI 997 Functional Acknowledgment

    The process of electronic data interchange of an EDI 997 starts with an 850 purchase order, 810 invoice, or any other document being sent to the trading partner. Upon receiving the EDI document, the trading partner will send a functional acknowledgment document to the sender. This document will serve as the acceptance or rejection notification.

    The typical reasons for the rejection of a purchase order include violation of character length requirements, invalid data, or incomplete or missing data in mandatory segments.

    Achieve EDI Compliance with EDIConnect

    Designed to simplify and expedite the exchange of EDI documents, EDIConnect is an enterprise-ready electronic data interchange software solution that supports the building and parsing of all ANSI X12, EDIFACT, and HIPAA transaction sets. With built-in EDI translation and validation features, as well as the ability to convert EDI files into a range of data formats, EDIConnect makes electronic data interchange a simple task for even business users.

    Here’s how EDIConnect simplifies data exchange for users:

    • It provides a graphical interface that allows users to construct intricate and structured EDI transactions.
    • It accommodates a diverse range of EDI standards, such as ANSI X12, HIPAA, and EDIFACT.
    • It verifies all files against the predefined validation rules, both standard and customized, specific to each trading partner.
    • It handles high volumes of EDI files with efficiency, regardless of their complexity.
    • It automates workflows through the utilization of job scheduling features.
    Become EDI Compliant with EDIConnect

    Authors:

    • Irfan Ahmed
    You MAY ALSO LIKE
    How to Automatically Convert Bank Statements to Excel
    Bank Statement Extraction: Software, Benefits, and Use Cases
    Why Your Organization Should Use AI to Improve Data Quality
    Considering Astera For Your Data Management Needs?

    Establish code-free connectivity with your enterprise applications, databases, and cloud applications to integrate all your data.

    Let’s Connect Now!
    lets-connect