CSMS #66789049

US Customs and Border Protection to enforce validations related to e214 submissions

· View this week in context on the trade timeline

System UpdateMedium urgency
Share this messageLinkedInEmail
U.S. Customs and Border Protection (CBP) reminds filers about the items below related to the FIRMS Code, Zone ID, and Port of Entry data submitted to the Automated Commercial Environment (ACE) in Foreign Trade Zone Admission transactions in the Production (PROD) environment. * The FIRMS Code * Cannot be blank and must be on file in CBP system (FIRMS code in FT10 or FZ10 record) * Must be an FTZ Site * Must be in Active status * Must be in the Port of Entry * Must be Bonded. * The bond on the FIRMS Code * Must be bond activity type 4 FTZ * Must be in Active Status * The Zone ID submitted in the FT10 record for all Action e214 FT Admission transactions: * Must be on file as a valid Zone ID identifier in the CBP system * Must match the Zone ID identifier assigned within the CBP system to the FIRMS Code which is declared on the FT10 record The validations are currently available in the Certification (CERT) environment and will be enforced in the Production Environment on December 11, 2025. Please note that these are existing requirements as listed in the ACE FTZ CATAIR located at cbp.gov/trade/automated/catair. *Trade parties who have an ACE Secure Accounts Portal view as an FTZ Operator can verify the Zone ID, FIRMS Code, and Port Code information associated with the FTZ Sites which they operate, by logging into their ACE Portal account. * For technical questions, please contact your assigned CBP Client Representative or your local Port of Entry. For questions about this CSMS please contact CREM@cbp.dhs.gov.
Programs affected
ACE

This week in context

This message came out the week of Nov. 8 to Nov. 14, 2025. See that week against the 90 days before it, with every CSMS message by subject and the trade actions behind them.

Trade timeline preview: the week of Nov. 8 to Nov. 14, 2025 highlighted against the 90 days beforeView this week in context on the trade timeline →