ITDS Annual Report Lists ITDS Data Elements for Entry/Entry Summary
The ITDS Board has submitted its annual report on the International Trade Data System to Congress, as required by the 2006 SAFE Port Act.1 The report includes updates on the status of ITDS implementation and the status of the Automated Commercial Environment within U.S. Customs and Border Protection, among other issues.
Sign up for a free preview to unlock the rest of this article
Communications Daily is required reading for senior executives at top telecom corporations, law firms, lobbying organizations, associations and government agencies (including the FCC). Join them today!
(ITDS, which is a part of ACE, is an interagency effort to eliminate redundant reporting by creating a "single-window" system, replacing multiple filings (often on paper) with a single electronic filing. Relevant data would be distributed electronically to the appropriate participating government agencies (PGAs), providing them with the ability to process that data electronically.)
Highlights of the report relating to the harmonization of PGA data requirements include the following (see future issues of ITT for further details on the report):
ITDS Data Set Listed, Should be "Finalized" for Reporting Messages This Year
The ITDS Standard Data Set (SDS) is a comprehensive list of the various data elements required by government agencies with a role in the import/export process.
Over the past year, work in harmonizing this data set was accelerated. By the end of calendar 2009, the data required by 26 agencies for the major import processes (entry, entry summary, manifest) should be specified to the detail necessary for adding that data to the appropriate reporting messages. Draft additions to those messages should also be prepared by that time.
Highlights of "Entry/Entry Summary" Standard Data Set
The report lists the ITDS Standard Set Data (SDS) for entry/entry summary. Note that it is unlikely that an entry/entry summary would require all of the listed elements; the required elements would depend on the product and CBP/PGA requirements.
According to the report and government sources, the data elements not currently collected by CBP include the following (those still under review end with a triple asterisk ***):
Commodity/Shipment Information
| UCR | Unique number assigned to goods being subject to cross border transactions |
| Commodity lot number | Identification number of a production lot |
| Commodity marketed size (AMS) | Marketed size of imported commodity |
| Commodity package volume | If package is marketed by volume instead of weight, volume marked on the package |
| Commodity intended use | The intended use of the commodity |
| Commodity process type code | The process or production associated with the commodity (e.g., method of growing, pretreatment, etc. |
| Commodity net weight | The weight of the commodity, excluding all packaging |
| Commodity process date | the date on which the process associated with the commodity was performed |
| Constituent element quantity | The specific quantity of the identified constituent element contained in the shipment |
| Constituent element name | The name of the specified material within the product, e.g. asbestos or milk solids |
| Constituent element active ingredient indicator | a designation that indicates this element is an active ingredient |
(Except for the UCR, all of the above data elements are commodity sub-items.)
General
| Tracking number *** | A number assigned to track a document, package, or transaction |
| Shipment type code *** | A code to indicate that the goods are eligible to be treated in a specific manner according to customs regulation |
| AMS requested inspection date and time | The date and time the applicant requests an government agency perform a physical exam. |
| Override reason code | A code to indicate the reason for an edit bypass by CBP or the trade. |
| Bond number | A unique number used to identify the posted bond |
| Remarks code | Code representing text remarks |
Country/Place/Location
| Source country code (foreign) *** | The location code required for reporting the country source in accordance with regulations and laws |
| Source geographic location, coded (foreign) *** | Identification of the geographic location required for reporting the political subunit source in accordance with regulations and law |
| Itinerary port name (foreign) | Name of a single port of call or other location of the itinerary of a means of transport |
| Requested inspection location, coded (domestic)2 | The specific facility where the importer is requesting that the goods be inspected |
| Location of goods, coded (domestic) 2 | The location where the goods are currently being held |
| Entry port, coded (domestic) 2 | To identify the regulatory office at which goods enter the customs territory at destination |
(The last two data elements are commodity sub-items.)
Persons/Parties
| Facility, coded *** | a building or place that provides a particular service or is used for a particular industry |
(See report for list of manifest SDS elements, including those not collected by CBP.)
1The "Security and Accountability for Every Port Act of 2006" (P.L. 109-347)
2CBP already requires a code for this information, but the name of the actual port, location, etc. is not collected by CBP
(See ITT's Online Archives or 11/06/09 news, 09110605, for ITT's first summary of this report, which covers the recommendation to have basic ITDS functions implemented using ABI.
See ITT's Online Archives or 11/09/09 news, (Ref:0911910), for the second summary, which focused on ITDS funding and the use of DUNS and UPCs.
See future issues of ITT for further details on the report.)
Report to Congress on the International Trade Data System (dated September 2009) available at http://www.itds.gov/xp/itds/whats_new/
(Spiral bound copy of report filed near this article in stacks)