Importer Security Filing and Additional Carrier Requirements

Federal RegisterNov 25, 2008

Ask Donna

What actually matters in this document.

Text

DEPARTMENT OF HOMELAND SECURITY

Bureau of Customs and Border Protection

19 CFR Parts 4, 12, 18, 101, 103, 113, 122, 123, 141, 143, 149, 178, and 192

[Docket Number USCBP-2007-0077; CBP Dec. 08-46]

RIN 1651-AA70

Importer Security Filing and Additional Carrier Requirements

AGENCY:

Customs and Border Protection, Department of Homeland Security.

ACTION:

Interim final rule, solicitation of comments.

SUMMARY:

To help prevent terrorist weapons from being transported to the United States, vessel carriers bringing cargo to the United States are required to transmit certain information to Customs and Border Protection (CBP) about the cargo they are transporting prior to lading that cargo at foreign ports of entry. This interim final rule requires both importers and carriers to submit additional information pertaining to cargo to CBP before the cargo is brought into the United States by vessel. This information must be submitted to CBP by way of a CBP-approved electronic data interchange system. The required information is reasonably necessary to improve CBP's ability to identify high-risk shipments so as to prevent smuggling and ensure cargo safety and security. These regulations specifically fulfill the requirements of section 203 of the Security and Accountability for Every (SAFE) Port Act of 2006 and section 343(a) of the Trade Act of 2002, as amended by the Maritime Transportation Security Act of 2002.

DATES:

Effective Date:

This rule is effective on January 26, 2009.

Compliance Dates:

The compliance dates for these regulations are set forth in § 4.7c(d), 4.7d(f), and 149.2(g).

Comment Date:

As provided in the “Public Participation” section of this document, comments are requested on certain aspects of the rule. Comments must be received on or before June 1, 2009.

ADDRESSES:

You may submit comments, identified by

docket number

, by

one

of the following methods:

•

Federal eRulemaking Portal: http://www.regulations.gov

. Follow the instructions for submitting comments via docket number USCBP-2007-0077.

•

Mail:

Border Security Regulations Branch, Office of International Trade, U.S. Customs and Border Protection, 799 9th Street, NW., Washington, DC 20001.

Instructions:

All submissions received must include the agency name and document number for this rulemaking. All comments received will be posted without change to

http://www.regulations.gov

, including any personal information provided. For detailed instructions on submitting comments and additional information on the rulemaking process, see the “Public Participation” heading of the

SUPPLEMENTARY INFORMATION

section of this document.

Docket:

For access to the docket to read background documents or comments received, go to

http://www.regulations.gov

. Submitted comments may also be inspected on regular business days between the hours of 9 a.m. and 4:30 p.m. at the Office of International Trade, Customs and Border Protection, 799 9th Street, NW., 5th Floor, Washington, DC. Arrangements to inspect submitted comments should be made in advance by calling Mr. Joseph Clark at (202) 325-0118.

FOR FURTHER INFORMATION CONTACT:

Richard Di Nucci, Office of Field Operations, (202) 344-2513.

SUPPLEMENTARY INFORMATION:

Table of Contents

I. Public Participation

II. Background

III. Carrier and Importer Requirements

A. Existing Requirements

B. New Carrier Requirements Under This Interim Final Rule

1. Vessel Stow Plans

2. Container Status Messages

C. New Importer Requirements Under This Interim Final Rule

D. Structured Review and Flexible Enforcement Period

E. Summary of Changes From NPRM

IV. Discussion of Comments Regarding This Rulemaking Generally

V. Discussion of Comments Regarding Proposed Carrier Requirements Relating to Vessel Cargo Destined to the United States

A. Overview; Vessel Stow Plan

B. Public Comments; Vessel Stow Plan

C. Overview; Container Status Messages

D. Public Comments; Container Status Messages

E. Public Comments; Carrier Requirements Generally

VI. Discussion of Comments Regarding Proposed Importer Requirements for Vessel Cargo Destined to the United States

A. Overview; Proposed Importer Requirements

1. Shipments Other Than FROB, IE Shipments, and T&E Shipments

2. FROB, IE Shipments, and T&E Shipments

B. Public Comments; Responsible Party

C. Public Comments; Agents

D. Public Comments; Customs Business

E. Public Comments; Bills of Lading

F. Public Comments; Required Elements

G. Public Comments; Technical Issues

H. Public Comments; Update and Withdrawal of Importer Security Filing

I. Public Comments; In-Bond Shipments

J. Public Comments; Importer Security Filing, Entry, and Application for FTZ Admission

K. Public Comments; Requests for Special Treatment

L. Public Comments; Importer Security Filing, Other Comments

VII. Discussion of Comments Regarding Proposed Amendments to Bond Requirements and Enforcement

A. Overview; Bond Conditions and Enforcement Related to the Proposed Importer Security Filing, Vessel Stow Plan, and Container Status Message Requirements

B. Public Comments; Bond Conditions and Enforcement Related to the Proposed Importer Security Filing, Vessel Stow Plan, and Container Status Message Requirements

C. Overview; Bond Conditions Related to the Trade Act Regulations

D. Public Comments; Bond Conditions Related to the Trade Act Regulations

VIII. Discussion of Comments Regarding the Cost, Benefit, and Feasibility Study

IX. Adoption of Proposal

X. Regulatory Analyses

A. Executive Order 12866

B. Regulatory Flexibility Act

C. Unfunded Mandates Reform Act

D. Paperwork Reduction Act

XI. Signing Authority

XII. Coordination of Interim Final Rule With Congress

XIII. Regulatory Amendments

Abbreviations and Terms Used in This Document

AAEI—American Association of Exporters and Importers

AAPA—American Association of Port Authorities

ABI—Automated Broker Interface

ACE—Automated Commercial Environment

AES—Automated Export System

AMS—Automated Manifest System

ANSI—American National Standards Institute

ATDI—Advance Trade Data Initiative

ATS—Automated Targeting System

BAPLIE—Bayplan/stowage plan occupied and empty locations message

CAMIR—Customs Automated Manifest Interface Requirements

CATAIR—Customs and Trade Automated Interface Requirements

CBP—Customs and Border Protection

CFR—Code of Federal Regulations

COAC—Departmental Advisory Committee on Commercial Operations of Customs and Border Protection and Related Homeland Security Functions

CSI—Container Security Initiative

CSM—Container status message

C-TPAT—Customs-Trade Partnership Against Terrorism

DDP—Delivered duty paid

DHS—U.S. Department of Homeland Security

DNL—Do not load

DUNS—Data Universal Numbering System

EIN—Employer identification number

FAQ—Frequently asked questions

FDA—U.S. Food and Drug Administration

FIRMS—Facilities Information and Resources Management System

FROB—Foreign cargo remaining on board

FTZ—Foreign trade zone

FR—Federal Register

GLN—Global Location Number

HTSUS—Harmonized Tariff Schedule of the United States

ICPA—International Compliance Professionals Association

IE—Immediate exportation

IIT—Instrument of international trade

IMO—International Maritime Organization

IRS—Internal Revenue Service

IT—Immediate transportation

ISF—Importer Security Filing

JIG—Joint Industry Group

LCL—Less than Container Load

MID—Manufacturer identification

MTSA—Maritime Transportation Security Act of 2002

NAM—National Association of Manufacturers

NCBFAA—National Customs Brokers and Forwarders Association of America

NII—Non-Intrusive Inspection

NPRM—Notice of Proposed Rule Making

NVOCC—Non-vessel operating common carrier

OCS—Outer Continental Shelf

OPA—Outward Processing Arrangement

OMB—Office of Management and Budget

PDF—Portable Document Format

PGA—Participating Government Agency

Pub. L.—Public Law

RILA—Retail Industry Leaders Association

RFA—Regulatory Flexibility Act of 1980

SAFE Port Act—Security and Accountability for Every Port Act of 2006

SBREFA—Small Business Regulatory Enforcement Fairness Act of 1996

sFTP—Secure File Transfer Protocol

SSN—Social Security Number

T&E—Transportation and exportation

TIB—Temporary Importation Bond

TSC—Technology Support Center

TSN—Trade Support Network

UMRA—Unfunded Mandates Reform Act of 1995

UN EDIFACT—United Nations rules for Electronic Data Interchange For Administration, Commerce and Transport

U.S.C.—United States Code

VIN—Vehicle Identification Number

VOCC—Vessel Operating Common Carrier

WHTI—Western Hemisphere Travel Initiative

WSC—World Shipping Council

I. Public Participation

Interested persons are invited to submit written comments on only the six data elements for which CBP is providing some type of flexibility (container stuffing location, consolidator (stuffer), manufacturer (or supplier), ship to party, country of origin, and commodity HTSUS number) and the requirements related to those elements discussed in section 149.2(b) and (f). CBP also invites comments on the revised Regulatory Assessment and Final Regulatory Flexibility Analysis, including compliance costs for various industry segments, the impact of the flexibilities provided in this rule, and the barriers to submitting Importer Security Filing data 24 hours prior to lading. We urge commenters to reference a specific portion of the rule, explain the reason for any recommended change, and include data, information, or authorities that support such recommended change.

II. Background

Section 203 of the Security and Accountability for Every Port Act of 2006 (Pub. L. 109-347, 120 Stat. 1884 (SAFE Port Act)) provides that the Secretary of Homeland Security (Secretary), acting through the Commissioner of CBP, shall promulgate regulations to “require the electronic transmission to the Department [of Homeland Security] of additional data elements for improved high-risk targeting, including appropriate security elements of entry data, as determined by the Secretary, to be provided as advanced information with respect to cargo destined for importation into the United States prior to loading of such cargo on vessels at foreign seaports.” Pursuant to this Act, and section 343(a) of the Trade Act of 2002 (19 U.S.C. 2071 note), CBP published a Notice of Proposed Rule Making (NPRM) in the

Federal Register

(73 FR 90) on January 2, 2008, proposing to require importers and carriers to submit additional information pertaining to cargo before the cargo is brought into the United States by vessel.

CBP has provided an overview of existing advance cargo information requirements and entry requirements below. For a detailed discussion of the advance cargo information requirements prior to this interim final rule, the statutory and regulatory histories, and the statutory factors governing development of these regulations, please see the NPRM published at 73 FR 90.

The proposed rule was known to the trade as both the “Importer Security Filing proposal” and the “10 + 2 proposal.” The name “10 + 2” is shorthand for the number of advance data elements CBP was proposing to collect. Carriers would be generally required to submit two additional data elements—a vessel stow plan and container status messages regarding certain events relating to containers loaded on vessels destined to the United States—to the elements they are already required to electronically transmit in advance (the “2” of “10+2”); and importers,

1

as defined in the proposed regulations, would be required to submit 10 data elements—an Importer Security Filing containing 10 data elements (the “10” of “10+2”).

1

For purposes of the proposed regulations, importer means the party causing goods to arrive within the limits of a port in the United States. For foreign cargo remaining on board (FROB), the importer was proposed to be construed as the carrier. For immediate exportation (IE) and transportation and exportation (T&E) in-bond shipments, and goods to be delivered to a foreign trade zone (FTZ), the importer was proposed to be construed as the party filing the IE, T&E, or FTZ documentation with CBP.

CBP extended the initial 60-day comment period by 15 days, from March 3, 2008 to March 18, 2008.

See

73 FR 6061 (Feb. 1, 2008). Approximately 200 commenters responded in a timely manner to the NPRM. As certain comments pertained to the proposed carrier requirements and others pertained to the proposed importer requirements, this interim final rule addresses separately the issues presented in the comments regarding the proposed carrier requirements and the proposed importer requirements.

III. Carrier and Importer Requirements

A. Existing Requirements

Carriers are currently required to submit advance cargo information for vessels, including a vessel's Cargo Declaration, to CBP no later than 24 hours before the cargo is laden aboard a vessel at a foreign port.

See

19 CFR 4.7 and 4.7a. This is generally referred to as the “24 Hour Rule.” This information must be submitted to CBP via the Vessel Automated Manifest System (AMS). Carriers are currently not required to submit vessel stow plans or container status messages to CBP. In addition, importers of record are generally required to file entry information, including CBP Form 3461, with CBP within fifteen calendar days of the date of arrival of a shipment at a United States port of entry and entry summary information, including CBP Form 7501, within 10 working days of the entry of the merchandise. Entry and entry summary information is submitted to CBP via the Automated Broker Interface (ABI) or via paper forms. Importers are not currently required to submit advance cargo information to CBP.

B. New Carrier Requirements Under This Interim Final Rule

1. Vessel Stow Plan

In addition to the existing carrier requirements pursuant to the 24 Hour Rule, this interim final rule requires

carriers to submit a vessel stow plan for vessels destined to the United States. Carriers must transmit the stow plan for vessels transporting containers so that CBP receives the stow plan no later than 48 hours after the carrier's departure from the last foreign port. For voyages less than 48 hours in duration, CBP must receive the stow plan prior to the vessel's arrival at the first port in the United States. Bulk and break bulk carriers are exempt from this requirement for vessels exclusively carrying bulk and break bulk cargo. Carriers must submit the vessel stow plan via the CBP-approved electronic data interchange system, which currently includes AMS, secure file transfer protocol (sFTP), or e-mail. If CBP approves of different or additional electronic data interchange systems, CBP will publish a notice in the

Federal Register

.

The vessel stow plan must include standard information relating to the vessel and each container laden on the vessel, including the following standard information:

With regard to the vessel,

(1) Vessel name (including international maritime organization (IMO) number);

(2) Vessel operator; and

(3) Voyage number.

With regard to each container,

(1) Container operator;

(2) Equipment number;

(3) Equipment size and type;

(4) Stow position;

(5) Hazmat code (if applicable);

(6) Port of lading; and

(7) Port of discharge.

2. Container Status Messages

In addition to the existing carrier requirements pursuant to the 24 Hour Rule, this interim final rule also requires carriers to submit container status messages (CSMs)

2

to CBP daily for certain events relating to all containers laden with cargo destined to arrive within the limits of a port in the United States by vessel. CSMs created under either the American National Standards Institute (ANSI) X.12 standard or the United Nations rules for Electronic Data Interchange For Administration, Commerce and Transport (UN EDIFACT) standard are acceptable.

2

CSMs are used to report terminal container movements (

e.g.

, loading and discharging the vessel) and to report the change in status of containers (

e.g.

, empty or full).

Carriers must submit a CSM when any of the required events occurs if the carrier creates or collects a CSM in its equipment tracking system reporting that event. Carriers are not required to create or collect any CSM data other than those which the carrier already creates or collects on its own and maintains in its electronic equipment tracking system. Carriers must submit CSMs no later than 24 hours after the message is entered into the carrier's equipment tracking system.

The events for which CSMs are required are:

(1) When the booking relating to a container which is destined to arrive within the limits of a port in the United States by vessel is confirmed;

(2) When a container destined to arrive within the limits of a port in the United States by vessel undergoes a terminal gate inspection;

(3) When a container, which is destined to arrive within the limits of a port in the United States by vessel, arrives or departs a facility (These events take place when a container enters or exits a port, container yard, or other facility. Generally, these CSMs are referred to as “gate-in” and “gate-out” messages.);

(4) When a container, which is destined to arrive within the limits of a port in the United States by vessel, is loaded on or unloaded from a conveyance (This includes vessel, feeder vessel, barge, rail and truck movements. Generally, these CSMs are referred to as “loaded on” and “unloaded from” messages.);

