PLDA customs errors

  1. D Tarbel 014 Produced Documents Missing
  2. Het eerste karakter van de aanvullende nationale code Taric mag niet 2,3, 4, 6, 7, 8, 9, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O of P zijn
  3. Taric-code bestaat niet 3919103110
  4. Write off electronical freight list
  5. Het bijgevoegd document Y040 moet verplicht in vak 44 aangegeven worden
  6. WO 002: customs event is niet gekend
  7. D Goods not Arrived: De goederen werden nog niet aangeboden, vandaar kan de aangifte niet aanvaard worden
  8. WO 006: onbekende goederenlijn
  9. D Reuse of LRN not Authorized: De LRN moet uniek zijn, tenzij voor een onvolledige/vereenvoudigde aangifte en zijn aanvullende aangifte en voor CIV gegevens en de overeenkomstige globalisatieaangifte
  10. ITEM_0024: Nettogewicht mag niet groter zijn dan brutogewicht
  11. BTW nr geadresseerde – DECL_EO_0047 (identifcationCodeType) is niet correct
  12. Invalid Goods location code
  13. Missing
  14. Package type is mandatory
  15. Vak 36 eerste positie is vereist of tweede en derde positie is vereist
  16. Invalid additional information type code
  17. VAK 17 a is verplicht
  18. Bij een aangifte IM7, moet er een additionele informatie zijn van type PLDA-DTO-1 of PLDA-DTO-2
  19. Vak 8 mag niet ingevuld worden
  20. Ongeldige combinatie van regeling, aanvullende code, nationale aanvullende codes, betaalwijze, betaalwijze BTW en borg
  21. Field ‘article’ is mandatory
  22. Excemption code 0600 for excises
  23. Fill in ‘quota’
  24. Het document C601 (vergunning actieve veredeling) ontbreekt in vak 44
  25. Het document 3046, 3047, 3050, 3051 of 3053 (nationale code vergunning actieve veredeling) ontbreekt in vak 44
  26. Invalid payment method code
  27. De geadresseerde heeft geen toestemming tot verlegging van betaling BTW
  28. Supplementary_unit_missing: Code statistische eenheid is niet correct. NAR is vereist
  29. Vak 37 (1e 2 posities) gelijk aan 71 en de aanvullende code 7A1 of 7A3 werd niet vermeld
  30. Changes customs bonded warehouse from 1 May 2016
  31. Invalid Produced document type : 3046
  32. Invalid Produced document type : 3047
  33. Invalid Produced document: 3036
  34. Lenght must be higher than 14
  35. Codes D and E are rejected when procedureComm1 = 71 or 78. 13

1. Cannot open a company in Logiqstar.

Symptom

When I try to open a company in Logiqstar by running the Microsoft Dynamics NAV Windows client, the following error message appears

Cause

The user that is trying to log on is not assigned to any department.

Solution

Ensure that the user that is trying to log on is assigned to a financial company and department in the Department Users window.

2 When picking goods from stock, not all inventory properties are available as filters in the picking list.

Symptom

When I pick goods from an IMS task, the Picking List window opens where, on the Filters FastTab, I should be able to use inventory properties as filters. However, some of the inventory properties are not available there.

Cause

To be able to use a general or supplementary inventory property as a filter in the Picking List window, such a property must have the Picking Filter check box selected.

Solution

Open the Inventory Property Setup window, select the required combination of commodity group and inventory type, and for inventory properties that you want to use as filters in the Picking List window, select the Picking Filter check box.

3 The order management search functionality cannot find records by container number, even though they are available in the database

Symptom

When I try to search the Order Management System application area to find operational orders by container number, the search results do not show any found operational orders.

Cause

Order management Search Setup is incorrect or incomplete.

Solution

In the Order Mgt. Search Setup window, ensure that the appropriate tables which are used for searching values in OMS are added to the order management search setup and that in those tables the required fields are set up for search. For this case, ensure that the following tables are added:

  • Table 2067192 (Oper. Order Task Container)
  • Table 2067193 (Oper. Order Task Goods)

For each of these tables, choose Search Fields on the Home tab in the Order Mgt. Search Setup window, and ensure that the Container No. field is added as a search field.

