CTSI EDI 310 Freight Receipt and Invoice (Ocean)

Schema Reference

22 segments · X12 310 Freight Receipt and Invoice (Ocean)

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

B308 Correction Indicator

O ID 2-2

B309 Delivery Date

C DT 8-8

B310 Date/Time Qualifier

C ID 3-3

B311 Standard Carrier Alpha Code

M ID 2-4

B312 Date

O DT 8-8

B313 Tariff Service Code

O ID 2-2

B314 Transportation Terms Code

O ID 3-3

B2A01 Transaction Set Purpose Code

M ID 2-2

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

V102 Vessel Name

C AN 2-28

V104 Flight/Voyage Number

O AN 2-10

C301 Currency Code

M ID 3-3

C302 Exchange Rate

O R 4-10

C303 Currency Code

O ID 3-3

Y201 Number of Containers

M N0 1-4

Y204 Equipment Type

M ID 4-4

Y205 Transportation Method/Type Code

O ID 1-2

Y206 Intermodal Service Code

O ID 1-2

Y207 Standard Carrier Alpha Code

O ID 2-4

N1 Loop Repeat: 10

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

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

R4 Loop Repeat: 20

R401 Port or Terminal Function Code

M ID 1-1

R402 Location Qualifier

C ID 1-2

R403 Location Identifier

C AN 1-30

R404 Port Name

O AN 2-24

R405 Country Code

O ID 2-3

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

LX Loop Repeat: 999

LX01 Assigned Number

M N0 1-6

N7 Loop Repeat: 999

N701 Equipment Initial

O AN 1-4

N702 Equipment Number

M AN 1-10

N722 Equipment Type

O ID 4-4

L1 Loop Repeat: 20

L101 Lading Line Item Number

O N0 1-3

L104 Charge

C N2 1-12

L108 Special Charge or Allowance Code

O ID 3-3

L110 Entitlement Code

O ID 1-1

L112 Special Charge Description

O AN 2-25

L117 Billed/Rated-as Quantity

C R 1-11

L118 Billed/Rated-as Qualifier

C ID 2-2

C301 Currency Code

M ID 3-3

C302 Exchange Rate

O R 4-10

C303 Currency Code

O ID 3-3

L0 Loop Repeat: 120

L001 Lading Line Item Number

O N0 1-3

L004 Weight

C R 1-10

L005 Weight Qualifier

C ID 1-2

L006 Volume

C R 1-8

L007 Volume Unit Qualifier

C ID 1-1

L008 Lading Quantity

C N0 1-7

L009 Packaging Form Code

C ID 3-3

L011 Weight Unit Code

O ID 1-1

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

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

L312 Weight Unit Code

O ID 1-1

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating CTSI EDI 310

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

Validate

Transform

Route

Monitor

Stacksync processes CTSI EDI 310 (Freight Receipt and Invoice (Ocean)) documents automatically — syncing data to your system in real time with no manual intervention required.

CTSI EDI 310 FAQ

Common questions about 310 Freight Receipt and Invoice (Ocean) transactions with CTSI.

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

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

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

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

What happens when CTSI updates their EDI specifications?

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