(5) When a vessel transporting a container, which is destined to arrive within the limits of a port in the United States by vessel, departs from or arrives at a port (These events are commonly referred to as “vessel departure” and “vessel arrival” notices.);

(6) When a container which is destined to arrive within the limits of a port in the United States by vessel undergoes an intra-terminal movement;

(7) When a container which is destined to arrive within the limits of a port in the United States by vessel is ordered stuffed or stripped;

(8) When a container which is destined to arrive within the limits of a port in the United States by vessel is confirmed stuffed or stripped; and

(9) When a container which is destined to arrive within the limits of a port in the United States by vessel is shopped for heavy repair.

3

3

A container is shopped for heavy repair when it is delivered to a facility for the purpose of being repaired.

CBP is aware that it might be cost beneficial for some carriers to transmit all CSMs, rather than filter out CSMs relating to containers destined to the United States or relating only to the required events. Therefore, carriers may transmit their “global” CSM messages, including CSMs relating to containers that do not contain cargo destined for importation into the United States and CSMs relating to events other than the required events. By transmitting CSMs in addition to those required by this interim final rule, a carrier authorizes CBP to access and use those data.

For each CSM submitted to CBP by the carrier, the following information must be included:

(1) Event code being reported, as defined in the ANSI X.12 or UN EDIFACT standards;

(2) Container number;

(3) Date and time of the event being reported;

(4) Status of the container (empty or full);

(5) Location where the event took place; and

(6) Vessel identification associated with the message if the container is associated with a specific vessel.

Carriers are exempt from the CSM requirement for bulk and break bulk cargo. Carriers must submit CSMs via the CBP-approved electronic data interchange system. The current electronic data interchange system for CSMs approved by CBP is sFTP. If CBP approves of a different or additional electronic data interchange system, CBP will publish a notice in the

Federal Register

.

The following chart illustrates the existing carrier data requirements pursuant to the 24 Hour Rule and the new carrier data requirements required pursuant to this interim final rule.

Existing Carrier Requirements Versus New Carrier Requirements

Existing requirements

New requirements

Requirement

Advance Cargo Information (

i.e.,

Trade Act Requirements or 24 Hour Rule)

Stow Plan

Container Status Messages

Timing

24 hours prior to lading

48 hours after departure; prior to arrival for voyages less than 48 hrs

24 hours after the message is entered into the carrier's equipment tracking system

Submission Method

vessel AMS

vessel AMS, sFTP, or email

sFTP

Elements

—Bill of Lading Number

—Foreign Port before vessel departs for U.S.

—Carrier SCAC [Standard Carrier Alpha Code]

—Carrier Assigned Voyage Number

—Date of Arrival at First U.S. Port

—Quantity

—Unit of measure of Quantity

—First Foreign Place of Receipt

—Commodity Description (or six-digit HTSUS Number)

—Commodity Weight

—Shipper Name and Address

With regard to the vessel,

—Vessel name (including international maritime organization (IMO) number);

—Vessel operator; and

—Voyage number

With regard to each container,

—Container operator;

—Equipment number;

—Equipment size and type;

—Stow position;

—Hazmat code (if applicable);

—Port of lading; and

—Port of discharge.

—Event code being reported, as defined in the ANSI X.12 or UN EDIFACT standards;

—Container number;

—Date and time of the event being reported;

—Status of the container (empty or full);

—Location where the event took place; and

—Vessel identification associated with the message if the container is associated with a specific vessel.

—Consignee Name and Address or ID Number

—Vessel Name

—Vessel Country

—Vessel Number

—Foreign Port of Lading

—Hazmat Code

—Container numbers

—Seal Numbers

—Date of Departure from Foreign Port

—Time of Departure from Foreign Port

C. New Importer Requirements Under This Interim Final Rule

This interim final rule requires Importer Security Filing (ISF) Importers, as defined in these regulations, or their agents, to transmit an Importer Security Filing to CBP, for cargo other than foreign cargo remaining on board (FROB), no later than 24 hours before cargo is laden aboard a vessel destined to the United States. See the “Structured Review and Flexible Enforcement Period” section of this document for flexibilities related to timing for certain Importer Security Filing elements. Because FROB is frequently laden based on a last-minute decision by the carrier, the Importer Security Filing for FROB is required any time prior to lading. An Importer Security Filing is required for each shipment, at the lowest bill of lading level (i.e., at the house bill of lading level, if applicable). The party required to submit the Importer Security Filing is the party causing the goods to enter the limits of a port in the United States. This party is the carrier for FROB and the party filing for the immediate exportation (IE), transportation and exportation (T&E), or foreign trade zone (FTZ) documentation for those types of shipments. The ISF Importer, as a business decision, may designate an authorized agent to file the Importer Security Filing on the ISF Importer's behalf. A party can act as an authorized agent for purposes of filing the Importer Security Filing if that party obtains access to ABI or AMS.

ISF Importers, or their agents, must transmit the Importer Security Filing via a CBP-approved electronic data interchange system. The current approved electronic data interchange systems for the Importer Security Filing is ABI and vessel AMS. If CBP approves a different or additional electronic data interchange system in the future, CBP will publish a notice in the

Federal Register

.

The party who filed the Importer Security Filing must update the Importer Security Filing if, after the filing and before the goods arrive within the limits of a port in the United States, there are changes to the information filed or more accurate information becomes available.

ISF Importers, or their agents, must submit 10 elements to CBP for shipments consisting of goods intended to be entered into the United States and goods intended to be delivered to an FTZ. ISF Importers, or their agents, must submit five elements to CBP for shipments consisting entirely of FROB and shipments consisting entirely of goods intended to be “transported” as IE or T&E in-bond shipments.

For shipments other than those consisting entirely of FROB and goods intended to be “transported” in-bond as an IE or T&E, the Importer Security Filing must consist of 10 elements, unless an element is specifically exempted. The manufacturer (or supplier), country of origin, and commodity Harmonized Tariff Schedule of the United States (HTSUS) number must be linked to one another at the line item level. The 10 elements are as follows: (1) Seller; (2) Buyer; (3) Importer of record number/Foreign trade zone applicant identification number; (4) Consignee number(s); (5) Manufacturer (or supplier); (6) Ship to party; (7) Country of origin; (8) Commodity HTSUS number; (9) Container stuffing location; and (10) Consolidator (stuffer).

For shipments consisting entirely of FROB and shipments consisting entirely of goods intended to be “transported” in-bond as an IE or T&E, the Importer Security Filing must consist of five elements, unless an element is specifically exempted. The five elements are as follows: (1) Booking party; (2) Foreign port of unlading; (3) Place of delivery; (4) Ship to party; and (5) Commodity HTSUS number.

Four of the Importer Security Filing elements are identical to elements submitted for entry (CBP Form 3461) and entry summary (CBP Form 7501) purposes. These elements are the importer of record number, consignee number, country of origin, and

commodity HTSUS number when provided at the 10-digit level. An importer may submit these elements once to be used for both Importer Security Filing and entry/entry summary purposes. If an importer chooses to have these elements used for entry/entry summary purposes, the Importer Security Filing and entry/entry summary must be self-filed by the importer or filed by a licensed customs broker in a single transmission to CBP no later than 24 hours prior to lading. In addition, the HTSUS number must be provided at the 10-digit level.

Two of the Importer Security Filing elements are identical to elements submitted for application to admit goods to an FTZ (CBP Form 214). These elements are the country of origin and commodity HTSUS number when provided at the 10-digit level. The filer may submit the Importer Security Filing and CBP Form 214 in the same electronic transmission to CBP and may submit the country of origin and commodity HTSUS number once to be used for both Importer Security Filing and FTZ admission purposes. If the party submitting the Importer Security Filing chooses to have this element used for FTZ admission purposes, the HTSUS number must be provided at the 10-digit level.

The following chart illustrates the existing importer data requirements for entry and entry summary purposes and the new importer data requirements pursuant to this interim final rule.

Existing Importer Requirements Versus New Importer Requirements

Existing Requirements

New Requirements

Requirement

Entry and Entry Summary

4

Importer Security Filing

Timing

Entry within 15 calendar days of date of arrival; Entry summary within 10 working days of entry

24 hours prior to lading for 8 of the elements; as early as possible, in no event later than 24 hours prior to arrival, for 2 of the elements

Submission Method

ABI or paper

ABI or vessel AMS

Elements

—Bill of Lading Number

—Importer of Record Number *

Shipments Other Than FROB, IE Shipments and T&E Shipments:

—Seller

—Foreign Port before vessel departs for U.S.

—Buyer

—Carrier SCAC

—Importer of record number/FTZ applicant identification number *

—Carrier Assigned Voyage Number

—Consignee number(s) *

—Date of Arrival at First U.S. Port

—Manufacturer (or supplier)

—Quantity

—Ship to party

—Unit of measure of Quantity

—Country of origin *

—First Foreign Place of Receipt

—Commodity HTSUS number *

—Commodity Description

—Container stuffing location

—Commodity HTSUS Number *

—Consolidator (stuffer)

—Commodity Weight

—Shipper Name and Address

—Consignee Name and Address and Number *

FROB, IE Shipments and T&E Shipments:

—Country of Origin *

—Booking party

—Vessel Name

—Foreign port of unlading

—Vessel Country

—Place of delivery

—Vessel Number

—Ship to party

—Foreign Port of Lading

—Commodity HTSUS number

—Hazmat Code

—Container numbers

—Seal Numbers

—Date of Departure from Foreign Port

—Time of Departure from Foreign Port

* These elements are provided for Importer Security Filing and entry/entry summary or FTZ admission purposes.

D. Structured Review and Flexible Enforcement Period

In order

to provide the trade sufficient time to adjust to the new requirements and in consideration of the business process changes that may be necessary to achieve full compliance, CBP will show restraint in enforcing the rule, taking into account difficulties that importers may face in complying with the rule, so long as importers are making satisfactory progress toward compliance and are making a good faith effort to comply with the rule to the extent of their current ability. This policy will last for twelve months after the effective date and will apply to all aspects of the filing rule.

4

Importers are not currently required to submit any information to CBP prior to foreign lading for targeting purposes.

In addition, this rule provides flexibility with respect to certain elements of the Importer Security Filings. This flexibility falls into two categories:

• Two elements of the Importer Security Filings will be subject to flexibility as to timing. These elements are the Container stuffing location and Consolidator (stuffer). The ISF Importer must submit these elements as early as possible, and in any event no later than 24 hours prior to arrival in a U.S. port (or upon lading at the foreign port if that is later than 24 hours prior to arrival in a U.S. port).

• Four elements will be subject to flexibility as to interpretation. These elements are the Manufacturer (or supplier), Ship to party, Country of origin, and Commodity HTSUS number. There is no special timing flexibility for these elements; they must be filed 24 hours prior to lading. However, CBP has added flexibility by allowing ISF Importers, in their initial filing, to provide a range of acceptable responses based on facts available to the importer at the time, in lieu of a single specific response (which may become known to the importer only at a later time). ISF Importers will be required to update

their filings with respect to these elements as soon as more precise or more accurate information is available, in no event later than 24 hours prior to arrival at a U.S. port (or upon lading at the foreign port if that is later than 24 hours prior to arrival in a U.S. port). For example, 24 hours prior to lading:

• The ISF Importer could identify the manufacturer as being one of three typically used manufacturers, with more precision to be provided in subsequent ISF updates.

• The ISF Importer could submit the identity of the importer, consignee, or the facility where the goods will be unladen in the event that the ship to party is unavailable (e.g., “to order” shipments).

• If the ISF Importer is, in good faith, unable to determine whether the country where the final stage of production of an article took place is the country of origin, the ISF Importer may provide the country where the final stage of production of the article took place in lieu of the country of origin, and update the ISF submission as soon as more accurate data are available.

The purpose of these flexibilities is to allow CBP to conduct a structured review of the elements, including an evaluation of any specific compliance difficulties that the trade may be encountering with respect to these elements. CBP may gather information by conducting reviews of particular importers to determine whether submission of all 10 data elements 24 hours prior to lading was in fact feasible and, if not, what barriers the importer encountered. The structured review will cover a range of enterprises, from small to large, and will include both integrated and nonintegrated supply chains.

The structured review will further be enhanced by comments filed in response to this publication. Although the rule is now final, CBP invites comments on the 6 data elements for which CBP is providing some type of flexibility (Container stuffing location, Consolidator (stuffer), Manufacturer (or supplier), Ship to party, Country of origin, and Commodity HTSUS number). These comments are due by June 1, 2009.

The structured review will also be enhanced by feedback provided in CBP's formal outreach program, described below. The information gathering phase of the structured review will end on June 1, 2009. All comments must be submitted to CBP by that date. We note, again, that CBP is not reopening the proposed rule in this action for comment; rather CBP is seeking comment on the requirements discussed in section 149.2(b) and (f) of this rule and the revised Regulatory Impact Assessment.

On the basis of information obtained during the structured review and public comments, DHS will undertake an analysis of the elements subject to flexibilities discussed in this section. The analysis will examine compliance costs for various industry segments, the impact of the flexibilities, the barriers to submitting these data 24 hours prior to lading, and the benefits of collecting these data. Based on that analysis, DHS, in coordination with other parts of the Executive Branch, will determine whether to eliminate, modify, or leave unchanged these requirements.

CBP is committed to fully supporting the trade community in its efforts to successfully implement the requirements of this rule. During the first months of implementation—(1) CBP will conduct an extended round of structured outreach activities to engage with the trade on all aspects of the rule with a series of regional seminars and trade round table discussions at all of CBP's major seaports of entry and other ports as needed or requested by the trade. (2) CBP will identify trade community operators who have established processes (or who have successfully re-engineered processes) to deliver the data timely to CBP to provide their colleagues in the community with business advice on how to comply with the regulatory requirements. (3) CBP's seminars will focus on all topics related to this rule, technical, operational, and process components, such as documentation adjustments (

e.g.

, modifying the terms of letters of credit to require receipt of data to effect final payment) and developing automated solutions to track supply chain partners and commodity orders (

e.g.

creating vendor/supplier databases).

A proposed schedule for these outreach activities is as follows:

Regions

Proposed dates

North East Coast:

• Ports of Newark/New York and Boston

30 days after publication.

South East Coast:

• Ports of Baltimore, Philadelphia, and Norfolk

45 days after publication.

• Ports of Charleston, Savannah, and Jacksonville

60 days after publication.

• Ports of Miami, Port Everglades, and San Juan

75 days after publication.

Gulf Coast:

• Ports of Houston and New Orleans

90 days after publication.

Northwest Pacific Coast:

• Ports of Seattle/Tacoma and Portland

105 days after publication.

• Ports of Oakland/San Francisco

120 days after publication.

Pacific Coast:

• Ports of Los Angeles/Long Beach

135 days after publication.

Additional sessions will be scheduled based on trade community needs and feedback. All material discussed and presented at the seminars will be published on the CBP Web site along with Frequently Asked Questions (FAQs) and a general “How to Guide.” CBP will consider an entity's progress in the implementation of the rule during the delayed enforcement period as a mitigating factor in any enforcement action following the delayed enforcement period.

E. Summary of Changes From NPRM

As referenced below, CBP is making several significant changes from the proposed rule. These changes consist of the following:

(1) A compliance date of one year from the effective date of this final rule is established (in new §§ 4.7c(d), 4.7d(f), and 149.2(g)).

(2) CBP has added flexibility for four Importer Security Filing elements (Manufacturer (or supplier), Ship to party, Country of origin, and Commodity HTSUS number). Specifically, CBP is allowing importers, in their initial filing, to provide a range of acceptable responses based on facts available to the importer at the time, in

