A E S Direct - Reduce Exporting Stress with A E S
Home

Press enter to skip left navigation bar
Log In
AESDirect
Certification Quizzes

Account Set-up & Management
Register New Account
Registration Help
Re-Activate an Account
Terms & Conditions
Privacy Policy

Vendor Account Set-up
Developers Center
Register Vendor Account

Training
AESDirect Tutorial
User Guides
Online Training
Workshops
AES Compliance

Using AESDirect
Who to Contact
Support Center
Browser Support
Developers Center
News

AESPcLink
About AESPcLink
Getting Started
Terms & Conditions

AESDirect VPN
About AESDirect VPN
Set up AESDirect VPN

Related Sites
Government Sites
Partner Sites
A E S Direct Developers Center

Customs Proprietary Format Notes
[Developers Center Home]

This document contains implementation notes on the Customs Proprietary Format that is accepted by AESDirect.

U.S. Principal Party in Interest (USPPI):

The first time that you file for an USPPI through AESDirect, you must send the complete N01-N03 sequence with complete USPPI profile information.

For subsequent shipments for the same USPPI, the USPPI ID in the B record will be used and the N01-N03 records may be omitted.

If you wish to change the profile for an USPPI, you must transmit the complete N01-N03 records with the updated information.

All Parties: (Except USPPI)

Whenever you transmit a party within a shipment, you must include the complete N01-N03 sequence as required by the party type. AESDirect does not accept previously filed parties based on the party ID alone.

Each new shipment must contain N01-N03 records for a consignee.

Other parties are optional, but when included you must include the full N01-N03 sequence for each party.

Party information can be omitted when sending changes, unless the change is to the party information> In this case the full N01-N03 sequence must be included.

Routed Transaction Flag:

The "Routed Transaction Flag" has been added to Position 41 of the SC2 Record. The January 2001 Customs Proprietary Format reflects this change, HOWEVER, AESDirect will be implementing this field as an OPTIONAL field. If the Routed Transaction Flag is not sent, AESDirect will assume the shipment is not a routed transaction and it will be sent to AES as such. Not sending the routed transaction flag will have the same effect as explicitly sending "N" in the Routed Transaction Flag field.

The "Routed Transaction Flag" will be implemented by customs on January 1, 2001. At this point you will be able to send shipments with the Flag. You can send shipments with the Flag before that time to enable a smooth transition.


U.S. Census Bureau Foreign Trade Logo U.S. Department of Commerce

[top of page]