cbp and trade automated interface requirements...record identifier se61 (input) ..... 67 record...

CBP and Trade Automated

Interface Requirements

ACE Cargo Release

October 16, 2020 Version 28

Pub#0875 0419

This chapter provides records pertaining to ACE Cargo Release (formerly

known as Simplified Entry) processing.

Be Advised:

A filer who transmits data or information through any electronic means to

CBP certifies, by the act of transmitting such data or information, that the

data or information transmitted is true and correct to the best of the filer’s

knowledge and belief. The filer also declares that all statements in an

electronically transmitted entry, entry summary, invoice, claim, or other filing

and all other information or data filed with the entry are true and correct to

the best of the filer’s knowledge and belief, and that the filer will produce at

once any data or information showing that the statements are not true and

correct.

ACE Cargo Release / SE

Note to reader:

This document is not intended to be a stand-alone handbook to conducting business

with U.S. Customs and Border Protection (CBP).

This CATAIR chapter provides direction on format and syntax for submitting the

ACE Cargo Release (SE) transaction dataset, and for submitting a single dataset

which satisfies the filing requirements for both Importer Security Filing (ISF) and

Cargo Release. Information included regarding definitions, business rules and input

parameters is present for the purpose of facilitating the implementation of various

statutes, regulations, directives, and policy.

While primarily a technical document, this text is written with the presumption that

the reader has some familiarity with applicable CBP laws, regulations, policies and

procedures.

Customs and Trade Automated Interface Requirements

October 16, 2020 – Version 28 ACE Cargo Release/SE SE-1

Table of Contents

Table of Changes: V19 – Forward

Transaction Processing…..………………………………………..………………………………12

Input Record Usage Map for “A” Add and “R” Replace Actions…………..……………………18

“D” Action to Cancel a Cargo Release Transaction………………...……………………………20

“U” Action to Update Bill of Lading & Manifest information on a Cargo Release transaction.…21

Output Record Usage Map………………………………………..………………………………22

Unified Entry/ISF Filing…………………………………………..………………………………24

Importer Security Filing (SF) Input Record Usage Map…………..……………………………...26

Record Identifier SE10 (Input)……………………………………………………………………27

Record Identifier SE11 (Input) ....................................................................................................... 32















Record Identifier SF10 (Input) ....................................................................................................... 68









Record Identifier SE90 (Output) .................................................................................................... 80

Appendix A (updated 10/8/2015)………………………………………………….......................81

Appendix B ..………………….………………………………………………….......................82

Appendix C ..………………….………………………………………………….......................83

Table of Changes: Version 1 through Version 18…..………………….…………………………85



Table of Changes: V19 – Forward

(*See “Table of Changes: Version 1 – Version 18” at the end of this document for changes made

prior to Version 19)

Revision

Number

Date of Change

Section(s) Affected

Brief Description of Change

28 October 16, 2020 Transaction Processing

Key Data Elements to Be Filed

Correction from previous

version. The following

sections were not changed.

Transaction Processing


27 August 5, 2020 Transaction Processing


Input Records

Updated SE10 Record:

Removed Entry Type 24, Trade Fair Entry (only

available for Non-ABI

entries) from Note 2

Updated Transaction

Processing:

Updated text with information on Consignee

for Entry Type 86

Updated Key Data Elements

to Be Filed:

Updated data element requirements for Entry

Type 86


Updated Notes 1 for Entry Type 86


Updated Notes 1 for Entry Type 86

26 June 2, 2020 Input Records Updated SE10 Record:

Entry Type 24, Trade Fair Entry moved to Note 2

instead of Note 5

25 May 29, 2020 Input Records Updated SE10 Record:

Added Entry Type 24, Trade Fair Entry

24 March 19, 2020 Input Records Updated SE60 Record:

Updated Note 2 which now describes the format

for inputting Chapter 99

and Chapter 1-97 HTS

codes

Note 3 was previously Note 2 which discusses



Line Value being

mandatory for Entry Type

86

23

Note: This

version

includes all

changes

from Draft

version 21

through

22.2, with

the exception

of the SE12

record.

November 25,

2019



Input Records

Updated Transaction

Processing: Updated text with information

on Consignee and Seller for

Entry Type 86


to Be Filed:

Updated data element requirements for Entry

Type 86


Updated Notes 12 and 13 for Entry Type 86


Updated Notes 7, 11, and 12 for Entry Type 86






Updated Note 2 for Entry Type 86

22.2

July 23, 2019 Input Records Updated SE11 Record:

Removed language from Description of Immediate

Delivery. This was

changed from version 21

and will be updated at a

future date

Updated Note 5 from

“For Future Use” to “TBD”. This was changed from version 21

and will be updated at a

future date

Added SE12 Record:

Added SE12 record for additional bond data

22.1

July 1, 2019 Input Records Updated Transaction Processing:

Updated with reference to Consignee

and Seller for Type 86


To Be Filed:

Importer of Record



Number made

Conditional

Buyer Name and Address made

Conditional

Consignee Number made Conditional

Manufacturer/

Supplier Name and Address made

Conditional


Updated Planned Port of Entry Description

Split Shipment Release

Code – removed Note 11 reference

Port of Unlading – removed Note 11

reference

Updated Note 1 to include replacement

actions

Updated Note 7 to include rule for

updating Planned Port

of Entry on Update

transaction

Updated Note 11 to include exception for

entry type 06

Added Note 13 for entry type 86


Updated Contact Name and Contact

Phone Description

Updated Note 2 reference to Appendix

A


Added Note 12 in reference to entry type

86


Updated record description to include

Consignee Name and

Address for low value

shipment for entry

types 11 and 86



Updated Note 1 with parties required for

entry type 86

Updated Note 2 to reference entry type 86


Removed Note 2 reference from

Address Information


Updated record description to include

Consignee Name and

Address for low value

shipment for entry types 11 and 86

Updated Note 1 with parties required for

entry type 86

Updated Note 2 to reference entry type 86

22 March 20, 2019 Input Records Updated SE10 Record:

Importer of Record Type made

Conditional

Importer of Record made Conditional

Added entry type 86 to Note 7



Updated Quantity Description for entry

type 86

Updated Note 7 with reference to entry type

86



Entity Identifier Qualifier made

Conditional, updated

description, and

removed reference to

Note 2

Entity Identifier made Conditional, updated

description, and

removed reference to

Note 2




Updated Note 2 for entry type 86

21 December 6,

2018 Input Records Future Use items are removed

and are now in draft

CATAIR.* Note: This was

never published.

20.1

August 7, 2017

a. Table of Contents

b. Transaction Processing

c. Input Record Usage Map for “A” Add and “R” Replace

Actions

d. “D” Action to Cancel a Cargo Release transaction

e. Input Records

Updated format of the Table

of Contents. Cntl+Click to

follow to specific section page

link.

Removed the first sentence

of the second paragraph

regarding use of the SE13

Under the section entitled

Rules covered by this

draft of the Cargo

Release

Implementation

Guide removed the

following rule as no

longer necessary to list:

“7. When the ACE

Cargo Release (SE)

transaction is used the

corresponding entry

summary must be filed

in ACE.”

Renumbered the

remaining listed

rules.

Formerly known as:

Input Record Usage Map

Added back Note 1.

Added Note 2

Removed Note 3.

Updated SE10 Record Descriptions:

Updated the references made

regarding ACS

Appendices to refer

to ACE Appendices.



Revision

Number

Date of Change

Section(s) Affected


Updated SE11 Record: Updated description for

Originating Warehouse

Entry Number from

