Carriers integration

XPO LTL EDI: pickups, status, invoices and remittance

A guide for shippers sending LTL pickup requests and bills of lading to XPO and receiving status, invoices and responses back, with 820 remittance on the payment side.

At a glance

XPO integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific XPO program or a customer relationship.

Illustration of a freight truck on a highway, representing the carriers industry that XPO operates in.
Industry. Carriers: where XPO operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with XPO through ECOM. You send 204, 211, 820; you receive 990, 214, 210; 997 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor XPO 204 211 820 204 211 820 990 214 210 990 214 210 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Tenders and invoices re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about XPO

Tell us which documents you exchange with XPO, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with XPO.

  • Review of XPO's requirements with you, once you have them
  • EDI and API integration with your TMS, ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
XPO

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How XPO integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringSFTP · AS2 · VAN
XPOIts program, documents and requirements
  1. ConfirmConfirm your XPO program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

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.

Business scenarios

Where XPO integration gets complicated

Typical requirements—confirm with your trading partner.

Pickup requests from your TMS

Warehouses and customer service teams book LTL pickups many times a day, and each pickup needs a bill of lading.

How ECOM helps: ECOM maps pickup and bill of lading data from your TMS or ERP to the XPO 204 or 211 and tracks the 990 response and any declined pickups.

What you gain: Fewer rekeyed bookings and early notice when a pickup is not accepted.

Invoice audit and remittance

LTL invoices carry accessorial charges that must be checked against your rates, and XPO asks that payments be explained with an 820 remittance.

How ECOM helps: ECOM matches each 210 to the shipment and agreed rate, lists charges that differ, and builds the 820 remittance with the invoice and PRO numbers.

What you gain: Fewer overcharges paid and payments that XPO can apply without calls.

Workflows

Typical XPO business workflows

The steps summarize the documents below. Where a step is not in XPO's published documents, it reflects common practice.

LTL shipment to payment

  1. 1Send 204 or 211 pickup request
  2. 2Receive 990 response
  3. 3Receive 214 status
  4. 4Receive 210 invoice
  5. 5Send 820 remittance

Documents and APIs

XPO documents by program

Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from XPO's published documents cited below; documents marked general guidance are common in this industry but not confirmed for XPO.

DocumentNameDirectionProgramStatusPurpose
204 Motor Carrier Load Tender To XPO XPO LTL EDI Named; level not stated The shipper requests an LTL pickup. XPO uses the 204 and 211 interchangeably.
211 Motor Carrier Bill of Lading To XPO XPO LTL EDI Named; level not stated The shipper sends the electronic bill of lading for the shipment.
990 Response to a Load Tender From XPO XPO LTL EDI Named; level not stated XPO responds to the pickup request and gives a reason if it is declined.
214 Transportation Carrier Shipment Status Message From XPO XPO LTL EDI Named; level not stated XPO reports pickup, estimated delivery and delivery status.
210 Motor Carrier Freight Details and Invoice From XPO XPO LTL EDI Named; level not stated XPO bills the shipper for any LTL shipment.
820 Payment Order/Remittance Advice To XPO XPO LTL EDI Named; level not stated The shipper sends payment remittance detail, including invoice or PRO numbers and amounts.
997 Functional Acknowledgment Both directions XPO LTL EDI Named; level not stated Confirms that each file was received.

Connectivity

How companies connect

  • SFTP

    XPO lists SFTP as a secure file transfer option with no cost once established.

    From XPO's published documents

  • AS2

    XPO lists AS2, based on EDIINT specifications, with no cost once established.

    From XPO's published documents

  • VAN

    XPO also exchanges EDI through a value-added network. Each side pays its own network charges.

    From XPO's published documents

Challenges

Common integration challenges

  • Pickup and bill of lading data

    Rating and billing depend on correct weights, classes and accessorials in the 204 or 211.

  • Status gaps

    Missing or late 214 messages hide delays. Status must be tied to the right order for customer service.

  • LTL invoice audit

    Accessorial charges and reweigh adjustments must be checked against agreed rates before payment.

  • EDI version

    XPO's help center names version 4010 as the limit in one place and 4010 or higher in another, so the version is confirmed during onboarding.

Automation options for XPO shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. XPO sets its own requirements; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Zero Trust for freight data exchange

Zero Trust EDI and MFT for your XPO connection

Freight exchanges with XPO carry tenders, status events, rates and freight invoices. A Zero Trust design assumes no connection, file or user is safe by default.

ECOM has implemented Zero Trust EDI and Zero Trust MFT in trucking.

For freight exchanges this means each carrier has its own scope, tenders, status messages and invoices are checked at the connection and the file, a late or missing file is noticed early, and every transfer has a record for freight billing disputes and security reviews.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up tenders, status or freight billing.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Carrier onboarding

Each carrier or broker gets its own identity and scope. A new carrier is tested before it reaches production, and a removed carrier loses access without affecting the others.

Tenders, status and invoices

Load tenders, status messages and freight invoices are checked at the connection and the file, and every transfer is logged.

Rates and contract data

Rate and accessorial files are limited to the roles that need them.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. XPO may set its own security requirements, which come first.

General EDI flow

How EDI with XPO typically works

The documents, their order and the timing are XPO's to set; this is the general sequence most programs of this kind follow.

  1. 204 Motor Carrier Load Tender

    From you to XPO

    The shipper requests an LTL pickup. XPO uses the 204 and 211 interchangeably.

  2. 211 Motor Carrier Bill of Lading

    From you to XPO

    The shipper sends the electronic bill of lading for the shipment.

  3. 990 Response to a Load Tender

    From XPO to you

    XPO responds to the pickup request and gives a reason if it is declined.

  4. 214 Transportation Carrier Shipment Status Message

    From XPO to you

    XPO reports pickup, estimated delivery and delivery status.

  5. 210 Motor Carrier Freight Details and Invoice

    From XPO to you

    XPO bills the shipper for any LTL shipment.

  6. 820 Payment Order/Remittance Advice

    From you to XPO

    The shipper sends payment remittance detail, including invoice or PRO numbers and amounts.

  7. 997 Functional Acknowledgment

    Both directions

    Confirms that each file was received.

Working from XPO's published specification?

Tell ECOM which program and documents apply to you. We read the published specification with you, map it to your systems and test against it. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your XPO program

Each request goes to an ECOM EDI specialist with XPO's name attached, so the reply starts from your program.

  • Review XPO's requirements

    Send us XPO's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect XPO to your ERP

    Tenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each XPO document, then go live with monitoring from the first file.

    Plan testing and certification

XPO integration FAQs

Which EDI documents does XPO LTL use?

XPO's LTL help center lists the 204 or 211 pickup request and bill of lading, the 990 response, 214 status, the 210 invoice, the 820 remittance and the 997 acknowledgment.

How does onboarding with XPO LTL work?

You submit XPO's onboarding form to its LTL EDI team. An analyst is assigned, reviews your requirements, arranges testing, and XPO moves you to production when both sides approve the test data.

Which connection methods does XPO support?

XPO lists SFTP, AS2 and a VAN for EDI. Its help center does not describe an API option, so confirm that with XPO if you need one.

Does this guide cover XPO's brokerage or contract logistics?

No. It covers XPO LTL. Brokerage and contract logistics are now separate companies and use their own onboarding.

Is ECOM an XPO partner?

This is an independent integration guide. It does not indicate an endorsement, partnership or approval by XPO.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. XPO sets its own requirements and can change them at any time; your XPO implementation guide, supplier portal or account contact is the authoritative source for your program.

Request XPO integration assistance

Tell us about your XPO program, documents and ERP. We will outline the connection, mapping and testing plan.