Automated Commercial Environment Update

1
Automated Commercial Environment Update
Date here City here Presenters here
2
Agenda

• ACE Program Status
• Cargo Systems Messaging System (CSMS)
• Periodic Monthly Processing (PMS)
• Entry Summary and Accounts Revenue (ESAR A1)
• Development Schedule
• International Trade Data System (ITDS)
• ESAR Entry type 01 and 11 (A2.2)
• Cargo Control and Release (CCR) Ocean Rail
  Manifest (M1 / A2.1)
• CCR Air Manifest, Multi-modal Manifest, Cargo
  Release
• ACE Reports Dictionary, training and reference
  guides
• New Electronic ACE Application Process
• Live Demonstration (PPT backup) Creating Reports

3
ACE Program Status

• Deployed truck manifest (e-manifest) capabilities
  to all land border
  ports
• Mandatory e-manifest policy implemented
• nationwide on February 11, 2008
• Processing more than 200,000 trucks per week
• 827 companies certified to file e-manifests via
  EDI
• ACE e-manifests processed 41 percent faster than
• paper manifests
• Over 15,000 ACE Secure Data Portal accounts
• Periodic Monthly Statement collections average
  nearly 1B per month
• Collected 6 billion in duties and fees via
  periodic monthly statement through the second
  quarter of FY08, representing approximately 41
  of all duties and fees collected
• Development continues for
• Entry Summary, Accounts, and Revenue capabilities
• Cargo Control and Release capabilities

Mandatory e-Manifest policy implemented
4
Cargo Systems Messaging Service

• Provides information on all commercial systems,
  including truck e-Manifest, air manifest, rail
  manifest, ocean manifest, and Automated Broker
  Interface (ABI)
• Existing ABI messages will eventually be
  converted to the Cargo Systems Messaging Service
  (CSMS)
• CSMS will eventually become the single broadcast
  message system for users of CBP automated
  commercial trade systems
• Messages from CSMS are sent instantly, providing
  near real-time access to the latest news and
  information
• Two ways to get information with CSMS
• Messages e-mailed directly to subscribers
• Messages also stored on a searchable database,
  accessible via CBP.gov

5
Cargo Systems Messaging Service(continued)

• To receive messages on any of the following
  topics, subscribe to CSMS via www.CBP.gov/moderniz
  ation
• ABI
• ACE Portal Accounts
• Periodic Monthly Statement
• Truck Manifest
• Cuentas en el Portal de ACE (ACE Portal Accounts
  Spanish)
• Transportistas de Camion (Truck Manifest
  Spanish)
• Air Manifest
• Ocean Manifest
• Rail Manifest
• ACE Outreach Events
• ACE Reports

6
Periodic Monthly Statement Overview

• Periodic Monthly Statement is a feature of the
  Automated Commercial Environment (ACE) that
  simplifies the processing of duties and fees and
  promotes account based processing
• Streamlines accounting and reporting processes by
  providing the capability to make periodic
  payments on a monthly basis
• Moves from a transaction-by-transaction payment
  process or a daily payment process to an
  interest-free periodic monthly statement process
• Rolls-up the collection processing of the duty
  and fees for eligible individual entry summaries
  for goods that are either entered or released
  during the previous month and allows payment on
  the 15th working day of the following month

7
Periodic Monthly Statement Benefits

• Benefits of Periodic Monthly Statement include
• Allows all eligible shipments released during the
  month to be paid on the 15th working day of the
  following month
• Provides additional flexibility in the management
  of working capital required for duty payments
• Provides potentially significant cash flow
  advantages
• Allows the filer to select either a national or a
  port statement
• Allows the broker to pay on behalf of the
  importer on either an importer or broker
  statement from the importer or broker Automated
  Clearinghouse (ACH) account
• Allows accounts to view the statement as it is
  being built

8
Overall Parameters

• The following entry summary payment options are
  available to all periodic monthly statement
  participants
• Single Pay
• Automated Broker Interface (ABI) Daily Statement
• Periodic Monthly Statement
• All ABI entries covered by a continuous bond may
  be flagged for inclusion on a periodic monthly
  statement except
• Reconciliation (Type 09)
• NAFTA Duty Deferral (Type 08)
• Entries with tax class codes

9
Periodic Monthly Statement Process

