Duty Drawback Software 2026 — What Brokers Use

What Drawback Software Actually Does

Five core functions:

1. **Import data ingestion** — pulls Form 7501 data from your customs broker or ACE directly, indexed by entry number, HTS, entered value, and duty paid.

2. **Export data ingestion** — pulls AES export filings, Bills of Lading, and customer-side export confirmations.

3. **Matching engine** — applies substitution rules, manufacturing BOM logic, or direct-identification matching to link imports to exports.

4. **Claim generation** — prepares CBP Form 7551 drawback entries, calculates refund amounts (capped at 99%), and packages supporting documentation.

5. **ACE Drawback filing** — submits claims directly through the ACE Drawback module and tracks claim status through CBP review.

What Brokers Use

The major customs brokerage firms run on a small set of established platforms. The most common platforms for high-volume drawback are CrimsonLogic Drawback, Descartes Customs Compliance, Thomson Reuters OneSource Global Trade Management (specifically the Drawback module), and proprietary in-house systems built by the largest brokerages (Livingston, Expeditors, CH Robinson).

Mid-market and smaller brokerages typically use third-party platforms or hybrid spreadsheet-plus-ACE workflows. The largest enterprises with in-house customs teams sometimes build their own drawback software for tight integration with ERP and TMS systems.

Brokers don't generally publish which software they use, but it matters when you're evaluating broker services — ask whether they're filing through a modern matching engine or running spreadsheets. The matching-engine answer is usually faster and cleaner.

Features That Matter

When evaluating drawback software, the features that move the needle:

**Substitution rule support** — TFTEA-era substitution drawback uses HTSUS-based commercial-interchangeability rules. Software that handles substitution natively saves enormous time.

**Manufacturing drawback BOM linking** — for manufacturers, the ability to link imported components to specific exported finished goods is critical and harder than it sounds.

**ACE Drawback filing integration** — direct submission, not export-then-upload.

**Audit trail and document retention** — drawback claims can be audited up to 5 years after filing. The software should preserve a complete documentation trail.

**Privilege management** — accelerated payment privilege, waiver tracking, and ruling letter management.

**ERP integration** — for enterprises, integrating with SAP, Oracle, or NetSuite for inventory and BOM data eliminates the data-quality issues that derail manual drawback programs.

Software vs Broker Service

Two reasonable models:

**Buy software, run drawback in-house.** Works for enterprises with strong customs and IT teams, ongoing drawback volume above ~$500K/year in recoverable duty, and the appetite to manage broker relationships, CBP communication, and audit response internally. Annual software licensing typically runs $25,000-$150,000+ for enterprise platforms.

**Hire a broker, no software.** Works for any drawback volume from $50K up. The broker provides the software, the expertise, and the CBP relationship. Pricing is typically a percentage of recovery (often 15-30%) or a flat fee per claim. The economics work because you're sharing software cost across the broker's entire client base.

**Hybrid: software you own + broker for filing.** Less common but useful for enterprises that want to control data and ERP integration but don't want to manage CBP communication directly.

For most importers under $250K/year in recoverable duty, broker service is the right answer. Above that, the math starts favoring in-house tooling — but only with the headcount to run it.

Red Flags

Three patterns to avoid when evaluating drawback software or services:

1. **Spreadsheet-only workflows** — vendors who run drawback exclusively in Excel can't handle volume, can't audit trail cleanly, and tend to lose data over the multi-year drawback cycle.

2. **No ACE Drawback filing capability** — drawback claims have been electronic-only since TFTEA implementation. A platform that requires manual filing is decades behind.

3. **No substitution support** — TFTEA-era substitution drawback is one of the highest-recovery categories. Software that doesn't handle substitution leaves money on the table.

When evaluating, ask specifically: Does it file directly through ACE Drawback? Does it handle substitution under TFTEA rules? Does it preserve audit-ready documentation for 5+ years?