Check-list for declaring in the New Computerised Transit System, NCTS

On this page we have compiled comprehensive tips that may be useful when declaring in the NCTS.

Follow the steps below to ensure that you declare correctly.

Check-list

1. Follow the declaration guide

Follow the declaration guide for your type of transit procedure.

If you intend to start a transit operation directly from a warehouse, as an authorised consignor, this is referred to as transit under the simplified procedure. You indicate this by declaring your status as an authorised consignor in the transit movement (see data element 12 12 000 000 – Authorisation).

If you intend to submit a transit movement to be started from a customs office, this is referred to as transit under the normal procedure. In this case, you do not specify an authorisation code under data element 12 12 000 000 – Authorisation.

Declaration guide for transit, NCTS

2. Await a response message

For cases to be initiated in a simplified procedure (see description above), wait for response message IE029 (release notification) before dispatching the goods.

For cases to be initiated at a customs office and where a previous export declaration has been specified in the transit movement, wait for message IE028, which provides the MRN number.

For cases to be initiated at customs offices where a previous export declaration has not been specified, no MRN number will be obtained before the declaration and goods are presented at the customs office of departure. Only await message IE928 (Positive acknowledgement).

Transit declaration procedure – Simplified procedure

Procedure for transit declarations – Normal procedure

Procedure for reporting incidents during transit

3. Have you received an error message?

Have you received an error message even though you followed the declaration guide? In the troubleshooting section below, you will find tips to help you understand and interpret various error messages.

Troubleshooting

If you have submitted a declaration in NCTS and received an error code, the lists below can help you interpret the codes.

Sample error message

Example of an error message when a valid EORI number has been incorrectly entered together with the name and address in IE015. In this example, condition C0250 is violated.

Responsible for the procedure

<errorPointer>/CC015C/HolderOfTheTransitProcedure/name</errorPointer

<originalAttributeValue>SuperNovix AB</originalAttributeValue>

</FunctionalError>

<errorPointer>/CC015C/HolderOfTheTransitProcedure/Address</errorPointer

</FunctionalError>

‘Error reasons’ for error messages

Error reasons for error messages

Error reasons for error messages	Category	External description
BR1513A	Authorisation	Verification of authorisations for IE015 and IE013. Conditions: The authorisation number provided in ‘authorisation/referenceNumber’ is registered The EORI provided in /holderOfTheTransitProcedure/identificationNumber is associated with the authorisation The authorisation concerns ‘Departure’ The type code of the authorisation is ‘C521’ The customs office number indicated in /customsOfficeOfDeparture/referenceNumber is associated with the authorisation
BR1513B	Authorisation	Verification of authorisations for IE015 and IE013. Conditions: /consignment/locationOfGoods/typeOfLocation: "B" /consignment/locationOfGoods/qualifierOfIdentification: "X" The reference number /consignment/locationOfGoods/additionalIdentifier is associated with the authorisation
BR007A	Authorisation	Verification of authorisation for IE077. Conditions: The authorisation number provided in /consignment/locationOfGoods/additionalIdentifier is registered The EORI provided in CC007C/traderAtDestination/identificationNumber is associated with the authorisation The authorisation concerns ‘Destination’ The type code of the authorisation is ‘C522’ The value provided in CC007C/customsOfficeOfDestination(Actual)/referenceNumber is associated with the authorisation
BR007B	Location of goods code	Verification of location of goods code. Conditions: CC007C/consignment/locationOfGoods/typeOfLocation: "B" CC007C/consignment/locationOfGoods/qualifierOfIdentification: "X" The value provided in CC007C/consignment/locationOfGoods/additionalIdentifier is associated with the relevant authorisation
SE7142	Enquiry procedure	Verification of whether an enquiry procedure has been initiated prior to registering the arrival of the goods. If IE007 is sent after the initiation of an enquiry procedure, IE007 will be rejected with IE057. Error pointer till IE007 och error code 92: ‘Message out of sequence’
BR20101	Security	The field may only contain 0 or 2 in NCTS P6

Functional error codes

Functional error codes
Error code (errorCode)	Name (EN)	Description (EN)
12	Codelist violation	Value of an element in a message is outside the predefined set of values or not part of the applicable business/technical code list. This type of error is applicable to all elements with code values, so it is also applicable to those elements that identify a message type.
13	Condition violation (Missing)	A mandatory/required element is missing in the received data following the validation of Rule or Condition , e.g. a required element is not present.
14	Rule violation
15	Condition violation (Not allowed)	An element is not allowed to have a value due to the following two reasons: The element is not allowed to be present according to some additional condition, e.g. if type of packages has the value 'UNPACKED' then number of package can not have a value (condition C0060 ).
26	Duplicate Message ID	The same interchange is received again. Duplication is detected by reception of a message identifier that has already been received.
50	Transitional constraint violation	An element is not valid (value, format or repetitions) according to a Transitional Constraint [Downgrade & Upgrade Conversion].
51	EDI violation post downgrade	An error reported by Convertor in the Technical Message Structure (EDIFACT level) validation on the downgraded message (ECS-P2/NCTS-P4 message) [Downgrade Conversion from NCTS-P5/AES to NCTS-P4/ECS-P2].
52	Functional violation post downgrade	An error reported by Convertor in the Functional Message Structure (ECS-P2/NCTS-P4 XML or Rules/Conditions) validation on the downgraded message (ECS-P2/NCTS-P4 message) [Downgrade Conversion from NCTS-P5/AES to NCTS-P4/ECS-P2].
90	Unknown MRN
92	Message out of sequence
93	Invalid MRN	The structure of the MRN is not conform specifications.

Error codes for guarantees in Release 5 of the NCTS

Error codes for guarantees in Release 5 of the NCTS
Error code	Name
G01	Guarantee does not exist
G02	Guarantee exists, but not valid
G03	Access code not valid
G04	Holder of Guarantee is not equal to Holder of Transit procedure in declaration
G05	Individual guarantee voucher already used
G06	Use restriction: No suspended goods
G08	Not valid for Country of Transit or Country of Destination
G09	Reference/Guarantee amounts NOT sufficient
G10	Individual guarantee by Guarantor already used
G11	Customs Office of Departure and Customs Office of Destination do not correspond (Guarantee type ‘2’)
G12	'Declared commodity code' and 'Commodity code' in guarantee do not match
G13	The 'GRN' and the 'Guarantee type' do not match