X12 transaction guide · Transportation

EDI 225 Response to a Cartage Work Assignment

The X12 document a cartage carrier uses to accept or decline a cartage work assignment and return its references.

Sent by
Cartage (drayage) carrier
Received by
The party that issued the work assignment
Standard
ANSI ASC X12

What is an EDI 225?

The EDI 225 Response to a Cartage Work Assignment is the ANSI X12 transaction set a cartage carrier uses to respond to a cartage work assignment (222). It states whether the carrier accepts or declines the assignment and returns any related reference numbers.

The response is small, but timing matters: a declined or unanswered assignment leaves a container at a ramp or port, where storage and demurrage charges accrue. Issuers use 225s to see quickly which moves still need a carrier.

How the EDI 225 worksDiagram of the EDI 225 Response to a Cartage Work Assignment. Cartage (drayage) carrier sends it to the party that issued the work assignment. It usually follows 222. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: SCP (Beginning Segment for a Cartage Work Assignment Response). 0 optional loops are listed by their first segment.How the EDI 225 worksResponse to a Cartage Work Assignment: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS222Cartage Work AssignmentEDI 225SENDERCartage (drayage)carrierRECEIVERThe party that issuedthe work assignment997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MYGS … GETransaction set 225ST … SEHEADINGSCPBeginning Segment for a Cartage Work Assignment ResponseBlue 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 225. Your trading partner's implementation guide adds its own requirements.
How the EDI 225 worksDiagram of the EDI 225 Response to a Cartage Work Assignment. Cartage (drayage) carrier sends it to the party that issued the work assignment. It usually follows 222. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: SCP (Beginning Segment for a Cartage Work Assignment Response). 0 optional loops are listed by their first segment.How the EDI 225 worksResponse to a Cartage Work Assignment: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS222Cartage Work AssignmentEDI 225SENDERCartage(drayage)carrierRECEIVERThe party thatissued the workassignment997 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 MY (GS … GE)Transaction set 225 (ST … SE)HEADINGSCPBeginning Segment for aCartage Work AssignmentResponseBlue 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 225. Your trading partner'simplementation guide adds its own requirements.

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

  • Accepting a drayage move
  • Declining an assignment the carrier cannot cover
  • Returning the carrier's own reference for the move

Where it fits in the document flow

Usually follows 222 Cartage Work Assignment
This document 225 Response to a Cartage Work Assignment
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 225 (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
  • SCP
  • SE

Practical example

The 225 in practice

A drayage company receives 30 work assignments for the next day. It accepts 27 with 225 responses carrying its dispatch numbers and declines three for which it has no chassis. The issuer reassigns the three declined moves to another drayage partner within the hour.

Implementation

Implementation considerations for the 225

  • Respond to every assignment, including declines, within the agreed time.
  • Return the assignment reference exactly as received.
  • Feed declines to the people who can reassign the move.
  • Use the carrier's reference in later status and billing messages.

Need help with the EDI 225?

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