Alliance Update Noteslegacydocs.kewill.com/documentation/alliance...ACE Post Summary Corrections...

Alliance Update Notes ACE Post Summary Corrections

October, 2011

2011 Update Notes

Copyright © 2011 by Kewill Inc.

TABLE OF CONTENTS

ACE Post Summary Corrections ....................... ................................................................................ 4

Summary of Changes to Alliance ..................... .............................................................................. 4

Setting Up Alliance for PSC........................ .................................................................................... 7

Entry Type Maintenance screen: .................................................................................................... 8

Validation Control Maintenance screen:.......................................................................................... 9

Correction Reason Codes Maintenance screen: ........................................................................... 10

Correction Reason Codes Detail Maintenance screen: ................................................................. 11

Alliance System Defaults Maintenance screen:............................................................................. 12

Post Summary Correction (PSC) Processing ........... ................................................................... 13

How to do a PSC Correction:........................ ................................................................................ 14

Shipment Processing: .................................................................................................................. 14

File Number Assignment screen:.................................................................................................. 15

Prepare PSC popup: .................................................................................................................... 16

PSC Explanation popup: .............................................................................................................. 17

PSC Header Reason Codes popup: ............................................................................................. 18

Quick Entry screen:...................................................................................................................... 19

Correction Reason Codes popup:................................................................................................. 21

E/S ABI Queue Update screen: .................................................................................................... 22

Review Validations Errors screen: ................................................................................................ 23

7501 Sample for PSC Transaction ............................................................................................... 25

Entry Summary Status Notification of PSC Rejection.................................................................... 26

Entry Summary Query – Liquidation Date Changes...................................................................... 26

Shipment Notes screen: ............................................................................................................... 27

Shipment Tracing – PSC screens..................... ............................................................................ 28

Shipment Tracing PSC Information popup screen:........................................................................ 28

ACE Entry Summary and PSC Transactions popup screen: ......................................................... 29

2011 Update Notes


ABS Send File for PSC Transaction: ............................................................................................ 30

Shipment Tracing PSC Explanation popup screen:....................................................................... 31

Shipment Tracing Quick Entry screen:.......................................................................................... 32

Shipment Tracing Quick Entry PSC Lines popup screen:.............................................................. 33

Appendix A – List of all Validations on which the n ew field, Valid for PSC, will be set to “N”..... 34

Appendix B – List of Header & Line Correction Codes .................................................................. 38

Post Summary Correction Header Reason Codes........ ............................................................... 38

Post Summary Correction Line Reason Codes .......... ................................................................. 39

Appendix C –Criteria Checking and Error Messages ... .................................................................. 42

2011 Update Notes


ACE Post Summary Corrections

Overview CBP is introducing the capability for ACE entry filers to make corrections through ABI to ACE entry summaries that have already been accepted by ABI and paid. These transactions are called Post Summary Corrections (PSC).

A new PSC indicator has been added to the ACE Entry Summary transaction. If it is set to Y, this indicates to CBP that the transaction is a PSC, not a regular entry summary. The PSC consists of all the records included on the Entry Summary, with some additional records to indicate correction reason codes and explanations.

PSC is allowed for ACE Entry Summaries that are an Entry Type that is valid for PSC, that have been sent and accepted by Customs and are not currently in a reject status, where the duty and fees have been paid and where a PSC that includes a request for accelerated liquidation has not already been accepted by CBP for the Entry.

Note on Billing . If the duty and fees amount changes because of the corrections, you must do an adjusted bill through Manual Billing to create the Invoice or credit the difference in amounts.

Summary of Changes to Alliance

Setting Up Alliance for PSC

• Set up new directory : In order to make the Post Summary Corrections available for searching and displaying to the screen in Shipment Tracing, a new directory must be created, [RUNTIME.ABS] . The logical ABS must be assigned to this directory. This setup will not be done by the Patch installation, so clients must complete this setup themselves. Contact the Support department if you need assistance with this setup.

• Maintenances : The following changes have been made to Alliance Maintenances to accommodate the new requirements. Note : Kewill will update these files during the installation process for any changes required for PSC. No setup work is required on the part of the user.

o Entry Type Maintenance – a new field, Valid PSC Ent Tp, has been added to indicate that Post Summary Corrections can be done for entries using that entry type.

o Validation Control Maintenance - a new field, Valid for PSC, has been added to indicate which validations will be performed on Post Summary Corrections.

o Correction Reason Codes Maintenance – this is a new maintenance to maintain the reason codes and the reason detail.

