your direct filing solution
ACE Certified ACE-Certified
Get Started Today
Linked InTwitterFacebookRSS

Categories

Archives

Recent Posts

Paying too much for your ISFs?

Ask us how you can save money and automate the process.

Get Started Today!

get started

Contact us for more information or to schedule a live demo.

Contact Us

FDA

CBP’s formal announcement on ACE deadline move to Oct 29

Thursday, September 8th, 2016

O

 

In follow up to yesterday’s blog post, here is US Customs’ official announcement of the move of the October 1 ACE deadline to October 29:

U.S. Customs and Border Protection (CBP) has been assessing stakeholder readiness for the mandatory transition of post-release capabilities in ACE and has heard from key industry partners on the need for additional flexibility in this transition.  As a result, CBP is moving this date from October 1, 2016 to October 29, 2016 to allow additional time for our trade stakeholders to transition these capabilities to ACE.

This adjustment affects the mandatory filing of liquidation, drawback, reconciliation, duty deferral, collections, statements, and automated surety interface. 

All capabilities included in the October 29, 2016 transition that are planned for but not yet deployed to the Certification environment (CERT) will be operational in CERT, and all known prioritized issues will be resolved, no later than September 30, 2016.

While CBP has implemented the capability for most Partner Government Agency (PGA) data to be filed electronically in ACE, trade users may continue to file a combination of CBP electronic data and PGA paper forms where that is currently permitted. 

APHIS Lacey, NHTSA, FDA and as of 9/20/16, NMFS, data is required to be filed electronically in ACE. 

For PGA data that is not required to be filed electronically in ACE, filers may file using options currently specified as available for those PGAs.

CBP will continue to coordinate and communicate as required the conclusion of PGA pilots via public notices.

To ensure quick resolution of any issues that may arise following the October 29th deployment, CBP will stand up an operations center to support the transition to ACE for post-release capabilities for CBP users. Trade users will continue to contact their assigned Client Representative as the first line point of contact. Client Representatives will escalate trade issues as needed to the operations center.  Additional information on support during the transition will be published prior to the October 29th deployment.

The information in this notice will be posted on cbp.gov by September 8.

New ACE adoption rate report published

Monday, August 22nd, 2016

Entry release and entry summary filing numbers have begun to converge based on expanded ACE functionality.  Note high percentage of FDA filings relative to total PGA filings.  FDA has done a solid job in outreach to the trade on ACE.

External_July_ACE Adoption Rate_Final

FDA/ACE: How to get a Prior Notice confirmation number… for now

Monday, August 8th, 2016

fdalogo

Per US Customs’ CSMS #16-000674:

This message is to provide an update to obtaining a standalone Prior Notice Confirmation Number for FDA.

There are currently three ways to obtain a standalone Prior Notice Confirmation Number:

  1. FDA’s Prior Notice System Interface (PNSI)
  2. The Automated Commercial System (ACS) – the WP function
  3. The Automated Commercial Environment (ACE) – the PE functionally

Filers can continue to transmit in BOTH ACS and ACE until a subsequent CSMS message is issued notifying the trade when ACS (WP) will be turned off. Following that date, ACE and the FDA PNSI will be the only systems available to provide a Prior Notice Confirmation Number.

FDA must receive prior notice before food is imported or offered for import into the United States. Advance notice of import shipments allows FDA, with the support of CBP, to target import inspections more effectively and help protect the nation’s food supply against terrorist acts and other public health emergencies.

FDA reviews response time frames in ACE

Friday, July 15th, 2016

