**Segment: ISA** Interchange Control Header

**Loop:** \_\_\_\_

**Usage:** Mandatory

**Max Use:** 1

**Max Length:** 106

**Purpose:** To start and identify an interchange of zero or more
functional groups and

> interchange-related control segments.

**Notes: 1 This segment is fixed length, data should be left justified
with trailing**

**Spaces to meet min/man requirements.**

**2 Unless otherwise stated the trade participant in the ACE truck
manifest**

**program will send one single transmission containing one transaction**

**group (GS/GE), containing one transaction set (ST/SE). In the event
the**

**trade participant chooses to batch multiple transmissions in a
single**

**interchange, notice must be provided to CBP ACE support.**

![](media/image1.png){width="5.999305555555556in"
height="2.170138888888889in"}

> **Data Element Summary**

**REF. DES. DATA ELEMENT NAME ATTRIBUTES**

**ISA01 I01 Authorization Information Qualifier M ID 2/2**

> Code identifying the type of information in the Authorization
> Information
>
> **CODE DEFINITION**
>
> **00** No authorization information present

**ISA02 I02 Authorization Information M AN 10/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.
>
> **For truck manifest, there is no authorization information. Map 10
> blank spaces in this element**

**ISA03 103 Security Information Qualifier M ID 2/2**

> Code identifying the type of information in the Security Information

**ISA04 I04 Security Information M AN 10/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)
>
> **In truck manifest this element is not used and must be space
> filled.**

**ISA05 I05 Interchange ID Qualifier M ID 2/2**

> Code indicating the system/method of code structure used to designate
> the
>
> sender or receiver ID element being qualified.
>
> **CODE DEFINITION**

2.  SCAC (Standard Carrier Alpha Code)

> **ZZ** Mutually defined
>
> **In truck, this indicates a sender or receiver ID that is not SCAC**

**ISA06 I06 Interchange Sender ID M AN 15/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 data
>
> Element
>
> **In truck manifest this must reflect a total displacement of 15
> bytes. If the Interchange Sender ID does not fill 15 bytes , The
> remaining amount must be filled with trailing spaces. May also reflect
> the ID of the bonafide certified service provider**

**ISA07 I05 Interchange ID Qualifier M ID 2/2**

> Code indicating the system/method of code structure used to designate
> the
>
> sender or receiver ID element being qualified.
>
> **CODE DEFINITION**
>
> **ZZ** Mutually defined

**ISA08 I07 Interchange Receiver ID M AN 15/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.
>
> **In the truck manifest use 'CBP-ACE-TEST' for test transmissions and
> 'CBP-ACE' for production data transmissions. This field must reflect a
> total displacement of 15 bytes. If the Interchange Receiver ID doesn't
> fill 15 bytes the remaining amount must be filled with trailing
> spaces. This may be the service provider who originally initiated the
> manifest.**

**ISA09 I08 Interchange Date M DT 6/6**

> Date of the interchange

# Date expressed as YYMMDD

**ISA10 I09 Interchange Time M TM 4/4**

> Time of the Interchange

**ISA11 I65 Repetition Separator M 1/1**

> Type is not applicable: The repetition separator is a delimiter and
> not a data element; this field provides the delimiter used to separate
> repeated occurrences of a simple data element or a composite data
> structure; this value must be different than the data element
> separator, component element separator and the segment terminator.
>
> **In truck manifest use '\~'**

**ISA12 I11 Interchange Control Version Number M ID 5/5**

> Code specifying the version number of the interchange control segments
>
> **CODE DEFINITION**
>
> **00406** Standards Approved for Publication by ASC X12
>
> Procedures Revue Board through October 2001

**ISA13 I12 Interchange Control Number M NO 9/9**

> A control number assigned by the interchange sender

**ISA14 I13 Acknowledgment Requested M ID 1/1**

> A code sent by the sender to request an interchange acknowledgment
>
> **CODE DEFINITION**

1.  No acknowledgment requested

2.  Interchange Acknowledgment requested

> **In truck manifest use '0'**

**ISA15 I14 Usage Indicator M ID 1/1**

> Code to indicate whether data enclosed by this interchange envelope is
> test, production, or information
>
> **CODE DEFINITION**
>
> **P** Production Data

**ISA16 I15 Component Element Separator M 1/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 element within a composite data structure;
> this value must be different than the data element separator and the
> segment terminator.
>
> **In truck manifest use: ':'**

**Segment: GS** Functional Group Header

**Loop:** \_\_\_\_

**Usage:** Mandatory

**Max Use:** 1

**Max Length:** 82

**Purpose:** To indicate the beginning of a functional group and to
provide control

> information

**Semantic: 1** GS04 is the group date

**2** GS05 is the group time

> **3** The data interchange control number GS06 in this header must be
> identical
>
> to the same data element in the associated functional group trailer,
> GE02

**Comments:** N/A

![](media/image2.png){width="5.998611111111111in"
height="1.4180555555555556in"}

> **Data Element Summary**

**REF. DES. DATA ELEMENT NAME ATTRIBUTES**

**GS01 479 Functional Identifier Code M ID 2/2**

> Code identifying a group of application related Transaction Sets.

**GS02 142 Application Sender's Code M AN 2/15**

> Code identifying party sending transmission. Codes agreed to by
> trading partners.

# This may be the identification code of the preparer,agent or broker 

> **Preparing the manifest on behalf of the carrier. Truck manifest
> accepts only 4 positions. If a broker is using his 3 character filer
> code as identification code it must be preceded by a '5'.**

**GS03 124 Application Receiver's Code M AN 2/15**

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

## For ACE Truck Manifest use 'CBP-ACE-TEST' for test transmissions and 'CBP-ACE' 

> **For production data transmissions.**

**GS04 373 Date M DT 8/8**

> Date expressed as CCYYMMDD

**GS05 337 Time M TM 4/8**

> 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)

**GS06 28 Group Control Number M N0 1/9**

> Assigned number originated and maintained by the sender.

**GS07 455 Responsible Agency Code M ID 1/2**

> Code identifying the issuer of the standard; this code is used in
> conjunction with
>
> Data Element 480
>
> **CODE DEFINITION**
>
> **X** Accredited Standards Committee X12

**GS08 480 Version / Release / Industry Identifier Code M AN 1/12**

> 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). I
>
> **In truck manifest this is '004060USCBP'**

**Segment: GE** Functional Group Trailer

**Loop:** \_\_\_\_

**Usage:** Mandatory

**Max Use:** 1

**Max Length:** 20

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

![](media/image3.png){width="2.6666666666666665in" height="0.96875in"}

> **Data Element Summary**

**REF. DES. DATA ELEMENT NAME ATTRIBUTES**

**GE01 97 Number of Transaction Sets Included M N0 1/6**

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

**GE02 28 Group Control Number M N0 1/9**

> Assigned number originated and maintained by the sender.

**Segment: IEA** Interchange Control Trailer

**Loop:** \_\_\_\_

**Usage:** Mandatory

**Max Use:** 1

**Max Length:** 20

**Purpose:** To define the end of an interchange of zero or more
functional groups and

> interchange-related control segments.

![](media/image4.png){width="2.6458333333333335in" height="0.84375in"}

> **Data Element Summary**

**REF. DES. DATA ELEMENT NAME ATTRIBUTES**

**IEA01 I16 Number of Included Functional Groups M N0 1/5**

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

**IEA02 I12 Interchange Control Number M N0 9/9**

> A control number assigned by the interchange sender