X12 transaction guide · Transportation

EDI 440 Shipment Weights

The X12 document used to transmit weights and scale information between any two interested parties.

Sent by
Shipper, carrier or weighing facility
Received by
Carrier, shipper or other interested party
Standard
ANSI ASC X12

What is an EDI 440?

The EDI 440 Shipment Weights is the ANSI X12 transaction set for transmitting weights and scale information between any two interested parties. It reports gross, tare and net weights for equipment such as rail cars, with the scale and weighing details.

Weights drive freight charges, safety limits and product accounting. In rail and bulk shipping, a shipper or carrier often weighs cars on a track scale and shares the result with the other party so that both bill and record the same figures.

How the EDI 440 worksDiagram of the EDI 440 Shipment Weights. Shipper, carrier or weighing facility sends it to carrier, shipper or other interested party. It usually starts the exchange. It is usually followed by 410 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BW (Beginning Segment for Weight Message Set) and G5 (Scale Information). 0 optional loops are listed by their first segment.How the EDI 440 worksShipment Weights: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 440SENDERShipper, carrier orweighing facilityRECEIVERCarrier, shipper orother interested party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY410Rail Carrier Freight Detailsand Invoice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WRGS … GETransaction set 440ST … SEHEADINGBWBeginning Segment for Weight Message SetG5Scale InformationBlue 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 440. Your trading partner's implementation guide adds its own requirements.
How the EDI 440 worksDiagram of the EDI 440 Shipment Weights. Shipper, carrier or weighing facility sends it to carrier, shipper or other interested party. It usually starts the exchange. It is usually followed by 410 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BW (Beginning Segment for Weight Message Set) and G5 (Scale Information). 0 optional loops are listed by their first segment.How the EDI 440 worksShipment Weights: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 440SENDERShipper, carrieror weighingfacilityRECEIVERCarrier, shipperor otherinterested party997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY410Rail Carrier Freight Details and Invoice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code WR (GS … GE)Transaction set 440 (ST … SE)HEADINGBWBeginning Segment for WeightMessage SetG5Scale InformationBlue 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 440. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 440, 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 440 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 rail car weights from a track scale
  • Sharing weights for freight billing
  • Reporting reweighs after disputes

Where it fits in the document flow

This document 440 Shipment Weights

Structure

Mandatory segments in the 440 (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
  • BW
  • G5
  • SE

Practical example

The 440 in practice

A grain elevator loads 75 hopper cars and weighs each on its certified track scale. It sends the railroad a 440 with each car's initials and number, gross, tare and net weight and the scale used. The railroad uses the weights for its freight bill, and the elevator uses the same figures to invoice the buyer.

Implementation

Implementation considerations for the 440

  • Identify equipment by its reporting marks and number exactly.
  • Include scale and certification details where partners require them.
  • Reconcile weights with bills of lading and invoices.
  • Agree how reweighs and corrections are communicated.

Need help with the EDI 440?

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