CBP Tightens ACE EDI Filing Rules for 2026

Two separate ACE changes landed on U.S. importers within three weeks of each other this summer, and both flow straight through the EDI/ABI pipeline that customs brokers and internal trade compliance teams already maintain. On July 15, 2026, CBP tightened ACE filing requirements for import entries, and on August 5, 2026, a separate final rule changed how duty increases from Post Summary Corrections get paid. If your team treats these as trade-compliance memos to forward to the customs broker and forget, you're missing the part that actually breaks: the data mapping between your ERP, your EDI layer, and the ABI transaction set your filer submits.

What CBP actually changed

The July 15 update applies to every import entry filed through ACE, not a subset of commodities. The updated filing requirements apply to all import entries and add new data fields covering origin verification, justification for tariff classification, and supplier traceability. Non-compliant submissions face rejection or clearance delays. That's a direct hit on whatever system generates your entry data today, whether that's a broker portal, a self-filed ABI connection, or a third-party trade management platform.

The August 5 change is narrower in scope but sharper in consequence. On August 3, 2026, in CSMS #69428352, CBP announced changes to the Post Summary Correction process that became effective August 5, 2026, following Federal Register Notice 91 FR 41053 issued July 6, 2026. Filers must now electronically remit increases in duties, taxes, and fees resulting from a PSC through ACH, and CBP will no longer accept check or cash payments for these increases. Partial payments aren't accepted, and ACE will not allow subsequent PSCs if a filer waits for billing at liquidation and the initial PSC remains unpaid.

Why this is an EDI problem, not just a compliance memo

Entry and entry summary data can't be filed through the ACE web portal at all. The Automated Broker Interface is the only approved method available for filing entry and entry summaries in ACE. Every field CBP adds to an entry requirement lands in the ABI CATAIR record layout your broker's software (or your own ABI connection, if you self-file) has to support. The main body of the CATAIR consists of the data record formats used for conducting electronic data interchange between the participant's computer system and Customs ABI. If you've mapped 856 ASNs and 810 invoices before, the mental model is the same: a fixed-format transaction set with mandatory, conditional, and optional elements, except this one has no tolerance for a rejected transmission sitting in a queue overnight while your container sits at the port.

Where the new fields actually come from

Origin verification, tariff classification justification, and supplier traceability data usually already exist somewhere in your document flow. Country of origin lives on the item master. HS classification lives on the commercial invoice. The problem is that most ERP/EDI configurations capture this at the item or PO level and never propagate it down to the lot or shipment level the broker's filing system now needs. If your ASN carries a single blanket country-of-origin flag for a multi-supplier shipment, that's the gap a July 15 rejection will expose.

• Audit whether your ERP-to-broker data feed carries lot-level or shipment-level origin data, not just item-master defaults.
• Confirm your customs broker or ABI software vendor has implemented the new CATAIR field set for entry summary filings.
• Verify ACH enrollment is complete and tested before your next Post Summary Correction is due, since filers must submit PSC electronic payment authorizations through ABI and to participate in either the ACH Debit or ACH Credit payment programs must enroll with CBP.
• Check whether your finance team's remittance workflow (the customs equivalent of an 820) can actually generate an ACH authorization on the timeline CBP now requires.

The ACH change hits at an unusually busy moment

The timing matters more than it looks. CBP built a separate tool inside ACE this year to handle a much larger financial event: on April 20, 2026, CBP launched the first phase of the Consolidated Administration and Processing of Entries tool in ACE to administer refunds of duties imposed under the International Emergency Economic Powers Act, after the Supreme Court held in February 2026 that certain IEEPA tariffs were unlawful. That refund volume, combined with the new PSC payment mandate, means finance and trade compliance teams are pushing more correction and payment traffic through ACE and ABI this year than in any recent cycle. Getting your ACH setup wrong now doesn't just delay one correction, it can block every subsequent PSC on that entry.

Deadlines at a glance

Customs data and carrier connectivity are becoming the same problem

Trade compliance data increasingly rides the same integration layer as shipment execution data. Platforms like Descartes and e2open already bundle customs and denied-party screening functions alongside carrier connectivity, and multi-carrier and TMS tools such as MercuryGate, Oracle Transportation Management, SAP TM, and Cargoson are under growing pressure to pass HS codes and origin data cleanly from booking through to entry filing. Treat "carrier connectivity" and "customs data connectivity" as one integration problem, because CBP just gave you another reason why they already are.

What to do this week

Don't wait for a rejected entry to discover the field gap. Pull a sample entry, run it against the new July 15 field requirements with your broker, and confirm your ACH enrollment is live and tested before your next Post Summary Correction comes due. If your customs broker or ABI software vendor hasn't sent you a change notice on either update yet, that's the call to make today, not after the next clearance delay.