U.S. Customs and Border Protection

Trade Support Network

e-Manifest: Trucks

Tuesday

June 29, 2004

(Updated 11/10/2004)

r

**TABLE OF CONTENTS**

e-Manifest: Trucks (Release 4) Overview [3](#__RefHeading___Toc76348273)

Portal Presentation [6](#__RefHeading___Toc76348274)

EDI Release 3 Presentation: Carrier Accounts - MEDPID
[12](#__RefHeading___Toc76348284)

EDI Communications: Communications for EDI (MQ Series) 13

EDI Release 4 Presentation: ANSI X.12 Messages 16

EDI Release 4 Presentation: EDIFACT Messages 19

Testing and Validation 20

Questions received after the June 30th TSN presentation 23

[]{#__RefHeading___Toc76348273 .anchor}e-Manifest: Trucks (Release 4)
Overview

1\. How many countries of origin will ACE accept for one Bill?

When reporting the country of origin on a Sec. 321 shipment type there
is no restriction to the number of countries of origin that can be
reported.

> 1a. Is the country of origin always at the commodity level?
>
> Yes. You will repeat the N10 loop (or UN/EDIFACT LOC Segment, Segment
> Group 15) to enter multiple countries of origin.

2\. Will we be able to have multiple BRASS codes for one shipment?

Yes. However, if multiple C4 codes are reported for one shipment then
all C4 codes must be for the same filer and the same importer.

> 2a. How do we insure that the broker is notified?
>
> As in rail AMS, a C4 code will be recorded in the shipment record of
> the electronic manifest (Portal or via EDI). This will activate the
> BRASS process when the truck arrives at the border. An entry number
> will be taken from a bank of entry numbers that are on file. Record of
> the BRASS release will be sent to the entry filer through ABI. ACE
> will also support the printing of the BRASS receipt which will contain
> the entry number.

3\. Will an importer be able to restrict the functionality of Sec.
321\'s?

No.

4\. At what time will the broker download happen? At filing, arrival or
release?

Broker download will take place when the carrier sends any of the
following:

-   a "complete" 309; M1009 = W

-   a "complete" CUSCAR; "6" confirmation in the BGM segment with trip
    number & date of arrival

-   a 353 to identify that a trip with preliminary bills is complete;

-   a CUSREP; "6" in the BGM segment with trip number & date of arrival

-   if the carrier is using Portal, when 'Submit Manifest" is selected.

Broker download functionality allows for a copy of the shipment data to
be sent to the broker. This gives the broker/entry filer information
that will enable him to exactly match the manifest shipment record's
Shipment Control Number and piece count.

> A new broker download message will be sent if the carrier submits an
> amendment.

5\. Would it be necessary for a carrier to be both an EDIFACT or
Ansi/X12 and a Portal user?

> If you are an EDI filer you will not be required to use the ACE Secure
> Data Portal for the filing of your manifests. However you may be
> required to provide information via the ACE Secure Data Portal that
> will be used to establish your account.
>
> A carrier could transmit EDIFACT accounts management messages (MEDPID)
> and ANSI X.12 Manifests. However a carrier can not be configured in
> ACE to send EDIFACT and ANSI X.12 Manifest messages at the same time.

6\. For carriers using a freight forwarder to cross into the border,
what is the responsibility of the primary carrier in submitting manifest
information?

The carrier that is crossing the border is the entity required to submit
the manifest.

7\. Will the BRASS shipment generate a status message when processed at
CBP and sent back to a broker?

> Yes. For specific details addressing the formatting of the response to
> the entry filer see the chapter on "Line Release" in the Automated
> Broker Interface CATAIR document

8\. What if the port code needs to change?

> The carrier could report the change of the estimated U.S. first port
> of arrival by amending the trip information. The truck will be
> proceesed in ACE if he arrives at a port other than the reported U.S.
> first port of arrival. However, if the truck arrives at a port other
> than the port of arrival reported in the entry then the port code
> would need to be changed in the entry. The present process of deleting
> the entry and refiling the entry for the actual port of arrival will
> continue.

9\. Is there still an intention to phase out BRASS? Time frame?

Yes. The time frame for phasing out BRASS has yet to be announced by
CBP.

10\. Is the country of origin always at the commodity level? Will we
have to repeat the N10 loop to enter multiple countries of origins?

See answer number 1 above.

11\. Does the entry (BCS) information have to be pre-filed within the 1
hour timeframe or is it just the manifest that has to be there within
the hour?

> "Cargo data" will be required to be filed 1 hour prior to the arrival
> of the conveyance or ½ an hour prior to the arrival of the conveyance
> if it is participating in FAST. As per the FRN published on August 17,
> 2004, "Required Advance Electronic Presentation of Cargo Information:
> Compliance Dates for Truck Carriers" (69 FR 51007), as an interim
> solution CBP has approved two methods of supplying this data prior to
> the implementation of ACE Truck Manifest. These interim solutions are
> PAPS and QP/WP.
>
> When ACE Truck Manifest is available, the pre-filed "cargo data"
> required by the Trade Act of 2002 will be supplied by submission of
> the Truck Manifest.

12\. Will the SCN match the BCN? Are these two separate numbers or is
this a difference in terminology?

> In the case where Bill Control Numbers (BCN / House Bills of Lading)
> are reported, a Shipment Control Number (SCN / Master Bill of Lading
> Number) will always be required to be associated with the BCN. A SCN
> can be either a simple bill of lading, a Master bill of lading, or a
> pro-bill number.
>
> **12a. Will the SCN have to be printed on the pro-forma invoice or
> just the manifest?**
>
> SCNs and BCNs are manifest requirements. A reconciliation of an entry
> with a manifest is accomplished by these numbers matching. Whether CBP
> requires the SCN (as a simple bill of lading) or the combination of
> SCN (as a Master bill of lading) and BCN (House bill of lading) to be
> reported on the pro-forma invoice, is a CBP policy matter.
>
> **12b. Is the BCN the current PAPS number?**
>
> PAPS requires that a SCN (as a pro-bill number) be reported with a
> pre-filed entry. If a shipment contains both SCN and BCN then both
> numbers must be recorded in the manifest and entry. Neither SCN nor
> BCN can be larger than SCAC plus12 characters in length.
>
> Although in today's environment a PAPS bar code does not support both
> SCN and BCN, this will not be a limitation in ACE Truck Manifest
> because a PAPS bar code will not be required for a pre-filed PAPS
> shipment.
>
> **12c. Where does the SCN number come into play? Where does it fit in
> the process? Is it in the EDI transaction or will it be a different
> number?**
>
> The SCN will normally be used to report the Truck Carriers Pro-bill or
> Freight bill number. Alternatively, it may be used to report an ocean
> or air carrier's Simple bill or Master bill of lading if the shipment
> is to be released via an entry filed at this level. The BCN is the
> House bill of lading issued by a Transportation Intermediary (NVOCC,
> freight forwarder, de-consolidator etc.)
>
> The SCN is a combination of the issuing Carrier's SCAC code reported
> in the M1112 and the identification number assigned to the shipment in
> the M1101 (or UN/EDIFACT RFF Segment, position 0380, C506/1154).
>
> The BCN is a combination of the issuing Carriers SCAC code reported in
> the M1113 (or UN/EDIFACT DOC Segment, position 0365, C503/1366) and
> the identification number assigned to the shipment in the M1111 (or
> UN/EDIFACT DOC Segment, position 0365, C503).

13\. What happens to trucks that show up at the wrong port?

> ACE will allow the processing of the manifest.
>
> However, today's process of the entry filer having to delete the entry
> and refile the entry for the actual port of arrival will continue
> until ACE becomes the system of record for entry filing.

14\. How will P/N timing be affected?

> The effect of Food and Drug Bio-terrorism rules on truck manifest have
> not yet been determined.

15\. What is the source of the proximity cards and transponders for
FAST?

Proximity cards and transponders will be issued to drivers and carriers
under the current procedures supported in Free and Secure Trade (FAST).

> FAST trips being processed in ACE (as Preferred) will require the
> driver to present the proximity card at the Primary booth. A driver's
> proximity card ID may be supplied in a Standard Manifest in the ANSI
> X.12 data element NM109 of the 309 or 358 sets. The proximity card ID
> may be supplied in the following EDIFACT message positions.
>
> CUSCAR: NAD Segment, position 0100, C082/3039
>
> CUSREP: NAD Segment, position 0290, C082/3039
>
> PAXLST: NAD Segment, posiiton 0160, C082/3039

[]{#__RefHeading___Toc76348274 .anchor}Portal Presentation

ACE Secure Data Portal

1\. If set-up as a broker/importer, will we have access to manifest
functionality or will we need to have Portal options updated?

> No. Importers and brokers in Release 4 would only have access to a
> Carrier's Manifest if the Carrier gave them access to their ACE Secure
> Data Portal.

2\. When will the Portal be available to view on line?

> Portal Screens for Manifest filing by Trade will only be available to
> the Trade in the ACE Production environment. These screens will be
> available for the Trade during User Acceptance Testing phase which
> will begin around the end of December 2004.

3\. Will there be a verification of the C4 codes at the manifest level
and will any negative determination be sent back to the carrier?

> ACE will edit for a valid C4 code. The error message will state "C4
> Code not Valid".

4\. When is the ETA to the port required?

The Estimated Date and Estimated Time of arrival will be required with
all Standard manifests filed in ACE at time of submission.

5\. Will there be an ability in a later release perhaps, to enable a
delete message back to a broker when they have been identified
incorrectly?

> This is not being considered for Release 4 but will be forwarded to
> the planning team for consideration in a subsequent release.

6\. In a true paperless environment with BRASS, if CBP does not stamp
the entry number on the paperwork, how will the broker get the invoice?
Currently, the first time an invoice is received by the broker is after
release. How does eCP envision this working?

As in the Rail AMS environment, the Broker will receive a message via
ABI that a BRASS shipment has been released. It will be up to the
exporter, importer, carrier and/or broker to make sure that the
commercial invoice is transmitted or given to the entry filer for entry
summary processing. The broker download functionality that will be
available to carriers will only send manifest shipment details to the
entry filer. It will not have the ability to transfer commercial invoice
details to the entry filer.

7\. Will the portal accept the HAZMAT contact name and phone number?

Yes. On a manifest, this information will be required to be sent when
HAZMAT is listed. It will be reported at the commodity level in the
shipment record.

9\. If a carrier sends a transaction to ACE through an EDI message and
that information is later updated through the Portal, will ACE send
response messages through EDI?

> EDI filers will not receive ANSI X.12 355 (accept/reject) messages if
> data is entered into the Portal. However, an EDI filer that has set
> his messaging preference to EDI in their Account Profile will receive
> ANSI X.12 350 (CBP status) messages if they enter data into the
> portal. This also applies to the appropriate EDIFACT CUSRES messages.

10\. If sending EDI, where do the UN/NA codes, FDA confirmation number,
and VIN numbers need to be translated? Will this information be required
by the end of the year?

> None of these data elements are "translated".
>
> The UN/DG codes for Dangerous Goods are to be supplied in the H101
> element of the 309 set when required (or UN/EDIFACT DGS Segment,
> C234/7124 in the CUSCAR).
>
> The FDA confirmation number (Prior Notice -- PN number or data) can
> not be reported as part of the Truck Manifest at this stage. The FDA
> Freight Indicator which is a Yes/No flag is asked for at the shipment
> level.
>
> In the Portal, the VIN number is to be supplied with the conveyance
> information. The Vehicle Identification Number (VIN) is to be supplied
> in the VEH02 element of the 309 and 358 set (or UN/EDIFACT TDT Segment
> of the CUSCAR or CUSREP).
>
> The VIN number is also required if the commodity being carried is a
> vehicle. In this case the VIN is reported in the bill section of the
> 309, data element VC01 (or UN/EDIFACT CUSCAR, FTX Segment, Segment
> Group 15, C108/4440).

11\. What do you want to see in the \"state\" field for the Travel
document type when the Birth Certificate country does not contain
states?

Leave the state code blank if the Country does not have state codes.

12\. When will the driver's nationality be required?

> A driver's nationality (citizenship) will be required to be submitted
> with the Manifest. The nationality can be stored in the carrier's
> master data file for crew members. If this is done then supplying the
> appropriate "look up" code for crew member will be sufficient.
> Supplying the FAST ACE ID for a crew member will also be sufficient.
>
> **12 a. When will the passenger information be required?**
>
> Passenger information is required when there is a passenger in the
> conveyance.
>
> **12 b. If there is a change in driver on the load, what is the
> process and time allowed to get the change in information to CBP?**
>
> A manifest should be amended when it is known that the driver has
> changed. This should be done as soon as possible within the guidelines
> of CBP manifest filing rules.

13\. Does the possibility exist to update the carrier portal with any
type of electronic update capability? (i.e.. XML)

> As an XML standard CBP message has not yet been developed by the
> standards organizations, XML is not supported in Release 4. Currently
> the only EDI message for supplying crew information to a carrier's
> account is via the EDIFACT MEDPID message set. In addition a carrier
> could manually supply crew data via the ACE Secure Data Portal.

14\. Will ACE allow a carrier visibility into another carrier's portal?
If so, with what restrictions?

> It is the carrier's prerogative to grant a third party access to their
> account. If a carrier grants access to their account, there are very
> limited, restrictions available. This functionality is currently under
> further consideration. This request has been forwarded to the planning
> team for consideration in a subsequent release.

15\. Will a carrier be able to save shipper and consignee ID#\'s in
their account?

No, not in release 4. This request has been forwarded to the planning
team for consideration in a subsequent release.

16\. Can the carrier\'s account restrict certain Users to "view only"?

> No.

17\. Are we standardizing with UN numbers or will we use both UN and NA?

> The United Nations Dangerous Goods codes are being used.

18\. Change shipment type. What type of validations will occur on the
change shipment type?

> Any validations done on Brass, Sec 321.
>
> BRASS will require a valid C4 code. In addition to standard shipment
> requirements, Sec. 321 will require a value to be declared that is not
> more than 200 dollars and a Country of Origin.
>
> PAPS will require that the entry filed in ABI contains the same
> Shipment Control Number (and if applicable, Bill Control Number) as
> well as shipment quantity, as is reported in the manifest.
>
> If shipment type is changed the commodity details would need to be
> re-entered with the new associated commodity details.

19\. Who supplies the proximity cards and transponders for FAST and what
data is required?

The proximity cards are issued by the FAST enrollment centers and the
transponders are issued by Mellon Bank. For more information see details
on FAST, posted on CBP's web site.

20\. On the create standard shipment screen you must include equipment
type. Does this restrict LTL carriers from inputting only after a
shipment is assigned to a trailer? Can LTL carriers submit shipments and
then assign a trailer number at a later time?

> When using the ACE Secure Data Portal a carrier will be required to
> identify the equipment (i.e. trailer, container etc.) that the
> shipment is loaded in when creating the shipment record. If the
> shipment is moved to another piece of equipment the carrier can modify
> or amend the shipment record.
>
> A usability report has been generated to address this issue.  Future
> modifications will allow the user to more easily change equipment. 
>
> EDI filers can report "NC" in the equipment VID segment of a
> Preliminary bill then at a later time report the equipment number in
> the VID segment along with the bill number in the 358 message set (or
> for UN/EDIFACT omit Segment Group 4 of the CUSCAR ).

21\. With respect to "ultimate consignee", what directive or definition
will be used at time of release? We are looking for uniformity.

The definition of shipper & consignee is set forth in the December 5,
2003, Federal Register Notice titled "Required Advance Electronic
Presentation of Cargo Information; Final Rule (*see 68 FR 68140)*. *"
(11) The shipper's complete name and address, or identification number,
from the bill(s) of lading (for each house bill in a consolidated
shipment, the identity of the foreign vendor, supplier, manufacturer, or
other similar party is acceptable (and the address of the foreign
vendor, etc., must be a foreign address); by contrast, the identity of
the carrier, freight forwarder, consolidator, or broker, is not
acceptable; the identification number will be a unique number to be
assigned by CBP upon the implementation of the Automated Commercial
Environment); and (12) The complete name and address" of the consignee,
or identification number, from the bill(s) of lading (the consignee is
the party to whom the cargo will be delivered in the United States... ;
the identification number will be a unique number assigned by CBP upon
implementation of the Automated Commercial Environment).*

22\. On the conceptual screens I did not see where the carrier would
supply the broker filer code or routing number.

> The entry filer's filer code will be reported by adding a "Party ID
> Type" "Broker download". The filer code, port code, and if necessary
> office code, will be needed to identify the recipient of the broker
> download data.

23\. If a driver is detained at CBP, how and in what time frame will CBP
notify the carrier?

> If a hold is placed on a crew member, a message may be sent to the
> carrier informing them that the Crew member is Held. Hold messages on
> crew, equipment, conveyance and shipments are only sent after the
> arrival of the truck.
>
> Specifically, the ANSI 350, V901 segment/element contains the
> following hold/release codes:
>
> HCR Crew/passengers Held
>
> (Used for Truck Release when crew members or passengers are detained
> at the border)
>
> RCR Crew/Passengers Released
>
> (Used for Truck Release when Crew/Passengers are released)

24\. Will the broker download be a two way communication? Will entry
data elements be sent back to the carrier as needed on the manifest?

No, broker download is a one way communication- that is, carrier to
broker. This request has been forwarded to the planning team for
consideration in a subsequent release.

25\. How will an importer be assured that a carrier does not use a C4
code for unauthorized shipments to receive a quicker release?

The same as today.

26\. Are ACE IDs assigned to the truck, the driver or both?

> If a truck driver (crew), conveyance or piece of equipment is recorded
> in an ACE truck carrier's account either via EDI (MEDPID) or via the
> ACE Secure Data Portal, an ACE ID number is assigned and can be used
> in lieu of supplying truck (conveyance), driver (crew) or equipment's
> (trailer/container/etc.) details.

27\. Will differences in the C4 code data filed via a manifest and the
entry data filed by the broker be tracked?

A C-4 code is included in the manifest.  ACE will draw the next
available entry number from the filer's bank.  The entry number is then
sent to ACS and the entry filer is notified through ABI that they need
to provide an entry for this particular entry number. Tracking
differences in C4 code data and entry data will take place as in today's
environment.

> **28. If an importer does not have the ability to control the
> assignment of the C4 code, then the Importer should not be held liable
> for the compliance rating in this area.**
>
> BRASS procedures have been in place for many years.  ACE will only
> enhance the current process by allowing the C4 code to be transmitted
> to CBP in advance of the arrival of the truck thereby eliminating the
> need for the driver to present a paper bar code.

29\. Are ACE IDs assigned through the portal or are there alternatives?

If you record crew, equipment or conveyance information in your ACE
account via MEDPID or direct data entry in to the ACE Secure Data
Portal, you will be assigned an ACE ID.

30\. If a FAST manifest can be filed without a port code, will there be
functionality in a future release to do the same for PAPS shipments?
Will the broker have an ability to send the release data for PAPS
without the port code, and then the manifest arrival backload to the
broker? This would effectively put the arrival decision with the
carrier, and eliminate the B35 report at the northern border (which had
gotten out of control).

> Not at this time. However, this policy and functionality is under
> discussion within CBP.

31\. For carriers using the ACE Secure Data Portal, will identification
of the FDA requirement trigger an ACE to FDA PN for the shipment?

> No.

31a. If so, will the carrier handle the PN as if it was submitted by the
broker or will the carrier be required to print some sort of PN
Notification?

> No.

31b Would a PN notification be presented within the ACE Secure Data
Portal?

> No.

32\. It would appear that the use of PAPS barcodes are not required if
there is a transponder in the truck. Today, these transponders are being
issued in FAST carriers only, will this policy change?

PAPS bar codes will not be needed because ACE will reconcile the entry
filed in ABI with the manifest shipment record filed in Truck Manifest.
This match will take place by correlating the Shipment Control Number
(SCN) with the Bill of Lading number reported in ABI as well as the Bill
Control Number (BCN) with the House Bill of Lading number, if
applicable. This correlation is not dependent upon use of a transponder.
Moving forward CBP will expect all trucks to have a transponder.

33\. Is there a list of standard commodity descriptions and codes that
we should be using? Will weight and piece count be required for each
individual commodity, and if so, when will this information be required?

> There are no standard commodity descriptions or codes used for
> descriptions. Free text is acceptable. However, CBP has published
> specific text descriptions that can not be used such as "freight of
> all kind" etc. Weight and piece count can be supplied for each
> individual commodity in the N10 record of the 309 set (UN/EDIFACT PAC
> Segment for the piece count and MEA Segment for the weight) or you can
> report a full bill quantity with description and weight for the entire
> shipment. This information is required upon submission of your
> manifest.

[]{#__RefHeading___Toc76348284 .anchor}EDI Release 3 Presentation

Carrier Accounts - MEDPID

1\. Is HAZMAT Name and phone number included in the carrier profile?

A HAZMAT Contact person can be stored in the carriers account. However a
HAZMAT contact and phone number is required to be sent with any Standard
Manifest shipment that contains Hazardous Materials.

2\. What about casual drivers that drive for one carrier 2 days per week
and another carrier the other 3 days of the week?

> The driver is only recorded in the account of the first carrier. This
> carrier will have control over the details of the driver's record. The
> second carrier can report the ACE ID in their manifest submission.
>
> If a second carrier enters the driver's CDL that is recorded in
> another carriers account an error message will indicate that the
> driver is recorded under another carrier's account. The ACE ID number
> will be indicated in the response to the second carrier.
>
> If the first carrier removes the relationship of a driver to its
> account the driver is then eligible to be associated to another
> carriers account.
>
> Any carrier can use a driver's ACE ID on a manifest regardless of
> whether a driver is associated with any carrier account.

3\. If the conveyance is registered for FAST does it need to be sent
again in MEDPID?

No

4\. Can one driver's ACE ID be used for multiple carriers?

Multiple carriers can use the ACE ID, but only one carrier is allowed to
change the driver's information. The first carrier to enter the driver
is the owner of the driver information and is the only one that can
change the information. If the driver moves to another carrier then the
first carrier must remove the relationship of the driver to it's account
before the driver can be related to the second carrier.

5\. Will there be an equivalent MEDPID message supported in ANSI X12?

The ANSI X12 359, equivalent to MEDPID, is not currently being support
in ACE Release 3 or 4. This request has been forwarded to the planning
team for consideration in a subsequent release.

6\. How does a carrier know a crew member\'s ACE ID?

When an ACE carrier enters a driver in their account, an ACE ID is
issued and either displayed in Portal or returned in a MEDPID response.

If you try to record a driver that already exists in another carrier's
account the response will indicate that the driver is recorded in
another carrier's account however the drivers ACE ID will be returned to
the carrier.

If a carrier has registered a driver in their account and the driver
subsequently becomes a FAST driver the carrier will be able to see the
driver in their Portal Account but will be unable to edit the driver's
information via either EDI or the Portal. Updates would need to be made
via existing FAST procedures.

If a carrier attempts to record an existing FAST driver in their account
the carrier will be notified that the driver is a FAST driver, the
attempt would be rejected however the drivers ACE ID will be returned to
the carrier.

7\. Is the ACE ID and the FAST ID the same number or can they be
different numbers?

FAST IDs for Shippers, Consignees and Importers of Record are different
than ACE IDs even though the FAST ID is referred to as an ACE ID in the
EDIFACT CUSCAR Implementation Guide

8\. Does CBP update the information for FAST approved drivers?

Data on drivers that are enrolled in FAST will be migrated to ACE and
frequently updated. The FAST driver ID can be used in a Standard
Manifest.

> The driver is responsible for notifying CBP of any changes to their
> current data including proof of status, current address, current
> employer, and name changes. This is currently being handled by either
> the enrollment centers, the Canadian processing center, or the FAST
> processing center.
>
> 8a. MEDPID should not need to be sent to add the driver.
>
> If the driver is a FAST registered driver they do not have to be added
> to the carrier's ACE account.

9\. Why wouldn\'t the FAST ID be converted to an ACE ID and make the
FAST ID go away?

> This request has been forwarded to the planning team for consideration
> in a subsequent release.

10\. Is the MEDPID a requirement, or can the driver\'s detailed
information be sent with each 309 manifest?

MEDPID is optional. You can send the driver information in each 309 (or
UN/EDIFACT PAXLST).

EDI Communications

Communications for EDI (MQ Series)

Communications

1\. Please discuss why CBP has not considered using AS2 for
connectivity.

See question and answer number 7 below in this section.

2\. What is considered "high volume"?

Volume criterion has not yet been determined by CBP with regard to
whether an ACE e-Manifest: Truck participant should or could use VPN/MQ
vs. Frame Relay/MQ. Current ACS dial up users of the Automated Broker
Interface or the Air and Ocean Automated Manifest Systems are considered
to be low volume.

3\. If we already have an MQ connection, can this be used as a back up?

If you already have an MQ connection on frame relay, it should have a
back up or secondary PVC connected to our redundant router. It is also
possible to have an ISDN dial back up to the frame relay/MQ connection.
Although it would be possible to use the internet VPN as a third back up
if desired, still using MQ, we would only want this to be a temporary
solution until the frame relay link is restored.

4\. What kind of enhancements are being built into the network to
relieve outages?

CBP is building a new ring into the architecture.  CBP currently relies
on Sprint\'s network and the Service Level Agreements it has established
with Sprint.  CBP is trying to work with Sprint to eliminate outages,
(we can never have 100%).   We are working to make the service as fail
proof as possible.

CBP just completed installing a new SONET ring between our Data Center
and the two servicing central offices. We have redundant routers and
firewalls installed at the Data Center, that allow a secondary PVC to be
provisioned to the alternate system. Beyond the Verizon central offices
into Sprint\'s frame relay network, we rely on Sprints redundancy and
recovery systems in their network architecture. We also maintain close
coordination with Sprint on all outages, and enforce Service Level
Agreement criteria on all outages.

5\. Any plan to support HTTPS?

CBP is not supporting HTTPS for the VPN connection to our Data Center to
process batch entries. This will be done with Cisco IP/SEC VPN
encryption and MQ Series. HTTPS is only supported for WEB access to the
ACE portal at this time.

6\. Have issues with scheduled downtimes been resolved? There are four
outages of which some fall within operational timeframes.

> The trade is referring to the CBP Middleware document "FRAME RELAY /
> MQ Series ENTERPRISE SOLUTION" that specifies the following...
>
> "Customs will have four scheduled maintenance windows a week as
> follows: All Times are Eastern
>
> Sunday - Monday 1:00 AM -- 2:00 AM
>
> Wednesday 5:00 AM -- 7:00 AM
>
> Saturday 5:00 AM -- 7:00 AM
>
> Saturday 11:00 PM -- 3:00 AM"
>
> CBP Middleware: "Network Engineering maintenance window from
> 01:00-02:00 on Monday mornings. When possible, we will only take down
> one system at a time for maintenance, leaving a redundant system
> operational, thus negating an outage to the user community. From time
> to time we do need to take an entire system down and cause a service
> disruption to perform upgrades that cannot be done independently. We
> will strive to minimize the times that disruptive maintenance needs to
> be done. The other maintenance windows are for application updates or
> changes and will need to be addressed by the appropriate application
> owner."

7\. About VPN standards \-- you mention Cisco exclusively \-- what about
other IPCs compatible equipment (Checkpoint, WatchGuard, SonicWall,
etc)? Is there anything proprietary about Cisco?

CBP Middleware: "CBP has standardized on the Cisco VPN technology. This
is consistent with the router and switch infrastructure that the VPN
will interface to at CBP, and in the future CBP will be incorporating
the VPN within the routers themselves. Due to synchronization and
configuration issues, CBP does not feel that interfacing to IP/SEC
devices other than Cisco should be done. CBP will only be able to
support the configuration and set up of Cisco router and VPN devices or
software."

8\. What would happen in the event that the MQ to the government is not
working for a period of time requiring the carrier to send the manifest
by alternate means and then the queue is restored and the same
information comes in via EDI?

The EDI messages would reject with an error message "already on file".

9\. If we use the MQ/VPN connection will we be required to use
Encryption boxes?

CBP Middleware: "The VPN solution via the internet will use the Cisco
IP/SEC 3DES encryption algorithm. There will be no other encryption unit
needed. The Cisco VPN client will be a software module on the Windows or
UNIX platform that you are using. The frame relay connection will still
require a frame relay link encryption unit to be on the circuit. The CBP
frame relay infrastructure only supports frame relay layer two link
encryption at this time."

10\. Can we send multiple ISA\'s in one message transmission?

No.

> 10a. Can we send multiple 309\'s in one interchange?
>
> No. In Release 4, ACE will accept only one 309 per ISA interchange.

11\. What would be the consequence of having EDI message control numbers
out of sequence?

Inbound messages to CBP would be of no consequence.

With respect to out of sequence messages to the carriers, this would
require further clarification from the trade.

12\. Are you providing any better communications / diagnostic tools for
users when networks, etc. fail?

CBP Middleware: "There are areas that need to be explored between
\"Sits\" and \"help desk\". Need better lines of communications between
these two groups and applications team. Help desk needs to be more
engaged in identifying issues. The \"Front End\" of the system needs to
communicate with the \"Back End\" of the system."

13\. When outages occur an email should be sent to the corporate email
account. We spend a lot of time researching problems; an email from CBP
would save us a lot of time. We understand you don\'t want to advertise
the outage, but a time frame should be set to initiate trade
communications.

Noted.

14\. Are we limited to sending one interchange per message transmission?

> Yes.

EDI Release 4 Presentation

Release 4

ANSI X.12

1\. If a shipment is placed in-bond after arrival at the border, does a
309 update of the shipment need to be made to indicate the in-bond in
order to later report the in-bond arrival?

> No.

2\. Are we limited to one 309 interchange per message transmission?

Only one 309 transaction per ISA-IEA interchange is currently accepted.

3\. What will happen if the 358 and/or 353 arrive before the 309?

If the 358 comes in it would be considered \"empty". If you provide a
353 before the 309, then you are submitting an empty trip. If a 309 came
in for this trip after the 353, you would be required to send an
amendment code.

If you specify bills in the MBL segment of the 358 set that were not set
up using a 309, you will get a "shipment not found" message for each
bill reported in the MBL segment.

4\. How will you report an empty Instrument of International Traffic
(IIT) loaded in a trailer?

You indicate that the trailer contains an empty container or IIT by
reporting the type of IIT in the VID18 element (or UN/EDIFACT CUSCAR RFF
Segment, Segment Group 7, C506/1154 or CUSREP RFF Segment, Segment Group
11, C506/1154) ).

5\. Up until what time can we file manifest amendments?

Although currently there is no time restriction, this is subject to
future CBP policy.

6\. Is ACE using the first 9 characters of a shipment number, including
SCAC, for In-Bond number?

When an In-bond number is not provided, the shipment control number will
be used as the In-Bond control number. The shipment control number would
be composed of the SCAC and a maximum of 12 alpha/numeric.

7\. Once the 353 is filed how are amendments/corrections managed?

They are managed in the same way as they are prior to the 353; however,
an amendment code is also required in this case.

8\. Will ACE allow the shipment information submitted by one carrier and
the conveyance and crew information submitted by another carrier to be
linked within ACE by the trip number?

Although this type of functionality is currently being considered, no
final determination has yet been made.

9\. If a carrier has several DOT #\'s, can they be submitted in the 309
or can they be entered as part of the carrier's profile?

Master data for a carriers account only supports one DOT number.

> When supplying a manifest you can only supply one DOT number per
> conveyance.
>
> You can supply a different DOT number for a different trip.
>
> The DOT number on the truck must be submitted in the 309 or 358.

10\. Can shipments created for possible inclusion on a Preferred
Manifest (Reduced Data Elements) be linked onto a Standard Manifest
without getting a reject when creating the Standard Manifest?

No.

11\. Will changes or submissions be accepted for a single manifest from
two sources at the same time (from Portal and EDI)?

> Yes. A carrier can use both EDI and Portal to file manifest
> information.
>
> **11a. If the answer is yes, will be there some type of message sent
> back to the user notifying them as such?**
>
> No. For example if an EDI filer adds a shipment to a manifest via the
> Portal, the shipment data will not be sent back to the carrier via
> EDI.
>
> **11b. What happens if EDI is filed at the same time data is being
> filed in the Portal?**
>
> The EDI transmission will be rejected.

12\. Is there a replacement function?

> ANSI X12:
>
> Yes, you can add, delete or replace shipment information in the M13
> Segment. The following is an extract from the 004060 USCBP 309
> Implementation Guidelines.
>
> M1303 580 Amendment Type Code
>
> Code identifying type of manifest amendment.
>
> CODE DEFINITION
>
> A Add a Bill of Lading
>
> D Delete a Bill of Lading
>
> M Replace a shipment segment, either adding, deleting, or substituting
> original manifest information. This permits users to substitute
> information in existing manifests without deleting and transmitting a
> new 309 set.
>
> The segment with the corrected information immediately follows the
> M13. The segments must be submitted in loops: NM1,DMG, REF, N3, N4; N1
> (shipper), N3, N4, N1 (consignee), N3, N4; VID, M7, N10, VC,H1. If
> anything is updated in an N10 (commodity), all N10 segments in the
> loop must be submitted. The M11 segment must be submitted every time
> the replace submission occurs. The N1 loops must also be submitted
> every time a replace submission occurs.
>
> UN/EDIFACT:\
> \
> To replace Trip information (any data concerning the conveyance,
> crew/passengers, or equipment) only, use Message Function Code (BGM
> Segment, DE 1225) = 20, Replace heading section only.\
> \
> To update commodity data, use Message Function Code (BGM Segment, DE
> 1225) = 4, Change and use Document status code (CNI Segment,
> C503/1373) = 24, Status 2.  This will allow changes to the Trip
> information, if needed, and modification to the commodity data.
>
> **12. Can you replace the estimated date of arrival?**
>
> You can not simply replace the estimated date of arrival.\
> \
> ANSI X.12:\
> \
> To change the estimated date of arrival in an existing manifest you
> must delete the trip (code 3 in the M1009), create a new trip and link
> the shipments to the trip.\
> \
> UN/EDIFACT:\
> \
> To change the estimated date of arrival in an existing manifest you
> must delete the trip (BGM Segment, DE 1225 = 3, Delete), create a new
> trip and link the shipments to the trip.

13\. If we cancel a manifest and resubmit, does this start the \"clock\"
again?

> Yes.

14\. The M13 speaks to a split shipment. Is there someplace to send a
split indicator?

No. Boarded quantity is used to indicate whether the shipment is a split
shipment. When using ANSI X12 the only way to report a split shipment is
to report the manifest quantity with the 309 set and report the boarded
quantity with the 358 set.

15\. Please provide examples of when an amendment would not restart the
clock.

There are none.

16\. If we have a full trailer that is traveling In-bond, could we
arrive all of the In-bonds contained within a trailer with one 353
reporting the trailer number or do we need to arrive each shipment
individually?

All In-bonds can be arrived by the container/trailer (equipment) number.
One shipment control number or an inbound number of a shipment within
the container would also be required.

17\. The 350 message to the carrier that provides the shipment
status..... does it contain the broker entry number at this time or do
we also have to wait for further entry ACE enhancement?

Although the 350 does contain the broker's entry number, the 350 set is
only sent after the arrival of the conveyance at the border. This
information is not sent pre-arrival of the carrier.

18\. When sending the 350 message back, do you send release or hold for
a shipment?

When the trucks arrive at the border you will receive an arrival
message. You get one message with status on all the components.
Subsequent 350 messages sets will be send as \"release\" messages.

19\. Will ACE accept multiple DOT #\'s and are they stored in the
profile?

No. An account is only associated with one DOT number. If a carrier uses
conveyances that have different DOT numbers, then the number must be
sent with the manifest record as a "one-time-conveyance".

EDIFACT Messages

**1. You have "add/change/delete". Do you have the same capability as
ANSI X12? Are you restricted to changing only certain fields or can you
change the entire record? Would changing fields or records reset the
clock?**

***Issue:* Design concerns regarding "replace / delete" were expressed.
An attendee didn't agree with the reasons behind some of the design
decisions. He would like to know why we will be using the design
currently in place as it does not follow the previous methods being used
today.**

Answer: You can change information at the trip level, header level or
shipment level as explained in the e-Manifest: Trucks EDI information
session presentation.

In looping records, like the N10, if any modification is made to a
single N10 then all of the N10s must be resubmitted for that bill
record. A whole bill does not have to be deleted and re-added in order
to simply update, for example, the bill quantity. This ability to modify
records instead of only having the option of deleting and re-adding
records is for the optional convenience of the carrier.

However, you still have the option to delete and re-add the entire trip,
header and shipment details as is done in FAST as well as Sea and Rail
AMS today.

Amendments prior to arrival but after the submission of the complete
manifest would re-start the 1 hour clock.

**2. Will Province be a 2 or 3 digit code?**

Currently only two digit codes are supported in ANSI. Two or three digit
codes are supported in EDIFACT. Options are currently being discussed.

**3. What standards version of EDIFACT will be used for Standard Truck
Manifest?**

The CUSCAR version is 03B.

**4. Can we send one complete CUSCAR for In-bond, or do we need to send
an additional CUSREP similar to the 358 in X12?**

You could request an In-bond move in ANSI by sending a "complete" 309
without having to follow up with a 358. In EDIFACT you could request an
In-bond move by sending just a CUSCAR if you identify it as a "complete"
CUSCAR. A follow-up CUSREP is required to affect the arrival of the
In-bond at destination.

**5. How will CBP know the difference between a FAST CUSCAR message set
and a Standard Truck Manifest CUSCAR?**

The message is identified in the BGM Segment, composite C002/1000, by
the word 'STANDARD'. However until ACE subsumes FAST, the FAST manifests
will be sent to a different MQ address.

**6. Can we have an example in X12 and EDIFACT of a service bureau
submitting data for a carrier? Please indicate the responsible parties
for the transmission and the content of the data.**

ACE Release 4 will only support the identification of the carrier as the
transmitter of the data.  However, this will not preclude the use of a
service center to submit data on behalf of a carrier.

All participating service centers are to submit the transmitter ID in
the EDI message header as that of the SCAC (carrier) code of the carrier
on whose behalf they are submitting.  This means that each ACE Release 4
carrier, regardless of whether they use a service provider or not, will
have a specific routing profile.

The ANSI X12, ISA record set will contain the carrier\'s SCAC code in
the ISA 06 data element and a qualifier of \"02\" in the ISA 05 data
element.  In EDIFACT the S002:007 qualifier data element will be
reported as \"02\" and the S002:004 data element will contain the
carrier\'s SCAC code.

**7. Are there any plans for the WCO to use anything other than
EDIFACT?**

No.

Testing and Validation

Testing and Validation

1\. The Pilot involving trade participants is starting at the end of
October. On Nov 29, there will be 30 days in which to conduct
integration testing with the various trade partners and ACE. One month
is not sufficient to do integration testing before going \"live\".

The trade will be able to send test EDI messages to the \"Test and
Certification\" environment no earlier than 10/25/04 and send production
EDI messages to the \"Production\" environment no earlier than
12/11/2004.

Pilot/User Acceptance Testing (UAT) for Blaine, Washington will take
place no earlier than 12/11/04 and will be completed no earlier than
2/23/05. At Buffalo (Peace Bridge & Lewiston points of entry), New York
the corrosponding dates will be no earlier than 01/15/05 thru 2/23/05.

2\. How firm is the PRR date? If testing with the trade cannot begin any
earlier then 30 days prior to PRR we feel that it does not provide
enough time for proper testing. Will the PRR date be moved forward?

There are no plans to move the PRR date currently set for 11/29/04
however the pilot UAT test will not place any earlier than 12/11/2004.

3\. Please note that the trade does not feel that 30 days is enough time
to properly test.

4\. What is the planned rollout schedule, including dates and sites for
ACE, starting with the PRR date?

The deployment order listed below are the tentative deployment dates for
ACE Release 4 and are all planned for Saturday midnight unless we
determine with the ports a better time.

12/10/04 - 12/17/04 1st Port Deployment & Pilot. Blaine.

01/14/05 - 01/21/05 2nd Port Deployment & Pilot. Buffalo & Lewiston

02/25/05 - 03/04/05 3rd & 4th Port Deployment Detroit (Ambassador Bridge
and Windsor Tunnel) / Port Huron

03/11/05 - 03/18/05 5th Port Deployment Champlain

03/25/05 - 04/01/05 6th Port Deployment Laredo (Bridge 3 & 4)

04/08/05 - 04/15/05 7th Port Deployment Otay Mesa

5\. What type of user test plans are going to be made available to the
trade?

A Federal Register Notice will be published announcing the test of Truck
Manifest.

The ANSI X12 and EDIFACT messages are posted on CBP's web site. The Test
and Certification environment will be set up for the trade to submit
sample messages. The T&C environment is scheduled to be available no
earlier than November 1, 2004 and the production environment will be
deployed in mid-December.

User Acceptance Testing (UAT) for the ACE Secure Data Portal for Blaine,
Washington is scheduled for December 11, 2004. Computer Based Training
(CBT) materials are scheduled to be made available around the end of
November 2004.

ACS client reps will administer EDI test scenarios.

6\. Are there any plans to provide 309 or 358 information back to the
originating carrier when data has been entered via the portal? Scenario:
A carrier submits preliminary Shipment information via EDI, then a
Manufacturer or Loading facility having access to the ACE portal for
that carrier, adds the Trip and Crew Information and attaches the orphan
bills to the trip. Could this new information be transmitted back to the
carrier or designated broker in EDI format?

No.

7\. Where in the test plan is volume/load testing?

There is no specific test scheduled for volume/load testing with the
trade. The test administered by ACS client reps may include a section
that would allow for the submission of a large volume of records.

8\. How are you going to disseminate the test results encountered during
SIT, SAT, and UAT? If these result in programming changes, the trade
will need to accommodate for these as well.

If changes to the messages are required, the messages will be updated
and the changes will be noted. Message updates will be posted to the CBP
web site.

9\. As part of system integration testing, it is also common to include
interfaces involving the trade. Since CBP can\'t possibly replicate all
of the scenarios faced by the trade, why isn\'t this also included?

System Integration is performing tests of the trade interface. eCP is
using a simulator to process messages through middleware and into and
out of ACE. eCP can fully test all messages coming from and going to
trade. This will ensure that the ACE (and middleware) applications
conform to stated requirements. Scenarios faced by the trade will get
tested as part of the Service Provider and Self-programmer validation
tests which will be performed in the T&C environment.

10\. CBP needs to develop some sort of checklist that can be shared
between the client and the client rep. More than often the client rep is
unsure as to the next step or who to contact for further information
regarding such matters (e.g, middleware, application, etc.). This is not
only going to be the case with ACE, but with other system integration
engaged by the trade, including but not limited to, the migration to MQ
Sprint Frame Relay.

Noted.

11\. How does CBP plan to test the truck manifest portal with the trade?
Please address volume testing as well as functional testing.

Truck Manifest Portal testing, which is the entering of manifests
through the portal, will be fully tested in our System Integration Test
and System Acceptance Test program. In those tests we will enter
manifests as though they were entered by the trade. Our test program
includes both functional and volume (performance) testing.

12\. What kind of training will be provided for the portal?

Training for e-Manifest: Trucks ACE Secure Data Portal will be Computer
Based Training (CBT).

13\. If we only intend to send complete manifests using the CUSCAR
without any CUSREP transmissions, will it still be necessary for us to
test the CUSREP (this would require additional unneeded programming on
our side)?

CUSREP is required if you choose to arrive in-bond shipments. However,
inbonds can be arrived by CBP or an ABI inbond participant. The similar
CUSREP counterpart in ANSI, the 358, is required to be used if you have
a split shipment. A CUSREP is not required to report split shipments
when using EDIFACT.

14\. Is the test environment going to be ongoing to test new functions
that come on board? Can you maintain the test environment for the
future?

Yes, this will be an ongoing environment.

15\. When will the Portal be available to view?

It is expected that the Portal will be available to view in December
2004.

16\. When in the testing environment, will there be a higher priority on
resolving issues that might arise from the reported test problems?

You will need to work with your CBP client representative to understand
the issue and determine the response time for resolution.

17\. If the Portal is not available in the T&C environment, how can the
trade test their business process if we plan to use a combination of the
Portal and EDI?

The T&C environment will only support EDI testing. Testing of the joint
EDI/Portal business process would have to take place in the production
environment.

18\. We operate both as a carrier and a broker and use 2 different
IRS#\'s. We have filed an application to be an ACE account for the
brokerage side. Although I am assuming we will have to file a separate
application as a carrier is it possible to have the same client
representative?

Please contact your client representative for advice.

A single ACE account can be established with multiple views. For example
you could have a broker view and a carrier view.

19\. Is the eCP utilizing a separate development environment than that
of test?

Yes.

20\. Will certification of hot sites/disaster sites be required or
allowed?

There are no requirements for the trade to certify hot sites or disaster
sites. You will work with your CBP client representative to determine if
hot sites need to be validated.

Questions received after the presentation

**Communication**

**1. In order to participate in the MQ Frame Relay Program, is it a
requirement that we secure an encryption \"black box\" from the CBP?**

The trade can purchase the Cylink encryptor from either Sprint or from
any Hardware/Software vendor.

**2. Why is the MQ VPN Program targeted for only \"low volume\"
carriers? We currently do high volume through IPSEC VPNs with many
trading partners today without issue. AS2: Please see link for
definition. <http://www.ietf.org/html.charters/ediint-charter.html> Many
carriers have been asked by many of their trading partners (mostly
retailers) to use EDIINT AS2 over the past two years. Many in the trade
have already adopted the necessary technologies to provide this
communication mechanism to their trading partners. EDIINT AS2 has built
in confidentiality, authentication, integrity and non-repudiation into
the standard message. EDIINT AS2 was built with server to server
processes in mind, not browser to process (as was alluded to during the
meeting re: HTTPS with SSL).**

Volume criterion has not yet been determined by CBP as to whether an ACE
e-Manifest: Truck participant should or could use VPN/MQ vs. Frame
Relay/MQ. Current ACS dial up users of the Automated Broker Interface or
the Air and Ocean Automated Manifest Systems are considered to be low
volume.

**MEDPID and Carrier Accounts**

**1. Is CBP requiring the trade to maintain all ACE assigned ID\'s, or
will the CBP maintain a cross reference where the trade can send their
location codes and CBP will look-up the appropriate ACE ID?**

If the trade chooses to use ACE ID's they must be maintained in ACE by
the carrier.

**2. Will the ACE IDs be based on any standard (i.e. Global Location
Code Standard)?**

No.

**Manifest Transactions**

Transponder IDs are issued via the FAST conveyance registration process.

Driver Proximity card application ID's are issued via the FAST driver
registration process.

ISO codes are used for country and sub-country validation.

Schedule D numbers are used for U.S. Port identification.

Schedule K numbers and IATA city codes are used for foreign city
identification.

FIRMS "Facilities Information and Resources Management System" are used
to identify bonded facilities.

**3. Is there any documentation or information available to the carriers
informing them of the type of information that can or cannot be stored
in the Portal? What information must be entered every time and what can
be stored under that account?**

Information can be stored in a carrier's ACE account for Conveyance,
Equipment and Crew. These data elements can be found in the MEDPID
messages that are posted on CBP's Web site**.**

**Process Flows**

**1. How much time can expire between the time the carrier sends the 353
and the Broker Entry Package is Filed?**

There is currently no limitation on the time between filing of the 353
and the broker entry package.

**2. Will there be a timing constraint placed on the Brokers to complete
this step within an hour? two hours?**

19 CFR 123.92, which establishes time frames for the transmission of
data by truck carriers, provides for CBP approved Electronic Data
Interchanges for transmitting data and allows importers and brokers to
submit some or all of the data for carriers. Prior to the implementation
of ACE e-Manifest: Trucks, CBP will enforce the pre-filing of cargo
information via PAPS and QP/WP (electronic in-bond). Exceptions,
including CAFES and BRASS will be supported. The time frames for
prefiling cargo information pre and post ACE, whether via the entry or
the manifest, will be no later than 1 hour prior to the carrier's
reaching the first port of arrival in the United States. For truck
carriers participating in the FAST (Free and Secure Trade) program, CBP
must electronically receive such cargo information no later than 30
minutes prior to the carrier's reaching the first port of arrival in the
United States.

*See* FRN published August 17, 2004 "Required Advance Electronic
Presentation of Cargo Information: Compliance Dates for Truck Carriers"
(69 FR 51007) for the interim requirements.

**Celedon**

**1. Is it still necessary for a driver to have CBP documents and
commercial invoice in hand when crossing the border if the ACE
transmissions were successful? What if the transmission failed or was
rejected?**

Yes a driver will be required to have CBP documents in his possession,
however a carrier would be able to confirm either though an EDI response
or over the ACE Secure Data Portal, that CBP would have the manifest on
file.  After a successful pilot of e-Manifest, CBP could make
modifications to the regulations to accept a paperless truck manifest. 
With reference to the commercial invoice, a carrier can not verify in
advance of the arrival whether CBP has the appropriate entry information
available for review.  Therefore, a carrier will still be required to
maintain a commercial invoice until further functionality is developed.

**2. We deliver Northbound loads to a freight forwarder in Nuevo Laredo
who contracts to a drayage carrier to haul the load across the border to
our yard in Laredo, TX. Who is responsible for the EDI in this case?
Freight Forwarder? Drayage Carrier?**

The carrier that physically brings the conveyance, equipment, crew and
shipments across the border is the entity responsible for submitting the
manifest to CBP either via EDI or the ACE Secure Data Portal. A carrier
can designate an agent to submit manifests on behalf of the carrier via
the ACE Secure Data Portal.  

 

**3. How detailed do the commodity descriptions need to be? Will
definitions like \"Automotive Parts\" suffice?**

The following was copied from CBP's FREQUENTLY ASKED QUESTIONS: 24-HOUR
ADVANCE VESSEL MANIFEST RULE published April 16, 2004. We do not expect
the requirements for Truck to be any different. Please refer to the
referenced CBP publication for further details.

"*To be clear, [IN NO CASE]{.underline} is a blank description, freight
all kinds (FAK), said to contain (STC) with or without other
description, general merchandise, "26 pallets", various retail
merchandise, consolidated cargo or other similarly vague descriptions
acceptable...*

*The following terms are meant to be used as a guide. They are
illustrative, not exhaustive, examples of acceptable and unacceptable
descriptions. Phrases or words in parenthesis are meant as examples."*

+-----------------------------+----------------------------------------+
| **Not Acceptable**          | **Acceptable**                         |
+-----------------------------+----------------------------------------+
| Apparel                     | Clothing                               |
|                             |                                        |
| Wearing Apparel             | Shoes                                  |
|                             |                                        |
| Ladies\' Apparel            | Footwear                               |
|                             |                                        |
| Men\'s Apparel              | Jewelry (may include watches)          |
+-----------------------------+----------------------------------------+
| Appliances                  | Kitchen Appliances                     |
|                             |                                        |
|                             | Industrial Appliances                  |
|                             |                                        |
|                             | Heat Pump                              |
+-----------------------------+----------------------------------------+
| Autoparts                   | New Autoparts                          |
|                             |                                        |
| Parts                       | Used Autoparts                         |
+-----------------------------+----------------------------------------+
| Caps                        | Baseball Caps                          |
|                             |                                        |
|                             | Blasting Caps                          |
|                             |                                        |
|                             | Bottle Caps                            |
|                             |                                        |
|                             | Hub Caps                               |
+-----------------------------+----------------------------------------+
| Chemicals, hazardous        | Actual Chemical Name (not brand name)  |
|                             |                                        |
| Chemicals, non-hazardous    | Or U.N. HAZMAT Code Identifier \#      |
+-----------------------------+----------------------------------------+
| Electronic Goods            | Computers                              |
|                             |                                        |
| Electronics                 | Consumer Electronics, Telephones       |
|                             |                                        |
|                             | Electronic Toys (can include Gameboys, |
|                             | Game Cubes,                            |
|                             |                                        |
|                             | Dancing Elmo Doll etc.)                |
|                             |                                        |
|                             | Personal/Household Electronics (i.e.   |
|                             | PDA\'s, VCR\'s, TV\'s)                 |
+-----------------------------+----------------------------------------+
| Equipment                   | Industrial Equipment, Oil Well         |
|                             | Equipment                              |
|                             |                                        |
|                             | Automotive Equipment, Poultry          |
|                             | Equipment etc.                         |
+-----------------------------+----------------------------------------+
| Flooring                    | Wood Flooring, Plastic Flooring,       |
|                             | Carpet, Ceramic Tile,                  |
|                             |                                        |
|                             | Marble Flooring                        |
+-----------------------------+----------------------------------------+
| Foodstuffs                  | Oranges                                |
|                             |                                        |
|                             | Fish                                   |
|                             |                                        |
|                             | Packaged Rice, Packaged Grain, Bulk    |
|                             | Grain                                  |
+-----------------------------+----------------------------------------+
| Iron                        | Iron Pipes, Steel Pipes                |
+-----------------------------+----------------------------------------+
| Steel                       | Iron Building Material, Steel Building |
|                             | Material                               |
+-----------------------------+----------------------------------------+
| Leather Articles            | Saddles                                |
|                             |                                        |
|                             | Leather Handbags                       |
|                             |                                        |
|                             | Leather Jackets, Shoes                 |
+-----------------------------+----------------------------------------+
| Machinery                   | Metal Working Machinery                |
|                             |                                        |
|                             | Cigarette Making Machinery             |
+-----------------------------+----------------------------------------+
| Machines                    | Sewing Machines                        |
|                             |                                        |
|                             | Printing Machines                      |
+-----------------------------+----------------------------------------+
| Pipes                       | Plastic Pipes                          |
|                             |                                        |
|                             | PVC Pipes                              |
|                             |                                        |
|                             | Steel Pipes                            |
|                             |                                        |
|                             | Copper Pipes                           |
+-----------------------------+----------------------------------------+
| Plastic Goods               | Plastic Kitchenware, Plastic House     |
|                             | ware,                                  |
|                             |                                        |
|                             | Industrial Plastics                    |
|                             |                                        |
|                             | Toys, New/Used Auto Parts              |
+-----------------------------+----------------------------------------+
| Polyurethane                | Polyurethane Threads                   |
|                             |                                        |
|                             | Polyurethane Medical Gloves            |
+-----------------------------+----------------------------------------+
|                             | Personal Effects                       |
|                             |                                        |
|                             | Household Goods                        |
+-----------------------------+----------------------------------------+
|                             |                                        |
+-----------------------------+----------------------------------------+
| **Not Acceptable**          | **Acceptable**                         |
+-----------------------------+----------------------------------------+
| Rubber Articles             | Rubber Hoses                           |
|                             |                                        |
|                             | Tires                                  |
|                             |                                        |
|                             | Toys                                   |
|                             |                                        |
|                             | Rubber Conveyor Belts                  |
+-----------------------------+----------------------------------------+
| Rods                        | Welding Rods                           |
|                             |                                        |
|                             | Rebar                                  |
|                             |                                        |
|                             | Aluminum Rods                          |
|                             |                                        |
|                             | Reactor Rods                           |
+-----------------------------+----------------------------------------+
| Scrap                       | Plastic Scrap                          |
|                             |                                        |
|                             | Aluminum Scrap                         |
|                             |                                        |
|                             | Iron Scrap                             |
+-----------------------------+----------------------------------------+
| STC (Said to Contain)       |                                        |
|                             |                                        |
| General Cargo               |                                        |
|                             |                                        |
| FAK ( Freight of All Kinds) |                                        |
|                             |                                        |
| \"No Description\"          |                                        |
+-----------------------------+----------------------------------------+
| Tiles                       | Ceramic Tiles                          |
|                             |                                        |
|                             | Marble Tiles                           |
+-----------------------------+----------------------------------------+
| Tools                       | Hand Tools                             |
|                             |                                        |
|                             | Power Tools                            |
|                             |                                        |
|                             | Industrial Tools                       |
+-----------------------------+----------------------------------------+
| Wires                       | Electric Wires                         |
|                             |                                        |
|                             | Auto Harness                           |
|                             |                                        |
|                             | Coiled Wire (Industrial)               |
+-----------------------------+----------------------------------------+

Automotive Parts is unacceptable.  Used Auto Parts or New Auto Parts
would be acceptable. 

**4. How do I find out who our client representative is?**

ACS client representatives are assigned by Janet Pence. Janet Pence can
be contacted at Janet.Pence@dhs.gov

**5. Are all brokers required to be able to access the data via broker
download? If we send data to ACE along with a broker\'s SCAC, are we
guaranteed the broker will get the information and will file the entry
before we get to the border?**

A broker is not required to receive broker download data.  However, if
the carrier supplies the customs broker or self filing importer\'s Filer
Code, Port Code, and if applicable, Office Code, then ACE e-Manifest:
Trucks (Release 4) will pass the shipment information to the entry filer
identified.  Although you are not guaranteed that the broker will get
the information, if the carrier identifies the broker properly there
will be a very high probability that the broker will be notified.  There
is certainly no guarantee that the entry will be filed before the truck
arrives at the border; this communication should take place between the
broker and the carrier. 

**6. If we are a bonded carrier, are we automatically able to file
paperless bonded moves via EDI?**

As an ACE carrier you will have the ability to request in-bond moves via
e-Manifest: Trucks (Release 4) either via the ACE Secure Data Portal or
via EDI.  With respect to an anticipated time frame for when the process
will be accepted as completely paperless, this is a CBP policy
decision. 

**7. How do I obtain a port code listing?**

The Schedule D, U.S. Port Code list can be obtained from CBP\'s web
site.

**8. For bonded moves, your specs are asking for the HTS number upon
export for purposes of the Corps of Engineers. Can you please explain
the role of the Corps of Engineers and how this applies. If we are
required to supply the HTS for all T&E bonded moves, how can I obtain a
listing of HTS numbers?**

When creating Transportation & Exportation or Immediate Export (In-bond)
requests for cargo that will be exported from the country by ocean, you
are required to supply the Harmonized Tariff Schedule (HTS) number. 
This information is passed from CBP to the Army Corps of Engineers for
statistical purposes.  The HTS is available for free from
[www.USITC.gov](http://www.USITC.gov/).

**9. What is an ACE proximity card ID? Is this the number on our FAST
transponder cards?**

Yes, this is the number associated with the Driver's FAST proximity
card.

**10. When will ACE be able to accept preferred manifests?**

Currently the plan is for ACE to accept preferred manifests when ACE has
been deployed in all FAST ports. Although FAST shipments will be filed
directly to FAST, ACE will process all FAST shipments that cross at an
ACE ports.

**11. Can we choose to handle In-Bond diversions manually rather then
via EDI?.**

Yes.  In other words you will not have to request a diversion via ACE or
ACS.  The fact that you arrive an In-bond via ACE or ACS at a port other
than the destination requested will identify that you made a diversion.
An In-bond must be arrived electronically either via the ACE Secure Data
Portal, EDI, QP/WP or CAFES.

**12. Will the REQDOC still be needed for preferred loads in ACE, when
preferred loads are implemented?**

Although all of the details of Preferred have not been worked out it
would be reasonable to assume that CBP will require that they have the
ability to request further details about a shipments either via an
EDIFACT REQDOC or a yet to be determined ANSI X12 equivalent. ACE
Release 4 does not have within its scope the requirement to receive
entry or invoice data directly from the trade.

**13. I am being told that in the case of a "Canada to Mexico" or
"Mexico to Canada" load, our driver approaches the CBP official, and the
official activates the T&E Bond. Then upon leaving the U.S., the CBP
official cancels the T&E Bond. Since the Bond# is to be sent in the EDI
manifest for ACE, how will this manual process be changed, if at all?**

You will be able to make the In-bond request (T&E) through the existing
CAFES or QP/WP legacy (ACS) interfaces or directly though the shipment
portion of the truck manifest declaration in ACE. This is accomplished
through the M12 segment of the ANSI 309 message set (or UN/EDIFACT DOC
Segment).

The inspector will release the shipment to move in-bond if the in-bond
request has been previously requested through one of the above methods

It will be the carrier\'s responsibility to report that the cargo has
arrived at its U.S. Destination via one of the above methods.

Reporting of the export of the shipment and thereby closing the in-bond
can only be reported to CBP via CAFES, QP/WP or manually by CBP
personnel. Under the current design the export of the in-bond can not be
reported via ACE.

**14. The IIT process on In-bond moves are still a bit unclear. We haul
auto parts on \"racks\" across the border all the time, and return the
empty racks. If our trailer contains the auto parts on the racks, is it
considered having partial IIT? If yes, do we still need to \"arrive\"
the IIT bonded portion of the load? Do we need to \"arrive\" full IIT
loads, empty racks or a full empty trailer? Do we need to state the
dollar value of IIT\'s? Would any of the procedures be different for
Canada to U.S. moves, or Canada to Mexico?**

If you have racks in the trailer/container you need to report them at
the Equipment level. If you are bringing a box truck across the border
and it contains IITs you must report them at the conveyance level.

In EDIFACT these codes are\...

EC: Shipment consists of empty IIT\'s covered by Carrier\'s bond

EI: Shipment consists of empty IIT\'s covered by Importer\'s bond

MC: Shipment consists of merchandise and IIT\'s. IIT\'s covered by
Carrier\'s bond

MI: Shipment consists of merchandise and IIT\'s. IIT\'s covered by
Importer\'s bond

These are not what we normally think of as \"In-bond\" moves 61, 62 or
63 and therefore they will not be given an \"In-bond move
authorization\" nor will you be required to \"arrive\" the IIT\'s at a
U.S. destination port. This declaration is made for the purpose of
declaring that there are Instruments of International Traffic on board
and identifying whether they are covered by the carrier or importer\'s
bond. No formal or informal entry would be required as long as they
qualify for IIT treatment. No dollar value is required. There would be
no difference between a "Canada to U.S." or a "Canada to Mexico" move.
Empty trailers or ocean containers should not be reported as IITs.

> **14a. If empty trailers are not considered IIT\'s, how do we report
> empty moves?**
>
> A trip with an empty trailer would report trip, crew, conveyance and
> equipment information but no shipment or IIT's.

**Zisser Group**

**1.  When the Truck Manifest is introduced, will it be used for export
and shipments?  In other words, will the truck manifest be introduced
for both imports and exports? **

ACE e-Manifest: Trucks (Release 4) will not be used for the reporting of
U.S. Goods being exported by land. However, an In-bond request for
either Immediate Exportation or Transportation and Exportation will be
able to be submitted via e-Manifest: Trucks (Release 4). You will be
able to use e-Manifest: Trucks to report the arrival of a T&E but you
will need to report the export of a T&E or I.E. directly to ACS.

** **

**2.  When the Truck Manifest is introduced, will it also be used for
In-bond shipments?  For example, Hitachi or Sony ships a load of Plasma
TVs from Tijuana to Panama via a Los Angeles port.  Would ACE truck
manifest be used in conjunction with the 7512/QP-WP/CAFES?  If not, how
would In-bond shipments meet the Trade Act of 2002 electronic manifest
requirements prior to arrival at the border? **

Yes, ACE will support QP-WP and CAFES, as well as allow the carrier to
request the In-bond move via the manifest shipment record.

> **2b. Likewise, would the truck manifest be used for the land portion
> of an In-bond shipment that originated in ASIA through the port of
> Long Beach with final In-bond destination being Tijuana?**
>
> No. You would be required to request the In-bond via Ocean AMS or
> QP/WP.

** **

**3.  Do you have a summary of the data elements required for the truck
manifest?  Or a sample truck manifest that will be used when it is
introduced?**

The data elements are listed on the CBP web site. Go to
[www.cbp.gov](http://www.cbp.gov/) -- Quick Links -- Trade Support
Network. See also -- ACE EDI message Drafts -- New Modified ACE EDI
Messages for Release 4 Truck Manifest. From here select "Manifest
Submission by Truck Carriers.xls" for a spreadsheet that contains data
elements for truck manifest. You can also look into the ANSI X.12 or
EDIFACT message drafts that are listed in the same area.

Yellow Roadway

1.  **Interchange Guide Version 5, Page 4: "The manifesting carrier will
    be obligated to provide detailed crew, passenger conveyance, and
    equipment information in the 309 Customs Manifest transaction set or
    the 358 Customs Consist Information (Trip) transaction Set. In each
    case (crew member, passenger, conveyance, or equipment) either the
    complete information or an ACE ID number or valid reference number
    from the carrier's account will be mandatory to satisfy this
    requirement." Remembering that we are a carrier using EDI, if we
    choose to send all the information each time, is there any
    requirement for us to store any of this information in our
    account?**

> No, you are not required to store this informaiton in your account.
>
> **Just to clarify, our options are:**

a.  **to send all information each time?**

> Yes

b.  **supply ACE ID number (assuming that you register the crew and
    equipment)?**

> Yes

c.  **Valid reference number. (How is this obtained and is this
    applicable only if you register the crew and equipment)**

> Valid reference numbers are either obtained from FAST or the Carriers
> ACE Account. For example a FAST proximity card number would draw
> details about the driver into an ACE manifest from information
> collected at a FAST enrollment center. A carrier can record conveyance
> details in their ACE carrier account. A Conveyance ID, recorded in the
> Carriers account could be used to drawn conveyance details into a
> manifest.

2.  **Can you explain how an ACE ID is assigned to a driver? My
    understanding was that it was automatically assigned by ACE when a
    driver became FAST approved however there was some question as to
    how the Carrier would actually obtain that number.**

> A FAST ID number (application number, located on the back of a
> proximity card) is issued when a driver enrolles in FAST at a FAST
> enrollment center. An ACE ID number is generated by ACE when a driver
> is added to a carrier's account. Although either ID can be used in
> ACE, when a FAST ID is used ACE will not be able to display the
> driver's details in the Portal.

3.  **Interchange Guide Version 5, Page 5, Split shipments. "If the
    manifesting carrier has transmitted an original 309 and find they
    cannot board the full manifested amount on the truck, they must
    submit the boarded quantities for the shipment. Subsequent portions
    of the quantity may be manifested on additional 358's until the full
    manifested quantity of the original 309 manifest is satisfied."**
    **Does this mean that we can transmit the same shipment ID (pro) on
    multiple 358's until all portions of the freight have been loaded?**

> Yes.
>
> **3a. If we internally assign unique #'s to manage this type of
> situation, can we use these rather than using the same pro \# multiple
> times.**
>
> No
>
> **3b. What happens if the entire shipment is never accounted for? That
> is, the total shipment is 15 pieces, 10 are shown as the boarded
> quantity in one message to CBP, however the other 5 are never actually
> transmitted. Is the carrier responsible to ensure that all pieces are
> boarded and is there a time limit for this?**
>
> Some guidance can be obtained from the split shipment FRN as follows:
>
> *"Comment: Proposed § 41.57(g)(2)(ii) contains a technical
> contradiction in requiring the entry summary to be filed no later than
> 10 working days after the first cargo release, while in effect not
> allowing summary filing before the arrival of the last portion of the
> split shipment which is to be included on the entry.*
>
> *Customs Response: There is no contradiction. Since all portions of
> the shipment must arrive within 10 calendar days of the portion that
> arrives first, and the entry summary must be filed under §
> 141.57(g)(2)(ii) within 10 working days from the date of first release
> of a portion of the shipment, there should be sufficient time for all
> portions of the split shipment to arrive before the entry summary is
> required to be filed. However, should any portions not arrive within
> 10 calendar days of the portion that arrived first, such late arriving
> portions would need to be separately entered, as prescribed in §
> 141.57(i).*
>
> *Comment: Regarding portions of a shipment that do not arrive within
> the required 10 calendar day period, it was asked whether the
> consignee or agent would be responsible for paying full duty on the
> entire shipment before it is complete.*
>
> *Customs Response: The importer of record will only be responsible for
> paying duty based on the value and/or quantity of merchandise
> contained in those portions of the split shipment that arrive within
> the required 10 calendar day time frame and are thus included in the
> split-shipment entry. As such, when a portion of a split shipment does
> not arrive within the prescribed 10 calendar day period, that portion
> will not be included on the entry, and thus no duty will yet be due on
> that portion. Duty on any delayed portion will become due when the
> portion does arrive and a separate entry for that portion is filed."*
>
> The above statements show that late cargo could be cleared on the same
> bill but only with a new entry. The rule does not address cargo that
> never arrives however it is our assumption that the entry and duty
> issues would need to be addressed by the entry filer and the original
> manifest records should be amended to the total number of pieces that
> actually crossed the border.

4.  **"350 Customs Status Information. Appropriate Customs status
    information messages will be released to the carrier at time of the
    truck's arrival at the border." Will you in fact be providing us
    with release information? If yes, will it be on all release types
    and at all locations?**

> Yes, on all ACE release types a status message will be returned to the
> carrier, however only for cargo arriving at ACE ports.

5.  **Shipment Amendments: Can an amendment be sent after the trip has
    crossed the border? Is there a time limitation on sending
    amendments?**

> Yes. There is currently no time limit established for sending
> amendments.

6.  **If we use the multi step process, do we receive the 997 and 355
    responses to the preliminary shipment data (309) individually before
    the 358 is actually sent in?**

> Yes.

7.  **Truck Manifest Submission by Carriers Draft -- Version 1d Note \#
    4: Shipment amendment codes. There are amendment codes for non
    In-bond, In-bond and both. Are all of these required amendments. If
    there is a wrong delivery on a non In-bond shipment, are we
    [required]{.underline} to send an update?**

> Amendment codes are required whenever you modify any manifest record
> after having "submitted" your manifest. A manifest is considered
> submitted by one of two actions.
>
> 1\. All manifest data is submitted as "Original" by indicating the
> letter "W" in the M1009 field of a 309.
>
> 2\. Submitted a 353 "end of manifest" to complete a series of
> preliminary 309 and 358 messages.
>
> This is accomplished by reporting a "Z" in the M1501 element.

8.  **Truck Manifest Submission by Carriers Draft -- Version 1d
    Amendment codes: #30. Inadvertently delivered without CBP release.
    Goods will be redelivered in tact or the carrier will pay duty,
    taxes and fees and/or liquidated damages. Can you describe in more
    detail how and when this would be used?**

> Example: If you were authorized to move shipments to your container
> freight station and you removed or delivered a shipment that did not
> have a proper CBP release you would report this amendment code.

9.  **Truck Manifest Submission by Carriers Draft -- Version 1d #25
    Equipment type shows conditional if equipment is not filed. What
    does this mean?**

> If a box truck is crossing the border and it is not pulling a trailer
> or container then equipment would not be reported. Equipment is
> conditional based on whether or not it exists. A Semi Tractor without
> a trailer would also fit this description.

10. **If we send only a conveyance (tractor) across the border, are we
    required to send the VID segment and specify in the VID01 NC for no
    equipment? (bobtailing)**

> As an ANSI protocall, the VID segment is required in the 309 and 358
> set. Therefore, if the tractor is bobtailing the VID segment would
> require "NC" for no equipment to be reported in the VID01 and "No
> Number" to be reported in the VID03 element.

11. **VID10 Load/Empty status code. Is this required on all equipment
    (trailers) moving to the U.S.?**

> The VID10 is only reported when you have Instruments of International
> Traffic inside a trailer or container. A totally empty trailer or
> container is not to be reported as an Instrument of International
> Traffic.

12. **Should a regular trailer be reported as a TL and a refrigerated
    trailer as a TW?**

> Yes, as long as their charateristics do not fit any of the other
> classifications supplied.

13. **Truck Manifest Submission by Carriers Draft -- Version 1d #26
    Equipment #. Conditional for equipment without license plates. What
    types of equipment would be examples of equipment without plates?
    Dolly/Converter?**

> A 20' or 40' ocean container would not have a license plate. The
> chassis on which the container is placed would need to be reported as
> a seperate piece of equipment with a license plate number. A
> dolly/converter is not required to be reported as equipment.

14. **Truck Manifest Submission by Carriers Draft -- Version 1d #26 and
    #27. If a piece of equipment has no plate #, we are required to
    provide the equipment \# (marking#). If a piece of equipment has a
    plate #, we are required to provide the plate \# only. Is this
    correct?**

> This is correct.
>
> Equipment number is a combination of VID02 and VID03 (or UN/EDIFACT
> CUSCAR EQD Segment, position 0220 and SGP Segment, position 0700;
> CUSREP EQD Segment, position 0500).

15. **Crew /person in charge. Can we get a definition of who CBP
    considers the "person in charge"? Is this the person driving the
    truck when they cross the border?**

> 19 USC 1431(b) provides that any manifest required by the Customs
> Service shall be signed, produced, delivered, or electronically
> transmitted by the master or person in charge of the vessel, aircraft,
> or vehicle, \...
>
> 19 USC 1401(e) provides the definition for "Master". The word
> \"master\" means the person having the command of the vessel.
>
> The "person in charge" is the person having command of the vehicle. 
> Not necessarily the person driving the vehicle across the border. 

16. **Truck Manifest Submission by Carriers Draft -- Version 1d #36
    party middle name, if present. Present where? On their
    identification / fast card, birth certificate in our system?**

> Report middle name or initial if it is reported on their drivers
> license or travel document.

17. **Truck Manifest Submission by Carriers Draft -- Version 1d #39
    address. Shows must be U.S.**

> **17a What about Canadian drivers?**
>
> See 17d.
>
> **17b What if not staying in a hotel in the U.S.?**
>
> Then any of the following would be sufficient (see 17d).
>
> **17c Will' Roadway's destined facillity suffice**?
>
> Yes, if the driver will be going to Roadway's facility.
>
> **17d What if the driver is going to make a delivery to a U.S.
> Customer, then make a pick up at another U.S. Customer, and then
> return to Canada?** Either U.S. address would be sufficent.
>
> The Crew members address requested to be reported in Truck Manifest
> willl be "the physical location, in the U.S., where a crew member will
> actually be on this particular trip. This could include a consignee's
> location, a hotel, a truck stop, or a family or friend's location.
> Those individuals possessing a FAST ID are exempt from the US address
> requirement."

18. **Truck Manifest Submission by Carriers Draft -- Version 1d #44
    Hazmat endorsement. Yes/no/state code. Are you looking for "yes" or
    "no", and if "yes" do you want the state or province code?**

> Report YES if the driver has a Hazmat endorsement. Blank or NO will be
> construed to mean that the driver does not have a Hazmat endorsement.
> You do not have to supply the state in which the Hazmat endorsement
> was given.

19. **If we transmit a passport, citizenship card and birth certificate,
    and the driver arrives with only a passport,will this be sufficient
    or is the driver required to arrive with the identification exactly
    as reported in the EDI message?**

> The driver is not legally required to arrive with the identification
> exactly as reported in the EDI message.  However, it would be in their
> best interest to arrive with the identification that was reported in
> the EDI message.

20. **When transmitting travel document information, the REF02 requires
    the number of the travel document. What if the travel document does
    not have a reference #?**

> If there is no number on the travel document supply "no number" in
> this element.

21. **How will we handle a shipment where one Invoice covers more than
    one shipment. that is, a shipment with two or more bills of lading
    therefore two or more pro#'s, and one set of CBP documents. Can we
    use the bill control #/ultimate house to handle this?**

> Report each Pro bill number as a seperate shipment. The entry filer
> can supply multiple Pro#s on one entry.

22. **Truck Manifest Submission by Carriers Draft -- Version 1d #61
    shipment identifier\...trader reference number. Number provided by
    the shipper to be passed through the broker on the Customs download.
    Can you provide some additional information on this? How and when
    would this be used?**

> In FAST this data elements is called "Trader Reference Number". The
> FAST IG references this number in the RFF segment and describes it as
> "Trader Reference Number (an..35): provided by the shipper to be
> passed through to the entry filer on the Customs download. Value will
> be returned unaltered with processing results. Edits will not be
> performed on this field and processing will not be controlled in the
> Customs system on the basis of this data element."
>
> The terminology used in the ANSI X12 Interchange Guideline (IG) is
> Shipper's Identifying Number for Shipment (SID) (N901 & N902). This
> data element will be returned to the carrier in the 305 and 355 data
> sets however it will not be sent to the entry filer in the Broker
> Download message in Release 4.

23. **Truck Manifest Submission by Carriers Draft -- Version 1d #62.
    Port of Loading. Port/Point at which merchandise is loaded on the
    conveyance that will cross the border. For an LTL carrier, please
    confirm that this is the last location dispatching freight to the
    border.**

> Yes.

24. **Truck Manifest Submission by Carriers Draft -- Version 1d #63
    place of receipt. Shows city where carrier took receipt of goods if
    different from port of loading. Can we send this every time
    regardless?**

> Yes.

25. **Truck Manifest Submission by Carriers Draft -- Version 1d #64
    service types. On what are you basing "Conditional" ? Can you please
    provide more information on this?**

> Condition: If the shipment is being delivered under one of the listed
> service types, then the appropriate service type must be reported;
> otherwise, do not report the service type.
>
> **CG** Ground
>
> **DS** Door Receive (Door to Door)
>
> **CD** Collect on Delivery
>
> **DC** Delivery Confirmation
>
> **EV** Excess Value Insurance
>
> **SD** Saturday Pickup (Delivery)
>
> **ON** Overnight
>
> **ND** Next Day (1 Day Service)
>
> **IZ** International Second Day (2 Day Service)

26. **Truck Manifest Submission by Carriers Draft -- Version 1d
    #65\...firms code. Are you looking for this on ALL shipments that
    move in bond to indicate there destination location?**

> Yes.

27. **Truck Manifest Submission by Carriers Draft -- Version 1d #66
    entry #. Would this be in the situation where the broker pre-files
    the entry but does not have the carrier's shipment #. If the carrier
    sends in the entry \# then it matches up in the CBP system.**

> Yes (In the ACE Secure Data Portal this is captured if you select
> Shipment Type -- BCS)

28. **Truck Manifest Submission by Carriers Draft -- Version 1d #67
    estimated date US Exit. As a carrier, we will often not know this.
    How close does this estimated date need to be?**

> There are no established guidelines for this data element.

29. **Truck Manifest Submission by Carriers Draft -- Version 1d #68
    Boarded Quantity\....handling units or pieces? Often freight is
    tendered to us as shipping units however the CBP document will
    reflect the actual piece count**

> The carrier must transmit the quantity of the lowest external
> packaging unit; containers and pallets are not acceptable manifested
> quantities.

30. **Truck Manifest Submission by Carriers Draft -- Version 1d #70 FDA
    confirmation indicator.**

> **Are you looking for the PN#?**
>
> No
>
> **30.a** **We often do not have this as it is the Importer / Shipper /
> Broker that currently communicates this to FDA. We currently confirm
> that Prior notification has been done and if we are verbally advised
> that it is, we will proceed to the border.**
>
> A "Y/N" flag is only required if a shipment is proceeding In-bond.

31. **Truck Manifest Submission by Carriers Draft -- Version 1d #71
    Entry Type Indicator? Does this only pertain to express releases and
    in bond only?**

> The ANSI data element M1201 is to be reported when claiming In-bond
> I.E., I.T. or T&Es (or UN/EDIFACT DOC Segment, CC002/1000).

32. **Truck Manifest Submission by Carriers Draft -- Version 1d #79
    Value. Is the value for an IT estimated or actual?**

> Actual if you have it, estimated if you don't.

33. **Truck Manifest Submission by Carriers Draft -- Version 1d #77
    VIN\...what if a motorcycle is shipped in one shipment with other
    goods\...the VIN \# will be sent for the shipment but not specific
    to that commodity line. Is that ok?**

> Yes, or you could send seperate commodity lines.

34. **Truck Manifest Submission by Carriers Draft -- Version 1d (page 21
    of 44) the top of this section shows 'Shipment Commodity
    Characteristics -- multiple occurances per commodity is applicable'.
    We may not have the breakdown by commodity the same way the broker
    will. Is this going to cause any problems? (value, vin#, country of
    origin are all in the section but will not be broken out by
    commodity\...does this create a problem)**

> Manifest descriptions do not have to corrolate with a broker's entry
> line items.

35. **Truck Manifest Submission by Carriers Draft -- Version 1d #80
    Country of Origin. Is the carrier going to report country of
    origin?**

> Country of origin is only required when claiming a Section 321 release
> type.

36. **Truck Manifest Submission by Carriers Draft -- Version 1d \# 91
    Party type:Are you looking for every party to the bill? Which are
    mandatory?**

> Shipper and Consignee are madatory on a Standard Manifest. Importer is
> also mandatory if you are filing a FAST manifest. Other parties
> reported on the Pro-bill should be reported.

37. **Truck Manifest Submission by Carriers Draft -- Version 1d Foreign
    Port of destination 101\...shipment from Toronto to California abc
    warehousing. In many cases we don't know the foreign port of
    destination.**

> Then you would be requesting an I.T. instead of a T&E. Only a T&E and
> an I.E. require "Foreign Port of Destination".

38. **Truck Manifest Submission by Carriers Draft -- Version 1d 104.
    Onward carrier. Can you provide a definition of what you consider an
    "Onward Carrier"?**

> The MMM Data Matrix provides for a bonded carrier ID, onward carrier,
> and transfer carrier.  In the truck manifest ANSI X12 standard, these
> 3 items are found in the M12 segment of the 309 data set.  This record
> is used in creating an authorized movement.  The bonded carrier ID and
> the transfer carrier are both IRS numbers used to designate the
> carrier assuming liability for the shipment in the movement.  The
> onward carrier is the SCAC of the carrier to whom the shipment is
> transferred beyond the initiating carrier. When an importing carrier
> wants to move his shipment inbond and wants to designate another
> carrier who picks up the shipment at the first US port of arrival for
> transport to destination, he provides that carrier\'s SCAC in M1207
> and the IRS of that carrier in M1209.  In M1208, he supplies the code
> \'BI\' for bonded carrier ID, to show that the carrier assumes
> liability for the in-bond movement.  This is current procedure in sea
> and rail AMS, and is unchanged in truck manifest.

39. **Truck Manifest Submission by Carriers Draft -- Version 1d 105
    Transfer carrier Can you provide a definition of what you consider a
    "Transfer Carrier"?**

> If the importing carrier initiates a local movement (PTT) in his bill
> data, and is not the carrier who will carry the shipment to the local
> destination, he cites the IRS number of the carrier who will, in
> M1209.  In M1208 he will supply the code \'TRC\' for transfer
> carrier.  This could be the cartman, lighterman, or other trucking
> company assuming liability for the local move. As PTT is not in
> Release 4, this feature is for future use.
>
> EDIFACT: CUSCAR: For transfer carrier or in-bond carrier (onward
> carrier), the EIN is supplied in the NAD Segment, position 0540,
> C082/3039. The carrier is identified by either \'GC\' for a bonded
> carrier or \'CH\' for a transfer carrier in DE 3035 of the same
> segment. For onward carrier, the SCAC is supplied in the NAD Segment,
> position 0540, C082/3039 with \'OCG\' in DE 3035.

40. **Truck Manifest Submission by Carriers Draft -- Version 1d 106
    Harmonized number for export via vessel. Often we don't know if some
    are going to be exported by vessel or not.**

> Then we assume you would file a I.T. instead of a T&E.

41. **We are looking for some additional information on electronic
    In-bonds that explains how the process works.**

> For information on QP/WP we refer you to the In-bond section of the
> Customs and Trade Interface Requirments (CATAIR). This can be
> downloaded from CBPs web site.
>
> There is also a great deal of information on CBPs web site with regard
> to the Customs Automated Forms Entry System.
>
> ANSI Data requirments for in-bond requests via Truck Manifest are
> specificed in the M12 sgement of the ANSI X12 309 set. The M15 segment
> of the 353 is used to report the arrival of an in-bond at its U.S.
> Port of Destination.
>
> UN/EDIFACT requirements for inbond data are found in the following
> segments of the CUSCAR:
>
> Inbond 7512 number: DOC Segment, position 0365
>
> Inbond type: DOC Segment, position 0365
>
> Inbond control number: DOC Segment, position 0365
>
> Inbond destination: LOC Segment, position 0410
>
> Transfer destination FIRMS code: LOC Segment, position 0410
>
> Estimated date of US exit: DTM Segment, position 0480
>
> To report an inbond arrival at destination, the CUSREP is used.
> Inbound data is found in the following segments:
>
> Inbond control number: DOC Segment, position 0160
>
> Inbond destination: LOC Segment, position 0190

42. **What happens when a driver arrives at the border and his PAPS are
    not set up?**

> The truck would be sent to secondary where the driver would contact
> the broker.

43. **What happens during system outages?**

> CBP policy to be determined.

44. **How do we handle TIB's?**

> TIBs filed in ABI will be matched to the manifest via the Shipment
> Control Number for release. This would be identified in the Carrier's
> Manifest as a Release type PAPS. The carrier is not expected to
> pre-determine the varity of entry types that a broker can file i.e.
> Quota Visa, Antidumping Countervailing duty, or TIBs.

45. **Truck Manifest Submission by Carriers Draft -- Version 1d This
    document shows Importer of record to be a mandatory data element
    however the Guide to Electronic Data Interchange (Version 5) show it
    to be mandatory only on FAST shipments. Can you please verify?**

> Importer of Record is mandatory only on FAST shipments; it is optional
> on Standard manifests. The carrier will identify the importer of
> record on BRASS shipments by supplying the appropriate C4 code or bar
> code.

46. **When we are participating in the Automated Manifest, what
    documents are actually required to be with the driver at the time of
    crossing? Bill of lading, Commercial invoice, certificate of origin
    etc, 7533?**

> Until CBP announces a change in policy, all documentation currently
> required should be with the driver at the time of crossing.

47. **When we are transmitting electronically, how will this work with
    the CFS station we currently use in Buffalo? Currently we fax
    documents to the broker, the driver drops off the original documents
    and the 7533 at the border, and then proceeds to our CFS. When CBP
    has processed the trailer, they fax the 7533 to our Buffalo location
    indicating which shipments are released and which are not. I am not
    sure that I am clear on how this will work when we are electronic.**

> The CBP inspector will authorized to move to the CFS. (no electronic
> request or authorization will be sent in Release 4 time frames) You
> will be required to hold the cargo until the shipments are released.
> You will recieve electronic release and hold messages electronically.
>
> **48. In the event that there are 2 trailers (28 ft pups), is there
> any requirement to show what shipments are physically loaded on each
> trailer?**
>
> Yes
>
> **49. Can a 309 message be sent as a standard and then changed to a
> preferred by simply updating the 309 or are we required to cancel the
> 309 and send an original add message showing it as preferred?**
>
> Currently a FAST transaction can only be sent directly to FAST and
> will be processed as a preferred release in ACE if the truck crosses
> at an ACE port. FAST currently only supports EDIFACT message sets.
>
> **50.** **Is there any ability to send a 309 as a standard and then
> when the 358 is sent, if all shipments on the conveyance are FAST,
> then simply report the 358 as preferred?**
>
> No
>
> **51. VEH21 & VEH 22  \--  ACE ID \-- if we are not using the portal
> (we will be using EDI), is this required?**
>
> No. However if you do not pre-register your conveyance details, in
> your ACE account, then you will be required to supply all conveyance
> details with each manifest transmission.
>
> **52. VID10 Load/Empty status code.  Is this required on all equipment
> (trailers) moving to the U.S.?**
>
> The VID10 is only reported when you have Instruments of International
> Traffic inside a trailer or container. A totally empty trailer or
> container is not to be reported in "ACE eManifest: Trucks (Release 4)"
> as an Instrument of International Traffic. 
>
> **52a. However it then does not show a loaded or empty indicator, it
> shows\...**
>
> **I               Instrument of International traffic**
>
> **Are you looking for the \'I\' indicator to show if there are any
> IIT\'s on board**
>
> Yes.
>
> **53. Are you looking for an empty or loaded indicator? **
>
> No, the absence of shipments and IITs will be construed to mean the
> equipment or conveyance is empty.
>
> **54. CII05 \-- Conveyance Insurance Policy Value.  Should this value
> be stated in U.S. Funds? **
>
> Yes. A carrier must have acceptable levels of public liability
> coverage (see web site for prescribed amounts) to operate in the U.S.
> <http://www.fmcsa.dot.gov/>
>
> **54a. If yes, at what exchange rate?**
>
> FMCSA requires carriers to maintain insurance or surety companies to
> be licensed or authorized to issue policies and bonds in the U.S.
> state that the carrier will operate in. The value that is reported to
> the state would be the value that you would use.
>
> **55. Truck Manifest Submission by Carriers Draft - Version 1d #36
> party middle name, if present.  Present where?  On their
> identification /** **FAST** **card, birth certificate in our system?**
>
> Middle name or initial is required if the person has a middle name.
>
> **55a. Can I assume that if it is on any piece of identification then
> it is a requirement that it be part of the EDI message?**
>
> Yes
>
> **55b. Will the initial suffice?**
>
> An initial is acceptable but not prefered.
>
> **56. NM109 Crew/Passenger ACE ID and ACE proximity card ID.  If we
> are not using the portal (using EDI), then is this data required?**
>
> No, However, if the driver has a FAST proximity card it would be much
> more advantagious to report it. If your driver does not have a
> proximity card and you have not stored their details in your ACE
> carrier account then you must supply crew and passenger details with
> every ACE eManifest.
>
> **57. Travel Document Type.  Permanent Resident Card.  Can this mean
> Permanent Resident of Canada?  (just want to be sure that this is not
> just for those that are permanent residents of the U.S.)**
>
> No, this is a Permanent Resident Card in the U.S.
>
> **58. VID17  Equipment ACE ID.  Please confirm that if we are not
> using the Portal (using EDI), then is this data element required?**
>
> VID17 is not required if you are sending all equipment details.
>
> **59. VID18 IIT\'s. I am unsure why this is part of the 358 message.
> If we have an LTL trailer with 25 shipments of which 2 are IIT\'s one
> is covered by the Importer\'s bond and one is covered by the Carrier's
> bond, how will we indicate in the 358 message which particular cargo
> is covered by the carriers bond and which is covered by the Importers
> bond? If they were both covered by the Importers bond, how will USCBP
> know which shipments (309\'s) are IIT\'s?**
>
> The Instruments of International Traffic (IITs) can be reported in the
> VID segment of the 358 if the IITs are located in a piece of equipment
> but not related to a specific shipment. IITs can be reported in the
> VEH segment of the 358 if the IITs are associated with a particular
> conveyance (i.e. box truck) and not a piece of equipment or shipment.
>
> If you wish to report IITs for shipments it must be done in the 309
> set in the VID segment under the M11 shipment identifier (bill of
> lading/Shipment Control Number).
>
> Whether the bond that covers the IITs is the importer's bond or the
> carrier's bond is indicated in the VEH23 or the VID18 element with one
> of the following codes.
>
> C Indicates party whose bond is obligated for the release of
> instruments of international traffic- empty IIT's covered by the
> Carrier's bond. In standard manifests, this indicates shipments
> consisting solely of empty IIT's covered by Carrier's bond
>
> I Indicates party whose bond is obligated for the release of
> Instruments of international traffic.- empty IIT's covered by the
> importer's bond. In standard manifests, this indicates shipments
> consisting solely of empty IIT's covered by importer's bond Indicates
> party whose bond is obligated for the release of international traffic
> -- merchandise and IIT's covered by the carrier's bond. In standard
> manifests, this indicates a shipment consisting of merchandise and
> IIT's. IIT's covered by carrier's bond.
>
> B Indicates party whose bond is obligated for release of instruments
> of international traffic- merchandise and IIT's covered by the
> importer's bond. In standard manifests, this indicates a shipment
> consisting of merchandise and IIT's. IIT's covered by importer's bond.
>
> **60.  Assuming that we choose to send** **the 309 preliminary
> message, and then when the load is complete, we will send the 358
> followed by the 353.  Are the following Data Elements, required on the
> 309 message?**
>
> **       ** **P401 Port of Entry**
>
> **       ** **P402 Estimated Date of arrival to Port of Entry**
>
> **       ** **P405 Estimated Time of arrival to Port of Entry**
>
> Yes

**       **        

> **61.  N901 Reference Identification\...can you please provide some
> additional information for this.  Is this required?  When is it
> used?**
>
> The N901 is a qualifier for the N902.
>
> If you will be identifing a customs broker or entry filer to whom you
> wish to have shipment data forwarded via the 'Broker Download"
> functionality then you would use qualifer 8S in the N901 and report
> the filer code, port code and office code in the N902.
>
> If your shipment type is 63 (Immediate Export) and the merchandise is
> being exported to Mexico then you are required to report FEN in the
> N901 and the Mexican Pedimento number in N902.
>
> If you anticipate that the entry filer (broker) is not going to report
> a shipment control number (Pro-bill) in their entry you can report the
> entry number with the shipment record by reporting the N901 as BEN and
> reporting the actual entry number in the N902 record. This would
> enable ACE to link the entry with the shipment record.
>
> N901 qualifiers OB and SI are for future use. It is anticipated that
> N901 qualifier SI will be used to report the FAST required "Shipment
> Identifying Number (SID)" which is refered to as the "Trader Reference
> Number" in FAST

** **

> **62.  N902  Reference Identification  **
>
> **Routing \# (filer code 3 digits, port code 4 digits office code 2
> digits)**
>
> **       Is this used for the broker download?**
>
> Yes, however the order is port -- filer code -- offices code.
>
> **62a. Where does one obtain the office codes, 2 digits?  Are these
> assigned by Customs?**
>
> The office code is rarely used. It is only used when a broker uses two
> versions of the same ABI software in the same city. You would have to
> obtain it from the Broker. The purpose is so that the message gets
> directed to the proper computer. The broker may have an airport office
> and a landborder office, both using seperate dial up communications.
>
> **63. What happens if there are 2 drivers in the truck and only one
> has a FAST ID, are we then required to provide the N301, N302, N401,
> N402\... or are we exempt because there is a driver in the vehicle who
> has a FAST ID?**
>
> The second driver's details will need to be sent.
>
> **64. 358 Amendments. Scenario: a number of 309P's have been sent. The
> 358 and the 353 has been sent. Now there is an equipment change. Are
> we required to send an amendment to the 358 or an amendment to the
> 309?**
>
> If the 353 has not been sent, update the 358, but if the 353 has been
> sent then amend the 358 with an amendment code.
>
> **65. M1109 BOLType Code.**
>
> **65a. 00 -- Regular bill -- Is this the code for a PAPS?**
>
> Yes
>
> **65b. "24 Single Entry Per C4 Line Release" please clarify.**
>
> Use this when one entry number is to be generated for each C4 code
> within a shipment.
>
> **"25 Individual Entry for Multiple C4 Line Releases" please
> clarify.**
>
> Use this when one entry number is to be generated for multiple C4
> codes.
>
> **65c. 34 -- Preferred PAPS**
>
> Not initially supported in Release 4
>
> **66. M1204 -- Port of Destination -- Should this be Schedule D?**
>
> Yes
>
> **67. M1204 -- Foreign Port of Destination -- Should this be Schedule
> K?**
>
> Yes, only required for T&Es and I.E.s
>
> **68. H105-HAZMAT contact, H111 -- telephone number. Are these fields
> required if HAZMAT is present?**
>
> Yes
>
> **69. Firms codes -- Will these be necessary for all US terminals
> where bonded freight may be destined?**
>
> Yes
>
> **70. If a PAPS pre-filed entry fails what happens to the "advanced
> information" clock" Does it start/stop, start over, or\...?**
>
> The clock would not start over because the carriers filing of the
> electronic manifest is sufficient to satisfy the advance cargo
> information rule.
>
> **71. Port of Loading -- How is this applied in the LTL and relay
> environment?**
>
> Port of Loading is the location where the cargo was physically loaded
> on the trailer that is dispatched to the border.
>
> **72. Pre-carrier -- What is the definition for an LTL truck
> environment?**
>
> Advance Connecting Line.
>
> **73. Will 357 messages be available at ACE pilot implementation?**
>
> No. The 357 is used for requesting subsequent in-bond moves. ACS will
> remain the system of record for in-bond moves throughout Release 4 and
> 5.
>
> **74. Once we close out with the 353 on the multi-step process
> (standard shipments), can we send an amendment? If so, which
> transaction set is used?**
>
> Yes. Use the transaction set that you wish to amend. The M13 records
> exist in both the 309 and 358.
>
> **75. If 309 is done, but the 358 hasn't been sent, can we go back and
> do an update to the 309 for a change? Or does it need to be an
> amendment before the 358 is sent?**
>
> If the 309 is preliminary, the carrier can update the shipment via the
> 309 without providing an amendment code in the M13.  If the trip has
> been created via the 358, and the shipments attached, a shipment may
> still be updated via the 309 set without an amendment code in the
> M13.  If the manifest has been completed and submitted and a 353 has
> been sent confirming this, a shipment can still be updated via the
> 309, but an amendment code must be submitted in the M13. 
>
> Shipments can be added or delinked in the 358 set via the M13 segment
>
> **76. Travel documents -- Does what the company transmit as travel
> document(s) get compared to what travel document(s) the driver present
> at the border? If they are not identical (e.g. transmission was for
> CDL and passport, but driver presents CDL and birth certificate. What
> will happen?**
>
> The transmitted travel document may be compaired to the documents
> presented by the driver at primary. The driver may be refered to
> secondary to resolve any discrepancy.

> **77. What exactly is a Permanent Resident Card?**
>
> A Permanent Resident Card, commonly known as a Green Card, is evidence
> of your status as a lawful permanent resident with a right to live and
> work permanently in the United States. It also is evidence of your
> registration in accordance with United States immigration laws. The
> Permanent Resident Card is also called USCIS Form I-551.
>
> **78. In-transits from Canada thru US to Canada\... will existing
> paper processes remain or will ACE Release 4 provide electronic
> method?**
>
> Existing paper processes will remain.
>
> **79. There isn't a BOL Type Code for US Government shipments\... how
> should these be indicated in the 309 message.**
>
> US government shipments are an ABI entry type 51 which would be
> indicated as PAPS with the expectation of the entry being filed via
> ABI. Truck manifest does not expect the carrier to know ABI entry
> types such as quota visa, antidumping/countervailing duty etc.
>
> **80. If there is an invalid BRASS C4 code entered in the 309, will a
> "C4 code is not valid" message be received by the carrier in responce
> to the 309 being sent?**
>
> Yes. Please refer to the error codes in the 355 set, first K1 segment.
>
> **81. Link a shipment to a Trip (Send amended 358?) What if the 353
> has or has not been already sent?**
>
> If the original 358 set has been sent, send another 358 with code
> \'Y\' in the M1009.  This signifies an amended trip mesage.  Use the
> M13 segment,  provide the bill number being added, and submit code
> **"A\"** in M1303.  If the 353 has also been sent the procedure is the
> same, but an amendment code is required in the M13 segment.
>
> **82. De-Link Shipment from a Trip (Again, Send amended 358?)  What if
> the 353 has or has not bee already sent?**
>
> If the original 358 set has been sent, send another 358 with code
> \'Y\' in the M1009.  This signifies an amended trip mesage.  Use the
> M13 segment,  provide the bill number being added, and submit code
> **"D\"** in M1303.  If the 353 has also been sent the procedure is the
> same, but an amendment code is required in the M13 segment.
>
> **83. Cancel Trip and Cancel Shipments (All in one 358, or 309\'s
> first followed by 358)**
>
> Use 358 set code \'3\' in M1009.  This will cancel the trip and
> de-link the shipments.  Shipments may be deleted in the 309 set with a
> code \'Y\' in the M1009.  Use the M13 containing the bill number and
> code \'D\'.  You may use multiple M13\'s per 309 set to delete all
> bills that were in the trip.
>
> **84. Cancel Trip and De-link Shipments (All in one 358, or 309\'s
> first followed by 358)**
>
> Use 358 set code \'3\' in M1009.  This will cancel the trip and
> de-link the shipments. 
>
> **85. Cancel Shipments - Do we need to do this if they will never
> cross the border?**
>
> Yes you should cancel shipments if cargo will never cross the border.
>
> **86. Delete Dormant Manifest** **- Again, do we need to do this if
> the Trip will never cross the border?**
>
> Yes you should cancel Manifests if trips will never cross the border.
>
> **87. What happens if you transmit a complete 309 with multiple
> shipments and one shipment is rejected? Is the manifest still
> complete?**
>
> No. A complete 309 undergoes complete manifest edits when the 309 is
> transmitted, and the manifest is considered \'submitted\'. If a
> shipment is rejected, the other shipments are accepted, but the
> manifest reverts to a \'"Preliminary" status. The carrier must make
> the correction to the rejected shipment, retransmit it, and then send
> a 353 set to indicate the manifest is complete and submitted. If this
> is not done, the manifest will not be in the system and available to
> CBP when the truck arrives at the border.
>
> **88. What disposition code from CBP says that the shipment has been
> placed In-bond within the 350 transaction?**
>
> Data element X407 Bill of Lading disposition Code "1J".
>
> **89. Likewise what code says it has been cleared and available for
> delivery?**
>
> Data element X407 Bill of Lading disposition Code "1C".
>
> **90. What code needs to be sent by the carrier to CBP saying that the
> shipment has arrived at the bonded to destination?**
>
> A 353 set is used to report the arrival of an in-bond move. An in-bond
> movement arrival can be reported by supplying the In-bond number,
> Shipment Control Number (Bill number) or Equipment number. This status
> is reported in the M1501 record
>
> 1 Arrival by In-bond Number at port of discharge/in-bond arrival
>
> 2 Arrival by Bill of Lading Number at port of discharge/in-bond
> arrival
>
> 3 Arrival by Equipment Number at port of discharge/in-bond arrival
>
> **91. The Quantity field in the 350, X402, says that CBP may send a
> partial release.  Can you explain this a little more in detail?**
>
> Piece count is important. If a broker files entry for a quantity of 50
> cartons and the manifest record reports 100 cartons for the same
> shipment then only 50 of the 100 cartons have been released.