What To Gather Before a Broker or Lawyer Reviews Your CAPE Entries

Use this CAPE entry review checklist to gather the right ACE data, liquidation details, protest posture, and ACH setup information before asking a broker or lawyer for help.

The fastest way to slow down a CAPE review is to ask for help before the file is organized.

Whether you are asking a customs broker, trade lawyer, or internal compliance lead to review your entries, they need the same basic picture first: what the entries are, where they sit procedurally, and what has already happened in ACE.

This checklist is the shortest way to build that review package before you send another email or another CSV.

Why This Matters

Most CAPE review delays come from one of three problems:

  • the entry list is incomplete
  • the liquidation posture is unclear
  • the filer or protest posture is missing

If the reviewer has to reconstruct those basics from scratch, you lose time and usually pay for avoidable back-and-forth.

Section 1: Entry-Level Basics

Gather these fields for every entry you want reviewed:

  1. full entry number
  2. entry date
  3. liquidation date, if any
  4. current liquidation status
  5. confirmation that the entry includes the relevant IEEPA Chapter 99 line

Without those five fields, nobody can reliably sort the entry into CAPE, protest, or CIT posture.

Section 2: Filing Identity and Broker Posture

The reviewer also needs to know who actually controls the filing lane.

Pull together:

  • the importer of record
  • the broker that filed the original entry summary
  • whether the same broker will handle any CAPE submission
  • whether a valid power of attorney is already in place

This is especially important when the file involves multiple brokers, because CAPE does not treat those entries as interchangeable.

Section 3: Protest and Litigation Posture

Do not send a CAPE review request without clarifying whether the entry is already in another path.

For each entry, identify:

  • whether a protest was filed
  • whether that protest is still open or suspended
  • whether the protest was filed solely for IEEPA refund purposes
  • whether any CIT litigation already exists or is under review

This is the difference between an operational cleanup and a path-selection problem.

Section 4: CAPE Readiness Data

If you are still considering CAPE, gather the pieces that actually matter for submission:

  • your current ACE account or reviewer access status
  • whether the refund recipient has active ACH refund setup in ACE
  • the draft or current entry-number-only CSV
  • any prior Validation Result File downloads
  • any Claim Details file already downloaded from Claim Status

These are the documents that explain what ACE has already accepted, rejected, or not yet reviewed.

Section 5: Category Blockers

For each entry, mark whether any of these are present:

  • drawback
  • reconciliation
  • final liquidation
  • pending-liquidation AD/CVD posture
  • warehouse or suspended status
  • filer mismatch or multi-broker complexity

Do not collapse these into a generic “problem entry” note. The reviewer needs to know which blocker applies.

Section 6: Money and Recipient Details

The reviewer does not need a perfect damages model on day one, but they do need a rough money picture.

Include:

  • estimated IEEPA duties paid
  • whether the expected refund should go to the IOR or a designated 4811 recipient
  • whether the receiving party’s ACH setup is already complete

That helps separate filing strategy from payment-setup risk.

A Simple Review Folder Structure

If you want the cleanest handoff, organize the file package like this:

  1. entry-list.csv or review spreadsheet
  2. liquidation-status.pdf or exported ACE status report
  3. protests/ folder for any protest documents
  4. cape-results/ folder for validation result files and claim details
  5. notes.md with a short summary of what you want the reviewer to answer

That structure is usually enough for a broker or lawyer to spot the real decision points quickly.

What Not To Do

Three things make reviews harder than they need to be:

Sending only screenshots without the entry list

Screenshots can help, but they do not replace the actual entry set.

Mixing CAPE-ready entries with obviously blocked entries and calling it one problem

That prevents the reviewer from classifying the file correctly.

Asking “Can I get a refund?” without showing the liquidation and protest posture

That question is too broad until the procedural facts are in place.

The Practical Takeaway

The best pre-review package is not a giant memo. It is a clean operating file.

If you gather the entry identifiers, liquidation posture, protest status, filer identity, CAPE artifacts, and refund-recipient setup up front, the review moves faster and the advice gets sharper.

For the technical submission side, pair this with our ACE Portal CAPE filing guide. For path selection, pair it with our CAPE, Protest, or CIT guide.

Need a reviewer to look at your entries, not just the theory?

If you already have the entry list, liquidation posture, and ACE output in hand, start with the assessment and we can direct the file to the right kind of review.

Get a Free Assessment

Sources

Source: CBP ACE and CAPE operational guidance published in April 2026.

Source: Advisor and trade-practice commentary on ACE data gathering, broker coordination, and refund preparation workflows.

We are not a law firm, customs broker, or government agency. This article is educational only.