• The filer transmits the entry summary data and
  schedules it for Periodic Daily Statement
• The periodic statement month (new field)
  indicates the month for payment. This controls
  the periodic monthly statement on which the entry
  summary will be included
• Entry summaries can be removed from the statement
  at various times throughout the process but
  depending on the timing of the removal could be
  subject to liquidated damages

10
Periodic Monthly Statement Process

• Scheduling Statement Due Date
• Entries should be scheduled for an ABI Periodic
  Daily Statement within ten working days of the
  date of entry
• Importer can choose from the first to the 11th
  working day of the month when the preliminary
  Periodic Monthly Statement is generated by U.S.
  Customs and Border Protection (CBP) (Default is
  the 11th working day of the month which CBP
  recommends all parties use)

11
ACH Debit

• Scheduling Statement Due Date
• The Periodic Daily Statement Debit Authorization
  and/or Entry Summary Presentation (PN Application
  Identifier) must be processed on schedule for
  each Periodic Daily Statement
• For ACH Debit participants, the PN acts as
  Debit Authorization AND Entry Summary
  Presentation
• For ACH Debit participants, on the 15th working
  day of each month, CBP will transmit the payment
  authorizations that were done for each Periodic
  Daily Statement to the bank
• Make certain the money is in the bank on the 15th
  working day. If there is no money to cover the
  PNs, nothing will be debited. Thus no payments
  are processed and all summaries are now subject
  to liquidated damages

12
ACH Credit

• Scheduling Statement Due Date
• A PN Application Identifier message must be
  processed on schedule for each Periodic Daily
  Statement
• For ACH Credit participants, the PN acts as
  Entry Summary Presentation
• ACH Credit participants are responsible for
  transmitting payment to CBP using the Periodic
  Monthly Statement number by the 15th working day
  of each month

13
Automated Clearinghouse Credit

• Scheduling Statement Due Date
• If an incorrect amount is pushed to CBP, it will
  be treated as follows
• Excess payments are placed on the account entry
  summaries on the periodic monthly statement are
  marked as paid
• Under payments are placed on the account no
  summaries are marked as paid. Summaries will
  remain unpaid until CBP personnel analyze the
  statement.

14
General Information

• Importer accounts will always have Port
  statements
• Just like today with Daily Statements, with
  Periodic Daily Statements and Periodic Monthly
  Statements, if an importer uses different brokers
  to process their entry summaries in a given port,
  these entry summaries will appear on different
  Periodic Daily Statements and Periodic Monthly
  Statements if they are filed with different filer
  codes. Only if entries are filed with one filer
  code, can all the entry summaries for that port
  appear on one Periodic Daily Statement and one
  Periodic Monthly Statement

15
Options for Participation in Periodic Monthly
Statement

• Importers have two options to participate in
  periodic monthly statement
• Establish an ACE account
• As an ACE account the importer will have access
  to the ACE Portal and reports
• Establish a non-Portal account through a broker
  who is an ACE Account
• As a non-Portal account, the importer will not
  have access to the ACE Portal and reports

16
Instructions for Participation Current ACE
Portal Account

17
Instructions for Participation Non Portal
Account

18
Common Issues

• Sending incorrect month on quota or RLF entries
• Revenue-free statements do not show on the
  monthly statement

19
Key A1 Trade Community Capabilities

• Merge Accounts
• Streamlines the process for merging accounts
  within the ACE Secure Data Portal
• Cross-Account Access
• Allows ACE Portal users to access multiple
  accounts using one user-id and password
• Broker Management
• Makes broker data (exam, license, and permit
  information) available at a National level
• New Account Types
• Expands ACE access to virtually every entity
  doing business with CBP

Michael Maricich
20
ESAR A1- New Account Types

• Account Types
• Broker
• Carrier (all modes)
• Cartman
• Driver/Crew
• Facility Operator
• Filer
• Foreign Trade Zone (FTZ)
• Importer
• Lighterman
• Service Provider
• Surety

21
Development Schedule

• A2.3 Remaining Entry Summary Types

• A2.4 Enhanced Entry Summary Functionality

• A3 Importer Activity Summary Statement

A2.1 M1 Reference Data
A2.2 Initial Entry Summary Types (01 and 11)

• M4 Bonded Facilities Control

