Overview
Understanding Southeastern Freight Lines integration
Who this is for: Shippers, brokers and logistics teams that ship less-than-truckload freight with Southeastern Freight Lines, and the transportation, IT and finance staff who connect those shipments to a TMS or ERP.
Scope: The six transaction sets come from the SEFL EDI page, which shows no date or X12 version. Acknowledgments, connection methods and test steps are typical practice.
Shippers that use Southeastern Freight Lines (SEFL) for LTL need pickup requests and bills of lading to reach the carrier, status events to come back to the TMS, and freight bills and remittances to reconcile in payables without keying bill numbers.
SEFL publishes an EDI page that it describes as suited for large to medium customers. It lists ANSI transaction sets for the load tender or LTL pickup request (204), tender response (990), bill of lading (211), shipment status (214), freight bill invoice (210) and electronic payment remittance (820). The page does not state a date or the X12 version.
ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications. It then monitors every file after go-live and handles partner changes, as software, as a managed service or both.