Frequently Asked Questions

Which ERP fields actually matter for a drawback program?

At minimum: part number, quantity, unit of measure, date of receipt or shipment, lot or serial number where one exists, and a link back to the purchase order and the import entry. The gap is rarely the ERP itself. It is that import entry numbers were never written back into it.

Do we need dedicated drawback software?

Not to start. Most programs run on data exported from existing systems into the filer’s platform. Dedicated software earns its place when claim volume, product count, or the number of facilities makes manual reconciliation the bottleneck rather than the data.

Our inventory is commingled and we cannot trace specific units. Is the program dead?

No. That is what the accounting methods in the regulations exist for. CBP allows recognized approaches for identifying which units were exported when physical tracing is impossible, applied consistently and documented. Commingled inventory is normal, not disqualifying.

How far back does the system data need to go?

Five years from the date of importation, which means migration history matters as much as the live system. Companies that changed ERP platforms during that period should confirm what came across and what sits in an archive before scoping a claim.

What breaks most often when a drawback program is automated?

The handoff between systems. Import data sits with the broker, export data sits in shipping or with a forwarder, and inventory sits in the ERP. Automating any one of them does not solve a claim that depends on all three agreeing on the same part number.

Who should own the data work, IT or trade compliance?

Compliance owns what the records have to prove. IT owns getting the fields out of the systems that hold them. Programs stall when one side is asked to do both, because the regulatory requirement and the data extract are genuinely different problems.