4 The required contact is not available in the list when trying to specify the customer in the Order Registration task

Symptom

When I try to specify the customer in the Code field on the Customer FastTab within the Contacts FastTab in the Order Registration task, the required operational address is not available in the list to choose from.

Cause

Business relations are not set up properly.

Whenever you register information about contacts on an operational task on the Contacts FastTab, the operational addresses that will be available for selection when you choose the Code field will only be operational addresses that are linked to the business relations code which is currently set up for that contact entity in the Business Relationship Setup window.

For example, for the contact entity Customer on the Order Registration task, when you choose the Code field, you will see the list of operational addresses that on their operational address card are linked to the business relations code which is currently specified in the Customer field on the Business Relations Setup window.

Solution

To ensure that the required operational address is visible in the list when you want to specify a customer in the Order Registration task, ensure that the corresponding business relations are set up properly. You can check the following:

  • Open the Business Relations Setup window, and ensure the Customer field is filled in.
  • Open the card of the required operational address, and in the Operational Address Card window, on the Navigate tab, choose Business Relations. In the Address Bus. Relations window that is open, ensure that there is a line with the required contact and for that contact, the Business Relation Code is filled in with value which is set up for customer in the Business Relations Setup window.

5 After posting a Transformation Confirmation task, the expected inventory ledger entries are not created.

Symptom

After a Transformation Confirmation task has been posted without errors, inventory ledger entries are not created.

Cause

If the changes that you make on goods lines in the Transformation Confirmation task between the pick and put lines are made in fields that are not set up as inventory properties, inventory ledger entries will not be created after posting the task.

Solution

To have inventory ledger entries created after posting a Transformation Confirmation task, ensure that the changes between the pick and put lines are made in the field(s) set up as inventory properties in the Inventory Property Setup.

6 Cannot attach an external document to an operational task using Drag ‘n’ Drop

Symptom

I cannot attach a document file to an operational task using the Drag ‘n’ Drop functionality because there is an error message in the Link Documents FactBox.

Cause

The Drag and Drop add-in for Logiqstar is not installed or not configured properly.

Solution

To be able to use the Drag and Drop functionality to attach files to operational tasks, ensure that the Drag and Drop is installed and configured: run the Logiqstar DragAndDrop for Microsoft Dynamics NAV 2016.msi file from the Logiqstar installation package to install the Drag and Drop add-in.

After you install the Drag and Drop add-in, open the Microsoft Dynamics NAV Windows client, and, in the Control Add-ins window, check that the Drag and Drop control add-in entry has been created.

7 The list of operational orders is empty or does not show the required orders

Symptom

When I open the Operational Orders window, the list is empty or the required operational orders are not displayed.

Cause

When operational orders are created, they are created for a specific department. If a user is assigned to a department which is different from the department an operational order was created for, such a user will not be able to see this operational order.

note: If the user has the permissions of a SUPER user, he will be able to see all operational order regardless of the department they were created for.

Solution

Ensure that the user is assigned to the same department to which the operational order that he is trying to access is linked to.

8 Cannot run an operational task in an operational order due dependency on the status of another operational task.

Symptom

When I try to run an operational task, an error message appears that another operational task must have a certain status.

Cause

In Logiqstar, you can set up run dependencies for operational tasks. These run dependencies allow you to set up an operational task in such a way that the user will be able to run it only after another task has reached a certain status.

Solution

For the operational task that you cannot run, check whether it has run dependencies. In the Operational Order Tasks window, choose Run Dependencies. If there is a run dependency, ensure that the related task has reached the specified status before you run the current operational task.

  

PLDA customs errors

The aim of this document is to help our LQS customers to understand and solve the customs errors received from customs authorities. This document will help you to clarify many of those customs errors. However, please do not hesitate to contact us in case you need any further assistance.

D_TARBEL_014_PRODUCED_DOCUMENTS_MISSING

This customs error means that there are produced documents missing in box 44. Sometimes the error will mention which produced document on which exact tariff line you need to add, change or remove.

