Adding Sub-Accounts and Notify Party in ACE (Form 4811): Step-by-Step Guide

What is Form 4811 used for in ACE?

CBP Form 4811 is the form used to designate a custodian for delivery of CBP correspondence, refunds, and notices on behalf of an importer of record. In ACE workflow, Form 4811 supports adding sub-accounts under a parent IOR and designating a Notify Party who receives ACE notifications, including refund disbursement notices and CAPE-related correspondence. Proper Form 4811 configuration is foundational for CAPE refund workflows because misconfigured Notify Party designations can cause refund notices and disbursement records to go to the wrong party, leading to missed deadlines and operational confusion.

Why does Form 4811 matter for CAPE refunds?

Form 4811 controls who receives CAPE-related correspondence in ACE. If the Notify Party designation is incorrect or outdated, REV-603 (Trade Refund Report), REV-615 (Trade CAPE Detail Refund Report), and other CAPE notices may go to the wrong party. The importer may not see their own refund disbursement notices, creating reconciliation gaps and missed dispute windows. For high-volume CAPE filings with thousands of entries, accurate Form 4811 configuration is foundational to managing the refund workflow.

---

TL;DR: CBP Form 4811 is foundational ACE configuration for designating sub-accounts under a parent IOR and Notify Party for CBP correspondence delivery. For CAPE refund workflows, Form 4811 configuration controls who receives REV-603, REV-615, and other CAPE notices in ACE. Misconfigured Form 4811 designations can cause refund correspondence to go to the wrong party, creating reconciliation gaps and missed dispute windows. This guide covers the Form 4811 purpose, the step-by-step submission process, common configuration gaps that affect CAPE workflows, and how to verify configuration is correct before filing CAPE Declarations. CBP processed approximately $166 billion in IEEPA duties across 53 million entries from 330,000 importers, and the Form 4811 configuration for the importer population varies widely; teams that handle CAPE workflows for clients commonly find Form 4811 gaps that need to be addressed before CAPE filing can proceed effectively. GingerControl's IEEPA refund service handles Form 4811 review and configuration as part of CAPE workflow setup.

Last updated: May 2026

---

What Form 4811 Actually Does

CBP Form 4811 (Claim for Importation by Notify Party or other authorized person) is used to designate a custodian for delivery of certain CBP correspondence. The form has several configurations that map to common ACE workflows:

Notify Party designation. The party that receives ACE notifications on behalf of the importer, including refund disbursement notices, liquidation notices, and correspondence about specific entries.

Sub-account configuration. When a parent IOR has sub-accounts (subsidiaries, related entities, or separately filed business units), Form 4811 designates the relationship.

Refund custodian. Specifies who receives refund disbursements when the importer's refund is processed.

Correspondence delivery address. Provides the physical or electronic delivery address for CBP correspondence.

Form 4811 is filed with CBP and recorded in ACE. The configuration affects how CBP correspondence flows in the system.

Why Form 4811 Is Foundational for CAPE Workflows

CAPE generates several ACE correspondence types that flow through Form 4811-configured channels:

REV-603 (Trade Refund Report). Shows refund disbursements for the importer. The report is accessible in ACE under the importer's profile; Notify Party designation controls who receives ACE notifications when REV-603 entries appear.

REV-615 (Trade CAPE Detail Refund Report). Provides CAPE-specific entry-level detail. Like REV-603, ACE notification flows through Form 4811 configuration.

CAPE rejection notices. When a CAPE Declaration or specific lines are rejected, the notification goes to the configured ACE recipient.

Disbursement notices. When ACH refund disbursement occurs, the notification flows through the Notify Party.

If Form 4811 designates the wrong Notify Party (an outdated broker, a former employee, a defunct entity), the CAPE-related correspondence goes to the wrong recipient. The importer may not see their own refund disbursement notices, creating reconciliation gaps and missed dispute windows.

Common Form 4811 Configuration Gaps

Five gaps that commonly affect CAPE workflows:

Gap 1: Outdated Notify Party. The Form 4811 on file designates a broker, consultant, or employee who is no longer the right recipient. Common after broker changes, organizational restructuring, or personnel turnover.

Gap 2: Sub-account not linked to parent IOR. A subsidiary or related entity files entries under its own IOR but is not linked to the parent IOR for correspondence aggregation. The parent does not see subsidiary refund activity through the parent's ACE profile.

