|
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4. Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued. The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags. |
| Message Type: | CUSRES |
|---|---|
| Version: | D |
| Release: | 95A |
| Contr. Agency: | UN |
| Status: | 2 |
| Revision: | 2 |
| Date: | 95-01-06 |
| SOURCE: | Joint development by the Pan American EDIFACT Board and the Western European EDIFACT Board. |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Customs response message (CUSRES) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
This Customs Response Message (CUSRES) permits the transfer of data from a customs administration to the sender of customs data. It may also be used by Customs to transmit electronic customs clearance of goods.
This Message may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.
It is envisaged that this message will allow a customs administration to respond to single or batched customs messages or give information to approved part(y)s; for example, errors in data, release/clearance notifications, etc. It is recognized that this message may be used by other parties to respond to customs messages.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Customs response message is CUSRES.
Note: Customs response messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | CUSRES |
| 0052 | D | |
| 0054 | 95A | |
| 0051 | UN |
A segment identifying the message type, its reference, date and the identification of a reference to which the CUSRES is a response.
A segment identifying the parties relevant to the message. For example, agent, importer, etc.
A segment identifying the places relevant to the message. For example, port of entry, location of goods, etc.
A segment identifying the relevant dates and times in the message. For example, payment date, date of arrival.
A segment identifying the various customs processing indicators. For example, cargo released, cargo held, examination required, earlier message accepted or rejected, etc.
A segment stating information in unsolicited clear text.
A segment identifying equipment initials and numbers required to identify a shipment, covering the whole message.
A group of segments identifying the location and specifics of an application error condition within a message to which the CUSRES is a response.
A segment identifying the location of an application error within another message.
A segment identifying the type of application errors within a message.
A group of segments identifying particular shipping or packing units reported in an earlier declaration which are now subject to customs action (examination, release, etc).
A segment identifying the number and type of manifested units that are being referenced.
A group of segments identifying markings and labels, and describing the goods related to PCI.
A segment identifying markings and labels on individual shipping or packing units.
A segment identifying packages, related to PCI, in narrative form.
A segment identifying totals for tax, fees, and duties declared and due for payment, following the computation by customs.
A segment identifying tax/duty/fee type, base and rate due for payment.
A segment identifying tax/duty/fee amounts due for payment (e.g. total tax amount).
A segment identifying an indicator related to the preceding TAX (e.g. method of payment indicator).
A group of segments identifying a reference and/or the item taxes, fees and duties (with the associated details), following their computation by customs based on data provided by the declarant.
A segment identifying a particular reference.
A segment identifying a date related to the preceding RFF.
Segment identifying various measurement values where these are required for the computation of duties/taxes/fees due.
A segment identifying equipment initials and numbers required to identify a shipment related to a declaration identified in the preceding RFF.
A group of segments identifying the monetary amount, currencies and the rate of exchange against which duties, taxes or fees are being computed.
A segment identifying the monetary amount against which any duty, tax, or fee is being computed.
A segment identifying currencies and the rate of exchange for a monetary amount identified within this group.
A group of segments identifying the customs amounts for duties, taxes and fees, following computation by customs.
A segment identifying the tax/duty/fee type, rate and base for customs item amounts.
A segment identifying a tax/duty/fee amount related to the TAX.
A segment identifying an indicator related to the preceding TAX (e.g. method of payment indicator).
A group of segments identifying documentary requirements where they are needed as supporting information for customs processing.
A segment identifying a document required as supporting information by customs.
A segment identifying a date related to the preceding DOC.
A segment identifying a location related to the preceding DOC.
A segment permitting the verification of the authenticity of the sender and the integrity of the data.
A segment containing the result of the algorithm permitting the verification of the authenticity of the sender and the integrity of the data.
A segment identifying a date associated with the preceding AUT.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| AUT | Authentication result | |
| BGM | Beginning of message | |
| CUX | Currencies | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| EQD | Equipment details | |
| ERC | Application error information | |
| ERP | Error point details | |
| FTX | Free text | |
| GIS | General indicator | |
| LOC | Place/location identification | |
| MEA | Measurements | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| PAC | Package | |
|
PCI | Package identification |
| RFF | Reference | |
| TAX | Duty/tax/fee details | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─NAD Name and address | ×5 | (C) |
| ├─LOC Place/location identification | ×5 | (C) |
| ├─DTM Date/time/period | ×7 | (C) |
| ├─GIS General indicator | ×10 | (C) |
| ├─FTX Free text | ×5 | (C) |
| ├─EQD Equipment details | ×999 | (C) |
| ├─Segment Group 1 | ×50 | (C) |
| │─├─ERP Error point details | ×1 | (M) |
| │─└─ERC Application error information | ×50 | (C) |
| ├─Segment Group 2 | ×999 | (C) |
| │─├─PAC Package | ×1 | (M) |
| │─└─Segment Group 3 | ×1 | (C) |
| │───├─PCI Package identification | ×1 | (M) |
| │───└─FTX Free text | ×1 | (C) |
| ├─Segment Group 4 | ×50 | (C) |
| │─├─TAX Duty/tax/fee details | ×1 | (M) |
| │─├─MOA Monetary amount | ×2 | (C) |
| │─└─GIS General indicator | ×1 | (C) |
| ├─Segment Group 5 | ×9999 | (M) |
| │─├─RFF Reference | ×1 | (M) |
| │─├─DTM Date/time/period | ×1 | (C) |
| │─├─MEA Measurements | ×20 | (C) |
| │─├─EQD Equipment details | ×99 | (C) |
| │─├─Segment Group 6 | ×10 | (C) |
| │─│─├─MOA Monetary amount | ×1 | (M) |
| │─│─└─CUX Currencies | ×1 | (C) |
| │─└─Segment Group 7 | ×20 | (C) |
| │───├─TAX Duty/tax/fee details | ×1 | (M) |
| │───├─MOA Monetary amount | ×2 | (C) |
| │───└─GIS General indicator | ×1 | (C) |
| ├─Segment Group 8 | ×5 | (C) |
| │─├─DOC Document/message details | ×1 | (M) |
| │─├─DTM Date/time/period | ×2 | (C) |
| │─└─LOC Place/location identification | ×1 | (C) |
| ├─Segment Group 9 | ×1 | (C) |
| │─├─AUT Authentication result | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |
