What is the difference between EDI 204 and EDI 990?

EDI 204 is a Motor Carrier Load Tender sent by a shipper or 3PL offering a shipment to a carrier with stops, dates, and equipment requirements. EDI 990 is the carrier's automated response accepting or declining the tendered load.

What triggers an EDI 214 shipment status message?

EDI 214 status updates are triggered by operational events including driver dispatch (D1), geofenced arrival at shipper (X3), departure with freight (AF), en route check calls (X6), arrival at receiver (X1), and completed delivery with signed POD (CD).

Why is an EDI 997 functional acknowledgment critical in freight operations?

An EDI 997 serves as the cryptographic receipt confirming that the trading partner's EDI translator successfully received and parsed the syntax of a document (such as a 204 tender or 210 invoice) without structural syntax errors.

Does Exspeedite TMS require a third-party VAN or external EDI translator?

No, Exspeedite includes native built-in EDI translation and direct AS2, SFTP, and REST API connectivity, eliminating per-kilo-character VAN transaction fees.

ANSI X12 Standard Reference • Native Exspeedite Translation Engine

Complete Freight EDI Code Dictionary & Segment Reference

The essential engineering reference for transportation Electronic Data Interchange (EDI). Search ANSI X12 transaction sets, segment identifiers, qualifier codes, and shipment milestone status triggers.

EDI 204 Inbound / Outbound

Motor Carrier Load Tender

Sent by shippers, brokers, or 3PLs to tender a freight shipment to a motor carrier. Specifies pickup, delivery, stop sequence, weight, equipment specs, and rate authority.

Key Segments: B2, L11, N1, S5, OID, L5

EDI 990 Outbound Response

Response to a Load Tender

Transmitted automatically by Exspeedite to accept (Code A) or decline (Code D) an EDI 204 load tender, binding the agreement and securing the dispatch record.

Key Segments: B1, N9, V9, K1

EDI 214 Real-Time Telematics

Carrier Shipment Status Message

Delivers automated shipment tracking milestones to shippers. Triggered automatically by Exspeedite via ELD GPS geofences and mobile CheckPoint updates.

Key Segments: B10, LX, AT7, MS1, MS2

EDI 210 Touchless Invoicing

Freight Details & Invoice

Transmits electronic freight billing details, line-item linehaul charges, fuel surcharges, and accessorial fees directly into the customer's accounts payable ERP.

Key Segments: B3, N1, L3, LX, L1

EDI 997 Audit Receipt

Functional Acknowledgment

Cryptographic receipt confirming that a transmission was received and validated against ANSI X12 syntax standards. Tracks accepted (A) or rejected (R) status.

Key Segments: AK1, AK2, AK3, AK5, AK9

EDI 315 Intermodal / Ocean

Status Details (Ocean Container)

Provides vessel discharge, gate-in, and customs hold milestones for marine containers. Powers Exspeedite's Last Free Day (LFD) demurrage countdown clock.

Key Segments: B4, N9, Q2, SG, R4

EDI 322 Terminal Moves

Terminal Operations Activity

Captures terminal gate moves, rail ramps (ingate/outgate), chassis interchanges, and mount/dismount events across marine ports and intermodal inland ramps.

Key Segments: ZR, Q5, W09, N7, R4

EDI 304 Ocean Instructions

Shipping Instructions (Ocean)

Transmits bill of lading instructions from forwarders and shippers to ocean carriers for export cargo bookings, verifying booking numbers and container tare weights.

Key Segments: BA1, Y4, N1, R4, H3

EDI 310 Ocean Freight Invoice

Freight Receipt & Invoice (Ocean)

The ocean carrier's electronic freight invoice detailing ocean freight charges, terminal handling charges (THC), and bunker adjustment factors (BAF).

Key Segments: B3, V1, N1, L3, L1