M3 Exports and Mail Entry Writing System

• M2.3 Cargo Release

M1 Vessel and Rail Manifest
M2.1 Air Manifest
M2.2 Full Multi-Modal Database
Q1
Q3
Q4
Q2
Q3
Q1
Q4
Q2
2011
2012
2009
2010
2008
Operational Readiness Review (ORR)

A2.3 will be implemented incrementally

• Subdivides Entry Summary, Accounts, and Revenue
  and Cargo Control and Release capabilities into
  smaller drops of related functionality
• Extends development schedule to 2012 while
  keeping cost upon full deployment at 3.3B
• Reflects greater program complexity than
  originally anticipated, which contributed to the
  need for an extended development schedule
• Calls for aggressive development and deployment
  leading up to 2010

22
Development Schedule - update

• An announcement of a delay in the anticipated
  deployment date of Sea and Rail manifest (M1) was
  published on July 25th via CSMS message
  08-000128.
• Due to problems discovered during software
  testing, the October 2008 deployment of ACE rail
  and sea manifest (M1) will be delayed six to
  eight months
• As a result of the M1 delay, the January 2009
  implementation of ACE initial entry summary
  processing capabilities (A2.2) will be postponed
  four to six months
• CBP is in the process of determining the impacts
  these delays will have on the overall ACE
  schedule and anticipates publishing a modified
  schedule in the near future.

23
International Trade Data System

• 45 Participating Government Agencies in ITDS
• More than 450 ACE Secure Data Portal end-users
  from 27 PGAs
• Security and Accountability For Every (SAFE) Port
  Act of 2006 officially established the ITDS
  initiative under the Department of the Treasury
  and mandated agencies involved in licensing and
  admissibility to join ITDS
• Executive Order 13439 (July 2007) established the
  Interagency Working Group on Import Safety
• Working group recommended that use of ITDS be
  required when collecting information to clear or
  license the import or export of cargo

24
International Trade Data System

• Office of Management and Budget directive
  M-07-23, dated September 10, 2007
• Mandated that each department designated to
  participate in the Presidents Working Group on
  Import Safety identify a senior executive, by
  September 21, 2007, to participate on an
  interagency team to coordinate agency use of ITDS
• Mandated quarterly tracking of specific
  milestones to monitor progress towards the
  completion of requirements and Memorandum of
  Understandings (MOUs)

25

• Entry Summary Accounts Revenue (ESAR)

26
A2.2 Detail

• January 2009 delivery with a limited number of
  trade participants
• Participation will be voluntary until all entry
  types can be submitted in ACE and sufficient
  Trade testing is completed
• A Federal Register Notice will be published to
  announce deployment of A2.2
• Entry summary status, payment, liquidation and
  other applicable information for type 01 and type
  11 entry summaries for ACE filers, will be
  interfaced between ACS and ACE
• ACE and ACS will not have the same set of edits
  and validations

27
ESAR A2.2 Edit Modification
CBP and the trade community held discussions
regarding which edits would be programmed in ACE
for entry processing CBP determined that in
accordance with the Modernization Act filers have
the primary responsibility for filing correct
declarations CBP concluded that a significant
number of edits would not be programmed in ACE
28
Edits are in scope for A2.2

• Trade voiced concern white papers, statistical
  evidence and metrics
• Resulted in CBP agreeing to add twenty four High
  Priority groups of edits
• The edits will not be delivered in time for the
  initial deployment of A2.2
• The edits will be in before ACE Summary filing is
  mandatory

29
A2.2 Operational Impacts

• Allowing the trade to send entry type 01 and 11
  entries to either ACE or ACS means that CBP and
  Trade will be operating in 2 systems
• Online maintenance of an entry summary will occur
  in the system of origin (either ACE or ACS) for
  example
• The type 01 and 11 entry summaries filed in ACE
  will be maintained in ACE
• All other entries that are filed by the same
  filer, including 01 and 11 entry summaries filed
  in ACS, will be maintained in ACS.
• An ACE filer will not have to file all of his
  type 01 and type 11 summaries in ACE. So long
  as the filer is ACS certified, he can choose to
  transmit ANY of his entries via ACS.
• Data for reports will be extracted from both ACE
  and ACS systems

30
Entry Summary Processing in A2.2