o Alliance System Defaults Maintenance – Three new PSC fields have been added to the screen.

2011 Update Notes


Shipment Processing The following changes have been made to Alliance to accommodate the new requirements:

• File Number Assignment screen - A new advertisement, PSC, now displays at the bottom of the screen when a file may be eligible for a Post Summary Correction. When you enter PSC in the ACTION field, the Prepare PSC popup screen will display.

• Prepare PSC popup screen – This is a new popup screen that lets you define the attributes of the PSC you will be entering.

• PSC Explanation popup screen – This is a new popup screen that displays after you have defined whether the PSC will include changes at the header level, line level or both.

• PSC Header Reason Codes popup screen – This is a new popup screen that displays if you indicated (H)eader or (B)oth on the Prepare PSC popup screen.

• Quick Entry screen – When you enter the line number, the PSC Line-level Correction Reason Codes screen will display. You can add, delete or change correction reason codes on the screen, as necessary. Afterwards, a “P” will display next to lines for which PSC Reason Codes have been entered.

• PSC Line-level Correction Reason Codes popup screen – This is a new popup that displays on the Quick Entry screen after you indicate which line is being corrected.

• Queue Update screen – For PSC entries, the Send E/S to Customs? question will change to Send PSC to Customs?

• Shipment Notes – A new note, “Post Summary Correction queued to send,” is created for Post Summary Corrections that are sent to ABI.

7501 form printing For PSC entries, the literal “POST SUMMARY CORRECTION” will print at the top of the form.

Validations Since a Post Summary Correction is basically an Entry Summary, most of the Entry Summary validations will be performed on a PSC. However, there are some validations that do not have to be performed on the Post Summary Corrections and these are marked as Valid For PSC “N” in Validations Control Maintenance.

Note : During installation of the patch, Kewill will set the flags for all validations that should not be run on Post Summary Corrections. [See Appendix for list of all Validations that are to be set to N.]

Shipment Tracing • PSC Information popup screen –This screen displays header-level information concerning each PSC that has been created for an entry.

• PSC Explanations popup screen –This screen displays the correction explanations that have been entered for each PSC that has been created for an entry.

• Shipment Tracing Quick Entry screen – A new view option, PSC-n, has been added to the Quick Entry screen to allow you to view PSC information related to the lines on the shipment.

2011 Update Notes


Dashboard • Three (3) new Dashboard Work Trans Status codes have been added for PSC: PSC Sent, PSC Rejected, and PSC Status Notf Rej.

2011 Update Notes


Setting Up Alliance for PSC

Overview The following must be set up to accommodate the PSC processing requirements:

• In order to make the Post Summary Corrections available for searching and displaying to the screen in Shipment Tracing, a new directory must be created, [RUNTIME.ABS] . The logical ABS must be assigned to this directory. This setup will not be done by the Patch installation, so clients must complete this setup themselves. Contact the Support department if you need assistance with this setup.

Note : Kewill will update the following maintenance files during the installation process for any changes required for PSC. No setup work is required on the part of the user.

• Entry Type Maintenance – a new field, Valid PSC Ent Tp, has been added to indicate that Post Summary Corrections can be done for entries using that entry type.

• Validation Control Maintenance – the screen includes a new field, Valid for PSC, to indicate which validations will be performed on Post Summary Corrections.

• Correction Reason Codes Maintenance – this is a new maintenance that has been added to maintain the reason codes and the reason detail. (Located on the Import File Maintenance Menu).

• Alliance System Defaults Maintenance – This screen has been modified to include three new PSC fields: PSC Max Days, PSC Liq Days, and PSC Paid Buffer.

2011 Update Notes


Entry Type Maintenance screen:

Entry Type Maintenance screen

A new field, Valid PSC Ent Tp, has been added to indicate that Post Summary Corrections can be done for entries using that entry type.

Note : Currently, only Entry Type 01, Consumption Entry, is supported by Alliance for PSC processing.

2011 Update Notes


Validation Control Maintenance screen:

Validation Control Maintenance screen

The screen has been redesigned and a new field, Valid for PSC, has been added to indicate which validations are valid for Post Summary Corrections.

Note : Kewill will update validations with a “Y” or an “N” in this field. [See the Appendix for a list of all validations where “N” was entered.]

2011 Update Notes


Correction Reason Codes Maintenance screen:

Correction Reason Codes Maintenance

screen

This is a new maintenance that has been added to maintain the reason codes and the reason detail. (Located on the Import File Maintenance Menu).

