ACE Cargo Release: How Brokers Transmit Release Data to CBP

Key Points

• ACE Cargo Release is the electronic successor to the paper CBP Form 3461, and it covers release of cargo only, not the entry summary.
• The broker transmits entry number, entry type, importer, consignee, bill of lading, HTS, value and partner government agency (PGA) data before or on arrival, and ACE matches it to the carrier's manifest.
• CBP returns dispositions such as release, hold, documents required and PGA messages, which the broker must monitor in ABI.
• Under 19 CFR 142.12, the entry summary generally follows within 10 working days after release, so release and summary are two separate filings.
• The most common failures are filing against a bill not yet on the manifest, missing PGA data, mismatched importer or consignee identity, and ignored hold messages.

On this page

1. At a glance
2. What is ACE Cargo Release and where does it come from?
3. When is ACE Cargo Release filed in the entry lifecycle?
4. How is ACE Cargo Release transmitted and reviewed?
5. Common ACE Cargo Release errors
6. How does ACE Cargo Release interact with other ACE functions?
7. Frequently asked questions
8. What importers and brokers should do
9. Key references

ACE Cargo Release is the Automated Commercial Environment transaction through which a customs broker or self-filing importer transmits the data CBP needs to decide whether to release imported cargo before or on arrival. It replaces the paper CBP Form 3461 and the older ACS Simplified Entry, and CBP answers it with disposition messages and holds. ACE Cargo Release sits at the front of the entry lifecycle and is distinct from the entry summary that follows.

This entry reflects the process as of October 2026. The links in this article go to the primary documents: the regulations, the CBP technical specifications, and the official form pages themselves. Read the source.

At a glance

• Full name: ACE Cargo Release (electronic release transaction in the Automated Commercial Environment)
• Who prepares or uses it: Licensed customs brokers and importer self-filers transmit it; carriers and terminals rely on the resulting dispositions
• When in the lifecycle: Before or on arrival, ahead of the entry summary
• System or channel: ACE via the Automated Broker Interface (ABI)
• Paper equivalent: CBP Form 3461
• Governing authority: 19 CFR part 142, including 142.3 (entry documentation); technical rules in the ACE Cargo Release chapter of the CATAIR
• Related terms: disposition codes, 1C release, ACE in-bond, ACE truck eManifest, MID code, CATAIR Appendix B

What is ACE Cargo Release and where does it come from?

ACE Cargo Release is the electronic form of the entry documentation that 19 CFR 142.3 requires an importer to file so CBP can decide release of merchandise. Historically, that documentation was presented on paper as CBP Form 3461, and later transmitted through the legacy ACS Simplified Entry. ACE consolidated those paths into one ABI transaction whose record layouts are published in the ACE Cargo Release chapter of the ACE ABI CATAIR.

The key conceptual point is that ACE Cargo Release answers one question: may this cargo leave CBP control? It does not finalize classification, duty or fees. That work belongs to the entry summary, filed on the 7501 data set, which CBP reviews and eventually liquidates.

Core data elements

According to CBP's process, a cargo release typically carries the entry number, entry type, importer of record, ultimate consignee, bill of lading or air waybill, HTS numbers, value, and any PGA data the commodity requires. Line level manufacturer data, such as the Manufacturer Identification code (MID code), is a core entry element; confirm in the current CATAIR exactly which manufacturer and party fields the release record requires for your entry type.

When is ACE Cargo Release filed in the entry lifecycle?

ACE Cargo Release is filed before or on arrival of the cargo, after the carrier's manifest data is available in ACE and before the entry summary. CBP permits transmission in advance of arrival so that targeting and PGA review can finish before the freight reaches the port. The exact advance window depends on mode of transport and current CBP rules, so confirm it in the CATAIR and with your port or ABI client representative before relying on it.

Release first, summary second

Once CBP releases the cargo, the clock for the entry summary starts. Under 19 CFR 142.12, the entry summary is generally due within 10 working days after release. Brokers who treat the release as the finished entry risk missing that window, which is why most filing teams track release date and summary due date as separate fields.

How is ACE Cargo Release transmitted and reviewed?

ACE Cargo Release is transmitted by the filer through ABI to ACE, which then runs three steps: manifest matching, targeting, and PGA processing. First, ACE looks for the bill of lading on the carrier's manifest, whether that is an ocean or air manifest or the ACE truck eManifest (ACE e-Manifest: Trucks), the electronic truck manifest highway carriers transmit before arrival at a land border port. Second, CBP targeting reviews the shipment. Third, any agency with jurisdiction over the goods evaluates the PGA data.