Gap 3: Notify Party address invalid. The designated address (physical or electronic) is no longer valid. CBP correspondence may not reach the recipient.

Gap 4: Conflicting designations across forms. Multiple Form 4811 submissions over time have conflicting designations, and ACE retains an outdated configuration.

Gap 5: No Form 4811 on file. For some IORs, no Form 4811 has been filed, leaving the default ACE configuration in place. The default may not match operational needs.

Each gap creates downstream issues in CAPE workflow. Verifying Form 4811 configuration before filing CAPE Declarations prevents the issues from surfacing during the refund process.

Step-by-Step: Submitting Form 4811

The Form 4811 submission process:

Step 1: Obtain the current form. Download Form 4811 from the CBP Forms page. Use the most recent version; older versions may not be accepted.

Step 2: Identify the IOR and designation type. Specify the importer of record (typically by IOR number) and the type of designation (Notify Party, sub-account, refund custodian, etc.).

Step 3: Provide the designated party information. Name, address, phone, and other identification for the party being designated. For Notify Party, ensure the contact information is current.

Step 4: Sign and authorize. The form requires authorized signature from the importer of record. The signatory should be an officer or authorized representative.

Step 5: Submit to CBP. Form 4811 submission methods vary. Electronic submission through ACE, fax submission to CBP, or mail submission may be required depending on the specific configuration. Check current CBP guidance for submission method.

Step 6: Verify acceptance in ACE. After CBP processes the form, verify the configuration appears correctly in ACE. The verification step catches processing errors before they affect downstream operations.

How to Verify Your Form 4811 Configuration Is CAPE-Ready

Before filing CAPE Declarations, verify Form 4811 configuration through ACE:

Verification 1: Notify Party is current. Confirm the Notify Party on file is the party that should receive CAPE correspondence. For organizations with internal compliance teams handling CAPE, the Notify Party should typically be the internal team, not an external broker (unless the broker is actively handling CAPE filings on behalf of the importer).

Verification 2: Sub-accounts are linked correctly. For organizations with multiple IORs (subsidiaries, related entities, business units), confirm the sub-account linkages match the operational structure.

Verification 3: Address and contact information are valid. Confirm the designated address and contact are current. Outdated information causes CBP correspondence delivery failure.

Verification 4: Authorization is valid. Confirm the authorization on file was made by an authorized signatory. Authorization signed by someone no longer with the organization may be considered invalid.

If any verification fails, file an updated Form 4811 before initiating CAPE Declaration filing.

Form 4811 and CAPE Sub-Account Patterns

For organizations with multi-entity structures, Form 4811 sub-account configuration affects how CAPE flows across the entities:

Pattern 1: Single IOR, internal compliance team Notify Party. Simplest pattern. Form 4811 designates the internal compliance team as Notify Party. CAPE filings happen at the IOR level; correspondence flows to the internal team.

Pattern 2: Single IOR, external broker Notify Party. Form 4811 designates an external customs broker as Notify Party. CAPE correspondence flows through the broker, who forwards to the importer. Adds a step but works if broker handling is reliable.

Pattern 3: Multiple IORs, parent-subsidiary structure. Each subsidiary IOR has its own Form 4811. The parent organization may need separate ACE access to view consolidated CAPE activity across subsidiaries. Operational coordination across multiple IORs requires structural alignment.

Pattern 4: Centralized compliance team across multiple IORs. Centralized compliance team designated as Notify Party for multiple IORs. The team sees CAPE correspondence for each IOR through ACE. Pattern works for organizations with strong central compliance.

The right pattern depends on organizational structure. Form 4811 configuration should reflect the operational reality.

What to Do if Form 4811 Configuration Is Wrong After CAPE Filing

If CAPE Declarations have been filed under incorrect Form 4811 configuration, immediate remediation steps:

Step 1: Identify what notices were missed. Review ACE for any CAPE-related notices (REV-603, REV-615, rejection notices) that flowed to the wrong party.

Step 2: File corrected Form 4811. Submit updated Form 4811 with correct Notify Party designation.

Step 3: Coordinate with the wrong-party recipient. If a broker, former employee, or outdated address received CAPE correspondence, retrieve any documents from that party. Some recipients may have discarded notices believing they were not relevant.

