X12
Outbound

LogiFlow X12 210 Motor Carrier Freight Details and Invoice

LogiFlow
The EDI 210 Freight Invoice is submitted by carriers to bill LogiFlow for completed shipments. It includes freight charges, accessorial fees, fuel surcharges, and references to the original load tender.
16segments
2loops
5mandatory

Schema Reference

16 segments · X12 210 Motor Carrier Freight Details and Invoice

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
B3 Beginning Segment for Carrier's Invoice
Mandatory Max: 1
B302 Invoice Number
M AN 1-22
B303 Shipment Identification Number
O AN 1-30
B304 Shipment Method of Payment
M ID 2-2
B306 Date
M DT 8-8
B307 Net Amount Due
M N2 1-12
B309 Delivery Date
C DT 8-8
B310 Date/Time Qualifier
C ID 3-3
B311 Standard Carrier Alpha Code
M ID 2-4
C3 Currency
Optional Max: 1
C301 Currency Code
M ID 3-3
N9 Reference Identification
Optional Max: 300
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
N1 Loop Repeat: 10
N1 Name
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
O ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
O ID 2-3
LX Loop Repeat: 9,999
LX Assigned Number
Optional Max: 1
LX01 Assigned Number
M N0 1-6
L5 Description, Marks and Numbers
Optional Max: 30
L501 Lading Line Item Number
O N0 1-3
L502 Lading Description
O AN 1-50
L0 Line Item - Quantity and Weight
Optional Max: 10
L001 Lading Line Item Number
O N0 1-3
L002 Billed/Rated-as Quantity
C R 1-11
L003 Billed/Rated-as Qualifier
C ID 2-2
L004 Weight
C R 1-10
L005 Weight Qualifier
C ID 1-2
L008 Lading Quantity
C N0 1-7
L009 Packaging Form Code
C ID 3-3
L011 Weight Unit Code
O ID 1-1
L1 Rate and Charges
Optional Max: 10
L101 Lading Line Item Number
O N0 1-3
L102 Freight Rate
C R 1-9
L103 Rate/Value Qualifier
C ID 2-2
L104 Charge
C N2 1-12
L105 Advances
C N2 1-9
L106 Prepaid Amount
C N2 1-9
L107 Rate Combination Point Code
O AN 3-9
L108 Special Charge or Allowance Code
O ID 3-3
L112 Special Charge Description
O AN 2-25
L7 Tariff Reference
Optional Max: 10
L701 Lading Line Item Number
O N0 1-3
L707 Freight Class Code
O AN 2-5
L3 Total Weight and Charges
Optional Max: 1
L301 Weight
C R 1-10
L302 Weight Qualifier
C ID 1-2
L305 Charge
O N2 1-12
L311 Lading Quantity
O N0 1-7
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating LogiFlow EDI 210

Stacksync validates, transforms, and delivers your 210 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync generates 210 Freight Invoices from your TMS billing data and submits them to LogiFlow — with rate details, accessorial charges, and load references mapped automatically.

LogiFlow EDI 210 FAQ

Common questions about 210 Motor Carrier Freight Details and Invoice transactions with LogiFlow.

How long does it take to set up LogiFlow EDI with Stacksync?

Most suppliers are fully connected and processing live LogiFlow EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with LogiFlow?

No. Stacksync handles the entire EDI transport layer. We connect directly to LogiFlow's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with LogiFlow compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for LogiFlow?

Stacksync supports all EDI document types required by LogiFlow — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect LogiFlow EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between LogiFlow's EDI network and your system in real time.

What happens when LogiFlow updates their EDI specifications?

Stacksync monitors LogiFlow's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.