lieu of a single specific response (which may become known to the importer only at a later time). Importers will be required to update their filings with respect to these elements as soon as more precise or more accurate information is available, in no event less than 24 hours prior to arrival at a U.S. port (or upon lading at the foreign port if that is later than 24 hours prior to arrival in a U.S. port).

(3) CBP has added flexibility for two Importer Security Filing elements (Container stuffing location and Consolidator (stuffer)) by requiring submission as early as possible, and in any event no later than 24 hours prior to arrival in a U.S. port (or upon lading at the foreign port if that is later than 24 hours prior to arrival in a U.S. port).

(4) The requirement that break bulk cargo be included on vessel stow plans is removed from § 4.7c.

(5) The liquidated damages amount for violations of the Importer Security Filing requirements are changed from the value of the merchandise, as proposed, to $5,000 for each violation in proposed §§ 113.62(j), 113.64(e), and 113.73(c) and new § 113.63(g) and Appendix D to part 113.

CBP is also making the following additional changes from the proposed rule:

(1) Proposed § 4.7(c)(5) required carriers to provide the “Hazmat-UN code.” This section is changed to allow the carrier to provide any Hazmat code, if applicable.

(2) Proposed § 4.7d(a) is changed to clarify that CSMs are required for empty containers.

(3) The label for the party required to submit the Importer Security Filing is changed from the “importer” to the “ISF Importer” in part 149 and proposed § 149.1(a) is changed to clarify that the ISF Importer is construed as the owner, purchaser, consignee, or agent such as a licensed customs broker.

(4) Proposed § 149.3(a)(5) is changed to clarify that the supplier must be the “party supplying” the finished goods in the country from which the goods are leaving and that this party does not necessarily need to be in the country from which the goods are leaving.

(5) The definition for the “Booking party” element in proposed § 149.3(b)(1) is changed to require the identity of the “party who initiates the reservation of the cargo space for the shipment.”

(6) Proposed § 149.3(a)(1), (2), (5), (6), (9), and (10) and (b)(1) and (b)(4) are changed to allow the ISF Importer to provide widely recognized commercially accepted identification numbers.

(7) The section heading for proposed § 149.5 is changed to clarify that the eligibility and bond requirements therein apply to an ISF Importer who submits an Importer Security Filing on his own behalf as well as agents submitting an Importer Security Filing on behalf of another party.

(8) An importer security filing bond is added in a new Appendix D of part 113 and provisions for the Importer Security Filing are added to § 113.63 in a new paragraph (g).

(9) The new importer security filing bond and basic custodial bond are added to the list of bonds in proposed § 149.5(b) that may be posted for Importer Security Filing purposes.

(10) Proposed § 149.5(b) is changed to require the ISF Importer to possess one of the required bonds or to have an agent post the agent's bond when submitting an Importer Security Filing on behalf of the ISF Importer.

(11) Proposed § 149.5(c) is changed to clarify that powers of attorney must be in English and that powers of attorney and letters of revocation must be retained for five years from revocation.

(12) Proposed new 113.64(c) provides that liquidated damages for violations of advance cargo information requirements are capped at $100,000 for vessel carriers. Proposed redesignated paragraph (d) of § 113.64 is changed to include a $100,000 cap on all other conveyance arrivals as well.

(13) Sections 4.7c, 4.7d, and 149.2 are added to the list of approved information collections in § 178.2.

IV. Discussion of Comments Regarding This Rulemaking Generally

Comment

CBP should postpone implementation until the regulations can be implemented through the Automated Commercial Environment (ACE), a vigorous outreach to the public sector and other agencies of the government is undertaken and CBP is able to further study the costs, benefits, and alternatives. CBP should then issue a new Strawman

5

or initially publish the rule as an interim final rule providing details of the bonding, liquidated damages, penalty, collection proposal, and data requirements, so that companies can develop or adapt their information technology systems and software to properly transmit the filing. When CBP does proceed, the rule should include a delayed effective date of 90 days to 14 months to provide ample time for the trade to prepare their systems and processes. Following the delayed effective date, CBP should phase-in enforcement over a 12-month period during which CBP should accept less than the full complement of data elements, accept data at some point less than 24 hours prior to lading, phase in individual elements, phase in trade participants, and/or not impose any punitive measures.

5

Prior to publishing the NPRM, CBP posted a “strawman” proposal on the CBP website along with a request for comments from the trade.

CBP Response

Section 203 of the SAFE Port Act of 2006 provides that the Secretary of Homeland Security shall promulgate regulations requiring additional data elements for improved high-risk targeting. CBP has engaged the trade through the rulemaking process and through consultation as required by section 203 of the SAFE Port Act (incorporating the requirements of section 343(a) of the Trade Act of 2002). CBP has met with groups representing the trade while developing the proposal, including: The Departmental Advisory Committee on Commercial Operations of Customs and Border Protection and Related Homeland Security Functions (COAC), the American Association of Exporters and Importers (AAEI), the American Association of Port Authorities (AAPA), the Joint Industry Group (JIG), the National Association of Manufacturers (NAM), the National Customs Brokers and Forwarders Association of America (NCBFAA), the International Compliance Professionals Association (ICPA), the Retail Industry Leaders Association (RILA), the Trade Support Network (TSN), the U.S. Chamber of Commerce, and the World Shipping Council (WSC). Prior to publishing the NPRM, CBP also posted a “strawman” proposal on the CBP Web site along with a request for comments from the trade. CBP has also considered the costs, benefits, and alternatives and has prepared a cost, benefit, and feasibility analysis. An updated cost, benefit, and feasibility analysis has been prepared for this interim final rule and is available in the public docket and on Regulations.gov.

After careful consideration, DHS has determined that issuance of this interim final rule is necessary at this time to fulfill the SAFE Port Act's statutory mandate and increase the security of cargo entering the United States by vessel by improving CBP's risk assessment capabilities. The information collected pursuant to this interim final rule will greatly enhance CBP's enforcement decision making process. The sooner that CBP can obtain these data, the sooner CBP can use these data to perform better risk analysis and identification of high-risk shipments.

CBP understands that the trade may need time to adjust business practices to comply with this interim final rule and that large and complex parties may respond to these requirements differently than small and less sophisticated importers. Therefore, in order to provide the trade sufficient time to adjust to the new requirements and in consideration of the business process changes that may be necessary to achieve full compliance, CBP will show restraint in enforcing the rule, taking into account difficulties that importers may face in complying with the rule, so long as importers are making satisfactory progress toward compliance and are making a good faith effort to comply with the rule to the extent of their current ability. This policy will last for twelve months after the effective date and will apply to all aspects of the filing rule.

During this period, CBP will also work with the trade to assist them in achieving compliance and will continue to update the trade on issues associated with the regulations in the form of FAQs, postings on the CBP Web site, other outreach to the trade, and consultation with foreign countries. This rule also provides flexibilities with respect to certain elements of Importer Security Filings. CBP has also committed to a structured review of the elements, including an evaluation of any specific compliance difficulties that the trade may be encountering with respect to these elements. See the “Structured Review and Flexible Enforcement Period” section of this document for further discussion regarding the delayed compliance period, flexibilities, and CBP's structured review.

Comment

Prior to finalizing the regulations, CBP should undertake a pilot test using the required timeframes for data submission and employing the actual targeting, validation, and electronic processes that are intended to be employed upon implementation

Comment Response

As part of CBP's pre-existing Advance Trade Data Initiative (ATDI), CBP worked with a wide variety of volunteers from the world trade community to test the trade's ability to provide data, including some elements of the Importer Security Filing, to CBP. ATDI has proven that the industry has access to the required data and can get the data to CBP. CBP also has proven the ability to incorporate the ATDI data into the Automated Targeting System (ATS). Regarding timing requirements, some ATDI participants are hitting the 24 hours prior to lading deadline today. However, CBP understands that some business practices may need to change in order for the ISF Importer to obtain the required information 24 hours prior to lading. Therefore, in order to provide the trade sufficient time to comply with these requirements, CBP has taken several steps, including adoption of a 12-month delayed compliance date. This rule also provides flexibilities with respect to certain elements of Importer Security Filings. In addition, CBP has committed to a structured review of the elements, including an evaluation of any specific compliance difficulties that the trade may be encountering with respect to these elements. See the “Structured Review and Flexible Enforcement Period” section of this document for further discussion regarding the delayed compliance period, flexibilities, and CBP's structured review.

Comment

CBP should extend the comment period for the NPRM.

CBP Response

CBP published a document in the

Federal Register

(73 FR 6061) on February 1, 2008, extending the comment period an additional 15 days until March 18, 2008.

Comment

When the technical information has been developed, CBP should publish proposed data specifications in the Customs and Trade Automated Interface Requirements (CATAIR) and Customs Automated Manifest Interface Requirements (CAMIR) without requiring that a confidentiality agreement be signed and should re-issue the NPRM with a 90-day comment period.

CBP Response

CBP disagrees that re-issuing the NPRM is necessary. CBP has amended the CATAIR, CAMIR, and American National Standards Institute (ANSI) X.12 transaction messages, providing the technical requirements necessary to comply with these regulations. CBP has posted these documents to the CBP Web site. While this interim final rule becomes effective 60 days from the date of publication in the

Federal Register

—thus codifying the specific requirements—CBP is extending the compliance date to one year from the effective date and is providing flexibilities with respect to certain elements of Importer Security Filings. See the “Structured Review and Flexible Enforcement Period” section of this document for further discussion regarding the delayed compliance period and flexibilities. CBP believes that, especially with the flexibilities that CBP is providing, this is sufficient time for the trade to prepare for and comply with the new requirements.

Comment

The proposed regulation runs afoul of section 343(a)(3)(I) of the Trade Act of 2002 which requires that, where practicable, the regulations shall avoid redundant requirements because the requirement for line item information for each shipment will result in redundant Importer Security Filing submissions and CBP has announced that it intends to target upon receipt of the Importer Security Filing as well as upon entry.

CBP Response

CBP is aware that four of the Importer Security Filing elements, while collected at a different time, are identical to elements submitted for entry (CBP Form 3461) and entry summary (CBP Form 7501) purposes and two of the Importer Security Filing elements, while collected at a different time, are identical to elements submitted for application to admit goods to an FTZ (CBP Form 214). In an effort to minimize the redundancy of data transmitted to CBP, after further consideration and in response to public comments, CBP is allowing an importer to submit these elements once via the same electronic transmission to be used for both Importer Security Filing and entry/entry summary or FTZ admission purposes. With regard to redundancy of multiple Importer Security Filings, CBP understands that for some Importer Security Filing filings the 10 data elements will not change for multiple bills of lading. Therefore, CBP will accept one Importer Security Filing for multiple bills of lading in the same shipment.

Comment

This rule has become superfluous with the statutory requirement for the foreign port image scanning of all containerized maritime cargoes prior to their being placed on vessels for shipment to the United States. In addition, there has been no demonstration that the Importer Security Filing will contribute to the effectiveness of the ATS.

CBP Response

CBP disagrees. Advance cargo information provides transparency into the transaction, including the parties

and goods involved, which is part of the overall risk analysis. The information required by this rule will allow CBP to conduct data analysis to more effectively identify high-risk containers for increased scrutiny, and screen out shipments for increased scrutiny. Additional scrutiny could include additional non-intrusive inspection (NII) and physical examination. The value of NII, including radiation detection capabilities, is increased when the targeter has a frame of reference which is provided by accompanying transaction data such as the data required pursuant to these regulations.

Comment

CBP should scan 100% of cargo in lieu of requiring an Importer Security Filing, vessel stow plans and container status messages (CSMs).

CBP Response

CBP disagrees. The physical cargo is only one piece of the puzzle. Information, such as the information collected as a result of this rulemaking will allow CBP to put the image produced by a scan into context. The scan and Importer Security Filing together will provide additional transparency and validate the shipment and parties involved.

Comment

It is unclear how the proposed requirements will enhance the security of the United States. This rule could result in increased transit time, which could actually increase security risks.

CBP Response

Pursuant to section 203 of the SAFE Port Act (6 U.S.C. 943), the Secretary of Homeland Security, acting through the Commissioner of CBP, must promulgate regulations to require the electronic transmission of additional data elements for improved high-risk targeting, including appropriate security elements of entry data for cargo destined to the United States by vessel prior to loading of such cargo on vessels at foreign seaports. The Importer Security Filing elements, vessel stow plans, and CSMs will enhance CBP's targeting and risk analysis capabilities by increasing the transparency of key supply chain participants, cargo, and events. CBP does not agree that increased transit time (dwell time at a foreign port terminal), if incurred due to this rulemaking, will result in an increased security risk. The risk reduction provided by the collection of additional information that will result from these regulations is significantly greater than any risk increase resulting from any increased dwell times. Furthermore, CBP is addressing global port security through other initiatives.

Comment

The Importer Security Filing should be expanded to prevent dangerous merchandise, including narcotics and other illegal consignments, from being shipped to the United States.

CBP Response

This rule is one part of CBP's layered approach to cargo security. CBP has implemented a comprehensive strategy designed to enhance national security while protecting the economic vitality of the United States. The Container Security Initiative (CSI), the 24 Hour Rule, and the Customs-Trade Partnership Against Terrorism (C-TPAT) are cornerstone approaches implemented to further this goal. Additionally, CBP has developed cargo risk assessment capabilities in its Automated Targeting System (ATS) to screen all maritime containers before they are loaded aboard vessels in foreign ports. Each of these initiatives is dependent upon data supplied by trade entities, including carriers, non-vessel operating common carriers (NVOCCs), brokers, importers or their agents. Internal and external government reviews have concluded that the more complete advance shipment data required pursuant to this interim final rule will produce even more effective and more vigorous cargo risk assessments. Accordingly, CBP will use these data to ensure cargo safety and security and to prevent smuggling.

Comment

Limiting the proposed requirements to the vessel environment will encourage circumvention by transshipment through Canada and Mexico. Does CBP plan to apply these requirements to other modes in the future? Significant adjustment will be necessary if these rules are applied to other modes.

CBP Response

CBP disagrees that this rule encourages circumvention, as the United States has a strong working relationship with both Canadian and Mexican border enforcement agencies. CBP will monitor any unexplained increases in land border traffic and will take appropriate security measures if warranted. This interim final rule is focused on vessel cargo pursuant to the requirements under the SAFE Port Act 2006 and the Trade Act of 2002. As such, this rule is an incremental step toward meeting the goal of securing shipments to the United States. CBP will continue to evaluate the effectiveness of this rule. However, at this time, CBP is not considering expanding the advance data requirements for other modes.

Comment

CBP should conduct outreach with the trade, including presentation of a white paper, PowerPoint presentation, and FAQs, prior to implementation and during the implementation phase, including a regular and recurring collaborative process with COAC and the TSN. CBP should also produce a “best practices” document, including detailed process flows, for industry and CBP officers to ensure that all trade participants understand how to comply with the new requirements. Importers will need to implement new processes regardless of whether enforcement is phased in.

CBP Response

CBP agrees that business practices and processes will need to be adjusted and that is reflected in our delayed compliance period and outreach efforts.

See

the “Structured Review and Flexible Enforcement Period” section of this document for further discussion regarding the delayed compliance period. CBP has amended the CATAIR, CAMIR, and X.12 transaction messages, providing the technical requirements necessary for submitting Importer Security Filings. These documents have been posted to the “Automated Systems” section of the CBP Web site. CBP will continue to conduct outreach with the trade, in fulfillment of its regulatory and statutory obligations, both during the delayed compliance period and thereafter, via FAQs, postings on the CBP Web site, and other outreach.

