CDS Feedback Required by Jan 31

As part HMRC work on the immediate payments solution,   an issue with the current notification consolidation patterns for CDS was identified.

As it stands, the Release 2 Imports DMS Business Rules codebase is configured to delay sending DMSTAX notification for 1 hour or send it along with the next notification - DMSCLE in most cases-  in a single consolidated message that is sent out, whichever is sooner.

However, in an immediate payment scenario, the ability for the trade to receive the DMSTAX notification which provides details of customs debt and payment reference is a necessary preliminary step to clearance given that clearance is predicated on receiving payment to cover outstanding liabilities.  

Therefore, if HMRC were to continue, without implementing any change, then processing an immediate payment declaration would result in DMSTAX being sent after the scheduled 1 hour delay with DMSCLE and DMSTAX again sent separately once sufficient payment has been received and declaration cleared accordingly. 

HMRC would like to remove this one-hour wait by implementing a change to ensure DMSTAX is sent to trade as soon as it is generated.  This change would apply for all declaration types and payment methods and mean that DMSTAX and DMSCLE will be sent as separate notifications in all scenarios, albeit that they will be received in quick succession for declarations using duty deferment.

In response to feedback, HMRC have already communicated plans to make changes to the timing of the DMSTAX notification (to send it before the 10 minute dwell time starts).  Therefore this proposal, to split the notifications in order to facilitate immediate payments, represents an earlier change to the current implementation, than you are currently expecting.

Can you please provide feedback on the impact this change to the DMSTAX and DMSCLE notifications will have on your development. Please include details as to timeline you would need to implement and test these changes, to allow us to determine when we could schedule this change appropriately for deployment.

Back to news

We use cookies on this site to improve your experience. By continuing to browse the site you are agreeing to our use of cookies. You will only see this message once. Find out more