• With A2.2 entry summaries will be processed in
  ACE through ABI using application identifier AE
• Entry summaries processed in ACE are required to
  be scheduled for a statement (Daily Statement or
  Periodic Daily Statement)
• ACS and ACE entry summaries will be commingled on
  the same daily statements
• Statement payments for entry summaries filed in
  ACS or ACE will be processed in ACS
• Entry summaries filed in ACS or ACE will be able
  to be removed from a statement using the
  statement delete (HP) application identifier in
  ACS
• If an ACE entry summary is removed from a
  statement the single entry payment will be
  processed in ACS

31
New CATAIR Records for ACE Entry Summary

• ACE Entry Summary ABI inbound AE outbound AX
• ACE Entry Summary ABI Query inbound JI outbound
  JR
• ACE Entry Summary Error Statistics Query ABI
  inbound RC outbound RD
• ACE Entry Summary Status Message ABI outbound
  UC
• ACE and ACS Entry Summary Edit Modification
• ACE Entry Summary Policy
• Must be ABI
• Must be filed on a Statement
• Must be ACE Trade Participant

32
Census Warning Override Process

• This is a new process by which the trade
  community can electronically correct Census
  warnings through the submission of an override
  code for entry summaries prior to or after
  receiving a Census warning message through ABI
• If you know the Census warning will happen you
  will be able to do a preemptive Census override
  before filing the entry
• If you get a Census warning due to an error in
  reporting you will be able to fix the entry then
  report the Census override
• If you file the entry and receive a censes
  warning but my data is correct you will be able
  to file a census override
• The detailed list of override codes will be
  provided as a part of Appendix H of the CATAIR

33
Census Warning Overrides

• ACE Census Warning ABI inbound CW outbound CO
• ACE Census Warning ABI Query inbound CJ
  outbound CL
• ACE Census Warning Overrides can be submitted
  within the ACE Entry Summary ABI inbound AE

34
ESAR A2.2 Portal Navigation Changes

• Goals
• Solve existing screen real-estate issues and
  provide room for growth in the Portal
• Create an easier-to-navigate, more intuitive,
  more modern user interface
• Consolidate like functionality, pages and
  portlets
• Drive user experience consistency across ACE
  Portal initiatives

35
Home Page
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
36
References
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
37
Tools / User Access
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
38
Account View (Importer)
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
39
Trade Declarations

• Type of Declarations
• Affidavit of Manufacturer
• Certain Marking Rulings (CROSS)
• Importer Certifying Statement
• North American Free Trade Agreement (NAFTA)
  Certificate of Origin
• Non-reimbursement Blanket Statement (AD/CVD)

40
Declaration Process

• Who can Create Declarations?
• Authorized Trade User for accounts to which User
  has access
• Who can Search and Display Declarations?
• Authorized Trade User for accounts to which User
  has access
• CBP Users
• Who can Edit Declarations?
• Once created and submitted, Declarations cannot
  be edited
• Who can Cancel Declarations?
• Authorized Trade User for accounts to which User
  has access
• CBP Users

41
Home Page
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
42
CBP Forms 28, 29 and 4647

• CBP Forms 28 (Request for Information), 29
  (Notice of Action) and 4647 (Notice to Mark
  and/or Notice to Redeliver) will be created by
  CBP and stored in a National Database
• CBP can mail and post to Trades ACE Portal
• Trade Portal Users can select their preferred
  method of communication via the Portal (mail,
  Portal or both)
• CBP Forms 28, 29, 4647 will be posted to the
  Trades Task List
• Trade Portal Users can interactively respond to
  the form and attach/upload documents in response
  to CBP via the Portal

43
Trade View - Method of Communication
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design

• Access maintained via the Manage Access Tab
• Selection is at the Top Account Level and Account
  Level

44
Trade View A2.2 Task List
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
45
Trade View Forms Response
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
46
Trade View - Forms
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
47
Trade View Attach Files (Forms)
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
48
Trade View Forms Search
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
49

• Cargo Control and Release (CCR)
• Future Multi-Modal Manifest Releases

50
Cargo Control and Release Overview

• Within ACE, the objective of the Cargo Control
  and Release (CCR) delivery is to