Comment

CBP should provide a Help Desk to assist in the resolution of problems associated with the Importer Security Filing requirements.

CBP Response

CBP will utilize existing resources to resolve problems associated with the Importer Security Filing requirements. In order to get access to the Automated Broker Interface (ABI) or the Vessel Automated Manifest System (vessel AMS), members of the trade should contact a CBP Client Representative or the CBP Technology Support Center (TSC), formerly known as the CBP Help Desk, for resolution of technical problems associated with Importer Security Filings. In addition, CBP has

established a dedicated email account for Importer Security Filing-related issues. Members of the public are directed to the CBP Web site at

http://www.cbp.gov

for the latest information regarding these contacts. CBP will also continue to update the trade in the form of FAQs, postings on the CBP Web site, and other outreach to the trade.

Comment

The information that CBP has requested is the same information that thousands of shippers, importers and manufacturers have at their fingertips every day. It has long been understood that importing into the United States is a privilege, not a right. Thus, it is completely proper for CBP to require those who would take advantage of our nation's prosperity to help to protect that prosperity. Importers will have an added incentive to investigate and identify the identity of their suppliers due to the penalties associated with improper Importer Security Filings. CBP should also be commended for its open, consultative approach in developing this initiative and these regulations.

CBP Response

CBP appreciates the support and cooperation offered by the trade.

V. Discussion of Comments Regarding Proposed Carrier Requirements Relating to Vessel Cargo Destined to the United States

A. Overview; Vessel Stow Plan

CBP proposed to require carriers to submit a vessel stow plan for vessels destined to the United States. Under the proposed regulations, carriers were required to transmit the stow plan for vessels transporting containers and/or break bulk cargo so that CBP received it no later than 48 hours after the carrier's departure from the last foreign port. For voyages less than 48 hours in duration, CBP was to receive the stow plan prior to the vessel's arrival at the first port in the United States. Bulk carriers were to be exempt from this requirement for vessels exclusively carrying bulk cargo. The proposal required carriers to submit the vessel stow plan via the CBP-approved electronic data interchange system. The current approved electronic data interchange system for the vessel stow plan is vessel AMS. The proposal stated that if CBP approves of different or additional electronic data interchange systems, CBP would publish a notice in the

Federal Register

.

Under the proposed regulations, the vessel stow plan was required to include standard information relating to the vessel and each container and unit of break bulk cargo laden on the vessel. The vessel stow plan was to include the following standard information:

With regard to the vessel,

(1) Vessel name (including international maritime organization (IMO) number);

(2) Vessel operator; and

(3) Voyage number.

With regard to each container or unit of break bulk cargo,

(1) Container operator, if containerized;

(2) Equipment number, if containerized;

(3) Equipment size and type, if containerized;

(4) Stow position;

(5) Hazmat-UN code;

(6) Port of lading; and

(7) Port of discharge.

B. Public Comments; Vessel Stow Plan

Comments Regarding Responsibilities

The vessel operating carrier, rather than the non-vessel operating common carrier (NVOCC), should be responsible for filing the stow plan. The NVOCC may not have the vessel stow plan because they do not operate the vessel and have no knowledge of the physical location of cargo as loaded on the vessel. Stow plans are not created to meet regulatory requirements, and therefore a vessel operating carrier should not be responsible for inaccuracies or incompleteness. In addition, carriers should not be responsible for errors in information carriers are unable to verify.

CBP Response

CBP agrees that the vessel operating carrier (i.e., vessel operator) is responsible for filing the stow plan. While, prior to this interim final rule, stow plans were not created to meet regulatory requirements, CBP is requiring, through this rulemaking, that vessel carriers submit accurate and timely stow plans for containerized cargo. CBP will use stow plan data to compare the containers listed on the stow plan with containers listed on the vessel's manifest in an effort to identify potentially unmanifested containers. CBP may take enforcement action against a carrier that fails to comply with the requirement to submit stow plans in a timely or accurate manner. CBP enforcement actions may include, but are not limited to, claims for liquidated damages pursuant to 19 CFR 113.64(f). However, CBP has set a compliance date of one year from the effective date of this interim final rule. During that one-year delayed compliance period, CBP will work with the trade to assist them in achieving compliance. CBP will also work with the trade on ongoing issues and will keep updating and posting new FAQs to the CBP Web site, while conducting additional outreach to the trade and various foreign government entities. See the “Structured Review and Flexible Enforcement Period” section of this document for further discussion regarding the delayed compliance period and CBP's planned outreach efforts.

Comments Regarding Procedures

Commenters questioned whether a stow plan is required for every U.S. arrival from a foreign port. Some also stated that CBP should provide the vessel stow plan filer an electronic acknowledgment, containing time and date of receipt and unique identification number, as evidence that the vessel stow plan was successfully received. Others questioned which formats can be used for submission of vessel stow plans and whether CBP will accept vessel stow plans in Adobe Portable Document Format (.pdf). Some also stated that CBP should also accept the U.S. hazardous material (hazmat) codes or Hazmat class in addition to the proposed Hazmat-UN code and that CBP should not use the stow plan for securing detailed and complete hazmat information. Where reference is made to the equipment number, commenters questioned whether CBP wanted carriers to report the unique Vehicle Identification Number (VIN) for vehicles or if a simple vehicle count is sufficient.

CBP Response

CBP must receive a stow plan after the vessel departs from the last foreign port. CBP agrees that the vessel stow plan filer should receive a status notification message acknowledging that the vessel stow plan was accepted by CBP's system. As to formats, CBP will accept vessel stow plans in the United Nations rules for Electronic Data Interchange For Administration, Commerce and Transport (UN EDIFACT) Bayplan/stowage plan occupied and empty locations message (BAPLIE) SMDG format, which is the industry-wide standard for carriers who currently use electronic stow plans. CBP will also work with carriers to accept the ANSI X.12 “324” format on a case-by-case basis. Other formats, such as the Adobe.pdf format, are not specifically designed for stow plans and, therefore, would be difficult for CBP systems to interpret. Therefore, CBP cannot justify the costs associated with supporting these additional formats at this time. CBP will continue to consider

additional formats in the future. Regarding hazardous materials reporting on vessel stow plans, the commenter did not provide information regarding what was intended by reference to U.S. Hazmat codes. The U.S. Department of Transportation Hazardous Materials Table lists Hazmat-UN identification numbers and hazard classes.

See

49 CFR part 172.101. In order to minimize the cost to carriers, CBP will accept any widely recognized commercially acceptable hazardous materials identification numbers and classifications that the carrier uses in the normal course of business, such as those listed on the U.S. Department of Transportation Hazardous Materials Table. Regarding VINs, a VIN is not required as part of a stow plan. Also, since stow plans are not required for break bulk merchandise, they will not be required for vehicles unless they are containerized.

Comments Regarding Scope of Requirements for Stow Plan

CBP should not require stow plans for vessels transporting fewer than a threshold number of containers or for vessels traveling solely within the U.S. Outer Continental Shelf (OCS). CBP should not require stow plans for break bulk cargo (including roll-on/roll-off vessels) because break bulk is obvious as to what it is and where it is in the cargo hold and, therefore, of limited security value. CBP should also not require stow plans for bulk ships carrying either containers or break bulk cargoes on deck. Some questioned whether a carrier will need to include cargo that is not bound for the United States on a stow plan.

CBP Response

A stow plan must be filed for each vessel carrying containerized cargo that is required to transmit an advance cargo declaration pursuant to section 343(a) of the Trade Act of 2002. CBP will use stow plan data to compare the containers listed on the stow plan with containers listed on the vessel's manifest in an effort to identify potentially unmanifested containers. Unmanifested containers are considered to be of the highest risk to our nation's security since there is little information available about the contents or intended destination of these containers. Even a single unmanifested container poses a possible threat to the security of the United States. For this reason, CBP does not intend to establish an exemption from the stow plan requirement based on the number of containers carried on a vessel or for vessels traveling solely within the U.S. OCS. After further consideration and in response to comments, CBP has determined to not require break bulk cargo on stow plans. However, regardless of the type of vessel (including break bulk and bulk vessels), a vessel stow plan accounting for all containers onboard a vessel must be submitted to CBP. Finally, carriers will be required to submit stow plans for all containerized cargo that will enter the limits of a port in the United States.

Comments Regarding the Timing for Submission of the Stow Plan

Commenters questioned the timing for stow plans for trips of very short duration (

e.g.

, Vancouver to Seattle). It was suggested that the stow plan not be required earlier than the required United States Coast Guard Notice of Arrival, which is 96 hours prior to arrival. It was also suggested that CBP should amend the regulations, as proposed, to require submission of the stow plan 48 hours after the vessel departs from the last foreign port where goods

are laden

on the vessel rather than the last foreign port. Others questioned when a vessel “arrives” for vessel stow plan timing purposes. Finally, commenters questioned whether carriers need to amend stow plans. If so, carriers should only be required to amend stow plans when they find that a container has been stowed aboard that was not on the stow plan as submitted to CBP and not when a container is on a stow plan but was not loaded aboard the vessel.

CBP Response

Stow plans are required for vessels carrying containers destined to the United States. For voyages less than 48 hours in duration (including very short voyages), CBP must receive the stow plan prior to the vessel's arrival at the first port in the United States. CBP disagrees with the remaining comments. Under the interim final rule, stow plans are required no later than 48 hours after the vessel departs from the last foreign port so that CBP has an accurate representation of the cargo laden on the vessel as it arrives in the United States. Except for voyages less than 48 hours in duration, a vessel stow plan must be submitted 48 hours after the vessel departs from the last foreign port, whether goods are laden and/or unladen at that port, so that the vessel stow plan will accurately depict the cargo onboard when the vessel arrives within the limits of a port in the United States. Vessel arrival for vessel stow plan purposes is the same as vessel arrival for vessel entry purposes. Arrival of a vessel is defined in 19 CFR 4.0.

See also

19 CFR 4.2 regarding reports of arrival of vessels. Finally, inasmuch as CBP requires that an accurate and complete stow plan be submitted, a carrier must submit a new accurate stow plan immediately upon discovery of any inaccuracies. However, the carrier will still be liable for enforcement actions resulting from the inaccurate vessel stow plan.

C. Overview; Container Status Messages

Pursuant to section 343(a) of the Trade Act of 2002, CBP proposed to require carriers to submit CSMs daily for certain events relating to all containers laden with cargo destined to arrive within the limits of a port in the United States by vessel.

Under the proposed regulations, CSMs created under either the ANSI X.12 standard or the UN EDIFACT standard were to be acceptable.

Under the proposed regulations, carriers were required to submit a CSM when any of the required events occurs if the carrier creates or collects a CSM in its equipment tracking system reporting that event. The proposed regulations would not require a carrier to create or collect any CSM data other than that which the carrier already creates or collects on its own and maintains in its electronic equipment tracking system. CSMs were to be submitted no later than 24 hours after the message is entered into the carrier's equipment tracking system.

The events for which CSMs would be required are:

(1) When the booking relating to a container which is destined to arrive within the limits of a port in the United States by vessel is confirmed;

(2) When a container which is destined to arrive within the limits of a port in the United States by vessel undergoes a terminal gate inspection;

(3) When a container, which is destined to arrive within the limits of a port in the United States by vessel, arrives or departs a facility (These events take place when a container enters or exits a port, container yard, or other facility. Generally, these CSMs are referred to as “gate-in” and “gate-out” messages.);

(4) When a container, which is destined to arrive within the limits of a port in the United States by vessel, is loaded on or unloaded from a conveyance (This includes vessel, feeder vessel, barge, rail and truck movements. Generally, these CSMs are referred to as “loaded on” and “unloaded from” messages);

(5) When a vessel transporting a container, which is destined to arrive within the limits of a port in the United States by vessel, departs from or arrives

at a port (These events are commonly referred to as “vessel departure” and “vessel arrival” notices);

(6) When a container which is destined to arrive within the limits of a port in the United States by vessel undergoes an intra-terminal movement;

(7) When a container which is destined to arrive within the limits of a port in the United States by vessel is ordered stuffed or stripped;

(8) When a container which is destined to arrive within the limits of a port in the United States by vessel is confirmed stuffed or stripped; and

(9) When a container which is destined to arrive within the limits of a port in the United States by vessel is shopped for heavy repair.

CBP is aware that it might be cost beneficial for some carriers to transmit all CSMs, rather than filter out CSMs relating to containers destined to the United States or relating only to the required events. Therefore, CBP proposed to allow carriers to transmit their “global” CSM messages, including CSMs relating to containers that do not contain cargo destined for importation into the United States and CSMs relating to events other than the required events. CBP stated in the proposal that by transmitting CSMs in addition to those required by the proposed regulations, a carrier would authorize CBP to access and use those data.

For each CSM submitted, the following information was proposed to be included:

(1) Event code being reported, as defined in the ANSI X.12 or UN EDIFACT standards;

(2) Container number;

(3) Date and time of the event being reported;

(4) Status of the container (empty or full);

(5) Location where the event took place; and

(6) Vessel identification associated with the message.

Carriers would be exempt from the CSM requirement for bulk and break bulk cargo. Under the proposed regulations, carriers would be required to submit CSMs via the CBP-approved electronic data interchange system. The current approved electronic data interchange system for CSMs is vessel AMS. The proposal stated that if CBP approves of a different or additional electronic data interchange system, CBP will publish notice in the

Federal Register

.

D. Public Comments; Container Status Messages

Comments Regarding Responsibilities

Some commenters questioned whether the vessel operating carrier or NVOCC, when applicable, is required to submit CSMs. Others asked whether a carrier that has no electronic equipment tracking system needs to report any CSMs and when a carrier may stop sending event messages. Some noted that CBP should require all carriers, not just those who currently create or collect CSMs, to submit CSMs.

CBP Response

Vessel operating carriers are required to submit CSMs. If a carrier currently does not create or collect CSMs in an equipment tracking system, the carrier is not required to submit CSMs to CBP. If a carrier does create or collect CSMs, the carrier's obligation to transmit CSMs ends upon discharge of the cargo in the United States. However, a carrier may transmit other CSMs in addition to those required by these regulations. By transmitting additional CSMs, the carrier authorizes CBP to access and use those data. In order to minimize the cost to carriers whose volume of business does not justify the creation of CSMs, CBP is declining to impose an obligation upon carriers to create or collect any CSM data pursuant to this rule.

Comments Regarding Scope of Requirements for CSMs

Some questioned whether CSMs are required for empty containers since as proposed, 19 CFR 4.7d would require CSMs for containers laden with cargo destined to arrive within the limits of a port in the United States from a foreign port by vessel. For each CSM, however, it seems that the “status of the container (empty or full)” must be reported. Others observed that some of the events for which CSMs are required are not reported via CSMs in all instances. For example, carriers may not create or collect CSMs when bookings are confirmed, when a container enters or exits a facility, when a vessel departs or arrives, when a container undergoes an intra-terminal movement, or when a container is ordered stuffed or stripped or confirmed stuffed or stripped. In addition, loaded containers are not “shopped for heavy repairs.” Others noted that since CSMs are not created to meet regulatory requirements a vessel operating carrier should not be responsible for inaccuracies or incompleteness. In addition, there should not be an obligation to ensure that each of the six data elements is in each CSM since there is “no requirement that a carrier create or collect any CSM data.”

