Post on 04-Aug-2018
Electronic Commerce Client Requirements Document (ECCRD) Chapter 11: Appendix F Advance Commercial Information (ACI)/eManifest UN/EDIFACT Versions 96A, 99B, 08A, and 11B Response Message Implementation Guide
Draft Version 6
Revision History
Date Changes Made
Version Changes Made Changes
Made By
September 2012 Draft 1.0 Draft for distribution EDI Reporting
October 2012 Draft 1.1 Draft for distribution EDI Reporting
October 2012 Draft 2.0 Draft for distribution EDI Reporting
December 2012 Draft 3.0 Draft for distribution EDI Reporting
December 2014 Draft 4.5 Draft for internal review EDI Reporting
January 2015 Draft 5 Draft for external distribution, see Summary of Changes.
EDI Reporting
December 2015 Draft 6 Draft for external distribution, see Summary of Changes.
EDI Reporting
Table of Contents
Table of Contents .................................................................................................................................. 4
UN/EDIFACT CUSRES 96A Customs Response Message Structure and Segments for Conveyance
Arrival Certification Message ............................................................................................................... 5
UN/EDIFACT CUSRES 99B Customs Response Message Structure and Segments for Conveyance
Arrival Certification Message ............................................................................................................. 11
UN/EDIFACT CUSRES 08A Customs Response Message Map ...................................................... 16
UN/EDIFACT CUSRES 08A Customs Response Technical Glossary .............................................. 22
UN/EDIFACT CUSRES 08A Customs Response Sample Message Maps ........................................ 30
UN/EDIFACT GOVCBR 11B Customs Response Data Model Mapping ......................................... 33
UN/EDIFACT GOVCBR 11B Customs Response Message Implementation Guide ........................ 35
UN/EDIFACT GOVCBR 11B Customs Response Sample Map ...................................................... 54
UN/EDIFACT CUSRES 96A Customs Response Message Structure and Segments for
Conveyance Arrival Certification Message
Page 6 of 56
MESSAGE STRUCTURE
INTERCHANGE HEADER UNB
GROUP HEADER UNG
MESSAGE HEADER UNH
CONVEYANCE REFERENCE BGM
NUMBER
SERVICE OPTION ID.
MESSAGE FUNCTION
PORT OF REPORT LOC
PROCESSING DATE/TIME DTM
PROCESSING INDICATOR GIS
REJECT TYPE ERP
ERROR MSG. REF. # Included if
Error or
REJECT REASON CODES ERC Reject
Once applies.
MESSAGE TRAILER UNT
GROUP TRAILER UNE
INTERCHANGE TRAILER UNZ
Page 7 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 96.A
Segment/
Element
ID.
Segment/
Element
Position
Data Element Name
Notes, Conditions and
Descriptions
Data
Type/
Size
Codes and
Values
Default
Syntax
Response
UNB INTERCHANGE HEADER a3 UNB + M1
S001 1 SYNTAX IDENTIFIER
0001 1.1 Syntax Identifier a4 UNOA : M
0002 1.2 Syntax Version Number n1 2 + M
S002 2 INTERCHANGE SENDER
0004 2.1 Sender Identification an..35 CBSA Network Id. : M
0007 2.2 Partner identification code
qualifier
an..4 CBSA Network
Mailbox ID qualifier,
if applicable
+ C
S003 3 INTERCHANGE RECIPIENT
0010 3.1 Recipient Id. an..35 Client Network Id. : M
0007 3.2 Partner identification code
qualifier
an..4 Network Mailbox ID
qualifier, if applicable
+ C
S004 4 DATE/TIME OF
PREPARATION
0017 4.1 Date Generated by Translator n6 YYMMDD : M
0019 4.2 Time Generated by Translator n4 HHMM + M
0020 5 INTERCHANGE CONTROL
REFERENCE NUMBER
Generated by Translator an..14 Unique reference
assigned by sender
++ M
0026 7 APPLICATION REFERENCE a6 CUSRES ' C
UNG FUNCTIONAL GROUP
HEADER
Multiple responses can be sent
within a group.
a3 UNG + M1
0038 1 FUNCTIONAL GROUP ID. a6 CUSRES + M
S006 2 APPLICATION SENDERS ID.
0040 2.1 Senders Identification CCR = Canada Customs
Response
a3 CCR + M
S007 3 APPLICATION RECIPIENTS
ID.
0044 3.1 Recipients Identification an..35 Mutually defined + M
S004 4 DATE/TIME OF
PREPARATION
0017 4.1 Date Generated by Translator n6 YYMMDD : M
0019 4.2 Time Generated by Translator n4 HHMM + M
0048 5 FUNCTIONAL GROUP
REFERENCE NUMBER
Generated by Translator an..14 Unique + M
0051 6 CONTROLLING AGENCY a2 UN + M
S008 7 MESSAGE VERSION
0052 7.1 Message Version Number Draft Status a1 D : M
0054 7.2 Message Release Number Directory Version 96.A an3 96A ' M
Page 8 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 96.A
Segment/
Element
ID.
Segment/
Element
Position
Data Element Name
Notes, Conditions and
Descriptions
Data
Type/
Size
Codes and
Values
Default
Syntax
Response
UNH MESSAGE HEADER a3 UNH + M1
0062 1 MESSAGE REFERENCE
NUMBER
Generated By Translator an..14 Unique + M
S009 2 MESSAGE IDENTIFIER
0065 2.1 Message Type Default a6 CUSRES : M
0052 2.2 Message Version Number Draft Status a1 D : M
0054 2.3 Message Release Number Directory Ver. 96.A an3 96A : M
0051 2.4 Controlling Agency United Nations (uppercase) a2 UN ' M
BGM BEGINNING OF MESSAGE a3 BGM + M1
C002 1 DOCUMENT MESSAGE
NAME
:::
1000 1.4 Document Message Name Service Option ID n..3 3-digit ACROSS
service option of the
inbound message
+ M
1004 2.1 DOCUMENT MESSAGE
NUMBER
Conveyance Reference number an..25 + M
1225 3.1 Message Function, Coded an..3 11 ' M
LOC PLACE/LOCATION a3 LOC + C1
3227 1 PLACE/LOCATION
QUALIFIER
{CBSA Office of Clearance} n2 22 + C
C517 2 LOCATION ID.
3225 2.1 Place/Location Identification CBSA office code. n4 Port of Report : C
DTM DATE/TIME/PERIOD a3 DTM + M1
C507 1 DATE/TIME/PERIOD
2005 1.1 Date/Time/Period qualifier
n..2 9 = {Processing Date} : M
2380 1.2 Date/Time/Period Processing date and time
n12 CCYYMMDDHHM
M
: M
2379 1.3 D/T/P Format Qualifier {EDIFACT qualifier} n3 203 ' M
GIS GENERAL INDICATOR a3 GIS + M1
C529 1 PROCESSING INDICATOR
7365 1.1 Processing Indicator, Coded n..3 1 = Message Content
Accepted
14 = Error message
' M
Segment
group 1
M1
ERP ERROR POINT DETAILS a3 ERP + C1
C701 1 ERROR POINT DETAILS
1049 1.1 Message Section, Coded Default value. n1 2 = Detail
: M
Page 9 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 96.A
Segment/
Element
ID.
Segment/
Element
Position
Data Element Name
Notes, Conditions and
Descriptions
Data
Type/
Size
Codes and
Values
Default
Syntax
Response
1052 1.2 Message Item Number In the case of a syntax error,
will contain the UNH 0062 -
Message Reference Number.
an..14 Senders Message
Reference Number
: C
1054 1.3 Message Sub-Item Number n2 20 = Administration
21 = Enforcement
22 = Conformance
28 = Batch Error
29 = Data Error
' M
ERC APPLICATION ERROR
INFORMATION
a3 ERC + M1
C49
C901 1 APPLICATION ERROR
DETAIL
9321 1.1 Application Error, Coded NOTE 1: These and
additional error message codes
can be found in Code Table 1
NOTE 2: Each 2-digit error
code appearing on the
outbound response is
represented as a 3-digit error
code found in Code Table 1.
Each 2-digit outbound error
code is to be preceded by the
letter “R”, with the exception of
34, which is preceded by the
letter “W”.
an..3 04 = Invalid arrival
message
06 = Invalid Office
Code
08 = EDIFACT
conformance check
error
12 = Invalid Code
17 = EDI arrival not
accepted –
Conveyance is
rejected
18 = Related
Conveyance must be
authorized to move
and arrived
19 = Port of Arrival
must be the same as
the Port of Report
20 = Conveyance is
future dated
21 = CRN exceeds
maximum size
22 = Port of Report
exceeds max size
' M
UNT MESSAGE TRAILER a3 UNT + M1
0074 1 NUMBER OF SEGMENTS IN
MESSAGE
Generated by Translator n..6 Variable + M
0062 2 MESSAGE REFERENCE
NUMBER
Same as UNH 0062 an..14 Unique ' M
UNE FUNCTIONAL GROUP
TRAILER
a3 UNE + M1
0060 1 NUMBER OF MESSAGES Generated by Translator # of
messages in group.
n..6 Variable + M
0048 2 FUNCTIONAL GROUP
REFERENCE NUMBER
Same as UNG 0048 an..14 Unique ' M
UNZ INTERCHANGE TRAILER a3 UNZ + M1
Page 10 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 96.A
Segment/
Element
ID.
Segment/
Element
Position
Data Element Name
Notes, Conditions and
Descriptions
Data
Type/
Size
Codes and
Values
Default
Syntax
Response
0036 1 INTERCHANGE CONTROL
COUNT
Generated by Translator n..6 Variable + M
0020 2 INTERCHANGE CONTROL
REFERENCE NUMBER
Same as UNB 0020 an..14 Unique ' M
UN/EDIFACT CUSRES 99B Customs Response Message Structure and Segments for
Conveyance Arrival Certification Message
Page 12 of 56
Introduction
This message map defines the data elements and structure associated with Electronic Data Interchange
(EDI) messages that will be the Canada Border Services Agency (CBSA) to a participant in response to
an EDI Conveyance arrival. This message has been designed using the international standard
UN/EDIFACT (United Nations/Electronic Data Interchange For Administration Commerce and Transport),
Version 99B.
Message Structure
UNB - Interchange Header
UNG - Functional Group Header
UNH - Message Header
BGM - Beginning of Message
Identifies the type of message
DTM - Date\Time\Period
Provides the Date\Time of preparation or clearance
LOC - Place / Location Identification
Provides the Customs Port of Report
GIS - General Indicator
Provides the processing indicator code
Segment Group 4
ERP - Error Point Details
Provides the error type to be provided in the ERC
RFF – Reference
Provides the Data in error (if applicable)
ERC - Application Error Information
Provides the application error information
UNT - Message Trailer
UNE - Functional Group Trailer
UNZ - Interchange Trailer
Page 13 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 99.B
Segment/
Element ID
Segment/
Element Position
Data Element Names Notes, Conditions and
Descriptions
Data Type/
Size
Codes and Values Default
Syntax
Response
UNB Interchange Header a3 UNB + M1
S001 1 SYNTAX IDENTIFIER
0001 1.1 Syntax identifier a4 UNOA : M
0002 1.2 Syntax version number n1 3 + M
S002 2 INTERCHANGE SENDER
0004 2.1 Sender identification Note that if there is no mailbox
ID qualifier, then the default
syntax for this element should
be a "+" instead of a ":"
an..35 CBSA Network Mailbox
ID
: M
0007 2.2 Partner identification code
qualifier
an..4 Network Mailbox ID
qualifier, if applicable
+ C
S003 3 INTERCHANGE
RECIPIENT ID
0010 3.1 Recipient Identification Note that if there is no mailbox
ID qualifier, then the default
syntax for this element should
be a "+" instead of a ":"
an..35 Client Network Mailbox
ID
: M
0007 3.2 Partner identification code
qualifier
Client Network Mailbox ID
qualifier, if applicable
an..4 Network Mailbox ID
qualifier, if applicable
+ C
S004 4 DATE\TIME OF
PREPARATION
0017 4.1 Date Format should be YYMMDD n6 : M
0019 4.2 Time Format should be HHMM n4 + M
0020 5 INTERCHANGE
CONTROL REFERENCE
CBSA strongly recommends
that every interchange for a
particular client have a unique
reference number, which will
make document tracking much
more effective
an..14 Unique Reference
Number
++ M
0026 7 APPLICATION
REFERENCE
a6 CUSRES ' C
UNG Functional Group Header a3 UNG + M1
0038 1 FUNCTIONAL GROUP
IDENTIFIER
a6 CUSRES + M
S006 2 APPLICATION SENDER'S
IDENTIFICATION
0040 2.1 Application sender's
identification
CCR – Canada Customs
Response
a3 CCR + M
S007 3 APPLICATION
RECIPIENT'S
IDENTIFICATION
0044 3.1 Recipient's identification an..35 Mutually defined + M
S004 4 DATE\TIME OF
PREPARATION
0017 4.1 Date Format should be YYMMDD n6 : M
0019 4.2 Time Format should be HHMM n4 + M
0048 5 FUNCTIONAL GROUP
REFERENCE NUMBER
This reference number must be
unique within the interchange
(UNB -UNZ) of Groups (UNG -
UNE)
an..14 Unique Reference
Number
+ M
0051 6 CONTROLLING AGENCY a2 UN + M
S008 7 MESSAGE VERSION
0052 7.1 Message version number a1 S : M
0054 7.2 Message release number an3 99B ' M
UNH Message Header a3 UNH + M1
Page 14 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 99.B
Segment/
Element ID
Segment/
Element Position
Data Element Names Notes, Conditions and
Descriptions
Data Type/
Size
Codes and Values Default
Syntax
Response
0062 1 MESSAGE REFERENCE
NUMBER
This reference number must be
unique within the group (UNG -
UNE) of messages (UNH -
UNT)
an..14 Unique Reference
Number
+ M
S009 2 MESSAGE IDENTIFIER
0065 2.1 Message Type a6 CUSRES : M
0052 2.2 Message version number a1 S : M
0054 2.3 Message release number an3 99B : M
0051 2.4 Controlling agency a2 UN ' M
BGM Beginning of Message a3 BGM + M1
C002 1 DOCUMENT\ MESSAGE
NAME
:::
1000 1.4 Document Name ACROSS Service Option n..3 3-digit ACROSS service
option of the inbound
message
+ M
1004 2.1 DOCUMENT MESSAGE
NUMBER
Conveyance Reference Number n..25
+ M
1225 3.1 MESSAGE FUNCTION,
CODED
n..3 11
‘ M
DTM Date\Time\Period a3 DTM + M1
C507 1 DATE\TIME\ PERIOD
2005 1.1 Date\time\period function
code qualifier
n..3 9 – Processing Date : M
2380 1.2 Date\time\period value n12 CCYYMMDDHHMM : M
2379 1.3 Date\time\period format
code
n3 203 –
CCYYMMDDHHMM
' M
LOC PLACE/ LOCATION
IDENTIFICATION
a3 LOC + C1
3227 1 PLACE/ LOCATION
QUALIFIER
n..3 22 – Customs Office of
Clearance
+ C
C517 LOCATION
IDENTIFICATION
3225 2 Place/Location ID n4 Customs office code for
Port of Clearance
: C
GIS GENERAL INDICATOR a3 GIS + M1
C529 1 PROCESSING
INDICATOR
7365 1.1 PROCESSING
INDICATOR - CODED
n..3 1 = Message Content
Accepted
14= Error message
' M
Segment
Group 4
M1
C98
ERP Error Point Details a3 ERP + M1
C701 1 ERROR POINT DETAILS
1049 1.1 Message Section, Coded n1 2 - Detail : M
1052 1.2 Message Item Number In the case of a syntax error, will
contain the UNH 0062 Message
Reference Number
an..14 Senders Message
Reference Number
: C
1054 1.3 Message Sub-Item Number n2 20 = Administration
21 = Enforcement
22 = Conformance
28 = Batch Error
29 = Data Error
' M
RFF REFERENCE a3 RFF + C1
Page 15 of 56
CBSA Response Message (EDIFACT/CUSRES) Version 99.B
Segment/
Element ID
Segment/
Element Position
Data Element Names Notes, Conditions and
Descriptions
Data Type/
Size
Codes and Values Default
Syntax
Response
C506 1 REFERENCE
1153 1.1 Reference Qualifier a3 ZZZ – Mutually Defined : M
1154 1.2 Reference Number Data in Error an..35 ' M
ERC APPLICATION ERROR
INFORMATION
a3 ERC + M1
C98
C901 1 APPLICATION ERROR
DETAIL
9321 1.1 Application Error
Identification
an..3 R04 = Invalid arrival or
delivery/query message
R06 = Invalid Office Code
R08 = EDIFACT
conformance check error
R12 = Invalid Code
* For additional Error
Codes, see Code Table 1
' M
UNT Message Trailer a3 UNT + M1
0074 1 NUMBER OF SEGMENTS
IN MESSAGE
This field indicates the number
of segments, including UNH
and UNT, within the message
(UNH - UNT set)
n..6 + M
0062 2 MESSAGE REFERENCE
NUMBER
Value should be the same as
UNH element 0062
an..14 ' M
UNE Functional Group Trailer a3 UNE + M1
0060 1 NUMBER OF MESSAGES This field indicates the number
of messages (UNH - UNT sets)
within the group (UNG - UNE)
n..6 + M
0048 2 FUNCTIONAL GROUP
REFERENCE NUMBER
Value should be the same as
UNG element 0048
an..14 ' M
UNZ Interchange Trailer a3 UNZ + M1
0036 1 INTERCHANGE
CONTROL COUNT
This field indicates the number
of groups (UNG - UNE sets)
within the interchange (UNB -
UNZ)
n..6 + M
0020 2 INTERCHANGE
CONTROL REFERENCE
NUMBER
Value should be the same as
UNB element 0020
an..14 ' M
Page 16 of 56
UN/EDIFACT CUSRES 08A Customs Response Message
Map
Page 17 of 56
Introduction
This message map defines the data elements and structure associated with Electronic Data Interchange
(EDI) messages that will be sent by the Canada Border Services Agency (CBSA) to a participant in
response to an EDI message. This message map will provide the client the following different types of
responses for Cargo and Conveyance only:
1. Functional acknowledgement or error/reject
2. Application acknowledgement or error/reject
3. Section 12(1) report of the Conveyance
Refer to the Release Notification System Participants Requirements Document for information regarding
message maps that define the data elements and structure associated with EDI release and arrival
messages for the following:
1. Inward/inbound CUSREP messages to CBSA:
i. Report the arrival of a shipment or rail Conveyance
ii. Query on the status of a shipment
2. Outward/outbound CUSRES responses from CBSA:
i. Declaration accepted, awaiting arrival message
ii. Automatic release notification message
This message has been designed based on the international standard UN/EDIFACT (United
Nations/Electronic Data Interchange For Administration Commerce and Transport), Version 08A.
Page 18 of 56
Explanation of Message Map Columns
The message map contains a number of information columns for each data element. The function and
values of the "columns" are described below.
UN/EDIFACT Segment Id.
Every EDIFACT segment (a group of associated data elements) is assigned a unique 3 alpha "Tag" for
reference purposes. The tags are defined within the EDIFACT data element directories. It should be
noted that the "tag" is transmitted within the EDI messages in the order that they are defined.
UN/EDIFACT Element Id.
This column of the map identifies the alphanumeric or numeric identifier of each of the UN/EDIFACT
data elements. There are three (3) types of elements defined. Descriptions of each are provided below.
It should be noted that the Element IDs are not transmitted within the message, only the value of the
data element is transmitted in the appropriate position within the segment.
Composite Data
Element Name - Identifies a high level name of a set of associated data elements. The associated data elements are referred to as "component" data elements. Composites are identified by a single alpha character (C or S) followed by 3 unique numerics.
Component Data
Element Name - Identification of a component data element which is part of a composite data element. Component data elements are identified by 4 unique numerics.
Simple Data
Element Name - Name of an unique/individual data element within a segment, a "simple" data element contains one element for a single function/use. Simple data elements are identified by 4 unique numerics.
Segment/Element Position
This column of the map identifies the Segment or Element position within the CUSRES message
structure. The Segments are numbered in ascending values of 10 for each occurrence of a segment in the
message structure. The Element position numbers identify the position of a data element within a
segment. In the EDIFACT documentation only Composite data elements and Simple data elements are
numbered in a segment. They are assigned ascending values of 10 for each occurrence of a composite or
simple data element. To more specifically identify the data element positions, each Composite is assigned
an incrementing number starting at 1. Within each composite, the component data elements are assigned a
sequential subordinate number. Simple data elements are assigned the next sequential number in order of
occurrence within the segment.
Page 19 of 56
Example:
UN/EDIFACT Definitions: Mapping Definitions:
Seg. Pos. Element Seg. Pos. Element
Pos. Pos. 0010 UNH Message Header 0010 UNH Message Header 0062 10 Message Reference Number 0062 1 Message Reference Number S009 20 Message Identifier S009 2 Message Identifier 0065 Message Type 0065 2.1 Message Type 0052 Message Version Number 0052 2.2 Message Version Number 0054 Message Release Number 0054 2.3 Message Release Number 0051 Controlling Agency 0051 2.4 Controlling Agency
EDIFACT Data Element Names
This column provides the name of the EDIFACT Segment, Composite, Component, or Simple Data
element, as defined in the UN/EDIFACT directories.
Notes and Descriptions
This column of the map provides notes and/or descriptions on the Segments Groups, Segments, and individual data elements. It also will identify the application data elements associated to the EDIFACT data elements. In many cases mandatory EDIFACT codes are used to qualify the data element being supplied. In these cases the description of the EDIFACT codes values are provided.
Data Type/Size
The attributes of data type and maximum size are defined in this column. These are described using an
EDIFACT standard of definition as follows;
A = Alpha characters (a to z)
N = Numeric characters (0 to 9)
AN = Alphanumeric characters (a to z, 0 to 9, plus special characters)
.. = Two periods indicate a variable length field, else it is a fixed length field
Examples : A5 = alpha must be 5 in length;
A..5 = alpha up to 5 in length;
N15 numeric must be 15 in length;
AN..12 = alpha numeric up to 12 in length.
Page 20 of 56
AN9..15 = alpha numeric, must be a minimum of 9 characters, up to 15.
Codes and Values
This column provides the details of the content of the data element, the expected values/codes or the applicable application data element to be supplied. In the case of Date/Time data elements the format of the date/time is also defined.
Default Syntax
The EDIFACT message structure is formatted using a set of special characters to control the position of
data within a segment. The required EDIFACT syntax to be transmitted after each value is provided in
this column. In some cases conditional data elements within a segment must be “skipped” (if they are not
used), in these case more than one syntax character has been specified after a particular data element.
Err Resp or RNS
The syntax of the message will depend on if it is an error response to an inbound arrival or Query
message or the message is issued as a positive syntax acknowledgement. The two columns describe the
status (mandatory or conditional – occurrence count) as described below.
Status - Mandatory or Conditional - Occurrence Count
Depending on the message requirement different rules of "mandatory" or "conditional" use of a data
element may apply. In addition a hierarchy of rules apply, if a segment or composite data element is
conditional, but it is used (based on the condition) some of the subordinate elements may be mandatory.
In addition to the status some segments may be repeated more that once within a message, if there is a
repeat factor this is also specified in this column.
M - Mandatory element must always be transmitted.
C - Conditional element, is transmitted if the application condition for this element applies.
M3 - A number after the condition indicates the number of occurrences at the segment level.
(e.g. Mandatory 3 times)
N/A- Not applicable for the particular message type.
Section 12(1) Report Notification:
Upon the Conveyance arrival at the FPOA, when the BSO updates the status of the Conveyance to
arrived, the CBSA will send the Section 12(1) Report notification to the transporting carrier detailing the
CCNs of the related cargo submissions that are deemed to have been reported as per section 12(1) of the
Customs Act. There will be one message sent for each trip, but each message will detail all of the CCNs
related to that trip.
This notification does not mean the goods have been released from customs control. Release notification
will still be delivered via RNS until ACI enhanced notifications are available.
Page 21 of 56
Message Structure
UNB - Interchange Header
UNG - Functional Group Header
UNH - Message Header
BGM - Beginning of Message
Identifies the type of message
DTM - Date\Time\Period
Provides the Date\Time of preparation or clearance
FTX - Free Text
Provides the delivery instructions if available
TDT - Transport information
Provides Conveyance Reference Number (CRN)
LOC - Place / Location Identification (S12 only)
Provides the consignment entry CBSA office location
GEI - General Indicator
Provides the processing indicator code
Segment Group 3
RFF - Reference
Provides the Secondary Business ID
Provides the Cargo Control Number (S12 only)
Segment Group 4
ERP - Error Point Details
Provides the error type to be provided in the ERC
RFF – Reference
Provides the Data in error (if applicable)
ERC - Application Error Information
Provides the application error information
FTX – Free Text
Provides the Textual error Description (if available)
UNT - Message Trailer
UNE - Functional Group Trailer
UNZ - Interchange Trailer
Page 22 of 56
UN/EDIFACT CUSRES 08A Customs Response Technical Glossary
Page 23 of 56
Data Element
Name
Data Element
Definition
Rules And Conditions
Message type Identification of the
type of message
being transmitted
CUSRES = Customs Response Message
Document message
name
Service Option
Identifier
976 – Highway Conveyance
992 – Rail Conveyance
984 – Cargo
Message function,
coded
A code indicating
the function of the
message.
11 = Response Message
Date\Time\Period
DTM(1)
Processing date/time Date and time at which the incoming message was processed will be transmitted
Format is CCYYMMDDHHMM where C=Century, Y=Year, M=Month, D=Day, H=Hour,
M=Minute
Date\Time\Period
DTM(2)
Section 12(1) Report
Notification
Upon the Conveyance arrival at the FPOA, when the BSO updates the status of the
Conveyance to arrived, or upon acceptance of the Conveyance Arrival Certification Message from
the rail carrier, the CBSA will send this notification to the carrier detailing the CCNs of the related
Cargo submissions that are deemed to have been reported as per section 12(1) of the Customs Act.
There will be one message sent for each trip containing 200 related CCNs or less, but each
message will detail all of the CCNs related to that trip. Multiple messages for the same
Conveyance will be generated when there are more than 200 related CCNs in increments of 200
CCNs per message.
This notification does not mean the goods have been released from customs control.
Release notification will still be delivered via RNS until ACI enhanced notifications
are available.
Location
Identification LOC
CBSA office code
for Port of Report
Used for Section 12(1) Report only. See Code Table #4 – CBSA Office Codes
General Indicator
GEI(1)
Processing indicator
for positive
responses/
acknowledgements
A code to indicate the positive processing acknowledgement
1 = Application Acknowledgement, Message content accepted
Page 24 of 56
General Indicator
GEI(2)
Processing indicator
for error responses
A code to indicate the negative error response.
14 = Error Message
General Indicator
GEI(3)
Processing indicator
for Section 12
Report message
Upon the Conveyance arrival at the FPOA, when the BSO updates the status of the Conveyance to
arrived, the CBSA will send the Section 12(1) Report notification to the transporting carrier detailing
the CCNs of the related Cargo submissions that are deemed to have been reported as per section
12(1) of the Customs Act. There will be one message sent for each trip, but each message will detail
all of the CCNs related to that trip.
General Indicator
GEI(4)
Processing Indicator
for Y66 message
This message is generated when there is less than one hour between receipt of transmission and
estimated time of arrival on the message.
NOTE: warning error message V67 is provided with code 66 as a second message on the
transaction, independent of either the acknowledgement or error message.
66 – Message content accepted with comment
Reference RFF(1) Secondary Business
ID
ZZZ – Secondary Business ID
NOTE: this identifier cannot be provided when the client transmits a delete. In this case, CBSA
will provide the reference ID supplied in the most recent EDI original /change request.
Reference RFF(2) Acknowledgement
Reference Identifier
ED – Export Declaration
Reference RFF(3) Section 12(1) Cargo
Control Number
XC – Cargo control number
Error Point Details
ERP
Senders Message
Reference Number
Will contain the UNH 0062 Message Reference Number
Error Point Details
ERP
Message Sub-Item
Number
Reject type code associated where the processing indicator = 14.
The following codes will be transmitted:
Syntax Reject:
28 – Batch Error
Validation Reject:
22 – Conformance
Manual Reject:
21 – Enforcement
Application Error
Information ERC
The code assigned
by the receiver of a
message to the
identification of a
data validation error
condition.
Reject reason code for application reject error responses with the processing indicator = 14.
See Code Table 1
ZZZ = Syntax Reject
Free Text FTX Error Description Data in Error or BSO Error Text
Page 25 of 56
EDIFACT
Segment
ID.
EDIFACT
Element ID.
Segment/
Element
Position
EDIFACT Data Element Name Notes, Conditions, and
Descriptions
Data Type
& Size
Codes & Values Default Syntax
Element Status M or C and
Occurrence Count
ACK Error
Responses
S12 V67
Insuff.
Time
Warning Accept Syntax
Reject
Appl.
Reject
UNB Interchange control header To start and identify an
interchange and
interchange-related control
segments
A3 UNB + M1 M1 M1 M1 M1
S001 1 Syntax identifier
0001 1.1 Syntax identifier Code identification of the Agency controlling syntax.
A4 UNOA : M M M M M
0002 1.2 Syntax version number Version number of the syntax. N1 4 + M M M M M
S002 2 Interchange sender
0004 2.1 Sender identification Name/coded representation of the sender.
AN..35 CBSA Network Mailbox ID : M M M M M
0007 2.2 Identification code qualifier AN..4 + C C C C C
S003 3 Interchange recipient
0010 3.1 Recipient identification Name/coded representation of the recipient.
AN..35 Client Network Mailbox ID + M M M M M
S004 4 Date/time of preparation
0017 4.1 Date of preparation Generated by Translator N6 YYMMDD : M M M M M
0019 4.2 Time of preparation Generated by Translator N4 HHMM + M M M M M
0020 5 Interchange control reference Unique Reference Number assigned by the sender. Generated by Translator
AN..14 ++ M M M M M
0026 7 Application Reference A6 + C C C C C
0029 8 Processing Priority Code A1 A +++ C C C C C
0035 11 Test Indicator N1 1 (Used for test only) ‘ C C C C C
UNG FUNCTIONAL GROUP
HEADER
To indicate the beginning
of a functional group and
to provide control
information
A3 UNG + M1 M1 M1 M1 M1
0038 1 Functional group identification Identification of the one type of message in the Functional Group
A6 CUSRES + M M M M M
S006 2 Application sender identification
0040 2.1 Sender identification CBSA Response AN8 CCR : M M M M M
0007 2.2 Sender id. Qualifier I/B Control Office (Optional) AN..4 + C C C C C
S007 3 Application recipient identification
0044 3.1 Recipient’s identification A7 Client’s Network Mailbox ID
+ M M M M M
S004 4 Date/time of preparation
0017 4.1 Date of preparation Generated by Translator N6 CCYYMMDD : M M M M M
0019 4.2 Time of preparation Generated by Translator N4 HHMM + M M M M M
Page 26 of 56
EDIFACT
Segment
ID.
EDIFACT
Element ID.
Segment/
Element
Position
EDIFACT Data Element Name Notes, Conditions, and
Descriptions
Data Type
& Size
Codes & Values Default Syntax
Element Status M or C and
Occurrence Count
ACK Error
Responses
S12 V67
Insuff.
Time
Warning Accept Syntax
Reject
Appl.
Reject
0048 5 Functional group reference number
Unique Reference Number Assigned by the Sender. Generated by Translator
AN..14 + M M M M M
0051 6 Controlling agency Agency Controlling the Message Type.
A2 UN + M M M M M
S008 7 Message version
0052 7.1 Message version number Version number of the message type.
A1 D : M M M M M
0054 7.2 Message release number Release number of the current message type.
AN3 08A M M M M M
UNH 0010 Message header A3 UNH + M1 M1 M1 M1 M1 0062 1 MESSAGE REFERENCE
NUMBER Unique message reference assigned by the sender
AN..14 Unique Reference Number + M M M M M
S009 2 MESSAGE IDENTIFIER
0065 2.1 Message Type A6 CUSRES : M M M M M
0052 2.2 Message version number A1 D : M M M M M
0054 2.3 Message release number AN3 08A : M M M M M
0051 2.4 Controlling agency A2 UN ' M M M M M
BGM Beginning of Message A3 BGM + M1 M1 M1 M1 M1 C002 1 DOCUMENT\MESSAGE NAME
1001 1.1 Document name code AN..3 : C C C C C 1131 1.2 Code list identification code AN..17 : C C C C C 3055 1.3 Code list responsible agency
code AN..3 : C C C C C
1000 1.4 Document Name ACROSS Service Option N..3 976 – Highway Conveyance 992 – Rail Conveyance
984 – Cargo
+ M M M M M
C106 2 DOCUMENT MESSAGE IDENTIFICATION
1004 2.1 Document identifier Cargo Control Number / Conveyance Reference Number
N..25 + M M M M M
1225 3.1 Message Function, coded AN..3 11 – Response ‘ M M M M M
DTM (1) Date\Time\Period Processing Date A3 DTM + M1 M1 M1 N/A M1 C507 1 DATE\TIME\PERIOD
2005 1.1 Date\time\period function code qualifier
N..3 9 – Processing Date : M M M M
2380 1.2 Date\time\period value N12..17 : M M M M
2379 1.3 Date\time\period format code N3 203 – CCYYMMDDHHMM ' M M M M
DTM (2) Date\Time\Period Section 12(1) Report Date A3 DTM + N/A N/A N/A M1 N/A C507 1 DATE\TIME\PERIOD
2005 1.1 Date\time\period function code qualifier
N..3 58 – Clearance Date (S12) : M
2380 1.2 Date\time\period value Date/time of report to CBSA. N12..17 : M
Page 27 of 56
EDIFACT
Segment
ID.
EDIFACT
Element ID.
Segment/
Element
Position
EDIFACT Data Element Name Notes, Conditions, and
Descriptions
Data Type
& Size
Codes & Values Default Syntax
Element Status M or C and
Occurrence Count
ACK Error
Responses
S12 V67
Insuff.
Time
Warning Accept Syntax
Reject
Appl.
Reject
2379 1.3 Date\time\period format code N3 204 – CCYYMMDDHHMMSS (S12)
' M
LOC PLACE/LOCATION
IDENTIFICATION
Used for Section 12(1)
Report only
A3 LOC + N/A N/A N/A C1 N/A
3227 1 PLACE/LOCATION QUALIFIER N..3 41 – Consignment entry customs office location
+ C
C517 2 LOCATION IDENTIFICATION
3225 2.1 Place/Location ID CBSA office code for Port of Report
N4 See Code Table #4 – CBSA Office Codes
: C
1131 2.2 Code List Qualifier N3 : C 3055 2.3 Code list responsible agency
code AN..3 96 – CA, Canada Border
Services Agency
‘ C
GEI(1) GENERAL INDICATOR Processing indicator
for positive responses/
acknowledgements
A3 GEI + M1 N/A N/A N/A N/A
9649 1 PROCESSING INFORMATION CODE QUALIFIER
An..3 5 – Consignment information + M
C012 2 PROCESSING INDICATOR
7365 2.1 Processing indicator description code
N..3 1 – Message content accepted (application acknowledgement)
17 – Message received (functional acknowledgement)
‘ M
GEI(2) GENERAL INDICATOR Processing indicator
for error responses
A3 GEI + N/A M1 M1 N/A N/A
9649 1 PROCESSING INFORMATION CODE QUALIFIER
An..3 5 – Consignment information + M M
C012 2 PROCESSING INDICATOR
7365 2.1 Processing indicator description code
N..3 14 – Error message for Syntax or Application Reject
‘ M M
GEI(3) GENERAL INDICATOR Processing indicator for
Section 12 Report message
A3 GEI + N/A N/A N/A M1 N/A
9649 1 PROCESSING INFORMATION CODE QUALIFIER
An..3 3 – Scheduling type information
+ M
C012 2 PROCESSING INDICATOR
7365 2.1 Processing indicator description code
N..3 200 – Reported
:: M
3055 2.3 Code list responsible agency code
an..3 96 – CA, Canada Border Services Agency
‘ C
Page 28 of 56
EDIFACT
Segment
ID.
EDIFACT
Element ID.
Segment/
Element
Position
EDIFACT Data Element Name Notes, Conditions, and
Descriptions
Data Type
& Size
Codes & Values Default Syntax
Element Status M or C and
Occurrence Count
ACK Error
Responses
S12 V67
Insuff.
Time
Warning Accept Syntax
Reject
Appl.
Reject
GEI(4) GENERAL INDICATOR Processing indicator for
V67 Insufficient Review
Time warning message
A3 GEI + N/A N/A N/A N/A M1
9649 1 PROCESSING INFORMATION CODE QUALIFIER
An..3 3 – Scheduling type information
+ M
C012 2 PROCESSING INDICATOR
7365 2.1 Processing indicator description code
NOTE: warning error message V67 is provided with code 66 as a second message on the transaction, independent of either an accept or a reject message.
N..3 66 – Message content accepted with comment
‘ M
Segment Group 3
C2 C1
C1
M1
C20
0
C1
RFF(1) REFERENCE Secondary Business ID A3 RFF + C1 C1 C1 M1 C1 C506 1 REFERENCE
1153 1.1 Reference Qualifier A2..3 ZZZ – Secondary Business ID : C C C C C
1154 1.2 Reference Number Secondary Business ID AN..25 ' C C C C C
RFF(2) REFERENCE Acknowledgement A3 RFF + C1 N/A N/A N/A N/A C506 1 REFERENCE
1153 1.1 Reference Qualifier A2..3 ED – Export Declaration : C
RFF(3) REFERENCE Section 12(1) CCN A3 RFF + N/A N/A N/A C20
0
N/A
C506 1 REFERENCE
1153 1.1 Reference Qualifier A2..3 XC – Cargo control number : C
1154 1.2 Reference Number Cargo Control Number AN..25 ' C
Segment Group 4 (Used for Messages)
N/A M1
C98
M1
C98
N/A M1
C98
ERP Error Point Details A3 ERP + N/A M1 M1 N/A M1 C701 1 ERROR POINT DETAILS
1049 1.1 Message Section, Coded N1 2 – Detail : M M M
1052 1.2 Message Item Number Will contain the UNH 0062 Message Reference Number
AN..14 Senders Message Reference Number
: C C C
1054 1.3 Message Sub-Item Number N2 20 – Administration
21 – Enforcement
22 – Conformance
28 – Batch Error
29 – Data Error
' M M M
ERC APPLICATION ERROR
INFORMATION
A3 ERC + N/A C99 C99 N/A C99
Page 29 of 56
EDIFACT
Segment
ID.
EDIFACT
Element ID.
Segment/
Element
Position
EDIFACT Data Element Name Notes, Conditions, and
Descriptions
Data Type
& Size
Codes & Values Default Syntax
Element Status M or C and
Occurrence Count
ACK Error
Responses
S12 V67
Insuff.
Time
Warning Accept Syntax
Reject
Appl.
Reject
C901 1 APPLICATION ERROR DETAIL
9321 1.1 Application Error Identification AN..3 See Code Table 1
ZZZ = Syntax Reject
' M M M
FTX FREE TEXT A3 FTX + N/A C99 C99 N/A N/A 4451 1 TEXT SUBJECT QUALIFIER A3 AAO – Error Description +++ M M
C108 4 TEXT LITERAL 4440 4.1 Free Text Data in Error or BSO Error Text AN..142 ‘ M M UNT Message Trailer A3 UNT + M1 M1 M1 M1 M1 0074 1 NUMBER OF SEGMENTS IN
MESSAGE This field indicates the number of segments, including UNH and UNT, within the message (UNH - UNT set)
N..6 + M M M M M
0062 2 MESSAGE REFERENCE NUMBER
Value should be the same as UNH element 0062
AN..14 ' M M M M M
UNE Functional Group Trailer A3 UNE + M1 M1 M1 M1 M1 0060 1 NUMBER OF MESSAGES This field indicates the number of
messages (UNH - UNT sets) within the group (UNG - UNE)
N..6 + M M M M M
0048 2 FUNCTIONAL GROUP REFERENCE NUMBER
Value should be the same as UNG element 0048
AN..14 ' M M M M M
UNZ Interchange Trailer A3 UNZ + M1 M1 M1 M1 M1 0036 1 INTERCHANGE CONTROL
COUNT This field indicates the number of groups (UNG - UNE sets) within the interchange (UNB - UNZ)
N..6 + M M M M M
0020 2 INTERCHANGE CONTROL REFERENCE NUMBER
Value should be the same as UNB element 0020
AN..14 '
Page 30 of 56
UN/EDIFACT CUSRES 08A Customs Response Sample
Message Maps
Page 31 of 56
Outbound for Positive Application Acknowledgement (ACK):
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+100712:1749+467+++A+++1
UNG+CUSRES+CCR+TEST+20100712:1749+233+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+:::984+2XXXADECCRDEDIFACTS12001+11
DTM+9:201007121742:203
GEI+5+1
UNT+5+1
UNE+1+233
UNZ+1+467
Outbound for Syntax Error (Elements too long – RFF and COM):
UNA:+.?
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+100712:1901+522+++A+++1
UNG+CUSRES+CCR+ECCRDTEST+20100712:1901+284+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+:::984+2XXXADECCRDEDIFACTSYNTAX001+11
DTM+9:201007121859:203
GEI+14
ERP+2:MSG_1:28
ERC+ZZZ
FTX+AAO+++SEGMENTRFFLINE7ELEM1154[1.2]ELEM TOO LONG
ERP+2:MSG_1:28
ERC+ZZZ
FTX+AAO+++SEGMENTCOMLINE21ELEM3148[1.1]ELEM TOO LONG
ERP+2:MSG_1:28
ERC+ZZZ
FTX+AAO+++SEGMENTCOMLINE24ELEM3148[1.1]ELEM TOO LONG
ERP+2:MSG_1:28
ERC+ZZZ
FTX+AAO+++SEGMENTCOMLINE27ELEM3148[1.1]ELEM TOO LONG
UNT+17+1
UNE+1+284
UNZ+1+522
Outbound for Syntax Error (Line count error):
UNA:+.?
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+999999:9999+1245+++A
UNG+CUSRES+CCR+ECCRDTEST+20100716:1458+385+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+:::984+2XXXADEDIFACTTESTCCN26+11
DTM+9:201007161458:203
GEI+5+14
ERP+2:MSG_1:28
ERC+ZZZ
FTX+AAO+++TRANSACTION AT BYTE OFFSET108-INVALID SEGMENT COUNT
UNT+8+1
UNE+1+385
UNZ+1+1245
Page 32 of 56
Outbound for Application Reject (Invalid Port Code 8527):
UNA:+.?
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+100712:1758+514+++A+++1
UNG+CUSRES+CCR+ECCRDTEST+20100712:1758+280+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+:::984+2XXXADECCRDEDIFACTY50001+11
DTM+9:201007121749:203
GEI+5+14
ERP+2:MSG_1:22
ERC+467
FTX+AAO+++8527
UNT+8+1
UNE+1+280
UNZ+1+514
Outbound for Warning Message for Insufficient Review Time:
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+101031:1317+5412+++A
UNG+CUSRES+CCR+ECCRDTEST+20101031:1317+1661+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+:::984+2XXXEDIFACTY66MSG01+11
DTM+9:201010311314:203
GEI+3+66
RFF+ZZZ:AD TEST Y66
ERP+2:MSG_1:22
ERC+V67
UNT+8+1
UNE+1+1661
UNZ+1+5412
Outbound for Section 12(1) Reporting Message:
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+101101:0827+5415+++A
UNG+CUSRES+CCR+ECCRDTEST+20101101:0827+1664+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+98:::976+2XXXEDIFACTS12OCT31V1+11
DTM+58:20101101082612:204
LOC+41+0495::96
GEI+3+200::96
RFF+ZZZ:AD TEST S12 OCT 31
RFF+XC:2XXXANSIY660001
RFF+XC:2XXXEDIFACTY660001
RFF+XC:2XXXEDIFACTY66MSG01
UNT+10+1
UNE+1+1664
UNZ+1+5415
Outbound for Manual Reject by Officer:
UNB+UNOA:4+TESTING:ZZ+ECCRDTEST+101031:1120+5404+++A
UNG+CUSRES+CCR+ECCRDTEST +20101031:1120+1657+UN+D:08A
UNH+1+CUSRES:D:08A:UN
BGM+:::984+2XXXEDIFACTOB0001+11
DTM+9:201008091349:203
GEI+5+14
RFF+ZZZ:AD TEST Y66
ERP+2:MSG 1:21
ERC+500
FTX+AAO+++TESTING EDIFACT OUTBOUND ERROR MESSAGE TEXT WHICH SHOULD APPEAR IN THE FXT
SEGMENT OF THE MAP AND SHOULD ALSO LOOP THE MESSAGE TEXT
UNT+9+1
UNE+1+1657
UNZ+1+5404
UN/EDIFACT GOVCBR 11B Customs Response Data
Model Mapping
Response DM to Response GOVCBR
Mapping
Model: CBSA Response Data Model Guide Root Element: Response
Standard: GOVCBR; 3.2; 20-09-2011 Guide: Response Message - EDIFACT
GOVCBR v11B
Legend: No=Consecutive Number, SeNo=Segment Number, Se=Segment, CDE=Composite Data Element, DE=Data Element, St=Status Status indicators: M=Mandantory, C=Conditional, R=Required, O=Optional, D=Depending, A=Advised, N/X=Not used
Response DM to Response GOVCBR; repo Issue date: 2012-08-20 Print date: 2012-08-20 Generated by GEFEG.FX
Page: 34 / 56
No Occurrence
Element SeN Se CDE DE St Format Example
001 1 .. 1 CBSA Message Type Specifies the message type
4 BGM C002 1001 M an..3 312
Path: GOVCBR.BGM.C002.1001(0020:010:01)
002 1 .. 1 CBSA Reference Number Original Client Supplied Request ID
4 BGM C106 1004 M an..40 8XXX1234
Path: GOVCBR.BGM.C106.1004(0020:020:01)
003 0 .. 1 CBSA Message Function, coded Indicate response message function
4 BGM 1225 M an..3 11
Path: GOVCBR.BGM.1225(0020:030)
004 1 .. 1 Response Date/Time Date/Time of the outbound response notice from CBSA
5 DTM C507 2380 M an..17 201208170900
Path: GOVCBR.DTM.C507.2380(0030:010:02)
005 0 .. 1 Secondary Business ID Secondary Business ID based on source document NOTE: this identifier cannot be provided when the client transmits a delete. In this case, CBSA will provide the reference ID supplied in the most recent EDI original /change request.
6 RFF C506 1154 M an..60 SECONDARY BUSINESS ID
Path: GOVCBR.RFF.C506.1154(0060:010:02)
006 0 .. 1 Data in error or BSO error text 8 FTX C108 4440 M an..256 DATA ELEMENT IN ERROR OR BSO TEXT
Path: GOVCBR.SG13.FTX.C108.4440(0560:040:01)
007 0 .. 1 CBSA Processing Indicator GEI indicator used by CBSA to determine the type of response being issued
9 GEI C012 7365 M an..3 66
Path: GOVCBR.SG13.GEI.C012.7365(0580:020:01)
008 0 .. 1 External error code Refer to ACROSS error message code table list at http://cbsa.gc.ca/ eservices/error-erreur.pdf
10 ERC C901 9321 M an..8 W40
Path: GOVCBR.SG17.ERC.C901.9321(0690:010:01)
UN/EDIFACT GOVCBR 11B Customs Response Message
Implementation Guide
Counter No Tag St MaxOcc Level Content
0000 1 UNB M 1 0 Interchange header
0000 2 UNG M 1 1 Functional group header
0010 3 UNH M 1 0 Message header
0020 4 BGM M 1 0 Beginning of message
0030 5 DTM M 1 1 Date/time/period
0060 6 RFF C 1 1 Secondary Business Number
0540 SG13 C 1 1 Processing Indicator
0550 7 RCS M 1 1 Requirements and conditions
0560 8 FTX C 1 2 Free text
0580 9 GEI C 1 2 Processing information
0680 SG17 C 99 1 ERC-ERP
0690 10 ERC M 1 1 Application error information
0700 SG18 C 1 2 ERP
0710 11 ERP M 1 2 Error point details
1810 12 UNS M 1 0 Section control
5960 13 HYN M 1 0 Hierarchy information
10360 14 UNS M 1 0 Section control
10390 15 UNT M 1 0 Message trailer
0000 16 UNE M 1 0 Functional group trailer
0000 17 UNZ M 1 0 Interchange trailer
Response Message - EDIFACT GOVCBR
Segments
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 37 / 56
Counter No Tag St MaxOcc Level Name
0000 1 UNB M 1 0 Interchange header
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNB
S001 Syntax identifier 010 M
0001 Syntax identifier 1 M a4 Code identification of the Agency controlling syntax. UNOA UN/ECE level A
0002 Syntax version number 2 M n1 Version number of the syntax. 3 Version 3
S002 Interchange sender 020 M
0004 Sender identification 3 M an..35 Name/coded representation of the sender. (CBSA Network ID)
0007 Partner identification code qualifier
4 O an..4 Sender ID Qualifier (Optional)
S003 Interchange recipient 030 M
0010 Recipient identification 5 M an..35 Name/coded representation of the recipient. (Client's Network ID)
0007 Partner identification code qualifier
6 O an..4 Receiver ID Qualifier (Optional)
S004 Date/time of preparation 040 M
0017 Date of preparation 7 M n6 Generated by Translator
0019 Time of preparation 8 M n4 Generated by Translator
0020 Interchange control reference
050 M an..14 Unique Reference Number assigned by the sender.
Remark:
Note the size of the entire interchange message cannot exceed 4MB
Example:
UNB+UNOA:3+SENDERID:ZZZ+RECEIVERID:ZZZ+120817:0900+99900000000001'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 38 / 56
Counter No Tag St MaxOcc Level Name
0000 2 UNG M 1 0 Functional group header
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNG
0038 Functional group identification
010 M an..6 GOVCBR Identification of the one type of message in the Functional Group
S006 Application sender's identification
020 M
0040 Sender identification 2 M an..35 Client's Transmission Site CCR = Canada Customs Response
S007 Application recipient's identification
030 M
0044 Recipient's identification 3 M an..35 Defined by client.
0007 Partner identification code qualifier
4 O an..4 Application Receiver ID Qualifier (Optional)
S004 Date/time of preparation 040 M
0017 Date of preparation 5 M n6..8 Generated by Translator
0019 Time of preparation 6 M n4 Generated by Translator
0048 Functional group reference number
050 M an..14 Unique Reference Number assigned by the sender.
0051 Controlling agency 060 M an..2 Agency controlling the message type. UN UN/CEFACT
S008 Message version 070 M
0052 Message version number 9 M an..3 Version number of the message type. D Draft version/UN/EDIFACT Directory
0054 Message release number 10 M an..3 11B Release 2011 - B Release number of the message type.
Remark:
Example:
UNG+GOVCBR+CCR+APPRECEIVERID:ZZZ+120817:0900+9999+UN+D:11B'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 39 / 56
Counter No Tag St MaxOcc Level Name
0010 3 UNH M 1 0 Message header
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNH
0062 Message reference number 010 M an..14 Unique Reference Number assigned by the sender.
S009 Message identifier 020 M
0065 Message type 2 M an..6 Identification of the message type. GOVCBR Government cross border regulatory
message
0052 Message version number 3 M an..3 Version number of the message type. D Draft version/UN/EDIFACT Directory
0054 Message release number 4 M an..3 Release number of the message type. 11B Release 2011 - B
0051 Controlling agency 5 M an..2 Agency controlling the message type. UN UN/CEFACT
Remark:
Example:
UNH+1234+GOVCBR:D:11B:UN'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 40 / 56
Counter No Tag St MaxOcc Level Name
0020 4 BGM M 1 0 Beginning of message
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
BGM
C002 Document/message name 010 M
1001 Document name code 1 M an..3 CBSA Message Type Specifies the message type
312 Acknowledgement message Positive application acknowledgement message
313 Application error message Negative application acknowledgement message
961 General response (Customs) Functional response messages
962 Document response (Customs) Insufficient review time notice
C106 Document/message identification
020 M
1004 Document identifier 2 M an..40 CBSA Reference Number Original Client Supplied Request ID
1225 Message function code 030 M an..3 11 Response CBSA Message Function, coded Indicate response message function
Remark:
CBSA Message Type 961 includes both Functional Acknowledgment Notices and Functional Reject Notices.
Example:
BGM+312+8XXX1234+11'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 41 / 56
Counter No Tag St MaxOcc Level Name
0030 5 DTM M 1 1 Date/time/period
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
DTM
C507 Date/time/period 010 M
2005 Date or time or period function code qualifier
1 M an..3 9 Processing date/time
2380 Date or time or period text 2 M an..17 Response Date/Time Date/Time of the outbound response notice from CBSA
2379 Date or time or period format code
3 M an..3 203 CCYYMMDDHHMM
Remark:
Example:
DTM+9:201208170900:203'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 42 / 56
Counter No Tag St MaxOcc Level Name
0060 6 RFF C 1 1 Secondary Business Number
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
RFF
C506 Reference 010 M
1153 Reference code qualifier 1 M an..3 AGO Sender's reference to the original message
1154 Reference identifier 2 C an..60 Secondary Business ID Secondary Business ID based on source document NOTE: this identifier cannot be provided when the client transmits a delete. In this case, CBSA will provide the reference ID supplied in the most recent EDI original /change request.
Remark:
Example:
RFF+AGO:SECONDARY BUSINESS ID'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 43 / 56
Counter No Tag St MaxOcc Level Name
0540 SG13 C 1 1 Processing Indicator
0550 7 RCS M 1 1 Requirements and conditions
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
RCS
7293 Sector area identification code qualifier
010 M an..3 11 Customs
Remark:
Required for syntax purposes (mandatory trigger segment)
Example:
RCS+11'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 44 / 56
Counter No Tag St MaxOcc Level Name
0540 SG13 C 1 1 Processing Indicator
0560 8 FTX C 1 2 Free text
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
FTX
4451 Text subject code qualifier 010 M an..3 AAO Error description (free text)
C108 Text literal 040 M
4440 Free text 4 M an..256 Data in error or BSO error text Note: for negative functional rejects only, the free text will be preceded with the Unique Message Reference Number from UNH 0062 with the format UMRN(1234)
Remark:
Example:
FTX+AAO+++DATA ELEMENT IN ERROR OR BSO TEXT'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 45 / 56
Counter No Tag St MaxOcc Level Name
0540 SG13 C 1 1 Processing Indicator
0580 9 GEI C 1 2 Processing information
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
GEI
9649 Processing information code qualifier
010 M an..3 5 Consignment type information
C012 Processing indicator 020 M
7365 Processing indicator description code
2 M an..3 CBSA Processing Indicator GEI indicator used by CBSA to determine the type of response being issued
1 Message content accepted Application Acknowledgement
2 Message content rejected with comment 14 Error message Functional or Application Reject
17 Message received Functional Acknowledgment
66 Message content accepted, with comments
Code 66 is used for ERC error code V67
Remark:
Example:
GEI+5+14'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 46 / 56
Counter No Tag St MaxOcc Level Name
0680 SG17 C 99 1 ERC-ERP
ERC-ERP segment will NOT appear on positive application response messages nor on any functional response messages (i.e. BGM response types 312 and 961)
0690 10 ERC M 1 1 Application error information
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
ERC
C901 Application error detail 010 M
9321 Application error code 1 M an..8 External error code Refer to ACROSS error message code table list at http://cbsa.gc.ca/eservices/error-erreur.pdf NOTE: warning error message V67 is provided with GEI code 66 as a second, separate message on the transaction, independent of either an accept or a reject message.
Remark:
Example:
ERC+W40'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 47 / 56
Counter No Tag St MaxOcc Level Name
0700 SG18 C 1 2 ERP
0710 11 ERP M 1 2 Error point details
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
ERP
C701 Error point details 010 M
1049 Message section code 1 M an..3 1 Heading section 2 Detail section
1052 Message item identifier 2 M an..35 Unique Message Reference Number from UNH 0062
1054 Message sub-item identifier
3 M n..6 20 – Administration 21 – Enforcement 22 – Conformance 28 – Batch Error 29 – Data Error
Remark:
Example:
ERP+2:UNIQUE MESSAGE REFERENCE NUMBER:22'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 48 / 56
Counter No Tag St MaxOcc Level Name
1810 12 UNS M 1 0 Section control
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNS
0081 Section identification 010 M a1 D Header/detail section separation
Remark:
Required for syntax purposes (mandatory trigger segment)
Example:
UNS+D'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 49 / 56
Counter No Tag St MaxOcc Level Name
5960 13 HYN M 1 0 Hierarchy information
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
HYN
7173 Hierarchy object code qualifier
010 M an..3 3 No hierarchy
Remark:
Required for syntax purposes (mandatory trigger segment)
Example:
HYN+3'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 50 / 56
Counter No Tag St MaxOcc Level Name
10360 14 UNS M 1 0 Section control
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNS
0081 Section identification 010 M a1 S Detail/summary section separation
Remark:
Required for syntax purposes (mandatory trigger segment)
Example:
UNS+S'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 51 / 56
Counter No Tag St MaxOcc Level Name
10390 15 UNT M 1 0 Message trailer
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNT
0074 Number of segments in the message
010 M n..6 Number of segments in message, includes UNH and UNT
0062 Message reference number 020 M an..14 Unique Reference Number assigned by the sender. (Same number as supplied in UNH 0062)
Remark:
Example:
UNT+13+1234'
Response Message - EDIFACT GOVCBR
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 52 / 56
Counter No Tag St MaxOcc Level Name
0000 16 UNE M 1 0 Functional group trailer
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNE
0060 Number of messages 010 M n..6 Number of messages (UNH-UNT) included in the functional group.
0048 Functional group reference number
020 M an..14 Unique Reference Number assigned by the sender. Same number as supplied in UNG 0048.
Remark:
Example:
UNE+1+9999'
No = Consecutive segment number St = Status MaxOcc = Maximum occurrence of the segment/group EDIFACT: M=Mandatory, C=Conditional Counter = Counter of segment/group within the standard User specific: R=Required, O=Optional, D=Dependent, Pos = Element position A=Advised, N=Not used Sep = Syntax separator
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 53 / 56
Counter No Tag St MaxOcc Level Name
0000 17 UNZ M 1 0 Interchange trailer
UN/EDIFACT Definitions CBSA Implementation
Tag Name Pos Place St Format Sep Usage / Remark
UNZ
0036 Interchange control count 010 M n..6 Number of functional groups (UNG-UNE) included in the interchange.
0020 Interchange control reference
020 M an..14 Unique reference number assigned by sender. Same number as supplied in UNB 0020.
Remark:
Example:
UNZ+1+99900000000001'
UN/EDIFACT GOVCBR 11B Customs Response Sample
Map
Sample Message Maps
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 55 / 56
Positive Functional Acknowledgement Notice Map:
UNA:+.?
UNB+UNOA:3+RCCECECPT+EMAN_XXXXXXX+130228:1111+16011++++++1
UNG+GOVCBR+CCR+EMAN_XXXXXXX+20130228:1111+5801+UN+D:11B
UNH+1+GOVCBR:D:11B:UN
BGM+961+8XXXESO950FUNCACKCCN1+11
DTM+9:201302281111:203
RFF+AGO:SECONDARY BUSINESS NUMBER
RCS+11
GEI+5+17
UNS+D
HYN+3
UNS+S
UNT+10+1
UNE+1+5801
UNZ+1+16011
Negative Functional Acknowledgement Notice Map:
UNA:+.?
UNB+UNOA:3+RCCECECPT+EMAN_XXXXXXX+130228:1119+16023++++++1
UNG+GOVCBR+CCR+EMAN_XXXXXXX+20130228:1119+5810+UN+D:11B
UNH+1+GOVCBR:D:11B:UN
BGM+961+8XXXESO950SYNTAXREJECT1+11
DTM+9:201302281119:203
RFF+AGO:SECONDARY BUSINESS NUMBER
RCS+11
FTX+AAO+++UMRN(MSGX1)SEGMENTLOCLINE50ELEM3225(2.1)ELEM TOO LONG
FTX+AAO+++UMRN(MSGX1)SEGMENTLOCLINE50ELEM3223(3.1)ELEM TOO LONG
GEI+5+14
UNS+D
HYN+3
UNS+S
UNT+12+1
UNE+1+5810
UNZ+1+16023
Application Acknowledgement Notice Map:
UNB+UNOA:3+RCCECECPT+EMAN_XXXXXXX+130228:1002+15944++++++1
UNG+GOVCBR+CCR+EMAN_XXXXXXX+20130228:1002+5761+UN+D:11B
UNH+1+GOVCBR:D:11B:UN
BGM+312+8XXXESO950HOUSEBILLCCN1+11
DTM+9:201302281001:203
RFF+AGO:SECONDARY BUSINESS NUMBER
RCS+11
GEI+5+1
UNS+D
HYN+3
UNS+S
UNT+10+1
UNE+1+5761
UNZ+1+15944
Sample Message Maps
Response Message - EDIFACT GOVCBR / GOVCBR Issue date: 2012-08-20 GOVCBR; 1.0; CBSA Generated by GEFEG.FX
Print date: 2012-08-20 Page: 56 / 56
Application Reject Notice Map:
UNB+UNOA:3+RCCECECPT+EMAN_XXXXXXX+130228:1152+16032++++++1
UNG+GOVCBR+CCR+EMAN_XXXXXXX+20130228:1152+5816+UN+D:11B
UNH+1+GOVCBR:D:11B:UN
BGM+313+8XXXESO950APPREJECT1+11
DTM+9:201302281151:203
RFF+AGO:SECONDARY BUSINESS NUMBER
RCS+11
FTX+AAO+++ZZ
GEI+5+14
ERC+294
ERP+2:MSGX1:22
UNS+D
HYN+3
UNS+S
UNT+13+1
UNE+1+5816
UNZ+1+16032