• Standardize cargo control processing, reporting
  tools and query capabilities across all
  transportation modes and to provide importers,
  exporters, customs brokers and transportation
  providers with one system for moving goods into
  or through the U. S. using ships, planes, trains,
  trucks and, ultimately, pipelines
• Consolidate manifest, entry, reference file data
  and screening and targeting results via the
  Web-based ACE Secure Data Portal to help
  facilitate identification of shipments that may
  pose a potential risk
• Providing Participating Government Agencies
  (PGAs) a single, integrated system and data
  repository to more efficiently control and
  evaluate shipments for security, commercial
  compliance and narcotics enforcement purposes

51
CCR Functionality Overview

• M1 A2.1
• Provides a common Multi-Modal database and
  shared cargo control software for sea and rail
  modes of transportation
• M2.1
• Inclusion of air cargo processing into ACE
  Multi-Modal Manifest environment
• M2.2
• Inclusion of Truck e-Manifest into the ACE
  Multi-Modal manifest environment
• M2.3
• Modernizes Cargo Release
• M3
• Brings export cargo processing into Multi-Modal
  Manifest environment allowing for export manifest
  reporting for truck, sea, rail, and air

52
Sea and Rail Manifest (M1)

• Will be deployed in Fall 2008
• Features
• Identification of un-manifested container through
  vessel stowage plan
• New functionality for sea and rail trade partners
  via the trade Portal.
• Validation of trade partner authorization to use
  custodial bonds to be maintained by the trade
• An e-Mail list serve capability for CBP to
  communicate with ACE trade partners
• Extends the broker download functionality into
  the sea cargo environment

53
Sea and Rail Manifest (M1) (cont.)

• CBP will be able to place and remove holds at the
  container level
• Bring in PGAs and provide them with hold/hold
  removal functionality
• Retires ACS vessel and rail manifest processing
• Benefits
• Enhanced trade functionality, improved cargo
  control processes for CBP, enhanced data capture
• M1 Development Deployment strategy
• The Automated Manifest System (AMS) will be run
  in parallel
• Builds on lessons learned from truck e-Manifest
  deployment
• Uses AMS functionality as its baseline

54
Custodial Bond User Verification for In-Bond
Moves A2.1 / M1

• Ocean and rail carriers will be able to create a
  carrier in-bond authorization through their ACE
  Portal account.
• If no In-Bond Authorization partners are
  activated, anyone may obligate the carriers bond
  
• If the carrier chooses to restrict the use of
  their bond to themselves, they must add
  themselves as an In-Bond Authorization partner
• If the carrier elects to restrict the use of
  their bond to specified carriers, they must add
  those carriers as In-Bond Authorization partners
  and must add themselves

55

Create Carrier In-Bond Authorization

• The In-Bond Authorization functionality allows
  the carrier to identify who (another carrier) is
  authorized to use its bond to move cargo.
• From the Bonds Tab, select Type 2 Bond
• Click In-Bond Authorization tab within the View
  Bond Master Data Portlet
• Click on Add Authorized Partner to create new
  authorization

Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
56

Maintain Carrier In-Bond Authorization Data
Port restrictions are recorded as yes or no No
restrictions allow the partner to use the
carriers bond between all ports at all
times Click hyperlink to view partner
authorization details.
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
57

Maintain Carrier In-Bond Authorization Data
If the partner has no restrictions the screen
will display all for Origin and Destination
Ports and none as the Effective End Date
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
58

Maintain Carrier In-Bond Authorization Data
To establish date and trade lane restrictions you
must complete Origin Port, Destination Port,
Effective Begin Date and Effective End Date
fields Click Add to List, then SAVE to return to
Display Authorized Ports screen
Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
59
Trade Portal Functionality A2.1 / M1

• Ocean conveyances will now be maintained in the
  ACE Portal.
• Ocean conveyances must exist in ACE prior to
  being used by the Trade on a manifest
• Carriers involved in initiating this process must
  have Mode of Transportation of Sea/Ocean
• Non-Vessel Operating Common Carriers will NOT be
  able to add conveyance data to the Portal

60
Create Ocean Conveyance

• From Account Tab click on Conveyance sub-tab
• Click on Add Conveyance

Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
61
Create Ocean Conveyance

• Enter data. SAVE. User will be returned to the
  Conveyance sub-tab.

Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
62
Ocean Conveyance Trade Download

