IMEXNet USDA APHIS Filing

 

IMEXNet

USDA APHIS

 

 

 

Update System to latest version & Run Web update Files *

 

 

 

When to Submit an APHIS Core Message Set in ACE?

  • On September 28, 2020, APHIS published a Federal Register notice that it will delay full implementation of the APHIS Core Message Set in the Automated Commercial Environment (ACE) until January 25, 2021. Prior to January 25, 2021, filing an APHIS Core message set will continue to be optional. After January 25, 2020, filers will have to submit an APHIS Core message set when they receive a flag in ACE to complete their entry.

 

Update 1/21/2021 CSMS #45773761 - Update to Rollout of APHIS Core Message Set Implementation

USDA (APHIS) is announcing a two-stage enforcement of the APHIS Core message set to allow trade to adjust to the data requirements. The first stage of enforcement will commence on January 25, 2021, requiring filers to submit message set data for regulated products. During this time, APHIS will continue to maintain “warning” level Harmonized Tariff Code flagging (refer to Federal Register Notice APHIS-2017-0069).

Beginning March 15, 2021, during the second and final stage, APHIS will fully enforce APHIS Core message set submission using “reject” severity flagging. The delay until March 15, 2021, is technical only; filers should start submitting APHIS Core message set data on January 25, 2021.

http://USDA APHIS | When to Submit an APHIS Core Message Set, by Entry Type, in ACE

 

Step 1 APHIS Header

 

 

Step 2 PG 10 Category Types

APQ Example Fruits and Vegetables (AP0600):

Bell Peppers (Capsicum Annuum)

For Import requirements visit APHIS FAVIR system https://www.aphis.usda.gov/aphis/ourfocus/planthealth/sa_import/sa_permits/sa_plant_plant_products/sa_fruits_vegetables/ct_favir/ *

 

Headers Key Requirements:

Agency Program: APQ(Plant Protection and Quarantine )

Processing Code(Facilitates Agency routing channels): A01(route to CBP Agriculture) A03 is Pre-Cleared and Treated prior to arrive by USDA(Form PPQ 203)

Intended Use: 230.00 For Consume as Human Food

PG02 Commodity specification(Product or Component): Product • PG17 Specific Common Name: Green Bell Peppers

PG 10 Category Type: AP0600

PG 10 Category Code(Specific Break only use 601,602 or 603): 601 Above Ground Part

* PG 10 Commodity Qualifier and characteristic is based If LPCO requires the need to further identify and/or characterize the commodity.

 

Demo on IMEXNet PGA screen

Header:

Step 2 Arrival/Inspection PG 30

  • Inspection Status is [A] Anticipated arrival.

  • Date of arrival is [MMDDCCYY].

  • Inspection or Arrival Location Code is Schedule D [2]

  • Inspection or Arrival Location is port (Ex. Laredo) [2304].

Step 3 (PG-26s Quantities)

  • Level - This code identifies the level of packaging for the product. Outermost (largest=1) packages to the innermost (smallest=6) packages. There can be up to 6 levels of packaging. If reporting only one level, show the total quantity for the item and report that as level 1.

  • APHIS Condition: Quantity reported should be “net” quantities.

  • FDA Rules(Base unit) apply for UOM on APHIS

Step 4 Licenses (PG 13-14) and Sources(PG05-06)

** Multiple licenses could be required to input. (Example: Permit to Import and Phytosanitary Certificate

Depending on product 1 or more LPCO’s are required.

LPCO Issuer - Government Geographic Code Qualifier is always ISO [ISO] Location (Country/State/Province) of Issuer of the LPCO is utilized by APHIS to report Country issuing the LPCO and is [US].

LPCO Type identifies the Specific LPCO. [A19 Permit to Import PPQ 587]

LPCO Number is [Certificate Number]. ** Multiple licenses could be required to input. LPCO Date Qualifier is Expiration Date for A19.

 

Step 5 Entities, Route and Container

• License Authorized Party (LAP)

 

 

 

 

• PG32 Route (Origin Location)

 

 

 

• PG27(Containers)