Coca EDI 210 Freight Invoice

Schema Reference

14 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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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

B308 Correction Indicator

O ID 2-2

B311 Standard Carrier Alpha Code

M ID 2-4

C301 Currency Code

M ID 3-3

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

H301 Special Handling Code

C ID 2-3

H302 Special Handling Description

C AN 2-30

N7 Loop Repeat: 10

N702 Equipment Number

M AN 1-10

N711 Equipment Description Code

O ID 2-2

S5 Loop Repeat: 999

S501 Stop Sequence Number

M N0 1-3

S502 Stop Reason Code

M ID 2-2

N1 Loop Repeat: 2

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

LX Loop Repeat: 9,999

LX01 Assigned Number

M N0 1-6

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

L112 Special Charge Description

O AN 2-25

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 Coca 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 Coca — with rate details, accessorial charges, and load references mapped automatically.

Coca EDI 210 FAQ

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

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

Most suppliers are fully connected and processing live Coca 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 Coca?

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

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

What happens when Coca updates their EDI specifications?

Stacksync monitors Coca'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.