referencing ACS

Appendix B to referring

to ACE Appendix B.

Removed the following sentence from the end

of Note 1 with regard to

reporting entities: “All

the other parties are

required to be reported

using a name and

address.”


Removed the following from the Header

introductory text: “BY

(Buyer), ST (Ship To

Party)”.

Removed the following sentence from the end

of Note 1 with regard to

reporting entities: “All

the other parties are

required to be reported

using a name and

address.” 20

PLEASE

NOTE:

Version 20

was not

published

externally

to

CBP.gov

June 8, 2017

{Changes from

Feb 17, 2017; to

April 12, 2017; to

May 25, 2017}

a. Overall

b. Table of Contents

c. Input Records Usage Map

Added Cover Page to this

document

Created new Table Section and

moved the bulk of historical

records for Table of

Changes.

Updated Input Records Usage

Map:

Adjusted Name for SE13 Record

SE13 Record now

marked as Mandatory

Line Level Entity Grouping now shows a

maximum of 7 Loop

Repeats.



Revision

Number

Date of Change

Section(s) Affected


d. “D” (Cancel) Action Input Usage Map

e. “U” (Update) Action Input Usage Map

f. Output Records Usage Map

g. Input Records

“D” (Cancel) Action Input Usage Map updated and reformatted for consistency

“U” (Update) Action Input Usage Map updated and reformatted for consistency

Output Usage Map updated

with column headers for

consistency


Data Element Name text for Entry Date

Election Code has

been updated to:

“Entry Date Election

Code *(for Future

Use)”

Description for Entry Date Election Code

has been updated —

While the transaction

schema accepts and

persists “P” and “A” as

valid inputs, no code

has been programed for

Immediate Delivery

functionality. This is

now marked as being

“for Future Use”.

Note 5 of the SE11 has been updated to notate

that it applies to Future

Use.


Introductory text updated—

SE13 is scheduled to

be a Mandatory

record for all SE

filings sometime after

August 1, 2017. Updated SE15 Record:

Description for Bill Type Indicator has

been updated

regarding use of M/H

bills of lading, and

those Modes of



Revision

Number

Date of Change

Section(s) Affected


h. Table of Changes (Archived)

Transportation which

require Bill Type “R”

(Regular/Simple).

Description for Issuer Code of Bill of Lading

Number has updated

to add ‘MOT 50:

Mail’ as a Mode of

Transportation where

this data element

should be space filled.

Text of Note 8 has

been updated with

regard to Bill Type

usage.

Text of Note 9 has been updated to

instruct that the

Quantity reported must

be greater than zero.

Text of Note 9 has been updated regarding

Bill of Lading input for

Modes of

Transportation 32, 33,

34.


Updated text of Note 3 with “Report Quantity,

for example, as

‘00000001’ (padded

with leading zeros).”


Appended Note 1 to include “PER”

(Perishable) Reference

Identifier Qualifier, &

explanation/definition.


Added Note 2 to indicate when reporting

Line Value is

mandatory.

Added new Table Section at the

end of this document to

accommodate historical

Table of Changes

records.



Revision

Number

Date of Change

Section(s) Affected


19 Feb 17, 2017 a. Input Records Updated SE10 Record:

Port of Entry is required for Non-AMS

bills

Updated Note 5 with Port of Entry

information

Port of Unlading is required for MOT 50,

60, and 70

Updated Note 2 to remove “For Future

Use”

Updated Note 5 for Non-AMS

Updated Note 7 Port of Entry

Updated Note 11 regarding MOT being

required on entry type

06 if Bill of Lading is

provided


Removed text from header section

regarding entry type 06

Updated Description section for Bill Type

Indicator, Bill of

Lading Number and

Quantity with new

reference for Note 10

Updated Note 3 for Bill of Lading and In-Bond

requirements on entry

types 06 & 22

Updated SCAC Description for MOT

32, 33, 34, and 60

Updated Note 9 for SCAC

Added Note 10 regarding entry type 06



ACE Cargo Release

This chapter contains sections pertaining to ACE Cargo Release (SE) transaction processing.


ACE Cargo Release processing in this submission will be available to importers and customs

brokers acting on behalf of an importer. The transaction set identifier for this input set is SE, and

the response from CBP will be in the SX output transaction set. The cargo release processing status

from CBP will be in the SO output transaction set described in the SO chapter of the CATAIR.

After a "D" (Cancel) action has been accepted by CBP, the entry remains on file with a status of

Cancelled. The entry number associated with the Cancelled entry cannot be reused.

An ACE Cargo Release can be associated with one or more Bills of Lading. With the exception

of a single entry for a Split Shipment (i.e. cargo tendered to the carrier as a single shipment under

a single bill of lading for carriage on a single conveyance, and subsequently split by the carrier for

transport on multiple conveyances) all Bills of Lading must arrive at the U.S. Port of Unlading on

a single conveyance.

One or more SE15 records may be used to report all the required Bill of Lading numbers. For Air

mode of transportation:

If an Express Carrier Tracking Number is used, then the AWB prefix must be reported along with the tracking number in the Bill of Lading Number data element.

If a House Bill of Lading is issued for the cargo under a Master Bill of Lading, then two SE15 records must be used with the AWB Prefix and Master Bill of Lading number

reported in the Bill of Lading Number data element of the first record, and the House Bill

of Lading number reported in the Bill of Lading Number data element of the second record.

If a Simple Bill of Lading number is used, then AWB prefix must be reported along with the Simple Bill of Lading number in the Bill of Lading Number data element.

There is one Importer of Record per ACE Cargo Release transaction, and this is reported in the

SE10 record only; all other required parties can be reported at the header or line level. The SE30,

SE35, and SE36 records are used to report a party at the header level; the SE50, SE55, and SE56

records are used to report a party at the line level. Consignee (CN) and Manufacturer (MF) are

required at the line level (For type 86, Consignee and Seller only); however, if all line items have

the same Consignee or Manufacturer (or Seller for type 86), then that party may be reported at the

header level only and will be deemed to be associated to all line items. The remaining parties are

required at the header level, though may be reported at the line item if that allows for more

accurate reporting.

The Importer of Record and Consignee are reported using an identifier in an Importer of Record

number format. Refer to the Notes to the SE30 and SE50 record sets for information about an

exception for low value shipments (Entry Types 11 and 86) when the entity name and address



may be reported for a Consignee. All the other parties are required to be reported using a name

and address.



The Output transaction will always return the SE10 and SE15 records, as well as any record on

which an error occurs. Each record that has an error will be followed by one or more SE90 error

record describing the error. A final transaction-level SE90 record is returned at the end of the

transaction indicating the overall acceptance or rejection of the transaction.

Rules covered by this draft of the Cargo Release Implementation Guide

1. Only Air, Ocean, Rail, Truck, Pipeline, Mail, Passenger, Auto, Pedestrian, and ‘Road, other.

Includes foot and animal-borne’ modes of transportation;

2. Only Entry Types 01, 02, 03, 06, 07, 11, 12, 21, 22, 23, 52 and 86;

3. Only a continuous bond and an electronically-filed single transaction bond may be used to support the entry filing at this time;

4. The filing of entries on unassembled or disassembled entities will not be supported at this time.

5. If the Port of Entry is different from the Port of Unlading, and, the Port of Entry and Port of Unlading are not both part of the same local port cluster for cross-port processing, then no

release will be issued unless an In-Bond is found to be associated with the bill of lading in the

CBP system.

6. If an In-Bond number is provided in the entry submission, the Planned Port of Entry must also be provided.

