U.S. Customs and Border Protection (CBP)
/
U.S. Customs Manifest (Receipt of Booking)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from U.S. Customs and Border Protection (CBP). Contact U.S. Customs and Border Protection (CBP) for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
U.S. Customs and Border Protection (CBP) logo

X12 309 U.S. Customs Manifest (Receipt of Booking)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the U.S. Customs Manifest Transaction Set (309) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by carriers, terminal operators, port authorities, or service centers to provide U.S. Customs with manifest data on cargo arriving in or departing from the U.S. on oceangoing vessels, railroad trains, or other types of conveyances. The transaction set can be also used by carriers to provide terminal operators, port authorities, or service centers with manifest data on cargo arriving at their facilities via the conveyances mentioned above.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/cbp/us-customs-manifest-receipt-of-booking/01HNGK0FB12RR02HNTRAB7EBTF
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
M10
020
Manifest Identifying Information
Max use 1
Required
P4 Loop
SE
200
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

SO
Ocean Shipment Information (304, 306, 309, 311, 317, 319, 321, 322, 323, 324, 325, 350, 352, 353, 354, 355, 356, 357, 358, 361)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
309
U.S. Customs Manifest
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

M10
020
Heading > M10

Manifest Identifying Information

RequiredMax use 1

To transmit manifest identifying information

Example
At least one of Vessel Code (M10-04) or Vessel Name (M10-05) is required
M10-01
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

Usage notes

CARRIER CODE
A code representing the importing/exporting carrier. This is the Standard
Carrier Alpha Code (SCAC) issued by the National Motor Freight Traffic
Association Inc., 2200 Mill Road, Alexandria, VA 22310. For water carriers
who own their containers, the SCAC is issued by the Intermodal Transportation
Association, 6410 Kenilworth Ave., Suite 108, Riverdale, MD 20737.
Equivalent AESTIR Proprietary Element: M01 - Carrier Code.

M10-02
91
Transportation Method/Type Code
Required
Identifier (ID)

Code specifying the method or type of transportation for the shipment

Usage notes

MODE OF TRANSPORTATION CODE
A code indicating the type of vessel used to carry the manifested cargo.
Required for input to the Customs and Border Protection (CBP).
VE Vessel, Ocean
Equivalent AESTIR Proprietary Element: M01 - Mode of Transportation Code.

VE
Vessel, Ocean
M10-03
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

  • M1003 is the code identifying the country in which the ship (vessel) is registered.
Usage notes

COUNTRY CODE
An International Standards Organization (ISO) code representing the flag of
the vessel. Required for input to the Customs and Border Protection (CBP).
Equivalent AESTIR Proprietary Element: M01- Vessel Country Code.

M10-04
597
Vessel Code
Optional
Identifier (ID)
Min 1Max 8

Code identifying vessel

  • M1004 is Lloyd's vessel code.
Usage notes

CONVEYANCE CODE
The Lloyds of London registry code representing the exporting conveyance.
This code is Mandatory if Vessel Name is not entered.
Equivalent AESTIR Proprietary Element: M01 - Conveyance Code.

M10-05
182
Vessel Name
Optional
String (AN)
Min 2Max 28

Name of ship as documented in "Lloyd's Register of Ships"

Usage notes

VESSEL NAME
A valid vessel name. Mandatory if missing Vessel Code.
Equivalent AESTIR Proprietary Element: M01 - Vessel Name.

M10-06
55
Flight/Voyage Number
Required
String (AN)
Min 2Max 10

Identifying designator for the particular flight or voyage on which the cargo travels

Usage notes

VOYAGE NUMBER
The voyage number. Required for input to the Customs and Border Protection
(CBP). If not known, send Julian date.
Equivalent AESTIR Proprietary Element: M01 - Voyage Number.

M10-07
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • M1007 is used for the six-digit Numeric Manifest Sequence Number.
Usage notes

SEQUENCE NUMBER
Optional, carrier assigned sequence number. The default is one (1). It may be a
date. Once transmitted, it cannot be changed. All subsequent transmissions for
the manifest must use the original manifest sequence number.
Equivalent AESTIR Proprietary Element: M01 - Manifest Sequence Number.

