--- title: "EDI 310 Freight Receipt and Invoice (Ocean) | Stacksync" description: "EDI 310 is the X12 Freight Receipt and Invoice (Ocean), used when ocean shipment charges are ready to bill. See its key segments and mapping checks." canonical: https://www.stacksync.com/edi/x12/310-freight-receipt-and-invoice-ocean last_modified: 2026-09-29 --- X12 transaction code # EDI 310 Freight Receipt and Invoice (Ocean) (X12 310) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 310 is the X12 Freight Receipt and Invoice (Ocean) transaction set, used when ocean shipment charges are ready to bill. 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. Standard X12 Code 310 Partner references 4 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 310 at a glance What the 310 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 310 Freight Receipt and Invoice (Ocean) summary** | | | | --- | --- | | Document | X12 310 Freight Receipt and Invoice (Ocean) | | Business record | Ocean-freight payable | | Who sends it to whom | 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 is sent | An ocean carrier receives cargo for a booked shipment and issues the combined receipt and freight invoice covering that movement. | | Match on | Carrier invoice, bill of lading and container references | | Partner references | 4 trading partners in this directory | ### Key segments in an EDI 310 The business segments that appear in at least half of the 5 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | B3 | Beginning Segment for Carrier's Invoice | To transmit basic data relating to the carrier's invoice. | 5 of 5 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 5 of 5 | | V1 | Vessel Identification | To provide vessel details and voyage number. | 5 of 5 | | C3 | Currency | To specify the currency being used in the transaction set. | 5 of 5 | | Y2 | Container Details | To specify container information and transportation service to be used. | 5 of 5 | | N1 | Name | To identify a party by type of organization, name, and code. | 5 of 5 | | N3 | Address Information | To specify the location of the named party. | 5 of 5 | | N4 | Geographic Location | To specify the geographic place of the named party. | 5 of 5 | | R4 | Port or Terminal | Contractual or operational port or point relevant to the movement of the cargo. | 5 of 5 | | DTM | Date/Time Reference | To specify pertinent dates and times. | 5 of 5 | Stacksync connects EDI documents such as the X12 310 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 310 mapping and validation X12 310 Freight Receipt and Invoice (Ocean) is used when ocean shipment charges are ready to bill. Preserve carrier invoice, bill of lading and container references so the ocean-freight payable in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **ocean-freight payable** carrier invoice, bill of lading and container references | Define which combination of carrier invoice, bill of lading and container references identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the ocean-freight payable** ID assigned by the receiving system and processing result | Reconcile charges for multiple containers to the bill total. Distinguish an additional charge from a replacement invoice for the same voyage. | | Check the processing result | **Processing status for the ocean-freight payable** Original document reference and matching response | Reconcile the ocean-freight payable with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when ocean shipment charges are ready to bill. Name the operational owner of the ocean-freight payable and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map carrier invoice, bill of lading and container references. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic ocean-freight payable data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful ocean-freight payable processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 310 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic ocean-freight payable data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out ocean-freight payable without processing it twice. ### Related documents and resources - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 310 Freight Receipt and Invoice (Ocean) at the element level The X12 310 reference contains 75 segment entries and 489 data elements; 78 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 75 Data elements 489 Mandatory elements 78 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 310 4 partners, 5 channels. Choose a channel to inspect its listed document reference and implementation context. - [Cass Information Systems, Inc](https://www.stacksync.com/edi/cass-information-systems-inc) [Cass Ocean (ISA: CASSOCEANFRT)](https://www.stacksync.com/edi/cass-information-systems-inc/cass-ocean-isa-cassoceanfrt/x12-310-freight-receipt-and-invoice-ocean) [Cass Motor (ISA: CASSMTRFRT)](https://www.stacksync.com/edi/cass-information-systems-inc/cass-motor-isa-cassmtrfrt/x12-310-freight-receipt-and-invoice-ocean) - [CTSI-Global](https://www.stacksync.com/edi/ctsi) [Molex USA (via CTSI) (ISA ID: CTSI5365)](https://www.stacksync.com/edi/ctsi/molex-usa-via-ctsi-isa-id-ctsi5365/x12-310-freight-receipt-and-invoice-ocean) - [Data2Logistics (Toshiba)](https://www.stacksync.com/edi/data2logistics-toshiba) [Data2Logistics (Toshiba)](https://www.stacksync.com/edi/data2logistics-toshiba/data2logistics-toshiba/x12-310-freight-receipt-and-invoice-ocean) - [Wayfair LLC](https://www.stacksync.com/edi/wayfair-llc) [Wayfair](https://www.stacksync.com/edi/wayfair-llc/wayfair/x12-310-freight-receipt-and-invoice-ocean) Catalog breakdown ## Where X12 310 Freight Receipt and Invoice (Ocean) appears in this catalog The largest groups of classified 310 catalog entries are in logistics & transport and e-commerce & marketplaces. ### By industry - logistics & transport 4 channels - e-commerce & marketplaces 1 channel ### By network - CTSI 1 channel Partner entries with the most listed channels - [Cass Information Systems, Inc](https://www.stacksync.com/edi/cass-information-systems-inc) - [CTSI-Global](https://www.stacksync.com/edi/ctsi) - [Data2Logistics (Toshiba)](https://www.stacksync.com/edi/data2logistics-toshiba) - [Wayfair LLC](https://www.stacksync.com/edi/wayfair-llc) FAQ ## EDI 310 questions ### What is an EDI 310? EDI 310 is the X12 Freight Receipt and Invoice (Ocean) transaction set. Trading partners use it when ocean shipment charges are ready to bill. It carries the data for the ocean-freight payable, and your system matches it on carrier invoice, bill of lading and container references. ### Who sends an EDI 310 and who receives it? 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. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 310 sent? An ocean carrier receives cargo for a booked shipment and issues the combined receipt and freight invoice covering that movement. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 310? Across 5 partner document references listed here, the business segments that appear most often include B3 (Beginning Segment for Carrier's Invoice), N9 (Reference Identification), V1 (Vessel Identification), C3 (Currency), Y2 (Container Details), N1 (Name). Each partner guide sets which segments and elements your account must send. ### What should I map for X12 310? Start with carrier invoice, bill of lading and container references and the target ocean-freight payable. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test 310 error handling? Reconcile charges for multiple containers to the bill total. Distinguish an additional charge from a replacement invoice for the same voyage. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 310? The directory on this page links 4 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ### How does 310 relate to other EDI messages? Keep 310 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the ocean-freight payable workflow; confirm any required companion messages with your partner. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)