Automated Export System (AES)

Document Image System Instructional Guide for Used Self-Propelled Vehicles

hkelly — Tue, 17 May 2022 18:02:46 +0000

Document Image System Instructional Guide for Used Self-Propelled Vehicles hkelly Tue, 05/17/2022 - 14:02

U.S. Customs and Border Protection plans to conduct a test to promote paperless processing of vehicle exports in an effort to expedite and modernize compliance review by allowing the submission of vehicle ownership documentation, currently required in 19 CFR 192, through the Document Image System (DIS). This modernization effort is intended to institute risk-based targeting of exports for field inspection and validation of ownership documentation in lieu of paper documentation review for every vehicle presented for export.

CBP will test the use of DIS for the submission of vehicle ownership documentation pursuant to 19 CFR 192 via the Automated Commercial Environment/Automated Export System. Participants will submit a readable PDF copy of documentation by email to CBP. The email will include the following data elements to be used by the system to store, search, and process the documents. Note that CBP reserves the right to request paper copies of the vehicle ownership documentation at any time during the test, at port discretion. For vehicles being exported by land, a copy may be required at the time of export to receive the CBP export processing stamp.

Data Elements in the Email Subject Line

Category (CBP09 for vehicle ownership documentation)
Internal Transaction Number
Action Code (Add, Delete, Replace)
CAT=GEN; ITN=X12345678910111; ACTION= ADD or REPLACE or DELETE

*Notes: Three identifier elements will go in the subject line as indicated above. Elements should be delimited by a semi-colon (;) and there should be no spaces before and after the ‘equal-to’ signs. Appendix B: General Guidelines for documents submitted to DIS via email lists multiple acceptable email subject lines. The subject line must contain the Internal Transaction Number as the second value. Vehicle title will not be considered submitted to CBP if any value; other than Internal Transaction Number, is entered. I.e., Bill of Lading, admission, or entry number.

Documents E-Mail Address

The email address to which computer readable PDFs of vehicle titles and other documentation required by 19 CFR 192, should be filed in accordance with current vehicle export filing deadlines (i.e. 72 prior to export; For air and sea environments, DIS submissions are only acceptable after the vehicle has been delivered to the port pending export; and for land environments, the DIS submission is required 72 hours prior to the vehicle arriving at the port to go foreign.) is: docs@cbp.dhs.gov.
- CBP can receive PDFs up to 10 MB in size.
- Upon submission of an email containing a .PDF used vehicle title, the above email address will generate an automated response email back to the sender. This response email will serve as the receipt for the filing.
- The PDF being submitted must have the naming convention, e.g., CBP09-ITN.pdf.

Required Data Elements

Data required in email to Automated Commercial System/Document Image System:
- START_DATA
- TRANSMITTER_NAME=Mandatory (Name of company)
- PORT_CD = (4-digit port code) Conditional (Required when responding to CEEs)
- HOUSE_BOL_NBR=Conditional (Required when sending Master BOL in subject line)
- POC_INFO= Optional (Name and Phone Number)
- COMMENT=Optional (Any clarification/remark)
- RETURN_EMAIL_ADDRESS=Optional (if different than sender email address)
- END_DATA
Rules of usage for “ADD, REPLACE, or DELETE” function:
- If the used vehicle title is a first-time submission, then set ACTION=ADD
  - If additional documents are required for the same submission,
  - Send another email with the same Key and set ACTION=ADD
- If a wrong document is submitted in error, i.e., wrong title, invoice, etc., and needs to replace with a new document.
  - Send an email with Key to be deleted and set ACTION=DELETE
  - Then another email with new PDF with same Key and set ACTION=REPLACE
- If the documents need to be deleted from a prior submission.
  - Send email for Key to be deleted and set ACTION=DELETE
- If the submission itself was sent incorrectly (ex. incorrect ITN) in a prior submission, then
  - Send an email with Key to be deleted and set ACTION=DELETE
  - Then send another email with the new Key and set ACTION=ADD
  - Note: the above term Key refers to the Internal Transaction Number.
- Participation in DIS Pilot:
  - Interested parties should contact their local CBP vehicle export processing office and express their interest and intent to participate in the DIS pilot.
  - Please see the Federal Register Notice for complete pilot details.
  - Complete details on formats and technical specifications necessary to transmit in DIS can be found in the Document Image System Implementation Guide.

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

Error Message Dictionaries/Lists

jwolford — Tue, 15 Feb 2022 19:33:13 +0000

Error Message Dictionaries/Lists jwolford Tue, 02/15/2022 - 14:33

This document provides guidance and explanations for errors returned on electronic data submitted to CBP via ACE.