CBP Response

CSMs are required for all containers, including empty containers, destined to arrive within the limits of a port in the United States from foreign by vessel (if the carrier creates or collects a CSM in its equipment tracking system). As commenters pointed out, each CSM must include the status of the container as either empty or full. The reference in the NPRM to containers “laden with cargo destined to arrive within the port limits in the United States” was intended to differentiate those containers that are destined for the United States from containers that are not destined to arrive within the limits of a port in the United States. Section 4.7d has been amended to clarify that CSMs are required for all containers destined to arrive within the limits of a port in the United States. It remains CBP's position at this time to minimize the cost to carriers whose volume of business does not justify the creation of CSMs by only requiring a carrier to submit CSMs if the carrier creates or collects a CSM in its equipment tracking system. Nevertheless, CBP believes that every CSM for containers laden with cargo destined to arrive within the limits of a port in the United States from foreign by vessel, by their very nature, must contain the six required elements. Accordingly, while there is no requirement that carriers create or collect any CSMs pursuant to this rule, every CSM submitted to CBP must contain the six required elements with the exception of the “Vessel identification associated with the message.” This element is not required when a container has not yet been associated with a specific vessel.

Comments Regarding Procedures

When the NPRM refers to “loaded on” and “unloaded from” messages, is CBP referring to CSMs generated when a container is loaded or unloaded to or from a vessel or to or from a rail carrier? CBP should also clarify whether the “date and time of the event being reported” refers to the date and time when the event occurred in real-time and not when it was entered into a carrier's equipment tracking system and whether CBP will accept the carrier's definition of location where the event took place as currently reported in their equipment system. CBP should clarify what type of identification should be transmitted for the “vessel identification associated with the message”—i.e., should this be a vessel name, number, IMO, vessel operator, or other

identification? In addition, some CSMs will be created before there is a vessel associated with the message. Commenters also stated that CBP should clarify when a container is considered to have been “confirmed stuffed or stripped,”—i.e., will it be left up to the carrier's discretion to define when they deem a booking has reached a “confirmed” status? A date should be optional for this CSM since stuffing and stripping of containers is generally not performed by the carrier. Finally, commenters questioned whether a do not load (DNL) should be issued; whether an importer's cargo would be subject to increased scrutiny if the carrier fails to submit a vessel stow plan or container status messages; whether the Importer Security Filing filer will be notified if a DNL is issued in this instance; and whether the importer be liable for vessel stow plan and CSM related errors (e.g., when a carrier “rolls over” a container to another vessel and fails to report this to CBP).

CBP Response

CSM events include messages about movements such as when a container, which is destined to arrive within the limits of a port in the United States by vessel, is loaded on or unloaded from any conveyance. This includes vessel, feeder vessel, barge, rail, and truck movements. The date and time when the event actually occurred should be reported. The location as recorded in the carrier's equipment tracking system should be reported. For purposes of the vessel identification, CBP will accept whatever unique identifier is used within the carrier's tracking system. CBP has changed the proposal in these interim final regulations to require the vessel identification associated with the message only if a container has been associated with a specific vessel. With regard to confirmation of stuffing, a booking is “confirmed” by a carrier's own booking system. Similarly, a container is confirmed stuffed or stripped by a carrier's own booking system. Accordingly, it is left up to the carrier's discretion to define when a booking is deemed confirmed and a container is confirmed stuffed or stripped. Finally, if a carrier fails to submit a vessel stow plan or container status messages, when a carrier is required to do so, CBP may take appropriate enforcement actions, including but not limited to, issuance of a DNL, a prelude to a denial of a permit to unlade the container(s) upon arrival in the United States. However, CBP will not notify the party who filed the Importer Security Filing regarding DNL messages not related to their Importer Security Filing. If parties wish to share these data, they will need to do so privately. Regarding vessel stow plan and CSM-related errors, the importer is not responsible for submitting stow plans and CSMs to CBP and is therefore not liable for inaccuracies or errors.

E. Public Comments; Carrier Requirements Generally

Comment

CBP should require the terminal operator to submit vessel stow plans and container status messages. The vessel operator should be responsible for filing CSMs and vessel stow plans when there is a vessel sharing or space charter agreement. In the alternative, carriers should be able to designate a third party to submit CSMs and the vessel stow plan on the carrier's behalf.

CBP Response

CBP disagrees that terminal operators should be required to submit vessel stow plans and container status messages. The vessel operator is responsible for the submission of the vessel stow plan because it is the party operating the vessel and transporting the cargo to the United States. All vessel operating carriers who create or collect CSMs for cargo that is destined to enter the limits of a port in the United States, including slot and other vessel sharing partners, are responsible for the submission of CSMs. In response to requests from the trade, CBP will allow the responsible carrier to designate a third party agent to transmit stow plans and CSMs. However, the obligation and liability for those requirements remains with the carrier.

VI. Discussion of Comments Regarding Proposed Importer Requirements for Vessel Cargo Destined to the United States

A. Overview; Proposed Importer Requirements

Pursuant to the authority of section 343(a) of the Trade Act of 2002, as amended by MTSA, and section 203 of the SAFE Port Act, in order to enhance the security of the maritime environment, CBP proposed to require importers, as defined in the proposal, or their agents, to transmit an Importer Security Filing to CBP, for cargo other than FROB, no later than 24 hours before cargo is laden aboard a vessel destined to the United States. Because FROB is frequently laden based on a last-minute decision by the carrier, the Importer Security Filing for FROB was to be required any time prior to lading.

6

Under the proposed regulations, an Importer Security Filing was required for each shipment, at the lowest bill of lading level (i.e., at the house bill of lading level, if applicable). It is information from the relevant house bill that CBP proposed to collect.

6

CBP did not propose to amend the timing requirements in 19 CFR part 4 requiring submission of advance manifest information 24 hours prior to lading.

Under the proposal, the party required to submit the Importer Security Filing was the party causing the goods to enter the limits of a port in the United States. The proposal stated that this party would be construed as the carrier for FROB and as the party filing IE, T&E, or FTZ documentation for those types of shipments. CBP proposed to allow an importer, as defined in the proposal, as a business decision, to designate an authorized agent to file the Importer Security Filing on the importer's behalf. Under the proposed regulations, a party could act as an authorized agent for purposes of filing the Importer Security Filing if that party obtains access to ABI or AMS and obtains a bond.

Under the proposed regulations, importers, as defined in the proposal, or their agents, would be required to transmit the Importer Security Filing via a CBP-approved electronic data interchange system. The proposal stated that the current approved electronic data interchange systems for the Importer Security Filing was ABI and vessel AMS and that, if CBP approves a different or additional electronic data interchange system in the future, CBP would publish notice in the

Federal Register

.

Under the proposed regulations, the party who filed the Importer Security Filing would be required to update the Importer Security Filing if, after the filing and before the goods arrive within the limits of a port in the United States, there were changes to the information filed or more accurate information becomes available.

Under the NPRM, CBP proposed to require ISF Importers to submit 10 elements for shipments consisting of goods intended to be entered into the United States and goods intended to be delivered to an FTZ. For goods to be delivered to an FTZ, CBP considered the importer to be the party filing the FTZ documentation with CBP. CBP proposed to require that the importer or the importer's agent must transmit these 10 elements to CBP. Under the proposal, five elements were required for shipments consisting entirely of FROB and shipments consisting entirely of

goods intended to be “transported” as IE or T&E in-bond shipments.

Under the proposal, for FROB, the importer would be construed as the international carrier of the vessel arriving in the United States. For IE and T&E in-bond shipments, the importer was construed as the party filing the IE or T&E documentation with CBP.

1. Shipments Other Than FROB, IE Shipments, and T&E Shipments

Under the proposed regulations, for the Importer Security Filing for shipments other than those consisting entirely of FROB and goods intended to be “transported” in-bond as an IE or T&E, 10 elements were required, unless specifically exempted. The manufacturer (or supplier) name and address, country of origin, and commodity Harmonized Tariff Schedule of the United States (HTSUS) number were to be linked to one another at the line item level.

The 10 proposed required elements were:

(1)

Manufacturer (or supplier) name and address.

Name and address of the entity that last manufactures, assembles, produces, or grows the commodity or name and address of the supplier of the finished goods in the country from which the goods are leaving. In the alternative, the name and address of the manufacturer (or supplier) that is currently required by the import laws, rules and regulations of the United States (i.e., entry procedures) may be provided (this is the information that is used to create the existing manufacturer identification (MID) number for entry purposes).

(2)

Seller name and address.

Name and address of the last known entity

by whom

the goods are sold or agreed to be sold. If the goods are to be imported otherwise than in pursuance of a purchase, the name and address of the owner of the goods must be provided.

7

7

The party required for this element is consistent with the information required on the invoice of imported merchandise.

See

19 CFR 141.86(a)(2).

(3)

Buyer name and address.

Name and address of the last known entity

to whom

the goods are sold or agreed to be sold. If the goods are to be imported otherwise than in pursuance of a purchase, the name and address of the owner of the goods must be provided.

8

8

The party required for this element is consistent with the information required on the invoice of imported merchandise.

See

19 CFR 141.86(a)(2).

(4)

Ship to name and address.

Name and address of the first deliver-to party scheduled to physically receive the goods after the goods have been released from customs custody.

(5)

Container stuffing location.

Name and address(es) of the physical location(s) where the goods were stuffed into the container. For break bulk shipments, the name and address(es) of the physical location(s) where the goods were made “ship ready” must be provided.

(6)

Consolidator (stuffer) name and address.

Name and address of the party who stuffed the container or arranged for the stuffing of the container. For break bulk shipments, the name and address of the party who made the goods “ship ready” or the party who arranged for the goods to be made “ship ready” must be provided.

(7)

Importer of record number/FTZ applicant identification number.

Internal Revenue Service (IRS) number, Employer Identification Number (EIN), Social Security Number (SSN), or CBP assigned number of the entity liable for payment of all duties and responsible for meeting all statutory and regulatory requirements incurred as a result of importation. For goods intended to be delivered to an FTZ, the IRS number, EIN, SSN, or CBP assigned number of the party filing the FTZ documentation with CBP must be provided. The importer of record number for Importer Security Filing purposes is the same as “importer number” on CBP Form 3461.

(8)

Consignee number(s).

Internal Revenue Service (IRS) number, Employer Identification Number (EIN), Social Security Number (SSN), or CBP assigned number of the individual(s) or firm(s) in the United States on whose account the merchandise is shipped. This element is the same as the “consignee number” on CBP Form 3461.

(9)

Country of origin.

Country of manufacture, production, or growth of the article, based upon the import laws, rules and regulations of the United States. This element is the same as the “country of origin” on CBP Form 3461.

(10)

Commodity HTSUS number.

Duty/statistical reporting number under which the article is classified in the Harmonized Tariff Schedule of the United States (HTSUS). The HTSUS number is required to be provided to the six-digit level. The HTSUS number may be provided up to the 10-digit level. This element is the same as the “H.S. number” on CBP Form 3461 and can only be used for entry purposes, if it is provided at the 10-digit level or greater.

2. FROB, IE Shipments, and T&E Shipments

Under the proposed regulations, for the Importer Security Filing for shipments consisting entirely of FROB and shipments consisting entirely of goods intended to be “transported” in-bond as an IE or T&E, five elements were to be provided in order to enhance the security of the maritime environment.

The five proposed required elements were:

(1)

Booking party name and address.

Name and address of the party who is paying for the transportation of the goods.

(2)

Foreign port of unlading.

Port code for the foreign port of unlading at the intended final destination.

(3)

Place of delivery.

City code for the place of delivery.

(4)

Ship to name and address.

Name and address of the first deliver-to party scheduled to physically receive the goods after the goods have been released from customs custody.

(5)

Commodity HTSUS number.

Duty/statistical reporting number under which the article is classified in the Harmonized Tariff Schedule of the United States (HTSUS). The HTSUS number must be provided to the six-digit level. The HTSUS number may be provided up to the 10-digit level.

Four of the proposed Importer Security Filing elements are identical to elements submitted for entry (CBP Form 3461) and entry summary (CBP Form 7501) purposes. These elements are the importer of record number, consignee number, country of origin, and commodity HTSUS number when provided at the 10-digit level. CBP proposed to allow an importer to submit these elements once to be used for both Importer Security Filing and entry/entry summary purposes. Under the proposed regulations, if an importer chooses to have these elements used for entry/entry summary purposes, the Importer Security Filing and entry/entry summary must be self-filed by the importer or filed by a licensed customs broker in a single transmission to CBP. In addition, the HTSUS number would be required at the 10-digit level.

As proposed, two of the Importer Security Filing elements are identical to elements submitted for application to admit goods to an FTZ (CBP Form 214). These elements are the country of origin and commodity HTSUS number when provided at the 10-digit level. CBP proposed to allow a filer to submit the Importer Security Filing and CBP Form 214 in the same electronic transmission to CBP and to submit the country of origin and commodity HTSUS number once to be used for both Importer Security Filing and FTZ admission purposes. If the party submitting the Importer Security Filing chose to have this element used for FTZ admission purposes, the HTSUS number would be required at the 10-digit level.

B. Public Comments; Responsible Party

Comment

Under section 343(a) of the Trade Act of 2002, as amended, the requirement to provide information to CBP is generally to be imposed upon the party likely to have direct knowledge of the required information. Although CBP has identified the importer (as defined in the NPRM) as the party to send the data, it has not demonstrated that the importer is in fact that party. The supplier, freight forwarder, and/or carrier actually may have the most direct knowledge of the required information. For example, some suppliers arrange their own carriage and, therefore, the importer will not have the information necessary to submit the Importer Security Filing. Similarly, the importer may not even be aware that the merchandise has been shipped until it arrives in the United States. CBP should require the party with the best knowledge of the shipment to submit the Importer Security Filing. Commenters suggested that CBP not create a new definition of “importer” for Importer Security Filing purposes only, but rather adopt an alternate term. This party should be defined to include the “importer” (as defined in 19 CFR 101.1) or the duly authorized agent of that party, and should include the traditional importer of record as listed on the CBP Form 7501. In the alternative, the definition of “importer” should be the “principal party of interest” as that term is used for the Shipper's Export Declaration or parties as defined for Incoterms.

CBP Response

Based on CBP's experience in the movement of goods in international trade, there is one party that is ultimately interested in and responsible for causing goods to arrive in the United States. CBP has determined that the party most likely to have direct knowledge of the required information, and therefore, the party considered to be the ISF Importer, is the party causing the goods to enter the limits of a port in the United States. CBP also has determined that such party must be the owner, purchaser, consignee or their agent (such as a licensed broker) who as a result of this rulemaking will now have an obligation to ascertain and report the data elements that CBP is requiring under this rule to enhance its ability to target high risk cargo destined for the United States. However, in recognition that there may be circumstances where the ISF Importer may not reasonably be able to verify the information, these regulations allow this party to submit the information on the basis of what it reasonably believes to be true. For FROB cargo, the ISF Importer is construed as the carrier. For IE and T&E in-bond shipments, and goods to be delivered to an FTZ, the ISF Importer is construed as the party filing the IE, T&E, or FTZ documentation. For other types of shipments, this party will usually be the importer of record. However, the party causing the goods to enter the limits of a port in the United States may be different parties to a transaction depending on the terms of the transaction and the parties involved, and this party may be a party other than the importer of record (e.g., for “to order” shipments). Therefore, requiring the importer of record to submit the Importer Security Filing in all instances would be inappropriate.

