T-Sets | ANSI X12 997

The American National Standards Institute X12 (ANSI X12) is one of the most critical standards available in Electronic Data Interchange (EDI). Though we’ve previously provided an in-depth guide to the ANSI X12 message, there are a large range of codes that go within this message that also warrant an explainer.

Today, we want to focus on the ANSI X12 997 transaction set (T-set). We’ll cover its main benefits, structure and processing, and best practices for navigating one of the many EDI T-sets available.

What is an ANSI X12 997 T-set?

The ANSI X12 997 T-set acts as the technical and functional acknowledgement that an ANSI X12 message has been received and accepted. 

The ANSI X12 997 message is a key component in maintaining streamlined communications for businesses. As its main function is to confirm the receipt of data, this T-set plays an essential role in assuring message integrity and effective communication protocols in B2B transactions.

Benefits and drawbacks of an ANSI X12 997 message

Every technology has its strengths and weaknesses. But when it comes to the ANSI X12 997 message, the benefits far outweigh the challenges:

The ANSI X12 997 T-Set, also known as the Functional Acknowledgement (FA), provides several key benefits:

  1. Improved tracking: By providing a record of transaction receipt, the 997 helps in tracking the status and timing of EDI transmission.
  2. Aids in compliance: It plays a crucial role in partner compliance as it is often required in EDI relationships.
  3. Automated verifications: As it is an automated response, it helps in reducing manual efforts in confirming transaction receipts.
  4. Enhanced communications: 997 provides a structured format for acknowledgements, improving consistency and reliability in B2B communications.
  5. Error management: The message reports any syntactical errors found in the received EDI transmission, ensuring data integrity. If any errors are detected, the parties involved can quickly correct them, improving efficiency and reducing potential costs or delays.

By integrating ANSI X12 997 in your EDI communication network, you can enhance how you communicate with partners, see greater operational efficiency and ultimately boost your bottom line and workflows.

The primary challenge of ANSI X12 997 comes down to its complexity. Factors like missing or invalid data can lead to the message being rejected. Properly implementing this T-set requires a certain degree of technical knowledge that can be daunting for businesses that are new to EDI. The best option is to look towards a trusted EDI managed services provider for help.

Structure of an ANSI X12 997 message

A typical ANSI X12 997 message would usually be structured with the following segments:

An actual INVOIC message (using the above placeholder examples) would look something like this:

ISAInterchange Control Header: Marks the beginning of an interchange and provides authorisation and security information.
GSFunctional Group Header: Marks the beginning of a functional group and provides control and application identifier information.
STTransaction Set Header: Signals the start of the transaction set and identifies the set.
AK1Functional Group Response Header: Provides a summary acknowledgment for a functional group.
AK2-AK5Transaction Set Response Header and Summary: Provides acknowledgment for a specific transaction set within the functional group. AK2 identifies the transaction set, and AK5 provides the summary acknowledgment.
AK9Functional Group Response Trailer: Provides a summary acknowledgment for the functional group.
SETransaction Set Trailer: Marks the end of the transaction set and verifies the integrity of the transaction set.
GEFunctional Group Trailer: Marks the end of a functional group and verifies the integrity of the functional group.
IEAInterchange Control Trailer: Marks the end of an interchange and verifies the integrity of the interchange data.

It’s also worth clarifying that what’s included in the message will depend on whether it’s acting as a technical response or a functional response (both interchangeably known as technical acknowledgements or functional acknowledgements, respectively.)

Technical acknowledgement: This is the acknowledgment that an electronic message was received and didn’t contain any syntax errors. It would include the AK1, AK2, and AK5 segments, giving the recipient details into  the previous interchange, including whether it was accepted, and the message type and ID.

Functional acknowledgement: This goes slightly more in-depth compared to a technical acknowledgement, as it informs the sender whether the recipient has processed the document. It’s worth noting that a functional response does not necessarily mean that the transaction was successfully processed — just that it was successfully received and processed to the point it could be analysed. This would also include the AK3 and AK4 segments, providing more detail into what led to potential errors behind the message.

How an ANSI X12 997 T-Set is processed

