ACE Portal Account Merger Requests After Acquisitions

Acquisitions can leave trade teams managing fragmented importer records, user access, reporting, and refund arrangements. The ACE Portal account merger process now provides a formal application path for placing multiple accounts under one top account, but successful consolidation still requires careful preparation across customs, finance, brokerage, and drawback functions.

What Changed in the ACE Portal Account Merger Process

A Formal Application Path for Acquiring Companies

On November 5, 2026, U.S. Customs and Border Protection added a “Merge Accounts” option to the ACE Portal Account Application. The option allows an acquiring entity to request that two or more ACE Secure Data Portal accounts be consolidated under a single top account following an acquisition.

The Trade Account Owner for the acquiring entity generally submits the request through the automated account application. This creates a defined intake path for post-acquisition account consolidation and reduces dependence on informal routing through individual contacts or separate email correspondence.

The change is administrative rather than transactional. It addresses the organization of ACE Portal accounts, but it does not automatically revise every customs relationship connected to the acquired business. Importer identifiers, customs bonds, broker powers of attorney, Automated Clearinghouse arrangements, refund instructions, drawback claimant status, and internal system mappings may still require separate review.

What an Account Merger Does and Does Not Do

An ACE Portal account merger generally places related accounts within a consolidated hierarchy for access and reporting purposes. It should not be treated as an automatic legal transfer of importer obligations, customs liabilities, or refund rights.

That distinction matters because an acquisition can take several forms. A stock purchase may leave the acquired legal entity and importer identity intact, while an asset purchase may create more substantial changes to importer roles, bonds, records, and contractual rights. Corporate trade teams should therefore evaluate the legal transaction structure before assuming that a Portal account merger resolves the broader customs integration.

The request should be viewed as one workstream within a larger post-acquisition trade compliance plan. Legal, customs, treasury, tax, brokerage, and information technology stakeholders may all have related responsibilities.

Preparing a Complete ACE Account Consolidation Request

Build an Inventory of Accounts and Importer Identifiers

The acquiring company should begin by identifying every ACE Portal account associated with the acquired entities. The inventory should include the account name, account identifier, legal entity name, importer of record numbers, Employer Identification Numbers, suffixes, and any customs-assigned importer numbers.

Trade teams should also document which employees, customs brokers, consultants, and service providers currently access each account. An account that appears inactive may still contain historical reports, entry data, liquidation information, reconciliation activity, or drawback records needed for compliance and audit support.

The inventory should distinguish between identifiers that remain active, identifiers that will be used only for historical reporting, and identifiers that may require deactivation or separate maintenance. Duplicate names and legacy corporate names should be reconciled before submission so that CBP can clearly identify the acquiring and acquired accounts.

Prepare the Required Signed Letter

The merger request must include a letter on company letterhead signed by the Trade Account Owner or another legally authorized company official. The letter should clearly provide:

• The company names of the acquiring and acquired entities
• The relevant ACE account identifiers for each entity
• The date the subsidiary or acquired entity was purchased
• A current telephone number
• A current email address

The information should align with ACE records and the underlying transaction documents. Differences in punctuation, legal suffixes, former names, or account ownership can create avoidable questions during review.

Gather Supporting Documentation

Supporting files, including customs bond information, may be uploaded with the application. Even when a document is optional, it can help explain the relationship between entities or clarify which importer identities remain active.

Before filing, the company should confirm that the signatory has appropriate authority, all listed identifiers are accurate, and the proposed top account belongs to the acquiring entity. Retaining a complete submission package also supports internal governance and future audit inquiries.

Managing Access, Bonds, Payments, and Reporting

Review User Access Before and After Consolidation

An acquisition often changes who should be permitted to view customs information. Before an ACE account consolidation request is submitted, the acquiring company should review all users associated with the acquired accounts and determine whether each person still requires access.

Access decisions should follow the company’s current organizational structure rather than simply reproducing legacy permissions. Former employees, divested business personnel, temporary integration consultants, and outdated broker contacts may need to be removed. New compliance personnel may require access based on their responsibilities.

The company should also define who will serve as the Trade Account Owner and who will administer user access after consolidation. Backup coverage is important because account administration can become dependent on a single individual during periods of organizational change.

Validate Bonds and Broker Authorizations Separately

A Portal account merger does not necessarily amend customs bonds or broker powers of attorney. The acquiring company and its brokers should review whether continuous bonds remain sufficient and correctly associated with each active importer of record number. Transaction changes may also affect bond sufficiency calculations, especially when import volume shifts between entities.