7. Entries that require additional data for another government agency will not be accepted unless the specific PGA filing is one that CBP has announced it is supporting with the ACE Cargo

Release (SE) transaction data set.

8. Use of CBP-created Encrypted Number [Format: -CCCCCCCCCCC] for Consignee is not accommodated for the ACE Cargo Release (SE) transaction at this time.

9. In a Unified Entry/ISF filing, the Importer of Record for Entry purposes and the ISF Importer must be the same entity, with the same Importer of Record Number.

10. In a Unified Entry/ISF filing, the entry must be for the full manifested bill of lading quantity.

11. In a Unified Entry/ISF filing, the same bond must cover both the import entry/entry summary transaction and the Importer Security Filing transaction.



Key Data Elements To Be Filed

Data Element Name Record Identifier Requirement

Importer of Record Number SE10 record Conditional

Buyer Name and Address SE30, SE35, and SE36 records;

or SE50, SE55, and SE56 records Conditional

Consignee Number SE30 record or SE50 record Conditional

Seller Name and Address SE30, SE35, and SE36 records;

or SE50, SE55, and SE56 records Mandatory

Ship To Party Name and Address SE30, SE35, and SE36 records;

or SE50, SE55, and SE56 records Optional

Consolidator Name and Address SE30, SE35, and SE36 records;


Container Stuffing Location Name and

Address

SE30, SE35, and SE36 records;


Manufacturer / Supplier Name and Address SE30, SE35, and SE36 records;

or SE50, SE55, and SE56 records Conditional

HTS 10-digit number SE60 record Mandatory

Country of Origin SE40 record Mandatory

Bill of Lading / House Air Waybill Number SE15 record Mandatory

Bill of Lading issuer code SE15 record Conditional

Entry Number SE10 record Mandatory

Entry Type SE10 record Mandatory

Estimated Entry Value SE10 record Mandatory



Record Layout Key

This sub-section is copied from ACE CATAIR Appendix Q, dated July 10, 2013, and

provides the record layout key for ACE ABI CATAIR chapters. It describes the columns

of the record layout definitions contained in ACE ABI CATAIR chapters. Please note that

this key is different from the record layout key for the ACS ABI CATAIR.

Data Element:

Contains the name of the reported data field.

Length:

Indicates the maximum, allowed length of the reported data element.

Class: Defines the domain of values accepted for the data element. The class definition represents

the accepted domain to be used in all filing scenarios. Class codes are as follows:

S = Space ONLY.

A = Alphabetic Data. Consists of characters A through Z (uppercase ONLY).

N = Numeric Data Only. Consists of numerals 0 through 9.

(S)N = Numeric Data Variation. May contain ‘Numeric Data Only’ or may consist of

one or more spaces followed by numerals 0 through 9. Must consist of at least one

right justified numeral. This variation of numeric class may be used for amounts,

rates, and counts (where specified).

AN = Alphanumeric Data. Consists of characters A through Z (uppercase ONLY),

numerals 0 through 9, and space.

D = Known Date. Consists of numerals 0 through 9 (format MMDDYY).

X = Special Data. Consists of characters A through Z (uppercase ONLY), numerals 0

through 9, space, and any other character found on a standard keyboard. The

following characters are accepted:

! @ # $ % ^ & * ( ) - _ = + [ { ] } \ | ; : ‘ “ , < . > / ? ` ~

Generally, the numeric data class is reserved for a data element used as an integer.

It may also include a data element used as a sequencer (e.g., a line number).

Generally, any identifier or code is classed as alphanumeric. Note that this would

include an identifier or code that may be required to be reported as all numerals.

Position: Indicates the beginning and ending position, respectively, of the reported data element

within the 80-character record.



Designation:

Indicates the reporting requirement as follows: M = Mandatory. A value conforming to the listed class is required in all filing

scenarios.

C = Conditional. A value conforming to the listed class may or may not be required

for a particular filing scenario. The usage notes will describe the specific cases in

which the data element is required or not allowed to be reported.

O = Optional. A value conforming to the listed class will be conditionally accepted if

provided. An optional data element may be subject to validation, however.

Description:

Defines the data element and provides a further description of how it is to be reported. May

include a list of acceptable values, an exception or further specification of the data class,

and/or various rules regarding format, justification, and truncation.

Note: Points to a further discussion regarding the reporting of the particular data element.

Additional Record Key Layout 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 lower-case letters, CBP cannot guarantee the consistency

of processing results for data transmitted in lower case.

All data elements are in fixed-length format. If all positions are not filled, the formatting rules are:

Code Description A Left justify and Space fill.

AN Left justify and Space fill.

N Right justify and zero-fill.

X Left justify and Space fill.

Note: Unless otherwise specified, if there is no data to insert in a field, Space fill.



Input Record Usage Map for “A” Add and “R” Replace Actions

The following tables illustrate how the automated interface expects repeating groups to be

structured within an input message.

Record

ID

Name

Req.

Des.

Max

Use

Loop

Repeat

Notes

Block Control Grouping M 1 1

Transaction Control Headers (A,B) M 1

SE Header Grouping M 999

SE10 SE Header M 1 2

SE11 SE Additional Header O 1

SE13 Contact /Correction / Cancellation information M 1 2

Bill of Lading Grouping C 999

SE15 Bill of Lading information M 3

Conveyance Grouping C 99

SE16 Conveyance information M 1

Equipment Grouping O 99

SE17 Equipment information M 1

SE20 Reference information C 99

Header Level Entity Grouping C 8

SE30 Entity Name and Type M 1

SE35 Entity Street Address C 3

SE36 Entity City and Country C 1

SE Line Grouping C 999

SE40 Line Item M 1

SE41 FTZ Status & Unit Quantity Information C 1

Line Level Entity Grouping C 7

SE50 Entity Name and Type M 1

SE55 Entity Street Address C 3

SE56 Entity City and Country C 1

Harmonized Tariff Schedule Grouping M 8

SE60 Harmonized Tariff Schedule M 1

SE61 FTZ Privileged Foreign Status Add’l Detail C 1

PGA Grouping C 999

OI M 1

PG01 M 1 …

PG35 C 1

Transaction Control Trailers (Y,Z) M 1 1

Designation: M = Reporting Mandatory; C = Reporting Conditional; O = Reporting Optional



Note 1

Transaction Control Headers and Trailers must conform to the requirements set out in the ACE

CATAIR ABI Batch & Block Control Chapter.

Note 2

Both the SE10 and SE13 records are required for the submission of a Replace action “R” at all

times.

Prior to any bill match on the transaction, and if there is no pending review by CBP, the filer should

expect the Replace action to be automatically approved by the CBP system.

Under any of the following conditions, the filer should expect that the submission of the action

code “R” to replace the cargo release transaction will automatically result in a Correction Request

which must be manually adjudicated by an authorized CBP user:

The transaction is pending a review by CBP, such as Document Requested and Intensive statuses.

The shipment has arrived but the cargo release transaction has not been released.

Once the shipment has arrived and the cargo release transaction has been released, no additional

EDI changes by the trade will be accepted using the “R” Replace action. The “U” Update can still

be used to correct bill of lading and manifest data for up to 15 calendar days after cargo release.



“D” Action to Cancel a Cargo Release Transaction

Record

ID

Name

Req.

Des.

Max

Use

Loop

Repeat

Notes

Block Control Grouping M 1 1

Transaction Control Headers (A,B) M 1


SE10 SE Header M 1 2

SE13 Contact / Correction / Cancellation M 1 2

SE20 Reference information C 99



