What is the ACE Portal? (2026 guide to CBP Automated Commercial Environment)

TL;DR

• ACE (Automated Commercial Environment) is U.S. Customs and Border Protection primary electronic trade-processing platform, launched in stages 2003-2016 as the mandated successor to the legacy ACS (Automated Commercial System).
• Every commercial entry into the United States is filed through ACE, either through the browser-based ACE Portal or through the EDI ACE Automated Broker Interface (ABI); by 2026 there is no non-ACE path for a commercial entry.
• ACE is a single window (per Trade Facilitation and Trade Enforcement Act 2015): the same shipment data is routed to CBP for customs processing and simultaneously to the applicable PGAs (CPSC, FDA, EPA, USDA, roughly 47 total participating agencies).
• Eight core modules cover the trade workflow: Account Activity, Manifest, Entry Summary, PGA Message Set, ACE Reports, Cargo Release, FTZ, and Bond Management.
• eManifest is required in advance of arrival by transport mode (ocean 24 hours pre-load, air 4 hours pre-departure, truck 1 hour pre-border, rail 2 hours pre-crossing).
• Entry summary (Form 7501 equivalent) is due within 10 working days of release and is the operative document for tariff classification, duty calculation, PGA compliance, and Section 232 / Section 301 additional-tariff application.
• TariffWatch integrates at the ACE Reports and CROSS rulings layer, monitoring the specific HTS codes an importer has filed against and alerting on new tariff actions affecting those codes.

What ACE actually is (history and legal basis)

ACE, formally the Automated Commercial Environment, is the electronic trade-processing platform operated by U.S. Customs and Border Protection under the Department of Homeland Security. Development began in the late 1990s as a modernization successor to the Automated Commercial System (ACS), the mainframe-based CBP legacy trade-processing platform that had been in operation since 1984. CBP awarded the initial ACE prime contract in April 2001, launched the first ACE modules (account management, eManifest for trucks) in 2003, and progressively rolled additional modules through the mid-2010s. The Executive Order 13659 issued February 19 2014 by President Obama directed the completion of the transition to a single-window trade-data platform by December 31 2016, which is the operative mandatory-ACE date in the trade compliance literature.

The legal basis for ACE rests on several statutes. The Customs Modernization Act (Title VI of NAFTA Implementation Act of 1993, Pub. L. 103-182) authorized CBP to require electronic filing of customs data. The SAFE Port Act of 2006 (Pub. L. 109-347) directed CBP to develop the single-window trade platform. The Trade Facilitation and Trade Enforcement Act of 2015 (Pub. L. 114-125) further codified the single-window mandate. These statutes together establish that ACE is not an optional filing convenience but the mandatory electronic filing channel for import trade data. The regulations implementing electronic filing appear across 19 CFR (Parts 4, 122, 141, 142, 143, and PGA-specific parts including 19 CFR 12.28 for FDA-regulated products), and the operational rules for ACE-specific procedures appear in CBP-issued CATAIR (Customs and Trade Automated Interface Requirements) technical documentation at cbp.gov/trade/ace.

Operationally, in 2026, every commercial import entry into the United States flows through ACE. Small-volume filers use the browser-based ACE Portal for occasional entries. High-volume filers use the ACE Automated Broker Interface for programmatic filing through EDI. Both routes result in the same underlying ACE entry record and the same downstream CBP and PGA processing.

ACE Portal vs ACE Automated Broker Interface (ABI)

The ACE platform exposes two distinct filing interfaces sitting on top of the same back-end data infrastructure.

The ACE Portal is the browser-based user interface accessed through the CBP Trade Portal login. It provides form-based filing for eManifests, entry summaries, and PGA-specific messages; account-management functions (bond status, account activity, user administration); and access to ACE Reports for business-intelligence queries against the account own data. The Portal is the interface a small-volume broker or self-filing importer typically uses, and is also the interface CBP staff and PGA staff use to review filed data.

The ACE Automated Broker Interface (ABI) is the EDI transaction interface for high-volume programmatic filing. ABI uses structured EDI message sets (formally defined in the CATAIR technical documentation) transmitted through CBP-approved communication paths, typically through commercial trade software vendors that maintain certified ABI connectivity. Large customs brokerages file the majority of their entries through ABI-integrated software rather than through the browser Portal, achieving throughput of thousands of entries per day per broker firm. ABI supports the same transaction sets as the Portal (eManifest, entry summary, PGA Message Set, bond management, ACE Reports queries) plus additional programmatic-only transactions for account maintenance and bulk operations.

