972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 926 Claim Status Report and Tracer Reply

The X12 document a carrier uses to report the status of a claim to the claimant or to reply to a claim tracer.

Sent by
Transportation carrier
Received by
Claimant
Standard
ANSI ASC X12

What is an EDI 926?

The EDI 926 Claim Status Report and Tracer Reply is the ANSI X12 transaction set a carrier uses to report the status of a claim to the claimant or to reply to a claim tracer (925). It can acknowledge a new claim, report that it is under investigation, or report that it has been paid, partly paid or declined, with reasons.

Claimants use 926 data to update their claim records, recognize recoveries in finance and decide whether to appeal declined claims.

How the EDI 926 worksDiagram of the EDI 926 Claim Status Report and Tracer Reply. Transportation carrier sends it to claimant. It usually follows 920, 924 and 925. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required F11 loop with F11 (Status). 0 optional loops are listed by their first segment.How the EDI 926 worksClaim Status Report and Tracer Reply: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS920Loss or Damage Claim -General Commodities924Loss or Damage Claim -Motor Vehicle925Claim TracerEDI 926SENDERTransportation carrierRECEIVERClaimant997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code GCGS … GETransaction set 926ST … SEHEADINGRequired loop F11 · repeats up to 500F11StatusBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 926. Your trading partner's implementation guide adds its own requirements.
How the EDI 926 worksDiagram of the EDI 926 Claim Status Report and Tracer Reply. Transportation carrier sends it to claimant. It usually follows 920, 924 and 925. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required F11 loop with F11 (Status). 0 optional loops are listed by their first segment.How the EDI 926 worksClaim Status Report and Tracer Reply: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS920Loss or Damage Claim - GeneralCommodities924Loss or Damage Claim - Motor Vehicle925Claim TracerEDI 926SENDERTransportationcarrierRECEIVERClaimant997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code GC (GS … GE)Transaction set 926 (ST … SE)HEADINGRequired loop F11 · repeats up to500F11StatusBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 926. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 926, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 926 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Acknowledging a new claim
  • Replying to a claim tracer
  • Reporting payment or declination of a claim

Where it fits in the document flow

Usually follows 920 Loss or Damage Claim - General Commodities924 Loss or Damage Claim - Motor Vehicle925 Claim Tracer
This document 926 Claim Status Report and Tracer Reply
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 926 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • F11
  • SE

Practical example

The 926 in practice

A carrier completes its investigation of a damage claim and agrees to pay part of the amount. It sends the shipper a 926 with the claim number, the amount allowed, the amount declined and the reason. The shipper's claims system records the recovery and flags the declined portion for review.

Implementation

Implementation considerations for the 926

  • Report reasons for partial payments and declinations.
  • Reference the claimant's claim identifiers as well as the carrier's.
  • Reconcile reported payments with the funds received.
  • Respond to tracers within the agreed time.

How ECOM helps

Automate the 926 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 926?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us