• Permits the Trade community to download/upload
  existing ocean conveyance details.
• Initiate the download by clicking on the Download
  Data or Upload File hyperlinks.

Conceptual Design To be used for discussion
only - Not necessarily representative of UI
Design
63
ACE Ocean and Rail (M1) Trade Testing

• Trade testing of ACE Multi-Modal Manifest release
  M1 will begin no sooner that September 2008
  Testing will be done using the current EDI data
  formats
• Ocean Manifest will use
• CAMIR (Amendment 13) or
• ANSI X-12 (version 4010)
• Rail manifest will only use ANSI X12 version 4040
  format.
• CBP will be moving to ANSI X-12 Version 5040 at a
  future date after the initial implementation of
  M1 in the ACE Production

64
Future CCR Releases Air Manifest (M2.1)

• Features
• Inclusion of air cargo processing into ACE
  Multi-Modal Manifest environment
• Improves cargo control for CBP, brings PGAs into
  air environment, better information for CBP and
  PGAs
• Improved In-bond functionality and intermodal
  In-Bond cargo movements
• Holds at master, house, sub-house and simple bill
  of lading levels in air cargo
• Electronic transfer of bond liability between
  trade partners.
• Electronic landing rights notification from CBP

65
Air Manifest (M2.1) continued

• New report capabilities for trade partners and
  CBP field officers via the ACE Portal
• Broker download capability extended to air cargo
  environment
• Expand 2nd Notify Capability into air cargo
  processing
• Retirement of legacy Air AMS manifest system
• Benefits
• Addresses requests from trade for new
  functionality
• Facilitates intermodal movement of cargo between
  trade
• Improves cargo control for CBP, brings PGAs into
  air environment

66
Cargo Release (M2.3)

• Features
• Bring new PGAs into ACE Cargo Release
  application.
• Support commercial identifiers in the Multi-Modal
  Manifest Bill of Lading and In-Bond identifier
  fields
• Provide custom reporting capabilities to CBP and
  PGA users
• Provide CBP and PGA user with the capability to
  attach electronic documents to entries
• Additional electronic status notifications
  related to PGA requirements
• New functionality as requested by CBP field
  officers and trade partners
• Ability to send electronic files (PDF, JPEG etc)
  by brokers to CBP in reply to information
  requests to facilitate cargo release

67
Cargo release M2.3 (continued)

• Benefits
• Termination of legacy ACS Cargo Selectivity
  application (the end of ACS in CCR area)
• Cargo Release and Cargo Control applications will
  share a common database environment that will
  allow for expanded functionality between
  transportation and entry filer communities
• Extends PGA functionality in ACE to over 20
  different Federal agencies
• Fully enfranchises the entry filer and
  transportation sectors of the trade in ACE

68
ACE Reports

69
Reports Dictionary Objectives

• To provide ACE users with a reference document
  that enhances understanding and encourages use of
  the reporting tool
• To facilitate identification of reports and
  attributes by providing detailed definitions of
  the top 116 frequently-accessed reports and their
  available data elements

70
Reports Dictionary Elements
1
2
3
4
5
71
Whats New?
New Account Revenue Periodic Statement Detail
Report

• Allows one-screen visibility of
• Total amount of monthly statement
• Total amount for each individual Importer of
  Record (IR) number
• Monthly statement, daily statement, and entry
  number data
• Data based on statement status (i.e., open,
  closed, deleted, or all)
• Importer and broker statement via tabs at the
  bottom of the screen
• The new report
• Can be easily customized via the new reporting
  tool
• Was designed with trade community input
• Is becoming one of the most used ACE reports

72
ACE Training and Reference Guides
73
Whats New?

• New electronic ACE application process
• Applications may now be downloaded, signed
  electronically, and e-mailed to CBP
• Shortens application processing time and allows
  instantaneous e-mail dialog between applicant and
  CBP

Effective May 30, 2008 a new toll free phone
number will be used as the sole access for the
Trade and Participating Government Agencies (PGA)
to the CBP Technology Support Center (previously
known as the ACE Help Desk) The new number is
1-866-530-4172. The new email address for all
Trade and PGA ACE issues is now
CBP.Technology.Support_at_DHS.gov
74
Questions?

75
(No Transcript)