A drawback claim is a state machine with statutory deadlines, and a missed transition ends the run. 19 CFR part 190 sequences the flow, and each state has a defined input, a defined actor and a defined failure mode.
State zero is not the claim
Drawback under 19 U.S.C. 1313(j)(1) starts with imported merchandise on which duty, tax or fee was paid, and 19 CFR 190.31(a) sets the condition that the goods went unused inside the United States before that exportation or destruction. Operations that do not amount to manufacture or production are not use under 19 CFR 190.31(c). A warehouse event stream that logs receipt, storage and outbound movement documents that condition without proving it. Ask the importer to confirm which operations were performed on the goods and record that answer against the SKU.
Export or destruction must land inside the five-year window
19 CFR 190.31(b) allows drawback on imported merchandise if, "before the close of the 5-year period beginning on the date of importation and before the drawback claim is filed," the merchandise is exported from the United States or destroyed under CBP supervision. Your event schema needs the importation date as an immutable field, the export or destruction date, and the claim filing date, because the boundary is measured from importation and the claim must follow the export. 19 CFR 190.42(a) states the failure plainly: "Drawback will be denied on merchandise that is exported or destroyed after the statutory 5-year time period." Record all three dates and compare them before anyone treats a lot as claimable.
The notice of intent is a lead-time event
19 CFR 190.35(a) requires the CBP Form 7553 notice of intent to export, destroy or return the merchandise, filed at the port where examination is intended no later than 5 working days before that exportation date, unless CBP agrees to another filing window or has already waived prior notice. The notice must certify the goods went unused inside the United States before they were exported or destroyed, and 19 CFR 190.35(b) asks for the bill of lading number when it is known, whom to contact, and where the goods are being held. Under 19 CFR 190.35(c) CBP then has 2 working days from receipt to say whether it will examine.
A state machine that models the notice as a checkbox rather than a scheduled event with a five-working-day lead will emit export instructions the notice cannot precede. Store the notice filing date, the port, the intended exportation date and the examination decision as separate fields.
Missing the notice does not automatically end the run. 19 CFR 190.36(a) covers goods shipped out or destroyed without the 19 CFR 190.35(a) notice in place as potentially eligible "subject to the following conditions," and the first of those is a written application to the drawback office with the required information. Model the missed notice as a branch into an application state, not as a terminal state, and let the claimant decide whether to pursue it.
Rejected goods and retail returns carry different documents
Rejected merchandise under 19 U.S.C. 1313(c) covers goods that do not conform to sample or specifications, were shipped without the consent of the consignee, were defective as of the time of importation, or were sold at retail and then returned to, and accepted by, the importer or the party that received them from the importer. 19 CFR 190.41 caps that drawback at 99 percent of the duties paid on the goods that were imported and duty-paid.
19 CFR 190.42(b) requires documentation establishing the nonconformity, the lack of consent or the defect. A claimant who was not the importer must also submit a signed statement from the importer and from each prior owner other than the ultimate purchaser of the goods, confirming no other drawback claim was made, and certify that records support that statement. 19 CFR 190.42(c) requires the same Form 7553 notice, filed at the port of intended redelivery to CBP custody.
Retail returns add their own fields under 19 CFR 190.45(b): the claimant designates an import made within 1 year before that exportation or destruction date, and certifies that one 8-digit HTSUS subheading plus the same product identifier cover both the import being designated and the units coming back. 19 CFR 190.45(c) caps the refund at 99 percent of duties paid.
Your schema therefore needs a claim-type field with different required documents per branch, and a product identifier that resolves to the same value on both sides of the designation.
Who holds the claim right
Under 19 CFR 190.33(a)(1), the exporter or destroyer is entitled to claim drawback for direct identification. That party may waive the right and assign it to the importer or any intermediate party, and where the claimant is neither the exporter nor the destroyer, that party's signed certification has to be obtained and kept, waiving the right and confirming it did not and will not let another party claim that exportation or destruction for drawback. The claimant must file that certification with each claim. Record the certificate holder as an identity field with a validity period, not as a role attached to a team.
Three modeling traps
The 99 percent figure is a cap on the allowable refund relative to duties paid, not a yield. Writing it into a business rule as expected recovery converts a statutory ceiling into a forecast the regulation does not make. Record it as a ceiling and let the claimant compute.
The 1-year designation window in 19 CFR 190.45(b) constrains which entry may be designated for a retail return claim. It does not license accepting returns on any schedule. Confirm the return acceptance facts with the importer and keep return acceptance separate from claim eligibility.
Claim rights sit with named parties under 19 CFR 190.33. Treating the right as available to whichever internal team holds the export file is a data model error. Agree with the importer and the exporter who signs the waiver certification, and record that agreement before any claim state opens.
IMPORTED -> IN_STORAGE -> {EXPORTED | DESTROYED}
require: import_date, duty_paid_amount, no_use_attestation
guard: export_or_destroy_date < import_date + 5 years
guard: claim_filed_after export_or_destroy_date
EXPORTED -> NOTICE_FILED
require: form_7553_date, port, intended_export_date,
contact, location, unused_certification
guard: form_7553_date <= intended_export_date - 5 working days
branch: missing notice -> APPLICATION_STATE (19 CFR 190.36)
NOTICE_FILED -> EXAM_DECISION
require: decision_date, examine_or_waive
guard: decision_date <= form_7553_receipt + 2 working days
EXAM_DECISION -> CLAIM_ASSEMBLED
require: claim_type, product_identifier, htsus_8,
waiver_certificate_holder, signed_statements
branch: rejected goods -> nonconformity evidence + owner statements
branch: retail return -> designated_entry within 1 year + matching id
What a warehouse can honestly export
FulfillNexa by SBT (fulfillnexa.com) can export a dated event stream for the same SKU from inbound receiving through outbound and recovery, which is the class of evidence that has to reconcile against the entry and the claim. The claim and the determination sit with the parties named in 19 CFR 190.33, and we do not sign for them or assert an outcome. Everything we operate sits in China, 24,000 square meters over three cities. The Suzhou floor runs 13,000 square meters of supplier consolidation, Dongguan keeps 8,000 for ecommerce storage and per-order fulfillment, and Shenzhen holds 3,000 for oversized cargo and the sea-air legs in between.
Top comments (0)