Step 4: Reconcile against the original CAPE Declaration. Use the reconciliation framework to identify any disbursements, exclusions, or offsets that may have been missed.

Step 5: Catch up on missed deadlines if possible. For dispute deadlines (offset disputes, line exclusion alternative recovery channels), assess whether deadlines have passed and whether late dispute is still procedurally possible.

The remediation is operationally complex but is the right approach for organizations that discover Form 4811 configuration gaps after CAPE filing.

Frequently Asked Questions

What is CBP Form 4811?

CBP Form 4811 is used to designate a custodian for delivery of CBP correspondence, refunds, and notices on behalf of an importer of record. In ACE, the form supports adding sub-accounts and designating Notify Party for ACE notifications.

Do I need Form 4811 for CAPE filing?

Form 4811 is not specifically required for CAPE filing itself, but the configuration affects who receives CAPE correspondence. If Notify Party is misconfigured, CAPE-related notices may not reach the right party. Verifying Form 4811 before CAPE filing prevents downstream issues.

How do I submit Form 4811?

Submission methods vary; check current CBP guidance for the right method. Electronic submission through ACE, fax, or mail may be available depending on the specific configuration. Most ACE-active filers use electronic submission.

Can I use Form 4811 to designate multiple Notify Parties?

Form 4811 typically designates a single Notify Party per IOR. For organizations needing multiple recipients to see CAPE correspondence, alternative approaches include centralized internal forwarding, ACE access for multiple users, or external systems that aggregate CBP correspondence.

What is the difference between Notify Party and Sub-Account in Form 4811 context?

Notify Party is the designated recipient for CBP correspondence. Sub-Account is a related IOR linked under a parent IOR structure. The two are different concepts; an IOR may have a Notify Party designated, separate IORs may be linked as Sub-Accounts of a parent, or both configurations may apply.

How quickly does Form 4811 update take effect in ACE?

CBP processes Form 4811 submissions typically within several business days. After processing, the updated configuration appears in ACE. Verify the update before relying on it for downstream workflow.

Can I file CAPE Declarations under a different Notify Party than my regular import operations?

The Notify Party designation is per IOR. If CAPE filings need a different Notify Party than regular import operations, the Form 4811 configuration affects all correspondence for the IOR, not just CAPE. For organizations needing CAPE-specific Notify Party, the workaround typically involves internal forwarding rather than changing the ACE configuration.

How does GingerControl handle Form 4811 review?

GingerControl's IEEPA refund service handles Form 4811 review as part of CAPE workflow setup. The review identifies configuration gaps, supports Form 4811 submission for required updates, and verifies the configuration is CAPE-ready before Declaration filing begins.

---

Verify Your Form 4811 Configuration Before CAPE Filing

If you have CAPE Declarations to file (or are receiving CAPE refunds based on prior filings), Form 4811 configuration affects who receives the correspondence. Misconfigured Notify Party designations create reconciliation gaps and missed dispute windows that can cost meaningful money.

Get a no-cost CAPE workflow review from GingerControl. The review includes Form 4811 verification, configuration update support, and CAPE Declaration filing across your IORs.

GingerControl is not just a tool. We work with importers, customs brokers, and trade compliance counsel on ACE configuration, Form 4811 management, and CAPE workflow setup. Talk to our team about your Form 4811 and CAPE situation.

---

References

[REF 1] CBP Form 4811, Claim for Importation by Notify Party Data cited: Form 4811 framework and configuration types Source: CBP Form 4811

[REF 2] U.S. Customs and Border Protection, IEEPA Duty Refunds Data cited: CAPE workflow framework Source: CBP IEEPA Duty Refunds

[REF 3] CBP IEEPA Refunds and CAPE Webinar (April 2026) Data cited: 330,000 importers, $166 billion IEEPA duties, 53 million+ entries Source: CBP IEEPA Refunds CAPE Webinar Published: April 2026

[REF 4] CBP ACE Portal Documentation Data cited: ACE access and notification framework Source: CBP ACE

[REF 5] CBP REV-603/REV-613 Quick Reference Card Data cited: REV-603 and REV-613 correspondence framework Source: CBP REV Reports QRC Published: April 2026

[REF 6] CBP Power of Attorney Guidance Data cited: POA framework underlying Form 4811 designations Source: CBP Power of Attorney