Ocean carriers and NVOCCs send their import manifest to U.S. Customs and Border Protection electronically, through ACE, in one of two CBP formats: ANSI X12 or CAMIR. Whichever you pick, CBP answers with acceptance, rejection and status messages your system must read. This guide explains both formats, the messages that come back, and how a company gets connected and tested.
Under 19 CFR 4.7(b)(2), CBP must receive the electronic equivalent of the vessel's Cargo Declaration (CBP Form 1302) from the incoming carrier 24 hours before the cargo is laden aboard the vessel at the foreign port. Bulk cargo, and break bulk cargo with an approved exemption, follow a different timing rule set out in the same section.
An NVOCC has a choice. Under 4.7(b)(3), an NVOCC licensed by or registered with the Federal Maritime Commission, and holding an International Carrier Bond with the required provisions, may transmit its house bill data directly to CBP. Otherwise it must give the full cargo information to the vessel carrier, which presents it to CBP. Either way the data travels by EDI, and the content rules in 19 CFR 4.7a apply. For the basics of who files what, see what ACE AMS filing is.
CBP's ACE Import Manifest Documentation page groups the ocean technical requirements into two sets: Ocean CAMIR and Ocean X12 implementation guides. CAMIR (Customs Automated Manifest Interface Requirements) is CBP's own record-based format, with records such as M01 (manifest), P01 (port), A01 (amendment), B01 (bill of lading) and S01 (shipper). X12 uses the national EDI standard, adapted by CBP.
| X12 transaction set | What it carries (per CBP's ocean list) |
|---|---|
| 309 | Manifest input with security filing; also used for the automated manifest download and hazardous materials download |
| 350 | Customs status information, including ISF status information |
| 353 | Events advisory details |
| 355 | Acceptance or rejection |
| 356 | Permit to transfer request |
| 357 | In-bond information |
| 997 | Functional acknowledgment |
Neither format is "better" for compliance; the data content is the same. The choice usually follows what your software or service provider supports and what your trading partners already use. If your team also exchanges EDI with lines and terminals, the same ANSI X12 skills carry over.
CBP's March 2026 import ocean 309 implementation guide states that it uses the ASC X12 4010 version as its base, with the structure altered for CBP requirements. A few rules regularly trip up first-time developers:
CBP also notes that its requirements may override the X12 standard's mandatory or conditional usage, so validating against a generic X12 4010 dictionary is not enough. Validate against the CBP guide.
Filing is a two-way conversation. After you transmit, CBP returns an acceptance or rejection (the 355 in X12) and later status notifications (the 350) as entries are filed, holds are placed and cargo is released. Each status carries a disposition code from CAMIR Ocean Appendix D, for example:
A system that sends manifests but cannot store and display these codes leaves your team checking status by phone. When a status matters, it should appear on the bill of lading record where people already work. If a filing is rejected, our guide to correcting a rejected ACE manifest covers the amendment side.
CBP's page on transmitting data by EDI lays out the path. In short:
The right answer depends on volume, in-house IT and how much control you want over timing and corrections.
| Question | Direct connection | Through a provider or software vendor |
|---|---|---|
| Who builds and tests the EDI? | You, with CBP testing | The provider or vendor |
| Who maintains it when CBP changes a guide? | Your IT team | The provider or vendor |
| Where do CBP status codes land? | In your own system, if you build it | Depends on the provider; ask before you sign |
| Best fit | High volume with in-house developers | Small and mid-size carriers and NVOCCs |
Everything above concerns import manifests. CBP's Export Manifest page says the ocean export manifest is still being phased in: it lists a Notice of Proposed Rulemaking for ocean (February 10, 2026), invites additional pilot participants, and says the export manifest will eventually be required electronically in ACE. It lists X12 309, 350, 353 and 355 message sets for ocean export as well. Keep an eye on CBP's Cargo Systems Messaging Service for the final rule.
GDZ Computer Services holds a long-standing U.S. Customs ACE interface certification, and GDZ-ISIS uploads the ACE manifest from the bills of lading already in the system while tracking CBP approvals, holds and inspections. Beyond Customs, GDZ has built EDI interfaces in standards including ANSI X12, XML, CSV, ASYCUDA, Excel and positional text. To talk through your current setup, contact our team.
Both are CBP-approved formats for sending the same manifest data to ACE. CAMIR is CBP's own record-based layout (M01, B01, A01 and so on), while X12 uses national standard transaction sets such as the 309 manifest and the 355 acceptance or rejection, adapted by CBP.
CBP's March 2026 import ocean 309 implementation guide says it uses ASC X12 version 4010 as its base, altered for CBP requirements. Always validate against the current CBP guide rather than a generic 4010 dictionary.
Yes, if it is licensed by or registered with the FMC and holds an International Carrier Bond with the provisions CBP requires, under 19 CFR 4.7(b)(3). Otherwise it must give the cargo information to the vessel carrier, which files it.
Yes. CBP states that companies intending to transmit data by EDI must successfully test with CBP before they are permitted to transmit production data. A CBP Client Representative guides you through it.
Not as of CBP's current Export Manifest page, which lists the ocean rule as a proposed rule (February 10, 2026) and invites pilot participants. Check the page and CBP's CSMS messages for updates.