Stable

Duty Drawback and IEEPA Refund Claims: Can Small Importers File Through ACE?

By Stable Software

Small importers can sometimes self-file customs refund requests, but duty drawback and IEEPA refund claims demand data accuracy and strong controls.

Duty Drawback and IEEPA Refund Claims: Can Small Importers File Through ACE?

Small importers often assume that recovering overpaid customs duties should be straightforward once an ACE account is active and ACH is in place. In practice, duty drawback and IEEPA refund claims can be manageable only when entry data, documentation, and filing workflows are tightly controlled from the start.

Why Self-Filing Looks Simple but Usually Is Not

An ACE account and ACH enrollment are important prerequisites for receiving customs-related refunds, but they do not by themselves make the filing process easy. For many importers, the real challenge begins after access is established: identifying eligible entries, validating commercial and customs data, assembling support files, and presenting the claim in a format CBP systems will accept.

The Core Difference Between Access and Execution

Many small importers already operate in ACE for visibility, statements, and broker oversight. That level of access can create the impression that filing a refund claim is simply an extension of ordinary account maintenance. It typically is not. Refund claims require a much higher standard of record linkage, transaction-level accuracy, and internal review than day-to-day portal usage.

With duty drawback filing, an importer generally must prove that imported merchandise was subsequently exported or destroyed under qualifying circumstances. That means import records, inventory movement, export records, bills of lading, commercial invoices, and calculations all need to align. Even minor inconsistencies in quantities, units of measure, dates, product identity, or claimant rights can delay or undermine a filing.

IEEPA refund claims may appear more accessible for smaller importers in situations where the portal supports direct submission without full ABI software. Even then, the burden shifts to the importer to prepare clean source data, confirm entry eligibility, and avoid filing against entries that fall outside the currently supported workflow. In many cases, the technical transmission may be easier than the legal and operational review needed before submission.

Why Error Rates Matter

Self-filing becomes risky when teams assume that rejected claims can simply be corrected later without consequence. Rework consumes staff time, extends recovery timelines, and can trigger additional scrutiny. For a small importer with limited compliance bandwidth, even a modest number of rejected or incomplete submissions can erase much of the expected refund value.

Duty Drawback Filing Requires Strong Traceability

Among customs recovery mechanisms, duty drawback filing remains one of the more documentation-intensive processes. The importer must generally demonstrate a traceable chain from import to qualifying export or destruction, while also ensuring that calculations, claimant status, and timing requirements are met.

What Makes Drawback Operationally Difficult

The complexity of drawback is not just legal; it is deeply operational. A compliant claim often depends on whether the importer can reconstruct product movement across purchasing, receiving, inventory, manufacturing, and shipping systems. If the business lacks lot control, SKU discipline, or a reliable audit trail, drawback preparation quickly becomes burdensome.

Small importers are especially vulnerable when records are split across freight forwarders, customs brokers, ERP systems, spreadsheets, and warehouse providers. What seems like a simple refund opportunity can turn into a manual reconciliation project involving dozens or hundreds of documents. The filing itself is only one stage. The more difficult work is proving that the numbers behind the claim are defensible.

Common Drawback Caveats for Small Importers

A small importer considering self-filing should generally evaluate several practical risks:

  • incomplete import or export documentation
  • inconsistent product descriptions across systems
  • weak inventory traceability
  • calculation errors tied to quantities or values
  • missed internal controls over review and approval
  • limited familiarity with ACE drawback workflows

Even when portal access is available, the process is rarely intuitive for first-time filers. Data often must be entered at multiple levels, and supporting records need to be organized in a way that can withstand examination. For that reason, many importers use specialized drawback software, outside advisors, or customs brokers with drawback expertise rather than relying solely on internal staff.

IEEPA Refund Claims May Be More Accessible, but They Still Demand Precision

For certain refund scenarios, ACE Portal workflows can make IEEPA refund claims more accessible to importers that have an active account and ACH capability. That does not mean the process is casual or self-explanatory. The submission may be simpler than traditional broker-mediated transaction filing, but the eligibility review and data preparation remain significant.

When ACE Portal Filing May Work Without ABI Software

In some filing environments, importers can prepare structured data files and submit declarations directly through ACE Portal rather than purchasing full ABI transmission software. This can lower the technology barrier for small importers, particularly where claims involve a manageable number of entries and relatively straightforward fact patterns.

That said, manual preparation should not be underestimated. The importer still needs to extract entry data, verify that entries qualify, reconcile amounts paid, and ensure that no excluded claim types or entry conditions are included. A claim can be rejected if required fields are missing, if entry-level details are inconsistent, or if the filing includes matters outside the supported refund process.

Important Limitations and Risks

Small importers should generally watch for several caveats when preparing IEEPA refund claims on their own:

  • only certain entries may be eligible in a given filing phase
  • protested entries or special entry types may require different handling
  • offsets may apply where other customs obligations remain unpaid
  • payment timing can vary based on validation and internal review
  • fraudulent outreach and refund scams may target claimants after filing

In other words, the absence of ABI software does not eliminate the need for compliance discipline. It simply changes where the complexity sits. Instead of purchasing a transmission platform, the importer may spend more time on data extraction, spreadsheet preparation, validation review, and exception handling.