Note 1


CATAIR ABI Batch & Block Control Chapter

Note 2

Both the SE10 and SE13 records are required for the submission of a cancellation action “D” at

all times.

Previous draft versions of this ACE Cargo Release (SE) Implementation

Guide provided that only the SE10 record needed to be transmitted to

request the cancellation of a Cargo Release transaction if the request

was made prior to a bill match of any listed bills of lading on the

transaction.

The SE13 record is now required for the submission of a cancellation

action “D”.

Prior to any bill match on the transaction, and if there is no pending review by CBP, the filer

should expect the cancellation action to be automatically approved by the CBP system.

Under any of the following conditions, the filer should expect that the submission of the action

code “D” to cancel the cargo release transaction will automatically result in a Cancellation

Request which must be manually adjudicated by an authorized CBP user:

The transaction is pending a review by CBP, such as Document Requested and Intensive statuses.

There has been a bill match for at least one bill of lading listed on the cargo release transaction.

The cargo release transaction has been released.



“U” Action to Update Bill of Lading & Manifest information on a Cargo

Release transaction

The “U” Update can still be used to correct bill of lading and manifest data for up to 15 calendar

days after cargo release.

Please note: The Port of Entry should NOT be updated using the Update action.

Record

ID

Name

Req.

Des.

Max

Use

Loop

Repeat

Notes

Block Control Grouping M 1 1 Transaction Control Headers (A,B) M 1


SE10 SE Header M 1 2 SE11 SE Additional Header O 1 3 SE13 Contact / Correction / Cancellation information M 1

Bill of Lading Grouping C 999

SE15 Bill of Lading information M 3 Conveyance Grouping C 99

SE16 Conveyance information M 1 Equipment Grouping O 99

SE17 Equipment information M 1



Note 1


CATAIR ABI Batch & Block Control Chapter

Note 2

Updating the value reported for Planned Port of Entry is not allowed when submitting an ACE

Cargo Release (SE) with action code “U” (Update)

Note 3

The Location of Goods may be updated via the Update action.

Note 4

Both the SE10 and SE13 records are required for the submission of a cancellation action “D” at

all times.



Output Record Usage Map

The following tables illustrate how the automated interface will structure repeating groups within

an output response message.

Record

ID Name

Req.

Des.

Max

Use

Loop

Repeat

Notes

Block Control Grouping M 1

Transaction Control Headers (A,B) M


SE Header Error Grouping M 1 SE10 SE Header M 1 SE90 Error Record C 9 SE11 SE Additional Header M 1 SE90 Error Record C 9

Contact / Correction / Cancellation Error Grouping

C

99

SE13 Contact / Correction / Cancellation M 1 SE90 Error Record C 9

Bill of Lading Grouping C 999 Bill of Lading Error Grouping C 3

SE15 Bill of Lading information

Error Record

M

C

1

9

SE90

Conveyance Grouping C 99 Conveyance Error Grouping C 1 SE16 Conveyance information M 1

SE90 Error Record C 9

Equipment Grouping C 99 Equipment Error Grouping C 1

SE17 Equipment information M 1 SE90 Error Record C 9

Reference Error Grouping C 99 SE20 Reference information M 1

SE90 Error Record C 9 Header Level Entity Grouping C 8 Entity Name and Type Error Grouping C 1 SE30 Entity Name and Type M 1 SE90 Error Record C 9

Entity Street Address Error Grouping C 3 SE35 Entity Street Address M 1



SE90 Error Record C 9 Entity City and Country Error Grouping C 1

SE36 Entity City and Country M 1 SE90 Error Record C 9

Simplified Entry Line Grouping C 999 Line Item Grouping C 1

SE40 Line Number M 1 SE90 Error Record C 9 SE41 FTZ Status & Unit Quantity Information C 1 SE90 Error Record C 9

Line Level Entity Grouping C 99 Entity Name and Type Error Grouping C 1 SE50 Entity Name and Type M 1 SE90 Error Record C 9

Entity Street Address Error Grouping C 3 SE55 Entity Street Address M 1 SE90 Error Record C 9

Entity City and Country Error Grouping C 1 SE56 Entity City and Country

Error Record

M

C

1

9

SE90 Harmonized Tariff Schedule Grouping C 8 Harmonized Tariff Schedule Error Grouping C 1

SE60 Harmonized Tariff Schedule M 1 SE61 FTZ Privileged Foreign Status Add’l Detail C 1 SE90 Error Record C 9

PGA Grouping C 999 OI M 1

PG01 M 1 …

PG35 C 1 SE90 Transaction Disposition Record M 1

Transaction Control Trailers (Y,Z) M 1




Unified Entry/ISF Filing

An ISF-10 Importer Security Filing (ISF) can be included with an Entry submission by inserting

the appropriate SF records immediately following the last Entry data record; i.e. the last SE60

record or the last Participating Government Agency (PG) record that is associated with the last

SE60 record.

Importer Security Filing ISF-10 reporting information:

1. Manufacturer Name and Address 2. Seller Name and Address 3. Buyer Name and Address 4. Ship To Name and Address 5. Scheduled Container Stuffing Location 6. Consolidator Name and Address 7. Importer of Record* 8. Consignee Number

The following are required ISF data elements but are not reported in the SF10 to SF36 records

because they will be extracted from the required Entry data for all entry types.

9. Country of Origin 10. Harmonized Tariff Schedule

In a Unified Entry/ISF filing, the Importer of Record for entry purposes (reported in the SE10

Record) and the ISF Importer (reported in the SF10 Record) must be the same entity, with the

same Importer of Record Number.

*As part of the Unified Entry/ISF transaction processing, the CBP system will create an SF30

record with the business entity type IM (Importer of Record). The data for this record will be

derived from the ISF Importer listed in the SF10 record.

The Consignee Number must be reported using an identifier in an Importer of Record number

format.

To delete a previously accepted Importer Security Filing, only the SF10 record is required

containing the ISF transaction number previously provided in the SN output transaction. The

Mandatory/Conditional status indicated for all other records applies to “Add” or “Replace” actions

only.

Response to an Importer Security Filing included with Entry data will be issued separately from

the Entry Response. The output application for the ISF-10 filing is SN.



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 lower-case letters, CBP cannot guarantee the consistency

of processing results for data transmitted in lower case.

Data Elements

The data element descriptors are defined as:

Code Description

A The data element is alphabetic only.

AN The data element is alphanumeric only.

C The data element is special characters.

N The 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:

Code Description

A Left justify and Space fill. AN

Left justify and Space fill. C

Left justify and Space fill. N

Right justify and zero-fill. X

Left justify and Space fill.

Note: Unless otherwise specified, if there is no data to insert in a field, Space fill.



Importer Security Filing (SF) Input Record Usage Map

The following SF input records must be included within the B-Y block Control Records.

They are to be included following the last input record of the ACE Cargo Release (SE) (i.e. the

last SE60 record or the last Participating Government Agency (PG) record that is associated with

the last SE60 record).

Record

ID

Description

Req.

Des.

Max

Use

Loop

Repeat

ISF Header Grouping M 1 SF10 Provides ISF header information M 1


SF20 Provides reference data C 999

SF25 Provides container information O 999

Entity Grouping M 999 SF30 Identifies the type of commercial entity whose

identity is being reported M 1

SF31 Provides a secondary name for the commercial

entity reported in the associated SF30 record. O 1

SF35 Provides the street number, street name and

optional addressing information of the suite/floor

number and building name

C 3

SF36 Provides geographical data pertaining to the city,

state/province, postal and country C 1