In LQS, in the built customs document, these produced documents codes can be found on tariff line level. Such codes as “N935”, for example, need to be added in the Document type field. If you choose the field, you can see different codes and descriptions. In the Document referenties field, you need to enter a reference to the produced document, for example an invoice number or typical reference to the document type you entered. Also Date is a mandatory field and in some cases it can be useful to add the involved customs office in the Voor document kantoor field.

The screenshot below shows how the Produced documents section looks like in a built customs document.

image16

note: For each customs commodity code, different produced documents needs to be added. On the Tarweb website of the Belgian Customs authorities you can find these codes.

 

Het eerste karakter van de aanvullende nationale code Taric mag niet 2,3, 4, 6, 7, 8, 9, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O of P zijn.

If you receive this error message, you need to check box 33, the Additional National Taric Code field. This box contains a wrong code and this code should be filled in another box, for example as an additional national code instead of this Additional National Taric code

 

Taric-code bestaat niet 3919103110

image14

This error means that the commodity code does not exist (anymore). In this case, you need to consult the TARWEB website from Belgian Customs Authorities to check for an existing TARIC Code (also known as customs commodity code). In normal cases, this error message also refers to the tariff line where the involved TARIC code is used. This can be found in the Error Location Detail field.

 

Write off electronical freight list

If you need to write off from an electronical freight list, the following information can help you to fill in all the necessary information customs requires.

  • In case of an electronical freight list, most of the time 126E is used as document type.
  • As voorafgaande verwijzing you need to refer to the harbour code, Stay number, Lloydsnumber and article number you need to write off from.

Harbour code, 1 digit, choose between the following options:

  • 1 = electronical freight list from Antwerp
  • 2 = electronical freight list from Zeebrugge
  • 3 = electronical freight list from Gent

Followed by 14 characters of the freight list number so 6 characters of the Stay Number and 8 characters of the Lloydsnumber; most of the time this Lloydsnumber starts with L followed by * (the asterisk is a delimiter character) followed by 4 digits of the article number you need to write off from.

  • Aanvullende info – additional information you need to add:

Code of the agent, maximum 6 characters, followed by *. Then the item numbers of 4 digits within the article number, again followed by *, and then 14 characters of the bill of lading number.

Below you can find an example of such an entrance:

image15

 

‘Het bijgevoegd document Y040 moet verplicht in vak 44 aangegeven worden’.

In case this error is received, customs are requesting to add the produced document code Y040 into box 44. As document referentie, the same EORI number is filled into box 8 – consignee, needs to be inserted, but without the identification code 000, 998, 005, etc.

Keep in mind that the document referenties, document datum and document type must always be filled in. If one of these mandatory fields is not filled in, LQS will provide an internal warning.

In case of fiscal representation, code Y040 and Y041 should be filled in. The screenshot below can assist you to achieve the necessary result.

image16

 

WO_002: customs event is niet gekend

This error code is received when the customs event is not known. This means the data you entered for your write-off is causing errors. The write-off data needs to be checked as there is a difference with the information in the customs system of PLDA or NCTS. It is possible that a wrong quantity or MRN is wrong or something else. If this data seems to be filled correctly, you need to have this verified at the PLDA helpdesk.

D_GOODS_NOT_ARRIVED: De goederen werden nog niet aangeboden, vandaar kan de aangifte niet aanvaard worden.

This error message is received when goods did not arrive. The moment goods arrive, a customs declaration can be sent again and will be accepted by customs.

 

WO_006: onbekende goederenlijn

This means that the write-off information, specified in box 40, is not known by customs. If the information seems to be correct, you need to contact the PLDA helpdesk and in most cases they will suggest a solution. In most cases, they will ask you to use manual codes.

 

D_REUSE_OF_LRN_NOT_AUTHORIZED: De LRN moet uniek zijn, tenzij voor een onvolledige/vereenvoudigde aangifte en zijn aanvullende aangifte en voor CIV gegevens en de overeenkomstige globalisatieaangifte

Due to communication problems it happens sometimes that the customs declaration could not be processed by customs. Also in this case we suggest contacting the PLDA helpdesk to double-check if this customs declaration was processed to avoid a double declaration even after this error is received. If the PLDA helpdesk confirms this declaration is not processed, you can send this declaration with a new LRN.

 