Powers of attorney should be reviewed by legal entity and importer identifier. A broker’s authority for one acquired company should not automatically be assumed to extend to the acquiring company or another subsidiary. The transaction structure, surviving entities, and applicable authorization documents generally determine the correct approach.

Protect Payment and Refund Continuity

Trade and treasury teams should confirm that Automated Clearinghouse payment arrangements, refund instructions, bank accounts, mailing addresses, and financial contacts remain valid. This is particularly important when acquired entities are being dissolved, renamed, or integrated into a shared-service structure.

Reporting should also be tested after the merger. Users should verify that expected entry, liquidation, reconciliation, and refund data remain available under the new hierarchy. Any missing data should be investigated before legacy users or processes are retired.

Coordinating Duty Drawback After an Acquisition

Account Consolidation Does Not Decide Drawback Rights

An ACE Portal account merger does not, by itself, transfer or eliminate duty drawback rights. Drawback eligibility, claimant status, succession, certificates of delivery, manufacturing records, and supporting documentation are governed separately under the drawback framework, including 19 U.S.C. 1313 and 19 CFR part 190.

The legal form of the acquisition can materially affect the analysis. If the acquired entity remains in existence, it may continue to hold records or rights associated with imports, exports, or destroyed merchandise. If entities merge, dissolve, or transfer assets, the parties may need to establish whether and how drawback-related rights and obligations pass to a successor.

A company should not assume that placing two accounts under one ACE top account allows the acquiring entity to claim drawback on every import or export associated with the acquired business. The claimant must still support its legal right to file and satisfy the applicable recordkeeping and traceability requirements.

Align Brokers, Drawback Filers, and Internal Data

The customs broker and drawback filer should receive a complete list of acquiring and acquired entities, importer identifiers, filer relationships, acquisition dates, and planned account changes. They should also understand which entities will continue importing, exporting, paying duties, receiving refunds, or maintaining supporting records.

Internal data mappings require equal attention. Enterprise resource planning systems, broker feeds, product databases, and drawback records may use different versions of company names or importer numbers. If those mappings are not updated, otherwise eligible transactions may be omitted, duplicated, or attributed to the wrong entity.

Companies should preserve pre-acquisition records and create a documented cutoff methodology. Entry dates, export dates, inventory transfers, and corporate transaction dates may all affect how activity is allocated. The Portal merger may simplify account administration, but defensible drawback claims still depend on accurate legal analysis, data continuity, and documentation.

Frequently Asked Questions

Who Should Submit an ACE Portal Account Merger Request?

The Trade Account Owner for the acquiring entity generally submits the request through the ACE Portal Account Application. Another legally authorized company official may sign the required letter. The company should confirm that the proposed top account belongs to the acquiring entity and that the signatory’s authority is documented.

What Information Must Be Included in the Merger Letter?

The letter should be on company letterhead and identify the acquiring and acquired company names, their ACE account identifiers, the subsidiary acquisition date, and current telephone and email contact information. It should be signed by the Trade Account Owner or another authorized official.

Should Customs Bond Information Be Included?

Bond information may be included as supporting documentation and can help clarify the relationship between active importer identities. However, merging Portal accounts does not automatically modify a bond. Bond sufficiency, principal information, and importer number coverage should be reviewed separately with the company’s customs broker and surety contacts.

Does an ACE Account Merger Transfer Duty Drawback Rights?

No. The account merger is an administrative consolidation and does not independently determine drawback ownership, successor rights, or claimant eligibility. Those issues generally depend on the transaction structure, the parties’ legal rights, the timing of imports and exports, and the availability of compliant supporting records.

Can Legacy ACE Accounts Be Disregarded After the Merger?

Legacy accounts should not be disregarded until the company confirms that historical reports, entry records, liquidation data, reconciliation activity, and refund information remain accessible. User access and internal integrations should be tested before old procedures are discontinued or legacy administrators are removed.

How Stable Software Can Help

Maintain Drawback Control Through Corporate Change

Acquisitions create a heightened risk of fragmented import, export, and entity data. Stable Software’s DrawbackAI is 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 importer’s refund. This model allows brokers to maintain direct control of the client relationship and filing process while supporting drawback programs through acquisitions, account consolidations, and other organizational changes. Brokers evaluating how to support post-acquisition drawback activity can explore DrawbackAI as part of a broader compliance and account integration strategy.

Resources