The table below provides quick links to all of the existing ACE message error dictionaries. This table will be updated as changes are made to the underlying documents.

Error Code Subjects	Main Document Location	Notes
ACE 5106 Error Dictionary	ACE CATAIR Supporting Documents
Cargo Release Condition / Error Codes	ACE CATAIR Supporting Documents
ACE Drawback Error Dictionary	ACE CATAIR Supporting Documents
ACE NDD Error Dictionary	ACE CATAIR Supporting Documents
ACE CATAIR Error Dictionary	ACE CATAIR Supporting Documents
ACE CATAIR Appendix P - FTZ Error Messages	ACE CATAIR Appendix P
ACE CATAIR Appendix T - Common In-Bond Errors	ACE CATAIR Appendix T
PGA Error Messages	PGA Message Set Documents / PGA
ACE CATAIR Reconciliation Error Dictionary	ACE CATAIR Supporting Documents
ACE CATAIR Request Reroute (cbp.gov)	ACH-PMS CATAIR QX record Note 2	Errors are listed within the CATAIR chapter. Please see page S-RR-11
Statement Error Dictionary	ACE CATAIR Supporting Documents
ACE CATAIR (cbp.gov)	TIB CATAIR E1 record Note 2	Errors are located in note 2 of the E1 record. Please see page TIB-14
ACE AESTIR Appendix A - Commodity Filing Response Messages	AESTIR Appendix A
ACE Air CAMIR Appendix A: Codes	Air CAMIR (Appendix A)
ACE Ocean CAMIR Appendix H Common Errors	Ocean-Rail CAMIR (Appendix H)
CUSCAR Customs Cargo Report Message (cbp.gov)	Truck EDIFACT, X.12

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

Trade

AESDirect Technical Information

dsykes — Tue, 05 May 2020 20:46:30 +0000

AESDirect Technical Information dsykes Tue, 05/05/2020 - 16:46

The content below provides technical documentation related to filing export related content to CBP and the Automated Commercial Environment's AESDirect.

Close all Open all

AESWebLink Developers Kit

AESWebLink Submission

AESWebLink enables Internet application developers and providers to allow their users to pass data from their own third party applications into AESDirect. This makes it easier for end-users to enter data into AESDirect and eliminate double entry of data into both the third party application and AESDirect.

Third party (web) applications will have to be certified (authorized) to interface with AESWebLink by completing the AESWebLink certification process.

A third party web application that is certified to interface with AESDirect will be referred to in the following text as an "Enabled Application".

An Enabled Application is an application that is collecting data for other export-trade purposes and wants to give its users the ability to streamline their processes and eliminate double entry of information. AESWebLink is intended as a plug-in capability for sharing information between an AESDirect certified third party browser application and AESDirect, thus further streamlining export data capture and information flow, and reducing data entry.

In addition to allowing automated submission of a shipment to AESDirect, the AESWebLink interface also provides the ability to submit a status inquiry transaction. An inquiry transaction can be submitted at any time. The response to the inquiry will be a transaction from AESDirect providing the current status of the shipment and the AES ITN (if available at the time of inquiry).

Using this capability an AESWebLink provider can build into their AESWebLink client-side interface the logic and ability to both submit the shipment transaction and to then to enquire the status of the shipment. A key element of the inquiry transaction is the ITN issued by AES for the shipment.

It is important to understand that the ITN will only be available once the shipment has been submitted to AES by AESDirect and a successful acceptance received. Thus the AESWebLink provider should take this timing into account if submitting an automated inquiry to obtain the ITN.

This inquiry capability is of particular importance if the AESWebLink provider wishes to obtain the ITN back into their client-side application for logistical and compliance purposes.

This AESWebLink Developers Information contains the following Sections:

EDI Upload Process

When an AESDirect filing companies as been validated for the EDI Upload capability (by completing the EDI certification, or using pre-certified software), the EDI File Upload function will be activated for their AESDirect Account.

The filing company can use this function to upload files containing the shipments you wish to file with AESDirect.

To Upload a File containing shipments

After logging in to AESDirect select "EDI File Upload" on the Main Menu.
Click the "Browse..." button and use the Windows Browse function to select a file, and then click continue to upload it to AESDirect.
If the EDI file is successfully uploaded to AESDirect and accepted for processing a confirmation message will be displayed, e.g. "File upload successful" File "local path and file name" was uploaded as "remote file name with timestamp and account code" at "time and date"
If AESDirect was unable to upload the file successfully an error message describing the problem encountered will be displayed.