Comment

An international carrier may not have house bill of lading level information for Importer Security Filings for FROB shipments because NVOCCs may not provide the information to the vessel operating carriers. Therefore, CBP should make the NVOCC responsible for Importer Security Filings in these situations. In addition, NVOCCs do not generate unique sub-house bills and, therefore, in order to comply with the Importer Security Filing requirements, NVOCCs will need six months to convert their systems. If the sub-house bill of lading number is required for the Importer Security Filing, this should also be required for AMS.

CBP Response

CBP disagrees that NVOCCs should be required to submit Importer Security Filings. The obligation for the Importer Security Filing for FROB remains with the vessel operating carrier because this is the party choosing to transport the cargo to the United States. CBP understands the house bill of lading level information may belong to the NVOCCs. Therefore, CBP clarifies that the NVOCC can submit the Importer Security Filing directly to CBP, if it does so as the vessel operating carrier's agent. CBP is requiring an Importer Security Filing at the lowest level to the house bill of lading level, if applicable. CBP is not requiring Importer Security Filings for sub-house bills.

Comment

For FTZ goods, CBP should require the “applicant on the FTZ documentation filed with CBP” to file the Importer Security Filing rather than the “party filing the FTZ documentation with CBP.” For IE and T&E shipments, commenters questioned whether the party required to submit the Importer Security Filing is the party named on the CBP Form 7512 or the party that submits the CBP Form 7512. Who is responsible for filing the Importer Security Filing for personal/household goods and military/government shipments? Who is the responsible party for delivered duty paid (DDP) shipments where the Importer Security Filing “importer” can be the overseas shipper? Commenters asked how NVOCCs will comply with the Importer Security Filing requirements.

CBP Response

For IE and T&E in-bond shipments and goods to be delivered to an FTZ, the ISF Importer is the party filing the documentation with CBP and not merely a party delivering the form to CBP. For shipments, including personal/household goods, military/government shipments, and DDP shipments that are intended to be entered into the United States, the ISF Importer would be the owner, purchaser, consignee, or agent such as a licensed customs broker, as the party causing the goods to enter the limits of the United States. If an NVOCC is the party required to submit an Importer Security Filing on its own behalf, or as an agent for another party, the NVOCC will need to submit the Importer Security Filing pursuant to these regulations.

Comment

CBP should expand the manifest filing to include elements such as the container stuffing location and consolidator (stuffer) rather than require a separate Importer Security Filing submission. CBP should require entry, with additional elements, be made prior to lading in lieu of requiring a separate Importer Security Filing.

CBP Response

CBP disagrees that the advance cargo declaration filing should be expanded. The data elements for the advance cargo declaration and the Importer Security Filing are required pursuant to two distinct statutory obligations, each with its own enforcement mechanism. With regard to the container stuffing location and consolidator (stuffer), CBP believes that the “importer,” as the party that ultimately has an interest in the goods and the responsibility for causing the goods to be placed on a vessel for delivery to the United States, has the most control over the underlying transaction so the importer can require this information be received by it more than 24 hours prior to lading as part of terms and conditions of purchase

contracts. However, in response to requests from the trade, CBP will allow carriers to submit an Importer Security Filing for IE, T&E, or FROB cargo and the advance cargo declaration via the same electronic transmission. CBP also disagrees that entry should be required, with additional elements, prior to lading. CBP is not requiring that entry be made 24 hours prior to lading. There are only four data elements on the current entry (CBP Form 3461) and entry summary (CBP Form 7512) that are among the 10 additional data elements CBP deems necessary for high risk targeting enhancement under this rule. However, in response to requests from the trade, CBP will allow an importer to submit the entry or entry/entry summary data via the same electronic transmission as the Importer Security Filing. If an importer chooses to do so, transmission must be made by the party entitled to make entry pursuant to 19 U.S.C. 1484 on its own behalf or a licensed customs broker.

Comment

In the NPRM, CBP stated that “one party must aggregate and submit all required elements.” Does one party need to aggregate and submit all elements per bill of lading, for each origin port, or for each importer at all origin ports? CBP should aggregate portions of a single Importer Security Filing, linked by the bill of lading, from multiple parties (similar to the Automated Export System (AES)).

CBP Response

One party must aggregate and submit all required elements for each individual Importer Security Filing. CBP will not aggregate portions of a single Importer Security Filing because it would be overly burdensome and costly for CBP to administer such a system. However, in response to requests from the trade, CBP will allow ISF Importers to designate an agent to submit the filing on behalf of the importer. While CBP understands that some business practices may need to be altered (e.g., amendment of shipping documents) to obtain the required information at an earlier point, CBP does not anticipate that these changes will be unduly burdensome, especially given the one-year delayed compliance period and other flexibilities that CBP is providing. See the “Structured Review and Flexible Enforcement Period” section of this document for further discussion regarding the delayed compliance period and flexibilities. CBP's ATDI testing has demonstrated that, in many cases, importers were able to collect this information from manufacturers, suppliers, and shippers at an earlier point by requiring the container stuffing location and consolidator name and address be provided as part of the regular commercial documentation.

C. Public Comments; Agents

Comment

Commenters stated that CBP should only allow U.S.-based entities or Customs-Trade Partnership Against Terrorism (C-TPAT) members to act as an agent for Importer Security Filing purposes. CBP should require authorized agents, including foreign parties, to meet the standards required of customs brokers when filing the Importer Security Filing, including standards relating to security. Commenters also stated that importers should be able to designate filers with CBP and Importer Security Filings submitted by undesignated parties should be rejected. Commenters asked what the liability would be for a party who misrepresents that they are sending data on behalf of an importer.

CBP Response

CBP will not create functionality whereby an ISF Importer can authorize alternate parties with CBP to file on their behalf. Nor will CBP create functionality to document unauthorized parties. CBP does not do this in its systems for other purposes and believes that it is best for private parties to manage these types of business relationships to allow for maximum flexibility. In order to provide this functionality, CBP would need to create and maintain a system cross-referencing millions of relationships between importers and their agents. This type of functionality would be extremely costly to set up and maintain and the potential advantages of such a system do not outweigh these costs.

In response to requests from the trade, an ISF Importer may, as a business decision, designate an agent to file the Importer Security Filing on the ISF Importer's behalf. CBP is not requiring the use of an agent and the ISF Importer is ultimately responsible for the timely, accurate, and complete submission of the Importer Security Filing. In order to act as an agent for purposes of filing the Importer Security Filing, a party must obtain access to ABI or AMS. CBP disagrees that agents should be limited to U.S.-based entities or C-TPAT members. Doing so would greatly limit the flexibility of ISF Importers in selecting agents for Importer Security Filing purposes. The accuracy and timeliness of Importer Security Filings is secured by a bond. An agent can file the Importer Security Filing under the ISF Importer's bond or, if the ISF Importer does not possess a required bond, the ISF Importer may choose to designate a bonded agent to file the Importer Security Filing under the agent's bond if the agent agrees to do so in writing.

Comment

CBP should require the Importer Security Filing filer, when the filer is an agent, to furnish the importer with a copy of the Importer Security Filing submitted on the importer's behalf.

CBP Response

CBP disagrees. CBP believes that this is a matter between private parties and, therefore, is not requiring the Importer Security Filing to be shared among private parties.

Comment

Commenters asked whether an importer will be held liable if an agent experiences problems with its systems resulting in a late, incomplete, or inaccurate Importer Security Filing. Commenters also stated that agents should not be liable for any lack of compliance with vessel stow plans, container status messages, or Importer Security Filings that are submitted on behalf of another party.

CBP Response

The ISF Importer is ultimately responsible for the timely, accurate, and complete submission of the Importer Security Filing, regardless of the cause for a late, inaccurate, or incomplete filing. After analyzing the results of tests performed through ATDI and in response to requests from the trade, CBP will allow ISF Importers and carriers to use agents to submit Importer Security Filings, vessel stow plans, and container status messages. However, the ISF Importer is ultimately liable for the timely, accurate, and complete submission of the Importer Security Filing and the carrier is ultimately responsible for the timely, accurate, and complete submission of the vessel stow plan and container status messages.

Comment

Because AMS users must be licensed by the Federal Maritime Commission, this will severely limit the choices for filers, driving self filers and brokers to utilize the Automated Broker Interface.

CBP Response

CBP disagrees that AMS users must be licensed by the Federal Maritime Commission. Any party will be able to

obtain access to ABI or AMS, with CBP approval, for purposes of filing an Importer Security Filing.

Comment

CBP has proposed to require a power of attorney to file an Importer Security Filing on another's behalf, but did not specify a particular form, the required language, the length of time, or the manner in which powers of attorney must be stored. Under what authority will CBP require production of power of attorney records? Is there a penalty for not having a power of attorney on file? Will CBP allow an exemption to the power of attorney requirement for goods consigned to the military, the government, or for household/personal goods?

CBP Response

CBP is not requiring a particular form for a power of attorney for Importer Security Filing purposes. However, 19 CFR 141.32 contains an example of an acceptable general power of attorney with unlimited authority. CBP has revised the regulations under this interim final rule to require that powers of attorney must be in English. Pursuant to 19 U.S.C. 1508(a), CBP has also clarified in the regulations that powers of attorney must be retained until revoked, and revoked powers of attorney and letters of revocation must be retained for five years after the date of revocation. Finally, CBP will not allow an exemption to the power of attorney requirement for goods consigned to the military, the government, or for personal/household goods. An exemption is not merited as there is no less of a security risk associated with these shipments. CBP still requires the certainty that powers of attorney provide when parties are interacting with CBP.

D. Public Comments; Customs Business

Comment

Commenters stated that the Importer Security Filing, including providing the HTSUS number (even at the six-digit level), importer of record number, and consignee number, is “customs business.” Therefore, the Importer Security Filing should be restricted to licensed Customs brokers. Other commenters stated that classification at the 10-digit level is “customs business” and, therefore, when the Importer Security Filing and entry are filed via the same electronic transmission (unified filing), this submission constitutes “customs business.” Non-brokers should be limited to the filing of the Importer Security Filing alone.

CBP Response

“Customs business” does not involve the mere electronic transmission of data received for transmission to CBP, but does involve classification for entry purposes.

See

19 CFR 111.1. The six-digit HTSUS number is intended exclusively for ensuring cargo safety and security, and not for determining merchandise entry procedures that fall within the scope of customs business. However, a 10-digit HTSUS number is needed and is used for merchandise entry purposes and, therefore, classification at the 10-digit level is considered customs business. CBP disagrees that providing the importer of record number and consignee number falls within the definition of customs business in 19 CFR 111.1. Pursuant to this interim final rule, if the Importer Security Filing and entry or entry summary are provided via a single electronic transmission to CBP, the party making the transmission must be an importer acting on its own behalf or a licensed customs broker.

E. Public Comments; Bills of Lading

Comment

Commenters asked CBP to clarify whether the bill of lading number (house and/or master) is a required data field, and whether the house or master bill number is required. If the bill of lading number is required, CBP should only require the house bill of lading number and it should be added as an additional required data element for the Importer Security Filing. Other commenters stated that carriers may not generate bill of lading numbers early enough for an importer to submit this information for Importer Security Filing purposes. Therefore, CBP should require the bill of lading number prior to arrival in the United States rather than 24 hours prior to lading. In the alternative, CBP should require carriers to make the bill of lading number available no later than 48 hours prior to lading the vessel or CBP should allow the use of booking number in lieu of the bill of lading number. In any event, the importer should not be penalized for a late Importer Security Filing when a carrier fails to provide the bill of lading number early enough. Commenters asked whether multiple Importer Security Filings will be required when one bill of lading covers multiple shipments. Commenters also stated that CBP should allow an importer to file one Importer Security Filing for all bills of lading in a shipment where the manufacturer, country of origin, and HTSUS numbers are the same. Lastly, commenters asked how the Importer Security Filing will be handled if the goods are divided and sold in transit to at least two separate parties, resulting in two new bills of lading.

CBP Response

A bill of lading number is integral to the Importer Security Filing and therefore, must be provided with the Importer Security Filing. The bill of lading number is not a data field, but an identifier which will be provided in the header information. However, after further consideration, CBP is requiring only the number for the bill of lading at the lowest level (

i.e.

, the regular straight/simple bill of lading or house bill of lading) and not the master bill of lading number. Under existing 24 Hour Rule requirements, the bill of lading number is required for containerized cargo 24 hours prior to lading. For bulk cargo and exempted break bulk cargo, the carrier must submit the bill of lading number 24 hours prior to arrival. Under this interim final rule, for containerized cargo, the Importer Security Filing is also required 24 hours prior to lading. For break bulk cargo that is exempted for 24 Hour Rule purposes, the Importer Security Filing is required 24 hours prior to arrival. For bulk cargo, an Importer Security Filing is not required. Accordingly, the bill of lading number will be available for Importer Security Filing purposes, and has always been a part of the transaction identification. CBP understands that business processes may need to be changed to ensure that the importer, as defined for these regulations, has the bill of lading number in a timely fashion. Regarding bills of lading covering multiple shipments, CBP has the capability to accept multiple Importer Security Filings per bill of lading. CBP will issue a unique identification number for each separate, not unified, Importer Security Filing as part of the acceptance/rejection acknowledgment response. Modification of a particular Importer Security Filing will be possible using the unique identification number. Under this interim final rule, one Importer Security Filing can satisfy multiple bills of lading. However, the manufacturer (or supplier), country of origin, and commodity HTSUS number elements must be linked to one another at the line item level. Lastly, when a shipment is divided into a new or multiple new shipments, each with its own house bill of lading number, the original Importer Security Filing will need to be amended. In addition, a new Importer Security Filing will be required for each new bill of lading number.

F. Public Comments; Required Elements

1. Manufacturer (or Supplier)

Comment

Commenters stated that, in some cases, there may be no manufacturer or the manufacturer may not be known. This may be the case for personal effects entered on a CBP Form 3299, for antiques, or when the importer purchases goods from a party who is not willing to provide the identity of their supplier due to business confidentiality concerns. Commenters also stated that the MID should be accepted for the manufacturer (or supplier). If the MID is not accepted, CBP should set up a registration system like the U.S. Food and Drug Administration (FDA) did for bioterrorism purposes. Commenters asked which law, rule, or regulation CBP was referring to in the NPRM which states that the name and address of the manufacturer (or supplier) that is currently required by the import laws, rules, and regulations of the United States may be provided. Commenters stated that the supplier of the goods may not be located in the “country from which the goods are leaving” and, therefore, this element should be changed accordingly. Commenters stated that the manufacturer (or supplier) requirements are inconsistent with merchandise produced under Outward Processing Arrangements (OPAs), for which importers must construct the MID based on the origin conferring manufacturer. Commenters asked which address should be used when a manufacturer has more than one address, including a corporate address.

CBP Response

CBP recognizes that, in some cases, the manufacturer's identity may be unavailable to the party responsible for filing the Importer Security Filing. Accordingly, CBP is requiring the identity of the manufacturer

or the supplier of the finished goods