Note : The records in this file will be added by Kewill during installation. [See Appendix B for a list of the Header and Lines Reason Codes.]

2011 Update Notes


Correction Reason Codes Detail Maintenance screen:

Correction Reason Codes Detail

Maintenance screen

This is the Detail screen of the Correction Reason Codes Maintenance. To access this screen in the ACTION field of the Correction Reason Codes Maintenance screen, enter Det-n (where “n” is the line number). The Detail screen will display and allow you to add, change or delete detailed descriptions of the reason codes.

2011 Update Notes


Alliance System Defaults Maintenance screen:

Alliance System Defaults Maintenance

screen

This screen has been modified to include three new PSC fields:

• PSC Max Days = Enter a number of days (1 to 999). A Post Summary Correction (PSC) cannot be done on an entry whose entry date is older than this number of days.

• PSC Liq Days = Enter a number of days (1 to 999). An entry whose liquidation is scheduled for a date which is sooner than this number of days away is not eligible for a Post Summary Correction.

• PSC Paid Buffer = Enter a number (1 to 99) that represents the number of days after the payment date on an entry after which a Post Summary Correction can be done.

These fields are set up by Kewill when installing the patch. The values stored in the fields should not be changed unless CBP changes these limitations.

Note : Several fields on the screen have been moved around to make room for the new PSC fields.

2011 Update Notes


Post Summary Correction (PSC) Processing

Criteria for creating a PSC

The following conditions must be met before you can proceed to do a Post Summary Correction (PSC):

• The ACE Entry Summary was sent and accepted by Customs and is not currently in a reject status.

• Entry Summary duty and fees paid.

• The Entry Type is valid for PSC.

• The Entry is not locked. If an entry is locked, you must unlock it before attempting to do the PSC.

• A PSC that included a request for accelerated liquidation has not already been accepted by CBI for the entry.

PSC Data Element Reporting Restrictions

As per CBP, the following information CANNOT be cha nged on a PSC:

Control ID/Data Element

10-Record District/Port of Entry

10-Record Cargo Release Certification Indicator

10-Record Consolidated Summary Indicator

10-Record Live Entry Indicator

10-Record NAFTA Reconciliation Indicator

10-Record Reconciliation Issue Code

10-Record Payment Type Code

10-Record Preliminary Statement Print Date

10-Record Periodic Statement Month

10-Record Statement Client Branch Identifier

11-Record Importer of Record Number

20-Record Location of Goods Code

Consolidated Release Grouping (32-Record)

DOT Grouping (DT01-03-Record)

FDA Grouping (FD01-05 Record)

2011 Update Notes


How to do a PSC Correction:

Procedure The following table shows the steps involved in processing a PSC.

Shipment Processing:

Step Action Comment

1 Go to Shipment Processing; select Entry Summary on the opening screen.

The File Number Assignment screen will display next.

2011 Update Notes


File Number Assignment screen:

File # Assignment Screen

There is a new advertisement, PSC that displays at the bottom of the screen when a file may be eligible for a Post Summary Correction.

• You must enter “PSC” to indicate you will be preparing a PSC before making any changes to the entry.

• When you enter “PSC” in the ACTION field, the Prepare PSC popup screen will display.

Step Action Comment

2 On the File Number Assignment screen, (F)ind the file number for the entry summary to be corrected.

The file data will display on the screen. If the criteria listed in “Criteria for creating a PSC” are met, “PSC” will display as an option for input at the ACTION prompt.

3 Before making changes to any field on The Prepare PSC popup screen will

2011 Update Notes


Step Action Comment

the File Number Assignment screen, in the ACTION field, enter PSC.

display. [See Appendix for list of Criteria that will be checked and the related error messages that may be displayed.]

Prepare PSC popup:

Prepare PSC popup screen

This is a new popup screen that lets you define the attributes of the PSC you will be entering:

• (H)eader level / (L)ine level / (B) oth / (N)either – This field lets you define whether the correction is (H)eader information change, (L)ine information change, (B)oth, or (N)either.

• 02 Accelerate Liquidation Y/N – This field lets you indicate whether or not you want to accelerate Liquidation for the entry. If you choose to accelerate the liquidation of the entry, and the PSC is accepted by CBP, no further Post Summary Corrections can be prepared for the entry.

Step Action Comment

4 On the Prepare PSC popup, in the first field, 01 (H)eader level / (L)ine level / (B)oth / (N)either, enter the appropriate selection.

Enter one of the following to proceed:

• Enter “H” if you will just be making a correction to Header level data.

