Customs and Trade Automated Interface Requirements
ACE Customs Bond/ CB
This chapter provides records pertaining to ACE Bond processing.TRANSACTION PROCESSING...... CB3
A description of the records required to process a Bond transaction.
INPUT RECORDS USAGE MAP...... CB5
OUTPUT RECORDS USAGE MAP...... CB7
RECORD DESCRIPTIONS
Record Identifier CB10 (Input)...... CB-9 mandatory Bond input record that provides data pertaining to the header levelinformation.
Record Identifier CB20 (Input)...... CB14
A conditionalBond input record that provides data pertaining to the single transaction bond.
Record Identifier CB30 (Input)...... CB15
A mandatory Bond input record that identifies the bond principal.
Record Identifier CB35 (Input)...... CB16
A conditional Bond record that is used to indentify a bond co-princpal.
Record Identifier CB36 (Input)...... CB17
A conditional Bond record that is used to report additional users of the bond.
Record Identifier CB40 (Input)...... CB18
A mandatory Bond input record that identifies the surety.
Record Identifier CB45 (Input)...... CB19
A conditional Bond record that is used to report a co-surety.
Record Identifier CB90 (Output)...... CB20
This is a mandatory Bond output record used to provide acceptance/rejection information to the bond filer.
Table of Changes
Revision Number / Date of Change / Section(s) Affected / Brief Description of Change1 / December 18, 2013 /
- Table of Content
- Record Layouts
Bond
The Bond chapter contains sections pertaining to bondtransaction processing.
Transaction Processing
Bondprocessing in this submission will be available to sureties and surety agents acting on behalf of a surety. The transaction set identifier for this input set is CB, and the response from CBP will be in the CX output transaction set.
A single transaction bond can only be associated with one transaction. The transaction will be associated to a primary single transaction bond and also one or more additional single transaction bonds as needed. The continuous bond will have several transactions associated to it over a specific time period. The transaction details in the CB20 record should only be reported for single transaction bonds.
The principal and surety are reported in the CB30 and CB40 records. The co-principal and co-surety may not always be applicable and are therefore conditional records. Bond users are only applicable to continuous bonds and should not be included when submitting a single transaction bond.
In the CX output transaction, each record that has an error will be followed by one or more CB90 error record describing the error. A final transaction-level CB90 record is returned at the end of the transaction indicating the overall acceptance or rejection of the transaction.
Key Data Elements To Be Filed
Data Element Name / Record Identifier / RequirementBond Designation Type Code / CB10 record / Mandatory
Bond Type Code / CB10 record / Mandatory
Bond Activity Code / CB10 record / Mandatory
Bond Amount / CB10 record / Mandatory
Execution date / CB10 record / Mandatory
Effective Date (Continuous Only)
Termination Date (Continuous Only) / CB10 record
CB10 record / Conditional Conditional
Bond Number / CB10 record / Conditional
Transaction ID Type Code (Single Transaction Only) / CB20 record / Mandatory
Entry Type Code (Single Transaction Only) / CB20 record / Conditional
Transaction ID (Single Transaction Only) / CB20 record / Mandatory
Principal ID Number / CB30 record / Mandatory
Principal Name / CB30 record / Mandatory
Co-principal ID Number / CB35 record / Conditional
Co-principal Name / CB35 record / Conditional
Bond User ID Number / CB36 record / Conditional
Bond User Name / CB36 record / Conditional
Surety Code
Agent ID Number
Surety Name
Surety Liability Amount
Co-surety Code
Agent ID Number
Co-surety Code
Co-Surety Liability Amount / CB40 record
CB40 record
CB40 record
CB40 record
CB45 record
CB45 record
CB45 record
CB45 record / Mandatory
Mandatory
Mandatory
Conditional
Conditional
Conditional
Conditional
Conditional
General Rules
Unused fields, which are defined as numeric, should not be zero-filled. These fields should be space filled or data errors may result.
Data should not be placed in fields defined as filler. If data is present in filler fields, an error message may be system generated.
When transmitting data, all letters must be upper case. While some applications may not return specific error messages when detecting lowercase letters, CBP cannot guarantee the consistency of processing results for data transmitted in lower case.
Data Elements
The data element descriptors are defined as:
CodeDescription
AThe data element is alphabetic only.
ANThe data element is alphanumeric only.
CThe data element is special characters.
NThe data element is numeric only.
X The data element is alphanumeric or special characters.
All data elements are in fixed-length format. If all positions are not filled, the formatting rules are:
CodeDescription
ALeft justify and Space fill.
ANLeft justify and Space fill.
CLeft justify and Space fill.
NRight justify and zero-fill.
XLeft justify and Space fill.
Note: If there is no data to insert in a field, Space fill.
INPUT RECORD USAGE MAPS
This section illustrates how the automated interface expects repeating groups to be structured within a CB transaction grouping. The transaction records described in this chapter must be preceded by the Batch and Block Control Header (A and B) records and followed by the Batch and Block Control Trailer (Y and Z) records as described in the ACE CATAIR Batch and Block Control chapter. Additional notes are provided for clarification on looping structures.
Record Usage Map for CB submissions to Add a New Basic Bond (N), Add an Additional Single Transaction (A), Substitute a Single Transaction Bond (S), or Supersede a Single Transaction Bond (C):
RecordReq. MaxLoop
IDNameDes. UseRepeatNotes
Block Control Grouping / M / 1Transaction Control Headers (A,B) / M
Bond Header Grouping / M / 999
CB10 / Bond Header information / M / 1
Single Transaction Bond Grouping / C / 1
CB20 / Single TransactionBond information / M / 1
Bond Principal Grouping / M / 1
CB30 / Principal information / M / 1
Bond Co-Principal Grouping / C / 99
CB35 / Co-Principal information / M / 1
Bond User Grouping / C / 99
CB36 / User information / M / 1
Bond Surety Grouping / M / 1
CB40 / Surety information / M / 1
Bond Co-Surety Grouping / C / 99
CB45 / Co-Surety information / M / 1
Transaction Control Trailers (Y,Z) / M
Designation: M = Reporting Mandatory; C = Reporting Conditional; O = Reporting Optional
Record Usage Map for CB submissions to Void the Single Transaction Bond (V), Replace the bond amount of the Single Transaction Bond (R), or Terminate the Continuous Bond (T):
RecordReq. MaxLoop
IDNameDes. UseRepeatNotes
Block Control Grouping / M / 1Transaction Control Headers (A,B) / M
Bond Header Grouping / M / 999
CB10 / Bond Header information / M / 1
Transaction Control Trailers (Y,Z) / M
Designation: M = Reporting Mandatory; C = Reporting Conditional; O = Reporting Optional
OUTPUT RECORD USAGE MAP
This section illustrates how the automated interface expects repeating groups to be structured within a Bond Transaction response (CX) transaction
Record Usage Map for CX responses to Add a New Basic Bond (N), Add an Additional Single Transaction (A), Substitute a Single Transaction Bond (S), and Supersede a Single Transaction Bond (C):
RecordReq. MaxLoop
IDNameDes. UseRepeatNotes
Block Control Grouping / M / 1Transaction Control Headers (A,B) / M
Bond Header Grouping / M / 999
Bond Header Error Grouping / M / 1
CB10 / Bond Header / M / 1
CB90 / Error Message / C / 9
Single Transaction Bond Error Grouping / C / 1
CB20 / Single Transaction Bondinformation / M / 1
CB90 / Error Message / C / 9
Bond Principal Grouping / M / 1
Bond Principal Error Grouping / C / 1
CB30 / Principal information / M / 1
CB90 / Error Message / C / 9
Bond Co-principal Error Grouping / C / 99
CB35 / Co-principal information / M / 1
CB90 / Error Message / C / 9
Bond User Error Grouping / C / 99
CB36 / User information / M / 1
CB90 / Error Message / C / 9
Bond Surety Grouping / M / 1
Bond Surety Error Grouping / C / 1
CB40 / Surety information / M / 1
CB90 / Error Message / C / 9
Bond Co-surety Error Grouping / C / 99
CB45 / Co-surety information / M / 1
CB90 / Error Message / C / 9
CB90 / Accept / Reject Message / M / 1
Transaction Control Trailers (Y,Z) / M
Designation: M = Reporting Mandatory; C = Reporting Conditional; O = Reporting Optional
Record Usage Map for CX response to Void the Single Transaction Bond (V), Replace the bond amount of the Single Transaction Bond (R), and Terminate the Continuous Bond (T):
RecordReq. MaxLoop
IDNameDes. UseRepeatNotes
Block Control Grouping / M / 1Transaction Control Headers (A,B) / M
Bond Header Grouping / M / 999
Bond Header Error Grouping / M / 1
CB10 / Bond Header / M / 1
CB90 / Error Message / C / 9
CB90 / Accept / Reject Message / M / 1
Transaction Control Trailers (Y,Z) / M
Designation: M = Reporting Mandatory; C = Reporting Conditional; O = Reporting Optional
Record Identifier CB10 (Input)
This is a mandatory Bond input record that provides data pertaining to the action code, entry filer code, entry number, entry type, importer of record number, bond holder, bond type code, bond activity code, and total entry value.
Record Identifier CB10 (Input)Data Element / Length/Class / Position / Status / Description / Note
Control Identifier / 2AN / 1-2 / M / Must always equal 10
Bond Designation Type Code / 1AN / 3 / M / A code representing the general purpose of the bond and the action to be taken. Valid codes are:
N = Add a new basic bond.
A = An additional bond; the bond that secures an AD/CVD, PGA or any other aspect not covered by the basic bond requirement. Applies to a Single Transaction Bond only.
V = Void theSingle Transaction Bondon file.
R = Replace the bond amount of the Single Transaction Bondon file.
S = Substitute for the bond presented at time of entry. Applies to a Single Transaction Bond only
C = Supersede the bond presented at time of entry. Applies to a Single Transaction Bond only.
T = Terminate theContinuous Bond on file. / 1
Bond Type Code / 1N / 4 / M / A code representing the bond type. Valid Bond Type Codes are:
8 = Continuous bond
9 = Single transaction bond
Bond Activity Code / 3AN / 57 / M / A code representing the bond activity type. If the code is less than 2 positions, it is left justified. Do not include hyphens, slashes, or other special characters. / 2
Bond Amount / 10N / 8-17 / M / The total value of the bond in whole US dollars. It must be greater than zero.If the amount is less than 10 positions, it is right justified. This data element must not contain decimals.
Execution Date / 6N / 1823 / M / A numeric date in MMDDYY (month, day, year) format representing the date the Bond is submitted to CBP.
Continuous Bond: Must be the same date or earlier than the effective date.
Single Transaction Bond: Must be the same date or earlier than the transaction date.
Surety Reference Number / 9N / 24-32 / O / This is an optional field provided for the Surety/Surety Agent’s internal use. A 9-digit self-generated surety reference number that a surety may opt to submit to CBP and have returned, unmodified in the response from CBP.
Effective Date / 6N / 3338 / C / A numeric date in MMDDYY (month, day, year) format representing the following:
Continuous Bond: Required field. Provide the date that transactions under the continuous bond may begin to be accepted by CBP.
Effective date must be the same or after the execution date.
Single Transaction Bond: Not applicable, space fill.
Termination Date / 6N / 3944 / C / A numeric date in MMDDYY (month, day, year) format representing the following:
Continuous Bond: Only used when the Bond Action Code = T. Provide the date that transactions under the continuous bond will no longer be accepted by CBP.
Termination date must be after the Effective date.
Single Transaction Bond: Not applicable, space fill.
Bond Number / 10AN / 45-54 / C / The CBP assigned number to the bond.
In CBs submitted to CBP: Only used when the Bond Action Code = V, R, or T. Provide the CBP assigned bond number for which the action should be taken.
Space fill on inputs when the Bond Action Code = N,A, C, or S.
In CXs returned from CBP: Upon successful completion of CB processing, a bond number will be provided here to communicate the number to the submitter. / 3
Filler / 26X / 5580 / M / Space fill.
Note1
For a Single Transaction Bond:
If the bond designation type code is ‘N’ and a bond is already on file for the Transaction ID, the CB submission will not be accepted.
If the bond designation type code is ‘A’ and no basic bond is on file for the Transaction ID, the CB submission will not be accepted.
If the bond designation type code is ‘V’ and the bond / transaction match has already occurred, the CB submission will not be accepted.
If the bond designation type code is ‘V’ or ’R’,the bond number must already be on file and the CBP bond number must be submitted in the CB10 record for ACE to identify the bond the action is against.
If the bond designation type code is ‘V’, the bond will bevoid and the bond number will not be reissued.
If the bond designation type code is ‘V’ or ’R’ and record CB20, CB30, CB35, CB36, CB40, or CB45 is submitted, the CB submission will not be accepted.
If the bond designation type code is ‘R’,’S’, or ‘C’ and the bond / transaction match has not occurred, the CB submission will not be accepted.
If the bond designation type code is ‘R’ or ‘S’,the Transaction ID Type Code = ‘1’ in the CB20, the bond / transaction match has occurred, and the Entry Summary is on file, the CB submission will not be accepted.
If the bond designation type code is ‘C’,the Transaction ID Type Code = ‘1’ in the CB20, and the bond / transaction match occurred over 90 days ago, the CB submission will not be accepted.
If the bond designation type code is ‘T’, the CB submission will not be accepted.
For a Continuous Bond:
If the bond designation type code is ‘N’ and a bond is already on file for the Bond Type Code, Bond Activity Type Code, and Principal ID Number combination, the CB submission will not be accepted.
If the bond designation type code is ‘A’, ‘V’, ‘R’, ‘S’, or ‘C’, the CB submission will not be accepted.
If the bond designation type code is ‘T’, the bond number must already be on file and the CBP bond number must be submitted in the CB10 record for ACE to identify the bond the action is against.
If the bond designation type code is ‘T’, the Termination Date is required and it must be after the Effective Date. The bond will be terminated and the bond number will not be reissued.
If the bond designation type code is ‘T’ and record CB20, CB30, CB35, CB36, CB40, or CB45 is submitted, the CB submission will not be accepted.
Note2
Valid Bond Activity Type Codes are:
CodeDescription
1Importer or Broker
1ADrawback Payments Refunds
2Custodian of Bonded Merchandise -Continuous Bond Only-
3International Carrier
3AInstruments of International Traffic -Continuous Bond Only-
4Foreign Trade Zone Operator-Continuous Bond Only-
5Public Gauger
6Wool & Fur Products -Single Transaction Only-
7Bill of Lading -Single Transaction Only-
8Detention of Copyrighted Material -Single Transaction Only-
9Neutrality -Single Transaction Only-
10Court Costs for Condemned Goods -Single Transaction Only-
11Airport Security Bond
16Importer Security Filing (ISF)
Note3
The Bond Number is assigned by CBP and will not be known until provided by CBP in the CX response upon successful processing of the bond. It is a required field for Bond Designation Type Codes‘V’, ‘R’, and ‘T’.
Record Identifier CB20 (Input)
This is a conditionalBond input record that provides data pertaining to the single transaction bond. It is required for a single transaction bond submission, but this record should not be submitted for a continuous bond.
Record Identifier CB20 (Input)Data Element / Length/Class / Position / Status / Description / Note
Control Identifier / 2AN / 1-2 / M / Must always equal 20.
Transaction ID Type Code / 1AN / 3 / M / Code identifying the type of transaction. Valid codes are:
1 = Entry Number (Activity Codes 1, 1a, or 6)
2 = ISF Reference Number (Activity Code 16)
3 = Seizure Number (Activity Code 10)
Entry Type Code / 2AN / 4-5 / C / A code identifying the type of entry being submitted.
Mandatory when Transaction ID Type Code equals 1.
Space fill on inputs when the Transaction ID Type Indicator does not equal 1.
Transaction ID / 40X / 645 / M / If the ID is less than 40 positions, it is left justified. Do not include spaces, hyphens, slashes or other special characters.
Filler / 35X / 4680 / M / Space fill.
Record Identifier CB30 (Input)
Principal Record
This is a mandatoryBondrecord that identifies the bond principal.
Record Identifier CB30 (Input)Data Element / Length/Class / Position / Status / Description / Note
Control Identifier / 2AN / 1-2 / M / Must always equal 30.
Principal ID Number Type / 3AN / 3-5 / M / The type of number being used to identify the Principal. / 1
Principal ID Number / 12X / 617 / M / Identification of the bond principal. / 2
Principal Name / 35X / 18-52 / M / The name of the bond principal identified.
Filler / 28X / 53-80 / M / This field is to be space filled
Note1
The qualifiers for Principal ID Number (left justified) are:
CodeDescription
EIEmployer Identification Number (IRS #)
ANICBP-assigned Number
34Social Security Number
Note2
Valid formats for the Principal ID Number are:
NNNNNNNNNXXInternal Revenue Service (IRS) Number
YYDDPPNNNNNCBP Assigned Number
NNNNNNNNNSocial Security Number
In these codes, N = number, X = alphanumeric, YY = the last two digits of the calendar year when the number is assigned, DDPP = the district/port code where the number is assigned.
Record Identifier CB35 (Input)
Co-principal Record
This is a conditional Bondrecord used to identifyco-principals. Each co-principal should be transmitted in its own CB35 record.
Record Identifier CB35 (Input)Data Element / Length/Class / Position / Status / Description / Note
Control Identifier / 2AN / 1-2 / M / Must always equal 35.
Co-principal ID Number Type / 3AN / 3-5 / M / The type of number being used to identify the co-principal. / 1
Co-principal ID Number / 12X / 617 / M / Identification of a co-principal for the bond. / 2
Co-principal Name / 35X / 18-52 / M / The name of the bond co-principal identified.
Filler / 28X / 53-80 / M / This field is to be space filled
Note1
The qualifiers for Principal ID Number (left justified) are:
CodeDescription
EIEmployer Identification Number (IRS #)
ANICBP-assigned Number
34Social Security Number
Note2
Valid formats for the Principal ID Number are:
NNNNNNNNNXXInternal Revenue Service (IRS) Number
YYDDPPNNNNNCBP Assigned Number
NNNNNNNNNSocial Security Number
In these codes, N = number, X = alphanumeric, YY = the last two digits of the calendar year when the number is assigned, DDPP = the district/port code where the number is assigned.
Record Identifier CB36 (Input)
Bond User Record
This is a conditional Bondrecord used to identifyadditional bond users. Each user should be transmitted in its own CB36 record.
Record Identifier CB36 (Input)Data Element / Length/Class / Position / Status / Description / Note
Control Identifier / 2AN / 1-2 / M / Must always equal 36.
Bond User ID Number Type / 3AN / 3-5 / M / The type of number being used to identify the bond user. / 1
Bond User ID Number / 12X / 617 / M / Identification of a user for the bond. / 2
Bond User Name / 35X / 18-52 / M / The name of the bond user identified.
Filler / 28X / 53-80 / M / This field is to be space filled
Note1