The processing of the ANSI X12 997 T-set follows four major steps:

  1. Sending of the original EDI document: The sender prepares and sends an EDI document, such as a Purchase Order (EDI 850), to a trading partner.
  2. Receipt and processing of the original EDI document: The receiving system accepts the incoming EDI document and performs an initial inspection for syntax errors.
  3. Generation of the 997 Functional Acknowledgment: If the document passes the syntax checks, the receiving system generates a 997 Functional Acknowledgment. The generated 997 will contain information about the acceptance or rejection of the received document based on the correctness of its format.
  4. Sending of the 997 Functional Acknowledgment: The 997 Functional Acknowledgment is sent back to the original sender. This informs them that their EDI document was received and whether it passed or failed the syntax checks.
  5. Reception and processing of the 997 Functional Acknowledgment by the sender: The sender receives the 997 Functional Acknowledgment and processes it to understand if their original EDI document was accepted or rejected.
  6. Addressing errors (if any): If the 997 indicates that the original EDI document was rejected due to syntax errors, the sender will investigate and correct the errors. The corrected document is then sent again to the trading partner, restarting the process from step 1.

Equivalents to other EDI standards

While the ANSI X12 standard is most common in the NAFTA region, it’s important to have an understanding of how it compares to messages in other EDI standards.

EDI standardEquivalent to ANSI X12 997
RosettaNetReceipt Acknowledgment / Acceptance Acknowledgment
VDAVDA 4913/VDA 4915

How Data Interchange can help

Understanding and implementing ANSI X12 997 can seem complex, but leveraging this powerful tool can be made seamless with the right partner.

At Data Interchange, we offer a robust portfolio of professional services, software, and managed services to help businesses address EDI. Solutions like our EDI via VAN (Value-Added Network) private network, capable of hosting tools like EDI mapping software, can help you increase efficiency, improve operational speed, and responsiveness to your clients’ needs. 

From an essential implementation like ANSI X12 997 to customised solutions, Data Interchange can deliver EDI support that meets your unique requirements, even under tight timelines.

To find out more about how we can assist your business, just get in touch with our team of experts!

1  How EDI Powers the Supply Chain

Transform your approach to supply chain management