• Enter “L” if you will just be making a correction to Line level data.

• Enter “B” if you will be making corrections to both the Header and Line level data.

2011 Update Notes


Step Action Comment

The cursor will move to the second field.

5 In the second field, 02 Accelerate Liquidation Y/N, enter either “Y” or “N”.

Note : If you enter “Y” to Accelerate Liquidation then once this PSC is accepted by CBP, no future corrections can be made via a PSC.

6 Update the screen to continue. The PSC Explanation popup screen displays.

PSC Explanation popup:

PSC Explanation popup screen

This is a new popup screen that displays after you have completed the Prepare PSC screen. The screen allows for input of the Responsible Party (Importer, Broker or Other) and the PSC Explanation.

• The responsible party information is not part of the PSC that is sent to

2011 Update Notes


CBP.

• A maximum of ninety-nine (99) lines of explanation can be entered. The explanation should give a complete description of the header and line level corrections being made. This explanation will be reviewed by CBP personnel.

Step Action Comment

7 On the PSC Explanation popup screen, enter “I”, “B”, or “O” in the Responsible Party (‘I’mporter / ‘B’roker / ‘O’ther field. This is informational only and is not part of the PSC which will be sent to CBP.

The cursor will go to the first line of the PSC Explanation fields.

8 In the PSC Explanation field(s), enter the complete description of the header and line level corrections to be included on the PSC.

This is the overall reason for the Post Summary Correction. CBP Personnel will review this explanation.

If you entered (H)eader or (B)oth on the previous screen, the PSC Header Reason Codes popup will display.

PSC Header Reason Codes popup:

PSC Header Reason Codes popup screen

This is a new popup screen that displays if you indicated (H)eader or (B)oth on the Prepare PSC popup screen. This screen lets you enter up to five (5) Reason codes. CBP allows a maximum of five header reason codes per PSC.

Step Action Comment

9 On the PSC Header Reason Codes popup screen, enter the Header Reason Code(s) applicable to these corrections. If you do not know the

This popup lets you enter the Header Corrections Reason Codes.

2011 Update Notes


Step Action Comment

correct Reason Code, enter “?” to go to the Reason Code Search screen to do a look-up to the Reason Code file.

When you are done, the File Number Assignment screen will re-display.

10 Make any necessary changes, and update the File Number Assignment screen.

Quick Entry screen:

Step Action Comment

11 On the Quick Entry screen, follow the

2011 Update Notes


Step Action Comment

instructions on the table below, based on the type of corrections being made.

Quick Entry screen Access the Quick Entry screen to do any of the actions listed below:

1. Enter Additional commercial invoices.

2. Delete existing commercial invoices.

3. Add lines to an existing commercial invoice.

4. Remove lines from an existing commercial invoice.

5. Change commercial invoice header information.

6. Change line-level information on a commercial invoice.

Action How To

Enter additional commercial invoices. • Enter the commercial invoice header information.

• Enter the lines associated with the new commercial invoice.

• The explanation entered on the PSC Explanation screen should explain the circumstances which require a new commercial invoice to be added.

Delete existing commercial invoices. • Find the commercial invoice.

• In the ACTION field, enter D to delete the invoice.

• The explanation entered on the PSC Explanation screen should describe the circumstances that require that the commercial invoice be deleted.

Add lines to an existing commercial invoice. • Find the commercial invoice.

• In the ACTION field, enter A to append a line.

• After the line number is defaulted or entered, the line-level Correction Reason Codes screen will pop up.

• The appropriate reason code may be L01, “Invoice ”.

2011 Update Notes


Action How To

Remove lines from an existing commercial invoice.

• Find the commercial invoice.

• In the ACTION field, enter D-n to delete a line.

• The explanation entered on the PSC Explanation screen should describe the circumstances that require that the line be deleted.

Change commercial invoice header information.


• Change the header information as needed.

• The explanation entered on the PSC Explanation screen should describe why the commercial invoice information needed to be changed.

Change line-level information on a commercial invoice.


• Access the line to be changed.

• On the line-level Correction Reason Codes screen, enter the appropriate line reason code.

• After updating the Correction Reason code popup, change the necessary information on the line.

Correction Reason Codes popup:

Quick Entry - PSC Line-level Correction Reason Codes popup

screen

This is a new popup that displays on the Quick Entry screen after you indicate which line is being corrected. It allows you to add, delete or change correction reason codes on the screen, as necessary.

2011 Update Notes


Step Action Comment

12 Enter the Line level Correction Reason Codes associated with the line being changed.

When you are done, the Quick Entry screen will redisplay.

13 Make the required changes to the line, or add the new line’s information and if you have no other corrections to make, update the screen.

A “P” will display next to lines for which PSC reason codes have been entered.

When you complete all Commercial Invoice changes, the E/S ABI Queue Update screen will display.

E/S ABI Queue Update screen:

E/S ABI Queue Update screen

For PSC entries, the Send E/S to Customs? question will change to Send PSC to Customs?

2011 Update Notes


Step Action Comment

14 On the E/S ABI Queue Update screen, in the Send PSC to Customs? field, enter Y.

When you enter Y next to the Send PSC to Customs field, this corrections transaction will be set-up to be sent to CBP.

15 Complete the rest of the screen. When you update the screen, duty and fees will recalculate and Validations will run.

If there are no errors, the transaction will be sent to CBP with the next Send file.

You may print the 7501, or wait for ABI results and then print the 7501.

Review Validations Errors screen:

Review Validations Errors screen

If there are validation errors associated with the entry, you can press F10 to see the errors on the Review Validation Errors screen. Both the standard display showing all current validation errors and the FATAL errors only display

2011 Update Notes


have been modified to display validations that were generated and then corrected by users, in addition to current validations. If the Validation is a Fatal validation that was cleared by a user, “Cleared ” will display in the Status column.

Step Action Comment

16 If there were errors, fix them and then re-run Validations.

The Review Validations Errors screen will display the cleared errors.

17 When there are no more errors, the transaction will be sent to CBP with the next Send file.

You may print the 7501, or wait for ABI results and then print the 7501.

2011 Update Notes


7501 Sample for PSC Transaction

Overview The following notation will print at the top of the 7501 for PSC Entry Summaries: * * POST SUMMARY CORRECTION * * [See sample below.]

2011 Update Notes


Entry Summary Status Notification of PSC Rejection

Summary – Notification of PSC

rejection

A PSC reject can come from CBP either shortly after the PSC transaction is sent to ABI, or later, after Customs personnel have reviewed the PSC.

A rejection received shortly after the PSC transaction is sent indicates that the PSC failed the ABI edits. For example, if the PSC indicator is set, but there were no lines of PSC explanation provided, then that transaction would fail the ABI edits. (Note : The Alliance screens should prevent these types of rejections.)

Some time after a PSC transaction passes the ABI edits and the broker has been notified that the PSC transaction has been accepted, it will go through a review by CBP personnel. They will look at the reason codes and explanations and determine if the broker has used the proper correction reason codes and sufficiently explained the need for the PSC. If they feel there is something incorrect or missing they can reject the PSC. The broker will be notified of this type of rejection via the Entry Summary Status Notification. The ACE Entry Summary Status Report prints these rejections for PSC transactions. This is a report that you should already be printing to check for other status notifications on your ACE transactions.

PSC transactions that are rejected via the Status Notification must be corrected within 24 hours. If you receive a Status Notification rejection, use Shipment Processing to create a new PSC transaction to correct the incorrect data.

Entry Summary Query – Liquidation Date Changes

Summary – PSC Handling of liquidation

date

When CBP does the initial acceptance of a PSC transaction, they put the entry on “liquidation hold”. If you do an Entry Summary Query of the entry after this initial PSC acceptance, the liquidation date for the entry will be removed, and a note will be added to Shipment Notes indicating “PSC in progress, Liquidation on hold.” The liquidation date that previously existed for the entry will be moved into a new date, e.g., date number 92021 (Pre-PSC Liquidation Date).

Once CBP completes their detailed review of the PSC, and determines that it is OK as is, and no additional information is needed, they will take the entry off liquidation hold. An Entry Summary Query done at this point will return the new liquidation date. A note will be added to Shipment Notes indicating “New liquidation date created after PSC”.

2011 Update Notes


Shipment Notes screen:

Shipment Notes screen After the PSC has been queued to be sent to Customs, a new note, “Post Summary Correction queued to send,” is created for the entry. The user will not be allowed to delete or change this note.

2011 Update Notes


Shipment Tracing – PSC screens

Shipment Tracing PSC Information popup screen:

Shipment Tracing PSC Information popup

screen

This screen displays header-level information concerning each PSC that has been created for an entry. You can view PSC information on a file by doing the following:

1. Go to the Shipment Tracing Summary/Key Dates screen and pull up a file containing Post Summary Corrections.

2. Enter PSC in the ACTION field. If there is any PSC data, the PSC Information Popup screen will display. On the PSC Information popup, a summary of the PSC displays on the screen.

3. To search for ACE Send files with this Filer Code/Entry Number combination, enter SRH in the ACTION field. The ACE Entry Summary and PSC Transactions popup will display.

2011 Update Notes


ACE Entry Summary and PSC Transactions popup screen :

SRH – ACE Entry Summary and PSC

Transactions popup screen

This screen shows you what was previously submitted to CBP in the ABI Entry Summary Message. You will want a copy of the Entry Summary CATAIR available for reference purposes (http://www.cbp.gov/xp/cgov/trade/automated/modernization/ace_edi_messages/catair_main/abi_catair/)

Enter SRH in the ACTION field and the ACE Entry Summary and PSC Transactions popup will display with a list of transactions for the broker filer/entry number.

• Transactions with “PSC” listed in the right column indicate it is a PSC Send file.

• Enter the line number in the ACTION field to display the Send file to the screen.

http://www.cbp.gov/xp/cgov/trade/automated/modernization/ace_edi_messages/catair_main/abi_catair/

2011 Update Notes


ABS Send File for PSC Transaction:

Send File for PSC transaction

The Send file record will display on the screen.

To view additional data or to return to the previous screen, press <RETURN>.

2011 Update Notes


Shipment Tracing PSC Explanation popup screen:

Shipment Tracing PSC Explanation popup

screen

Enter “EXPL” on the PSC Information screen to display this explanations popup. This screen displays the correction explanations that have been entered for each PSC that has been created for an entry.

2011 Update Notes


Shipment Tracing Quick Entry screen:

Shipment Tracing Quick Entry screen

To access the Quick Entry screen data from the Shipment Tracing Summary/Key Dates screen, press F8 at the ACTION field to display the Inquiry Options Menu. Then select Quick Entry from the menu options.

To access the PSC Lines information for the file, enter PSC-n (where “n” is the line number on the screen) in the ACTION field. The PSC Lines popup screen will display.

2011 Update Notes


Shipment Tracing Quick Entry PSC Lines popup screen :

Shipment Tracing Quick Entry PSC Lines

popup screen

To access the Quick Entry PSC Lines popup screen, enter PSC-n (where “n” is the line number on the screen) in the ACTION field of the Shipment Tracing Quick Entry screen. The popup screen will display the PSC Line information.

• Press <Return > to see more records.

2011 Update Notes


Appendix A – List of all Validations on which the new field, Valid for PSC, will be set to “N”.

Overview A new field, Valid For PSC, has been added to Validation Control Maintenance. It will be set to “N” on the records for validations that should not be performed on a PSC. It will be set to “Y” on the records for validations that should be performed on a PSC.

The following validations will be set to “N” so that the validations will not be performed on a PSC. Users can set the flag to “N” on other validations, or remove the flag “N” from these validations if necessary.

Val Number Description

00090 Facility Type of 7 & 8 not valid for entry process

00100 FWS Information is required for the Tariff Number

00101 FWS information is required for the Tariff Number

00102 FWS Information is required for Tariff Number

00105 FWS information may be required.

00240 Payment type 6, 7, 8 invalid for entry type

00241 File has Census warning, check payment type

00242 Pay due date is equal to or later than PMS date.

00243 Invalid Payment Type For Non-CTPAT Customer

00420 Location must be specified

00430 Value Exceeds Informal Limit for the entry

00431 Value may exceed Informal limit for entry.

00435 Value Exceeds Informal Limit for the entry

00520 Food and Drug Admin. Form 701 may be required

00525 Food and Drug Admin. Form 701 may be required

00530 Food and Drug Admin. Form 701 is required.


2011 Update Notes





00540 USDA Meat Inspn may be required.

00545 USDA Meat Inspection is required

00550 Dept of Transportation Review may be required

00555 Dept of Transportation Review may be required

00560 Dept of Transportation review is required.

00561 Dept of Transportation Review is required.

00565 Dept of Transportation review is required.

00566 Dept of Transportation Review is required

00660 APHIS Lacey reporting may be required.

00661 APHIS Lacey reporting is required.

00662 APHIS Lacey reporting may be required.

00663 APHIS Lacey reporting is required.

00664 CR PGA Ingredient is Required

00665 ES PGA Ingredient is Required

00930 Informal Entry Type is invalid

00940 Consolidated Entry cannot exceed $1,250.00

01420 Must specify payment due date and/or type

01425 Filer must pay by ACH for Quota Entry

01430 Payment type indicator must be a 2,3,5,6,7 or 8

01435 Missing Payer Unit# for Payment type 3,5,6 OR 8

01445 Payment type indicator must match customer pay type

01455 Release Date is required for Consolidated Entries

01460 Release Dates cannot vary by more than 7 days

2011 Update Notes



01480 C/R Certified entries cannot be consolidated

01490 Consolidated Codes P & X Valid only on an Informal

01530 Pymt Type must be 2,3,5,6,7 or 8(Paperless E/S)

01570 Informal Entry type not allowed for this Tariff #





01600 Cannot resend after processing results returned

01640 More than one Release ID needed for consolidation

01720 FIRMS Code invalid for Port of Entry

01740 Total FDA Value exceeds total shipment value

01750 FDA Value exceeds total line value

01755 FDA line value exceeds total line value

01900 Tariff may require Prior Notice, not entered

01901 Tariff requires Prior Notice, not entered

01902 Tariff may require Prior Notice, not entered

01903 Tariff requires Prior Notice, not entered

01904 Prior Notice information missing or invalid

01905 Prior Notice information missing or invalid

02200 No Consignee IRS No, cannot do Unified Filing

02205 Unified filing missing required commercial entity.

02206 Invalid use of FT Action Reason Code

02210 Missing ISF Commercial entity MF for tariff (C/R)

02211 Missing ISF Commercial entity MF for tariff (E/S)

2011 Update Notes



02212 Missing ISF Commercial entity MF for tariff (FTZ)

02215 Unified Filing flag set, data not entered

05027 Consol Entry not allowed w/Multi. Countries Export

05021 Examination Location not on File

05022 Intensive Exam Location not on File

05023 Invoice Type not on File

07200 FDA description missing

07205 FDA description missing

07400 DOT Description missing

07405 DOT Description missing


99925 Arrival Date is more than 60 days after System Date

99950 Payment Due Date must be < 90 from the System Date

99955 Payment Due Date must be greater then System Date

99970 Payment Due Date must be within 10 days after Release

99975 Presentation date is greater than Payment Due Date

99980 Payment due date is more than 10 days from Import

2011 Update Notes


Appendix B – List of Header & Line Correction Codes

Overview The tables below contain the Post Summary Correction Reason Codes that Kewill will add to your system during the Installation process:

• PSC Header Reason Codes

• PSC Lines Reason Codes

Post Summary Correction Header Reason Codes

Post Summary Correction Header

Reason Code Description

H01 Entry Type 01-to-03 -- The Entry Type Code has been changed specifically from 01 to 03. [Note : This correction is not currently supported by Alliance because Alliance does not support creating ACE Entry Summaries for Entry Type 03.]

H02 Entry Type-Other -- The Entry Type Code has been changed (other).

H04 Mode of Transportation -- The Mode of Transportation (MOT) Code has changed.

H05 Bond-Surety -- The basic and/or additional Surety Company Code has changed.

H06 Bond–Superseding -- The Continuous Superseded Bond Indicator has changed.

H07 Bond-Other -- Other basic and/or additional bond data has changed. Includes Bond Type Code, Single Transaction Bond Amount, Single Transaction Bond Producer Account Number, Bond Waiver Indicator, and Bond Waiver Reason Code.

H08 Electronic Invoice Availability -- The Electronic Invoice Indicator has changed.

H09 Shipment Usage Type -- The Shipment Usage Type Code has changed.

H10 Consignee -- The Consignee Number has changed.

H11 Date of Importation --The Date of Importation has changed.

H12 State of Destination -- The U.S. State of Destination Code has changed.

2011 Update Notes


Post Summary Correction Header

Reason Code Description

H13 Header Fee -- One or more Entry Summary Header Fee (Header Fee Amount or Accounting Class Code) has changed. Includes 311 (Informal MPF), 500 (Manual Surcharge), and 496 (Mail).

H99 Data Change–Other -- Another Entry Summary Header Grouping data element, not listed above, has changed. Clearly describe the reason for the change in the PSC Filing Explanation grouping (36-Record).

Post Summary Correction Line Reason Codes

Post Summary Correction Line Reason Code Description

L01 Invoice -- The commercial invoice has changed or items (i.e., lines) were missed in the original submission. This change may result in more or fewer Entry Summary Line Item Groupings. For an EIP summary the change may affect the EIP Invoice Grouping (i.e., the Invoice Line Reference Detail).

L02 SPI -- The Trade Agreement / Special Program Claim Code has changed (but not the article classification).

L03 Classification -- The classification of an article has changed; the HTS Number has changed. This may affect the Article Set Indicator and/or the Trade Agreement / Special Program Claim Code.

L04 Value -- The value of the merchandise has changed (i.e., the Value of Goods Amount) or the basis/determination for the value has changed (e.g., the NAFTA Net Cost Indicator). This reason may be used if a currency conversion was a factor that resulted in a change to the value.

L05 Non-Dutiable Charges -- The Charges Amount has changed.

L06 Duty -- The Duty Amount has changed.

L07 COO -- The Country of Origin Code has changed.

L08 COE -- The Country of Export Code has changed.

L09 AD/CVD Case-Critical Circumstances -- The U.S. Department of Commerce has invoked ‘Critical Circumstances’ (regarding an Entry Type 01 Entry Summary filed 90 days prior to the Preliminary or Order period for an AD/CVD case).

2011 Update Notes



L10 AD/CVD Case-Party -- One or more Article Party Identifier(s) has changed; thus changing the AD/CVD case suffix.

L11 AD/CVD Case-Rate -- The Case Deposit Rate and/or Case Rate Type Qualifier Code has changed.

L12 AD/CVD Case-Scope -- The ‘scope’ of the AD/CVD case has changed.

L13 AD/CVD Case-Non-Reimbursement Statement -- The AD/CVD Non-Reimbursement Statement and/or AD/CVD Non-Reimbursement Declaration Identifier has changed.

L14 Ruling -- The Ruling Type Code or Ruling Number has changed.

L15 PGA-FCC -- The 740 Header and/or 740 Continuation has changed (includes a change to an FCC PGA Invoice Description)

L16 Tax -- The IR Tax Information (IR Tax Amount or Accounting Class Code) has changed.

L17 MPF -- The formal Merchandise Processing Fee (499) (User Fee Amount or Accounting Class Code) has changed.

L18 Fee-Other -- Another fee has changed (User Fee Amount or Accounting Class Code). Includes a change to 501-HMF or any agriculture commodity fee.

L19 Manufacturer -- The Manufacturer / Supplier Code has changed.

L20 Foreign Exporter -- The Foreign Exporter Code has changed.

L21 Sold to Party -- The Sold To Party Identifier has changed.

L22 Delivered To Party -- The Delivered To Party Identifier has changed.

L23 Textile Category -- The Category Code (for Textiles) has changed.

L24 Standard Visa -- The Standard Visa Number has changed.

L25 Textile Export Date -- The Date of Exportation (for Textiles) has changed.

L26 License/Certificate/Permit -- The License/Certificate/ Permit Type Code and/or License Number/ Certificate Number/Permit Number has changed.

L27 Softwood Lumber Export Price -- The Softwood Lumber Export Price amount has change.

2011 Update Notes



L28 Softwood Lumber Export Charges --The Softwood Lumber Export Charges amount has changed.

L29 Quantity Change -- Quantity (1, 2, or 3) has changed on any HTS Number for the article.

L30 Relationship Change -- The Related Party Indicator has changed.

L31 Shipping Weight -- The Gross Shipping Weight has changed.

2011 Update Notes


Appendix C –Criteria Checking and Error Messages

Criteria Checking for PSC

On the File Number Assignment screen, after you enter PSC, the system will check the following criteria for the transaction before displaying the Prepare PSC pop-up screen.

1. If Accelerated Liquidation has been requested on a previous PSC for this file, and that PSC was accepted, the message “Accelerated Liquidation request has been accepted,” will display.

2. If the file has already been included in a Reconciliation, the message “Entry is part of reconciliation” will display with the Recon Entry number.

3. If a PSC has been submitted for this file, and the acceptance/rejection results have not been received yet, the message “Waiting for prior PSC results” will display.

4. If the entry has already liquidated, the message “Entry was liquidated on 99/99/9999” (where the 9’s are a date), will display.

If the entry is scheduled for within 20 days, the message “Entry scheduled for liquidation within 20 days” will display.

5. If the entry is older than 270 days, even if it is not liquidated yet, you can’t do a PSC for it. If the entry is older than 270 days, the message “Entry date 99/99/9999 is more than X days ago” will display.

Copyright © 2011 by Kewill Inc. [Last revision date: 09/26/11]

Alliance Update Noteslegacydocs.kewill.com/documentation/alliance...ACE Post Summary Corrections...

Documents

Transcript of Alliance Update Noteslegacydocs.kewill.com/documentation/alliance...ACE Post Summary Corrections...