The choice between Portal and ABI is essentially a volume decision: below roughly 20 entries per day the Portal is sufficient; above roughly 100 entries per day ABI-integrated software is operationally required. In between, many small brokerages run hybrid setups (Portal for one-off entries, ABI-integrated software for recurring commercial clients). Both interfaces produce identical entry records; there is no CBP-side treatment difference between an entry filed through the Portal versus an entry filed through ABI.

The eight core modules and what each does

The eight modules do not correspond to eight separate applications; they are functional groupings within the same ACE user interface, with the specific modules a given user sees determined by the user role and the account permissions. An importer account sees Account Activity, Entry Summary, PGA Message Set, ACE Reports, Cargo Release, and Bond Management for that importer own entries; a broker account additionally sees these modules for client importer entries the broker is authorized to file; a carrier account sees the Manifest module for the carrier own filings.

eManifest deep dive (24 Hour Rule and mode-specific deadlines)

The eManifest is the electronic cargo manifest filed by the arriving carrier in advance of the shipment reaching the U.S. port of entry. Advance-electronic-data requirements were authorized by the Trade Act of 2002 (Pub. L. 107-210) and are implemented at 19 CFR Parts 4 (vessel), 122 (air), 123 (land), and 124 (rail). The regime is CBP primary cargo-security data source, driving the National Targeting Center risk assessment of every arriving shipment.

Mode-specific advance-filing deadlines are load-bearing. For ocean cargo, the 24 Hour Rule at 19 CFR Section 4.7(b) requires the vessel manifest to be filed 24 hours before the cargo is loaded at the foreign port; missing the 24 Hour Rule for a container triggers a Do Not Load message that literally prevents the container from being loaded onto the vessel. For air cargo, 19 CFR Section 122.48a requires the air manifest to be filed 4 hours before the aircraft departs the last foreign airport before the U.S. (for long-haul flights) or at wheels-up (for near-U.S. flights from Canada, Mexico, Central America, and Caribbean origin). For truck cargo, the manifest must be filed 1 hour before the truck crosses the U.S. border (30 minutes for FAST-participant trucks). For rail cargo, the manifest must be filed 2 hours before the train crosses the U.S. border.

The eManifest data includes the vessel or aircraft or truck or train identifier, the arrival location and estimated arrival time, and per-shipment data (shipper name and address, consignee name and address, commodity description, package count, weight, container number for containerized cargo, hazardous-materials indicators). CBP processes the manifest data through the ATS (Automated Targeting System) risk-assessment engine and may issue a hold on any shipment before arrival based on the risk-score output. Manifest-only holds are a common failure mode for importers whose commodity description is vague or whose consignee data is inconsistent with prior shipments; correcting the manifest requires the carrier (not the importer) to file the correction, which is one reason importers work carefully with carriers on manifest data quality even though the eManifest is technically the carrier filing responsibility.

Entry vs entry summary vs PSC

Three distinct filings comprise the standard entry lifecycle for a commercial shipment, and importers new to the ACE workflow commonly confuse them.

Initial entry (CBP Form 3461 equivalent, filed as ACE entry). Filed at or before arrival, providing basic entry data (importer of record, port of entry, mode of transportation, entry type, filer code, entry number) and requesting CBP release of the cargo from customs custody. The initial entry is the operative document CBP releases against; once released, the importer can take physical possession of the cargo. The initial entry does not fully calculate duties owed; that happens at entry-summary time.

Entry summary (CBP Form 7501 equivalent). Due within ten working days of the entry release under 19 CFR Section 142.12(b), the entry summary is the fuller filing with complete tariff classification (10-digit HTSUS by line item), declared customs value, applicable duty rate, PGA data, preferential-tariff-program claims, and calculated duty and fee amounts. Duty payment is due at entry-summary time (Periodic Monthly Statement filers under 19 CFR Section 24.25 aggregate multiple entries for month-end payment). The entry summary is where the operative compliance work happens: tariff classification accuracy, Section 232 / Section 301 additional-tariff application, USMCA claim substantiation, PGA compliance.

Post-Summary Correction (PSC). A subsequent filing that amends a submitted entry summary to correct errors identified after original submission. PSCs are filed under 19 CFR Section 141.113 within 300 days of entry summary submission for most corrections; corrections after that window use the protest process under 19 CFR Part 174. PSCs are the routine correction mechanism for classification refinements, valuation adjustments, and PGA-data updates identified during importer post-entry review. Deliberate misstatement of the entry summary followed by PSC to reduce duty owed is a subject of CBP audit scrutiny; PSCs used to correct genuine errors identified during good-faith post-entry review are the design intent.

