X12 transaction guide · Transportation
EDI 310 Freight Receipt and Invoice (Ocean)
The X12 document ocean carriers send with bill of lading information, serving as a receipt for the shipment and often as the freight invoice.
- Sent by
- Ocean carrier
- Received by
- Shipper, forwarder, consignee or other interested party
- Standard
- ANSI ASC X12
What is an EDI 310?
The EDI 310 Freight Receipt and Invoice (Ocean) is the ANSI X12 transaction set ocean carriers use to provide bill of lading information to interested parties. It can serve as the receipt for the shipment, replace a paper bill of lading where the parties agree one is not needed, let the shipper or forwarder verify the bill of lading before the original is printed, and carry freight charges for invoicing.
Because it mirrors the bill of lading, the 310 is the point at which errors in the shipping instructions become visible. Checking it promptly avoids corrections, delays at destination and disputed charges.
How to read this diagram: the top row shows who sends the 310, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 310 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.
When it is used
- Verifying draft bills of lading before release
- Receiving electronic bills of lading or sea waybills
- Receiving ocean freight charges for payment
Where it fits in the document flow
Structure
Mandatory segments in the 310 (X12 release 008010)
The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.
- ST
- B3
- V1
- N1
- R4
- C8
- LX
- N7
- L1
- H1
- LH1
- L0
- L3
- SE
Practical example
The 310 in practice
The carrier sends a 310 for the exporter's shipment. The forwarder's system compares it with the 304 instructions and flags a misspelled consignee name. The forwarder requests a correction before the bill of lading is finalized, avoiding a customs hold in Rotterdam. The charges in the 310 are later matched to the freight quote.
Implementation
Implementation considerations for the 310
- Compare each 310 with the shipping instructions automatically and flag differences.
- Match freight charges to agreed rates before approving payment.
- Agree with partners when the electronic record replaces the paper bill of lading.
Trading partners
Integration guides that include the 310

- Alba Wheels Up


- Approved Freight Forwarders


- CMA CGM America
- COSCO Shipping Logistics North America



- DHL Group
- Dimerco Express Group
- DSV US

- ELM Global Logistics




- Grimaldi Group USA
- Gulf Winds International
- Hapag-Lloyd America

- Hoegh Autoliners
- ICAT Logistics
- JAS Worldwide
- John A. Steer Co.

- Kuehne+Nagel USA

- Logistics Plus


- Matson
- Matson Logistics

- MSC Mediterranean Shipping Company




- ProTrans International
- PSA BDP




- Seaboard Marine




- Tucker Company Worldwide

How ECOM helps
Automate the 310 with ECOM
Industry
Transportation and Logistics
Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
Solution
Ocean Freight EDI and API Integration
Ocean carrier, terminal and customs integration for booking, shipping instructions, VGM, container tracking and freight invoices.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related transportation documents
- 304Shipping Instructions
- 300Reservation (Booking Request) (Ocean)
- 301Confirmation (Ocean)
- 303Booking Cancellation (Ocean)
- 313Shipment Status Inquiry (Ocean)
- 315Status Details (Ocean)
- 323Vessel Schedule and Itinerary (Ocean)
- 361Carrier Interchange Agreement (Ocean)
- 410Rail Carrier Freight Details and Invoice
- 312Arrival Notice (Ocean)
- 324Vessel Stow Plan (Ocean)
- 104Air Shipment Information
From the guide to go-live
Put this into practice with ECOM
Reading about EDI is the first step. When you are ready to meet a trading partner's requirements, an ECOM specialist can help.
-
EDI compliance help
Check documents against the partner's rules before they are sent, and find out why labels, ship notices or invoices are rejected or short-paid for EDI 310.
-
EDI implementation
Map, test and certify the documents for EDI 310, and connect them to your ERP, warehouse or order system.
-
Managed EDI
Have ECOM run the day-to-day EDI: monitoring, error handling and new trading partner setup.
Need help with the EDI 310?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.