After your EDI file has been processed by AESDirect an e-mail will be generated by AESDirect to your E-Mail Response address. This e-mail will detail the results of AESDirect processing all of the shipments in your EDI file. This will include a report of any validation problems found, and confirmation of any shipments that passed all AESDirect validations and accepted by AESDirect.

Please Note:

Only shipments accepted by AESDirect are stored permanently and sent to AES.
Any shipment rejected by AESDirect will need to be corrected and re-submitted.
That a shipment delivered through an EDI Upload will automatically create USPPI and Consignee profiles.
Any shipment accepted through an EDI Upload will also be available for access through the AESDirect interactive functions.

Any shipment accepted by AESDirect will automatically be stored in AESDirect and sent to AES. For any AES responses received by AESDirect for accepted shipments an e-mail containing each response will be sent to your AESDirect E-Mail Response address.

AESDirect Testing Environment

Software developers can use the test environment to test bulk upload and weblink filings. The attached documents shows the step by step process.

General steps for this process include:

The user must login to ACE portal with their credential and have launched AES Direct application as they do normally and navigates to the AES Direct application. (Detailed steps provided in attached document)
The user navigates to the trade website as they normally do on a different browser tab and creates their shipment on the trade side. (Steps 1 & 2 are interchangeable)
User submits the filing data to the weblink API as form POST variables.
The user reviews the data and submits the form as they would do normally and submits the form.
After submission, the user will have an option to be redirected back to the trade website. The user will receive responses in email just like any submissions created through AESDirect.

The AESDirect Upload Test Files page includes links to three documents that contain sample test files for ADESDrecit WebLink Submissions, AESDirect AESTIR Submissions, and AESDirect X12 601 Submissions.

The AESDirect WebLink Test Process provides step-by-step instructions on logging into the test environment and sending a test filing.

The AESDirect Bulk Upload Test Process provides step-by-step instructions on logging into the test environment and submitting a bulk upload of EDI files.

Support

If you have technical issues filing in the new system, please contact the AES Help Desk at askaes@census.gov or 800-549-0595, option 1.

If you have technical issues with your ACE Accounts Access, please contact the ACE Service Desk at ACE.Support@cbp.dhs.gov or 1-866-530-4172, option 1, then option 2.

For information on how to sign up for an ACE Exporter Account, please visit the Getting Started page.

Frequently Asked Questions

Click here to view AESDirect FAQs

Q: I submit a filing using bulk upload I get the error saying ‘Exemption code is missing’. But when I open the filing in shipment manager, I see the code. Why?

A: The AESTIR specification requires that you transmit the license exemption code for certain license type codes in the Export License Number/CFR Citation/Authorization Symbol/KCP#/ ACM# (AESTIR CL2 record positions 65-76 or X12 X102 field). If your bulk upload file had spaces in this field and the license type code reported requires an exception code, AES will reject and generate a FATAL error. When you open the shipment in the filing manager, you will see the error. However, the UI might show the correct value. This is a side effect of the UI auto populating certain fields based on previously entered values. Consult the Appendix F and find out if an exemption code is required for the license type code and report the correct value in the file.

The following license numbers can be used to test shipments requiring BIS or DDTC license.

BIS test license numbers are given below. Use any ECCN that conforms to the valid format NANNN (for example: 0A001).

License Code	Test License Number
C30	D115044
C30	D115874
C30	D120080

DDTC test licenses numbers and the codes to be used are:

Test license numbers, registration numbers, and export information codes are given below. Values in the test shipments must range from $2501 and $3000.

License Code	Test License Numbers	Test Registration Number **	Export Information Code
S05	ck1001 through ck1030	M-2619	OS
S61	ck1031 through ck1035	M-2619	OS
S73	ck1036 through ck1040	M-2619	OS
S85	018366	M-2619	OS
S94	any code of the format AA-A-AAA where "A" represents an alphanumeric character and "--" represents a dash *	M-2619	FS or FI

* If the license number for an S94 shipment is formatted in any other manner, the shipment will be rejected.

** The dash in the registrant number must be input

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

Trade

Delaware CBP Seizes Grossly Undervalued 2016 Range Rover bound for Nigeria

ssapp — Wed, 06 Nov 2019 19:45:45 +0000

Delaware CBP Seizes Grossly Undervalued 2016 Range Rover bound for Nigeria ssapp Wed, 11/06/2019 - 14:45

WILMINGTON, Del. – It isn’t only stolen vehicles that U.S. Customs and Border Protection (CBP) officers are encountering at the Port of Wilmington, Del. Officers seized a 2016 Land Rover Range Rover Monday that was destined to Lagos, Nigeria for being grossly undervalued.