The PGA Message Set (why ACE became a single window)

Before ACE reached PGA maturity in 2016, importers of PGA-regulated products (children products under CPSC, medical devices under FDA, chemicals under EPA, agricultural products under USDA, and dozens of other regulated categories) submitted PGA-specific data through the applicable PGA separate paper or electronic filing channel in addition to the CBP customs filing. The single-window mandate directed the consolidation of PGA data into ACE, delivered through the PGA Message Set structured data fields transmitted alongside the customs entry.

Roughly 47 Partner Government Agencies participate in the ACE PGA Message Set as of the 2026 baseline. The most operationally significant for consumer product importers include: CPSC (Consumer Product Safety Commission, mandatory PGA Message Set July 8 2026), FDA (Food and Drug Administration, various regulated product categories under 21 CFR), EPA (Environmental Protection Agency, chemical substances under TSCA, pesticides under FIFRA), USDA APHIS (Animal and Plant Health Inspection Service), USDA FSIS (Food Safety and Inspection Service), DOT NHTSA (National Highway Traffic Safety Administration, motor vehicles and equipment), and TTB (Alcohol and Tobacco Tax and Trade Bureau). The specific PGA Message Set fields required per shipment vary by agency and by product; typical fields include the responsible-party identifier, the applicable regulation citation, the test-report or registration-number reference, and the product-identification data specific to the PGA.

Failure to transmit a required PGA Message Set field for a regulated shipment triggers a PGA-side hold at the port. The shipment sits pending resolution, with the carrier accruing demurrage and detention charges until the missing data is corrected and re-transmitted. Prevention through pre-transmission data validation (the general category EntryProof lives in for CPSC-regulated products) is much cheaper than post-hold recovery.

ACE Reports and the trade-data warehouse

ACE Reports is the business-intelligence layer built on top of the ACE transactional data, providing pre-built and custom reports queryable through the ACE Portal by authorized users. The underlying data warehouse aggregates every entry filed under the queried account, including entry-summary tariff classification detail, PGA data submission history, duty and fee payment history, bond activity, and account financial position. Importer accounts see reports over their own filed entries; broker accounts see reports over client importer entries the broker is authorized to see; PGA staff accounts see reports over the PGA-specific data streams for their agency.

The pre-built reports cover common use cases: entry summary filings by date range, HTS code usage across the account, PGA activity, duty payments by month, account financial position. Custom reports (through the ACE Reports custom-query builder) allow authorized users to run parameterized queries against the account data, useful for internal compliance audit, duty-drawback claim preparation under 19 U.S.C. Section 1313, and tariff-classification consistency reviews. For an importer running a serious trade compliance program, ACE Reports is one of the highest-leverage self-service tools; the same data would be prohibitively expensive to reconstruct from broker invoices and internal purchase-order data.

Getting an ACE Portal account

ACE Portal account creation runs different paths for the different user roles.

For a self-filing importer, the workflow: (1) the importer obtains an IRS Employer Identification Number if it does not already have one, (2) the importer registers as an importer of record with CBP through CBP Form 5106 filing, (3) the importer applies for ACE Portal access through the CBP ACE Secure Data Portal application at cbp.gov, designating a portal-account owner (individual with primary responsibility) and providing identity verification through Login.gov or equivalent, (4) CBP staff review the application and issue account credentials within 5 to 10 business days pending identity verification, (5) the importer sets up multi-factor authentication using a hardware or software token, (6) the importer designates additional user accounts as needed for internal staff with entry-filing responsibilities.

For a licensed customs broker, the firm applies through the same portal with the firm broker license documentation (CBP-issued broker license under 19 CFR Part 111), designates a broker firm account owner, and provisions additional user accounts for individual broker staff who will file entries. The firm can further authorize a specific broker user to file entries on behalf of specific importer clients, subject to the broker having a valid CBP Form 5106 power of attorney from the importer.

For a carrier or FTZ operator or surety, similar processes with the applicable role-specific documentation. For a PGA staff user, the PGA administrator provisions the user account through the PGA-side administration workflow.

How TariffWatch integrates with ACE-emitted data

TariffWatch is a Section 232 metals monitoring product for U.S. importers, priced from free (for the BIS comment-window utilities and the initial exposure checker) through the $99 per rebuttal paid tier for substantive comment-letter drafting for BIS Section 232 rebuttals. A separate $29 per month HTS watchlist tier alerts importers when a specific 10-digit HTS code on their watch list becomes subject to a new tariff action (Section 232 derivative-articles inclusion, Section 301 China tariff increase, IEEPA modification, antidumping / countervailing duty case initiation, USMCA rule-of-origin change).

