Skip to main content
US Foreign-Trade Zone (FTZ) Management
Search
Search ONESOURCE Global Trade Support Help and Support.

This article applies to:

  • Product: ONESOURCE Global Trade
  • Sub-Product: US Regimes & Connectivity

FTZ Management: Appendix - e214 Example Responses and Valid Modes of Transportation (CATAIR)

Example 1: CBP Acceptance, Paperless Authorization of Admission

User
CBP
Status in IP FTZ
Transmit e214 to CBP
N/A
TRANSMITTING
e214 successfully transmitted
N/A
TRANSMITTED
Receive response from CBP
Acceptance (B1 data passes all edits)
ACCEPTED
important
If the e214 is a Replace transmission, there will be a delay (up to 48 hours) for the CBP officer to review and respond to the request. The below will occur on Replace 214s only if the request is approved.
RAP (request approved) or RDE (request denied)
POSTING MESSAGE
Receive response from CBP
Paperless Admission (B4)
ACCEPTED
Receive response from CBP
Admission Authorized (BF Goods)
READY TO CONCUR
Transmit e214 Concurrence to CBP
N/A
TRANSMITTING
Concurrence successfully transmitted
N/A
TRANSMITTED
Receive response from CBP
FZ Data Accepted (B6 – concurrence accepted and Bills of Lading will post)
ACCEPTED
Receive response from CBP
Admission Number Concurrence (B8 – manifest quantity of each Bill of Lading on e214 posted to AMS)
FINAL
Receive response from CBP
Bill of Lading Concurrence (B9)
POSTED

Example 2: Post Admission Correction Response

User
CBP
Status in FTZ Management
Transmit Post Admission Correction to CBP
N/A
TRANSMITTING
PAC successfully transmitted
N/A
TRANSMITTED
Receive response from CBP
Acceptance (B6 data passes all edits)
ACCEPTED
Receive response from CBP
important
There will be a delay (up to 48 hours) for the CBP officer to review and respond to the request
JAP (request approved) or JDE (request denied)
ACCEPTED or REJECTED

Example 3: CBP Acceptance, Documents Required Before Admission is Authorized

Note: Common reasons documents may be requested are for Census warnings or screening/targeting hits for consideration.
User
CBP
Status in IP FTZ
Transmit e214 to CBP
N/A
TRANSMITTING
e214 successfully transmitted
N/A
TRANSMITTED
Receive response from CBP
Acceptance (B1 data passes all edits)
ACCEPTED
Receive response from CBP
Documents Required (B5)
ACCEPTED-ACTION REQ
Provide 214 package to CBP. Port inspectors can authorize at their discretion without paperwork
N/A
ACCEPTED-ACTION REQ
Receive response from CBP
Review documents, authorize for admission (BF Goods)
READY TO CONCUR
Transmit e214 Concurrence to CBP
N/A
TRANSMITTING
Concurrence successfully transmitted
N/A
TRANSMITTED
Receive response from CBP
FZ Data Accepted (B6 – concurrence accepted and Bills of Lading will post)
ACCEPTED
Receive response from CBP
Admission Number Concurrence (B8 – manifest quantity of each Bill of Lading on e214 posted to AMS)
FINAL
Receive response from CBP
Bill of Lading Concurrence (B9)
POSTED

Example 4: CBP Rejection

After an e214 is transmitted to CBP (status in system is TRANSMITTING or TRANSMITTED), the e214 could potentially be rejected by CBP. Should this occur, the disposition code will be B3 – Data Does Not Pass CBP Edit Checks. This will show as REJECTED in FTZ Management. See the below table for a list of common reasons why CBP may reject an e214.
Common Reasons for CBP Rejection
Description
Bill of Lading Number Missing/Invalid
The submitted Bill of Lading Number does not match the Bill of Lading Number in AMS. Common root causes for this error are a typo or wrong SCAC.
Bill/In-Bond Not On File
The submitted SCAC does not match the SCAC code on the IT Number. Invalid SCAC Wrong format, wrong code.
Invalid SCAC
Wrong format, wrong code.
Invalid Voyage/ Flight/Trip Number
More or less than the required 4 characters were entered.
To find out why the data was rejected:
  1. Click
    Detail
    .
