Introduction
The SANCRT message permits a commercial operator to apply to a national agency for the issue of a certificate, permit, authorization etc. regarding products to be imported or exported. It further permits the issuing authority to transmit to the applicant and to the exporting or importing country's relevant national authority, (e.g. U.S. Customs and Border Protection (CBP), Agriculture etc.) the details of the certificate, permit or authorization in respect of those products thus facilitating the import/export clearance of the consignment whilst ensuring that all certificate, permit, authorization requirements are met.
Notes
This Message Implementation Guideline (MIG) for the Electronic Visa System must be used to transmit Visa information to U.S. Customs and Border Protection (CBP).
Multiple SANCRT messages must be batched together in separate UNH-UNT message loops within the same interchange envelope (UNB/UNZ). U.S. Customs and Border Protection will accept a maximum of three thousand (3000) UNH-UNT message loops ( a complete Visa transaction) per interchange envelope.
UNG/UNE group header/trailer segments will not be supported in the Electronic Visa System.
Only one message type (e.g.: SANCRT) per interchange envelope is acceptable to CBP.
The SANCRT message incorporates all required data elements required by CBP and the Department of Commerce to satisfy the business data requirements of the electronic Visa program..
Data elements and segments shown as 'Conditional' in this MIG must be reported if specific conditions are stated for their inclusion. There are no 'Optional' segments.
| Pos. No. | Seg. ID | Name | Req. Des. | Max. Use | Group Repeat | Notes and Comments | |
|---|---|---|---|---|---|---|---|
| M | 0010 | UNH | Message Header | M | 1 | ||
| M | 0020 | BGM | Beginning of Message | M | 1 | ||
| Must Use | 0030 | DTM | Date/Time/Period | C | 1 | ||
| Must Use | 0040 | Segment Group 1: PNA-ADR | C | 3 | |||
| M | 0050 | PNA | Party Identification | M | 1 | ||
| Must Use | 0060 | ADR | Address | C | 1 | ||
| Must Use | 0070 | Segment Group 2: LIN-RFF-QTY | C | 5 | |||
| M | 0080 | LIN | Line Item | M | 1 | ||
| Must Use | 0090 | RFF | Reference | C | 5 | ||
| Must Use | 0100 | QTY | Quantity | C | 5 | ||
| 0110 | CNT | Control Total | C | 1 | |||
| M | 0120 | UNT | Message Trailer | M | 1 |
| Segment | UNH Message Header |
|---|---|
| Postion: | 0010 |
| Group: | |
| Level: | 0 |
| Usage: | Mandatory |
| Max Use: | 1 |
| Purpose: | A service segment starting and uniquely identifying a message. The message type code for the International movement of goods governmental regulatory message is SANCRT. |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | 0062 | Message Reference Number | M 1 an..14 | |
| Unique message reference assigned by the sender. This is a control number generated by the electronic Visa participant. |
||||
| M | S009 | Message Identifier | M 1 | |
| Identification of the type, version etc. of the message being interchanged. | ||||
| M | 0065 | Message Type Identifier | M an..6 | |
| Code identifying a type of message and assigned by its controlling agency. Always "SANCRT". SANCRT International movement of goods governmental regulatory message |
||||
| M | 0052 | Message Type Version Number | M an..3 | |
| Version number of a message type. Always "D". D Draft version/UN/EDIFACT Directory |
||||
| M | 0054 | Message Type Release Number | M an..3 | |
| Release number within the current message type version number (0052). Always "99A". 99A Release 1999 - A |
||||
| M | 0051 | Controlling Agency | M an..2 | |
| Code identifying the agency controlling the specification, maintenance and publication of the message type. Always "UN". UN UN/ECE/TRADE/WP.4 |
||||
| Segment | BGM Beginning of Message |
|---|---|
| Postion: | 0020 |
| Group: | |
| Level: | 0 |
| Usage: | Mandatory |
| Max Use: | 1 |
| Purpose: | A segment uniquely identifying the type of document (e.g. certificate of origin, export license, application for license), its function and the document reference number. |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: | |
| Notes: | This segment must be used to identify the Visa number and the action that this message represents: Cancellation, Addition or Replacement. |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| Must Use | C002 | Document/Message Name | C 1 | |
| Identification of a type of document/message by code or name. Code preferred. | ||||
| Must Use | 1001 | Document/Message Name, Coded | C an..3 | |
| Document/message identifier expressed in code. Always "811". 811 Export license |
||||
| Must Use | C106 | Document/Message Identification | C 1 | |
| Identification of document/message by its number and eventually its version or revision. | ||||
| Must Use | 1004 | Document/Message Number | C an..35 | |
| Reference number assigned to the document/message by the issuer. For the Electronic Visa System and the Visa document, always use the 9-character Visa number. The standard Visa number format is required for the Visa number. The Standard format is as follows: YCCNNNNNN where: Y = Year of export from country of origin CC = Country of origin NNNNNN = Document number Number must not duplicate within the year of issuance. This formula is subject to change in the future. |
||||
| 1225 | Message Function, Coded | C1 an..3 | ||
| Code indicating the function of the message. Only the following codes can be used in the Electronic Visa System: 1 - Cancellation. This code indicates that the transmitter wishes to cancel Visa data that has already been accepted by CBP. 2 - Add. This code indicates that the current Visa transaction is the initial transmission. 5 - Replace. This code indicates that the Visa transaction in the current message is meant to replace Visa data that is already on file in the CBP system. Note: Visas on file in the CBP system in a "Cancel" status, cannot be replaced or added. A canceled Visa is permanently inactivated. |
||||
| Segment | DTM Date/Time/Period |
|---|---|
| Postion: | 0030 |
| Group: | |
| Level: | 0 |
| Usage: | Conditional (Required) |
| Max Use: | 1 |
| Purpose: | A segment identifying dates relevant to the document specified in the above BGM (e.g. date of issue, the validity period, the date on which license is available for inspection, the date goods are available for inspection, the authentication date, time of the document). |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: | |
| Notes: | This segment is required to report the effective date of the Visa identified in the BGM segment, C106, sub-element 1004. To specify a Visa effective date, data element 2005 must equal "7", data element 2380 must equal. |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | C507 | Date/Time/Period | M 1 | |
| Date and/or time, or period relevant to the specified date/time/period type. | ||||
| M | 2005 | Date/Time/Period Qualifier | M an..3 | |
| Code giving specific meaning to a date, time or period. This data element reports the effective date of the Visa. Always "7". 7 Effective date/time |
||||
| Must Use | 2380 | Date/Time/Period | C an..35 | |
| The value of a date, a date and time, a time or of a period in a specified representation. Format "CCYYMMDD". |
||||
| Must Use | 2379 | Date/Time/Period Format Qualifier | C an..3 | |
| Specification of the representation of a date, a date and time or of a period. Always use "102". 102 CCYYMMDD |
||||
| Segment | PNA Party Identification |
|---|---|
| Postion: | 0050 (Trigger Segment) |
| Group: | Segment Group 1 (Party Identification) Conditional (Required) |
| Level: | 1 |
| Usage: | Mandatory |
| Max Use: | 1 |
| Purpose: | A segment identifying the name or other references of a party associated with the message (e.g. importer, consignor, consignee, exporter, applicant, transport company, manufacturer, company to which product is to be transferred, certificate issuing authority, authenticating party). |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: | |
| Notes: | A maximum of three (3) PNA loops may be used to provide identification information. For the Electronic Visa System, this segment references the official company name of the Manufacturer, Buyer or Exporter associated with the Visa. Personnel names are not acceptable. |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | 3035 | Party Qualifier | M 1 an..3 | |
| Code giving specific meaning to a party. Document Party Role. Providing data on party qualifier 'EX' - Exporter, by the participant is optional. U.S. Customs and Border Protection (CBP) requires the participant to report at a minimum, 'MF' - manufacturer information. BY Buyer EX Exporter MF Manufacturer of goods |
||||
| Must Use | C206 | Identification Number | C 1 | |
| The identification of an object. | ||||
| M | 7402 | Identity Number | M an..35 | |
| The number given to an object for its unique identification. CBP Manufacturer's Identification Number (MID Number) for Manufacturer information is required. Use CBP formula to create MID. Importer number for Buyer ID. Manufacturer Country ID for export information |
||||
| C082 | Party Identification Details | C 1 | ||
| Identification of a transaction party by code. Not Used. |
||||
| 3403 | Name Type, Coded | C 1 an..3 | ||
| Code for type of name such as official name, alias. Always "9". 9 Company name |
||||
| 3397 | Name Status, Coded | C 1 an..3 | ||
| To specify the status of a name (such as current name). Not Used. |
||||
| Must Use | C816 | Name Component Details | C 1 | |
| To specify a name component. | ||||
| M | 3405 | Name Component Qualifier | M an..3 | |
| To identify the type of name component. This data element requires the complete company name of the party identified in data element 7402 of composite C206. 10 Whole name |
||||
| Must Use | 3398 | Name Component | C an..70 | |
| Part of party name such as family name or given name. Complete, legal (Company) name of Manufacturer, Exporter or Buyer. |
||||
| Segment | ADR Address |
|---|---|
| Postion: | 0060 |
| Group: | Segment Group 1 (Party Identification) Conditional (Required) |
| Level: | 2 |
| Usage: | Conditional (Required) |
| Max Use: | 1 |
| Purpose: | A segment identifying the address of a party associated with the message (e.g. importer, consignor, consignee, exporter, applicant, transport company, manufacturer, company to which product is to be transferred, certificate issuing authority, authenticating party). |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: | |
| Notes: | This segment is not required if data element 3035 - Party qualifier - in the PNA segment at position 50 equals "EX". |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| Must Use | C817 | Address Usage | C 1 | |
| To describe the usage of an address. Always "2". |
||||
| Must Use | 3299 | Address Purpose, Coded | C an..3 | |
| To specify the purpose of the address. Use of code "2" in this data element implies the contact address of the business enterprise (e.g., manufacturer, exporter, buyer). CBP will not accept a Post Office Box Number, "In Care Of (c/o)", a forwarding or personal address. 2 Contact address |
||||
| C090 | Address Detail | C 1 | ||
| To specify the details of an address. | ||||
| M | 3477 | Address Format, Coded | M an..3 | |
| To specify the content of the various address components. Always "5". 5 Unstructured address |
||||
| M | 3286 | Address Component | M an..70 | |
| To specify a component of an address. Company Address. |
||||
| 3286 | Address Component | C an..70 | ||
| To specify a component of an address. Company Address (continued)- For the Electronic Visa System, use up to 35 bytes. |
||||
| Must Use | 3164 | City Name | C 1 an..35 | |
| Name of a City (a town, a village)for addressing purposes. Legal name of the City. |
||||
| Must Use | 3251 | Post Code Identification | C 1 an..9 | |
| Code defining postal zones or addresses. Postal codes such as Zip Codes, Province or Regional codes, Prefecture or Zone Codes must NOT include hyphens or other non character punctuation. |
||||
| Must Use | 3207 | Country, Coded | C 1 an..3 | |
| Identification of the name of a country or other geographical entity as specified in ISO 3166. Use only the two (2) character International Standards Organization (ISO) code for the Country. |
||||
| C819 | Country Sub-Entity Details | C 1 | ||
| To specify a part of a country (e.g. county or part of a city). Country sub-entity includes, but not limited to Proinces, Regions, Prefectures or Zones. |
||||
| 3229 | Country Sub-Entity Identification | C an..9 | ||
| Identification of the name of sub-entitie (state, province) defined by appropriate governmental agencies. When data element 3035 of the PNA segment in position 50 equals "BY" - Buyer, then this data element must identify the State in the buyer's address. |
||||
| Segment | LIN Line Item |
|---|---|
| Postion: | 0080 (Trigger Segment) |
| Group: | Segment Group 2 (Line Item) Conditional (Required) |
| Level: | 1 |
| Usage: | Mandatory |
| Max Use: | 1 |
| Purpose: | A segment identifying product item details for a line on the message. |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | 1082 | Line Item Number | M 1 an..6 | |
| Serial number designating each separate item within a series of articles. This data element must begin with a value of q, subsequently incremented by +1 as needed within each Visa transaction. |
||||
| Segment | RFF Reference |
|---|---|
| Postion: | 0090 |
| Group: | Segment Group 2 (Line Item) Conditional (Required) |
| Level: | 2 |
| Usage: | Conditional (Required) |
| Max Use: | 5 |
| Purpose: | To specify a reference. |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: | |
| Notes: | The RFF segment is used to identify the 'Article' (category) codes. A maximum of five (5) RFF segments are allowed in each |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | C506 | Reference | M 1 | |
| Identification of a reference. | ||||
| M | 1153 | Reference Qualifier | M an..3 | |
| Code giving specific meaning to a reference segment or a reference number. Always "ABU". ABU Article number |
||||
| Must Use | 1154 | Reference Number | C an..35 | |
| Identification number the nature and function of which can be qualified by an entry in data element 1153 Reference qualifier. For the USCS Electronic Visa System and the Visa document, use the category number with the Standard format. Category numbers are 3-5 character identifiers with the first three (3) positions numeric. The fourth (4th) and fifth (5th) positions can be alpha, numeric or combinations thereof . No leading spaces will be supported. Examples of acceptable formats are : NNN, NNNA, NNNAA, NNNN, NNNNN, NNNAN, NNNNA. |
||||
| Segment | QTY Quantity |
|---|---|
| Postion: | 0100 |
| Group: | Segment Group 2 (Line Item) Conditional (Required) |
| Level: | 2 |
| Usage: | Conditional (Required) |
| Max Use: | 5 |
| Purpose: | A segment identifying quantity details relevant to the product item (e.g. quantity manufactured, quantity in commercial units, quantity in control units, quantity in quota units, quantity shipped). |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | C186 | Quantity Details | M 1 | |
| Quantity information in a transaction, qualified when relevant. | ||||
| M | 6063 | Quantity Qualifier | M an..3 | |
| Code giving specific meaning to a quantity. Always "346". 346 Number of units |
||||
| M | 6060 | Quantity | M n..15 | |
| Numeric value of a quanity. This data element requires a numeric value in whole numbers only. No decimals or fractional values are accepted. The Electronic Visa System will accept a maximum of nine (9) whole number digits. |
||||
| Must Use | 6411 | Measure Unit Qualifier | C an..3 | |
| Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or other quantity is expressed. The electronic Visa application will support the following units of measure: DOZ Dozen |
||||
| Segment | CNT Control Total |
|---|---|
| Postion: | 0110 |
| Group: | |
| Level: | 0 |
| Usage: | Conditional (Optional) |
| Max Use: | 1 |
| Purpose: | To provide control total. |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: | |
| Notes: | This CNT segment must provide the nunber of LIN segments associated with a Visa transaction. |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | C270 | Control | M 1 | |
| Control totla for checking integrity of a message or part of a message. | ||||
| M | 6069 | Control Qualifier | M an..3 | |
| Determines the source data elements in the message which forms the basis for 6066 Control value. Always "5". 5 Number of CBP item detail lines |
||||
| M | 6066 | Control Value | M n..18 | |
| Value obtained from summing the values specified by the Control Qualifier throughout the message (Hash total). This data element must reflect the total number of LIN Loop segments in this Visa transaction. |
||||
| Segment | UNT Message Trailer |
|---|---|
| Postion: | 0120 |
| Group: | |
| Level: | 0 |
| Usage: | Mandatory |
| Max Use: | 1 |
| Purpose: | A service segment ending a message, giving the total number of segments in the message and the control reference number of the message. |
| Dependency Notes: | |
| Semantic Notes: | |
| Comments: |
Data Element Summary
| Data Element | Component Element | Name | Attributes | |
|---|---|---|---|---|
| M | 0074 | Number of Segments in a Message | M1 n..6 | |
| Control count of number of segments in a message. | ||||
| M | 0062 | Message Reference Number | M1 an..14 | |
| Unique message reference assigned by the sender. | ||||
SANCRT4 (D.99A), November 28, 2001