Officers initially inspected the Range Rover October 29, which the New Jersey exporter valued at $13,000. A fair assessment of the vehicle is about $55,000. According to 13USC305, it is a violation of federal law to submit a false export declaration and undervaluing an export. Violations may include a civil penalty, forfeiture of the export commodity, and/or criminal charges. CBP officers seized the vehicle.

“Export examinations are a critical component of Customs and Border Protection’s trade enforcement and border security missions,” said Casey Durst, Director of Field Operations for CBP’s Baltimore Field Office. “CBP officers remain committed to intercepting these nefarious practices that deliberately circumvent our nation’s laws for financial gain.”

CBP officers routinely examine outbound vehicle shipments to ensure the vehicle and its documentation is in compliance with U.S. export laws, and to ensure that the vehicles are not stolen.

CBP officers at the Port of Wilmington set a record for seizures of stolen vehicle exports during fiscal year 2019. Officers seized 16 stolen vehicles with a combined value of $454,007. A majority of those vehicles were being shipped to West Africa.

CBP routinely inspects imported and exported international cargo to search for weapons, illicit narcotics, bulk currency, counterfeit consumer products, and other prohibited items, and to ensure that new and used vehicles, boats, campers and farm machinery comply with existing U.S. laws. See CBP guidance for Exporting a Motor Vehicle.

CBP's border security mission is led at ports of entry by CBP officers from the Office of Field Operations. Please visit CBP Ports of Entry to learn more about how CBP’s Office of Field Operations secures our nation’s borders. Learn what CBP achieved during "A Typical Day" in 2018, or visit www.CBP.gov.

U.S. Customs and Border Protection is the unified border agency within the Department of Homeland Security charged with the management, control and protection of our nation's borders at and between official ports of entry. CBP is charged with securing the borders of the United States while enforcing hundreds of laws and facilitating lawful trade and travel.

Tags:

Trade Enforcement

Port Security

Cargo Security

Automated Export System (AES)

Archive Media Releases

Release Date

Wed, 11/06/2019 - 12:00

AESDirect WebLink Submission API

hkelly — Fri, 05 May 2017 13:44:27 +0000

AESDirect WebLink Submission API hkelly Fri, 05/05/2017 - 09:44

Pub#: 0875-0419

Document Type

Guidance

Document Posting Date

Tue, 05/09/2023 - 12:00

AESDirect WebLink Submission API

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

AESDirect WebLink Submission API

AESDirect Upload Test Files

Anonymous — Fri, 26 Feb 2016 20:02:58 +0000

AESDirect Upload Test Files Anonymous (not verified) Fri, 02/26/2016 - 15:02

EO13891-OT-370

Document Type

Guidance

Document Posting Date

Fri, 03/11/2016 - 12:00

Files included:

AESDirect WebLink Submission Test File
AESDirect Sample AESTIR Test File
AESDirect Sample Test File for X12 601

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

AESDirect Sample AESTIR Test File

AESDirect Sample Test for X12 601

AESDirect Weblink Submission Test File

AESDirect Bulk Upload Test Process

Anonymous — Thu, 18 Feb 2016 17:27:56 +0000

AESDirect Bulk Upload Test Process Anonymous (not verified) Thu, 02/18/2016 - 12:27

Document Type

Guidance

Document Posting Date

Thu, 02/18/2016 - 12:00

This page provides the message formats and technical specifications necessary to electronically transmit data to CBP's automated systems.

Tags:

Automated Export System (AES)

AES Direct Bulk Upload Test Process

AESDirect WebLink Test Process

Anonymous — Thu, 18 Feb 2016 17:25:13 +0000

AESDirect WebLink Test Process Anonymous (not verified) Thu, 02/18/2016 - 12:25

Document Type

Guidance

Document Posting Date

Fri, 03/11/2022 - 12:00

This page provides the message formats and technical specifications necessary to electronically transmit data to CBP's automated systems.

Tags:

Automated Export System (AES)

AESDirect WebLink Test Process

AESDirect WebLink Inquiry API

dsykes — Wed, 03 Feb 2016 18:44:29 +0000

AESDirect WebLink Inquiry API dsykes Wed, 02/03/2016 - 13:44

Introduction:

The AESWebLink Inquiry API is a definition of the protocol by which an AESWebLink Enabled Application will interface and interact with AESWebLink.
The AESWebLink Inquiry API consists of the URL for the AESWebLink application on the AESDirect server, and the data elements that can be passed to it.

WebLink Status API URL:

Test/Training environment : https://ace.cbp.dhs.gov/aesdc/aes/aesdirect-ui/secured/weblinkFilingInquiry
Production environment : https://ace.cbp.dhs.gov/nace/aes/aesdirect-ui/secured/weblinkFilingInqu…

