This article is a reference for the EDI transaction types supported in Load Manager and the logs used to review EDI activity. Use it when you need to understand what each EDI document does or where to check whether EDI activity was recorded.
| Transaction | Direction | Purpose | Common Load Manager Use |
|---|---|---|---|
| EDI 204 | Inbound | Load tender | The customer sends a load tender so a load can be created from EDI data. |
| EDI 990 | Outbound | Tender response | Load Manager sends an accept or reject response for the tender. |
| EDI 214 | Outbound | Shipment status update | Load Manager sends shipment progress or location updates to the customer. |
| EDI 210 | Outbound | Freight invoice | Invoice information is sent electronically when the trading partner requires it. |
| EDI 810 | Outbound | Customer invoice | Customer invoice information is sent electronically for EDI-enabled customers. |
Screen cue: the EDI Loads screen shows pending, missing, and received EDI activity.
A typical EDI workflow may look like this:
Screen cue: use Logs to confirm whether Load Manager recorded the expected EDI or load activity.
The EDI Log shows recorded EDI activity across supported transaction types.
The EDI Log table includes Load #, BOL #, Doc Type, Action, Customer, and Date / Time. These fields help confirm whether a transaction was recorded and which load or customer it belongs to.
The EDI Log menu includes a Location Updates option for EDI 214 monitoring. Use this screen when you need to review shipment update activity and compliance for EDI 214 loads.
The EDI 214 Location Updates table includes Load #, BOL #, Updates, KPI, Customer, Carrier, Driver, Driver Cell, and Date / Time. The KPI value is based on the number of updates compared with the tracking time window for the load.
Outbound EDI activity can depend on customer-level settings. On the customer profile, Load Manager includes EDI options such as Send EDI 214 and Send EDI 810.
If these options are not enabled for the customer, the expected outbound EDI messages may not generate for that customer.