Check your tariff refund file before you send it.
Nemotron AI models on Nebius Token Factory
Can't be undone. Once Customs accepts the file, you can't edit it or take shipments back out. Corrections and appeals on those shipments are blocked until Customs finalizes them. Decide what goes in BEFORE you upload.
Not legal or customs advice. Have your licensed customs broker review the list before it is uploaded.
US importers are owed money back for tariffs that were struck down. To get it, they upload one file to Customs, and it can't be undone. One wrong shipment can turn a refund into a bill. This checks the file first.
Sample data: made-up shipments, not real trade data. Not legal advice. We never ask for logins or bank details.
If you paid the struck-down IEEPA tariffs, Customs refunds them through one CSV upload that cannot be edited once accepted. This checks the file first. In the made-up sample of 69 shipments, $467,490.84 is safe to file now, and 15 shipments would have been rejected.
Sample data is synthetic. Figures come from the plain-code rules engine, not from the AI.
does all the money math and sorts every shipment. The AI never makes up a number.
(Nemotron Lightning) cleans up messy data.
(Nemotron Ultra) explains each tricky case.
A spreadsheet can check columns. It cannot read the broker's note that says “protest filed 10/20” on a row whose protest column is blank, or notice that “TIB” and “courtesy notice” are not the same thing as a drawback claim.
We never ask for logins, bank details or tax IDs. Files are checked in memory and never stored. You or your broker do the real upload.
Upload format: a derived schema. It follows CBP's ES-003 report (entry, lines, IEEPA duty) plus ES-701 dates, and adds columns of our own (hts_valid, framework_group, non_ieepa_underpaid_usd, broker_note) that you fill in or leave blank. The file you send to CBP is different: one column, “Entry Number”.
Did Customs change the rules since this was built?
Customs publishes the refund rules on a web page. This reads the live page and compares it with a copy saved on 2026-07-11. Every change is quoted from the page (July on the left, now on the right). No AI is involved.
Does the rules engine put each shipment in the right group? The 69 made-up sample shipments were labelled by hand from Customs' published rules, without reading the engine's code or output, then the engine was scored against those labels. The sample was built to exercise these rules, so this shows the engine follows the rules, not how it does on a real file.
Scoring the sample.
Paste the email or contract. The check runs in your browser with plain code, so the text is not uploaded anywhere, and no AI is involved. It lists what the offer says about fees, logins, who gets the money and lock-in, next to what CBP says to watch for.
CBP's published position: “No. CBP does not charge any fees for processing tariff refunds.” CBP IEEPA Duty Refunds page, FAQ on fees, read 2026-10-30. CBP also warns about third parties in its CAPE Refund Fraud fact sheet.
Nothing checked yet. Paste an offer or pick an example.
Each link was opened and returned HTTP 200 on 2026-10-30. Rule-watch re-checks the CBP FAQ page for changes.
CBP publishes 28 distinct reasons it can reject a CAPE file or entry (its File Validation and Entry Validation tables). 19 are checked from your ACE report, 4 are ruled out by how the upload file is built, and 5 cannot be checked from a report. They are listed so you know what is left to your broker.
Counted from the tables on CBP: IEEPA Duty Refunds (FAQ and error tables); the file table is also in ACE quick reference guide: CAPE Declarations and Error Definitions. One cause, "Entry Summary Not Found or Archived in ACE", sits in both tables and is counted once. CBP also lists items that are not errors, such as direct-deposit (ACH) setup and anti-dumping duties; they are not in the error tables, so they are not counted.