ICEGATE error 700 "Error-Refile": what it means and what to do
The short answer
700 is ICEGATE's catch-all refusal: no field, no reason. All six 700s on record were accepted the same day when sent again. So check the signed CSN JSON free at scmtr.io/check, fix anything it flags, and send it again; it can keep its control number. If the same 700 comes back, stop re-sending and ask the ICEGATE helpdesk, quoting the uniqueId.
The full answer
700 Error-Refile is ICEGATE's catch-all refusal. It names no field and gives no reason, and it is not in the MIG's own table of 452 codes, which is why looking it up finds nothing.
What happened next, every time. Six 700s are on record, from 20 August to 30 September 2026, at five ports, on imports and exports alike. Every one of those bills was accepted the same day when it was sent again, between 8 minutes and about 6 hours after the refusal. ICEGATE's engineers told the trade on 12 September 2026 that a 700 on a large file can be the system refusing it under load at a busy time, with the same file going through later.
What to do
- Check the file you sent. Drop the signed CSN JSON on scmtr.io/check, free and with no sign-in, and fix anything it flags. Then rule out these four, cheapest first (nobody outside customs knows which one usually causes a
700):
- The arithmetic: packages on the items, the house bills and the master; container weights against the gross weight; the equipment and line totals.
- A duplicate: whether an earlier send of this filing was accepted or is still waiting for its answer.
- The consolidation shape: the consolidated indicator against the house bills actually in the file, and the consolidator PAN with its
PAN:prefix. - The voyage: the VCN customs issued for that ship's call (not the carrier's voyage number from the B/L), and the IMO number.
- Send it again, the same day. A refusal does not use the control number up, so it can go under its original number, unless an earlier send of that number was accepted or is still waiting for an answer.
- Same
700again? Stop re-sending it unchanged. Ask the ICEGATE helpdesk, quoting the tracking id (uniqueId) from the acknowledgement.
Where this comes from
The SCMTR reference pages this answer rests on — free to read, no sign-in.
- Why customs rejects a filingRejection codes by family, what each one is really complaining about, and what to change to clear it.
- Which error list does my code come from?ICEGATE fronts several customs systems and each answers from its own list. Which list your error code came from, and where to look it up.
- ICEGATE error codesAll 452 business-validation codes in ICEGATE’s own wording, grouped by what to change, with how to read an acknowledgement file.
- One consignment, several transmissionsA refused filing sent again is a new transmission with a reply of its own — so one corrected shipment can leave you holding several.
- Reading an acknowledgement from customsYou filed and a JSON file came back. Which of the three files you have, what the verdict means, and why some refusals carry no code at all.
Was this helpful?
This answer is provided to the best of our knowledge based on our SCMTR reference materials and is for general informational purposes only. It is not legal or customs-compliance advice, may not reflect the most current ICEGATE/CBIC requirements, and creates no obligation on our part. Always verify against the official ICEGATE/CBIC sources or consult a licensed customs broker before filing.
Someone in your group asking the same?
Send them this answer — it opens with the short version and the sources.
From SCMTR.io
SCMTR filing, checked before ICEGATE sees it
CSN, SAM / SDM and export SCX for forwarders, consol agents and shipping lines — every check before you sign.
- Check your SCMTR JSONFree, no sign-in — what customs would reject, and the fix.
- Track a B/LFree, no login — the SAM status straight from ICEGATE.