if the actual manufacturer is unknown. CBP disagrees that the MID should be accepted for the manufacturer (or supplier). In general, the MID does not include the complete address of the manufacturer. CBP believes that the complete manufacturer's (or supplier's) name and address is a critical piece of information to effectively target high risk cargo. Since the current MID has limited targeting utility, CBP will not accept the current MID as an alternative to the complete name and address of the manufacturer. However, CBP will allow the trade to provide widely recognized commercially accepted identification numbers such as Dun and Bradstreet Data Universal Numbering System (DUNS) numbers as an alternative. When referring to previously existing laws and regulations, CBP is referring to title 19 of the United States Code Annotated and title 19 of the Code of Federal Regulations. CBP agrees that the supplier may not be located in the same country where the goods are leaving. In this interim final rule, CBP clarifies that this is the party supplying the finished goods in the country from which the goods are leaving. In many instances, this party will be located in the country from which the goods are leaving. In instances where the MID for the origin conferring manufacturer is currently supplied for entry purposes, the identity for this party should be provided in the Importer Security Filing. When a manufacturer has more than one address, CBP would like the address where the goods were actually manufactured. CBP understands that, in certain cases, this address may not be known to the ISF Importer and, therefore, will accept the corporate address for the manufacturer or supplier.

2. Buyer

Comment

The buyer's identity may not be available at the time of shipment and, when available, may not be applicable to each individual carton in a shipment. This data element, as well as the ship to party, should not be required prior to shipment, but at the time of the filing of the entry. What party's identity should be provided for multi-tier transactions, “sold in shipments,” and shipments involving a buying agent? What if merchandise is sold in transit?

CBP Response

The Importer Security Filing elements must be reported at the lowest bill of lading level. At this level, the buyer's identity should be applicable to the entire shipment. If the buyer's name and address is not available at the time of shipment, the identity of the owner, consignee, or the buyer's agent should be provided instead on the Importer Security Filing. For “buying agent” transactions, the buying agent should be provided for the buyer element and the party who sold the goods to the buying agent should be provided for the seller element. If, after the filing is submitted and before the goods enter the limits of a port in the United States, any of the information submitted in an Importer Security Filing changes or more accurate information becomes available, including changes to the buyer's identity, the ISF Importer must update the filing.

3. Ship to Party

Comment

Commenters stated that the ship to party should not be required because this party will be the importer of record. In addition, the physical location where the container will arrive does not pose a security risk as much as who is the party that caused the importation to the United States. If the ship to party is required, CBP should accept the identity of the importer or consignee as indicated on the bill of lading when the ship to party is unknown when the Importer Security Filing is submitted. Commenters also stated that the ship to party should be kept confidential because it could be used by competitors. Commenters also asked whether the “ship to name” needs to be the name of a legal business entity. Can the importer transmit the name of its distribution center, even though the distribution center is not a separate legal entity in its own right? Will CBP accept Facilities Information and Resources Management System (FIRMS) codes in lieu of the name and address for the ship to party? Lastly, commenters asked which address should be used when a ship to party has more than one address, including a corporate address. Does a container freight station constitute the first ship to party?

CBP Response

CBP has determined, as the result of internal and external analysis, including analysis of ATDI testing, that the ship to party's identity and address will allow CBP to more effectively assess the risk of cargo destined for the United States. In some instances, the ship to party may also be the importer of record or consignee. However, this is not always the case. In addition, the importer of record's and consignee's corporate offices usually differ from the actual delivery address which is required for this element. Therefore, both parties' identities are necessary for effective risk assessment. If the party scheduled to physically receive the goods after the goods will be released from CBP custody is unknown 24 hours prior to lading (e.g., “to order” shipments), the filer must provide the identity of the facility where the goods will be unladen. The filer must update this element if, after the filing is submitted and before the goods enter the limits of a port in the United States, the party scheduled to physically receive the goods becomes known. All elements of the Importer Security Filing, including

the ship to party information, will be kept confidential as per the statutory requirements within the SAFE Port Act of 2006 and section 343(a) of the Trade Act of 2002. The ISF Importer must identify the ship to party, regardless of whether that party is a separate legal entity. However, CBP will accept a widely recognized commercially accepted identification number such as the DUNS number or FIRMS code, when applicable, for the ship to party. The

first

deliver-to party scheduled to physically receive the goods after the goods have been released from customs custody must be provided. A container freight station can be the ship to party if it meets the parameters of the definition in this rule that it is the first place of delivery after the goods have been released from customs custody.

4. Container Stuffing Location

Comment

Commenters stated that importers do not know the container stuffing location, except in the case of repetitive movements. Commenters also stated that providing the container stuffing location would be redundant in cases where shipments are stuffed by the manufacturer. Commenters asked which location should be reported when multiple containers are included on one bill of lading, and thus one Importer Security Filing contains multiple containers stuffed in multiple locations. Also, in some cases, there may be multiple stuffing locations, such as for “Less than Container Load” (LCL) shipments. Commenters also stated that CBP should accept the “scheduled” stuffing location in lieu of the actual stuffing location because the actual location cannot be confirmed until stuffing is completed, particularly in cases involving the use of a container freight station. The container stuffing location may change at the last minute for legitimate reasons. Lastly, commenters asked CBP to define “ship ready” with regard to container stuffing location and consolidator (stuffer) for break bulk cargo.

CBP Response

If an ISF Importer does not know an element, including container stuffing location, this party must take steps necessary to obtain the information. Where the ISF Importer receives any of the required information, including container stuffing location, from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, that party acquired the information, and whether and how the importer is able to verify the information. If the container is sealed at the manufacturer or factory facility, as is the case for a factory load, this location should be provided for the container stuffing location. CBP is aware that the same entity may be provided for more than one element. In cases where the consolidator has subcontracted out, or arranged a third party to do the actual stuffing, the name and address of the party at whose location the container was stuffed should be provided. When a container is stuffed at more than one location and/or more than one container is on a single bill of lading, all of the stuffing locations for the goods listed on the bill of lading must be provided. However, an ISF Importer is not required to submit container numbers and, when container numbers are reported, an ISF Importer is not required to report which container was stuffed at which location. CBP agrees that the “scheduled” stuffing location should be accepted. The ISF Importer is required to report the container stuffing location 24 hours prior to lading based on the ISF Importer's knowledge at that time. However, the ISF Importer must update the filing if, after the filing is submitted and before the goods enter the limits of a port in the United States, any of the information submitted changes or more accurate information, including container stuffing location, becomes available. Regarding break bulk cargo, break bulk cargo is made “ship ready” when the cargo is palletized, lashed, wrapped, or otherwise prepared to be laden on a vessel.

5. Consolidator (Stuffer)

Comment

The consolidator (stuffer) element should only be required when a container is stuffed by a consolidator because the container stuffing location already spells out the location where the physical container will be stuffed.

CBP Response

CBP disagrees with the comment that the consolidator (stuffer) element should be conditional. CBP is aware that the same entity may be provided for more than one element. If an element is not provided, CBP would have no way of knowing whether the element is not provided because the same information is provided for another element or because the ISF Importer merely failed to provide the information. In addition, when the same information is provided for more than one element, the additional burden on the trade should be minimal.

Comment

The “last known” consolidator should be required for the consolidator (stuffer) element.

CBP Response

Even if there are multiple stuffing locations, there should only be one party per bill of lading who stuffed the container or arranged for the stuffing of the container.

6. Importer of Record Number/FTZ Applicant Identification Number

Comment

The importer of record number is not always known. For example, what number should be provided for household goods and personal effects where a foreign party without one of the required unique identification numbers is importing their own goods?

CBP Response

The ISF Importer must submit the IRS number, EIN, SSN, or CBP assigned number of the entity liable for payment of all duties and responsible for meeting all statutory and regulatory requirements incurred as a result of importation. For goods intended to be delivered to an FTZ, the IRS number, EIN, SSN, or CBP assigned number of the party filing the FTZ documentation with CBP must be provided. If this party does not have an IRS number, EIN, SSN, or CBP assigned number when the Importer Security Filing is submitted, this party must obtain one. For household goods and personal effects where a foreign party without one of the required unique identification numbers is importing their own goods, the ISF Importer may provide the importer of record's passport number, country of issuance, and date of birth.

Comment

The importer of record number should not be required prior to shipment, but at the time of the filing of the entry.

CBP Response

CBP disagrees. In order for CBP to effectively target cargo before it is loaded, the Importer Security Filing, including the importer of record number or FTZ applicant identification number, must be received by CBP 24 hours prior to lading (any time prior to lading for FROB). CBP notes that section 203 of the SAFE Port Act requires that this information be provided prior to lading of cargo at foreign seaports.

Comment

The importer of record may not always be the party responsible for

filing the Importer Security Filing and, therefore, CBP should clarify that penalties and other liabilities will be applicable to the party required to file the Importer Security Filing pursuant to proposed 19 CFR 149.1.

CBP Response

CBP recognizes that the importer of record may not always be the party responsible for filing the Importer Security Filing. The ISF Importer is required to post their bond to secure the timely, accurate, and complete Importer Security Filing. When necessary, CBP will issue penalties and claims for liquidated damages against that party.

7. Consignee Number(s)

Comment

The consignee number(s) may not be known prior to shipment from overseas. What should be submitted for the consignee number(s) when a shipment cannot be consigned to the importer at the time of filing? For example, some shipments are consigned to a factory or a vendor's negotiating bank. What number should be provided for household goods and personal effects where a foreign party without one of the required unique identification numbers is importing their own goods?

CBP Response

CBP understands that business practices may need to change in order for the ISF Importer to determine who the consignee in the United States is for a shipment 24 hours prior to lading. For example, for shipments that are consigned to the importer, a factory, or vendor's negotiating bank, where those parties will not be the actual consignee if the goods are not consigned before arrival in the United States, the ISF Importer may need to designate a warehouse in the United States to receive the goods and, therefore, to be listed as the consignee. For household goods and personal effects where a foreign party without one of the required unique identification numbers is importing their own goods, the ISF Importer may provide the importer of record's passport number, country of issuance, and date of birth.

Comment

Can the unique identification number for a nominal consignee be provided for the consignee number element?

CBP Response

Yes, the unique identification number for a nominal consignee may be provided for the consignee number(s) element.

Comment

CBP should accept the name and address of the consignee in lieu of the consignee number because of the sensitive nature of the consignee number.

CBP Response

CBP disagrees. Based on external and internal analysis, CBP has determined that the consignee number will provide more visibility into the parties involved in a transaction than the name and address.

Comment

CBP should allow the use of the ACE ID or other universal participating government agency (PGA) identifiers.

CBP Response

CBP disagrees because these identifiers do not currently exist in the CBP systems. CBP will continue to explore the potential use of the ACE ID and PGA identifiers in the future and as ACE is developed.

Comment

The consignee number(s) element should be consistent with the party submitted to CBP on the CBP Form 3461 pursuant to 19 CFR 142.3(a)(6).

CBP Response

The party required for the consignee number(s) element is the same party provided on the CBP Form 3461.

8. Country of Origin

Comment

The importer may not have direct knowledge of the country of origin.

CBP Response

Where the ISF Importer receives any of the information from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, the ISF Importer acquired such information, and whether and how that party is able to verify this information. Where that party is not reasonably able to verify such information, CBP will permit the party to electronically present the information on the basis of what the party reasonably believes to be true.

9. Commodity HTSUS Number

Comment

The precise manifest description should be accepted in lieu of the HTSUS number. The ISF Importer may lack the expertise to classify merchandise and/or the ISF Importer may not know the HTSUS number prior to lading. If CBP does require the HTSUS number, the HTSUS number should be limited to the four-digit level because the four-digit number provides sufficient information to properly assess risk factors.

CBP Response

CBP disagrees. Based on external and internal analysis, CBP has determined that the six-digit HTSUS number will provide more visibility into cargo imported into the United States than the four-digit HTSUS number or a textual description because the six-digit number provides a more specific classification of the cargo. Furthermore, the tariff schedule is harmonized internationally to the six-digit level. If an ISF Importer does not know an element that is required pursuant to the regulations, including the HTSUS number at the six-digit level, the ISF Importer must take steps necessary to obtain the information. CBP recognizes that, for most importers, this information is known well before the placement of the order for their goods because of the need to determine duty cost and admissibility status prior to finalizing the purchase contract or shipment contract.

Comment

CBP should allow the submission of the 10-digit HTSUS code regardless of whether the Importer Security Filing is combined with the entry. The HTSUS number is subject to change (e.g., based on the quota fill status at the date of entry).

CBP Response

CBP agrees. While CBP is not requiring the HTSUS number at the 10-digit level unless the Importer Security Filing is submitted via the same electronic transmission as entry or entry/entry summary, CBP will accept the HTSUS number at the 10-digit level if the Importer Security Filing is submitted in a separate transmission. The ISF Importer must update the filing if, after the filing is submitted and before the goods enter the limits of a port in the United States, any of the information submitted changes or more accurate information, including HTSUS number, becomes available.

Comment

Will CBP compare the HTSUS data submitted in the Importer Security Filing with the HTSUS data used at entry?

CBP Response

Yes. CBP will use the information available, including entry data, to

analyze and assess risk and to validate Importer Security Filing data.

Comment

The HTSUS and country of origin do not have any security value to CBP. In addition, this information is already required under the 24 Hour Rule.

CBP Response

CBP is requiring this information pursuant to Section 203 of the SAFE Port Act, which requires the electronic transmission prior to lading of additional data elements,

including appropriate security elements of entry data,

as determined by the Secretary of Homeland Security. Based on external and internal analysis, CBP has determined that the HTSUS and country of origin will allow CBP to more accurately assess risk. CBP is aware that some information is also provided at other times and by other parties, such as for entry purposes on CBP Forms 3461 and 7501. However, this information is often submitted after the cargo departs on a vessel destined for the United States and, in many cases, after the cargo arrives in the United States. By collecting this information at an earlier point, CBP will be able to more effectively target cargo prior to it being laden on a vessel at a foreign port and prior to its arrival in the United States. In addition, CBP is collecting supply chain information from more than one party in order to more effectively validate the information.

Comment

Can an importer provide a single HTSUS number for multiple parts when the number is the same at the six-digit level (i.e., as reported on the CBP Form 7501)?

CBP Response

The HTSUS number is required to be provided to the six-digit level and, therefore, a single HTSUS number may be provided for multiple parts when the numbers are the same at the six-digit level.

Comment

Carriers are unable to provide the HTSUS number because they do not see the invoice details. The six-digit HTSUS number should be an optional element when a carrier submits an Importer Security Filing for FROB, IE, and T&E cargo as it is for manifest filings for U.S. import cargo. The precise cargo description should be accepted in lieu of the HTSUS number.

CBP Response

CBP disagrees. The six-digit HTSUS number is sometimes provided by members of the trade community on T&E and IE in-bond movements. CBP understands that, in some cases, business practices may have to be altered to obtain the required information in a timely fashion (e.g., requiring the information on commercial documents).

10. Booking Party

Comment

The definition of the booking party does not meet commercial practices because the carrier may not know the party “paying for the transportation of the goods” at the time of filing and there may be more than one party that is paying for the transportation. CBP should amend the definition of this element to be “the party who initiates the reservation of the cargo space for the shipment.” In addition, the booking party should only be required when it is available to the carrier.

CBP Response

In response to comments and in an effort to align this element with commercial practices, CBP has changed the definition for booking party to be “the party who initiates the reservation of the cargo space for the shipment.”

11. Foreign Port of Unlading

Comment

CBP should accept Bureau of Census Schedule K port codes for the foreign port of unlading element. When designating a source for port codes, CBP should consider that the foreign port of unlading could be an air or land port for cargo that is transferred to another mode.

CBP Response

CBP agrees. CBP will accept Bureau of Census Schedule K port codes for the foreign port of unlading element.

12. Place of Delivery

