Entry Response Explanations<accepted> <entry-no>ABC-0000001-1</entry-no> </accepted>
This, however does not mean the entry was accepted by customs. It only states that the entry has been successfully uploaded into the system. If you include the <transmit> tag, the response will also include the following:
<accepted> <transmitted /> <entry-no>ABC-0000001-1</entry-no> </accepted>
or:
<accepted> <not-transmitted>entry contains errors</not-transmitted> <entry-no>ABC-0000001-1</entry-no> </accepted>
An accepted entry may also include warnings. They would be returned as follows:
<accepted> <warning>Warning message appears here</warning> <entry-no>ABC-0000001-1</entry-no> </accepted>
For Type 86 entries, additional warnings have been added to help assist brokers to be compliant with CBP regulations. The following checks have been put into place:
1. If a description is used that matches our internal list of generic descriptions, we will give a warning to update the description to be more specific. (e.g. Items would be a generic description that CBP might flag)
2. If a description is used for multiple different HTS codes in the upload, our system will throw a warning to make each tariff have a unique description.
3. Each tariff needs a description. If there is not one, the system will throw a warning to inform the user.
4. Chapter 98 tariffs are invalid for type 86 entries.
5. The consignee name will be checked against a list of invalid consignees provided by CBP.
6. Check if the weight to value ratio (weight per kilogram / value in dollars) is greater than 1.
7. Check to see if the preparer port is required or invalid
These warnings could be configured to "Informational", "Error", or "None" under Account -> Preferences -> Broker Preferences.
1. Information - The system will create the entry and provide the warnings as shown in the example below
2. Error - The system will not create the entry and provide the cbp-warnings inside a <rejection> tag
3. None - The system will not check for these warnings at all.
The system will report these errors in the <cbp-warning> tag as a direct child of the <accepted> tag. The below is an example with the "Informational CBP Warnings" setting and the Entry Number in the request.
<accepted>
<warning>Existing warning message appears here</warning>
<entry-no>ABC-0000001-1</entry-no>
<cbp-warnings>
<entity-warning>
<entity-type>ENTRY_NUMBER</entity-type>
<entity-id>ABC-0000001-1</entity-type>
<warning>
<type>hts-duplicate-description</type>
<description>Multiple HTS cannot contain same Description</description>
<invalid-item>HATS</invalid-item>
</warning>
<warning>
<type>hts-generic-description</type>
<description>HTS has a generic Description</description>
<invalid-item>ITEMS</invalid-item>
</warning>
<warning>
<type>hts-value-ratio</type>
<description>
The Value to Weight ratio must not exceed 1.0 KG per dollar
</description>
<invalid-item>220.0</invalid-item>
</warning>
<warning>
<type>invalid-consignee</type>
<description>The consignee is invalid</description>
<invalid-item>CRAZY GRANDMA</invalid-item>
</warning>
<warning>
<type>preparer-port</type>
<description>The Preparer Port is Required</description>
<invalid-item></invalid-item>
</warning>
</entity-warning>
</cbp-warnings>
</accepted>
An example with the "Error CBP Warnings" setting and with the system genenerated entry number in request
<rejected>
<cbp-warnings>
<entity-warning>
<entity-type>INVOICE_NUMBER</entity-type>
<entity-id>12345</entity-type>
<warning>
<type>hts-duplicate-description</type>
<description>Multiple HTS cannot contain same Description</description>
<invalid-item>HATS</invalid-item>
</warning>
<warning>
<type>hts-generic-description</type>
<description>HTS has a generic Description</description>
<invalid-item>ITEMS</invalid-item>
</warning>
</entity-warning>
<entity-warning>
<entity-type>NO_ID</entity-type>
<entity-id></entity-type>
<warning>
<type>invalid-consignee</type>
<description>The consignee is invalid</description>
<invalid-item>CRAZY GRANDMA</invalid-item>
</warning>
<warning>
<type>preparer-port</type>
<description>The Preparer Port Should match the Account Processing Port</description>
<invalid-item>3001</invalid-item>
</warning>
</entity-warning>
</cbp-warnings>
</rejected>
The entity-type has the following valid values for the Entry Web Service -
1. ENTRY_NUMBER - This will be used if the xml provides a entry number in the request
2. INVOICE_NUMBER - This will be used if there is no entry number in xml and the error is in the invoice
3. HOUSE_BILL - This will be used if there is no entry number in the xml and the issue is outside of the Invoice (i.e. invalid consignee)
4. NO_ID - This will be used if there is no entry number in the request, the error is outside of the invoice, and there is no House bill
*** If entity-type is ENTRY_NUMBER, the entity-id will be {Filer Code}-{Entry Number}-{Check Digit} (i.e. ST9-1000001-1). ***
Each Request could have multiple entity-warning tags if the entry number is not specified in request
If there are problems, they will be in the following forms:
<rejected>username/password invalid</rejected>
<rejected>
<validation-error>
Line 31: cvc-complex-type.2.4.a: Invalid content was found starting with element
'bad-tag'. One of '{"http://www.netchb.com/xml/entry":entry-no,
"http://www.netchb.com/xml/entry":precalculated}' is expected.
</validation-error>
</rejected>
<rejected>duplicate entry number</rejected>
<rejected>
importer not found - an importer with tax id 11-12345678 must be in the user's importer table
</rejected>
<rejected>you do not have sufficient privileges</rejected>
<error><!-- A stack trace would be included here --></error>