ACE Foreign Importer of Record Filing Changes

Foreign importer of record filings are entering a more structured compliance environment. New ACE fields will require customs brokers, self-filers, and software providers to classify importer status accurately, report certain broker relationships, and maintain supporting records before production validations begin on January 5, 2027.

ACE Deployment Timeline and Technical Scope

The Foreign IOR Enhancement is scheduled to become available in the ACE Certification environment on November 12, 2026. Production deployment is scheduled for January 5, 2027, giving ABI software providers, customs brokers, and self-filers a limited period to complete development, certification testing, and operational implementation.

The enhancement affects both cargo release and entry summary processing. It also updates the supporting ACE query functions, error dictionaries, and validation messages that filers use to identify and resolve rejected transmissions.

CATAIR Changes for Entry Summary and Cargo Release

For entry summary transactions, Entry Summary Create/Update Version 112 adds three elements to the 15-record:

• U.S. Importer of Record Indicator
• Broker Acting as IOR Indicator
• Principal on Power of Attorney

Entry Summary Query Version 28 and Entry Summary Error Dictionary Version 56 are also being updated to support the new data and related responses.

For cargo release transactions, Cargo Release Version 41.1 adds information to the SE-20 record. The additions include the U.S. IOR Indicator, Broker Acting as IOR Certification, Principal on Power of Attorney, and Principal on Power of Attorney Type. The Cargo Release Error Code file is also being revised.

These are not merely visual changes to CBP Form 3461 and CBP Form 7501. ABI systems must populate the correct records, apply conditional requirements, interpret error responses, and preserve the submitted values for audit and client-service purposes.

Testing should cover complete transaction lifecycles rather than isolated fields. That includes initial cargo release, entry summary creation, corrections, queries, and scenarios involving broker-held importer numbers. Filers should also verify that user interfaces, data imports, API mappings, and document-generation processes all reflect the same IOR classification.

How the Three Foreign IOR Fields Work

The new fields require filers to distinguish the legal status of the importer from the broker's role in the transaction. Treating all importer numbers as equivalent will create significant rejection and compliance risk once the production validations begin.

U.S. Importer of Record Indicator

The U.S. Importer of Record field is reported as Y when the named IOR meets the applicable U.S. IOR criteria. It is also reported as Y when a customs broker acts as the IOR and the principal identified on the power of attorney meets those criteria. The field is reported as N when neither condition is satisfied.

The determination should be based on verified facts, not assumptions drawn from an EIN, mailing address, corporate name, or prior filing history. A foreign-owned entity can potentially meet U.S. IOR criteria, while an entity with U.S. contact information may not. Brokers should establish a documented classification process and retain the evidence supporting each answer.

Broker Acting on Behalf of a Principal

The Acting on behalf of field is Y when the customs broker identifies itself as both the filer and the importer of record while making entry for a principal. It is N when the broker is not serving in that dual capacity.

This field should not be set to Y merely because the broker holds a power of attorney or transmits the entry. Most brokerage transactions involve representation under a power of attorney without the broker becoming the importer of record.

Principal on Power of Attorney

The Principal on Power of Attorney field is generally required when a non-CTPAT validated broker acts as IOR for a principal. The broker reports the principal's importer number, which may be an SSN, EIN, or CBP-assigned number associated with the principal's CBP Form 5106 record.

Conditional field logic should prevent submission without the principal when that information is required. Because importer numbers can include sensitive data, firms should also review access controls, masking, retention, and secure transmission practices. The operational objective is a consistent relationship among the entry, power of attorney, importer record, and supporting onboarding documentation.

Broker Readiness, Rejection Risk, and Recordkeeping

The production date creates both a technology deadline and a client-management deadline. Brokers should not wait for an ACE rejection to determine whether an importer is foreign, whether the broker is acting as IOR, or whether the principal's CBP Form 5106 information is current.

Build a Client-Level IOR Classification

Each importer relationship should be mapped to a documented Y or N determination for U.S. IOR status. The file should identify the facts reviewed, the responsible reviewer, the date of verification, and any circumstances that would require reassessment.