M10-08
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • M1008 is used for number of bills lading. (Maximum five-digits.)
Usage notes

TOTAL NUMBER OF BOOKINGS/BILLS OF LADING
Provide number of bills of lading/bookings in the manifest.
Equivalent AESTIR Proprietary Element: M01 - Number of Bookings or Bills
of Lading.

M10-09
256
Manifest Type Code
Required
Identifier (ID)

Code identifying the type of manifest transmitted

Usage notes

APPLICATION IDENTIFIER
A code representing the type of application detail data contained within the
block.
D Updation Export Manifest Prior to Vessel Departure from Carrier to CBP.
E Original Export Manifest from Carrier to CBP.
P Preliminary Manifest from Carrier to CBP.
Equivalent AESTIR Proprietary Element: ACR - Application Identifier

D
Updating Export Manifest Prior to Vessel Departure From Carrier to U.S. Customs
E
Original Export Manifest from Carrier to U.S. Customs
P
Preliminary Manifest from Carrier to U.S. Customs
M10-12
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • M1012 is a unique identification number for the manifest assigned by the originator of the manifest with a maximum length of 15.
Usage notes

CARRIER ASSIGNED NUMBER
Optional, carrier assigned number, 1-23 positions. There is no editing on the
format and it is returned as received in the CBP output.
Acceptance/Rejection Transaction Set (355) to the carriers. This is not used in
the Status Information Transaction Set (350) returned from CBP to the carriers.
Equivalent AESTIR Proprietary Element: M01 - Carrier Assigned Number

P4 Loop
RequiredMax >1
P4
040
Heading > P4 Loop > P4

U.S. Port Information

RequiredMax use 1

To transmit identifying information for a U.S. port

Example
P4-01
310
Location Identifier
Required
String (AN)
Min 1Max 30

Code which identifies a specific location

  • P401 is used for customs district and port code (census schedule D).
Usage notes

PORT OF LADING CODE
A code representing the Customs and Border Protection (CBP) District/Port of
Lading. For listing of valid codes, use AESTIR Part III, Appendix D.
Equivalent AESTIR Proprietary Element: P01 - CBP Port of Lading Code.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • P402 is the estimated date of arrival.
Usage notes

ESTIMATED DATE OF DEPARTURE
A date in the YYYYMMDD format representing the scheduled date of
departure from (for exports) or arrival at (for imports) this port.
Equivalent AESTIR Proprietary Element: P01 - Estimated Date of Departure.

P4-03
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • P403 is used for number of bills of lading.
Usage notes

NUMBER OF BOOKINGS/BILLS OF LADING FOR PORT
A value representing the total number of bookings or bills of lading/house bills
transmitted for this Port.
Equivalent AESTIR Proprietary Element: P01 - Number of Bookings or Bills
of Lading for Port.

LX Loop
RequiredMax >1
LX
060
Heading > P4 Loop > LX Loop > LX

Assigned Number

RequiredMax use 1

To reference a line number in a transaction set

Example
LX-01
554
Assigned Number
Required
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set

Usage notes

LOOP CONTROL NUMBER
Provide sender controlled number for the loop.

M11
080
Heading > P4 Loop > LX Loop > M11

Manifest Bill of Lading Details

RequiredMax use 1

To transmit bill of lading detail information for a manifest

Example
M11-12
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • M1112 is the unique bill of lading issuer code.
Usage notes

ISSUER CODE
A SCAC code of the issuer of the bookings.
Equivalent AESTIR Proprietary Element: J01 - Carrier Master Booking/Bill of
Lading Issuer Code.

N9
085
Heading > P4 Loop > LX Loop > N9

Reference Identification

RequiredMax use 999

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

Usage notes

QUALIFIER
Control number qualifier.
BN Booking Number
Equivalent AESTIR Proprietary Element: B02 - Qualifier.

BN
Booking Number
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

CONTROL NUMBER
The number representing the issuer-assigned control number that identifies the
booking or house bill. The control number must be unique by vessel voyage.
Equivalent AESTIR Proprietary Element: B02 - Control Number.

LX Loop end
P4 Loop end
SE
200
Heading > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Heading end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.