Comment

Is the “place of delivery” the place of delivery under the terms of the carrier's contract of carriage? CBP should accept port codes in lieu of city codes for this element.

CBP Response

The place of delivery is the foreign location where the carrier's responsibility for the transport of the goods terminates. CBP will allow the use of UN Locodes or Schedule K codes, when applicable, for this element.

G. Public Comments; Technical Issues

Comment

CBP should include the actual data fields that will need to be submitted in the interim final rule. CBP should establish a guide for developers that will include sample record sets for different business scenarios. A test system and a technical FAQ should be made available to developers.

CBP Response

CBP has amended the guides for developers, including the CATAIR, CAMIR, and X.12 transaction messages, providing the technical requirements necessary for submitting Importer Security Filings. These documents include the actual data fields, and have been posted to the “Automated Systems” section of the CBP Web site. An electronic FAQ will also be posted to the CBP Web site. In addition, the ability to submit data to a test system and receive responses will be provided.

Comments

CBP should work with the trade to identify the mechanisms that are needed for all parties to manage the Importer Security Filing. Importers should receive a timely confirmation message, including a unique identification number, indicating that the Importer Security Filing has been received and accepted by CBP (or rejected listing errors). Unique identifiers should also be created for amendments and deletions.

CBP Response

CBP will send a response message to the Importer Security Filing filer indicating whether an Importer Security Filing has been accepted or rejected by CBP's systems. The response message will contain a unique number generated by CBP. The ISF Importer may choose to share this Importer Security Filing number with other parties. However, CBP will not issue a new unique identifier when an Importer Security Filing is amended or deleted.

Comment

How will a carrier validate that an Importer Security Filing has been filed? Carriers should be notified through AMS. The filer should also be able to identify additional parties to be notified of the acknowledgement message.

CBP Response

AMS creates notifications of the status of the bill that go back to the filer and any other parties nominated on the bill to receive such notification. CBP will notify the filer of the bill of lading that

an Importer Security Filing has been received for the bill of lading through this process.

Comment

How long will carrier submissions remain in the CBP data system without being reconciled with Importer Security Filing submissions?

CBP Response

The carrier's advance cargo declaration is submitted pursuant to a different regulatory requirement and is not dependent upon the submission of Importer Security Filings.

Comment

How must the Importer Security Filings, vessel stow plans, and container status messages be transmitted to CBP? The CAMIR should be modified accordingly.

CBP Response

Importer Security Filings, stow plans, and container status messages (CSMs) must be submitted via a CBP-approved electronic interchange system. The current approved electronic interchange systems for Importer Security Filings are the vessel AMS and ABI. CBP has re-evaluated the electronic interchange systems that will best allow the trade to submit vessel stow plans and container status messages and has determined that stow plans must be submitted through vessel AMS, secure file transfer protocol (sFTP), or email, and CSMs may be submitted through sFTP. CBP will publish a notice in the

Federal Register

if different or additional electronic data interchange systems are approved in the future. CBP has amended the CATAIR, CAMIR, and X.12 transaction messages, providing the technical requirements necessary for submitting Importer Security Filings. These documents have been posted to the “Automated Systems” section of the CBP Web site.

Comment

The Importer Security Filing should be deemed to have taken place upon submission, not CBP receipt.

CBP Response

CBP agrees. This provision of the regulatory text has been changed accordingly. In the absence of specific evidence to the contrary, however, the time of CBP's receipt of the Importer Security Filing will be evidence of the time of submission by the filer. In response to requests from the trade, CBP will transmit an acknowledgement to the filer to confirm that CBP has received an Importer Security Filing. CBP will publish FAQs regarding protocols for when an approved electronic interchange system is experiencing technical difficulties (e.g., for scheduled maintenance).

Comment

Importers may not possess the technology to transmit these data directly to CBP.

CBP Response

If an ISF Importer does not possess the technology to transmit the Importer Security Filing data to CBP, the importer can either obtain the necessary technology or use an agent to submit the Importer Security Filing on the ISF Importer's behalf.

Comment

CBP should allow a filer to initially submit a “shell record” of partial Importer Security Filing data that can be subsequently amended by multiple parties.

CBP Response

CBP disagrees. A shell record would not serve any targeting or risk assessment purposes. Records of this type that could subsequently be amended by multiple parties would create numerous problems, including a lack of finality (CBP would not know when the final Importer Security Filing information has been submitted and/or amended), security and privacy issues (who will determine which parties can amend which information), and cost (such a system would be expensive to develop and maintain). The ISF Importer is ultimately responsible for the timely, accurate, and complete submission of the Importer Security Filing. In response to requests from the trade, an ISF Importer can designate an agent to submit the filing on behalf of the ISF Importer. While CBP understands that some business practices may need to be altered to obtain the required information at an earlier point, CBP does not anticipate that these changes will be unduly burdensome.

Comment

Importers should be allowed a review period before the Importer Security Filing must be filed if it is filed by an agent.

CBP Response

The Importer Security Filing must be filed no later than 24 hours prior to lading (any time prior to lading for FROB). However, see the “Structured Review and Flexible Enforcement Period” section of this document for flexibilities related to timing for certain Importer Security Filing elements. If an ISF Importer chooses to use an agent, the ISF Importer may choose to include a “review period” as part of their contract with their agent.

Comment

CBP should transmit an electronic acknowledgement to the filer after an Importer Security Filing is received. This acknowledgement should include a unique number which can be used by other parties to verify that an Importer Security Filing has been filed. The importer should be able to designate multiple parties to receive the acknowledgement. Parties should also be able to query previously submitted Importer Security Filings.

CBP Response

CBP will transmit an electronic acknowledgement to the filer only when CBP receives an Importer Security Filing. The acknowledgement will include a unique identification number. This number cannot be used to perform a query in ABI or AMS. However, the party who submits the advance manifest information and any notify party on the bill of lading in AMS will receive all status notifications posted to that bill, including the notification that an Importer Security Filing was accepted for the bill of lading.

Comment

What will the procedures be when the Importer Security Filing system is down? Will CBP's systems be able to handle the exponential increase in data that will result from this rule?

CBP Response

CBP has planned for the expected increase of data that will result from this rule. However, CBP will publish FAQs regarding protocols for when an approved electronic interchange system is experiencing technical difficulties (e.g., for scheduled maintenance).

Comment

The technical detail of the construct of the Importer Security Filing should be developed consistent with CATAIR and CAMIR standards. CBP should immediately release, and accept additional comments on, the data formats for the new requirements, including templates and instructions relating to the following: data type for each element (alphanumeric, numeric, etc.), length for each element, address information format, element definitions, hierarchy of message, and what validations for existing data will be performed for these filings.

CBP Response

CBP has amended the CATAIR, CAMIR, and X.12 transaction messages, providing the technical requirements necessary for submitting Importer Security Filings. These documents have been posted to the “Automated Systems” section of the CBP Web site. CBP disagrees that any further notice and comment is necessary for technical changes.

Comment

CBP should codify all elements that require a name and address and assign a unique identification number to each entity, or CBP should accept widely recognized commercially acceptable identification numbers such as DUNS numbers in lieu of the name and address.

CBP Response

CBP disagrees that a unique identifier number should be assigned to each party listed in the Importer Security Filing because, at this time, CBP is not technologically prepared to create such a system and such a system would be unduly burdensome and expensive. However, CBP will continue to explore the potential development and use of the ACE ID in the future as ACE is developed. In response to requests from the trade, CBP has changed the proposal in this interim final rule so that widely recognized commercially accepted identification numbers (such as DUNS numbers) will be accepted in lieu of the name and address.

Comment

CBP should provide a source, such as United Nations Location Codes (UN Locodes), for city codes that are required for the “place of delivery” element. An ABI query would be helpful to maintain the list as updates are made to add or delete items on the list.

CBP Response

CBP agrees and, where applicable, such as “place of delivery,” CBP has adopted the use of UN Locodes and Schedule K codes. However, CBP will not provide a table of codes in ABI or AMS that the trade can query because these are available from other sources.

9

9

UN Locodes are available on the United Nations Web site at

http://www.unece.org/cefact/codesfortrade/codes_index.htm

. Schedule K codes are available on the U.S. Army Corps of Engineers Web site at

http://www.iwr.usace.army.mil/NDC/wcsc/scheduleK/schedulek.htm

.

Comment

CBP should adopt standards for address information, such as the use of Global Location Number (GLN) standards. Such standards should be harmonized on a global basis.

CBP Response

In response to requests from the trade, CBP has changed the regulations, as proposed, so that widely recognized commercially accepted identification numbers (such as DUNS numbers) will be accepted in lieu of the name and address. At this time, however, CBP will not accept the GLN because it is unclear whether the GLN is a widely recognized and commercially accepted number. However, CBP will continue to work with the trade to evaluate existing identification numbers such as the GLN to determine which of these are appropriate for Importer Security Filing purposes. CBP will also continue to explore the potential development and use of the ACE ID in the future as ACE is developed. CBP will continue to update the trade regarding acceptable numbers in the form of FAQs, postings on the CBP Web site, and other outreach to the trade. The technical requirements necessary for submitting Importer Security Filings, including guidance relating to the submission of address information, has been added to the CATAIR, CAMIR, and X.12 transaction messages. These documents have been posted to the “Automated Systems” section of the CBP Web site.

H. Public Comments; Update and Withdrawal of Importer Security Filing

Comment

The requirement that the party who initially filed the Importer Security Filing must update the filing does not take into consideration the dynamic nature of international trade. For example, goods may be sold in transit. In addition, the SAFE Port Act and the Trade Act of 2002 do not contemplate an ongoing duty to update information on a post loading basis. Any authorized party should be able to update the filing.

CBP Response

The ISF Importer, as the party who causes the goods to enter the limits of a port in the United States, submits (or uses an agent to submit) the Importer Security Filing, and posts their bond. Therefore, it is ultimately responsible for updating the Importer Security Filing if, after the filing is submitted and before the goods enter the limits of a port in the United States, any of the information submitted changes or more accurate information becomes available. However, that party may use an agent to update the Importer Security Filing. If goods are sold in transit, the original Importer Security Filing filer must notify CBP that the goods have been sold, including the party to whom the goods have been sold.

Comment

The final importer should be able to see and update the Importer Security Filing.

CBP Response

CBP disagrees. Importers will not be able to access specific Importer Security Filing elements in CBP systems. Such functionality would be too costly and raises security concerns. If an ISF Importer wants to access Importer Security Filings that are submitted on their behalf by an agent, the ISF Importer should obtain the information from their agent.

Comment

How will a filer designate an update so that it is applied to the correct Importer Security Filing, particularly in the case where there are multiple filings for a single bill of lading?

CBP Response

CBP will issue a CBP-generated unique identifier for each Importer Security Filing it receives. That unique number can be used by the Importer Security Filing filer to amend an Importer Security Filing.

Comment

What if cargo is diverted while in transit, due to shifting inventory/distribution needs? Will an Importer Security Filing need to be updated if a shipment is split after the initial Importer Security Filing has been filed?

CBP Response

Pursuant to this interim final rule, the Importer Security Filing must be updated if, after the filing and before the goods enter the limits of a port in the United States, there are changes to the information filed, including when cargo is diverted into a shipment for which a different number of elements is required (5 elements to 10 elements or 10 elements to 5 elements). In addition, when a shipment is split resulting in (a) new bill of lading number(s), a new Importer Security Filing must be filed for each new bill of lading because each Importer Security Filing is associated with a bill of lading.

Comment

Does an Importer Security Filing need to be updated if a shipment is rolled to a different vessel?

CBP Response

If the bill of lading number remains the same, a new Importer Security Filing is not required, nor is an amendment required. However, if a new bill of lading is issued or the bill number changes, a new Importer Security Filing must be filed.

Comment

If a party reported on an Importer Security Filing remains the same, but the address for that party changes, is an amendment required?

CBP Response

The Importer Security Filing must be amended if any of the information submitted, including the address of a party, changes or more accurate information becomes available.

Comment

The NPRM states that an Importer Security Filing must be amended if there is a change “before the goods enter the limits of a port in the United States.” Does “port” refer to the first port of arrival or the port of discharge or the port of destination on the ocean bill of lading?

CBP Response

The Importer Security Filing must be amended if there is a change before the goods enter the limits of a port in the United States. For goods that will be unladen in the United States, the Importer Security Filing must be updated if there is a change before the goods enter the port of discharge.

Comment

When an Importer Security Filing is submitted in the same electronic transmission as entry, will both need to be amended independently?

CBP Response

When an Importer Security Filing is initially submitted in the same electronic transmission as entry, both can be amended via the same electronic transmission. CBP has amended the CATAIR, CAMIR, and X.12 transaction messages, providing the technical requirements necessary for amending Importer Security Filings. These documents have been posted to the “Automated Systems” section of the CBP Web site. CBP will continue to conduct outreach with the trade, fulfilling its regulatory and statutory obligations, both during the delayed compliance period and thereafter, via FAQs, postings on the CBP Web site, and other outreach.

Comment

CBP should accept the entry information submitted on CBP Forms 3461, 7501, and 214 as an update of the Importer Security Filing.

CBP Response

CBP disagrees. Entry information will not be accepted in lieu of an Importer Security Filing update. Entry is governed by a different statutory provision, 19 U.S.C. 1484, and serves a much different function. It is a well settled area of law that has distinct limitations as to who may make entry, and what constitutes the act of making entry on another's behalf, with its own discrete regulations and limitations. Furthermore, most of the Importer Security Filing elements are not current entry data elements nor is the totality of what constitutes an entry necessarily compatible with what constitutes an Importer Security Filing.

I. Public Comments; In-Bond Shipments

Comment

For shipments consisting entirely of FROB and shipments intended to be transported in-bond as an IE or a T&E, does the IE or T&E in-bond need to be created before an Importer Security Filing is submitted?

CBP Response

No. Parties are not required to file an in-bond document prior to submission of an Importer Security Filing.

Comment

The submission of an Importer Security Filing consisting of 10 elements should serve as the request for permission to convert a shipment from an IE or T&E shipment into a shipment that will be entered into the United States. If CBP declines to accept the full Importer Security Filing as the request for permission, permission should be required from the port director of the original port of entry or the port of entry filing. How will CBP indicate that permission has been granted?

CBP Response

The ISF Importer must submit the complete Importer Security Filing to CBP consisting of 10 elements as soon as a decision is made to change the disposition of the cargo. However, CBP disagrees that this submission should serve as the request for permission to convert an IE or T&E shipment into a shipment that will be entered into the United States. Instead, the party wishing to divert the cargo, must present the request to CBP in writing at the original port of unlading and CBP will indicate permission on the documentation.

Comment

CBP should clarify the application of proposed 19 CFR 18.5, which would require permission to “divert” in-bond shipments regarding IE in-bond shipment since IE shipments are retained within the port of unlading. Will affirmative permission be required for such changes and, if so, what is the purpose of such permission and on what basis would CBP refuse permission?

CBP Response

For in-bond shipments which, at the time of transmission of the Importer Security Filing are intended to be entered as an IE or T&E shipment, permission to divert the in-bond movement to a port other than the listed port of destination or export or t

This text is long and has been trimmed here. Open the source document for the complete record.

This is a copy of a public record, reproduced as it was published. It is not legal advice, and it may not be the version a court would rely on. Check the official source before you cite it.

A word about cookies

We need a few to keep you signed in and the library working. The rest help us see which pages people use and where they get stuck. They stay off unless you say yes.