X12 transaction code
X12 310 Freight Receipt And Invoice Ocean
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 310
- Trading partners
- 4
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 |
- Invoice Number
- Shipment Method of Payment
- Date
- Net Amount Due
- Standard Carrier Alpha Code
- Transaction Set Purpose Code
- Authority
- Authorization Date
Trading partners that support X12 310
4 partners, 5 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 310 Freight Receipt And Invoice Ocean
310 is used most heavily in logistics & transport and e-commerce & marketplaces.
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. An ocean carrier receives cargo for a booked shipment and issues the combined receipt and freight invoice covering that movement.
By industry
- logistics & transport 4 channels
- e-commerce & marketplaces 1 channel
By network
- CTSI 1 channel
FAQ
X12 310 questions
What is X12 310 Freight Receipt And Invoice Ocean?
X12 310 (Freight Receipt And Invoice Ocean) is an EDI transaction set defined by ANSI ASC X12 for exchanging freight receipt and invoice ocean between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 4 Stacksync trading partners support this code across 5 channels.
Which trading partners use X12 310?
4 Stacksync partners accept X12 310: Cass Information Systems, Inc, CTSI-Global, Data2Logistics (Toshiba), Wayfair LLC. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 310 with my ERP?
Stacksync handles the full X12 310 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