Dispositions and holds

ACE returns status notifications to the broker in ABI. These ACE cargo release disposition codes describe what happened: released, held, documents required, PGA action, or canceled. The release message that carriers and terminals wait for is the 1C release (disposition code 1C), which means CBP has released the entry but is not a final determination of admissibility or duty and is not PGA clearance by itself. Code values and their meanings are listed in CATAIR Appendix B, Valid Codes, the CATAIR appendix holding code tables used across ABI transactions; rely on that appendix rather than memory.

When CBP requests documents, brokers commonly answer through the Document Image System. When a hold posts, cargo cannot move until the hold is resolved and a new disposition is received.

Common ACE Cargo Release errors

ACE Cargo Release errors usually come from timing or data mismatches rather than complex legal questions, and they cost time at the terminal, demurrage, and sometimes exams.

• Bill not yet on the manifest: a release filed before the carrier transmits the bill will not match, so no release can issue until the manifest catches up.
• Missing PGA data: if the HTS or commodity triggers an agency requirement and the data set is absent, expect a PGA hold or rejection.
• Identity mismatch: importer or consignee numbers that do not agree with CBP records, or with the summary filed later, cause rejects and downstream corrections.
• Ignored hold messages: a hold or documents required message left unanswered keeps the freight in place, and moving cargo without release creates serious exposure.

Technical rejection causes and their fixes are described in the ACE Cargo Release chapter of the CATAIR; when a reject is unclear, the ABI client representative, the CBP Office of Trade contact assigned to each ABI filer, is the right escalation point.

How does ACE Cargo Release interact with other ACE functions?

ACE Cargo Release is one link in a chain of ACE functions, and confusing it with neighboring transactions is a frequent source of error.

• Entry summary: the 7501 is the summary, not the release. Duties, AD/CVD data keyed against ACE AD/CVD case management (the ACE function publishing Commerce case numbers, company suffixes and cash deposit rates), and the ACE Reconciliation flag (entry type 09) all live on the summary.
• ACE in-bond: the electronic in-bond system moves unentered merchandise under bond between ports or to export; it is not ACE Cargo Release, though a release may be filed at the destination port after an in-bond move.
• ACE protest module: the ACE Protest module, where importers file protests (the electronic CBP Form 19) under 19 U.S.C. 1514 and 19 CFR part 174, addresses protestable CBP decisions later in the lifecycle, not release status.
• ISF: the Importer Security Filing is a separate advance security filing and does not substitute for a cargo release.

Frequently asked questions

Is ACE Cargo Release the same as CBP Form 3461?

ACE Cargo Release is the electronic successor to CBP Form 3461 and serves the same purpose: giving CBP the data to decide release. In ACE, the transaction is filed through ABI rather than on paper.

Does a 1C release mean my entry is finished?

No. A 1C release on an ACE Cargo Release means CBP released the cargo, but the entry summary is still due, generally within 10 working days after release under 19 CFR 142.12, and PGA clearance may be separate.

Can ACE Cargo Release be filed before the ship or truck arrives?

Yes, ACE Cargo Release can be transmitted before arrival so review can finish early. The bill must be on the carrier's manifest for matching, and the permitted advance window should be confirmed in the CATAIR.

Where do I find disposition code meanings?

Disposition codes returned on an ACE Cargo Release are listed in CATAIR Appendix B. Check the current version, because code tables are updated.

What importers and brokers should do

1. Confirm the carrier's manifest shows the bill of lading before transmitting the ACE Cargo Release, and recheck if no match returns.
2. Map every HTS number to its PGA requirements and verify importer and consignee identifiers before filing.
3. Assign someone to monitor ABI dispositions daily and answer holds and document requests the same day.
4. Calendar the entry summary due date from the release date, using the 10 working day rule in 19 CFR 142.12.

Key references

• 19 CFR part 142: entry process regulations, including 142.3 entry documentation and 142.12 entry summary timing.
• ACE ABI CATAIR: CBP technical specifications, including the ACE Cargo Release chapter and Appendix B, Valid Codes.
• CBP forms: CBP's official forms page, where CBP Form 3461, the paper equivalent, is published.