fdalogoFrom CSMS #16-000554:

  • FDA regulated commodities go through multiple screening processes, depending on the product. From the time FDA successfully receives the entry data in its system, the screening process can vary from minutes to same business day processing, or multiple business days depending on the volume of entries/lines sent by CBP at a given time and the quality of information transmitted.
  • At the end of this screening process FDA’s system will return to CBP a message from CBP’s ACE Cargo Release Status Notification Implementation guide.
  • For commodities that require Prior Notice, the Prior Notice Confirmation Number should typically be received within 30 minutes (based on volume of entries/lines received within that window) from the time FDA successfully receives the data in their system.
  • FDA does not have a regulatory mandate regarding entry review time frames when determining admissibility of the FDA-regulated articles under 801(a.) However, FDA continues to improve the efficiency and consistency of the import admissibility process, including development of internal standards regarding entry review for an initial admissibility determination under 801(a.)
  • FDA regularly monitors its system and process performance throughout each day for anomalies.

FDA ACE entries: common errors

Thursday, July 7th, 2016

fdalogoPer US Customs CSMS #16-000557:

ALL ABI FILERS OF ACE ENTRIES

FROM: THE FOOD & DRUG ADMINISTRATION

Since the month of June FDA has seen a sharp increase in submission of ACE entries containing errors which do not result in a reject at this time, but cause issues with FDA’s automated processing and subsequent admissibility decision-making process. This message is intended to convey these common errors so filers may make any corrections to their ABI systems that will avoid them moving forward.

1. One of the most common errors is the submission of duplicate units of measure when describing the quantity of product on a single FDA line. FDA’s quantity reporting requirements have not changed with ACE and filers should continue to describe the product from largest container down to the smallest base unit. An example would be a product that ships in 100 cartons (CT), each containing 24 boxes (BX), each containing 10 packages (PK) of 12 oz. (OZ) each. It is not appropriate to send cartons, boxes, packages or ounces twice on this example line. Different packaging sizes should be transmitted as separate lines in order to accurately reflect the product’s state when making entry into the country. Instructions on transmitting quantity to FDA are attached to this CSMS message.

