60 likes | 138 Views
Automation of ‘Provisional Payment’ requirements 21 August 2014 Stakeholder Modernisation Meeting (Megawatt) Varsha Singh. What we need to achieve.
E N D
Automation of ‘Provisional Payment’ requirements 21 August 2014 Stakeholder Modernisation Meeting (Megawatt) Varsha Singh
What we need to achieve • Automation to the transactional ‘Security’ (provisional payment) requirements that will also be included within the CUSDEC message format. This eliminates the separate paper transaction (DA70) for electronic declarations and allows for full automation and end-to-end management of Customs’ security requirements. The scope includes pre and post declaration “security”, as well as “penalty” and “forfeiture” amounts. • Automate Provisional Payments as part of an Integrated Process • Develop Provisional Payments as part of iCBS • Manage the conditions pertaining to the type of provisional payment lodged. • Finalise the liquidation of provisional payments.
Platform • Phase 1: Link to Declaration • EDI Channel • Processing on iCBS • Develop as part of declaration and VOC • Section 91 – submitted as a supporting document with signature • Development will be required by the trader systems as well as internally ito interfaces
Provisional Payment Categories - Type 1 Part of Declaration / VOC
Provisional Payment Categories – Type 2 Part of VOC
Provisional Payment Categories – Type 3/4 Part of VOC