ABI client rep: Your CBP Contact for ACE Testing and Certification

Key Points

• An ABI client rep is the CBP Office of Trade contact assigned to each ABI filer, whether a broker, an importer self-filer, or a software vendor.
• The ABI client rep is assigned when a new filer applies for an ABI filer code, and CBP posts assignments by filer code.
• The ABI client rep sets up the test environment, oversees certification transactions before production, and remains the contact for rejects, system messages, outages, and new-program testing.
• The Automated Broker Interface rules sit in 19 CFR part 143 subpart A (sections 143.1 to 143.8); confirm current text before relying on any provision.
• The ABI client rep is not the Center account manager and not the ACE Trade Account Owner, and the port is the wrong first call for a systems problem.

On this page

1. At a glance
2. What does an ABI client rep do?
3. When does a filer work with the ABI client rep?
4. How the ABI client rep connects to ACE transactions and related programs
5. Who is not the ABI client rep?
6. Common ABI client rep mistakes and what they cost
7. Frequently asked questions
8. What importers and brokers should do
9. Key references

An ABI client rep (ABI client representative) is the CBP Office of Trade contact assigned to each Automated Broker Interface filer, including customs brokers, importer self-filers, and software vendors, to handle that filer's ACE connectivity, testing, certification, and production issues. The ABI client rep is assigned when the filer applies for an ABI filer code and stays with the filer from test setup through live entry filing. The role is a systems relationship, not a trade account or commercial one.

This entry reflects the CBP framework as of November 2026. The links in this article go to the primary documents: the regulations and official CBP program pages themselves. Read the source.

At a glance

• Full name: ABI client representative, CBP Office of Trade
• Who uses it: ABI filers: customs brokers, importer self-filers, and software vendors
• When in the lifecycle: From the ABI filer code application through testing, certification, and ongoing production
• System or channel: ACE via the Automated Broker Interface; contact method and hours: confirm with CBP
• Governing authority: 19 CFR part 143 subpart A (Automated Broker Interface, 143.1 to 143.8)
• Identifier: Assignments are posted by ABI filer code
• Related terms: ACE Cargo Release, disposition codes, CATAIR Appendix B, ACE in-bond, ACE truck eManifest

What does an ABI client rep do?

An ABI client rep is the single CBP technical point of contact for one ABI filer's electronic interface with ACE. The Automated Broker Interface itself is governed by 19 CFR part 143 subpart A, which covers who may participate, how filers apply, and the conditions for using the interface. The ABI client rep is the person who puts that participation into practice for a given filer code.

Core responsibilities

• Test environment setup: configures the filer's access so transactions can be sent and returned without affecting live cargo.
• Certification oversight: reviews the certification transactions a filer must complete before CBP allows production filing.
• Production support: remains the contact for rejects, system messages, and outages once the filer is live.
• New-program testing: coordinates testing when a filer adds PGA message sets, new record types, or other new transaction types.
• Escalation: receives persistent ACE errors and vendor-related problems that the filer cannot resolve on its own.

When does a filer work with the ABI client rep?

A filer first works with the ABI client rep when it applies for an ABI filer code, and the relationship continues for as long as that filer code transmits to ACE. The timeline below describes the typical sequence; confirm current application steps on the CBP automated systems pages.

Application and assignment

A new filer applies for an ABI filer code under the participation rules in part 143 subpart A. CBP then assigns an ABI client rep and posts assignments by filer code, so a filer can identify its representative from its own code.

Testing and certification

The ABI client rep sets up the test environment and watches the certification transactions. A filer does not move to production for a transaction type until certification for that type is complete.

Production and change

After go-live, the ABI client rep handles rejects that point to a systems issue, interprets system messages, and is the contact during outages. When the filer adds a new program, such as a PGA message set or a new record type, the ABI client rep coordinates fresh testing before that transaction goes live.

How the ABI client rep connects to ACE transactions and related programs

The ABI client rep supports the filer's technical ability to send every ABI transaction type, even though the trade rules for each transaction live elsewhere. Knowing which questions belong to the ABI client rep, and which belong to the filer's own compliance work, saves time.