ITEM_0024: Nettogewicht mag niet groter zijn dan brutogewicht

This error means that the net weight cannot be larger than the gross weight. Please correct the weights.

image17

BTW nr geadresseerde – DECL_EO_0047 (identifcationCodeType) is niet correct –

A Belgian VAT number should be filled in in the following way: BE + 000 and the first digit of the KBO number (= VAT number + additional zero). For example: BE0000404785354.

A foreign VAT number should be filled as follows: country code + 998 + VAT number. For example: NL998801923608B01

 

Invalid Goods location code

If you receive this error message, it means that the goods location code, specified in box 30 on the header level, is incorrect. The list of these codes is changed often and can be retrieved from customs.

image18

 

Missing

image19

In this case, the 40: Voorafgaande Documenten field is not filled in while this is a mandatory field. On tariff lines > previous documents, you need to refer to the previous regime. For example, make s reference to the storage into the customs warehouse or the freight list. In case you do not know these codes by heart, you choose the field and select from a list.

 

Package type is mandatory

In box 31, the package type is not filled. This is a mandatory field. You can choose the field to search for the necessary code.

Vak 36 eerste positie is vereist of tweede en derde positie is vereist

This error message refers to the 1st, 2nd or 3rd part of box 36 namelijke the preference. This field can be found on tariff lines.

image20

Invalid additional information type code

Correction needs to be done in box 44: bijzondere vermeldingen (or in English version of the field: Special Mentions). The code is invalid or cannot be used for this type or regulation.

VAK 17 a is verplicht

Box 17, which Is a country of destination, is mandatory. This field can be found on header level. This field is not mandatory for all declarations. In fact for an EXA D document this box should be empty.

image21

Bij een aangifte IM7, moet er een additionele informatie zijn van type PLDA-DTO-1 of PLDA-DTO-2

Bijzondere vermelding ‘44-PLDA-DTO-1 or 44-PLDA-DTO-2’ should be filled in box 44 as a special mention on tariff lines for a storage document for bonded warehouse B, since 01-05-2016 bonded warehouse type S.

image22

 

Vak 8 mag niet ingevuld worden

In box 8 the consignee must be specified for a T2L or T2L declaration.

 

Ongeldige combinatie van regeling, aanvullende code, nationale aanvullende codes, betaalwijze, betaalwijze BTW en borg.

If this error message is received, the different fields related to the regulation need to be checked where you specify the following information: regulation, previous regulation, additional codes, national additional codes, payment method, payment method VAT and guarantee.

If it is still not clear what to correct, please feel free to contact the Logiqstar helpdesk or the PLDA helpdesk.

Het veld ‘artikel’ is vereist – Field ‘article’ is mandatory

The Article field in box 40 – previous documents – is not filled in. If category X, type IM is used, the Article field is mandatory.

 

Vrijstellingcode voor accijnzen: 0600 – Excemption code 0600 for excises

In some cases, code 0600 is allowed to be used to have exemption for excises. This code needs to be specified in box 33. In LQS, this should be filled as shown in the screenshot below.

image23

Invullen tariefcontingent – Fill in ‘quota’

In case you need to use a quota, there are 2 fields that need to be taken into account, namely Preference and Quota. The quota is linked to a specific preference and in the field Quota, you need to specify the number of the quota (= tariefcontingent, also called order number).

image24 image25

For more information about which preference and quota number you can use, consult the TARWEB website of Belgian customs authorities.

Het document C601 (vergunning actieve veredeling) ontbreekt in vak 44

This error means that document number C601 for inward processing is missing in box 44, on the produced documents.

image26

Het document 3046, 3047, 3050, 3051 of 3053 (nationale code vergunning actieve veredeling) ontbreekt in vak 44

Depending on which license of inward processing you own, you need to insert as a produced document one of the mentioned codes.

Invalid payment method code

This error is received when you used the incorrect payment method code. This payment method code is related to the regulation and declarant information. This field can be found on the Betalingsgegevens tab.