Record Identifier SE10 (Input)

This is a mandatory input record that provides data pertaining to the update action code, entry

filer code, entry number, entry type, importer of record number, mode of transportation, bond

type code, estimated total entry value, planned port of entry, split shipment release code, and port

of unloading.

Record Identifier SE10 (Input) Data Element Length/

Class

Position Status Description Note

Control Identifier 4AN 1-4 M Must always equal SE10 Update Action Code 1A 5 M A code representing the update action. 1

Entry Filer Code 3AN 6-8 M A unique code assigned by CBP to all active

entry document preparers. The Entry Filer

Code occupies the first three positions of an

entry number regardless of where the entry

is filed. This code must be the same as the

Entry Filer Code in the block control header

record (Record Identifier B).

Filler 2X 9-10 M Space fill. Reserved filler for possible future

expansion of Entry Filer Code and/or Entry

Number.

Entry Number 8AN 11-18 M Unique identifying number assigned to the

Entry by the Filer. For additional

information on valid entry number formats,

refer to Appendix E of the ACE CATAIR

Chapters publication.

Filler 1X 19 M Space fill. Entry Type 2AN 20-21 M A code representing the entry type. Valid

entry type codes are listed in Appendix B of

the ACE CATAIR Chapters publication.

2, 9, 10

Importer of Record

Type

3AN 22-24 C The type of number being used to identify

the importer of record.

3, 12

Importer of Record 12X 25-36 C Identification of the importer of record. 4, 12

Mode of

Transportation

(MOT) Code

2AN 37-38 C A code representing the mode of

transportation. Valid mode of transportation

codes are listed in Appendix B of the ACE

CATAIR Chapters publication.

5, 11

Bond Type Code 1N 39 M A code representing the bond type. 6

Estimated Entry

Value

10N 40-49 M The total entered value of the entry in whole

US dollars. 13




Class


Planned Port of

Entry

5AN 50-54 C Planned / scheduled port of entry in

Schedule D code.

**See Note 7 for explanation regarding

input for this data element.**

Updating the value reported for Planned

Port of Entry is not allowed when submitting

an SE with action code “U” (Update)

Planned Port of Entry is required for entries

with Non-AMs bills

7

Split Shipment

Release Code

1AN 55 O A code representing an option for releasing

split shipments.

8

Port of Unlading 5AN 56-60 C Planned / scheduled port of unlading in

Schedule D code.

Port of Unlading is required for Mail (MOT

50), Passenger Hand Carried (MOT 60), and

Fixed Transport Installation (MOT 70)

Filler 20X 61-80 M Space fill.

Note 1

Valid Update Action Codes are:

Code Description

A Add

D Cancel R Replace

U Update

Both the SE10 and SE13 records are required for the submission of a cancellation action “D”

and replacement action “R” at all times.



If the update action code is D, and a bill match has occurred, the transaction is processed as a

Cancellation Request that requires approval by CBP. For a Cancellation Request, the SE10 and

SE13 records are mandatory, and the SE20 record is conditional. After a Cancellation Request

has been accepted by CBP, the entry remains on file with a status of Cancelled. The entry number

associated with the Cancelled entry cannot be reused.

A submission with an update action of R will not be accepted if the bill of lading has arrived and

the entry has been issued a release.

If the update action code is U, the only records that can be reported are SE10, SE11, SE15, SE16,

SE17, and SE20. The U update action code is used to replace the Bill of Lading information and

to report specific transportation information.

Note 2

Only the below Entry Type codes are valid for use at this time:

Code Description

1 Consumption – Free and Dutiable 2 Consumption - Quota/Visa 3 Consumption - Antidumping/ Countervailing Duty

6 Consumption - Foreign Trade Zone (FTZ) 7 Consumption - Antidumping/ Countervailing Duty & Quota/Visa Combination 11 Informal – Free and Dutiable 12 Informal - Quota/Visa (other than textiles) 21 Warehouse 22 Re-Warehouse 23 Temporary Importation Bond (TIB) 52 Government Dutiable

86 Section 321

Note 3

The qualifiers for Importer of Record Type (left justified) are:

Code Description

