top of page

997 FA

Purpose

 

The EASI 997 Functional Acknowledgment is an electronic response to an EASI document that was sent from one trading partner to another.  This electronic receipt notification advises the sending trading partner whether or not the receiving trading partner successfully received their file.  

 

As an example, when a Purchaser sends a Seller an EASI 940 Drop Ship Purchase Order, the Seller can send the Purchaser an EASI 997 Functional Acknowledgement to indicate that the Drop Ship Purchase Order was successfully received.  Similarly, when a Seller sends a Purchaser an EASI 810 Invoice, the Purchaser can send the Seller an EASI 997 Functional Acknowledgement to indicate that the Invoice was successfully received. 

 

997 Functional Acknowledgement - "Did you receive my order?"

 

 

The Functional Acknowledgement is a small file, but an integral part of successful communication between trading partners exchanging critical, and perhaps time sensitive, electronic documents.  The 997 confirms the receipt of a specific routing envelope, as identified by sender ID, recipient ID, creation date, creation time, and the distinct interchange ID.  The 997 makes no reference to the file or files within the routing envelope.

 

 

The 997 is not intended to be human readable, but rather should be used programmatically to update the status of the routing envelope within a log or database.  Routing envelopes not acknowledged after a specified period could be retransmitted until a 997 is received.  

 

 

Of perhaps even greater benefit is a reporting tool utilizing the database and allowing interested parties to view the status of routing envelopes and their respective files.  Having a tool to access status information is more efficient than making a phone call, for both trading partners.  The ?acknowledged? or ?received? status answers the question: ?did you receive my order??

 

 

The 997 is a valuable tool.  The efficiency achieved by using it is related to the degree of automation in processing it and the ease and timeliness with which the status information is provided to the parties who need it.

 

Exported by the Seller and Purchaser

 

Imported by the Seller and Purchaser

 

Key Elements

 

  • Sender details (DUNS Number)

  • Receiver details (DUNS Number)

  • Date and Time details of the file that was received

  • Interchange ID details of the file that was received (unique identifier)

  • Acknowledgement Status (Codes: Accepted, Accepted but Errors Noted, or Rejected)

 

Specific Benefits for Sellers

 

  • Opportunity to reduce administrative expenses associated with manual follow-up or tracking procedures

  • Opportunity for improved visibility and accountability with regards to transmitted data and trading partners

  • Opportunity to identify EASI transmission problems / issues

 

Specific Benefits for Purchasers

 

  • Opportunity to reduce administrative expenses associated with manual follow-up or tracking procedures

  • Opportunity for improved visibility and accountability with regards to transmitted data and trading partners

  • Opportunity to identify EASI transmission problems / issues

 

EASI Mapping Documents

 

Download the standard: EASI 997 Functional Acknowledgment Standard

​

Download the sample: EASI 997 v2.0 Sample File (no routing envelope)

 

Download a previous version: EASI 997 v1.0 Functional Acknolwedgement Standard
Download the sample file: EASI 997  v1.0 Sample File

bottom of page