Talk to an Expert

    Epicor values your privacy. Website terms and conditions.


    ANSI X12 EDI 865 T-Set: Structure, Benefits & Use Cases

    The VDA 4987 Message: Structure, Benefits & Use Cases

    ANSI X12 EDI 850 T-Set: Structure, Benefits & Use Cases

    The VDA 4938 Message: Structure, Benefits & Use Cases

    The EDIFACT DELJIT T-Set: Structure, Benefits & Use Cases

    The EDIFACT DELFOR T-Set: Structure, Benefits & Use Cases

    The VDA 4915 Message Explained

    The VDA 4905 Message Explained

    T-Sets | ANSI X12 810

    How to optimise your EDI and ERP system integration



    Exploring Cloud EDI Services in ERP: Architecture, Security, and Scalability

    VDA Explained: Message Standards and Transaction Sets

    ANSI X12 Explained: Message Standards and Transaction Sets

    EDIFACT Explained: Message Standards and Transaction Sets

    The Power of Web EDI for Global Supply Chains

    How to Get the Most Out of AS2

    How EDI Simplifies Transactions in the Manufacturing Sector

    Why Your Automotive Supply Chain Needs an OFTP2 Connection

    Digital Supply Chain Trends Impacting 2023 and Beyond

    How to Manage Global Supply Chain Complexities

    How to Overcome Supply Chain Risk

    What is the Future of Supply Chain Management in 2023?

    How to Improve your Supply Chain Strategy

    Why Scalable EDI is Integral to Rapid Business Growth

    How to Pick the Right EDI File Transfer Protocol

    An Introduction to OFTP2 (Odette File Transfer Protocol)

    What are the Costs of EDI Implementation?

    What is PEPPOL?

    A Guide to EDI Protocols

    EDI VAN Costs: Get the Right Solution for your Business

    How Much Does EDI Cost?

    How Do On-Premise EDI Solutions Work?

    Our Plan at Data Interchange to Change EDI and Supply Chain Management

    Integrating EDI with your ERP

    In-house vs Managed Service EDI

    What is an API Integration? And how does it affect EDI?

    Epicor Acquires EDI Provider Data Interchange

    6 Benefits of EDI in the Logistics Industry

    4 Challenges Facing the Logistics Industry and How to Overcome Them

    Top EDI Solution Providers in 2023

    Solving Supply Chain Problems in the Logistics Industry

    B2B EDI Integration Best Practices in 2023

    How to Choose The Right EDI Provider in 2022

    Supply Chain Analytics Trends in 2022

    Future-proof your business: Take Advantage of Market Growth

    Announcement: Andrew Filby becomes CEO of Data Interchange

    7 Advantages of EDI in The Automotive Industry

    Consumer Expectations cause Demand for Integrated Data

    How to Optimise Your Automotive Supply Chain Processes

    Post-Pandemic Supply Chain Challenges Increase the Pressure

    EDI Made Simple for the Automotive Industry

    Overcoming Supply Chain Visibility Issues in the Automotive Industry

    Complex Supply Chain Problems and Simple Solutions

    Supply Chain Flexibility: Why your customers need it

    5 Automotive Supply Chain Challenges Facing the Industry

    Supplier Performance Management Reimagined in 2023

    How to Unite Emerging Supply Chain Management Technology Trends

    Meet the Team: Marketing

    Supplier Management Best Practices after COVID-19

    The Future of EDI: Looking Beyond 2025

    The top three supply chain data exchange requirements

    The Advantages of EDI in E-Commerce: How to Gain a Competitive Advantage Online in 2021

    A Crash Course on EDI Industry Standards: ANSI x12 vs EDIFACT vs OFTP and more

    What is EDI Mapping?

    What is EDI: The History and Future of Electronic Data Interchange

    The Future of the Automotive Supply Chain

    Supplier Relationship Management: How to reduce risk and improve performance

    How EDI-as-a-Service Changes Supply Chain Best Practices in 2021

    Agile Supplier Onboarding: Supply Chain Security in Uncertain Times

    The impact of failed EDI on Supply Chain

    Cloud-Based EDI Solutions vs On-Premise

    Different Types of EDI Compared

    5 Most Common EDI Implementation Issues and How to Solve Them

    Are your EDI documents ready for the new EU/UK customs border?

    B2B Integration Challenges

    EDI vs API: Bridge the B2B connectivity gap

    Ten things to look for in an EDI Managed Service Provider

    World Mental Health Day 2020

    Logicalis & Data Interchange – partnering for success

    EDI – A data integration service critical to business success

    Joining forces with SnapLogic: bringing together market leading iPaaS and EDI solutions

    Joining Data Interchange: My lockdown experience

    Data Interchange announces strategic partnership with SmarterPay

    Access new trading partners quickly for COVID-19 support

    Keeping supply chains moving

    Our Web EDI solution gets a makeover

    Coronavirus: Our Business Continuity Plan

    With love from Data Interchange ♥

    A new decade, renewed ambition and the next generation

    Brexit and EDI

    Data Interchange transform their Support service for an improved customer experience

    Interview: An update on Data Interchange’s new CEO, Robert Steiner

    Data Interchange appoints Robert Steiner as new CEO

    MQ messages over ENX – Renault

    Five key questions for your EDI provider

    Data Interchange at the Odette Conference 2018

    How to select the right EDI provider

    Future proof your EDI and unleash growth

    EDI: the Supply chain performance enhancer

    Taking cost out of the chain

    Non-EDI users held up in the mail

    Over 41% of companies at risk without EDI

    ​Consolidating VAN providers

    Increase visibility and productivity of supply chain logistics with Data Interchange’s B2B integration solutions

    Data Interchange wins large business of the year award

    Data Interchange launch new Support Portal

    Data Interchange will be showcasing our EDI solution offerings and promoting the benefits of MMOG/LE

    Metaldyne receive special recognition from Ford for 11th consecutive year

    Making the move to cloud based EDI Solutions

    Top 5 reasons to switch to EDI Managed Services

    Data Interchange to power QAD Managed EDI On Demand