Should a Small Importer File Without a Specialist?

The right answer depends on claim volume, internal controls, staff expertise, and the quality of underlying trade data. A small importer with only a few clean, well-documented claims and a strong compliance lead may be able to handle a limited number of IEEPA refund claims internally. Duty drawback, however, generally presents a much steeper learning curve.

A Practical Decision Framework

Self-filing is usually more realistic when the importer has:

  • a well-maintained ACE account
  • ACH enrollment already verified
  • accurate entry data available in exportable format
  • complete commercial and shipping records
  • personnel who understand customs entry logic and reconciliation
  • low claim volume and limited complexity

Using a specialist is usually the better choice when the importer has:

  • mixed or incomplete documentation
  • high entry counts
  • multiple product lines or inventory transformations
  • uncertainty around eligibility
  • no internal drawback or refund workflow
  • limited tolerance for delays, denials, or audits

The Hidden Cost of Doing It Alone

Importers often evaluate self-filing based only on visible third-party fees. That can be misleading. Internal labor, delayed refunds, management time, rejected submissions, and downstream audit exposure all carry real cost. In many cases, specialist support pays for itself by reducing correction cycles and improving claim defensibility.

For small importers, the core question is not whether self-filing is theoretically possible. It is whether the organization can prepare a complete, supportable claim without disrupting daily operations or increasing compliance risk. If the answer is uncertain, outside support is generally the safer path.

Recent Developments
  • CBP CAPE Phase 1 Launch (April 20, 2026): CBP activated the Consolidated Administration and Processing of Entries (CAPE) tool in the ACE Portal for IEEPA refund claims; small importers with ACE accounts and ACH enrollment can self-file CSV declarations listing eligible unliquidated/recently liquidated entries—no ABI software needed, but manual data prep (e.g., ES-003 reports) required; 63% of initial submissions passed validation.
  • IEEPA Refunds Issued (May 12–15, 2026): First ACH refunds via "CBP TREAS 310" hitting accounts (~$35.5B processed across 15M+ entries, including interest at ~5.3–5.4%); small importers report 2-week turnaround post-filing for simple claims, but Phase 1 excludes drawback/entry type 47 or protested entries.
  • Duty Drawback Filing Remains Complex (Ongoing): All drawback claims must be e-filed via ACE Portal (no paper); small importers need import/export docs, precise calculations, and traceability proof—user-unfriendly per practitioner views; software/brokers recommended over self-filing to avoid errors/delays.
  • Caveats for Self-Filing: ACE setup/ACH mandatory (broker can't file IOR's CAPE alone); rejections common (e.g., missing data, protests); offsets against other duties possible; scams targeting claimants rising; drawback requires airtight proof/export docs, risking denial/audits without specialists.
1 2 3 4 5 6

Frequently Asked Questions

Can a Small Importer File Duty Drawback Claims Through ACE Portal?

Generally, yes, drawback claims are handled electronically through ACE. However, portal access alone does not make the process easy. The importer still needs complete import and export documentation, strong traceability, accurate calculations, and a clear understanding of how the claim must be structured.

Can IEEPA Refund Claims Be Filed Without ABI Software?

In some situations, yes. Certain ACE Portal workflows may allow importers to submit IEEPA refund claims without full ABI software, especially where structured entry data can be prepared and uploaded directly. Even so, the importer typically remains responsible for validating eligibility, formatting data correctly, and resolving submission errors.

Is ACH Required to Receive a Customs Refund?

In many cases, ACH enrollment is an important part of efficient refund processing, particularly for importers expecting direct payment into their bank account. Importers should confirm that their account setup, banking details, and portal permissions are current before filing any refund-related submission.

What Is the Biggest Risk of Self-Filing Duty Drawback?

The biggest risk is usually weak documentation and traceability. If the importer cannot clearly connect the import entry to qualifying export or destruction activity, the claim may be delayed, reduced, or denied. Poor calculations and inconsistent product data can create additional exposure.

Are IEEPA Refund Claims Easier Than Duty Drawback Claims?

Typically, yes, at least from a documentation standpoint. Duty drawback often requires more extensive proof of export or destruction and more complex transactional linkage. IEEPA refund claims may be more straightforward for eligible entries, but they still require clean data, careful review, and attention to filing limitations.

Should a Small Importer Use a Broker or Specialist?

For many small importers, yes. A broker or specialist can generally help verify eligibility, prepare support files, avoid common ACE errors, and reduce the risk of delay. This is especially valuable for first-time filers, high-dollar claims, or any drawback filing involving multiple systems and document sources.

How Stable Software Can Help

Stable Software helps importers and customs brokers bring structure to complex customs workflows, including entry visibility, data standardization, document management, and process automation. For teams evaluating duty drawback filing, IEEPA refund claims, or broader customs refund process improvements, better data control usually makes the difference between a smooth recovery effort and a costly manual project.

By centralizing trade records and reducing spreadsheet-driven work, Stable Software can help organizations prepare cleaner submissions, improve audit readiness, and support scalable compliance operations. Learn more about how Stable Software supports modern import operations at stablesoftware.com.

✉️

Sign up for our newsletter

A monthly post on trade, tariffs, and customs — delivered straight to your inbox.