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 228 Equipment Inspection Report

The X12 document a carrier uses to give equipment owners the results of an inspection, including any damage found.

Sent by
Transportation carrier or terminal
Received by
Equipment owner or lessor
Standard
ANSI ASC X12

What is an EDI 228?

The EDI 228 Equipment Inspection Report is the ANSI X12 transaction set a transportation carrier uses to give equipment owners the results of an equipment inspection. It states whether the equipment is damaged and, if so, describes the damage.

Inspections happen when containers, trailers and chassis are interchanged between parties, so the report helps establish who had the equipment when damage occurred. The 228 does not carry damage claims or repair activity; those use other transaction sets, such as the 412 for repair billing.

How the EDI 228 worksDiagram of the EDI 228 Equipment Inspection Report. Transportation carrier or terminal sends it to equipment owner or lessor. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), Q5 (Status Details) and the required W2 loop with W2 (Equipment Identification) and the required EQD loop with EQD (EQD Equipment Damage Information). 2 optional loops are listed by their first segment.How the EDI 228 worksEquipment Inspection Report: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 228SENDERTransportation carrieror terminalRECEIVEREquipment owner orlessor997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code ENGS … GETransaction set 228ST … SEHEADINGBGNBeginning SegmentQ5Status DetailsRequired loop W2 · repeats up to 1,000W2Equipment IdentificationRequired loop EQD · repeats up to 1,000EQDEQD Equipment Damage Information+ 2 optional loops, starting with:N1NM1Blue 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 228. Your trading partner's implementation guide adds its own requirements.
How the EDI 228 worksDiagram of the EDI 228 Equipment Inspection Report. Transportation carrier or terminal sends it to equipment owner or lessor. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), Q5 (Status Details) and the required W2 loop with W2 (Equipment Identification) and the required EQD loop with EQD (EQD Equipment Damage Information). 2 optional loops are listed by their first segment.How the EDI 228 worksEquipment Inspection Report: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 228SENDERTransportationcarrier orterminalRECEIVEREquipmentowner or lessor997 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 EN (GS … GE)Transaction set 228 (ST … SE)HEADINGBGNBeginning SegmentQ5Status DetailsRequired loop W2 · repeats up to1,000W2Equipment IdentificationRequired loop EQD · repeatsup to 1,000EQDEQD EquipmentDamage Information+ 2 optional loops, starting with:N1NM1Blue 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 228. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 228, 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 228 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

  • Reporting the condition of equipment at interchange
  • Notifying owners of damage found on inspection
  • Recording clean inspections for later reference

Where it fits in the document flow

This document 228 Equipment Inspection Report
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 228 (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
  • BGN
  • Q5
  • W2
  • N1
  • EQD
  • NM1
  • SE

Practical example

The 228 in practice

A container returns to a marine terminal after a drayage move. The terminal's inspector finds a dented side panel and a torn door seal. The terminal sends the container's owner a 228 with the container number, the inspection date and place, and the damage location and type. The owner uses the report to decide on repair and to assign responsibility.

Implementation

Implementation considerations for the 228

  • Record the inspection place, date and interchange parties precisely.
  • Use agreed damage location and type codes, so reports are comparable.
  • Keep inspection reports separate from claims and repair billing.
  • Retain reports as evidence for later disputes.

How ECOM helps

Automate the 228 with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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 228?

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

Request a Demo Contact us