Ics19
My feedback
5 results found
-
1 voteIcs19
shared this idea
·
-
8 votesIcs19
supported this idea
·
-
7 votesIcs19
supported this idea
·
An error occurred while saving the comment -
1 voteIcs19
shared this idea
·
-
1 vote
An error occurred while saving the comment Ics19
commented
> The problem is C & D automatically generates a customs label when we send from N Ireland to the Republic
Well, that's a different problem :) The field you originally described is for the customs data of individual products and wouldn't be the place to say that you're resident in NI and therefore trading under the NI protocol (or it's replacement). Either there needs to be a new setting entirely or better still Click and Drop should just automatically recognise your place of dispatch based on your account information.
An error occurred while saving the comment Ics19
commented
Are you referring to this guidance:
https://taxation-customs.ec.europa.eu/system/files/2020-11/use_of_gb_and_xi_codes_guidance.pdf
If so, page 22 says that "The rules of origin do not distinguish between Northern Ireland and other parts of the United Kingdom. The code GB is used."
The guidance says it applies from from 1 January 2021?
Yes, it's pants isn't it. Unlike you, we do upload descriptions, but they do also get replaced - we recently had "Vehicle wiper blades" replaced by "Dog toy"! It seems related to the length of input tariff code - where 6 digits were once ok (as they are the WTO standard), CnD are now substituting their own 10 digits and these aren't necessarily representative of the previous entry. If 10 digits are mandatory in the system, then 1) the documentation should state this and 2) it should be an error when anything less 10 is entered, rather than some potentially bogus erroneous value submitted on your behalf that could have a negative impact on import charges incurred by the customer, or worse, refused and returned by customs particularly if you're sending to Ireland and the new code falls into the illogical An Poste banned list. As a work around, you could look into padding your current 8 digit code(s) with trailing zeros to make them 10 digits (and the same for any 6 digits codes). While this may not be technically correct in all situations, it would be more accurate then the fudge data currently being substituted and does appear to allow the entered data to be kept - I would ensure you do enter a valid description though, as that really is a requirement :)