If you insert code E, exemption, as payment method code for VAT, you will receive this error as this should be L, temporary exemption, in this case.

image27

note: There is a possibility that you retrieve another payment method code back in the release message of customs. This is a known error on the customs side , but keep in mind that this can be very confusing.

De geadresseerde heeft geen toestemming tot verlegging van betaling BTW.

In this case consignee is not allowed to use exemption for VAT. This means that code G was filled in as the payment method code for VAT. Only code A, payment of VAT, can be used. Be aware that this has serious consequences in practice as they have no deferment of paying the VAT if code A is used.

Supplementary_unit_missing: Code statistische eenheid is niet correct. NAR is vereist.

The supplementary unit (: ‘aanvullende eenheden) should be specified. For example, you can fill in NAR in box 41. You can choose the field to see the list of available codes and descriptions. Also TARWEB, the website of Belgian Customs can be referred to find out which code should be used here.

image28

 

Vak 37 (1e 2 posities) gelijk aan 71 en de aanvullende code 7A1 of 7A3 werd niet vermeld

Since May 2016, changes in the legislation were implemented for all storage documents. For example, additional code 7A1 is removed and cannot be used in a storage document anymore.

image29

 

Changes customs bonded warehouse from 1 May 2016

The types of customs warehouses are changed. In the table below you can get an overview of the changes. (left: until April 30th 2016, right: starting May 1st 2016)

image30

In LQS, in the built document, this should be filled in as shown in the screenshot below:

image31

 

Invalid Produced document type : 3046

Produced document type code 3046 is removed since 1 May 2016. This code must not be used anymore.

 

Invalid Produced document type : 3047

Produced document type code 3047 is removed since 1 May 2016. This code must not be used anymore.

 

Invalid Produced document: 3036

Starting May 1st 2016 various produced documents have been changed. Some codes must not be used anymore and new codes are applicable. For example, 3036 is replaced with C517.

In the table below, you can see the old codes and the new codes that must be used instead of the old ones.

image32

 

Lenght must be higher than 14

This error message informs you that the document number is not in the correct format. In this case, the number of characters is less than the allowed length.

image33

The WOFF of a freight list into a PLDA customs declaration should look similar to the following example:

image34

Codes D and E are rejected when procedureComm1 = 71 or 78

image35

From 1 May 2016, customs warehouse type E is not allowed anymore as this has been replaced with code U.

Please consult section 1.30 for more details.

 NCTS customs errors

CC015A[1]/GOOITEGDS[1]

Information on tariff line 1 is insufficient. Please fill all the necessary information.

GUA(1)REF(1).Access code

An incorrect pin code is used. This pin code is, for example, not correct for the used GRN (Guarantee Reference Number) or not correct for the representative that is used in this customs declaration.

GDS(1).NR2

This error message is received if there are container numbers filled in but the container indicator has amount zero or vice versa.

The numbers of containers are mentioned on tariff lines in box 31, but, on the header, there is a field that is sent to customs to refer to these containers. If the container indicator is filled in with value 1, this means that this concerns a container shipment and container numbers should be filled in. In case of value 0, there should be no container numbers filled in.

Container indicator on heading:

image36

Container number on tariff lines:

image37

Exception: execute of service GUA_INTEG_CHECK failed

This error message means that the GRN number can’t be validated in the customs system. In most cases it helps to resend the declaration. Otherwise we advise to contact the NCTS helpdesk.

GDS(1)AR2(1).Previous document type

This error is referring to box 40 previous document, which can be found on tariff lines. Please find below an example how this node should looks like.

faq0001

GDS(1)AR2(1).Previous document reference

The Previous reference field or in Dutch ‘Voorafgaande verwijzing, box 40’, does not contain the correct information or does not contain any information. This field can be found on tariff lines.

Technical invalidation

A ‘technical validation error’ is a customs error where customs authorities want to inform you that there is a mandatory field in the related customs declaration that does not contain any value or a field contains the value in a wrong format. In the example below, the document type is filled in but there is no reference in the Voorafgaande verwijzing field. It is difficult to solve such errors so in this case you can always contact the LQS support team and/or the NCTS helpdesk.

image39