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 925 - Claim Tracer document?
The 925 EDI document type is an electronic version of a paper Claim Tracer. Standard EDI formats include X12, ANSI, EDIFACT and its subsets.
The 925 EDI document type is used to request the status of a loss or damage claim.
What makes up the 925 - Claim Tracer document?
An EDI 925 - Claim Tracer 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 925 Claim Tracer. There are an infinite number of possibilities available for a company to include data on an 925 - Claim Tracer.
How is a 925 - Claim Tracer used?
The 925 Claim Tracer is transmitted by the claimant to a carrier after the claimant has sent a 920 or 924 EDI document. After the 925 Claim Tracer is received, a 997 Functional Acknowledgement is sent back from the carrier indicating that the Claim Tracer was successfully received, and will respond with a 926 Claim Status Report and Tracer Reply.
How is a 925 - Claim Tracer 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.