WebLink Filing API URL:

Test/Training environment : https://ace.cbp.dhs.gov/aesdc/aes/aesdirect-ui/secured/createWeblinkFiling
Production environment : https://ace.cbp.dhs.gov/nace/aes/aesdirect-ui/secured/createWeblinkFili…

Key:

Variable: The name of the variable used to send this data element
Description: Description of the Variable
Required By: WebLink - This element is required for submission to AESWebLink. AESWebLink will reject the submission if this is missing.
Value(s): Codes or acceptable value(s) for this element. When this is left blank the element is free text.
Size: Maximum length of data that can be passed in this element.

System Variables
Variable	Description	Required By	Value(s)	Size
FID	Filer ID used for the commodity filing	WebLink	Alphanumeric	11
SRN	Shipment Reference Number	WebLink	Alphanumeric	17
URL	Return URL (optional, needed only for automated ITN redirect. Only https URL will be supported.)	Optional	Valid URL	150

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

AESDirect WebLink Submission API

Anonymous — Thu, 31 Dec 2015 14:45:21 +0000

AESDirect WebLink Submission API Anonymous (not verified) Thu, 12/31/2015 - 09:45

Introduction:

The AESWebLink Submission API is a definition of the protocol by which an AESWebLink Enabled Application will interface and interact with AESWebLink.

The AESWebLink Submission API consists of the URL for the AESWebLink application on the AESDirect server, and the data elements that can be passed to it. The transaction to AESDirect AESWebLink should be an HTTP POST transaction. HTTP GET transactions should not be used due to restrictions on the length of the QUERY_STRING that can be passed with a GET.

AESDirect WebLink Submission API Table

Variable: The name of the variable used to send this data element

Description: Description of the Variable

Editable: User can edit this data element in AESWebLink IF it is missing or incorrect

Required By:

WebLink - This element is required for submission to AESWebLink. AESWebLink will reject the submission if this is missing.

AES - This element is required by AES. Unless otherwise noted, it is not required by AESWebLink, however it will have to be entered by the end user prior to submission to AES.

Value(s): Codes or acceptable value(s) for this element. When this is left blank the element is free text.
Size: Maximum length of data that can be passed in this element.

Notes:
AESWebLink is designed to provide the ability to pass information back to the enabled application at certain points in the process (see AESWebLink Process Overview for details). In order to enable this, the return URLs in the system variables section need to be passed to AESWebLink. If these cannot be passed AESWebLink will use default pages on AESWebLink in place of the return URLs not passed.
Should be a valid E-Mail address. You can send multiple E-Mail addresses separated by commas. If you do not send an E-Mail address, default address for the users account will be used.
AES VPN e-Response Flag - If an account is set up for AES VPN e-Response, setting VPN=1 will direct a copy of responses to the VPN Download Client. If the VPN flag is set to 1 and the Account does not have AES VPN e-Response enabled, the VPN flag will be ignored.
AES VPN Email Suppression Flag - This flag allows suppression of e-mail responses to AESWebLink shipments. To suppress e-mail responses the following 3 conditions have to be satisfied: The VPN Flag must be set to 1 AND the account must have VPN e-Response Enabled (see note 3); the NOEMAIL Flag must be set to 1; and the EMAIL Field must be empty or missing
The field names in the table below refer to the field name in the CBP Proprietary Commodity Format specification. Refer to the field for field length, data type and when the fields are required to be reported. The CBP Proprietary Commodity Format specification can be found at https://www.cbp.gov/document/guidance/cbp-proprietary-format

Tags:

Automated Commercial Environment (ACE)

Automated Export System (AES)

Automated Export System (AES)

Document Image System Instructional Guide for Used Self-Propelled Vehicles

Data Elements in the Email Subject Line

Documents E-Mail Address

Required Data Elements

Error Message Dictionaries/Lists

Error Code Subjects

Main Document Location

Notes

AESDirect Technical Information

AESWebLink Developers Kit

AESWebLink Inquiry

EDI Upload Process

Processing of Your File

Submission to AES

AESDirect Testing Environment

Support

Frequently Asked Questions

Q: Is there a valid license number I can use for testing in the training environment?

Delaware CBP Seizes Grossly Undervalued 2016 Range Rover bound for Nigeria

AESDirect WebLink Submission API

AESDirect Upload Test Files

AESDirect Bulk Upload Test Process

AESDirect WebLink Test Process

AESDirect WebLink Inquiry API

System Variables

AESDirect WebLink Submission API