Further quantity examples:

  • Product: 1000 cases of mineral water, 24/12 ounce bottles in each case
    • Data pairs: 1000 CS (Case)
    • 24 BO (Bottle, Non-protected, Cyl)
    • 12 FOZ (Ounces, fluid) (Base Unit)
  • Product: 200 cartons of 100 rolls surgical gauze, 75 square yards per roll
    • Data pairs: 200 CT (Carton)
    • 100 RO (Roll)
    • 75 (SYD (Square Yards) (Base Unit)

2. FDA requires Manufacturer (MF) as a mandatory entity in PG19 for lines on entries with Product Codes that are identified as “Non-Food” (not requiring Prior Notice) and for lines on entries with Product Codes that are identified as “Food” and already having a Prior Notice Confirmation. Filers need to provide the Manufacturer entity in PG19 for these scenarios.

3. FDA limits “Affirmation of Compliance Qualifier field” in PG23 (Affirmation of Compliance) to a size of 30 characters. Filers should provide no more than 30 characters for this field in PG23. In addition, the qualifier must follow the syntax indicated in the FDA Supplemental Guide.

4. Intended Use Code: FDA requires trade to provide a valid intended use code which is listed in the FDA Supplemental Guide 2.4.1 and CBP ACE CATAIR

5. Missing/Invalid Affirmations of Compliance- AofC Codes are required based on product type (and FDA Product Code), intended use, mode of transport. There have been additions and changes to many AofCs in ACE

6. Missing/Invalid Entities

• 4-5 Entities are required for Non-PN Lines

• 7 Entities are required for PN Lines

Incorrect entity role codes for a given commodity can cause processing errors and delays. Refer to the FDA Supplemental Guide to determine which entities should be provided for a given product.

Please direct any questions to ACE_SUPPORT@FDA.HHS.GOV

FDA to give “priority processing” to ACE entries, implement production calls with trade

Tuesday, June 14th, 2016

As posted here previously, US Customs is mandating filing in ACE for select FDA entry types as of tomorrow, June 15, 2016.  In addition to establishing a 24/7 ACE support center, FDA is taking further, significant steps to assist the trade in the transition to ACE, including:

  • Institution of “production calls”
    • a meeting between the FDA, the entry filer and the entry filer’s software vendor (preferably) to walk through an entry that is being submitted via ACE
    • Production calls allow FDA and the entry filer to talk about the entry submission in real time
  • Priority processing of ACE entries
    • The average processing time for manual review and release of ACE submitted entries is 25% faster than the average processing time for manual review and release of ACS submitted entries
    • slide1When review of documents is necessary, processing time from when documents are requested to the release of ACE submitted entries is 33% faster than for ACS submitted entries, resulting in a savings of 1 ¼ days of processing time

slide1

FDA ACE support center help desk goes live tomorrow!

Monday, June 13th, 2016

fdalogo

From our friends at the NCBFAA:

The FDA has set up a 24/7 help desk — the ACE Support Center — to support implementation of ACE. This call center will address issues with ACE and will help facilitate the resolution of issues reported for ACE entries. FDA will continue to also provide e-mail support. Issues related to ACE entries can be sent to  Ace_support@fdahhs.gov.

The help desk goes live on Tuesday, June 14, 2016. It can be reached at:

  • Domestic Toll Free: 877-345-1101
  • Local/International: 571-620-7320

 

 

GAO: FDA’s PREDICT tool for food imports “working as intended”

Thursday, June 9th, 2016

fdalogoFrom the US General Accountability Office’s May 2016 Report “IMPORTED FOOD SAFETY: FDA’s Targeting Tool Has Enhanced Screening, but Further Improvements Are Possible”:

FDA officials reported that they conduct monitoring of PREDICT on an ongoing basis and that the data they collect as part of this monitoring show that PREDICT is working as intended—that is, PREDICT is focusing entry reviewers’ attention on items determined to be of higher risk. Data provided by FDA from fiscal years 2012 to 2014 confirmed that in general, PREDICT is fulfilling this role. Our analysis of these data showed that in general, the higher the PREDICT risk score, the more often entry lines were examined and the more often they were found violative.

For example, for fiscal year 2014, entry lines that received higher PREDICT scores generally were more often selected for a field examination, for a label examination, or for sampling, and entry lines with higher PREDICT scores were more often found violative.

gao fda predict report

 

 

 

 

 

 

 

 

 

The full GAO report is available here.

ACE: New CBP guidance on PGA Entry Type Codes

Monday, June 6th, 2016

seal_ace

Per CSMS #16-000439:

This following advises which CBP Entry Type Codes will require Partner Government Agency data, (i.e., the PGA Message Set) when the entry types are deployed and the PGA is ready to accept them. Below is an explanation of the legend on the attached chart detailing PGA filing requirements by entry type code, and additional clarification on the Entry Type 06 Foreign Trade Zones.

Explanation:

• The word “Yes” in the entry type line/box indicates the PGA’s data is required for, the entry type when the entry contains the (HTS) commodities, regulated by that specific PGA.

• The word “No” indicates the PGA’s data is not required for the entry type.

  • TYPE 06 – Consumption, Foreign Trade Zone (FTZ):
  • The PGA’s chose one of two options for requiring their PGA data:
    • At Cargo Release
      • Eleven (11) agencies require the PGA message set at Cargo Release, whether it is a Regular Type 06 or a Weekly Estimate:
        • ATF / AMS / APHIS / DEA / EPA / FDA / FDA / FSIS /FWS / OMC / and TTB
    • DUAL option
      • If a regular 06 entry is filed at cargo release, then the PGA data is required with the filing.
      • If a weekly estimate is filed at Cargo Release, the PGA data is required at Entry Summary, (no PGA data is to be sent with the weekly estimate).
      • Four (4) agencies opted for the dual option:
        • APHIS Lacey / CPSC / NHTSA and NMFS

Any questions can be referred to William.R.Scopa@CBP.DHS.GOV

 

0001

0002

ACE: Update on status of PGA pilots

Friday, June 3rd, 2016

Here is CBP’s latest report on the status of 17 PGA pilot programs regarding ACE:

ACE PGA pilots