1. RECORD LAYOUT
   
   CREATE AN ABI TRANSACTION TO CAPTURE THE RECONCILIATION HEADER DATA AS WELL AS THE IMPORT ENTRY ASSOCIATION FILE DATA REQUIRED. THIS WILL BE THE ONLY MEANS OF ADDING A RECONCILIATION ENTRY SUMMARY TO ACS.
   
   CREATE a new ABI program to permit the filing of an entry type 09' reconciliation summary. It will permit these type 09' entries to be placed on a daily statement for collection via on-line or ACH.BR>
   
   

• 'R10' - Header record, containing ENA' level header data
  
  
• 'R11' - R14' (RESERVED FOR FUTURE USE)
  
  
• 'R15' - Header Continuation and Comment record. Contains brief description of issue
  
  
• 'R16' - Comment continuation. Optional record for continuing issue description
  
  
• 'R17' - Header payment record to permit payment information
  
  
• 'R18' - 'R19' (RESERVED FOR FUTURE USE)
  
  
• 'R20' - Import Entry Association Trailer record. May be up to 9,999 R20' records per Reconciliation. Record contains import entry level reconciliation data.
  
  
• 'R21' - Import entry level reconciliation data for fees. May be up to 10 records for an import ( R20'). Breaks fees down by collection class code within an import entry on the association file.
  
  
• 'R89' - Fee summary trailer record. May be up to 10 records. Summarizes all import entry fees to arrive at totals by collection class code.
  
  
• 'R90' - Recon Master summary record. Summarizes monetary amounts and import entry trailer record counts.
  
  
• 'R91' - Recon Master summary record for interest. Summarizes interest monetary amount from import trailers.
  
  

'RA' SPEC FOR HEADER RECONCILIATION ENTRY

Reconciliation Entry Add/Delete/Replace -

I N P U T    T R A N S A C T I O N - ABI transaction 'RA' ----------------------------------------------------------------------------

R10 record - MANDATORY (Recon HEADER Record)

1. The control ID will always be 'R' and the record type must be '10'. (MANDATORY)
   
   
2. The ACTION code must either be 'A', 'R' or 'D'. (MANDATORY)
   
   
3. The Recon Entry nbr must be in valid FFFNNNNNNNN format, with valid filer code and check digit. (MANDATORY)
   
   
4. The Recon Port must be one of the pre-identified prototype ports. Ports may be added as we go along. It must also be valid on RDP'. (MANDATORY)
   
   
5. The Importer ID must be in valid IR#(NN-NNNNNNNXX), SS# (NNN-NN-NNNN), or Customs Assigned # (NNNNNN-NNNN) format. (MANDATORY)
   
   
6. The surety code shown must be a valid code and as found on file, regardless of the status. This will be used to match against import entry surety codes. (MANDATORY)
   
   
7. The estimated Recon entry date must be given in MMDDYY format. Cannot be > 90 days from sys-date. If action code = 'A', date cannot be < system date. (MANDATORY)
   
   
8. The Recon Team must be a valid team for the DDPP of the Recon as shown. The second position of the team number must = 'R'. (MANDATORY)
   
   
9. The Issue code is mandatory and must be one of the indicated values. (MANDATORY)
   
   
10. The Aggregate Recon Indicator is mandatory. The only valid input is 'Y' or 'N'. If the indicator = 'Y', this will indicate to the program which subsequent entry record data is required (R20, R89). If 'N', all entry-by-entry data is required (R20, R21, R89). If the Aggregate Recon Indicator = 'Y', the Increase/Refund indicator must = '1'. (MANDATORY)
    
    
11. The Increase/Refund Indicator will be used to validate Aggregate Recon claim. If this indicator is a '2' or '3', aggregate indicator MUST = 'N'. (MANDATORY)
    
    
12. If the issue code = 'NF', the Earliest Import Date must be shown in MMDDYY format. (CONDITIONAL)
    
    
13. If the issue code is not = 'NF' (ie - it is one of the other values), the Earliest Entry Summary Date must be shown in MMDDYY format. (CONDITIONAL)
    
    
14. If a (Agent/Broker reference number) 4811 reference is to be used, it must be in valid IR#(NN-NNNNNNNXX), SS# (NNN-NN-NNNN), or Customs Assigned # (NNNNNN-NNNN) format, and must be valid for the importer ID on ACS file. If not used, space fill.(OPTIONAL)
    
    
15. The broker reference number is a free-form 9 character input for the use of the filer. If not used, space fill. (OPTIONAL)
    
    

1. The control ID will always be 'R' and the record type must be '15'. (MANDATORY)
   
   
2. The import entry source switch will be used to determine whether ALL of the associated import entries were filed within the 50 states. This is needed for financial reasons. An indicator of '1' means that ALL entries were filed within one of the 50 states. Import entries filed in Puerto Rico must be on a separate reconciliation. The indicator of '2' will mean that all of the imports were entered in Puerto Rico. Imports filed in the U.S. Virgin Islands must also be a separate reconciliation. An indicator of '3' will mean that all of the imports were filed in the Virgin Islands. (MANDATORY)
   
   
3. The Text Comment area will consist of 75 free-form characters. Minimum input will consist of at least 1 character in the first position. Unused positions will be space-filled.
   
   

1. The control ID will always be 'R' and the record type must be '16'. (MANDATORY)
   
   
2. The Text Comment area will consist of 75 free-form characters. Minimum input will consist of at least 1 character in the first position. Unused positions will be space-filled.
   
   
3. The 'R16' is an optional record that is only used if the initial 'R15' comment area is not long enough to accommodate the comment. Only one 'R16' record per 'R15' is permitted, for a total comment area of 150 character.
   
   

1. The control ID will always be 'R' and the record type must be '17'. (MANDATORY)
   
   
2. The payment type indicator must be '1', '2', '3', or '5'. '1' indicates single manual payment. '2' - '5' indicates statement process. (MANDATORY)
   
   
3. The payment due date must be a valid date in MMDDYY format. It cannot be a Sat., Sun., or holiday, nor can it be > 90 days from sys-date in the future. If the payment type is '1', this field MUST be space-filled. (CONDITIONAL) (See CATAIR ENS-74)
   
   
4. The client branch designation field is conditional upon filer wishing a separate statement for each branch designated. If spaces, only one statement will be issued for all offices, otherwise one will be issued for each designation. (CONDITIONAL) (See CATAIR ENS-74)
   
   
5. The DUTY payment amount field is the amount of duty that should appear as payable on the statement. It MUST be equal to the DIFFERENCE between the Total Original Duty and the Total Recon Duty on the 'R90' record. If the duty payment amount is a negative amount or zero, zero-fill the field. Input is in implied decimal format, right justified. Leading zeroes will be required. For 'R'(replacement) transactions, no new statement will be generated. While this is the new total duty due amount, filer will actually pay only the difference between the original paid amount and the new amount, if any. (MANDATORY)
   
   
6. The TAX payment amount field is the amount of tax that should appear as payable on the statement. It MUST be equal to the DIFFERENCE between the Total Original Taxes and the Total Recon Taxes on the 'R90' record. If the tax payment amount is a negative amount or zero, zero-fill the field. Input is in implied decimal format, right justified. Leading zeroes will be required. For 'R' (replacement) transactions, no new statement will be generated. While this is the new total tax due amount, filer will actually pay only the difference between the original paid amount and the new amount, if any. (MANDATORY)
   
   
7. The FEE payment amount field is the amount of Fees that should appear as payable on the statement. It MUST be equal to the DIFFERENCE between the Total Original Fees and the Total Recon Fees on the 'R90' record. If the fee payment amount is a negative amount or zero, zero-fill the field. Input is in implied decimal format, right justified. Leading zeroes will be required. This total will be broken down by class code from the 'R89' record(s) on the statement. For 'R' (replacement) transactions, no new statement will be generated. While this is the new total fee due amount, filer will actually pay only the difference between the original paid amount and the new amount, if any. Payment will have to be broken down by class code(s) as shown in the 'R89' records. (MANDATORY)
   
   
8. The INTEREST payment amount field is the amount of Interest that should appear as payable on the statement. It MUST be equal to the Total Recon Interest on the 'R91' record. If the interest payment amount is zero, zero-fill the field. Input is in implied decimal format, right justified. Leading zeroes will be required. For 'R'(replacement) transactions, no new statement will be generated. While this is the new total interest due amount, filer will actually pay only the difference between the original paid amount and the new amount, if any. (MANDATORY)
   
   

1. The control ID will always be 'R' and the record type must be '20'. (MANDATORY)
   
   
2. The trailer number is the sequence counter of 'R20' records. 'R20' records are numbered sequentially, beginning with '0001' and ending with a maximum of '9999'. Minimum input consists of at least ONE (1) 'R20' record. (MANDATORY)
   
   
3. The import entry number must be in FFFNNNNNNNN format and must be valid ENTRY SUMMARY in ACS as a type '01', '02', or '06' (without ADCVD) entry. The entry must have been previously "flagged" for reconciliation for the issue code indicated in the 'R10' record. (MANDATORY)
   
   
4. The entry port is the port code associated with the above import entry. Must be an exact match. (MANDATORY)
   
   
5. The ORIGINAL DUTY input is the total duty amount (either the PREVIOUS recon amount, or the paid and/or liquidated amount) as reflected on the above entry record. Input is in implied decimal format, right justified. Leading zeroes will be required. If original duty is zero, zeroes will be inserted in this field. If the 'R10' aggregate indicator = 'Y', must be zero-fill. (MANDATORY)
   
   
6. The EST. RECON DUTY is the total estimated reconciliation DUTY amount due against the above entry. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon duty is zero, zeroes will be inserted in this field. If the 'R10' aggregate indicator = 'Y', must be zero-fill. (MANDATORY)
   
   
7. The ORIGINAL TAX input is the total tax amount (either the PREVIOUS recon amount, or the paid and/or liquidated amount) as reflected on the above entry record. Input is in implied decimal format, right justified. Leading zeroes will be required. If original tax is zero, zeroes will be inserted in this field. If the 'R10' aggregate indicator = 'Y', must be zero-fill. (MANDATORY)
   
   
8. The EST. RECON TAX is the total estimated reconciliation TAX amount due against the above entry. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon tax is zero, zeroes will be inserted in this field. If the 'R10' aggregate indicator = 'Y', must be zero-fill. (MANDATORY)
   
   
9. The EST. RECON INTEREST is the total estimated reconciliation INTEREST amount due against the above entry. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon interest is zero, zeroes will be inserted in this field. If the 'R10' aggregate indicator = 'Y', must be zero-fill. (MANDATORY).
   
   
10. NOTE: For all above monetary fields, if the 'R10' Aggregate Indicator = 'Y', all monetary fields on 'R20' must = zero and be zero-filled.
    
    
11. The fee trailer counter is a count of all 'R21' fee trailer records transmitted as associated with this 'R20' import entry record. It should = the highest 'R21' record trailer number. This field will be edited to ensure we (or the filers) haven't missed records. If NO 'R21' records are used, the 'R20' fee trailer counter must = '00'. (MANDATORY)
    
    

1. The control ID will always be 'R' and the record type must be '21'. (MANDATORY)
   
   
2. If any fees appeared on the original import entry and the 'R10' aggregate indicator = 'N', at least ONE 'R21' required. If indicator = 'Y', NO 'R21' records are required. If 'R10' indicator = 'Y' and 'R21'(s) given, they will be ignored by the program.
   
   
3. The trailer number is the sequence counter of 'R21' records. 'R21' records are numbered sequentially, beginning with '01' and ending with a maximum of '10'. (MANDATORY)
   
   
4. The first fee class code will be input and MUST be a valid collection class code on the original import entry. (MANDATORY)
   
   VALID FEE CODES
   
   

   '053'	BEEF IMPORT ASSESSMENTS
   '054'	PORK IMPORT ASSESSMENTS
   '055'	HONEY IMPORT ASSESSMENTS
   '056'	COTTON IMPORT ASSESSMENTS
   '057'	PECAN IMPORT ASSESSMENTS
   '058'	OTHER AGENCIES
   '079'	SUGAR IMPORT FEE
   '090'	POTATO IMPORTS ASSESSMENTS
   '102'	RESERVED FOR LIME COLLECTIONS
   '103'	MUSHROOM IMPORTS ASSESSMENTS
   '104'	WATERMELON IMPORT ASSESSMENT
   '105'	SHEEP AND SHEEP PRODUCTS IMPORT ASSESSMENTS
   '499'	MERCHANDISE PROCESSING FEE
   '501'	HARBOR MAINTENANCE FEE - FORMAL ENTRY

   
   
   
5. The 1st ORIGINAL FEE input is the total fee amount (either the PREVIOUS recon amount, or the paid and/or liquidated amount) as reflected on the above entry record for the ABOVE class code. Must be > zero. Implied decimal format, right justified. Leading zeroes will be required. (MANDATORY)
   
   
6. The 1st EST RECON FEE is the total estimated reconciliation fee amount due against the above entry for the above class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. (MANDATORY)
   
   
7. The second fee class code, if input, MUST be a valid collection class code on the original import entry. If no second class needed, space fill. (CONDITIONAL)
   
   
8. The 2nd ORIGINAL FEE input is the total fee amount (either the PREVIOUS recon amount, or the paid and/or liquidated amount) as reflected on the above entry record for the ABOVE second class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If second class = spaces, zero fill this field. (CONDITIONAL)
   
   
9. The 2nd EST RECON FEE is the total estimated reconciliation fee amount due against the above entry for the above second class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. If the second fee class code > spaces, this field must be > spaces. If second class = spaces, zero fill this field. (CONDITIONAL)
   
   
10. The third fee class code, if input, MUST be a valid collection class code on the original import entry. If no third class needed, space fill. (CONDITIONAL)
    
    
11. The 3rd ORIGINAL FEE input is the total fee amount (either the PREVIOUS recon amount, or the paid and/or liquidated amount) as reflected on the above entry record for the ABOVE third class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If the third fee class code > spaces, this field must be > spaces. If third class = spaces, zero fill this field. (CONDITIONAL)
    
    
12. The 3rd EST RECON FEE is the total estimated reconciliation fee amount due against the above entry for the above third class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. If the third fee class code > spaces, this field must be > spaces. If third class = spaces, zero fill this field. (CONDITIONAL)
    
    
13. The 'R21' is repeatable up to 10 occurs. Each occur must have a minimum of the 1st fee class code and associated original/recon fee amounts. Multiple 'R21' records should only occur where not all applicable fees fit on a previous 'R21'.
    
    
14. NOTE: If the 'R10' Aggregate Indicator = 'Y', 'R21' records should NOT be used. If 'R21' record(s) used and 'R10' aggregate indicator = 'Y', program will ignore them.
    
    

1. The control ID will always be 'R' and the record type must be '89'. (MANDATORY)
   
   
2. The fee summary trailer number is the sequence counter of 'R89' records. 'R89' records are numbered sequentially, beginning with '01' and ending with a maximum of '10'. (MANDATORY)
   
   
3. The first fee class code will be input and MUST be a valid collection class code on at least one 'R21' record. The class code given MAY appear on MORE THAN ONE 'R21' record, but MUST be present on at least on one 'R21'. If 'R21' records were ignored or not given because 'R10' aggregate indicator = Y', code may = any valid fee class code. (MANDATORY)
   
   
4. The ORIGINAL FEE input is the TOTAL fee amount (paid and/or liquidated) as reflected for a recon for the ABOVE class code. The amount will be the SUM of the original fee amount for ALL 'R21' records on the recon for THE ABOVE class code. For example, if class code '499' appears on 5 different 'R21' records, the amount input here will be the sum of ALL 'R21' original fee amount fields for class code '499'. If no 'R21' records, insert total original fee for class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If original fee is zero, zeroes will be inserted in this field. (MANDATORY)
   
   
5. The TOT EST RECON FEE is the total estimated reconciliation fee amount due against the above entry for the ABOVE class code. The amount will be the SUM of the recon fee amount for ALL 'R21' records on the recon for THE ABOVE class code. For example, if class code '499' appears on 5 different 'R21' records, the amount input here will be the sum of ALL 'R21' recon fee amount fields for class code '499'. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. If 'R10' AGGREGATE INDICATOR = 'Y', tot est recon fee for class code must be = or > corresponding original fee. (MANDATORY)
   
   
6. The second fee class code, if input, MUST be a valid collection class code on at least one 'R21' record. The class code given MAY appear on MORE THAN ONE 'R21' record, but MUST be present on at least on one 'R21'. If no second class needed, space fill. If 'R21' records were ignored or not given because 'R10' aggregate indicator = Y', code may = any valid fee class code. (CONDITIONAL)
   
   
7. The ORIGINAL FEE input is the TOTAL fee amount (paid and/or liquidated) as reflected for a recon for the ABOVE second class code. The amount will be the SUM of the original fee amount for ALL 'R21' records on the recon for THE ABOVE second class code. For example, if class code '499' appears on 5 different 'R21' records, the amount input here will be the sum of ALL 'R21' original fee amount fields for class code '499'. If no 'R21' records, insert total original fee for class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If original fee is zero, zeroes will be inserted in this field. If the second fee class code > spaces, this field must be > spaces. If second class = spaces, zero fill this field. (CONDITIONAL)
   
   
8. The TOT EST RECON FEE is the total estimated reconciliation fee amount due against the above entry for the ABOVE second class code. The amount will be the SUM of the recon fee amount for ALL 'R21' records on the recon for THE ABOVE second class code. For example, if class code '499' appears on 5 different 'R21' records, the amount input here will be the sum of ALL 'R21' recon fee amount fields for class code '499'. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. If the second fee class code > spaces, this field must be > spaces. If second class = spaces, zero fill this field. If R10' AGGREGATE INDICATOR = Y', tot est recon fee for class code must be = or > corresponding original fee. (CONDITIONAL)
   
   
9. The third fee class code, if input, MUST be a valid collection class code on at least one 'R21' record. The class code given MAY appear on MORE THAN ONE 'R21' record, but MUST be present on at least on one 'R21'. If no third class needed, space fill. If 'R21' records were ignored or not given because 'R10' aggregate indicator = Y', code may = any valid fee class code. (CONDITIONAL)
   
   
10. The ORIGINAL FEE input is the TOTAL fee amount (paid and/or liquidated) as reflected for a recon for the ABOVE third class code. The amount will be the SUM of the original fee amount for ALL 'R21' records on the recon for THE ABOVE third class code. For example, if class code '499' appears on 5 different 'R21' records, the amount input here will be the sum of ALL 'R21' original fee amount fields for class code '499'. If no 'R21' records, insert total original fee for class code. Input is in implied decimal format, right justified. Leading zeroes will be required. If original fee is zero, zeroes will be inserted in this field. If the third fee class code > spaces, this field must be > spaces. If third class = spaces, zero fill this field. (CONDITIONAL)
    
    
11. The TOT EST RECON FEE is the total estimated reconciliation fee amount due against the above entry for the ABOVE third class code. The amount will be the SUM of the recon fee amount for ALL 'R21' records on the recon for THE ABOVE third class code. For example, if class code '499' appears on 5 different 'R21' records, the amount input here will be the sum of ALL 'R21' recon fee amount fields for class code '499'. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. If the third fee class code > spaces, this field must be > spaces. If third class = spaces, zero fill this field. If R10' AGGREGATE INDICATOR = Y', tot est recon fee for class code must be = or > corresponding original fee. (CONDITIONAL)
    
    

1. The control ID will always be 'R' and the record type must be '90'. (MANDATORY)
   
   
2. The Import Trailer number is the TOTAL COUNT of all 'R20' records for the reconciliation. (MANDATORY)
   
   
3. The TOTAL ORIGINAL DUTY input is the total duty amount (paid and/or liquidated) as reflected on the above entries. It is the SUM of the original duty amounts from ALL 'R20' records (or if aggregate, edited for format only). Input is in implied decimal format, right justified. Leading zeroes will be required. If original duty is zero, zeroes will be inserted in this field. (MANDATORY)
   
   
4. The TOTAL EST RECON DUTY is the total estimated reconciliation DUTY amount due as reflected on the above entries. It is the SUM of the reconciliation duty amounts from ALL 'R20' records (or if aggregate, edited for format only). Input is in implied decimal format, right justified. Leading zeroes will be required. If recon duty is zero, zeroes will be inserted in this field. If 'R10' AGGREGATE INDICATOR = Y', tot est recon duty must be = or > total original duty. (MANDATORY)
   
   
5. The TOTAL ORIGINAL TAX input is the total tax amount (paid and/or liquidated) as reflected on the above entries. It is the SUM of the original tax amounts from ALL 'R20' records (or aggregate, edited for format only). Input is in implied decimal format, right justified. Leading zeroes will be required. If original tax is zero, zeroes will be inserted in this field. (MANDATORY)
   
   
6. The TOTAL EST RECON TAX is the total estimated reconciliation TAX amount due as reflected on the above entries. It is the SUM of the recon tax amounts from ALL 'R20' records (or if aggregate, edited for format only). Input is in implied decimal format, right justified. Leading zeroes will be required. If recon tax is zero, zeroes will be inserted in this field. If 'R10' AGGREGATE INDICATOR = 'Y', tot est recon tax must be = or > total original tax. (MANDATORY)
   
   
7. The TOTAL ORIGINAL FEE is the total original fee amount and is the SUM of ALL the original fee amounts for ALL class codes on the 'R89' records. Input is in implied decimal format, right justified. Leading zeroes will be required. (MANDATORY)
   
   
8. The TOTAL EST RECON FEE is the total estimated reconciliation fee amount due on the above entries and is the SUM of ALL fee amounts for ALL class codes on the 'R89' records. Input is in implied decimal format, right justified. Leading zeroes will be required. If recon fee is zero, zeroes will be inserted in this field. If 'R10' AGGREGATE INDICATOR = Y', tot est recon fee must be = or > total original fee. (MANDATORY)
   
   

1. This record is required if the sum of the interest amounts from ALL 'R20' records is > zero. If sum of all 'R20' interest amounts = zero and the R10' AGGREGATE INDICATOR = N', this record will STILL be required and zero-filled. If the 'R10' AGGREGATE INDICATOR = Y' and interest > zero is due, 'R91' WILL be used, but not edited against 'R20' records. If 'R10' AGGREGATE INDICATOR = Y' and interest = zero, zero fill.
   
   
2. The control ID will always be 'R' and the record type must be '91'. (MANDATORY)
   
   
3. The TOTAL EST RECON INTEREST is the total estimated reconciliation INTEREST amount due as reflected on the above entries. It is the SUM of the recon interest amounts from ALL 'R20' records (unless 'R10' AGGREGATE INDICATOR = Y', in which case we edit format only). Input is in implied decimal format, right justified. Leading zeroes will be required. This field represents interest DUE and PAYABLE. The amount in this record will be reflected, as needed, in the 'R17' payment record. If NO interest is payable, zero fill this field. (MANDATORY)
   
   
4. If the USCS computed interest amount differs from the 'R91' amount, data will be accepted with a WARNING message to the effect "WARNING - ESTIMATED/CALCULATED INTEREST DIFFERENCE".
   
   

O U T P U T   T R A N S A C T I O N - ABI transaction 'RB' (output 'ER' records will be returned for each offending record, as will the record itself. An additional FINAL 'ER' will be returned for the entire entry. Only ONE '01' record will be returned.) (R90 Record)

1. This transaction will be the ONLY means of creating RECONCILIATION entries in ACS.
   
   
2. The A, B, Y, Z records will follow current ABI requirements, with some exceptions as noted below. Item 4, below, provides for changes in the 'B' control record to accommodate reconciliation processing.
   
   
3. In order for an ABI filer to be permitted to perform the new 'RA' transaction, the filer must have an ABI record on file, matching the 'B' record processing DDPP and FILER CODE, that shows he is OPERATIONAL for ABI Entry Summary Processing. If the record is NOT showing OPERATIONAL for entry summary or if there is no record for the processing DDPP/Filer Code, reject transaction with "SECURITY VIOLATION/ RA NOT ALLOWED" (or similar wording) error message UNLESS the filer has provided data in positions 56 and 47-53, as described below (logic similar to remote filing).
   
   
4. In editing the 'B' input record, we will treat RECONCILIATION entries similarly to the way we treat imports done via REMOTE FILING. If there is no processing DDPP/Filer Code match on file or if the filer record is not operational for entry summary, position 56 of the 'B' record MUST indicate '2' (RECONCILIATION) (see below spec for details of 'B' record change), else reject transaction with "SECURITY VIOLATION/RA NOT ALLOWED". NOTE: TO TAKE ADVANTAGE OF THIS FEATURE, THE FILER MUST MEET ALL OTHER CURRENT REQUIREMENTS IN EXISTENCE FOR REMOTE FILING WITH THE EXCEPTION OF ACH PAYMENT. OTHERWISE, THE FILER WILL HAVE TO HAVE AN ABI RECORD, OPERATIONAL FOR ENTRY SUMMARY, IN THE PROCESSING DDPP LOCATION.
   
   
   • MODIFY the ABI 'B' record logic to be used for 'RA' for position 56. Currently, position 56 of the 'B' record for 'EI' is either space (if not remote entry) or '1' (if remote entry). We will add another value = '2' to be used ONLY for the new 'RA' transaction where the filer does not have an ABI record for the 'B' record processing DDPP/Filer Code OR if the ABI record exists but is not operational for entry summary. The value of '2' will indicate RECONCILIATION, and can only be used with new 'RA' transaction. '2' will be invalid for the 'EI' or any other ABI application. If the filer uses a '2' with any other application, the transaction will be rejected.
     
     
   • If position 56 = '2', a preparer district port code must be shown in positions 47-50 and a preparer filer code must be shown in positions 51-53. If position 56 = '2' and either the preparer DDPP or code = spaces, reject transaction with message "PREPARER DDPP MISSING" or "PREPARER CODE MISSING", as appropriate. If above edits pass, the DDPP code in position 4-7 must = the DDPP of the entry in the 'R10' input record and the filer code in positions 8-10 must match the first 3 positions of the Recon Entry nbr in positions 11-13 of the 'R10' input record else reject transaction.
     
     
   • If positions 47-53 are filled in, program will validate that a record exists for that preparer filer code and preparer DDPP to relate them to the processing DDPP in positions 4-7. If a record exists, program will accept and continue. If no record exists for the relationship, reject transaction.
     
     
5. The correct sequence of records should be 'R10', 'R15', 'R16' - optional, 'R17', 'R20', 'R21', (additional 'R20's followed by 'R21's), 'R89' - multiples possible, 'R90', 'R91'. For those records with possible multiple occurs ('R20','R21', 'R89'), all such occurs must be grouped together in numerical sequence by counter. If records out of order, generate "LINE MISSING, INVALID, OUT OF SEQ" error and reject. For any records with sequences ( 'R20', 'R21', 'R89'), records must be in sequence order else generate same error and reject. Below is an example of record order:
   
   

   A record		mandatory
   B record		mandatory
   'R10'			mandatory
   'R15'			mandatory
   'R16'			optional
   'R17'			mandatory
   'R20'			mandatory
   'R21'			conditional (1st occur); optional (add'l occurs)
   ('R20)			add'l
   ('R21')			add'l
   'R89'			mandatory (1st occur); optional (add'l occurs)
   ( R89')			add'l
   'R90'			mandatory
   'R91'			mandatory
   Y record		mandatory
   Z record		mandatory

   
   
   
6. For output records, we will return the offending input record for any error and the 'R90' record for any final rejection or warning (as we do with other ABI transactions.)
   
   
7. If the transaction has been rejected, NO records will be created or updated.
   
   

1. For the input header record, the Control ID must = 'R' (or whatever final control ID is decided upon), and Record Type must = '10', else generate an ABI level error message and reject as we currently do for other ABI transactions.
   
   
2. Allowable action codes = 'A' (ADD), 'R' (REPLACE), and 'D' (DELETE). If any other code used, reject at ABI level:
   
   
   • If the action code = 'A', program will read to determine if a duplicate reconciliation record exists. If found, reject transaction with message "RECON EXISTS - ADD NOT PERMITTED" (or similar wording).
     
     
     • If entry exists but is not type '09', reject with "EXISTING ENTRY NOT RECON TYPE" message.
       
       
   NOTE: IN ORDER TO PERFORM A REPLACEMENT OR DELETE OF AN 'RA' TRANSACTION THAT HAD A PAYMENT INDICATOR OF '2', '3', OR '5' WHERE THE STATEMENT HAS NOT YET BEEN PAID, THE FILER MUST PERFORM AN 'HP' TRANSACTION TO REMOVE THE ENTRY FROM STATEMENT PROCESSING BEFORE AN 'RA' REPLACE/DELETE CAN BE PERFORMED .
   
   
   • A REPLACE transaction ('R') may ONLY be performed if the entry is NOT in a Customs-accepted status. An entry re-transmitted via an 'R' transaction will NOT be placed on a new statement , and would be automatically subject to a single payment. If a reconciliation is in Customs-accepted status, replacement will reject with error "EXISTING RECON IN CUSTOMS STATUS" (or similar wording).
     
     
     • Additionally, the entry must already be on file as a type '09' entry and must appear on file for a replace to be valid, else reject with "EXISTING ENTRY NOT RECON TYPE" message.
       
       
   • A DELETE ('D') transaction can ONLY be done if the entry is not in Customs-accepted status AND a preliminary statement for the entry has NOT been cut, OR the entry has been deleted from a statement, OR the entry is not on statement and has NOT been paid.
     
     
     • A 'D' transaction will only require the submission of the normal A,B,Y,Z records and the 'R10' header record. If the 'R10' action code = 'D', only the entry number and port (positions 5-19) will be required input.
       
       
     • Additionally, the entry must already be on file as a type '09' entry and must appear on file for a delete to be valid, else reject with "EXISTING ENTRY NOT RECON TYPE" message.