EI Employer Identification Number (IRS #) ANI CBP-assigned Number

34 Social Security Number



Note 4

Valid formats for the Importer of Record Number are:

NN-NNNNNNNXX Internal Revenue Service (IRS) Number

YYDDPP-NNNNN CBP Assigned Number

NNN-NN-NNNN Social 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.

Note 5

Valid Mode of Transportation Codes are:

Code Description

10 Vessel, Non-container 11 Vessel, Container 12 Border Water-borne (only Mexico and Canada) 20 Rail, Non-container 21 Rail, Container 30 Truck, Non-container 31 Truck, Container 32 Auto 33 Pedestrian 34 Road, other. Includes foot and animal-borne. 40 Air, Non-container 41 Air, Container 50 Mail

60 Passenger, Hand Carried

70 Fixed Transport Installations. Includes pipeline and powerhouse.

Note 6

Valid Bond Type Codes are:

Code Description

0 No bond required 8 Continuous bond 9 Single transaction bond

If bond type is 9, it is mandatory to report the following Reference Identifier Codes in SE20

records:

V1 Surety Code

AMT Bond amount



Note 7

If the Planned Port of Entry is left blank (i.e. Space Filled), then the filer is making an affirmative

election to have the Planned Port of Entry derived from the U.S. Port of Unlading of the Bill of

Lading listed in the SE15 record.

In the case where the Planned Port of Entry is left blank (i.e. Space Filled) and an In-Bond is posted

against the Bill of Lading, the Planned Port of Entry will be derived from the Port of In-Bond

Destination of the involved In-Bond.

If the associated In-Bond has been reported as Arrived in a Port (aka Port C) other than the Port

of In-Bond Destination listed with the creation of the In-Bond, the CBP system recognizes ‘Port

C’ as the current location of the cargo. In the scenario where the Planned Port of Entry is left blank

(i.e. Space Filled), the Planned Port of Entry will be derived from ‘Port C’. If a Planned Port of

Entry is declared on the Cargo Release submission then the declared Planned Port of Entry will be

compared to ‘Port C’ for purposes of authorizing CBP release of the transaction.

The Planned Port of Entry must be provided if any of the following conditions apply:

An In-Bond number is reported in the entry filing

PGA data is included in the entry filing

Entry types 02, 06, 07, 12, 21, 22, 23, 86

Cancel Transactions

Non-AMS bills

Updating the value reported for Planned Port of Entry is not allowed when submitting an ACE

Cargo Release (SE) with action code “U” (Update)

Note 8

Valid Split Shipment Release Codes are:

Code Description

1 Hold All - Release Entry when all cargo qualifies for release.

2 Request Special Permit to release cargo incrementally under Immediate Delivery procedures. Entry date will be set to when the first portion of the split shipment is

released.

Note 9

When the Entry type is 21 or 22, the FIRMS Code of the CBP Bonded Warehouse that the Importer

is applying to enter the cargo into must be reported in the SE11 Record, Position 65-68. The

FIRMS Code must be a facility type 04 (Bonded Warehouse), be located in the Port of Entry (or

in the recognized local port cluster for cross-port processing) of the Cargo Release transaction, and

must be in an Active status in the CBP system.



Note 10

When the Entry type is 22, the originating warehouse entry number that the merchandise is coming

from must be reported in the SE11 Record, Position 69-79.

Note 11

MOT is required on all Entry Types except for type 06. MOT is required on Entry Type 06 if Bill of

Lading is provided.

Note 12

Notes 3 and 4 do not apply for type 86 unless PGA data is included in the entry filing or otherwise

required by a PGA.

Note 13

Entry value cannot exceed $800 for type 86 entries or $2500 for type 11 entries.

Record Identifier SE11 (Input) This is a conditional input record that provides additional data according to the specific entry

needs.


Class


Control Identifier 4AN 1-4 M Must always equal SE11. Entry Date Election

Code

1X 5 C A code representing the source of the

Elected Entry Date. Valid codes are:

W = Weekly Entry (Entry type 06, only)

Code “W” is only reported on an entry

type 06 when the transaction is being used

to submit a Weekly Entry.



Elected Entry Date 6N 6-11 C Enter a numeric date in MMDDYY

(month, day, year) format.

The date submitted in this field will be

used as the Date of Entry for Entry

Summary and duty calculation

purposes.

For entry type 06, and an Entry Date

Election Code = “W” (Weekly Entry),

this represents the date of the first day of

the Zone Week.

1

Location of Goods

(FIRMS)

4AN 12-15 C FIRMS code of the location where the

cargo is currently stored.

4



Record Identifier SE11 (Inpu t) Data Element Length/

Class


Elected Exam Site

(FIRMS)

4AN 16-19 O Filer’s preferred Centralized

Examination Station (CES)

location.

For use when CBP determines that a

required Intensive Examination is to

be conducted at a Centralized

Examination Station (CES).

As per CD 3550-29, if there is more

than one CES in the port of entry, the

broker/filer specifies which CES

location they wish used for the

examination.

If there is only one CES in the port of

entry, no FIRMS Code needs to be

submitted for this data element.

This data element should be Space

Filled if no FIRMS Code is being

submitted.

Conveyance Name

or FTZ ID*

[Note: This is not

the same format that

is used on the e214

FTZ Admission.]

20X 20-39 C Name of the Conveyance.

For entry type 06, list the Foreign Trade

ZoneID. The data must be submitted in

the format specified in Note 6*.

*NOTE: Please refer to Note 6 below

for proper format of the FTZ ID.

6

Voyage/Flight/Trip

Manifest Number

5X 40-44 C The voyage/flight/trip number of the

importing carrier.

7

General Order

(G.O.) Number

20AN 45-64 O The G.O. Number if the cargo has been

placed in General Order.

CBP Bonded

Warehouse

(FIRMS)

4AN 65-68 C FIRMS code of the CBP Bonded

Warehouse where cargo is to be entered.

(Entry Types 21 and 22 only)

2

Originating

Warehouse Entry

Filer Code

3AN 69-71 C Filer Code of the originating warehouse

entry that the merchandise is coming

from. The Originating entry listed must

be entry type 21 or 22 only.

The Entry Filer Code occupies the first

three positions of an entry number.

3




Class


Originating

Warehouse Entry

Number

8AN 72-79 C Originating warehouse entry number that

the merchandise is coming from. The

Originating entry listed must be entry

type 21 or 22 only.

Unique identifying number assigned to

the Entry by the Filer. For additional

information on valid entry number

formats, refer to Appendix B of the ACE

CATAIR Chapters publication.

3

Immediate

Delivery Indicator

1X 80 C Space fill. Not currently in use.

Note 1

An entry date must be provided if ‘W’ is selected for Entry Date Election Code. The date submitted

in this field will be used as the Date of Entry for Entry Summary and duty calculation purposes.

The elected entry date may be the current date or a future date. If a future date is used, the date

must be within 7 calendar days of the transaction filing date. Note: The zone week is a Zone

Operator selected 7 calendar day period.

Note 2

Mandatory when the Entry type is 21 or 22. This identifies the FIRMS Code of the CBP Bonded

Warehouse that the Importer is applying to enter the cargo into. The FIRMS Code must be a

facility type 04 (Bonded Warehouse), be located in the Port of Entry (or in the recognized local

port cluster for cross-port processing) of the Cargo Release transaction, and must be in an Active

status in the CBP system.



Note 3

Mandatory when the Entry type is 22. This identifies the originating warehouse entry number that the

merchandise is coming from. The Import Date on the original warehouse entry (type 21) [which

introduced the merchandise into a customs bonded warehouse] cannot be greater than 5 years ago.

Note 4

When the Entry type is 06, the FIRMS code of the FTZ site must be entered. If the local Port

Director, or his designee, has approved the use of a single FIRMS code for filing electronic FTZ

Admissions (aka e214) for a subzone with multiple authorized sites (each with a unique assigned

FIRMS code) which are all covered under a single activity type FTZ bond and under a single

inventory control and record keeping system, this single FIRMS code may also be declared as the

Locations of Goods in the SE11 record.

If the SE11 Record is included in the submission of an ACE Cargo Release (SE) with Action Code “U”

(Update), the Location of Goods data element can be updated as well.

Note 5 (TBD)

Note 6

When the Entry type is 06, enter the characters “FTZ” followed by the FTZ project number [3

digits]; Subzone number or General Purpose Zone Acreage Site number) [2 characters]; Subzone Site

number [2 digits] (as applicable), in one of the following format(s), including any needed leading

zeros:

FTZ0260A01 FTZ 26, Subzone A, Subzone Site 01 FTZ02610

FTZ 26, General Purpose Zone Acreage Site 10

FTZ026T2 FTZ 26, General Purpose Zone Acreage Site T2

Note 7

This element is not used for entry type 06 FTZ.




This is a mandatory input record that provides Filer contact information for the cargo release

transaction submission. When the submission is a cancellation requests, the filer must also

provide a Reason Code


Class


Control Identifier 4AN 1-4 M Must always equal SE13. Contact Name 40AN 5-44 M Contact Name for the entry filing

Contact Phone 15AN 45-59 M Phone Number for the entry filing

Reason Code 2A 60-61 C Reason code for Cancellation request.

Space fill for Correction requests.

1

Multiple Cargo

Dispositions

Indicator

1N 62 O Use 1 to indicate that multiple cargo

dispositions exist in addition to the reason

code provided for the entry in the

cancellation request.

Space fill for Correction requests.

DIS indicator 1N 63 O Use 1 to indicate a Document Image

System (DIS) submission has been made

in support of the correction or

cancellation request

2

Split Shipment

indicator

1N 64 O Use 1 to indicate that the SE is associated

with a split shipment

3


Note 1

Valid Cancellation request reason codes are:

Code Description

1 Clerical error 2 Entry replaced by CBPF 7512 (replacement in-bond number required) 3 Merchandise cleared under another entry (replacement entry number required) 4 Entry replaced by FTZ Admission (replacement FTZ Admission Number

required)

5 Merchandise cleared under informal entry 6 Merchandise seized 7 Merchandise destroyed 8 Non-arrival 9 Shipment refused by importer 10 Shipment not authorized for import 11 System error 12 No Foreign status goods removed from FTZ [Used only for Entry Type 06]



For Reason Code 02, an In-bond Number that is on file with CBP must be provided in the SE20

record; for reason code 03, the replacement Entry Number that is on file with CBP must be

provided in the SE20 record; for reason code 04, the replacement FTZ Admission Number that is

on file with CBP must be provided in the SE20 record.

Reason Code 12, is to be submitted only for Entry Type 06 FTZ. This code may also be submitted

when the Entry Type 06 Cargo Release transaction is used as a Weekly Entry. The submission of

this reason code indicates that no Foreign [zone] status merchandise has been, or will be, entered

into the U.S. Commerce using the Cargo Release transaction which the filer is requesting be

cancelled.

Note 2