Brokers should generally incorporate this analysis into onboarding and periodic client reviews. Changes in entity structure, address, residency, ownership, or customs registration may require renewed verification. Supporting U.S. IOR verification records should typically be retained for five years, with controls for ongoing confirmation.

Power of attorney records also require attention. When a broker may act as IOR, the named principal, importer number, and Form 5106 record should align. Discrepancies involving legal names, entity identifiers, or outdated addresses can complicate both filing and post-entry review.

Prepare for Production Validations

Beginning January 5, 2027, CBP may reject entries or entry summaries when a foreign IOR files without the required CTPAT validation or involvement of a CTPAT validated broker. A submission may also be rejected when a non-CTPAT validated broker acts as IOR but omits the principal information required for that transaction.

Testing should include positive and negative scenarios for each combination of importer status, broker status, and principal reporting. Operations teams also need written procedures for interpreting new errors, escalating classification questions, correcting data, and communicating shipment consequences to clients.

A delayed compliance request may be available in appropriate circumstances, but it must be submitted no later than January 5, 2027. Firms considering that option should evaluate eligibility, scope, and operational impact before the deadline rather than treating delayed compliance as an automatic extension.

Importer identity should also remain consistent across post-entry programs. Duty drawback claims rely on the importer information associated with underlying import entries. Although the new fields do not themselves add data elements to drawback claim transmissions, conflicting IOR records can impede import matching, documentation review, and claim support.

Frequently Asked Questions

When Do the New ACE Foreign IOR Fields Take Effect?

The fields are scheduled for ACE CERT availability on November 12, 2026, followed by production deployment on January 5, 2027. Software teams should use the CERT period to validate record placement, conditional requirements, queries, corrections, and error handling. Brokers should complete client classification and procedure updates before the production date.

Does a Broker Report Acting on Behalf of as Y Whenever It Holds a Power of Attorney?

No. The indicator is Y only when the broker lists itself as both the filer and the importer of record while acting for a principal. A broker that files an entry for an importer under a standard power of attorney generally reports N if the broker is not itself listed as IOR.

What Information Is Reported for the Principal on Power of Attorney?

The filer reports the principal's importer of record number. Depending on the principal, this may be an EIN, SSN, or CBP-assigned number. The identifier should correspond to the principal's Form 5106 record. Firms should apply appropriate security controls when processing personally identifiable or otherwise sensitive importer data.

What Could Cause an Entry or Entry Summary Rejection?

Potential rejection scenarios include a foreign IOR filing without the required CTPAT status or qualifying broker involvement, a missing principal when a non-CTPAT validated broker acts as IOR, and inconsistent field combinations. Technical errors may also arise from incorrect record formatting, invalid indicator values, or importer numbers that do not align with CBP records.

What Should Brokers Complete Before January 5, 2027?

Brokers should classify affected clients, document U.S. or foreign IOR status, review powers of attorney, confirm Form 5106 information, update onboarding procedures, test ABI changes, and train entry personnel. They should also establish an escalation process for uncertain classifications and determine whether a delayed compliance request is appropriate.

Do the New Fields Apply Directly to Duty Drawback Claims?

The enhancement adds fields to cargo release and entry summary transactions, not to drawback claim transmissions. However, drawback claims depend on the identity and data associated with the underlying import entries. Brokers and importers should therefore maintain consistent importer numbers, entity records, and IOR documentation across entry and drawback operations.

How Stable Software Can Help

Preserve Importer Identity Across Duty Drawback Operations

Foreign IOR compliance reinforces the importance of consistent importer identity across entry records, powers of attorney, Form 5106 data, and downstream refund programs. Drawback claims can become more difficult to support when importer numbers or entity records conflict with the underlying entries.

Stable Software provides DrawbackAI, flat-license duty drawback software that U.S. customs brokers can white-label for importer clients and use to file under their own filer codes. Stable Software charges a flat software license and never takes a percentage of the refund. Customs brokerage firms reviewing how importer data flows into drawback operations can learn more about Stable Software's approach for customs brokers.

Resources