.png){kind=small}
ISA Interchange Control Header
CTSI X12 310 Freight Receipt and Invoice (Ocean)
X12 310 (Freight Receipt and Invoice (Ocean)) is the EDI transaction exchanged between CTSI and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 22
- Loops
- 6
- X12 310
- All partners ↗
Schema reference
22 segments · 6 loops · X12 310 Freight Receipt and Invoice (Ocean)
GS Functional Group Header
Transaction Set Header
Beginning Segment for Carrier's Invoice
Set Purpose
Reference Identification
Vessel Identification
Currency
Container Details
Loop
Name
Address Information
Geographic Location
Loop
Port or Terminal
Date/Time Reference
Loop
Assigned Number
Loop
Equipment Details
Loop
Rate and Charges
Currency
Loop
Line Item - Quantity and Weight
Description, Marks and Numbers
Total Weight and Charges
Transaction Set Trailer
Trading partners
2+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
CTSI EDI 310 FAQ
Common questions about 310 Freight Receipt and Invoice (Ocean) with CTSI.
What is X12 310 Freight Receipt and Invoice (Ocean)?
X12 310 (Freight Receipt and Invoice (Ocean)) is the EDI transaction set used to exchange freight receipt and invoice (ocean) data. CTSI requires it from trading partners.
Does CTSI require 310 for trading partners?
Yes — CTSI supports X12 310 Freight Receipt and Invoice (Ocean). Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate CTSI 310 with Stacksync?
Most companies go live with CTSI 310 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your CTSI EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.