See below a screenshot of an e214 that was rejected because the Bill of Lading was not on file.
Contact the carrier (as needed) to determine the root cause for the error and gather the correct data. Make corrections to the data and re-generate the e214. If the error has been resolved, the transmission, acceptance, concurrence, and finalization process will go forward as normal.

Example 5: Census Rejection

In this example, the e214 was transmitted to CBP. Although the data passed CBP validation, a Census error has occurred. Should this occur, the disposition code will be B2. This will show as ACCEPTED-W/WARNING in FTZ Management. ACCEPTED – ACTION REQ may also appear, indicating further paperwork is needed to resolve the issue.
See the table below a list of common reasons why CBP may reject an e214.
Common Reasons for Census Rejection
Description
*CENSUS*INVLD NON-AIR NON-VSL MOT
There was a validation error comparing the Port of Lading to the Mode of Transport.
*CENSUS*EXCEEDING CHARGES
Aggregate charges do not relate to the value. Verify the accuracy of the reported charges.
  1. Click
    Replies
     on the e214.
  2. To find out what warnings are on the B2 disposition code, click
    Detail
    .
  3. An explanation for the disposition code is shown below. Click
    Details
     to view the remarks. This is a situation where Census has a problem with the data that has been sent.
  4. Make corrections to the data and re-generate the e214. If the error has been resolved, the transmission, acceptance, concurrence, and finalization process will go forward as normal.
Contact the carrier (as needed) to determine the root cause for the error and gather the correct data.
The
READY TO CONCUR
 status may also be received prior to the resubmission of the e214, provided CBP authorizes after receiving the Census error and requested documents.

Example 6: BOL Messages (Can be received for all scenarios)

During the processing of an e214, messages regarding the status of the Bills of Lading (Master and House) on the e214 may be received. Depending upon the message, action may or may not be required. These messages may be received at any point during the process examples above.
If a message is received, the FTZ Status will update to
POSTING MESSAGE
. Should this occur, view the details of the message in order to determine if action is needed.
Common Reasons for Bill of Lading Messages
Authorization was delayed. This may occur in cases where a Documents Required message is received and manual intervention is needed by CBP in order to obtain authorization.
There is a CBP program issue involving closure of the Bill of Lading.
The notifications generated as the result of concurrence transactions submitted with a specified admission number (e.g. a copy of the notification to the carrier following a PTT will be received if the PTT specified the admission number).
Common BOL Messages from CBP
Description
Action to Take: Contact CBP Port Personnel and/or Carrier to Resolve Issue
N/A
1L
Bill of Lading is late; In-Bond is not closed; transit period expired. 30 days allowed from In-Bond origination until delivery at the FTZ.
1K
5 days until General Order (GO); In-Bond is still open. All goods must be received to close the In-Bond within 15 days after receipt at the FTZ.
1R
2 days until General Order.
1S
Ordered to General Order. Lay order has expired. CBP takes possession of user’s merchandise.
54
Carrier bill deleted. Bill of Lading has been deleted from the manifest.
55
Carrier bill added. Bill of Lading has been added to the manifest.

Valid Modes of Transportation

Modes of Transportation Codes
Description
10
Vessel, Non-Containerized
11
Vessel, Containerized
12
Border, Waterborne MX or CA
20
Rail, Non-Containerized
21
Rail, Containerized
30
Truck, Non-Containerized
31
Truck, Containerized
32
Auto
33
Pedestrian
34
Road, Other (Pedestrian, Animal)
40
Air, Non-Containerized
41
Air, Containerized
50
Mail
60
Passenger, Hand Carried
70
Fixed Transport (Pipeline and Powerhouse)
80
Not in Place
Canadian Provinces
Description
XA
Alberta
XB
New Brunswick
XC
British Columbia
XM
Manitoba
XN
Nova Scotia
XO
Ontario
XP
Prince Edward Island
XQ
Quebec
XS
Saskatchewan
XT
Northwest Territories
XV
Nunavut
XW
Newfoundland
XY
Yukon Territory

Related Content