The use of the DIS indicator denotes to CBP that the filer has submitted an electronic file or files

in support of the correction or cancellation request. When the DIS indicator is reported in the

SE13 record, the SE20 record is required with the Reference Identifier Qualifier code “DIS” (Filer-

Defined DIS Reference Number). This is a filer-assigned reference number to identify the DIS

submission. This reference number should be unique for the associated entry number and should

not be repeated for other DIS submissions for the same entry number, including for the entry

summary and other post summary submissions. .

The DIS submission related to the correction / cancellation request:

should be transmitted in advance of the submission of the correction / cancellation request

should include the Filer-assigned [DIS] Reference number which links it to the specific correction / cancellation request.

For instructions on submitting electronic files to CBP via DIS, see the DIS Implementation

Guide of the ACE ABI CATAIR link in Appendix A.

Note 3

Use 1 to indicate that the ACE Cargo Release (SE) is associated with a split shipment, which is a

factor in adjudicating the Cancellation Request.




This is a conditional input record that provides data pertaining to the issuer of a bill of lading

number and bill of lading quantity to be entered. Additional SE15 Records are used to report

multiple bill of lading/air waybill data.


Class


Control Identifier 4AN 1-4 M Must always equal SE15. Bill Type Indicator 1A 5 M Code identifying the type of Bill of

Lading Number. Valid codes are:

R = Regular / Simple Bill of Lading;

▪ Use ‘R’ for Mode Rail (MOT 20, 21)

▪ Use ‘R’ for Mode Truck(MOT 30, 31) [aka Shipment Control Number]

▪ Use ‘R’ for Mode Pipeline (MOT 70)

▪ Use ‘R’ for Mode Passenger, Hand Carried (MOT 60)

▪ Use ‘R’ for Mode Mail, (MOT 50)

▪ Use ‘R’ for Modes 32, 33, 34

Automobile (MOT 32)

Pedestrian (MOT 33)

Road, other. Includes Foot and Animal Borne (MOT 34)

M = Master Bill of Lading; (Not currently valid for all modes)

H = House Bill of Lading; (Not currently valid for all modes)

T = Express Carrier Tracking Number

(air only) I = In-bond number

See Note 3 regarding entry type 22.

See Note 9 regarding MOT 60.



3,7,8, 9, 10,

11




Class


Issuer Code of Bill

of Lading Number

4AN 6-9 C A code representing the issuer of the bill

of lading.

Space fill for:

In-Bond

Air Shipments (MOT 40, 41)

Auto (MOT 32), Pedestrian (MOT 33), Road/Other (MOT

34), Passenger, Mail (MOT 50),

Hand Carried (MOT 60)

Use of “UNKN” as a carrier code is not

permitted.

10

Bill of Lading

Number

50X 10-59 M The bill of lading number as listed on the

manifest; or, In-Bond number. If the

number is less than 50 positions, it is left

justified. Do not include spaces, hyphens,

slashes or other special characters.

Include the AWB prefix for Air

shipments for Master / Simple Bill of

Lading and Tracking Numbers.





1,3,4, 9,10,

12

Quantity 8N 60-67 C Enter the quantity associated with the bill

of lading number being reported. It is the

smallest exterior packaging unit.





2,3,9, 10, 11

Filler 5X 68-72 M Space fill. Non-AMS indicator 1X 73 M Default value is ‘N’.

Enter ‘Y’ to represent that the bill of

lading will not be manifested via EDI

with a CBP automated manifest system.

See Note 5 below for specific instances

when a ‘Y’ must be declared.

When ‘Y’ is declared in this field, use of

the SE16 record is mandatory.

5, 6




Note 1

To report Bill of Lading Numbers for Air shipments:

Master Bill of Lading / House Bill of Lading – Use an SE15 record with Bill Type Indicator ‘M’ to report the Master Bill of lading Number (including the AWB prefix) followed by

another SE15 with Bill Type Indicator ‘H’ and the House Bill of Lading Number.

Simple Bill of Lading – Use a single SE15 record with Bill Type Indicator ‘R’ to report

the Simple Bill of Lading Number (including the AWB prefix).

Express Carrier Tracking Number – Use a single SE15 record with Bill Type Indicator ‘T’ to report the Tracking Number (including the AWB prefix).

In-bond Number – Use an SE15 record with Bill Type Indicator ‘I’ to report the In-bond

Number. This record should:

o not contain a Quantity, as it is only reported at the Bill Level; and, o be followed by another SE15 with Simple Bill of Lading; or, o be followed by pair of SE15 records: the first SE15 record with Bill Type Indicator

‘M’ and the Master Bill of Lading Number (including the AWB prefix), and second SE15 record with Bill Type Indicator ‘H’ and the House Bill of Lading Number.

Reminder: Bill quantity is entered at the most detailed (i.e. lowest) level of the bill.

To report Bill of Lading Numbers for Ocean shipments:

Master Bill of Lading / House Bill of Lading – Use an SE15 record with Bill Type Indicator ‘M’ to report the Master Bill of lading Number followed by another SE15 with Bill Type

Indicator ‘H’ and the House Bill of Lading Number.

Simple Bill of Lading – Use a single SE15 record with Bill Type Indicator ‘R’ to report

the Simple Bill of Lading Number.



o not contain a Quantity, as it is only reported at the Bill Level; and, o be followed by another SE15 with Simple Bill of Lading; or, o be followed by pair of SE15 records: the first SE15 record with Bill Type Indicator

‘M’ and the Master Bill of Lading Number, and second SE15 record with Bill Type Indicator ‘H’ and the House Bill of Lading Number.

Reminder: Bill quantity is entered at the most detailed level of the bill.



To report Bill of Lading Numbers for Rail shipments:

Simple Bill of Lading – Use a single SE15 record with Bill Type Indicator ‘R’ and the

Simple Bill of Lading Number.

In-bond Number – Use an SE15 record with Bill Type Indicator ‘I’ to report the In-bond Number. This record should:

o not contain a Quantity, as it is only reported at the Bill Level; and,

o be followed by another SE15 with Simple Bill of Lading.

To report Bill of Lading Numbers for Truck shipments:

Simple Bill of Lading (aka Shipment Control Number) – Use a single SE15 record with

Bill Type Indicator ‘R’ and the Simple Bill of Lading Number.



o not contain a Quantity, as it is only reported at the Bill Level; and,

o be followed by another SE15 with Simple Bill of Lading.

Valid formats for In-bond Number are:

NNNNNNNNN CBP assigned IT number

NNNNNNNNNNN Air Waybill number *(leading NNN = airline prefix code)

XXXNNNNNNNN “Paperless” Master In-Bond format

Note 2

If a data value is reported for Quantity (Pos 60-67) in the ACE Cargo Release (SE), that value will

be used as the entered and released quantity for the bill. If a data value for Quantity is not reported

in the ACE Cargo Release (SE), the full manifested bill quantity will be used as the entered and

released quantity. In the case of a split shipment, release will be issued to the carrier under either

the Hold All or Incremental Release under Immediate Delivery procedures.

In the case where the Cargo Release is being filed for a quantity which is less than the full

manifested bill of lading quantity, the data element Quantity must be submitted and the value

reported must be greater than zero.

Do not provide quantity on SE15 record if SE16 record is present, except as specified in Note 3

and Note 9.

Note 3

Bill of Lading is not required for entry type 22, Re-Warehouse.

If the originating Warehouse entry (type 21) or Re-Warehouse entry is in another port of entry so that

the merchandise is transported under an In-Bond, then both In-Bond Number and Bill Number