• ACE Cargo Release: the ACE transaction, successor to the paper CBP Form 3461, that transmits release data. If cargo release transmissions fail at the interface level, the ABI client rep is the contact. See ACE Cargo Release: How Brokers Transmit Release Data to CBP.
• Disposition codes and 1C release: ACE cargo release disposition codes are the statuses CBP returns in ABI notifications, and disposition code 1C means CBP has released the entry. If expected disposition messages stop arriving, that is a systems question for the ABI client rep; a hold itself is not.
• CATAIR Appendix B: CATAIR Appendix B, Valid Codes, lists code values used across ABI transactions. A filer whose software is sending outdated code values should check the appendix first; see CATAIR Appendix B: Valid Codes Reference for ABI Filers.
• ACE in-bond and ACE truck eManifest: ACE in-bond, the electronic in-bond system, and ACE truck eManifest, the electronic truck manifest highway carriers transmit before arrival, are separate applications. Filers adding them should treat each as a new transaction type for testing.
• ACE AD/CVD case management: the ACE function publishing Commerce's antidumping and countervailing duty case data. Case number questions are not systems questions, but rejects caused by interface handling of case data may be.
• ACE reconciliation: ACE Reconciliation (entry type 09) flags and reconciliation entries are distinct transactions that may require their own certification.
• MID code and MID construction: the Manufacturer Identification code (MID) is built under CBP's MID construction rule from the manufacturer's country code, name, and address. A reject for a malformed MID code is a data error the filer fixes, not an issue to escalate to the ABI client rep.

Who is not the ABI client rep?

The ABI client rep is a CBP Office of Trade systems contact, and the role is regularly confused with two others. The Center account manager is the importer's contact at a Center of Excellence and Expertise for trade and account matters; that person does not handle connectivity or certification. The ACE Trade Account Owner controls the importer's or broker's ACE portal account and user access; that is a trade-side role, not a CBP one. The ABI client rep is also not a broker's own commercial client. For more on portal roles, see ACE proxy TAO: Trade Account Owner Proxy Role Explained.

Common ABI client rep mistakes and what they cost

Most problems with the ABI client rep relationship come from routing systems issues to the wrong place or from letting the relationship lapse.

• Calling the port for a systems problem: port staff handle cargo and entry questions, not ABI connectivity. Systems issues routed to the port tend to stall while freight waits.
• Letting the software vendor own the relationship: vendors have their own ABI client rep relationships, but the filer code is the filer's. A broker that never contacts its own ABI client rep may lack visibility when an outage or reject pattern affects its entries.
• Skipping certification for a new transaction type: sending a new PGA message set or record type into production without the ABI client rep's certification can produce rejects and delayed release. Confirm certification status before going live.

Frequently asked questions

How do I find my ABI client rep?

CBP posts ABI client rep assignments by ABI filer code. Check the CBP automated systems pages for the current listing and contact channel; this article does not list names, contact details, or hours.

Does an importer self-filer have an ABI client rep?

Yes. An importer self-filer that holds an ABI filer code is assigned an ABI client rep, just as a broker or software vendor is.

Should I contact the ABI client rep about a CBP hold?

Usually not. A hold or other disposition is a cargo or admissibility matter. Contact the ABI client rep only if the problem is with transmission or receipt of the messages themselves.

Do I need the ABI client rep to add a PGA message set?

Yes. New-program testing, including PGA message sets and new record types, runs through the ABI client rep before production filing.

What importers and brokers should do

• Confirm which ABI client rep is assigned to each ABI filer code you use, using CBP's posted assignments.
• Keep a direct relationship with your ABI client rep even when a software vendor handles most technical work.
• Before transmitting any new transaction type, confirm with the ABI client rep that certification is complete.
• Route systems problems to the ABI client rep and cargo or account questions to the port or Center account manager.

Key references

• 19 CFR part 143 subpart A: Automated Broker Interface regulations, sections 143.1 to 143.8.
• CBP Automated Systems: CBP's landing page for ACE, ABI participation, and related technical resources.
• 19 CFR part 143 (Cornell LII): alternate reading copy of the special entry procedures part containing the ABI subpart.