Cords

We Make EDI Integration Easy


Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

>>  Request a Demo
>>  Map Your Ideal Integration



 
What is a 926 - Claim Status Report and Tracer Reply document?

The 926 EDI document type is an electronic version of a paper Claim Status Report and Tracer Reply. Standard EDI formats include X12, ANSI, EDIFACT and its subsets. The 926 EDI document type is used to report the status of a claim to a claimant or reply to a 925 Claim Tracer from a claimant.

What makes up the 926 - Claim Status Report and Tracer Reply document?

An EDI 926 - Claim Status Report and Tracer Reply document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. There are an infinite number of possibilities available for a company to include data on an 926 Claim Status Report and Tracer Reply. There are an infinite number of possibilities available for a company to include data on an 926 - Claim Status Report and Tracer Reply.

How is a 926 - Claim Status Report and Tracer Reply used?

The 926 Claim Status Report and Tracer Reply is transmitted by the carrier in response to any one of a 920, 924, or 925 EDI document. After the 926 Claim Status Report and Tracer Reply is received, a 997 Functional Acknowledgement is sent back from the claimant indicating that the Claim Status Report and Tracer Reply was successfully received.

How is a 926 - Claim Status Report and Tracer Reply processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.