Arcbest via Mercury Gate EDI 210 Freight Invoice

Schema Reference

21 segments · X12 210 Motor Carrier Freight Details and Invoice

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

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

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

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

B311 Standard Carrier Alpha Code

M ID 2-4

B312 Date

O DT 8-8

C301 Currency Code

M ID 3-3

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

R304 Transportation Method/Type Code

O ID 1-2

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N104 Identification Code

C AN 2-80

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

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

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

SPO Loop Repeat: 999,999

SPO01 Purchase Order Number

M AN 1-22

LX Loop Repeat: 9,999

LX01 Assigned Number

M N0 1-6

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

L001 Lading Line Item Number

O N0 1-3

L004 Weight

C R 1-10

L008 Lading Quantity

C N0 1-7

L009 Packaging Form Code

C ID 3-3

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

L108 Special Charge or Allowance Code

O ID 3-3

L120 Currency Code

O ID 3-3

L701 Lading Line Item Number

O N0 1-3

L707 Freight Class Code

O AN 2-5

L301 Weight

C R 1-10

L305 Charge

O N2 1-12

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Arcbest via Mercury Gate 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 Arcbest via Mercury Gate — with rate details, accessorial charges, and load references mapped automatically.

Arcbest via Mercury Gate EDI 210 FAQ

Common questions about 210 Motor Carrier Freight Details and Invoice transactions with Arcbest via Mercury Gate.

How long does it take to set up Arcbest via Mercury Gate EDI with Stacksync?

Most suppliers are fully connected and processing live Arcbest via Mercury Gate 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 Arcbest via Mercury Gate?

No. Stacksync handles the entire EDI transport layer. We connect directly to Arcbest via Mercury Gate'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 Arcbest via Mercury Gate 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 Arcbest via Mercury Gate?

Stacksync supports all EDI document types required by Arcbest via Mercury Gate — 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 Arcbest via Mercury Gate 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 Arcbest via Mercury Gate's EDI network and your system in real time.

What happens when Arcbest via Mercury Gate updates their EDI specifications?

Stacksync monitors Arcbest via Mercury Gate'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.