Overview
Understanding XPO integration
Who this is for: Shippers and accounts payable teams that move less-than-truckload freight with XPO and want pickups, shipment status, invoices and payment remittance automated.
Scope: This guide covers XPO LTL, as described in XPO's LTL help center. XPO's brokerage and contract logistics businesses are now separate companies with their own channels.
If you ship LTL freight with XPO, the exchange that matters is the shipment record you send and the status and invoice you get back. XPO's LTL help center lists the X12 documents it uses: the 204 or 211 from the customer to request a pickup and send the bill of lading, the 990 response from XPO (with a reason if a pickup is declined), 214 status messages, the 210 invoice for any LTL shipment, and the 820 payment remittance from the customer. The 997 acknowledgment is used in both directions.
XPO says it can trade any EDI version up to and including 4010, supports SFTP, AS2 and a VAN, and starts onboarding with a form sent to its LTL EDI onboarding team, followed by testing and a move to production. During invoice testing, XPO sends both paper and EDI invoices so you can compare them. XPO also recommends pairing EFT or ACH payment with the 820.
ECOM maps these documents to your TMS, ERP and accounts payable system, builds the connection, runs test cycles with XPO, and monitors every file after go-live. Shippers get fewer manual pickup bookings, status that updates customer service systems, and invoices checked against your rates before payment.