To start and identify an interchange of zero or more functional groups and interchange-related control segments
Cass Information Systems, Inc X12 310 Freight Receipt and Invoice (Ocean)
X12 310 (Freight Receipt and Invoice (Ocean)) is the EDI transaction exchanged between Cass Information Systems, Inc (Cass Ocean (ISA: CASSOCEANFRT)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 33
- Loops
- 8
- X12 310
- All partners ↗
Transaction context
Where 310 Freight Receipt and Invoice (Ocean) fits on Cass Ocean (ISA: CASSOCEANFRT)
- Cass Information Systems, Inc channels
- 2 of 2
- Trading partners
- 4
- Channels
- 5
2 of Cass Information Systems, Inc's 2 channels carry 310
partners across the Stacksync network trade 310
channels network-wide carry 310
Most common alongside 310
The 310 is the ocean carrier's combined freight receipt and invoice. It confirms receipt of cargo for a shipment, can substitute for a paper ocean bill of lading where the parties have agreed, lets the shipper or forwarder verify bill of lading data before an original is printed and released, conveys manifest information to a terminal operator, and bills the ocean freight. Trading partners require it because it serves as both the payment request and the shipment record for the ocean leg. The ocean carrier sends the 310 to interested parties to the shipment, typically the shipper or freight forwarder, and can also use it to pass manifest information to a terminal operator.
When it fires: An ocean carrier receives cargo for a booked shipment and issues the combined receipt and freight invoice covering that movement.
Common 310 rejection causes
- Charge detail in the L1 segments that does not reconcile with the agreed rates or with the invoice totals, which stalls the freight-payment audit.
- Vessel, voyage, or port identification errors in the V1 and location segments that prevent the receiver from matching the invoice to the booking and manifest.
- Missing hazardous material detail (H1/H2 segments) on dangerous goods shipments, which fails compliance checks at the receiver.
- Treating the 310 as a bill of lading substitute without prior agreement; the standard permits replacing a paper bill of lading only where the parties have agreed it is not necessary.
Specification summary
X12 310 Freight Receipt and Invoice (Ocean) at the element level
The X12 310 specification defines 75 segments carrying 489 data elements, 78 of which are mandatory.
- Segments
- 75
- Data elements
- 489
- Mandatory elements
- 78
| Segment | Elements | Mandatory |
|---|---|---|
| B3 | 14 | 5 |
| B2A | 2 | 1 |
| Y6 | 3 | 2 |
| G3 | 6 | 1 |
| N9 | 6 | 1 |
| M0 | 4 | 1 |
| M1 | 12 | 1 |
| C2 | 7 | 3 |
| C3 | 4 | 1 |
| Y2 | 10 | 2 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
Key identifiers in 310
- Invoice Number
- Shipment Method of Payment
- Date
- Net Amount Due
- Standard Carrier Alpha Code
- Transaction Set Purpose Code
- Authority
- Authorization Date
Full segment guideline — 33 segments 8 loops · X12 310 Freight Receipt and Invoice (Ocean)
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit basic data relating to the carrier's invoice
To allow for positive identification of transaction set purpose
To specify the authority for authorizing an action and the date authentication is made
To transmit identifying information as specified by the Reference Identification Qualifier
To provide vessel details and voyage number
To transmit letter of credit details
To specify the currency being used in the transaction set
To specify container information and transportation service to be used
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To identify a person or office to whom communications should be directed
R4 Loop Repeat: 20
Contractual or operational port or point relevant to the movement of the cargo
To specify pertinent dates and times
To specify carrier and routing sequences and details
To specify special handling instructions in coded or free-form format
C8 Loop Repeat: 20
To specify applicable certifications and clauses
LX Loop Repeat: 999
To reference a line number in a transaction set
N7 Loop Repeat: 999
To identify the equipment
To specify quantity information
To record seal numbers used and the organization that applied the seals
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
To identify the type or transmission or both of paperwork or supporting information
To transmit information in a free-form format for comment or special instruction
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
L1 Loop Repeat: 20
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
L0 Loop Repeat: 120
To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data
To specify the line item in terms of description, quantity, packaging, and marks and numbers
To reference details of the tariff used to arrive at applicable rates or charge
H1 Loop Repeat: 10
To specify information relative to hazardous material
Trading partners
1+ 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.
Cass Information Systems, Inc Cass Ocean (ISA: CASSOCEANFRT) EDI 310 FAQ
Common questions about 310 Freight Receipt and Invoice (Ocean) on the Cass Ocean (ISA: CASSOCEANFRT) channel.
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. Cass Information Systems, Inc's Cass Ocean (ISA: CASSOCEANFRT) channel requires it from trading partners.
Does Cass Information Systems, Inc Cass Ocean (ISA: CASSOCEANFRT) require 310 for trading partners?
Yes, Cass Information Systems, Inc (Cass Ocean (ISA: CASSOCEANFRT)) 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 Cass Information Systems, Inc 310 with Stacksync?
Most companies go live with Cass Information Systems, Inc 310 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Cass Information Systems, Inc channels accept 310?
X12 310 runs on 2 of Cass Information Systems, Inc's 2 channels. Besides Cass Ocean (ISA: CASSOCEANFRT), it is accepted on Cass Motor (ISA: CASSMTRFRT). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your Cass Information Systems, Inc EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