The product integrates with ACE-emitted data at three touch points, each carefully scoped to stay outside the 19 CFR Part 111 customs-brokerage licensing regime that TariffWatch does not hold.

Touch point 1: ACE Reports data ingest (importer-authorized). An importer using TariffWatch may authorize the product to receive a periodic export of the importer own ACE Reports entry-summary data (typically monthly). The export identifies the specific HTS codes the importer has actually filed against over the trailing period, which TariffWatch uses to personalize the watchlist. This is the importer own data flowing from ACE to the importer to TariffWatch under the importer control; TariffWatch does not access ACE directly.

Touch point 2: CROSS rulings monitoring. TariffWatch monitors the CBP CROSS (Customs Rulings Online Search System) database at rulings.cbp.gov for new rulings affecting the HTS codes on any customer watchlist. New rulings that reclassify a product or change the applicability of an additional tariff to a specific HTS heading are surfaced as alerts to the affected customers. CROSS is a public database; TariffWatch monitoring uses only publicly-accessible data.

Touch point 3: Federal Register + BIS + USTR tariff action monitoring. TariffWatch monitors the Federal Register at federalregister.gov, the Bureau of Industry and Security notices at bis.doc.gov, and the U.S. Trade Representative Section 301 notices at ustr.gov for new tariff actions affecting the HTS codes on any customer watchlist. This is the surface where new Section 232 derivative-articles inclusions and Section 301 tariff-list changes are announced; watchlist alerts fire the day the notice is published. All monitored data sources are publicly accessible; TariffWatch does not require importer-side authorization for this touch point.

TariffWatch does not file entries through ACE, does not act as an importer of record, and does not act as a licensed customs broker. Filing entries on behalf of another importer would fall inside the 19 CFR Part 111 licensing regime, which requires a CBP-issued customs broker license that TariffWatch does not hold and does not represent as holding. The product is scoped as tariff-monitoring intelligence and Section 232 rebuttal drafting, delivered separately from the ACE filing workflow. Importers use TariffWatch alerts to inform their own filing decisions (with their own customs broker), not as a filing agent.

TariffWatch is a data and workflow tool that estimates Section 232 tariff exposure from publicly available Federal Register, USITC, and CBP data. TariffWatch is NOT a licensed customs broker under 19 CFR 111, NOT a filer of record, and NOT a legal-advice service. This is not customs classification advice. Compliance decisions remain the responsibility of the importer and their customs broker or trade attorney. TariffWatch does not guarantee that any classification, exposure estimate, or comment letter will be accepted by CBP, BIS, or Commerce.

FAQ

References and primary sources

1. CBP — Automated Commercial Environment (ACE) landing page (cbp.gov).
2. CBP — CATAIR (Customs and Trade Automated Interface Requirements) technical documentation.
3. CBP — Getting Started with ACE (account application overview).
4. Executive Order 13659 — Streamlining the Export/Import Process for America's Businesses (single-window mandate).
5. Trade Facilitation and Trade Enforcement Act of 2015 — Public Law 114-125.
6. Trade Act of 2002 — Public Law 107-210 (advance-electronic-data authorization).
7. 19 CFR Part 4 — Vessels in Foreign and Domestic Trades (eCFR).
8. 19 CFR Part 122 — Air Commerce Regulations (eCFR).
9. 19 CFR Part 141 — Entry of Merchandise (eCFR).
10. 19 CFR Part 142 — Entry Process (eCFR).
11. 19 CFR Part 111 — Customs Broker Licensing (eCFR).
12. CBP — CROSS rulings database.
13. USITC — Harmonized Tariff Schedule of the United States (HTSUS).
14. Federal Register — Federal Register (tariff-action notices).
15. BIS — Bureau of Industry and Security (Section 232 authority).
16. USTR — U.S. Trade Representative (Section 301 authority).
17. TariffWatch — TariffWatch product overview.
18. Related reading — HTS classification guide for beginners (2026).
19. Related reading — Interactive HTS checker (Section 232 exposure).

TariffWatch is not affiliated with the U.S. Department of Commerce, the Bureau of Industry and Security (BIS), U.S. Customs and Border Protection (CBP), or the U.S. International Trade Commission (USITC).

Digital Empire Holdings LLC, 30 N Gould St Ste N, Sheridan WY 82801