Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page lists all currently known issues and temporary workarounds if they’re available.

...

  1. HMRC have not finished with the submission request yet so haven’t issued a response - wait for a response and if you’ve not received a response in a reasonable timeframe then contact customs providing them with the UCR Ref ID shown against the shipment.

  2. Bond may have missed a response message (only seen in Bond versions earlier than v5.6.9).

...

  1. Customs may require a copy of the invoice showing the stock values

https://visionsoftware.atlassian.net/wiki/spaces/VB/pages/2890629201/Communicating+with+HMRC#Querying-CDS may assist in force clearing these, however customs should be contacted for advice if this is not the case.

Rejections

Tag name

Element name

Validation Code & Description

Explanation

DeclarationGoodsShipmentItemAdditionalDocument

AdditionalDocument

X447

For GP1 greater than 60000hl and ASV greater than 7.5% this additional code needs to be supplied

In the Declaration > Goods Shipment Item > Commodity:

  • TARIC Add Classif ID should be set to X447

  • TARIC Add Identi Type Code should be set to TRA

This is required for high strength beers, when VW-6476 is released in v6.5.1 this will be automatic, users need to follow the workaround above in the meantime.

Note

26/09/2022

DeclarationGoodsShipmentItemCustomsValuation / MethodCode rejection.

Customs Valuation / Method Code rejection

HMRC appear to have updated the live CDS system and introduced new validation which we were not expecting to go live so soon, as communication about this update was poor and we’ve started discussions with HMRC about this to avoid this happening in future. As a result, all declarations from all customer systems will be rejected until we get a new version of Bond out which is compatible with the changes they’ve made.

We’re working on getting this version out as quickly as possible but do not expect anything to be sent out until the later half of w/c 03/10/2022 earliest, we are currently awaiting guidance from HMRC.

In the meantime do not ‘Import’ new declarations into CDS, otherwise you will be left with many failed declarations all needing to be submitted individuallyupgrading to Bond version 5.6.11, which was available for customers to upgrade to from Monday 3rd October 2022.

HMRC’s changes require the invoice number (which shows the stock values paid for by the customer) to be sent in the declaration, a field we do not currently hold. As such we’ve agreed with HMRC that the Customer PO Number will be sent instead until the necessary changes can be incorporated into Warehousing and rolled out.

It’s also come to light that one of HMRC’s developer specification documents was missing vital information about potential messages which could be returned to Bond, two specific messages in fact which act as an instruction from HMRC for a copy of the invoice to be provided to them in order for the declaration to be cleared. At this stage it’s unclear whether any customers would’ve received one of these messages however due to some declarations appearing stuck in some systems it would appear likely. Again we’re in discussions with HMRC about how this should be handled and we’ll provide an update when we have one, in the meantime customers should upgrade to the new version and continue as they have done until now and if any declarations become stuck then the advice provided in the points above should be followed.

After upgrading to Bond v5.6.11 customers can continue to ‘Import’ new declarations into CDS.

Update 27/09/2022: We expect the FSD will be unaffected. As no customers have submitted declarations to CHIEF via CFSP in September you should be able to generate the CDS FSD in your current versions without waiting to submit the remaining September declarations.Update 29/09/2022: The application changes are complete however we’re still awaiting a response from HMRC for confirmation that we can proceed in the way we’d planned. Until we have confirmation we will not be able to start rolling out the release.