should be reported.



Note 4

If the mode of transportation code in the SE10 record is Pipeline (70), the pipeline carrier’s

SCAC code should be entered here.

If the mode of transportation code in the SE10 record is Pipeline (70), there must be a bill of

lading reported, and that bill of lading must have a prefix consisting of the carrier’s prefix.

If this is an In-Bond movement originating from one of the following, the originating bonded

facility’s FIRMS Code may have been set up as a Carrier Code in the CBP system and may have

been used on the In-Bond as the SCAC of the ‘non-import-manifest’ bill of lading. This is

acceptable:

Note 5

General Order Warehouse

Customs Bonded Warehouse

Foreign Trade Zone

Seizure

Non-AMS Indicator – This is a mandatory field. The default value is ‘N’, meaning the bill of

lading in the SE15 record is, yes, expected to be manifested electronically with CBP and the bill

is expected to be matched to the tables in CBP’s automated manifest systems.

Enter ‘Y’ to represent that the bill of lading will not be manifested electronically with CBP.

In all instances, if the Bill Type Indicator in the SE15 is “I”, set this field to ’N’.

If the Entry Type Code in the SE10 record is 22 Re-Warehouse, and the Bill Type Indicator in the

SE15 is “I”, set this field to ’N’.

If the Entry Type Code in the SE10 record is 06 FTZ, and the Bill Type Indicator in the SE15 is

“I”, set this field to ’N’.

If the Mode of Transportation Code in the SE10 record is any of those listed below, this field

must be set to ‘Y’:

32 Auto 33 Pedestrian 34 Road, other. Includes foot and animal-borne. 50 Mail

60 Passenger, Hand Carried

70 Fixed Transport Installations. Includes pipeline and powerhouse.

If the General Order Number field in the SE11 record is not {null} this field must be set to ‘Y’.

If this is a shipment originating from Seizure (CBP custody), this field must be set to ‘Y’.



Port of Entry is required when the non-AMS indicator is set to ‘Y’.



Note 6

When ‘Y’ is declared in this field, use of the SE16 record is mandatory.

Note 7

Bill type =’T’ cannot be Non-AMS bill type and not allowed for type 86 entries.

Note 8

Bill Type Indicator values ‘M’ and ’H’ are not valid for Rail mode of transportation (MOT 20,

21). Rail bills of lading are to be reported as ‘R’ (Regular/Simple).

Bill Type Indicator values ‘M’ and ’H’ are not currently valid for Truck mode of transportation

(MOT 30, 31). Truck bills of lading are to be reported as ‘R’ (Regular/Simple).

Bill Type Indicator values ‘M’ and ’H’ are not currently valid for

Pipeline (MOT 70)

Passenger, Hand Carried (MOT 60)

Mail, (MOT 50)

Automobile (MOT 32)

Pedestrian (MOT 33)

Road, other. Includes Foot and Animal-Borne (MOT 34)



Note 9

For Passenger, Hand Carried (MOT 60):

Bill Type Indicator is reported as ‘R’ (Regular / Simple Bill of Lading)

Issuer Code of Bill of Lading Number is reported as [Space Filled]

Bill of Lading Number is reported as ‘HANDCARRIED’

Quantity reported must be greater than zero

Non-AMS Indicator should be declared as ‘Y’

For Passenger, Hand Carried (MOT 32):

*Bill of Lading Number is reported as ‘AUTOMOBILE’ or ‘VEHICLE’

For Automobile (MOT 33):

*Bill of Lading Number is reported as ‘PEDESTRIAN’

For Road, other. Includes Foot and Animal-Borne (MOT 34):

*Bill of Lading Number is reported as ‘LIVECATTLE’ or ‘ANIMALBORNE’

[NOTE: These are only suggestions for standardized input. Local CBP may provide specific policy

and guidance as to what should be declared in the Bill of Lading data field for these Modes of

Transportation.]

Note 10

This record is not used for entry type 06 FTZ with one exception: If Privileged or Non- Privileged

zone merchandise was removed from an FTZ in Port A, and has been transported to Port B, the Port

of Entry for the 06, then the SE15 record is used to report the In-Bond Number and Bill.

Note 11

Bill Quantity is mandatory for entry type 86.

Note 12

Only one bill is allowed per entry for entry type 86. A master with one house bill is considered one bill

for entry type 86.




This is a conditional input record that provides data pertaining to the conveyance associated

with the bill of lading number reported in the preceding SE15 record.

The inclusion of this record is mandatory if the bill of lading in the preceding SE15 record is

Non-Automated.

When to use if a Split Shipment is involved:

If the cargo release transaction filing is for the full manifested quantity of the bill of lading, and

the bill is a split shipment, then the SE16 record should not be submitted.

This record is used when filing for cargo release if the bill of lading is a split shipment and the

bill quantity being declared is less than the full manifested quantity for the bill. The SE16 record

will specify the manifest details (e.g. carrier, flight, date, bill qty) and specific bill quantity for

which the cargo release transaction is being filed.

This record may be repeated once for each split part being represented on the cargo release

transaction.

*[Refer to Appendix C to this document for examples of filing for Split Shipments.]

This record is not used for entry type 06 FTZ.


Class


Control Identifier 4AN 1-4 M Must always equal SE16. Carrier Code 4AN 5-8 M A code identifying the carrier. 3

Voyage/Flight/Trip

Manifest Number

5X 9-13 M The voyage/flight/trip number of the

importing carrier.

3

Date of Arrival 6N 14-19 M A numeric date in MMDDYY (month,

day, year) format representing the date of

arrival.

2,3

Quantity 8N 20-27 M The entered quantity associated with the

bill of lading number being reported in

the related SE15 record. It is the smallest

exterior packaging unit.

1,3

Unit of Measure 5X 28-32 O The unit of measure corresponding to the

bill of lading quantity.

Conveyance Name 20X 33-52 C Name of the conveyance. 2


Note 1

This data field is used to indicate the quantity to be entered for each SE16 record (i.e. each ‘split

part’) that is being reported on the cargo release transaction.



Note 2

When the mode of transportation code in the SE10 record is Pipeline (70) enter the name of the

pipeline as the conveyance name.

Date of Arrival must be reported.

Note 3

When the mode of transportation code in the SE10 record is Passenger, Hand Carried (60):

Report the Carrier Code of the carrier which brought the passenger and the merchandise to the 1st Port of U.S. Unlading.

Report the Voyage/Flight/Trip Manifest Number of the conveyance which brought the passenger and the merchandise to the 1st Port of U.S. Unlading.

Report the Date of Arrival of the conveyance which brought the passenger and the merchandise to the 1st Port of U.S. Unlading.

Report Quantity, for example, as ‘00000001’ (padded with leading zeros).




This is an optional input record that provides data pertaining to the container or equipment

associated with the bill of lading number in the immediately preceding SE15 record which holds

the merchandise for which cargo release submission is being made.

This record is not used for entry type 06 FTZ.


Data Element Length/

Class


Control Identifier 4AN 1-4 M Must always equal SE17.

Equipment

Number

20AN 5-24 M Equipment unit's full number

including: the SCAC prefix, the

sequencing or serial part of an

equipment unit's identifying number,

and the check digit





This is a conditional input record that provides reference data.


Class


Control Identifier 4AN 1-4 M Must always equal SE20. Reference Identifier

Qualifier

3AN 5-7 M Code that defines the Reference Identifier. 1, 2

Reference Identifier 50X 8-57 M Reference da

cbp and trade automated interface requirements...record identifier se61 (input) ..... 67 record...

Documents