AIFBA
Menu icoMenu232Dark icoCross32Dark
<
>
  • Meet the Board
  • Mission Objectives
  • AIFBA eStore
  • News and Updates

Add a logo, a button or social media links

Edit
  • AIFBA
  • Home ▴▾
  • About ▴▾
    • Meet the Board
    • Mission Objectives
    • AIFBA eStore
    • News and Updates
  • Community ▴▾
    • Events and Membership
    • Committees
    • Job Listings
  • Contact ▴▾
  • Log in
  • Meet the Board
  • Mission Objectives
  • AIFBA eStore
  • News and Updates
  • Events and Membership
  • Committees
  • Job Listings
Meet the Board Mission Objectives AIFBA eStore News and Updates
Back
CSMS # 59875134 FIRMS Validations

CSMS # 59875134 FIRMS Validations

As noted in CSMS# 59651310, on March 2, 2024, the U.S. Customs and Border Protection (CBP) deployed to the Automated Commercial Environment (ACE) Certification (CERT) Environment an update that requires the Facilities Information and Resource Management System (FIRMS) code when arriving an in-bond for Non-Air.

The following implementation guides have been updated to emphasize that the FIRMS field is mandatory when reporting the arrival for all In-Bonds:

In-Bond | U.S. Customs and Border Protection (cbp.gov)

CATAIR In-bond arrival via WP application – FIRMS Location on In-Bond Arrival - Positions 48-51. For Action Code of ‘1’, ‘2’, or ‘3,’ the FIRMS Code must be reported. Please note this is not required for an Air in-bond arrival.

ACE Rail 353 | U.S. Customs and Border Protection (cbp.gov)

Rail X12 – 353, “Events Advisory Details Transaction Set,” for M1501 message codes of ‘1’, ‘2’, or ‘3’, the FIRMS Code must be reported in the M1517.

ACE Ocean Manifest 353 Events Advisory Details Transaction Set | U.S. Customs and Border Protection (cbp.gov)

Ocean X12 – 353, “Events Advisory Details Transaction Set,” for M1501 message codes of ‘1’, ‘2’, or ‘3,’ the FIRMS Code must be reported in the M1517.

ACE Ocean CAMIR In-Bond Vessel Departure Arrival Message | U.S. Customs and Border Protection (cbp.gov)

Ocean “In-Bond Vessel Departure Arrival Message” HI Application – H01 - Positions 76-79, reporting the FIRMS Code for Message Code of ‘1’, ‘2’, or ‘3,’is required.

ACE Truck Manifest ANSI X12 353 Message | U.S. Customs and Border Protection (cbp.gov)

Truck ANSI X12 -353, “Events Advisory Details Transaction Set,” for M1501 message codes of ‘1’, ‘2’, or ‘3,’ the FIRMS Code must be reported in data element M1517.

Standard Truck Manifest CUSREP Conveyance Report Message | U.S. Customs and Border Protection (cbp.gov)

Truck UN/Edifact – “CUSREP Conveyance Report” - BGM – Data Element 1225 - Message Function Code “64.” Reporting an in-bond arrival must also transmit the LOC record reporting the FIRMS Code of the facility at the port/point of in-bond destination, where the shipment is kept prior to entry/export in data element C519.

ACE FTZ CATAIR | U.S. Customs and Border Protection (cbp.gov)

DRAFT FTZ CATAIR v3.1.1 was created to reflect these FIRMS code changes Foreign Trade Zone (v3.1.1) - Draft FIRMS Code.

To clarify the previous CSMS# 59651310 message regarding to the Foreign Trade Zone (FTZ) update, a new condition was added indicating when a FIRMS code is mandatory for reporting of FTZ Physical Arrival of Goods - FZ Application - FZ10 – record in which the Action Qualifier field is '3' and the Action Code field is 'I'. The FIRMS Code must be reported in positions 65-68. Please note this update is not required for an Air In-Bond Arrival.

The changes related to this FIRMS code update will be deployed sooner than the updates to FTZ related to Ocean House bill, noted in the FTZ CATAIR v3.6 DRAFT Ocean House Bill. Therefore, FTZ CATAIR v3.1.1 DRAFT FIRMS Code was created to reflect these FIRMS code changes only. Both draft versions of the FTZ CATAIR are posted on the ‘DRAFT CHAPTERS: FUTURE CAPABILITIES’ section.

In addition, the Trade Manifest In-Bond UI has been updated to require the FIRMS code when arriving an in-bond. In the future, users will not be able to arrive an in-bond without entering a valid FIRMS code.

Please reach out to your Client Representative if you have any technical-related questions. For Policy/Operational questions about this requirement, please email cscwarehousing@cbp.dhs.gov.

For any questions about this CSMS, please email CREM@cbp.dhs.gov.

Related Message: CSMS # 59651310

icoFacebook35Color icoTwitter35Color icoLinkedin35Color
icoFacebook35Color icoTwitter35Color icoLinkedin35Color
See also
CSMS # 60199688 - Submitting Large Documents via Email to the DIS

CSMS # 60199688 - Submitting Large Documents via Email to the DIS

When submitting documents to the Document Image System (DIS), do not send individual emails with...

April 29, 2024
Broker Cybersecurity Incident Procedures

Broker Cybersecurity Incident Procedures

This guidance explains the process and roles and responsibilities of U.S. Customs and Border...

March 19, 2024
Atlanta Cargo Email Address Update

Atlanta Cargo Email Address Update

Effective, Monday January 22, 2024, the CARGO ATL email box will be disabled. The new Atlanta...

January 19, 2024
CPSC eFiling Newsletter – December 2023 Edition

CPSC eFiling Newsletter – December 2023 Edition

CPSC is committed to the continuous improvement of our importation process so that we may help...

December 26, 2023
2024 Customs Broker Triennial Status Report

2024 Customs Broker Triennial Status Report

Customs and Border Protection (CBP) said “Save Time, Submit Online,” when it announced that the...

December 20, 2023
Meet our new CBP Personnel!

Meet our new CBP Personnel!

Welcome Cargo Supervisor Hobson and Chief Vaughn – both new to Atlanta!

December 15, 2023
icoFacebook24Color icoTwitter24Color icoLinkedin24Color
  • Site map
  • Licenses
  • Legal notice
  • T&C
  • Configure cookies
  • Log in
  • Powered by Springly, created with 💙 for organizations everywhere