EDI documents
Understand the transaction before you map it
Review the primary X12 documents used across transportation, billing, status, and acknowledgment workflows.
204
Load tender
Used by a shipper, broker, or other party to offer shipment information and instructions to a motor carrier.
View document guide214
Shipment status
Used to communicate shipment-status events and progress updates between transportation partners.
View document guide212
Trailer manifest
Used to communicate shipment and delivery information for freight contained on a trailer.
View document guide210
Freight invoice
Used by a carrier to submit freight charges and shipment-related invoice information.
View document guide990
Tender response
Used by a carrier to accept or decline a load tender.
View document guide997
Functional acknowledgment
Used to confirm that an EDI message was received and structurally processed. It does not confirm completion of the underlying business transaction.
View document guide810
Commercial invoice
Used to exchange invoice details between trading partners for goods or services.
View document guide820
Payment and remittance
Used to communicate payment instructions or remittance details so accounting teams can match funds to invoices and shipments.
View document guide211
Motor carrier bill of lading
Used to send bill-of-lading details for a motor-carrier shipment, including parties, references, freight, and routing information.
View document guideNeed another transaction set?
Select “Other” when signing up and describe the document you need. We’ll confirm support after reviewing your requirements.
Your next step
Ready to start EDI?
Tell us what you need to connect. We’ll help you work through the details.
