CUSRES Customs response

TBG4 Customs

This Customs Response Message (CUSRES) permits the transfer of data from a customs administration:

- to acknowledge the receipt of the message - to indicate whether the information received is correct or if there are errors (i.e. accepted without errors, accepted with errors, rejected, etc.) - to inform the sender of the status of the customs declaration (i.e. goods released, goods for examination, documents required, etc.) - to transmit additional information as agreed between parties (i.e. tax information, quantity information, etc.) - to respond to batched messages (i.e. CUSDEC, CUSCAR, CUSREP, CUSEXP).

Note: this message is not meant to replace the functionality of the CONTRL message.

Header

Position
Segment
Name
Max use
  1. 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 21A 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.
  2. A segment identifying the type and the reference number of the message to which the CUSRES is a response.

  3. A segment identifying the relevant dates and times in the message. For example, payment date.

  4. A segment stating information in unsolicited clear text.

  5. A segment to specify any means of transport that is related to all information at the lower level of the message.

    040 D5(040,030) If first, then all
  6. A segment to identify a country and/or place and/or location information related to the whole message.

  7. A segment identifying the various customs processing indicators. For example, cargo released, cargo held, examination required, earlier message accepted or rejected, etc.

  8. A segment identifying equipment initials and numbers required to identify a shipment, covering the whole message, e.g. to indicate the container number that Customs wants to examine.

  9. Segment group 1
    Repeat 99
    1. A segment to identify the name and/or address of the party related to all information at the lower level of the message. For example, the importer.

    2. Segment group 2
      Repeat 9
      1. A segment to identify a person or a department to whom communication should be directed.

      2. A segment to identify a communication number of a department or a person to whom communication should be directed.

  10. Segment group 3
    Repeat 999
    1. A segment identifying references (e.g. manifest number).

    2. A segment identifying a date related to the preceding RFF.

    3. A segment identifying a location related to the preceding RFF.

  11. Segment group 4
    Repeat 99999
    1. A segment identifying the location of an application error within the referenced message.

    2. A segment to provide the references related to the application error.

    3. A segment identifying the type of application errors within a message.

    4. A segment to provide explanation and/or supplementary information related to the specified application error.

  12. Segment group 5
    Repeat 99
    1. A segment identifying the tax and/or duty and/or fee type, rate and base totals for all customs declarations.

    2. A segment to identify a tax and/or duty and/or fee amount related to TAX.

    3. A segment identifying method of payment.

  13. Segment group 6
    Repeat 99999
    1. A segment to identify the master bill number reported in a multi-consignment message. This segment can also be used to identify the Customs declaration where the CUSRES is responding to multiple declarations.

    2. A segment identifying number and type of packages.

    3. A segment identifying a particular reference, e.g. house of bill number, master bill number.

    4. A segment identifying marking and labels on individual shipping or packing units.

    5. A segment to provide the goods description.

    6. A segment to identify any means of transport that is related to a part of the information in the message. For example, when one CUSRES message contains more than one release note.

      040 D5(040,030) If first, then all
    7. A segment identifying the places relevant to the item, which is different from the places identified at header level. For example, customs house of entry, warehouse, etc.

    8. A segment identifying necessary dates.

    9. A segment identifying customs processing indicator at item level.

    10. Segment identifying various measurement values.

    11. A segment identifying equipment initials and numbers.

    12. Segment group 7
      Repeat 9
      1. A segment identifying information about a party related only to a part of the message. For example, in a message with several release notes or in a message related to several declarations, a customs agent and the person responsible for the information.

      2. Segment group 8
        Repeat 9
        1. A segment to identify a person or a department to whom communication should be directed.

        2. A segment to identify a communication number of a department or a person to whom communication should be directed.

    13. Segment group 9
      Repeat 99
      1. A segment identifying the monetary amount.

      2. Segment group 10
        Repeat 9
        1. A segment identifying currencies and the rate of exchange for a monetary amount identified within this group.

        2. A segment identifying a date related to the rate of exchange.

    14. Segment group 11
      Repeat 99
      1. A segment identifying tax/duty/fee related to a single customs declaration.

      2. A segment identifying tax/duty/fee amounts related to TAX.

      3. A segment identifying the methods of payment related to TAX.

    15. Segment group 12
      Repeat 9999
      1. A segment identifying goods in terms of customs identities, status and intended use.

      2. A segment to specify the goods description.

      3. Segment group 13
        Repeat 999999
        1. A segment identifying the tax and/or duty and/or fee type, rate and base for customs item amounts.

        2. A segment identifying a tax and/or duty and/or fee amount related to TAX.

        3. A segment identifying method of payment.

        4. A segment to identify measurements related to the calculation of the customs duties.

        5. A segment to identify reference numbers related to the tax calculations (e.g. reference number for VAT free allowance).

    16. Segment group 14
      Repeat 9999
      1. A segment identifying the location of an application error.

      2. A segment to provide the references related to the application error.

      3. A segment identifying the type of application errors.

      4. A segment to provide explanation and/or supplementary information related to the specified application error.

  14. A segment to identify control totals.

  15. Segment group 15
    Repeat 9
    1. A segment containing the result of the algorithm permitting the verification of the authenticity of the sender and the integrity of the data.

    2. A segment identifying a date associated with the preceding AUT.

  16. A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.