EDI 211 Motor Carrier Bill of Lading: Segments and Use Cases
For edi and integration analysts, it leads at shippers, 3pls and carriers · Understand the problem

EDI 211 Motor Carrier Bill of Lading: Segments and Use Cases: Illustrative TMS–ERP order and invoice handoff review beside a warehouse floor; not a client facility.
Quick answer: edi 211 motor carrier bill of lading
The EDI 211 Motor Carrier Bill of Lading is the X12 message a shipper sends a carrier before pickup. BOL carries the bill number and payment terms, N1 loops name shipper, consignee and bill-to, and AT1, AT4 and AT2 hold each line, with AT2 giving handling units, weight, NMFC item and class. L5 and AT8 belong to the 204 tender.
TL;DR — what you’ll learn
- BOL02 decides who is invoiced (PP, CC or TP), and a TP bill needs its own N1 BT loop or the carrier will usually bill the shipper.
- Freight detail sits in AT2, elements AT201 to AT210; mapping from a cloned 204 that expects L5 and AT8 drops the commodity data.
- Populate AT201 and AT205 from the WMS load confirmation; one illustrative order-based count produced a 19 percent weight variance and a $200.40 correction.
- India has no 211: the goods forwarding note and the lorry receipt issued in triplicate under the Carriage by Road Act 2007 feed e-way bill Part B above ₹50,000.
Topics: edi 211 motor carrier bill of lading · x12 211 segments · 211 vs vics bill of lading · edi 211 at2 segment · electronic bill of lading ltl
All quantities, amounts, product codes and events are illustrative teaching examples.
The driver arrives at door 7 with a printed bill that says six pallets, the warehouse loaded four, and the carrier's terminal re-keys whatever the dock clerk scrawled. Three weeks later the freight invoice arrives with a reweigh, a reclass and a bill-to address that belongs to the consignee. Every one of those errors started as a field nobody owned on the bill of lading.
The X12 211 Motor Carrier Bill of Lading moves that document to the carrier as data before pickup, so the carrier can pre-rate the shipment, print the PRO label and bill the right party. Mapped well, it removes re-keying at the terminal and gives freight audit a shipper-declared baseline to compare against the carrier's invoice.
- What follows: the 211's segments in X12 version 004010, the elements that drive billing and rating, a complete sample transaction, and a field map from the paper VICS bill of lading.
- Beyond the glossary: what each mistake costs in the warehouse, in freight audit and, for Indian operations, in the lorry receipt and e-way bill that play the same role there.
What the 211 carries and why carriers ask for it before pickup
The 211 is the shipper's bill of lading sent electronically to a motor carrier, usually a less-than-truckload carrier, ahead of pickup. The X12 purpose statement limits it to providing a legal bill of lading for a shipment and excludes load tenders, pickup manifests and appointment scheduling, which have their own transaction sets.
That boundary matters when integration teams pick a message. A truckload move is offered with the 204 Motor Carrier Load Tender, whose purpose statement in turn excludes less-than-truckload bills of lading. A shipper with many daily LTL pickups for one carrier may use the 215 pickup manifest. The 211 sits between them: one shipment, one bill, sent once and changed only through its purpose code.
- Carrier benefit: the terminal receives weights, handling units and classes before the truck arrives, so it can plan linehaul and pre-rate instead of keying from paper.
- Shipper benefit: the declared data becomes a dated record that freight audit can hold the carrier's invoice against.
- Shared benefit: the carrier's PRO number, returned on the bill or a later status message, links the shipper's BOL number to every downstream event.
Our page on automating bill-of-lading preparation with a versioned review queue covers the approval workflow for a draft bill before it is released. This article is narrower: the 211's structure and what each field does once a carrier receives it.
BOL, B2A and N1: identifying the shipment and who pays
Three heading-level choices decide most billing outcomes: the payment method in BOL02, the purpose code in B2A01, and which N1 party is marked as bill-to. Get those right and most invoice disputes become pricing questions rather than "who owes this" questions.
Scroll horizontally to see all columns.
| Element | Name | Format | What the carrier does with it |
|---|---|---|---|
| BOL01 | Standard Carrier Alpha Code | ID, 2 to 4 | Confirms the bill reached the intended carrier |
| BOL02 | Shipment Method of Payment | ID, 2 (PP prepaid, CC collect, TP third party) | Decides whether shipper, consignee or a third party is invoiced |
| BOL03 | Shipment Identification Number | AN, 1 to 30, usually the BOL number | Primary key for matching status messages and invoices |
| BOL04, BOL05 | Pickup date and time | CCYYMMDD, HHMM | Dispatch planning and the date on the carrier's receipt |
| BOL06 | Reference Identification | AN, 1 to 30, usually the PRO number | Carrier-assigned tracking number when pre-assigned |
| B2A01 | Transaction Set Purpose Code | ID, 2 (00 original, 01 cancellation, 04 change, 05 replace) | Whether to create, cancel or overwrite the bill |
| N101 | Entity Identifier Code | SH shipper, CN consignee, BT bill-to, PF freight bill recipient | Names each party; BT and PF route the invoice |
The party loop repeats up to ten times, so one bill can name a ship-from location (SF), a ship-to (ST), the legal shipper and consignee, and a third-party payer. Send the bill-to as its own N1 loop with full N3 and N4 address lines whenever BOL02 is TP. Carriers that cannot find a BT party typically invoice the shipper, which turns a prepaid-by-customer arrangement into a collections problem.
The heading area also holds L11 references such as the purchase order number, up to six G62 date and time segments, AT5 handling requirements and K1 remarks. AT5 allows either a coded special handling or service request, or a free-text description, but not both in the same segment, which is a common reason a translator rejects an otherwise valid bill.
Line items: AT1, AT2 and AT4 instead of L5 and AT8
In the 211, freight detail sits in the AT1 line-item loop, not in the L5 and AT8 segments many mappers expect. L5 and AT8 belong to the 204 load tender; the 211 in versions 004010 and 005010 uses AT1 for the line number, AT4 for the lading description and AT2 for counts, weight, NMFC number and class.
AT2 carries the numbers that drive rating. AT201 is the count of carrier handling units and AT202 their packaging form, such as PLT for pallets. AT205 is the weight, qualified by AT203 and AT204. When AT202 is PLT, SKD or SLP, AT206 and AT207 give the pieces on those units, and AT208 tells the carrier whether to verify that piece count. AT209 holds the NMFC item and AT210 the freight class.
- Handling units first: AT201 is what the driver counts at the door, so it must come from the warehouse's loaded pallet count, not from the order's ordered quantity.
- Weight source: AT205 should be the scaled weight from the dock or the system weight with the pallet included, and AT204 must say L for pounds or K for kilograms.
- Classification fields: AT209 and AT210 must match the item master. Since NMFTA's Docket 2025-1 took effect on 19 July 2025, many items rate by density, which our page on NMFC density-based classification changes covers.
- Description: AT401 allows 50 characters and is described as the item description required for rating and billing, so it should match the NMFC description, not the marketing name of the product.
Hazardous materials have their own loops inside each line: a G61 emergency contact, LH6 certification and up to 25 LH1 to LHT loops for identification, class and shipping name. The US hazardous materials shipping paper rules still apply to the printed bill the driver carries, so treat the EDI as a copy of that paper, not a substitute for it.
A complete sample 211 for one LTL pickup, segment by segment
A minimal valid 211 for a single-line prepaid shipment needs only about fifteen segments. The sample below uses version 004010 element order, with the interchange and group envelopes omitted. Names, the carrier code and the NMFC item are illustrative.
ST*211*0001~
BOL*ABCD*PP*00141411234567890*20261113*1430~
B2A*00~
L11*4500098123*PO~
N1*SH*NORTHFIELD SUPPLY DC~
N3*1200 INDUSTRIAL PKWY~
N4*COLUMBUS*OH*43228~
N1*CN*LAKESIDE RETAIL DC 14~
N3*88 COMMERCE DR~
N4*INDIANAPOLIS*IN*46241~
N1*BT*NORTHFIELD SUPPLY ACCOUNTS PAYABLE~
AT1*1~
AT4*PLASTIC STORAGE BINS NESTED~
AT2*4*PLT*G*L*1800*96*CTN*N*123456*70~
SE*15*0001~
Reading the AT2 line:
AT201 = 4 handling units AT202 = PLT pallets
AT203 = G gross weight AT204 = L pounds
AT205 = 1800 weight AT206 = 96 pieces on the pallets
AT207 = CTN cartons AT208 = N carrier need not verify carton count
AT209 = 123456 NMFC item (illustrative) AT210 = 70 freight class
SE01 counts every segment from ST to SE inclusive.
BOL03 here is a 17-digit VICS-style bill number: a seven-digit company prefix, a nine-digit serial and a check digit. The GS1 US Bill of Lading Guideline, which succeeded the VICS guideline, has made that standard number a mandatory part of the standard bill since 1 July 2003 and recommends keeping each number unique for 24 months, which is also a sensible duplicate-check window for the translator.
An EDI 211 Motor Carrier Bill of Lading in X12 version 004010 carries handling units, gross weight, NMFC item and freight class in segment AT2, elements AT201 to AT210; freight audit should compare AT205 with the carrier's billed weight and flag any difference above 5 percent before the 210 invoice is approved.
Mapping the paper VICS bill to 211 fields and naming an owner
Every box on the paper bill should map to one 211 element with one owner who supplies it. The federal minimum for the carrier's receipt is short, but the VICS bill and the 211 carry far more, and unowned fields are where errors start.
Under 49 CFR 373.101, a motor carrier's receipt or bill of lading must show the consignor and consignee, origin and destination, the number of packages, a description of the freight, and its weight, volume or measurement where that affects the rate. The VICS bill, now published by GS1 US, adds trailer and seal numbers, the SCAC, the PRO, freight charge terms, COD terms and NMFC item and class for LTL.
Scroll horizontally to see all columns.
| VICS bill box | 211 element | Required by 49 CFR 373.101 | Source system | Owner and sign-off |
|---|---|---|---|---|
| Bill of lading number | BOL03 | No | WMS or TMS number range | Shipping supervisor |
| Ship from, ship to | N1 SH or SF and CN or ST loops | Yes (consignor, consignee, origin, destination) | Order and location master | Customer service lead |
| Third party freight charges bill to | N1 BT loop | No | Customer terms in the ERP | Credit or AR manager |
| Freight charge terms | BOL02 | No | Order freight terms | Transport planner |
| Handling unit quantity and type | AT201, AT202 | Yes (number of packages) | WMS load confirmation | Dock lead, at loading |
| Weight | AT203 to AT205 | Yes, where it affects rating | Dock scale or WMS weight | Dock lead |
| Commodity description, NMFC number, class | AT401, AT209, AT210 | Yes (description) | Item master | Master data owner, approved by transport manager |
| Trailer and seal numbers | Not in the core 211 segments; agree an L11 qualifier with the carrier | No | Yard or dock system | Yard or dock lead |
Bill of lading mapping for the X12 211 must cover the five items 49 CFR 373.101 requires on a motor carrier receipt: consignor and consignee, origin and destination, number of packages, freight description, and rating weight or measure, sourced from the WMS load confirmation rather than the sales order.
Where the core structure has no obvious home for a VICS field, such as seal numbers, agree the L11 reference qualifier with each carrier in writing rather than guessing. An undocumented qualifier is accepted by the translator and then ignored by the carrier, which is worse than an outright rejection.
Where a wrong 211 field surfaces in warehouse, audit and claims
A 211 error rarely fails at transmission; it fails days later as a reweigh, a misdirected invoice or a weak claim. The incident below shows one shipment with an unowned handling unit count and weight, traced from the dock to the freight invoice. Identifiers and figures are illustrative.
- Tuesday 13:52, bill sent: The TMS builds BOL 00141411234567890 from the sales order and sends a 211 with AT201 of 4 pallets and AT205 of 1,800 lb, taken from item master weights without pallets.
- Tuesday 14:30, pickup: The WMS load confirmation shows 5 pallets because one SKU was split. The driver signs the paper bill showing 4, with "freight counted by shipper" ticked.
- Wednesday 06:15, terminal inspection: The carrier's dimensioner records 5 pallets and 2,150 lb, and the density places the shipment above class 70. An inspection correction is issued against PRO 4471-22918.
- Friday 11:05, invoice: The carrier's 210 bills at the corrected weight and class plus an inspection fee. Freight audit compares it with the 211 baseline and flags a 19 percent weight variance.
- Controlled version: The WMS load confirmation, not the order, populates AT201 and AT205 at door close; a rule blocks sending when the loaded count differs from the order count without a reason code, and the bill goes out with 5 pallets and 2,150 lb.
For the carrier side of the same conversation, our page on reconciling 214 status and 210 freight invoices covers matching those corrections back to the bill. The point here is that the 211 is only a useful baseline when its counts come from the dock rather than from the order.
Cost of one wrong field: a reclass in dollars and a held truck in rupees
The 211 is a US and Canadian motor freight standard; Indian road freight does not use it. The comparison below therefore sets a US reclass caused by bad AT2 data against the Indian equivalent, a consignment held because the lorry receipt and e-way bill did not match the vehicle. All rates and charges are illustrative.
Scroll horizontally to see all columns.
| Line | US LTL shipment (USD) | Indian road consignment (INR) |
|---|---|---|
| Declared on the shipper's document | 4 pallets, 1,800 lb, class 70 on the 211 | 18 packages, 2,450 kg, value ₹4,20,000 on the goods forwarding note and e-way bill |
| What went wrong | Actual 5 pallets, 2,150 lb, higher density class | Vehicle changed at the hub; e-way bill Part B not updated |
| Charge as declared | 18 cwt × $22.90 = $412.20 | Agreed freight ₹21,500 |
| Charge after correction or delay | 21.5 cwt × $26.40 = $567.60 | Detention 9 h × ₹650 = ₹5,850 |
| Fees added | Inspection fee $45.00 | Missed unloading slot, re-delivery ₹3,500 |
| Cost of the error per shipment | $567.60 + $45.00 − $412.20 = $200.40 | ₹5,850 + ₹3,500 = ₹9,350 |
| Annual exposure at the stated error rate | 3% of 4,000 shipments = 120 × $200.40 = $24,048 | 1.5% of 6,000 consignments = 90 × ₹9,350 = ₹8,41,500 |
Neither figure includes the internal time spent disputing the charge, which is usually larger than the charge itself. That is why the strongest business case for a 211, or for its Indian counterpart controls, rests on avoided disputes rather than on saved keying time.
India: goods receipt, forwarding note and e-way bill Part B
Indian road freight has no X12 211, but the same two documents exist in law. Under the Carriage by Road Act, 2007, the consignor executes a goods forwarding note and the common carrier issues a goods receipt, commonly called the lorry receipt or LR. The e-way bill then ties that receipt to the vehicle.
Section 8 requires the goods forwarding note to declare the consignment's value and any goods of a dangerous or hazardous nature, makes the consignor responsible for the correctness of its particulars, and requires the consignor to indemnify the carrier for incorrect or incomplete details. Functionally, that note plays the role the 211 plays in the US: the shipper's declaration.
- Goods receipt timing: Section 9 requires the carrier to issue the goods receipt on completion of loading where the consignor loads, or on acceptance of the goods otherwise.
- Copies and evidence: The goods receipt is issued in triplicate with the original to the consignor, and it is prima facie evidence of the weight or measure, other particulars and number of packages stated in it.
- Liability statement: The goods receipt must include the carrier's undertaking about liability under section 10 or section 11 of the Act.
- Claim notice: Section 16 bars a suit for loss or damage unless written notice reaches the carrier within 180 days of booking.
GST adds the movement layer. CGST Rule 138 requires an e-way bill for consignments above ₹50,000, and the transport document number in Part B of FORM GST EWB-01 is the goods receipt number for road movements. Rule 138A then requires the person in charge of the conveyance to carry the invoice, bill of supply or delivery challan, and the e-way bill in physical, electronic or RFID-mapped form.
An Indian road consignment's lorry receipt, issued in triplicate under section 9 of the Carriage by Road Act 2007, supplies the transport document number in Part B of FORM GST EWB-01; above ₹50,000 under CGST Rule 138, a vehicle change without a Part B update leaves the e-way bill naming the wrong truck.
Our page on generating e-way bills from e-invoice IRNs explains the Part B data flow in detail. For a shipper running both markets, the practical design is one internal shipment record that feeds a 211 for US carriers and a goods forwarding note plus e-way bill Part A for Indian carriers, with the carrier's PRO or LR number written back to the same record.
Which 211 checks are fixed rules and where a person reviews
Structural validation and count reconciliation should be automatic and blocking. Classification judgements, reading a carrier's handwritten exception on a paper bill and resolving a disputed reclass need a person, with software assembling evidence.
Scroll horizontally to see all columns.
| Task | Fixed rule | Where software or AI assists a person |
|---|---|---|
| Rejecting a 211 with AT206 but no AT207 | Yes, X12 syntax rule P0607 | None needed |
| Blocking a bill whose AT201 differs from the WMS loaded pallet count | Yes, unless a reason code is entered | Suggesting the likely split SKU |
| Checking BOL03 uniqueness over 24 months | Yes, translator duplicate check | None needed |
| Choosing the NMFC item and class for a new SKU | No | Proposing an item from the product description and measured density for the transport manager to approve |
| Reading a driver's exception note on a scanned paper bill | No | Extracting the note and the signed counts for a clerk to confirm |
| Matching the LR number to e-way bill Part B after a vehicle change | Yes, vehicle and LR must match before the truck leaves the hub | Alerting the hub supervisor when a change is logged in the yard system |
| Accepting or disputing a carrier inspection correction | No | Assembling the 211, dock scale photo and dimensioner record |
Onboarding a carrier on the 211 without breaking billing
Treat each carrier as a separate implementation, because carriers differ on which optional segments they read, how they return the PRO and how they handle changes. A short test cycle with real shipments catches most of the expensive problems before go-live.
Scroll horizontally to see all columns.
| Checkpoint | Pass condition | Evidence to keep | Owner |
|---|---|---|---|
| Version and guide | Both sides use the same X12 version and the carrier's own 211 guide | Signed implementation guide | EDI analyst |
| Bill-to routing | A TP test bill is invoiced to the BT party, not the shipper | Test invoice | AR manager |
| Change handling | B2A 04 and 01 behaviour agreed with a pickup-day cut-off | Trading partner agreement clause | Transport manager |
| Counts from the dock | AT201 and AT205 populated from WMS load confirmation | Ten shipments compared with signed bills | Warehouse operations lead |
| PRO return | Carrier PRO written back to the shipment within one hour of pickup | Status message log | EDI analyst |
| Hazardous lines | Hazmat loop matches the printed shipping paper | Side-by-side test bill | Hazmat coordinator |
| Audit baseline | Freight audit compares AT205 and AT210 with each 210 invoice | Variance report | Freight audit lead |
The 211 is one message in a chain that runs from tender to invoice; the logistics and supply chain library covers the others. If you are planning a carrier EDI programme or a TMS change that includes bill-of-lading messaging, you can outline your carriers and volumes through our request for proposal form.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Common operational questions
Practical answers for operations, engineering, and finance teams working on edi 211 motor carrier bill of lading in logistics & supply chain.
What is the difference between an EDI 211 and an EDI 204?
Which 211 segment carries weight, freight class and NMFC number?
Does sending a 211 replace the paper bill of lading the driver signs?
What is the Indian equivalent of an EDI 211 bill of lading?
References
Sources checked 13 November 2026. US and India statutory authorities and vendor documentation support platform facts; the worked examples and diagrams are original.
- X12 211 Motor Carrier Bill of Lading, version 004010 - transaction set structure and purpose (Stedi X12 reference)Segment order, loops and the purpose statement. Element detail checked on the BOL, B2A, AT1, AT2, AT4 and AT5 segment pages and code lists for elements 98, 146 and 353. Accessed 13 November 2026.
- X12 211 Motor Carrier Bill of Lading, version 005010 - transaction set structure (Stedi X12 reference)Confirms L5 and AT8 are not part of the 211 structure in 005010. Accessed 13 November 2026.
- X12 204 Motor Carrier Load Tender, version 004010 - transaction set structure (Stedi X12 reference)L5 and AT8 positions in the 204 and its purpose statement excluding LTL bills of lading. Accessed 13 November 2026.
- US Code of Federal Regulations - 49 CFR 373.101, Motor carrier bills of ladingMinimum contents of the motor carrier's receipt or bill of lading. Accessed 13 November 2026.
- GS1 US - Bill of Lading Guideline R4.0 (6 April 2015), successor to the VICS Voluntary Guidelines for the Bill of LadingAccessed 13 November 2026. Standard bill layout, 17-digit BOL number mandatory from 1 July 2003, example of a seven-digit company prefix with a nine-digit serial and check digit, 24-month uniqueness retention, and trailer, seal, SCAC, PRO, COD and NMFC fields.
- NMFTA - NMFTA implements historic NMFC changes (Docket 2025-1)Effective date of 19 July 2025 for the Docket 2025-1 classification changes. Accessed 13 November 2026.
- Government of India (India Code) - The Carriage by Road Act, 2007 (Act 41 of 2007), sections 2, 8, 9 and 16Accessed 13 November 2026. Official gazetted text on India Code. India Code refuses automated downloads, so the section 8 goods forwarding note and section 9 goods receipt in triplicate, original to the consignor, were checked through the search-index text of this file.
- CBIC - CGST Rules 2017, Rule 138 (e-way bill) and Rule 138A (documents to be carried in a conveyance)Accessed 13 November 2026. Rule 138A sub-rule (1) documents; Rule 138 ₹50,000 threshold checked on the companion Rule 138 page.
- CBEC - Notification 27/2017-Central Tax (30 August 2017), FORM GST EWB-01 as notifiedAccessed 13 November 2026. Note 2 to FORM GST EWB-01: the transport document number means the goods receipt, railway receipt, airway bill or bill of lading number.
- ASC X12 — EDI Supply Chain & Transportation Transaction Sets (204/210/214/856/940/945)US standard for electronic data interchange across shippers, 3PLs, and motor carriers.
- FMCSA — 49 CFR Part 395 Hours of Service & Electronic Logging Devices (ELD)US federal motor carrier dispatch and driver duty-status compliance mandate.
- ULIP & NIC GST E-Way Bill Portal — Unified Logistics & Rule 138 ComplianceIndian statutory goods-in-transit and multi-modal logistics verification framework.