Segment Tag	Segment Name	Common Sets	Purpose & Architectural Usage	Example Payload
B2	Beginning Segment for Shipment	204	Specifies standard carrier alpha code (SCAC), tender identification number, and payment terms.	B2*EXSPTNDR10049**PP~
B3	Beginning Segment for Invoice	210, 310	Transmits invoice number, invoice date, payment method, net amount due, and delivery date.	B3*INV-89412PO-99120PP20261011285000**20261010~
B10	Beginning Segment for Status	214	Contains reference numbers linking the status update to a shipper's bill of lading and shipment ID.	B10990142BOL-4491*EXSP~
L11	Business Instructions & Reference	204, 214, 210	Provides critical reference numbers: PO (Purchase Order), BM (Bill of Lading), SE (Seal), SI (Shipper ID).	L11PO-994101PO~
N1	Name / Entity Identifier	204, 210, 304	Defines trading entity roles: SH (Shipper), CN (Consignee), BT (Bill-to Party), CA (Carrier).	N1SHMIDWEST LOGISTICS HUB9210491~
S5	Stop-Off Details	204	Specifies stop sequence number, stop reason code (CL: Complete Load, CU: Complete Unload, PL: Part Load).	S51CL42000G800E~
AT7	Shipment Status Details	214	The core milestone event segment in an EDI 214. Contains shipment status code, reason code, date, and time.	AT7AFNS**202610111420*CT~
MS1	Equipment Location	214	Geographic location of the event: City, State, Country code, or GPS latitude/longitude coordinates.	MS1MINNEAPOLISMN*USA~
MS2	Equipment Identifier	214	Carrier alpha prefix and equipment trailer / container number.	MS2EXSP53091~
L1	Rate and Charges	210	Line-item financial billing segment specifying linehaul rates, fuel surcharges, detention, or lumper charges.	L11245000FR245000****405~

Status Code	Status Definition	Trigger Source	Operational Significance	Exspeedite Automation
D1	Driver Dispatched	Exspeedite Fast Dispatch	Driver has been assigned and dispatched to pickup origin.	Instant Trigger
X3	Arrived at Pickup Location	Samsara / Motive Geofence	Vehicle enters geofence of the pickup shipper facility. Detention clock starts.	Auto-Geofence
AF	Departed Origin Terminal / Pickup	Geofence Exit / BOL Upload	Driver leaves pickup geofence with loaded trailer and signed bill of lading.	Auto-Geofence
X6	En Route to Delivery Location	Automated Hourly Breadcrumb	Periodic GPS check-call updating transit coordinates and revised delivery ETA.	60-Min Cron
X1	Arrived at Delivery Location	Receiver Geofence Arrival	Tractor crosses receiver facility geofence. Receiver detention timer initiates.	Auto-Geofence
CD	Carrier Completed Delivery	Mobile POD Scan & Geofence Exit	Freight delivered, POD captured, trailer empty. Triggers EDI 210 invoice generation.	Auto-Billing Run
SD	Shipment Delayed (Exception)	Driver HOS / Traffic Congestion	Operational delay: HOS out-of-hours, mechanical breakdown, or road weather closure.	Dispatcher Alert

Technical EDI Architecture FAQs

How does Exspeedite handle AS2 communication without third-party VAN fees?

Exspeedite deploys an integrated, secure AS2 (Applicability Statement 2) station capable of direct cryptographic EDI envelope transmission using SHA-256 signatures and AES-256 encryption. By establishing point-to-point connections with retail shippers (e.g. Walmart, Target, Home Depot, Amazon), carriers avoid third-party Value Added Network (VAN) per-character fees that often run thousands of dollars per month.

What happens when a trading partner changes their EDI 204 specification guidelines?

Because Exspeedite owns its proprietary translation engine built over 19+ years, custom element maps (such as proprietary L11 reference qualifiers or special N1 loops) are configured directly in your trading partner profile within minutes, without requiring expensive external EDI consultant billable hours.