Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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

General

Unhandled exception

This occurs when the system hasn’t yet been authenticated with HMRC (or the authentication token has expired) and one of the necessary Microsoft components are not installed on your system.

This is usually installed automatically by our installer however some anti virus / threat systems may block the installation. In this case install Microsoft Edge WebView2 Runtime manually from the following link https://developer.microsoft.com/en-us/microsoft-edge/webview2/#download-section - be sure to run as administrator.

Bond becomes stuck during HMRC submission

Only after just entering your HMRC gateway credentials, if Bond appears to become stuck showing “Please wait while communicating with CDS service” for a prolonged period of time while attempting to submit declarations then this could mean that the gateway credentials you’ve used do not have access to the CDS service, close Bond and retry with a different HMRC gateway account (you’ll likely need to force close the application when this occurs).

Declarations not clearing

If declarations appear to get stuck (not progress to ‘Cleared’ status) this can mean one of two things:

  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).

  3. 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.

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, 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 upgrading 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 is missing vital information about response messages which could potentially 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. In the absence of accurate documentation 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. Further new versions are likely to follow as we make progress with HMRC on the matter.

Update 27/09/2022: The FSD will be unaffected. As no customers have submitted declarations to CHIEF via CFSP in September you can still generate the CDS FSD in your current versions without waiting to submit the remaining September declarations.

  • No labels