11.04.2014 Views

Customs Declaration Processing System Detailed User and ...

Customs Declaration Processing System Detailed User and ...

Customs Declaration Processing System Detailed User and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

ORIGINATOR: EU Contractor ISSUE DATE: 21/7/2008 VERSION: 1.00-EN<br />

SUBJECT:<br />

<strong>Customs</strong> <strong>Declaration</strong> <strong>Processing</strong> <strong>System</strong><br />

<strong>Detailed</strong> <strong>User</strong> <strong>and</strong> Technical Requirements<br />

And Use-case Models<br />

REVISIONS<br />

EDI. REV. DATE DESCRIPTION<br />

1 00 .. . 6. 2008 First draft of content – sent for consideration to MCA<br />

1 01 .. . 6. 2008 Update by project team<br />

1 02 25.6.2008 Initial draft version finished (given to MCA, EAR)<br />

1 03 25.6.-2.7.2008 Update by project team<br />

1 04 2.7.2008 Second draft version finished (given to MCA)<br />

1 05 2.-10.7.2008 Initial Comments of MCA to transit <strong>and</strong> export<br />

Update by project team<br />

1 06 10.7.2008 Third draft version finished (given to MCA)<br />

1 07 11.-21.7.2008 Initial Comments of MCA to import<br />

Use-case models (transit, export <strong>and</strong> import)<br />

Update by project team<br />

13 Update with final comments by beneficiary (MCA)<br />

Final 16 12.08.2008 Updated with information on LDAP <strong>and</strong> integration with subapplications.<br />

Page 1/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Table of Contents<br />

REVISIONS ........................................................................................................................................................... 1<br />

TABLE OF CONTENTS ..................................................................................................................................... 2<br />

1 INTRODUCTION - EXECUTIVE SUMMARY .................................................................................... 12<br />

1.1 Purpose of CDPS............................................................................................................................. 12<br />

1.2 Objectives of CDPS......................................................................................................................... 12<br />

1.3 Scope of CDPS................................................................................................................................. 13<br />

1.4 Intended audience ........................................................................................................................... 13<br />

1.5 Structure of this document............................................................................................................. 14<br />

1.6 Terminology..................................................................................................................................... 14<br />

THERE ARE DIFFERENT LEVELS OF REQUIREMENTS:........................................................................... 14<br />

A) USER REQUIREMENTS ............................................................................................................................ 14<br />

B) FUNCTIONAL SPECIFICATIONS ........................................................................................................... 14<br />

C) TECHNICAL SPECIFICATIONS (SOFTWARE SPECIFICATION)................................................... 14<br />

MUST .................................................................................................................................................................. 15<br />

MUST NOT......................................................................................................................................................... 15<br />

SHOULD ............................................................................................................................................................. 15<br />

SHOULD NOT.................................................................................................................................................... 15<br />

MAY .................................................................................................................................................................... 15<br />

THIS WORD, OR THE ADJECTIVE "OPTIONAL", MEANS THAT AN ITEM IS TRULY<br />

OPTIONAL. ................................................................................................................................................ 15<br />

1.7 Abbreviations used in this document ............................................................................................ 15<br />

1.8 Related documents.......................................................................................................................... 16<br />

2 DOMAINS OF THE CDPS.................................................................................................................... 18<br />

2.1 National Domain ............................................................................................................................. 19<br />

2.2 External Domain ............................................................................................................................. 19<br />

2.3 Domains of the government agencies ............................................................................................ 20<br />

2.4 Common Domain (only for EU-EFTA communication) ............................................................. 21<br />

3 CDPS – MAIN APPLICATION............................................................................................................... 22<br />

3.1 Transit regime (NCTS)................................................................................................................... 22<br />

3.1.1 Trade <strong>Customs</strong> office of departure....................................................................... 22<br />

3.1.1.1 Electronic transit declaration...................................................................................... 22<br />

3.1.1.2 Paper transit declarations ........................................................................................... 23<br />

3.1.1.3 Documents to accompany the transit declaration....................................................... 24<br />

3.1.1.4 Acceptance, customs controls, modifications, rectifications <strong>and</strong> cancellation of<br />

transit declaration....................................................................................................... 24<br />

3.1.1.5 Cancellation of transit declaration or transit regime .................................................. 25<br />

3.1.1.6 Consultation of the status of transit declaration......................................................... 26<br />

3.1.2 Release of goods for transit regime ................................................................................ 26<br />

3.1.2.1 Use of st<strong>and</strong>ard procedure.......................................................................................... 26<br />

Page 2/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.1.2.2 Use of simplified procedure of authorised consignor ................................................ 27<br />

3.1.3 <strong>Customs</strong> office of departure <strong>Customs</strong> office of guarantee.................................. 28<br />

3.1.3.1 Check of the guarantee............................................................................................... 28<br />

3.1.3.2 Register of guarantee usage ....................................................................................... 30<br />

3.1.3.3 Writing off the guarantee ........................................................................................... 30<br />

3.1.4 <strong>Customs</strong> office of departure <strong>Customs</strong> office of transit........................................ 30<br />

3.1.4.1 Anticipated Transit Record ........................................................................................ 30<br />

3.1.4.2 Transit Accompanying Document ............................................................................. 31<br />

3.1.4.3 Incidents during the transport..................................................................................... 31<br />

3.1.5 <strong>Customs</strong> office of departure <strong>Customs</strong> office of destination................................ 32<br />

3.1.5.1 Anticipated Arrival Record........................................................................................ 32<br />

3.1.5.2 Transit Accompanying Document ............................................................................. 33<br />

3.1.5.3 Cancellation of transit regime .................................................................................... 33<br />

3.1.6 Trade <strong>Customs</strong> office of transit (Common/Community transit)........................ 33<br />

3.1.6.1 Notification of arrival <strong>and</strong> presentation of goods....................................................... 33<br />

3.1.6.2 Control of goods......................................................................................................... 34<br />

3.1.7 Trade <strong>Customs</strong> office of entry or exit................................................................... 34<br />

3.1.7.1 Entry or exit summary declaration............................................................................. 34<br />

3.1.7.2 Risk analysis .............................................................................................................. 35<br />

3.1.7.3 Presentation of goods <strong>and</strong> notification of arrival ....................................................... 35<br />

3.1.7.4 Control of goods......................................................................................................... 35<br />

3.1.7.5 Registration ................................................................................................................ 35<br />

3.1.7.6 Diversion.................................................................................................................... 35<br />

3.1.8 Trade <strong>Customs</strong> office of destination ..................................................................... 36<br />

3.1.8.1 Notification of arrival................................................................................................. 36<br />

3.1.8.2 Risk analysis .............................................................................................................. 36<br />

3.1.8.3 Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure..................................... 36<br />

3.1.8.4 Diversion.................................................................................................................... 37<br />

3.1.8.5 Use of simplified procedure of authorised consignee ................................................ 37<br />

3.1.9 <strong>Customs</strong> office of destination <strong>Customs</strong> office of departure................................ 39<br />

3.1.9.1 Presentation of goods at destination (Arrival Advice)............................................... 39<br />

3.1.9.2 Control of goods (Control results) <strong>and</strong> ending of transit regime ............................... 39<br />

3.1.9.3 Discrepancies ............................................................................................................. 39<br />

3.1.10 Write-off by <strong>Customs</strong> office of departure...................................................................... 40<br />

3.1.10.1 End of transit procedure confirmed............................................................................ 40<br />

3.1.10.2 Release of guarantee .................................................................................................. 40<br />

3.1.10.3 Principal notification on discharge of transit regime ................................................. 40<br />

3.1.11 Enquiry procedure........................................................................................................... 40<br />

3.1.11.1 Notification towards Principal ................................................................................... 41<br />

3.1.11.2 Enquiry procedure towards declared/actual <strong>Customs</strong> office of destination............... 41<br />

3.1.11.3 Enquiry procedure towards declared/actual customs office of transit ....................... 41<br />

3.1.11.4 Recovery procedure towards a debtor (a principal) ................................................... 42<br />

3.1.12 NCTS/TIR procedure...................................................................................................... 42<br />

3.1.12.1 NCTS/TIR procedure at <strong>Customs</strong> office of departure ............................................... 42<br />

3.1.12.2 NCTS/TIR procedure at <strong>Customs</strong> office of destination............................................. 43<br />

3.1.12.3 Write-off by <strong>Customs</strong> office of departure (NCTS/TIR)............................................. 44<br />

3.1.13 Railway procedure........................................................................................................... 44<br />

3.1.13.1 Railway procedure at <strong>Customs</strong> office of departure (national transit) ........................ 45<br />

3.1.13.2 Railway procedure at <strong>Customs</strong> office of destination (national transit)...................... 45<br />

Page 3/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.1.13.3 Write-off by <strong>Customs</strong> office of departure (Railway)................................................. 46<br />

3.2 Export regimes ................................................................................................................................ 47<br />

3.2.1 Trade <strong>Customs</strong> office of export............................................................................. 47<br />

3.2.1.1 Electronic export declaration ..................................................................................... 47<br />

3.2.1.2 Paper export declarations ........................................................................................... 48<br />

3.2.1.3 Oral export declaration............................................................................................... 48<br />

3.2.1.4 Documents to accompany the export declaration ...................................................... 49<br />

3.2.1.5 Control of accompanied documents........................................................................... 49<br />

3.2.1.6 Acceptance, modifications, rectifications <strong>and</strong> deletions of export declarations ........ 50<br />

3.2.1.7 Cancellation of export declaration ............................................................................. 51<br />

3.2.2 Release of goods for export regime................................................................................. 51<br />

3.2.2.1 Use of st<strong>and</strong>ard procedure.......................................................................................... 51<br />

3.2.2.2 Use of simplified procedure of local clearance.......................................................... 52<br />

3.2.2.3 Use of simplified procedure of incomplete export declaration .................................. 53<br />

3.2.2.4 Use of simplified procedure of simplified export declaration.................................... 54<br />

3.2.2.5 Cancellation of export regime.................................................................................... 56<br />

3.2.2.6 Consultation of the status of export declaration......................................................... 57<br />

3.2.3 <strong>Customs</strong> office of export <strong>Customs</strong> office of exit................................................... 57<br />

3.2.3.1 Anticipated Export Record......................................................................................... 57<br />

3.2.3.2 Export Accompanying Document.............................................................................. 58<br />

3.2.3.3 Cancellation of export regime.................................................................................... 58<br />

3.2.4 Trade <strong>Customs</strong> office of exit.................................................................................. 58<br />

3.2.4.1 Notification of arrival................................................................................................. 58<br />

3.2.4.2 Risk analysis <strong>and</strong> pre-requisite controls of data......................................................... 58<br />

3.2.4.3 Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure..................................... 58<br />

3.2.4.4 Diversion.................................................................................................................... 59<br />

3.2.5 Exit authority (airport h<strong>and</strong>ling company) <strong>Customs</strong> of exit.............................. 59<br />

3.2.5.1 Goods movement information.................................................................................... 60<br />

3.2.5.2 Risk analysis - pre-requisite controls of data ............................................................. 60<br />

3.2.5.3 Presentation of goods ................................................................................................. 60<br />

3.2.5.4 Control of goods......................................................................................................... 60<br />

3.2.5.5 Notification of exit..................................................................................................... 61<br />

3.2.6 <strong>Customs</strong> office of exit <strong>Customs</strong> office of export................................................... 61<br />

3.2.6.1 Presentation of goods at exit ...................................................................................... 61<br />

3.2.6.2 Confirmation of Exit <strong>and</strong> Control results................................................................... 62<br />

3.2.6.3 Discrepancies ............................................................................................................. 62<br />

3.2.6.4 Invalidation of export declaration acknowledgement ................................................ 62<br />

3.2.7 Write-off by <strong>Customs</strong> office of export............................................................................ 63<br />

3.2.7.1 Exit of exported goods confirmed.............................................................................. 63<br />

3.2.7.2 Goods not exported .................................................................................................... 63<br />

3.2.7.3 Exit not confirmed – invalidation of export declaration ............................................ 63<br />

3.2.7.4 Notification of exit to declarant <strong>and</strong>/or exporter........................................................ 64<br />

3.2.8 Diversion........................................................................................................................... 64<br />

3.2.8.1 Export declaration request.......................................................................................... 64<br />

3.2.8.2 Export Advice Response............................................................................................ 64<br />

3.2.8.3 Diversion Notification................................................................................................ 64<br />

3.2.9 Split Consignments .......................................................................................................... 65<br />

3.2.9.1 Exit of goods via one <strong>Customs</strong> office of exit............................................................. 65<br />

3.2.9.2 Exit of goods via more than one <strong>Customs</strong> office of exit (computerised solution)..... 65<br />

3.2.9.3 Exit of goods via more than one <strong>Customs</strong> office of exit (paper solution).................. 66<br />

Page 4/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.2.10 Consolidated Consignments............................................................................................ 66<br />

3.3 Export control system..................................................................................................................... 67<br />

3.3.1 Trade <strong>Customs</strong> office of lodgement of EXD......................................................... 67<br />

3.3.1.1 Electronic exit summary declaration.......................................................................... 67<br />

3.3.1.2 Paper-based exit summary declaration....................................................................... 68<br />

3.3.1.3 Acceptance, modifications, rectifications <strong>and</strong> deletions of EXD............................... 68<br />

3.3.2 Trade <strong>Customs</strong> office of exit.................................................................................. 69<br />

3.3.2.1 Risk analysis - pre-requisite controls of data ............................................................. 69<br />

3.3.2.2 Notification of arrival................................................................................................. 69<br />

3.3.2.3 Presentation of goods ................................................................................................. 69<br />

3.3.2.4 Control of goods......................................................................................................... 69<br />

3.3.2.5 Diversion.................................................................................................................... 70<br />

3.3.3 Exit authority (airport h<strong>and</strong>ling company) <strong>Customs</strong> of exit.............................. 70<br />

3.4 Import regimes................................................................................................................................ 70<br />

3.4.1 Trade <strong>Customs</strong> office of lodgement of summary declaration............................. 70<br />

3.4.1.1 Electronic or paper summary declaration................................................................... 70<br />

3.4.1.2 Acceptance, modifications, rectifications <strong>and</strong> deletions of SD.................................. 71<br />

3.4.1.3 Temporary storage ..................................................................................................... 72<br />

3.4.1.4 Release from temporary storage................................................................................. 72<br />

3.4.2 Trade <strong>Customs</strong> office of import ............................................................................ 72<br />

3.4.2.1 Electronic or paper-based import declaration ............................................................ 72<br />

3.4.2.2 Oral import declarations............................................................................................. 74<br />

3.4.2.3 Documents to accompany the import declaration...................................................... 75<br />

3.4.2.4 Control of accompanied documents........................................................................... 75<br />

3.4.2.5 Acceptance, modifications, rectifications <strong>and</strong> deletions of import declarations........ 75<br />

3.4.2.6 Cancellation of import declaration............................................................................. 76<br />

3.4.3 <strong>Customs</strong> office of import <strong>Customs</strong> office of guarantee ....................................... 77<br />

3.4.3.1 Check of the guarantee............................................................................................... 77<br />

3.4.3.2 Register of guarantee usage ....................................................................................... 77<br />

3.4.3.3 Writing off the guarantee ........................................................................................... 78<br />

3.4.4 Release of goods for import regime of free circulation................................................. 78<br />

3.4.4.1 Use of st<strong>and</strong>ard procedure.......................................................................................... 78<br />

3.4.4.2 Use of simplified procedure of local clearance.......................................................... 80<br />

3.4.4.3 Use of simplified procedure of incomplete declaration ............................................. 81<br />

3.4.4.4 Use of simplified procedure of simplified declaration............................................... 82<br />

3.4.4.5 Cancellation of regime ............................................................................................... 84<br />

3.4.5 Release of goods for import regimes with economic impact ........................................ 85<br />

3.4.5.1 Use of st<strong>and</strong>ard procedure.......................................................................................... 85<br />

3.4.5.2 Control of goods......................................................................................................... 86<br />

3.4.5.3 Use of simplified procedure of local clearance.......................................................... 87<br />

3.4.5.4 Use of simplified procedure of incomplete declaration ............................................. 88<br />

3.4.5.5 Use of simplified procedure of simplified declaration............................................... 90<br />

3.4.5.6 Cancellation of an import regime with economic impact .......................................... 92<br />

3.4.5.7 Discharge of import regime with economic impact................................................... 92<br />

3.5 Import control system..................................................................................................................... 93<br />

3.5.1 Trade <strong>Customs</strong> office of lodgement of END......................................................... 93<br />

3.5.1.1 Electronic entry summary declaration (END)............................................................ 93<br />

3.5.1.2 Paper-based entry summary declaration .................................................................... 94<br />

3.5.1.3 Acceptance, modifications, rectifications <strong>and</strong> deletions of END............................... 94<br />

Page 5/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.5.2 Trade <strong>Customs</strong> office of first entry....................................................................... 95<br />

3.5.2.1 Risk analysis - pre-requisite controls ......................................................................... 95<br />

3.5.2.2 Arrival notification..................................................................................................... 95<br />

3.5.2.3 Presentation of goods ................................................................................................. 95<br />

3.5.2.4 Control of goods......................................................................................................... 96<br />

3.5.2.5 Diversion.................................................................................................................... 96<br />

3.5.3 Trade <strong>Customs</strong> office of subsequent entry........................................................... 96<br />

3.5.3.1 Notification of arrival................................................................................................. 96<br />

3.5.3.2 Pre-requisite controls ................................................................................................. 97<br />

3.5.3.3 Presentation of goods ................................................................................................. 97<br />

3.5.3.4 Diversion.................................................................................................................... 97<br />

3.5.4 Process at entry ................................................................................................................ 98<br />

4 SUB-APPLICATIONS .............................................................................................................................. 98<br />

4.1 Authorisations sub-application...................................................................................................... 98<br />

4.1.1 Authorisations in Transit regime ................................................................................... 98<br />

4.1.1.1 Simplified procedure of authorised consignor ........................................................... 98<br />

4.1.1.2 Simplified procedure of authorised consignee........................................................... 99<br />

4.1.1.3 Simplified procedure of use of special seals ............................................................ 100<br />

4.1.1.4 Simplified procedure of exemption regarding prescribed itinerary ......................... 101<br />

4.1.1.5 Electronic communications in transit....................................................................... 101<br />

4.1.1.6 Authorisation for representation in transit ............................................................... 104<br />

4.1.2 Authorisations in Export regimes................................................................................. 104<br />

4.1.2.1 Simplified procedure of local clearance in export regimes...................................... 104<br />

4.1.2.2 Simplified procedure of incomplete declaration in export regimes ......................... 105<br />

4.1.2.3 Simplified procedure of simplified declaration in export regimes........................... 106<br />

4.1.2.4 Use of outward processing regime (authorisation for RwEI)................................... 106<br />

4.1.2.5 Electronic communications in export regimes......................................................... 107<br />

4.1.2.6 Authorisation for representation in export ............................................................... 109<br />

4.1.3 Authorisations in Import regimes ................................................................................ 109<br />

4.1.3.1 Simplified procedure of local clearance in free circulation ..................................... 109<br />

4.1.3.2 Simplified procedure of incomplete declaration in free circulation......................... 110<br />

4.1.3.3 Simplified procedure of simplified declaration in free circulation .......................... 111<br />

4.1.3.4 Authorisation of end-use.......................................................................................... 112<br />

4.1.3.5 Use of customs warehousing regime (authorisation for RwEI) ............................... 112<br />

4.1.3.6 Use of inward processing regime (authorisation for RwEI)..................................... 113<br />

4.1.3.7 Use of temporary importation regime (authorisation for RwEI).............................. 114<br />

4.1.3.8 Use of processing under customs control regime (authorisation for RwEI) ............ 115<br />

4.1.3.9 Electronic communications in import regimes......................................................... 116<br />

4.1.3.10 Authorisation for representation in import............................................................... 118<br />

4.1.4 Authorised economic operator (AEO)................................................................................... 119<br />

4.1.4.1 Simplifications................................................................................................................. 119<br />

4.1.4.2 Security <strong>and</strong> safety........................................................................................................... 119<br />

4.1.4.3 Simplifications <strong>and</strong> Security <strong>and</strong> safety........................................................................... 120<br />

4.1.4.4 National <strong>and</strong> European AEO database............................................................................. 120<br />

4.2 Guarantee management system........................................................................................................ 121<br />

4.2.1 Guarantees in transit regime.................................................................................................. 121<br />

4.2.1.1 Guarantee in the form of cash deposit ............................................................................. 121<br />

4.2.1.2 Individual guarantee in the form of single guarantee undertaking .................................. 122<br />

4.2.1.3 Individual guarantee in the form of guarantee vouchers ................................................. 123<br />

4.2.1.4 Comprehensive guarantee................................................................................................ 123<br />

Page 6/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

4.2.1.5 Comprehensive guarantee waiver.................................................................................... 124<br />

4.2.2 Guarantees in other regimes than transit regime................................................................. 125<br />

4.2.2.1 Guarantee in the form of cash deposit ............................................................................. 125<br />

4.2.2.2 Individual guarantee in the form of single guarantee undertaking .................................. 126<br />

4.2.2.3 Comprehensive guarantee................................................................................................ 126<br />

4.2.3 Electronic communication with Office of Guarantee........................................................... 127<br />

4.3 Risk analysis <strong>and</strong> risk management system..................................................................................... 128<br />

4.3.1 Risk management.................................................................................................................... 128<br />

4.3.2 Risk management within the customs authorities................................................................ 129<br />

4.3.2.1 The context ...................................................................................................................... 129<br />

4.3.2.2 Selectivity, Profiling <strong>and</strong> Targeting................................................................................. 129<br />

4.3.2.3 Evaluation <strong>and</strong> review ..................................................................................................... 130<br />

4.3.2.4 Compliance Measurement Areas..................................................................................... 130<br />

4.3.2.5 Use of information technology for effective implementation of Risk Management ....... 131<br />

4.4 Tarim (TARIC).................................................................................................................................. 131<br />

4.4.1 General conditions of Tarim (TARIC)...................................................................................... 131<br />

4.4.2 Content of Tarim (TARIC) ....................................................................................................... 132<br />

4.4.3 Information flows...................................................................................................................... 132<br />

4.4.4 Business Process <strong>and</strong> Security Requirements ........................................................................... 133<br />

4.5 Accounting management system sub-application........................................................................... 133<br />

4.5.1 General conditions of Accounting management system sub-application.................................. 133<br />

5. TECHNICAL REQUIREMENTS .............................................................................................................. 134<br />

5.1 Introduction of concept <strong>and</strong> architecture........................................................................................ 134<br />

5.2 General Technical Requirements..................................................................................................... 134<br />

5.2.1 Networking Requirements......................................................................................................... 134<br />

5.2.1.1 Common Domain............................................................................................................. 135<br />

5.2.2 Modes of operation.................................................................................................................... 135<br />

5.2.3 Globalisation <strong>and</strong> Localisation.................................................................................................. 136<br />

5.2.3.1 Common Domain............................................................................................................. 136<br />

5.2.4 Fallback <strong>and</strong> availability ........................................................................................................... 136<br />

5.2.4.1 Overview.......................................................................................................................... 136<br />

5.2.4.2 Requirements ................................................................................................................... 137<br />

5.2.4.2.1 Common Domain Specific Requirements .................................................................... 138<br />

5.2.5 Security ..................................................................................................................................... 139<br />

5.2.5.1 Overview.......................................................................................................................... 139<br />

5.2.5.1.1 <strong>User</strong>s ............................................................................................................................. 139<br />

5.2.5.1.2 Access Rights, Roles <strong>and</strong> Security ............................................................................... 139<br />

5.2.5.1.3 Authentication <strong>and</strong> Digital Certificates ........................................................................ 140<br />

5.2.5.2 Requirements ................................................................................................................... 140<br />

5.2.5.2.1 Common Domain Specific Requirements .................................................................... 143<br />

5.2.6 Other – Supporting Services ..................................................................................................... 144<br />

5.2.7 Data Warehouse <strong>and</strong> Reporting................................................................................................. 144<br />

5.2.8 Technical Architecture .............................................................................................................. 145<br />

5.2.9 Operating Environment............................................................................................................. 146<br />

5.2.10 Version management <strong>and</strong> work packages ............................................................................... 148<br />

5.2.11 <strong>User</strong> Interface.......................................................................................................................... 149<br />

Page 7/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

5.3 CDPS Requirements.......................................................................................................................... 150<br />

5.3.1 Introduction............................................................................................................................... 150<br />

5.3.2 Integration Architecture ............................................................................................................ 151<br />

5.3.3 CDPS modules .......................................................................................................................... 152<br />

5.3.3.1 Transit Control <strong>System</strong> (TCS)......................................................................................... 152<br />

5.3.3.1.1 Availability Requirements............................................................................................ 153<br />

5.3.3.1.2 Requirements ................................................................................................................ 153<br />

5.3.3.2 Export regimes/Export Control <strong>System</strong> (ECS)................................................................ 153<br />

5.3.3.2.1 Availability Requirements............................................................................................ 153<br />

5.3.3.2.2 Requirements ................................................................................................................ 153<br />

5.3.3.3 Import Regime/Import Control <strong>System</strong> (ICS) ................................................................. 153<br />

5.3.3.3.1 Availability Requirements............................................................................................ 153<br />

5.3.3.3.2 Requirements ................................................................................................................ 153<br />

5.3.3.4 Reference Data Application............................................................................................. 153<br />

5.3.3.4.1 Requirements ................................................................................................................ 154<br />

5.3.3.4.1.1 Common Domain....................................................................................................... 154<br />

5.3.3.4.2 Availability requirements ............................................................................................. 154<br />

5.3.4 Integration with Common Domain ........................................................................................... 155<br />

5.3.4.1 Transit Control <strong>System</strong> (TCS)......................................................................................... 155<br />

5.3.4.2 Automated Export <strong>System</strong>/Export Control <strong>System</strong> (ECS) .............................................. 156<br />

5.3.4.3 Automated Import <strong>System</strong>/Import Control <strong>System</strong> (ICS) ............................................... 157<br />

5.3.4.4 Common Domain Conformance Testing Environment ................................................... 158<br />

5.3.4.4.1 Conformance Testing of CDPS .................................................................................... 158<br />

5.3.4.4.2 Conformance Testing Requirements ............................................................................ 159<br />

5.3.4.5 Connection to Common Domain ..................................................................................... 159<br />

5.3.5 Integration with National Domain............................................................................................. 160<br />

5.3.5.1 Connection to National Domain ...................................................................................... 160<br />

5.3.6 Integration with External Domain............................................................................................. 161<br />

5.3.6.1 Economic Operators ........................................................................................................ 161<br />

5.3.6.2 Other Government Agencies ........................................................................................... 161<br />

5.3.6.3 Connection to External Domain ...................................................................................... 161<br />

5.3.7 Conformance testing ................................................................................................................. 162<br />

5.3.8 Outsplication hosting................................................................................................................. 163<br />

6. PHASING/MILESTONES FOR THE CDPS PROOURCING OF APJECT ......................................... 164<br />

6.2 Introduction of the stages.................................................................................................................. 164<br />

6.2.1 Phase plan ................................................................................................................................ 164<br />

6.2.2 Phase objectives....................................................................................................................... 164<br />

7. USE-CASE MODELS.................................................................................................................................. 166<br />

7.1 Transit use-case model (national transit) ........................................................................................ 166<br />

7.1.1 Overview of Transit Core Business .......................................................................................... 167<br />

7.1.2 CO1A - Process Departure - Acceptance/Controls ................................................................... 168<br />

7.1.3 CO1B - Process Departure – Release........................................................................................ 169<br />

7.1.4 CO02 - Process Arrival at Office of destination ....................................................................... 170<br />

A) PROCESS ARRIVAL – PART I .................................................................................................................. 170<br />

B) PROCESS ARRIVAL - PART II.................................................................................................................. 171<br />

C) PROCESS ARRIVAL - PART III................................................................................................................. 172<br />

Page 8/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.5 CO04 - HANDLE ENQUIRY................................................................................................................... 173<br />

A) HANDLE ENQUIRY - PART 1................................................................................................................... 173<br />

B) HANDLE ENQUIRY - PART 2 ................................................................................................................... 174<br />

7.1.6 CO06 - Process Cancellation..................................................................................................... 175<br />

7.1.7 CO08 - Confirm Authorised Consignee.................................................................................... 176<br />

7.2 Transit use-case model (common/Community transit) .................................................................. 177<br />

7.2.1 Overview of common/Community Transit Core Business ....................................................... 177<br />

7.2.2 CO1A - Process Departure - Acceptance/Controls ................................................................... 178<br />

7.2.3 CO1B - Process Departure – Release........................................................................................ 179<br />

7.2.4 CO02 - Process Arrival at Office of destination ....................................................................... 180<br />

A) PROCESS ARRIVAL PART I ..................................................................................................................... 180<br />

B) PROCESS ARRIVAL PART II .................................................................................................................... 181<br />

C) PROCESS ARRIVAL PART III................................................................................................................... 182<br />

7.2.5 CO03 - Process movement at Office of Transit ........................................................................ 183<br />

7.2.6 CO04 - H<strong>and</strong>le enquiry ............................................................................................................. 184<br />

A) HANDLE ENQUIRY - PART 1................................................................................................................... 184<br />

B) HANDLE ENQUIRY - PART 2 ................................................................................................................... 185<br />

7.2.7 CO06 - Process Cancellation..................................................................................................... 186<br />

7.2.8 CO07 - Query Movement Information...................................................................................... 187<br />

7.2.9 CO08 - Confirm Authorised Consignee.................................................................................... 188<br />

7.3 National export use-case model ........................................................................................................ 189<br />

7.3.1 Overview of Export Core Business........................................................................................... 189<br />

7.3.2 CO1A - Process Export - Acceptance/Controls at Office of Export......................................... 190<br />

7.3.3 CO1B - Process Export – Release at Office of Export.............................................................. 191<br />

7.3.4 CO02 - Process Arrival at Actual Office of Exit....................................................................... 192<br />

A) PROCESS ARRIVAL AT ACTUAL OFFICE OF EXIT - PART I............................................................. 192<br />

B) PROCESS ARRIVAL AT OFFICE OF EXIT - PART II............................................................................. 193<br />

7.3.5 CO03 - Process Exit at Actual Office of Exit ........................................................................... 194<br />

A) PROCESS EXIT AT ACTUAL OFFICE OF EXIT - PART I ..................................................................... 194<br />

B) PROCESS EXIT AT ACTUAL OFFICE OF EXIT - PART II .................................................................... 195<br />

7.3.6 CO04 - HANDLE FOLLOW-UP.............................................................................................................. 196<br />

7.3.7 CO06 - Process Cancellation..................................................................................................... 197<br />

7.3.8 CO07 - Query Export Operation Information ........................................................................... 198<br />

7.4 ECS - AES use-case model ................................................................................................................ 199<br />

7.4.1 Overview of Export Core Business........................................................................................... 199<br />

7.4.2 CO1A - Process Export - Acceptance/Controls at Office of Export......................................... 200<br />

7.4.3 CO1B - Process Export – Release at Office of Export.............................................................. 201<br />

7.4.4 CO02 - Process Arrival at Actual Office of Exit....................................................................... 202<br />

A) PROCESS ARRIVAL AT ACTUAL OFFICE OF EXIT - PART I............................................................. 202<br />

B) PROCESS ARRIVAL AT OFFICE OF EXIT - PART II............................................................................. 203<br />

Page 9/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.5 CO03 - PROCESS EXIT AT ACTUAL OFFICE OF EXIT .................................................................... 204<br />

A) PROCESS EXIT AT ACTUAL OFFICE OF EXIT - PART I ..................................................................... 204<br />

B) PROCESS EXIT AT ACTUAL OFFICE OF EXIT - PART II .................................................................... 205<br />

7.4.6 CO04 - HANDLE FOLLOW-UP.............................................................................................................. 206<br />

7.4.7 CO06 - Process Cancellation..................................................................................................... 207<br />

7.4.8 CO07 - Query Export Operation Information ........................................................................... 208<br />

7.4.9 CO01A (SUM) – Process Exit summary declaration at Office of Lodgement ......................... 209<br />

7.4.10 CO02 (SUM) – Process Arrival at Actual Office of Exit........................................................ 210<br />

A) CO02 (SUM) – PROCESS ARRIVAL AT ACTUAL OFFICE OF EXIT PART I ..................................... 210<br />

B) CO02 (SUM) – PROCESS ARRIVAL AT ACTUAL OFFICE OF EXIT PART II.................................... 211<br />

7.4.11 CO03 (SUM) – Process Exit at Actual Office of Exit ............................................................ 212<br />

7.5 National import use-case model........................................................................................................ 214<br />

7.5.1 Overview of Import Core Business........................................................................................... 214<br />

7.5.2 CO1A - Process Import - Acceptance/Controls at Office of Import......................................... 215<br />

7.5.3 CO1B - Process Import – Release at Office of Import.............................................................. 216<br />

7.5.4 CO2 - Process Import – Discharge of Import Regime .............................................................. 217<br />

7.5.5 CO03 - H<strong>and</strong>le Follow-Up........................................................................................................ 218<br />

7.5.6 CO04 - Process Cancellation..................................................................................................... 219<br />

7.6 ICS - AIS use-case model .................................................................................................................. 220<br />

7.6.1 Overview of ICS-Core Business – ENS lodged at an Office of Lodgement............................. 220<br />

7.6.2 Overview of ICS-Core Business – ENS lodged at an Office of first Entry .............................. 221<br />

7.6.3 CO1A (SUM) – Process Entry Summary <strong>Declaration</strong> at Office of Lodgement ....................... 222<br />

7.6.4 CO1B (SUM) – Process Entry Summary <strong>Declaration</strong> at Office of first Entry.......................... 223<br />

7.6.5 CO1C (SUM) – Process Entry Summary <strong>Declaration</strong> at Office of subsequent Entry .............. 224<br />

7.6.6 C01D – Process international diversion at Office of first Entry ............................................... 225<br />

7.6.7 CO3A – Presentation at Actual Office of first Entry ................................................................ 226<br />

7.6.8 CO3B – Presentation at Actual Office of subsequent Entry ..................................................... 227<br />

7.6.9 CO3C– Release for Entry at Actual Office of (first or subsequent) Entry................................ 228<br />

7.6.10 Overview of Import Core Business......................................................................................... 229<br />

7.6.11 CO1A - Process Import - Acceptance/Controls at Office of Import....................................... 230<br />

7.6.12 CO1B - Process Import – Release at Office of Import............................................................ 231<br />

7.6.13 CO2 - Process Import – Discharge of Import Regime ............................................................ 232<br />

7.6.14 CO03 - H<strong>and</strong>le Follow-Up...................................................................................................... 233<br />

7.6.15 CO04 - Process Cancellation................................................................................................... 234<br />

8. ANNEXES..................................................................................................................................................... 235<br />

ANNEX 1 - DOMAINS FOR COMMUNICATION ..................................................................................... 235<br />

NATIONAL TRANSIT REGIME: .................................................................................................................... 235<br />

COMMON/COMMUNITY TRANSIT REGIME: ............................................................................................ 235<br />

NATIONAL EXPORT REGIME:...................................................................................................................... 236<br />

ECS - AES:......................................................................................................................................................... 236<br />

NATIONAL IMPORT REGIME:...................................................................................................................... 237<br />

Page 10/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

ICS - AIS:........................................................................................................................................................... 237<br />

ANNEX 2 - STAGES AND MILESTONES FOR CDPS.............................................................................. 238<br />

ANNEX 3 – LOCAL SELECTIVITY PROCESS......................................................................................... 239<br />

ANNEX 4 – SELECTIVITY PROFILE FILTER SYSTEM........................................................................ 240<br />

ANNEX 5 – NCTS REFERENCE DATA ...................................................................................................... 241<br />

ANNEX 6 – AES REFERENCE DATA ........................................................................................................ 253<br />

ANNEX 7 – AIS REFERENCE DATA .......................................................................................................... 268<br />

Page 11/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

1 INTRODUCTION - EXECUTIVE SUMMARY<br />

1.1 Purpose of CDPS<br />

The purpose of this document is to provide the user <strong>and</strong> technical requirement for the “<strong>Customs</strong> <strong>Declaration</strong><br />

<strong>Processing</strong> <strong>System</strong>” (CDPS).<br />

The purpose of the CDPS project is to provide a solution that will allow the customs offices involved in all<br />

customs regimes to:<br />

- h<strong>and</strong>le (receive, register, validate, accept, store <strong>and</strong> transmit) the customs declarations,<br />

- release the goods for declared customs regime,<br />

- exchange electronic messages in order automate the administrative flow of the operation,<br />

- elevate the effectiveness of controls against customs duties, taxes <strong>and</strong> other charges <strong>and</strong> other fraud,<br />

- expedite the flow of goods, <strong>and</strong><br />

- contribute to better supply chain security within WCO initiative <strong>and</strong> later within EU membership.<br />

The purpose of the CDPS project is to provide a solution to exchange data not only between <strong>Customs</strong><br />

authorities but also with other governmental organisations <strong>and</strong> economic operators.<br />

All efforts <strong>and</strong> attempts to lay down the groundwork for the implementation of the CDPS are part of a<br />

complete strategy from an electronic customs perspective. Similar strategy has been set up by European<br />

Commission, European Council <strong>and</strong> European Parliament <strong>and</strong> it is under development in all EU member<br />

states as well as in European Commission, DG TAXUD.<br />

1.2 Objectives of CDPS<br />

The overall long term objective of the CDPS project is to provide a system that will allow seamless flow of<br />

electronic information between all actors involved in the import, export or transit process, linking together<br />

the External-, National- <strong>and</strong> Common Domains (for EU-EFTA communications) as well as the Domain of<br />

other government agencies. To simplify <strong>and</strong> automate the administrative flow of the import, export or transit<br />

process will elevate the effectiveness of controls <strong>and</strong> expedite the flow of goods. All parties, traders,<br />

Macedonian customs authorities, other agencies <strong>and</strong> society will benefit from this development.<br />

From a legal/procedural, as well as from an IT point of view, there are similarities between the export<br />

regimes, transit regime (national transit, as well as common/Community transit system) <strong>and</strong> import regimes.<br />

Basing the export <strong>and</strong> import modules of CDPS on the technological achievements of transit module,<br />

especially NCTS, <strong>and</strong> the experience gained during the Single window, transit module, project will also<br />

allow Macedonian customs administration (MCA) to implement a defined <strong>and</strong> specified CDPS which takes<br />

into account both the national requirements, insofar as interface between the declarant <strong>and</strong> the office of<br />

export or import is concerned, <strong>and</strong> international requirements.<br />

The key element of the CDPS is to set the necessary conditions for an import, export <strong>and</strong> transit regimes on<br />

the basis of specifications (functional <strong>and</strong> technical level) which are compatible <strong>and</strong> in line with EU<br />

commonly agreed specifications for transit regime (NCTS), export regimes (ECS-AES) <strong>and</strong> import regimes<br />

(ICS-AIS) where:<br />

• the use of advanced computer systems <strong>and</strong> the electronic processing of data should, amongst other<br />

things, ensure a more efficient management of the export import, export <strong>and</strong> transit regimes than the<br />

paper-based system <strong>and</strong> should improve the efficiency of customs controls, particularly those relating to<br />

export, import <strong>and</strong> transit restrictions <strong>and</strong> to the entry or exit of goods, <strong>and</strong> their effectiveness in the fight<br />

against fraud in these areas;<br />

• new computerized procedures based on the use of modern information technology <strong>and</strong> electronic data<br />

interchange (EDI) are covered by adapted legal provisions to provide procedural, technical, legal<br />

certainty <strong>and</strong> for possible security-linked needs, if found necessary. With regard to the common <strong>and</strong><br />

comprehensive use of such a system in Macedonian customs administration (MCA), all system related<br />

procedures not directly impacting upon the trading community should be governed by guidelines.<br />

Page 12/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

• most of the products delivered <strong>and</strong>/or produced in context of transit regime (NCTS) for the exchange of<br />

messages via the Common Domain (within EU-EFTA common transit procedure) will be re-used after<br />

the accession of the Republic of Macedonia into the EU in order to limit the resources <strong>and</strong> the timescale<br />

acceptable for all participants involved; <strong>and</strong><br />

• in the first stage the Republic of Macedonia will be linked with EU <strong>and</strong> EFTA countries via a common<br />

network in order to exchange NCTS st<strong>and</strong>ard messages, wherever possible in real time, <strong>and</strong> in the<br />

second stage with EU member states in order to exchange ECS-AES or ICS-AIS st<strong>and</strong>ard messages.<br />

1.3 Scope of CDPS<br />

The CDPS will apply to the movement of goods released for import, export or transit regime, either covered<br />

by declarations made under the normal procedure, i.e. where a full declaration is submitted to the office of<br />

import/export/departure, or under the simplified procedure when goods are released for regime or the regime<br />

is ended:<br />

- incomplete or simplified import declarations or local clearance,<br />

- incomplete or simplified export declarations or local clearance,<br />

- authorized consignor or authorised consignee in transit regime.<br />

The scope of the CDPS will cover the lodgement of electronic or paper-based declarations (customs<br />

declaration, summary declaration as well as entry or exit summary declaration) from the trader´s External<br />

Domain to the National Domain of the customs office <strong>and</strong> the exchange of data of declarations between the<br />

Republic of Macedonia <strong>and</strong> EFTA countries or EU member states via Common Domain (on the day of<br />

accession into the Convention on a common transit procedure 15 or on the day of accession into the EU).<br />

The scope of the CDPS will also cover the lodgement of electronic entry or exit summary declaration from<br />

the trader’s External Domain to the National Domain of the customs office <strong>and</strong> the exchange of entry<br />

summary declaration information <strong>and</strong> risk information between the MS (at the latest on the day of the<br />

accession into the EU). In the last amendments of the Implementing Provisions, defining the necessary<br />

amendments of the <strong>Customs</strong> Code by Regulation (EC) 648/2005, there are new obligations in the way:<br />

- entry summary declaration shall be lodged at the customs office of entry,<br />

- exit summary declaration shall be lodged at the customs office of exit.<br />

1.4 Intended audience<br />

The intended audience are all stakeholders involved in the core CDPS process when goods are:<br />

- brought into the customs territory of Republic of Macedonia <strong>and</strong> the people who later on will establish<br />

the functional <strong>and</strong> technical specifications of the import module of CDPS,<br />

- taken off from the customs territory of Republic of Macedonia <strong>and</strong> the people who later on will establish<br />

the functional <strong>and</strong> technical specifications of the export module of CDPS,<br />

- carried through the customs territory of Republic of Macedonia <strong>and</strong> the people who later on will<br />

establish the functional <strong>and</strong> technical specifications of the transit module of CDPS.<br />

The intended audience are all stakeholders involved in the development of sub-applications linked to the<br />

CDPS, especially responsible for:<br />

- establishing the functional <strong>and</strong> technical specification for Authorisation sub-application <strong>and</strong> later on for<br />

capturing <strong>and</strong>/or management of the authorisations data,<br />

- establishing the functional <strong>and</strong> technical specification for Guarantee management sub-application <strong>and</strong><br />

later on for capturing <strong>and</strong>/or management of the guarantee data,<br />

- establishing the functional <strong>and</strong> technical specification for Risk analysis <strong>and</strong> risk management subapplication<br />

<strong>and</strong> later on for specification/creation <strong>and</strong>/or management of the risk profiles data,<br />

- establishing the functional <strong>and</strong> technical specification for Accounting management sub-application <strong>and</strong><br />

later on for management of the accounting system data,<br />

Page 13/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- establishing the functional <strong>and</strong> technical specification for Tarim (TARIC) sub-application <strong>and</strong> later on<br />

for capturing <strong>and</strong>/or management of the Tarim (TARIC) data,<br />

- establishing the functional <strong>and</strong> technical specification for National/European Binding Tariff Information<br />

<strong>and</strong> later on for capturing <strong>and</strong>/or management of the Binding Tariff Information data,<br />

- establishing the functional <strong>and</strong> technical specification for National/European Tariff quotas <strong>and</strong> ceilings<br />

sub-application (or module in Single window sub-application) <strong>and</strong> later on for capturing <strong>and</strong>/or<br />

management of the Tariff quotas <strong>and</strong> ceilings data,<br />

- establishing the functional <strong>and</strong> technical specification for European <strong>Customs</strong> Inventory of Chemical<br />

Substances sub-application <strong>and</strong> later on for management of the European <strong>Customs</strong> Inventory of<br />

Chemical Substances data,<br />

- establishing the functional <strong>and</strong> technical specification for European Autonomous Tariff Suspensions subapplication<br />

<strong>and</strong> later on for management of the European Autonomous Tariff Suspensions data,<br />

- establishing the functional <strong>and</strong> technical specification for European surveillance of data in the<br />

framework of import - export sub-application <strong>and</strong> later on for management of the European surveillance<br />

of data in the framework of import - export data,<br />

- establishing the functional <strong>and</strong> technical specification for Single electronic access point sub-application.<br />

1.5 Structure of this document<br />

After this introduction chapter the document is composed of 7 other chapters. Chapter 2 gives an overall<br />

description of the domains used for communication, chapter 3 describes the CDPS, chapter 4 the concerned<br />

sub-applications which should be developed in parallel with core CDPS, chapter 5 gives a technical<br />

requirements of CDPS, chapter 6 describes the phasing/milestones for development of CDPS, chapter 7<br />

gives the use-case models for main parts of CDPS, chapter 8 contains the annexes of this document.<br />

1.6 Terminology<br />

<strong>User</strong> Requirements refers to the features or attributes the CDPS system should have or how it should perform<br />

from the users’ perspective. The UR describes what the proposed new system will do, but nothing about<br />

how it will be built or implemented.<br />

There are different levels of requirements:<br />

a) <strong>User</strong> Requirements<br />

Narrative descriptions <strong>and</strong> diagrams showing the services the proposed system will deliver <strong>and</strong> its<br />

limitations.<br />

b) Functional Specifications<br />

A well structured document describing the system functionality in detail. The document can be used as a<br />

“contract” between the client <strong>and</strong> the people who will build the system. This document is mainly written for<br />

the system-end users, the system architects <strong>and</strong> the software developers.<br />

c) Technical Specifications (Software specification)<br />

A detailed description which will be the basis for system design <strong>and</strong> implementation. The document is<br />

mainly written for the system architects <strong>and</strong> the software developers.<br />

A common practice is to divide the requirements into functional <strong>and</strong> qualitative requirements. Qualitative<br />

requirements can also be called non-functional requirements or constraints.<br />

According to the European Commission st<strong>and</strong>ard for UR the key words “must”, “must not”, “required”,<br />

“shall”, “shall not”, “should”, “should not”, “recommended”, “may”, <strong>and</strong> “optional” in this document are to<br />

be interpreted as follows:<br />

Page 14/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

MUST<br />

This word, or the terms "REQUIRED" or "SHALL", means that the definition is an absolute requirement of<br />

the specification.<br />

MUST NOT<br />

This phrase, or the phrase "SHALL NOT", means that the definition is an absolute prohibition of the<br />

specification.<br />

SHOULD<br />

This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in particular<br />

circumstances to ignore a particular item, but the full implications must be understood <strong>and</strong> carefully weighed<br />

before choosing a different course.<br />

SHOULD NOT<br />

This phrase, or the phrase "NOT RECOMMENDED" means that there may exist valid reasons in particular<br />

circumstances when the particular behaviour is acceptable or even useful, but the full implications should be<br />

understood <strong>and</strong> the case carefully weighed<br />

MAY<br />

This word, or the adjective "OPTIONAL", means that an item is truly optional.<br />

1.7 Abbreviations used in this document<br />

AAR<br />

ATR<br />

AEO<br />

AES<br />

AIS<br />

CCN-CSI<br />

CDPS<br />

DDS<br />

DG TAXUD<br />

DTI<br />

DWS<br />

EAD<br />

EBTI<br />

ECS<br />

EDI<br />

EDIFACT<br />

EFTA<br />

END<br />

EORI<br />

EU<br />

EXD<br />

ICS<br />

IRU<br />

ITE<br />

LRN<br />

MCA<br />

MRN<br />

MS<br />

NCTS<br />

Anticipated Arrival Record<br />

Anticipated Transit Record<br />

Authorised Economic Operator<br />

Automated Export <strong>System</strong><br />

Automated Import <strong>System</strong><br />

Common Communication Network – Common <strong>System</strong> Interface<br />

<strong>Customs</strong> <strong>Declaration</strong> <strong>Processing</strong> <strong>System</strong><br />

Data Dissemination <strong>System</strong><br />

Directorate General for Taxation <strong>and</strong> <strong>Customs</strong> Union, European Commission<br />

Direct Trader Input<br />

Data Warehouse <strong>System</strong><br />

Export Accompanying Document<br />

European Binding Tariff Information<br />

Export Control <strong>System</strong><br />

Electronic Data Interchange<br />

International EDI st<strong>and</strong>ard developed under the United Nations<br />

European Free Trade Area<br />

Entry Summary <strong>Declaration</strong><br />

Economic Operators' Registration <strong>and</strong> Identification <strong>System</strong><br />

European Union<br />

Exit Summary <strong>Declaration</strong><br />

Import Control <strong>System</strong><br />

International Road Transport Union<br />

Integrated Tariff Environment<br />

Local Reference Number<br />

Macedonian <strong>Customs</strong> Administration<br />

Movement Reference Number<br />

EU member state<br />

New Computerised Transit <strong>System</strong><br />

Page 15/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

RDA<br />

REX<br />

RIF<br />

RMF<br />

RwEI<br />

SAD<br />

SD<br />

SEAP<br />

TAD<br />

TARIC<br />

Tarim<br />

TIN<br />

TPS<br />

UR<br />

XML<br />

WCO<br />

Reference Data application<br />

Registered Exporters<br />

Risk Information Form<br />

Risk Information Management <strong>System</strong><br />

Regimes with Economic Impact<br />

Single Administrative Document<br />

Summary <strong>Declaration</strong><br />

Single European Access Point<br />

Transit Accompanying Document<br />

Online customs tariff database<br />

Macedonian customs tariff database<br />

Trader Identification Number<br />

Transaction <strong>Processing</strong> <strong>System</strong><br />

<strong>User</strong> requirements<br />

Extensible Markup Language; a general-purpose specification for creating custom markup<br />

language<br />

World <strong>Customs</strong> Organisation (<strong>Customs</strong> Cooperation Council)<br />

The detailed list of abbreviations is available in another document delivered within this project (List of<br />

acronyms).<br />

1.8 Related documents<br />

• <strong>Customs</strong> Law 1<br />

• <strong>Customs</strong> Law Implementing Regulations 2<br />

• Rulebook on the Manner of Completing the <strong>Customs</strong> <strong>Declaration</strong> <strong>and</strong> the List of Codes which are<br />

being used 3<br />

• Implementing regulation for detailed criteria <strong>and</strong> the rules for implementing the relief from the<br />

payment of import duties, as well as value, quantity <strong>and</strong> type 4<br />

• Decision on the determination of types of goods subject to customs proceedings at specific Border<br />

Crossing Points 5<br />

• Implementing Regulation prescribing in more detail the conditions which must be complied with for<br />

goods to be subject to autonomous measures for reduction or suspension of import duties, the<br />

procedure for introduction of autonomous measures as well as their distribution or use 6<br />

• Decision on the paperless environment for customs <strong>and</strong> trade - 'Electronic <strong>Customs</strong> Decision' 7<br />

• Community <strong>Customs</strong> Code 8<br />

1 <strong>Customs</strong> Law published in Official Gazette of Republic of Macedonia No. 39/2005 <strong>and</strong> amended with Law published in Official Gazette of<br />

Republic of Macedonia No. 4/2008 from 10.1.2008<br />

2 <strong>Customs</strong> Law Implementing Regulation published in Official Gazette of Republic of Macedonia No. 66/2005 <strong>and</strong> amended with Law published in<br />

Official Gazette of Republic of Macedonia No. 73/2006 <strong>and</strong> amended with Law published in Official Gazette of Republic of Macedonia No.<br />

32/2007 from 18.5.2007<br />

3 Rulebook on the Manner of Completing the <strong>Customs</strong> <strong>Declaration</strong> <strong>and</strong> the List of Codes which are being used published in Official Gazette of<br />

Republic of Macedonia No. 97/2005<br />

4 Implementing regulation for detailed criteria <strong>and</strong> the rules for implementing the relief from the payment of import duties, as well as value, quantity<br />

<strong>and</strong> type published in Official Gazette of Republic of Macedonia No. 117/2005<br />

5 Decision on the determination of types of goods subject to customs proceedings at specific Border Crossing Points published in Official Gazette of<br />

Republic of Macedonia No. 111/2005<br />

6 Implementing Regulation prescribing in more detail the conditions which must be complied with for goods to be subject to autonomous measures<br />

for reduction or suspension of import duties, the procedure for introduction of autonomous measures as well as their distribution or use published<br />

in Official Gazette of Republic of Macedonia No. 119/2005<br />

7 Decision on the paperless environment for customs <strong>and</strong> trade - 'Electronic <strong>Customs</strong> Decision' No. 70/2008/EC published in EU Official Journal No.<br />

L 23 from 26.1.2008<br />

Page 16/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

• Community <strong>Customs</strong> Code Implementing Provisions 9<br />

• Modernised <strong>Customs</strong> Code 10<br />

• The Multi Annual Strategic Plan 11<br />

• Functional Transit <strong>System</strong> Specification, phase 4 of NCTS 12<br />

• Functional Transit <strong>System</strong> Specification – Automated Export <strong>System</strong> Addendum, AES-ECS 13<br />

• Functional Transit <strong>System</strong> Specification – Automated Import <strong>System</strong> Addendum, ICS 14<br />

• Convention on a common transit procedure 15<br />

• International Convention on the Simplification <strong>and</strong> Harmonisation of <strong>Customs</strong> Procedures 16<br />

• Guidelines to International Convention on the Simplification <strong>and</strong> Harmonisation of <strong>Customs</strong><br />

Procedures 17 .<br />

The following documents are applicable to this document:<br />

Ref. Identifier Title Version<br />

A01 CUD-SC01-DDNXA<br />

A02 TCE-L1-DDCOM<br />

A03 CUD-SC01-DDNTA<br />

A04 CUD-SC01-DDNIA<br />

Design Document for National Export<br />

Applications<br />

Design Document for Common Operations <strong>and</strong><br />

Methods<br />

Design Document for National Transit<br />

Applications<br />

Design Document for National Import<br />

Applications<br />

2.00-EN<br />

1.10-EN<br />

10.10-<br />

EN<br />

0.20-EN<br />

A05 CUD-SPEED-FSS SPEED Functional Specifications 1.00-EN<br />

A06 ETIC-FS-02 Single Portal for Entry or Exit of Data (SPEED) 05.01<br />

A07 SSS-e<strong>Customs</strong> Security<br />

Specifications<br />

A08 CUD-SC01-ECS2-CTP-<br />

DOC<br />

e<strong>Customs</strong> Security <strong>System</strong> Specifications<br />

Conformance Test Protocol for ECS Phase 2<br />

Table 1: Applicable Documents<br />

The following documents are of interest to the CDPS technical requirements:<br />

0.10-EN<br />

0.20-EN<br />

8 Council Regulation (EEC) No 2913/92 of the 12 October 1992 establishing the Community <strong>Customs</strong> Code<br />

9 Commission Regulation (EEC) No 2454/93 of 2 July 1993 laying down provisions for the Implementation of Council Regulation (EEC) No<br />

2913/92 establishing the Community <strong>Customs</strong> Code<br />

10 Regulation (EC) No 450/2008 of the European Parliament <strong>and</strong> of the Council of 23 April 2008 laying down the Community <strong>Customs</strong> Code<br />

(Modernised <strong>Customs</strong> Code) published in EU Official Journal No. L 145 from 4.6.2008<br />

11 TAXUD/477/2004 is published at:<br />

http://ec.europa.eu/taxation_customs/resources/documents/customs/policy_issues/e-customs_initiative/MASP_rev8.pdf<br />

12 DG TAXUD Working Document No.<br />

13 DG TAXUD Working Document No. TAXUD/1040/2006<br />

14 DG TAXUD Working Document No. TAXUD/1043/2006<br />

15 Convention on a common transit procedure is available at:<br />

http://eur-lex.europa.eu/smartapi/cgi/sga_doc?smartapi!celexapi!prod!CELEXnumdoc&lg=en&numdoc=21987A0813(01)&model=guicheti<br />

16 Revised Kyoto Convention is available at: http://www.wcoomd.org/kybodycontent.htm<br />

17 The guidelines to the revised Kyoto Convention are available in the World <strong>Customs</strong> Organisation.<br />

Page 17/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Ref. Identifier Title Version<br />

R01 FTSS – AES Addendum Automated Export <strong>System</strong> Addendum 1/2006<br />

Final<br />

R02 FTSS – NCTS Addendum Functional Transit <strong>System</strong> Specifications 4.00 as<br />

amended with Corrigendum 1/2007<br />

1/2007<br />

Final<br />

R03 FTSS – AIS Addendum Automated Import <strong>System</strong> Addendum 1/2006<br />

Rev.3<br />

R04 CUD-SC01-ECS2-SD The Scope of ECS Phase 2 2.00-EN<br />

R05 TCE-L1-SDCOM Scope Document Common Volume 1.00-EN<br />

R06 CSRD-<strong>System</strong><br />

Requirements Definition<br />

R07 CSMIS-<strong>System</strong><br />

Requirements Definition<br />

CS/RD <strong>System</strong> Requirements Definitions<br />

CS/MIS <strong>System</strong> Requirements Definitions<br />

3.10-EN<br />

3.20-EN<br />

R08 CUD-SC01-ICS-SD The Scope of ICS 1.21-EN<br />

R09 CUD-SC01-NCTS SEC<br />

<strong>and</strong> ENQ-SD<br />

The Scope of NCTS Phase 4<br />

R10 MASP-TAXUD/477/2004 Electronic <strong>Customs</strong> Multi-Annual Strategic Plan<br />

R11 AEO-FS-FSS<br />

AEO - Full <strong>System</strong> - Functional <strong>System</strong><br />

Specifications<br />

3.00-EN<br />

rev.8<br />

R12 CCN-COVW-GEN CCN/CSI <strong>System</strong> Overview EN12.00<br />

R13 TCE-TTSS-L1DOC-P32<br />

R14 CUD-SC01-EORI-SPM<br />

R15<br />

R16<br />

R17<br />

R18<br />

R19<br />

Technical Transit <strong>System</strong> Specifications for<br />

Phase 3.2<br />

2.00<br />

1.00-EN<br />

EORI <strong>System</strong> Process Model <strong>and</strong> Requirements 3.00-EN<br />

Taxation <strong>and</strong> <strong>Customs</strong> Union DG, CUST/DEV 1.00<br />

Project, “e<strong>Customs</strong> Technical Architecture<br />

Specification”<br />

Toni Stojanovski, Markku Oraviita, “<strong>Customs</strong> 0.8<br />

<strong>Declaration</strong> <strong>Processing</strong> <strong>System</strong>: Functional <strong>and</strong><br />

Technical Architecture”<br />

Toni Stojanovski, Markku Oraviita, “<strong>Customs</strong><br />

<strong>Declaration</strong> <strong>Processing</strong> <strong>System</strong>: Technical<br />

Specification”<br />

“Закон за податоците во електронски облик и<br />

електронски птпис”, “Сл. Весник на<br />

Р.Македонија” бр.34 од 3.05.2001<br />

<strong>Customs</strong> Directorate of the Republic of Croatia:<br />

IS Development Strategy<br />

Table 2: Reference Documents<br />

0.8<br />

1.1.6<br />

2 DOMAINS OF THE CDPS<br />

Page 18/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

We have domains for the different actors involved in the import, export <strong>and</strong> transit processes. The domains<br />

define clear interfaces between the actors involved <strong>and</strong> divide the responsibility. The domains identified are<br />

the External Domain, the National Domain, the Common Domain <strong>and</strong> the Domain of other government<br />

agencies on a national level. Communications within <strong>and</strong> between these domains in transit, export as well as<br />

export control system, import <strong>and</strong> import control system are described in the Annex 1 of this document (see<br />

Chapter 8).<br />

2.1 National Domain<br />

This covers the relationship between the <strong>Customs</strong> Offices of Republic of Macedonia <strong>and</strong> national system -<br />

CDPS. This domain is under the sole responsibility of the national customs administration concerned.<br />

2.2 External Domain<br />

This covers the relationship between the national customs administration <strong>and</strong> Traders. This domain is under<br />

the sole responsibility of national customs administration concerned. Within the External Domain, Traders<br />

interact with their national customs administration, which is the body responsible for specifying <strong>and</strong> setting<br />

up the interfaces for them.<br />

For the purpose of data capture by the respective customs office (office of export, office of exit, office of<br />

import, office of entry, office of departure or office of destination) four methods should be considered:<br />

• EDI – Electronic Data Interchange (XML, EDIFACT),<br />

• DTI – Direct Trader Input,<br />

• Internet application,<br />

• Data capture by the respective customs office.<br />

It is recommended that a commonly defined declaration message should be established in view of:<br />

- national customs legislation for SAD 3 ,<br />

- Appendix III Annexes D1, D2 of Convention on a common transit procedure 15 ,<br />

- Annex 30a of EU <strong>Customs</strong> Code Implementing Provisions 9 .<br />

The electronic customs declaration <strong>and</strong> other messages sent by a declarant (principal) to the respective<br />

customs office (office of export, office of exit, office of import, office of entry, office of departure or office<br />

of destination, <strong>and</strong> office of guarantee) shall be authenticated with e-signature according to the Articles 4 <strong>and</strong><br />

5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

The h<strong>and</strong> written signature of a declarant (principal) or his direct representative shall be replaced by e-<br />

signature according to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be<br />

registered together with the identification of a declarant / principal / his direct representative in the module<br />

for authorisation of e-communication in the Authorisation sub-application.<br />

The declaration data shall be validated by the system at the respective customs office (office of export, office<br />

of exit, office of import, office of entry, office of departure or office of destination) <strong>and</strong> further messages<br />

need to be in place in order to advise the declarant (principal) of the acceptance <strong>and</strong>/or the rejection of the<br />

declaration data. While these messages should be subject to common functional specification, their<br />

implementation is left to the responsibility of national customs administration, possibly taking advantage of<br />

the transit regime (NCTS procedures) in place.<br />

The electronic decision on release of goods for customs regime <strong>and</strong> all others electronic messages sent by the<br />

respective customs office (office of export, office of exit, office of import, office of entry, office of departure<br />

or office of destination, <strong>and</strong> office of guarantee) to the declarant (principal) shall be authenticated with e-<br />

signature of customs administration, according to the Article 109 para. 2 of <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

However, the Commission, as a depositor for the Convention on a common transit procedure 15 , <strong>and</strong> EFTA<br />

countries as well as EU member states have developed rules <strong>and</strong> guidelines to pave the way for<br />

Page 19/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

st<strong>and</strong>ardisation in the common transit regime, i.e. the Appendix III Annexes D1, D2, D3 <strong>and</strong> D4 of<br />

Convention on a common transit procedure 15 .<br />

However, the Commission <strong>and</strong> EU member states have developed rules <strong>and</strong> guidelines to pave the way for<br />

st<strong>and</strong>ardisation in the AES-ECS system, i.e. the Annexes 30a, 45c <strong>and</strong> 45d of EU <strong>Customs</strong> Code<br />

Implementing Provisions 9 .<br />

However, the Commission <strong>and</strong> EU member states have developed rules <strong>and</strong> guidelines to pave the way for<br />

st<strong>and</strong>ardisation in the AIS-ICS system, i.e. the Annexes 30a, 45c <strong>and</strong> 45d of EU <strong>Customs</strong> Code<br />

Implementing Provisions 9 .<br />

The data required for the messages will be captured within the export or import or transit declaration,<br />

processed <strong>and</strong> transmitted by the participating National Administrations' own systems. The information<br />

exchange between the exporter/consignor <strong>and</strong> the office of export or between the importer <strong>and</strong> the office of<br />

import or between principal in national transit regime should be implemented using the same type of<br />

messages <strong>and</strong> procedures common to NCTS (common/Community transit regime).<br />

2.3 Domains of the government agencies<br />

The domain of other government agencies is a very important part of the CDPS-scope. This requires<br />

electronic integrated processes with other government agencies involved in the entry, import <strong>and</strong> transit<br />

formalities. If not achieved there will be problem with delivery of seamless, predictable customs process (in<br />

export, import <strong>and</strong> transit operations) to the trade. This domain can also be regarded as <strong>and</strong> included in the<br />

External Domain.<br />

This covers the relationship between the <strong>Customs</strong> national system – CDPS <strong>and</strong> the systems or databases of<br />

the government agencies, e.g. Ministry of Finances, including Public Revenue Office, National Bank of the<br />

RM, Ministry of Interior, Ministry of Agriculture, Forestry <strong>and</strong> Water Supply, Ministry of Health, Ministry<br />

of Environment <strong>and</strong> Physical Planning, Ministry of transport <strong>and</strong> Communications, Ministry of Culture,<br />

Ministry of Economy, Directorate for Radiation Security, Institute for st<strong>and</strong>ardisation, State Statistical<br />

Office, Central Registry Office.<br />

Page 20/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

2.4 Common Domain (only for EU-EFTA communication)<br />

The respective parts of CDPS (NCTS, AES-ECS, AIS-ICS) will use the existing Common Domain for the<br />

electronic transfer of data between customs offices.<br />

The NCTS shall cover the common transit of goods transported from one contracting party of the<br />

Convention on a common transit procedure 15 via or into another contracting party – EU or EFTA country<br />

(direct transit). The NCTS shall also cover the common transit of goods transported from one contracting<br />

party of the Convention on a common transit procedure 15 through third country (neither EU nor EFTA<br />

country) via or into another contracting party – EU or EFTA country (indirect transit). The core element of<br />

the NCTS shall be the information exchange in the Common Domain between the office of departure, the<br />

office of destination, the office of transit <strong>and</strong> office of guarantee to:<br />

• verify at the office of guarantee whether a declared guarantee is valid, can be used by this principal, has<br />

sufficient amount of reference amount before the release of goods for common transit regime at the<br />

office of departure (where the office of guarantee <strong>and</strong> the office of departure are located in different<br />

countries);<br />

• tie up the security amount of the used guarantee at the office of guarantee for goods for which common<br />

transit formalities have been completed at the office of departure (where the office of guarantee <strong>and</strong> the<br />

office of departure are located in different countries);<br />

• inform the office of destination of the anticipated arrival of goods for which common transit formalities<br />

have been completed at the office of departure;<br />

• inform the office(s) of transit of the anticipated transit of goods for which common transit formalities<br />

have been completed at the office of departure;<br />

• h<strong>and</strong>le diversions (change of office of transit or destination);<br />

• inform the office of departure of presenting of goods at office of transit;<br />

• inform the office of departure of delivery of goods at office of destination;<br />

• inform the office of departure of control results;<br />

• inform the office of guarantee of discharging the common transit regime; <strong>and</strong><br />

• h<strong>and</strong>le discrepancies.<br />

The AES-ECS shall cover the export of goods transported from one EU member state (office of export) via<br />

another EU member state (office of exit) – indirect exportation. Taking into account that national customs<br />

administration will develop functions for both office of export <strong>and</strong> exit, direct exportation is implicitly<br />

covered by the system, as is the re-exportation of non-Community goods, in circumstances where an export<br />

or summary declaration is required. The core element of the ECS shall be the information exchange in the<br />

Common Domain between the office of export <strong>and</strong> the office of exit to:<br />

• inform the office of exit of the anticipated arrival of goods for which export formalities have been<br />

completed at the office of export;<br />

• h<strong>and</strong>le diversions;<br />

• inform the office of export of confirmation of exit <strong>and</strong>/or control results including the date of exit from<br />

the customs territory of the European Union; <strong>and</strong><br />

• h<strong>and</strong>le partial <strong>and</strong> consolidated shipments.<br />

The AIS-ICS shall cover the export of goods transported into one EU member state (office of import) via<br />

another EU member state (office of entry) – indirect importation. Taking into account that national customs<br />

administration will develop functions for both office of import <strong>and</strong> entry, direct importation is implicitly<br />

covered by the system in circumstances where an import or entry summary declaration or summary<br />

declaration is required. The core element of the AIS-ICS shall be the information exchange in the Common<br />

Domain between the office of entry <strong>and</strong> the office of import:<br />

• inform the office of first entry of the anticipated arrival of goods with entry summary declaration;<br />

• inform the office of entry (first <strong>and</strong> subsequent) of the arrival of goods with the arrival notification;<br />

• h<strong>and</strong>le diversions;<br />

• inform the office of subsequent entry of risk profiles linked to the goods with entry summary declaration.<br />

Page 21/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

The Common Domain is the domain containing common databases <strong>and</strong> applications by the Commission, as<br />

well as the communication between the MS.<br />

3 CDPS – MAIN APPLICATION<br />

3.1 Transit regime (NCTS)<br />

3.1.1 Trade <strong>Customs</strong> office of departure<br />

3.1.1.1 Electronic transit declaration<br />

- Lodging of electronic customs declaration is possible according to the Article 71 para. b) <strong>and</strong> Article 89<br />

of <strong>Customs</strong> Law 1 .<br />

- Electronic lodging of customs declaration for transit regime by a principal or his direct representative<br />

shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a principal or his direct representative shall be replaced by e-signature<br />

according to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be<br />

registered together with the identification of a principal (or his direct representative) in the module for<br />

authorisation of e-communication in the Authorisation sub-application.<br />

- Lodging of electronic customs declaration for transit regime is obligatory for granting the simplified<br />

procedure of authorised consignor according to the Article 271 para. 1 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- Lodging of electronic customs declaration for transit regime is obligatory for granting the simplified<br />

procedure of authorised consignor according to the Article 71 para. 1 of Appendix I of Convention on a<br />

common transit procedure 12 .<br />

- It is assumed that at the time of lodging of electronic transit declaration, the goods are already loaded to<br />

the loading compartment of means of transport, they are ready to be presented to the customs office of<br />

departure <strong>and</strong> they are ready for placing for transit regime.<br />

- Automated initial checks of electronic customs declaration shall cover:<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application,<br />

o filling in the data-elements or data-groups (boxes of declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of transit licences through the data from licence’s<br />

module of Single window sub-application.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure (if it is used)<br />

through the data from modules of Authorisation sub-application shall cover the authorisation of:<br />

o simplified procedure authorised consignor,<br />

o simplified procedure use of special seals,<br />

o simplified procedure of exemption regarding prescribed itinerary.<br />

- Automated check of guarantee through data from transit module of Guarantee management system subapplication<br />

shall cover the existence, validity, authorisation by principal with access code (PIN),<br />

sufficient amount of guarantee (at least on line management of comprehensive guarantees <strong>and</strong> individual<br />

guarantees with vouchers, management of individual guarantee is also appropriate).<br />

- The electronic transit declaration shall be registered with MRN (Movement Reference Number) by the<br />

customs office of departure if all above automated checks passed successfully. This MRN shall be<br />

Page 22/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

electronically notified to a principal. Authentication of this notification shall be with an e-signature of<br />

customs administration, according to the Article 109 para. 2 of <strong>Customs</strong> Law implementing Regulation 2 .<br />

- If any automatic checks didn’t pass successfully the transit declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be electronically notified to a principal. Authentication<br />

of this notification shall be with an e-signature of customs administration, according to the Article 109<br />

para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . Receiving this information a principal shall:<br />

o amend his refused transit declaration, sign it (with his e-signature) <strong>and</strong> send it (with same Local<br />

Reference Number - LRN) electronically again to the customs office of departure, or<br />

o send a new electronic transit declaration to the customs office of departure (with new LRN).<br />

3.1.1.2 Paper transit declarations<br />

- Lodging of paper customs transit declaration is possible in prescribed forms:<br />

o according to Article 105 para. 2 of <strong>Customs</strong> Law 1 in the form of SAD, TIR Carnet, ATA Carnet,<br />

form 302 or postal declaration,<br />

o according to Articles 277 <strong>and</strong> 278 of <strong>Customs</strong> Law Implementing Regulation 2 in the form of CIM<br />

Consignment Note,<br />

o according to Articles 290 <strong>and</strong> 292 of <strong>Customs</strong> Law Implementing Regulation 2 in the form of TR<br />

Transfer Note,<br />

o according to Articles 305 <strong>and</strong> 292 of <strong>Customs</strong> Law Implementing Regulation 2 in the form of the<br />

goods manifest (for goods transported by air).<br />

- Data of paper customs transit declaration shall be:<br />

o keyed in to the CDPS by a customs officer at the customs office of departure, or<br />

o electronically lodged to the customs office of departure in parallel with the paper customs transit<br />

declaration <strong>and</strong> it is not necessary to be approved by customs authorities.<br />

- The customs officer shall have a possibility for temporary storage of unfinished entry of transit<br />

declaration. The MCA shall set up the time limit for this temporary storage of unfinished transit<br />

declaration.<br />

- It is assumed that at the time of lodging of paper transit declaration, the goods are already loaded to the<br />

loading compartment of means of transport, presented to the customs authorities <strong>and</strong> they are ready for<br />

placing for transit regime.<br />

- Automated initial checks of data of paper customs transit declaration:<br />

o filling in the data-elements or data-groups (boxes of declaration) specified for each type of<br />

customs declaration,<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups <strong>and</strong><br />

specified for each type of customs declaration.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls<br />

specified for each type of transit declaration).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of transit licences via data from licences module of<br />

Single window sub-application.<br />

- Automated check of guarantee via data from transit module of Guarantee management system subapplication,<br />

i.e. existence, validity, authorisation by principal with access code (PIN), sufficient amount<br />

of guarantee (at least on line management of comprehensive guarantees <strong>and</strong> individual guarantees with<br />

vouchers, management of individual guarantee is also appropriate), cross-check via a list of invalid TIR<br />

Carnets distributed by IRU.<br />

- The paper transit declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number)<br />

by the customs office of departure if all above automated checks passed successfully.<br />

Page 23/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- If any automatic checks didn’t pass successfully the transit declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified by a customs officer to a principal (oral or<br />

written notification). Receiving this information a principal shall:<br />

o amend his refused declaration <strong>and</strong> lodge it (with same LRN) again to the customs office of<br />

departure, or<br />

o lodge a new transit declaration to the customs office of departure (with new LRN).<br />

3.1.1.3 Documents to accompany the transit declaration<br />

- Necessary documents to accompany the transit declaration shall be lodged by a principal to the office of<br />

departure according to the Article 72 para. 2 of <strong>Customs</strong> Law 1 <strong>and</strong> Article 126 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 . The customs office of departure may dispense with the presentation of these<br />

documents at the time of completion of the formalities at customs office of departure.<br />

- The documents to accompany the transit declaration shall be lodged by a principal to the office of<br />

departure in electronic or paper form.<br />

- The electronic form of documents to accompany the transit declaration shall be authenticated with<br />

electronic signature of a principal. The delivery <strong>and</strong> acceptance of electronic form of documents to<br />

accompany the transit declaration shall be electronically notified to a principal by customs office of<br />

departure with information about the acceptance of transit declaration. Authentication of this notification<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

- The electronic transit declaration shall be accepted by the customs office of departure, when the<br />

documents to accompany the transit declaration (in the paper form) are presented at that customs office<br />

with the goods to be released for the transit regime.<br />

- When the simplified procedure authorised consignor is used the documents to accompany the transit<br />

declaration shall be available for customs at the principal’s premise.<br />

3.1.1.4 Acceptance, customs controls, modifications, rectifications <strong>and</strong> cancellation of transit declaration<br />

- The transit declaration shall be accepted by the customs office of departure when:<br />

o all above automatic checks passed successfully,<br />

o all documents to accompany the transit declaration are lodged by a principal to that customs office or<br />

the waiver for lodging the documents to accompany the transit declaration was granted or the<br />

simplified procedure authorised consignor is used,<br />

o the goods are presented to that customs office.<br />

- In case that the transit declaration was lodged electronically, this MRN shall be electronically notified to<br />

a principal. Authentication of this notification shall be with an e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . In case that the<br />

transit declaration was not lodged electronically, the acceptance of transit declaration with this MRN<br />

shall be notified (oral notification) to a principal at the customs office of departure.<br />

- The registered or accepted transit declaration can be changed by a principal before the decision on a<br />

control of goods is taken. When transit declaration was registered or accepted by the customs office of<br />

departure, this transit declaration can be:<br />

o modified by an electronic message (with MRN <strong>and</strong> same LRN) sent to the customs office of<br />

departure, or<br />

o changed or amended by a new transit declaration which shall be sent to the customs office of<br />

departure (old transit declaration shall be cancelled by another electronic message),<br />

o cancelled by a message sent to the customs office of departure.<br />

Page 24/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Any modification or cancellation done by an electronic message shall be confirmed by the customs<br />

office of departure with an electronic message. Authentication of this decision shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

- After the acceptance of transit declaration by the customs office of departure the decision on control<br />

shall be taken by a customs officer at the customs office of departure. The Risk analysis <strong>and</strong> risk<br />

management system sub-application shall be used for automated evaluation of possible risks.<br />

- If NCTS (CDPS) is also used for the purpose of safety <strong>and</strong> security, then full safety <strong>and</strong> security related<br />

risk analysis for all the goods shall be performed additionally within the prescribed time limits (after the<br />

change of national customs legislation or after the accession into EU) - see part 3.1.7 of this<br />

document.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

departure to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o principal’s approval of amendment of transit declaration based on the discovered discrepancies,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- When decision on control of goods is taken, the transit declaration cannot be changed, modified,<br />

amended or cancelled at the customs office of departure. The results of control shall be registered at this<br />

customs office.<br />

- Based on the customs control, the declared goods can be released for transit regime or the transit<br />

declaration shall be modified, changed or cancelled.<br />

3.1.1.5 Cancellation of transit declaration or transit regime<br />

- The cancellation of a transit declaration (before the decision on release of goods is taken) or a transit<br />

regime (i.e. the decision on release of goods for transit regime) shall be initiated either by a principal or<br />

by the customs office of departure (annulment/revocation of transit declaration).<br />

- The cancellation of transit declaration or transit regime by a principal shall be initiated in:<br />

o electronic form, i.e. by an electronic message sent by a principal to the customs office of departure,<br />

o paper form lodged by a principal at the customs office of departure.<br />

- The registered or accepted transit declaration shall be cancelled by an electronic message sent to the<br />

customs office of departure before the decision on control of goods is taken or after the customs control.<br />

- The transit regime, i.e. the decision on release of goods for transit regime, shall be cancelled by an<br />

electronic message sent to the customs office of departure before the presenting the goods at:<br />

o the customs office of transit, i.e. before the message that goods have been presented at the customs<br />

office of transit is delivered to the customs office of departure (for common/Community transit<br />

regime),<br />

o the customs office of destination, i.e. before the message that goods have been presented at the<br />

customs office of destination is delivered to the customs office of departure (national transit regime).<br />

- The both cancellations done by an electronic message shall be confirmed by the customs office of<br />

departure with an electronic message. Authentication of this decision shall be with an e-signature of<br />

customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 . The cancellation done in paper form shall be confirmed by the customs office of departure<br />

in paper form.<br />

Page 25/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The cancellation of a transit declaration (before the decision on release of goods is taken) or a transit<br />

regime (i.e. the decision on release of goods for transit regime) initiated by a principal in written form<br />

shall be confirmed by the customs office of departure by a decision issued in written form.<br />

- When the <strong>Customs</strong> Officer at the customs office of departure accepts the request for cancellation of a<br />

transit declaration (i.e. before the decision on release of goods is taken), this means that the declared<br />

customs office(s) of transit (for common/Community transit regime) <strong>and</strong> the declared customs office of<br />

destination have not been electronically notified of the release for transit regime <strong>and</strong> therefore customs<br />

office of departure shall not inform this(these) customs office(s) about the cancellation.<br />

3.1.1.6 Consultation of the status of transit declaration<br />

- A customs officer with an appropriate level of authorisation <strong>and</strong> access to NCTS part of CDPS at any<br />

customs office, may request the movement information for a movement with a given MRN, i.e. the<br />

details of transit declaration <strong>and</strong> up-dated information about the status of transit operation. This includes<br />

the case of an en-route control, if access to the NCTS is available.<br />

- A principal or his direct representative with access to web site of Macedonian customs administration<br />

may request the transit movement information for a movement with a given MRN. <strong>System</strong> (NCTS) shall<br />

provide him via this web site with up-dated information about the status of transit operation, especially<br />

whether:<br />

o transit declaration was registered <strong>and</strong> accepted (when <strong>and</strong> where),<br />

o goods were released for transit regime (when <strong>and</strong> where),<br />

o goods were presented at the customs office of exit (when <strong>and</strong> where), if the transit declaration was<br />

also used for safety <strong>and</strong> security purposes,<br />

o goods passed the customs office(s) of transit (when <strong>and</strong> where),<br />

o goods were presented at the customs office of destination (when <strong>and</strong> where),<br />

o control results were sent from the customs office of destination (when, where <strong>and</strong> result),<br />

o transit regime was discharged by the customs office of departure.<br />

3.1.2 Release of goods for transit regime<br />

3.1.2.1 Use of st<strong>and</strong>ard procedure<br />

- The decision on release of goods for transit regime can be issued by the customs office of departure<br />

using the st<strong>and</strong>ard procedure or simplified procedure of authorised consignor. The usage of simplified<br />

procedure authorised consignor is described bellow – see part 3.1.2.2 of this document.<br />

- In case that the transit declaration was lodged electronically <strong>and</strong> the transit declaration was registered<br />

with MRN, this MRN is after that used for identification of that declaration during all next<br />

communication (principal <strong>and</strong> customs office of departure <strong>and</strong> vice versa, customs office of departure<br />

<strong>and</strong> customs office of destination <strong>and</strong> vice versa, customs office of departure <strong>and</strong> customs office(s) of<br />

transit <strong>and</strong> vice versa (in common/Community transit regime)).<br />

- In case that the transit declaration was lodged electronically, the decision on release of goods for transit<br />

regime is issued by the customs office of departure electronically <strong>and</strong> it is electronically sent to the<br />

principal. Authentication of this decision shall be with an e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . At that time the<br />

Transit Accompanying Document 18 <strong>and</strong> List of Items 19 (hereinafter called “Transit Accompanying<br />

Document”), which shall conform to the specimens in Annexes D3 <strong>and</strong> D5 of Appendix III of<br />

Convention on a common transit procedure, 15 shall be:<br />

o printed out by the customs office of departure,<br />

18 The new annex to the <strong>Customs</strong> Law Implementing Regulation 2 containing the Transit Accompanying Document shall be added.<br />

19 The new annex to the <strong>Customs</strong> Law Implementing Regulation 2 containing the List of Items shall be added.<br />

Page 26/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o verified by a customs officer from the customs office of departure with his/her h<strong>and</strong>-written<br />

signature <strong>and</strong> personal customs stamp (a h<strong>and</strong>-written signature <strong>and</strong> personal customs stamp can be<br />

replaced by a code printed in box D of Transit Accompanying Document), <strong>and</strong><br />

o issued to the principal or his direct representative (person who presented the goods to the customs<br />

office of departure).<br />

- In case that the transit declaration was lodged electronically, the decision that the goods shall not be<br />

released for transit regime is issued by the customs office of departure electronically <strong>and</strong> it is<br />

electronically sent to the principal. Authentication of this decision shall be with an e-signature of<br />

customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

- In case that the transit declaration was not lodged electronically, the decision on release of goods for<br />

transit regime is issued by the customs office of departure in the paper form, i.e. in the form of:<br />

o Transit Accompanying Document, when the transit declaration was lodged in the form of SAD<br />

(according to the Article 236 paras. 1 <strong>and</strong> 2 of <strong>Customs</strong> Law Implementing Regulation 2 ),<br />

o vouchers No 1 <strong>and</strong> 2 of TIR Carnet, when the transit declaration was lodged in the form of TIR<br />

Carnet (according to Article 105 para. 2 of <strong>Customs</strong> Law 1 ), accompanied by Transit Accompanying<br />

Document (see part 3.1.12 of this document concerning the NCTS/TIR),<br />

o transit sheets (2 blue pages of ATA Carnet), when the transit declaration was lodged in the form of<br />

ATA Carnet (according to Article 105 para. 2 of <strong>Customs</strong> Law 1 ),<br />

o form 302, when the transit declaration was lodged in the form of form 302 (according to Article 105<br />

para. 2 of <strong>Customs</strong> Law 1 ),<br />

o postal declaration, when the transit declaration was lodged in the form of postal declaration<br />

(according to Article 105 para. 2 of <strong>Customs</strong> Law 1 ),<br />

o CIM Consignment Note, when the transit declaration was lodged in the form of CIM Consignment<br />

Note (according to Articles 277 <strong>and</strong> 278 of <strong>Customs</strong> Law Implementing Regulation 2 ),<br />

o TR Transfer Note, when the transit declaration was lodged in the form of TR Transfer Note<br />

(according to Articles 290 <strong>and</strong> 292 of <strong>Customs</strong> Law Implementing Regulation 2 ),<br />

o goods manifest, when the transit declaration was lodged in the form of goods manifest (according to<br />

Articles 305 <strong>and</strong> 292 of <strong>Customs</strong> Law Implementing Regulation 2 ).<br />

- The decision on release of goods for transport regime issued in the paper form shall be authenticated by<br />

the customs officer from customs office of departure with his h<strong>and</strong> written signature <strong>and</strong> his personal<br />

customs stamp.<br />

3.1.2.2 Use of simplified procedure of authorised consignor<br />

- Simplified procedure authorised consignor cannot be used with paper declaration for transit regime<br />

according to the Article 271 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 . The rules <strong>and</strong> processes<br />

described in part 3.1.1.1 of this document are used within the usage of simplified procedure of authorised<br />

consignor.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure authorised<br />

consignor through the data from modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised place, where goods are available, via code of this place (given in the authorisation),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for presenting the goods at the customs office of destination (given in the<br />

authorisation),<br />

o authorised country of final consignor or consignee (the list of prohibited countries is given in the<br />

authorisation),<br />

Page 27/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o identification of special seals (if they are used), via the serial number of the special seal (given in<br />

the authorisation),<br />

o number of authorised guarantee (GRN), i.e. a comprehensive guarantee or a comprehensive<br />

guarantee waiver shall be used (given in the authorisation).<br />

- When the simplified procedure authorised consignor is used the documents to accompany the transit<br />

declaration shall be available for customs at the principal’s premise. This condition is set up in the<br />

authorisation of simplified procedure authorised consignor issued by Macedonian customs authorities.<br />

- When all the above automated checks passed successfully, the electronic transit declaration shall be<br />

accepted with MRN (Movement Reference Number) by the customs office of departure. This MRN shall<br />

be electronically notified to a principal. Authentication of this notification shall be with an e-signature of<br />

customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

- A principal shall not wait for the authorisation for loading of goods to the loading compartment of means<br />

of transport. It is assumed that at the time of lodging of transit declaration, the goods are already loaded<br />

to the loading compartment of means of transport <strong>and</strong> they are ready for placing for transit regime.<br />

- The goods are loaded to the loading compartment of means of transport <strong>and</strong> they are ready for releasing<br />

for transit regime at the authorised place when the electronic transit declaration is lodged. This place is<br />

registered <strong>and</strong> authorised within the authorisation of simplified procedure authorised consignor.<br />

- The customs authorities (customs office of departure within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure authorised consignor within<br />

the time limit (timer for automatic release of goods) set up in the within the authorisation of simplified<br />

procedure authorised consignor.<br />

- When the decision on control of goods which have been declared within the simplified procedure<br />

authorised consignor is taken, the notification of this control shall be electronically sent to a principal or<br />

his representative (to a person who lodge the transit declaration). Authentication of this notification of<br />

control shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 . This notification shall be sent at the end of the time limit (timer<br />

for automatic release of goods) set up in the authorisation to give a time to the customs authorities<br />

responsible for this control to be present at the authorised place, where the goods are available, before<br />

the notification is sent to a principal or his representative (to a person who lodge the transit declaration).<br />

At that time the timer for automatic release of goods shall be stopped.<br />

- When the timer for automatic release of goods expired <strong>and</strong> no decision on control of goods was taken,<br />

the goods are automatically released for transit regime. The decision on release of goods for transit<br />

regime shall be electronically sent to the principal or his representative at that moment. Authentication of<br />

this decision shall be with an e-signature of customs administration, according to the Article 109 para. 2<br />

of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- Based on the decision on release of goods for transit regime which was electronically sent to the<br />

principal or his representative by the customs office of departure, the principal shall print out the Transit<br />

Accompanying Document – TAD, which will follow the goods to the customs office of destination. The<br />

permission for printing out of TAD by the principal is given according to the Article 236 para. 2 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 . The TAD shall be authenticated by the stamp of authorised<br />

consignor, which could be replaced by the imprint done within the printing of TAD.<br />

- The transit operation can start immediately when the decision on release of goods for transit regime is<br />

electronically delivered to the principal or his representative <strong>and</strong> when the TAD is printed <strong>and</strong><br />

authenticated.<br />

3.1.3 <strong>Customs</strong> office of departure <strong>Customs</strong> office of guarantee<br />

3.1.3.1 Check of the guarantee<br />

Page 28/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The guarantees shall be checked <strong>and</strong> registered based on data of the accepted transit declaration.<br />

- When the necessary data is not available the amount of duties <strong>and</strong> taxes in risk is presumed to be EUR<br />

7000 in corresponding denar value, according to the Article 256 para. 1 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 . According to the Article 226 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 (in case of<br />

individual guarantee) or to the Article 256 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 (in case of<br />

comprehensive guarantee) the amount of duties <strong>and</strong> taxes in risk is calculated manually by the customs<br />

officer or automatically when the Tariff code is used within the transit declaration.<br />

- transit module of CDPS (NCTS) shall assist in offering the minimum rate for sensitive goods:<br />

o in case of national transit regime see the Annex 28 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o in case of common transit regime see the Annex I of Appendix I of the Convention on a common<br />

transit procedure 15 .<br />

- transit module of CDPS (NCTS) shall assist in:<br />

o calculation of amount of duties <strong>and</strong> taxes based on of the highest import duties applicable to goods<br />

of the same kind in the Republic of Macedonia, as well as other duties <strong>and</strong> taxes the customs<br />

authorities are authorised to collect in accordance with the provisions regulating such duties <strong>and</strong><br />

taxes, when the Tariff code is used within the transit declaration, or<br />

o a pre-defined default amount of duties <strong>and</strong> taxes, i.e. EUR 7000 in corresponding denar value within<br />

the limits of Article 256 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 (in case of national<br />

transit regime) or Article 56 of Appendix I of the Convention on a common transit procedure 15 (in<br />

case of common transit regime).<br />

- The calculated amount of duties <strong>and</strong> taxes in risk shall be registered in transit module of CDPS (NCTS).<br />

- Transit module of CDPS (NCTS) with Guarantee management system sub-application shall be able to<br />

carry out:<br />

o on line management of comprehensive guarantees, especially to check:<br />

→ existence of comprehensive guarantee, i.e. the comprehensive guarantee was registered by the<br />

customs office of guarantee <strong>and</strong> it is still valid,<br />

→ scope of validity of comprehensive guarantee, i.e. it is valid for declared goods (a special<br />

comprehensive guarantee shall be issued for high risky goods listed in Annex 28 of <strong>Customs</strong><br />

Law Implementing Regulation 2 ),<br />

→ if the authorisation for comprehensive guarantee was granted to the principal,<br />

→ validity of access code (PIN), issued to the principal for proving his right to use this guarantee,<br />

→ if the actual amount of reference amount does not exceed the reference amount of<br />

comprehensive guarantee,<br />

o on line management of comprehensive guarantee waivers, especially to check:<br />

→ existence of comprehensive guarantee waiver, i.e. the comprehensive guarantee waiver was<br />

granted by the customs office of guarantee <strong>and</strong> it is still valid,<br />

→ scope of validity of comprehensive guarantee, i.e. it is valid for declared goods (a<br />

comprehensive guarantee waiver shall not be issued for high risky goods listed in Annex 28 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 ),<br />

→ if the authorisation for comprehensive guarantee waivers was granted to the principal,<br />

→ validity of access code (PIN), issued to the principal for proving his right to use this<br />

comprehensive guarantee waiver,<br />

→ if the actual amount of reference amount does not exceed the reference amount of<br />

comprehensive guarantee waiver,<br />

o on line management of individual guarantee with vouchers, especially to check:<br />

→ existence of individual guarantee with vouchers, i.e. the authorisation to issue individual<br />

guarantee with vouchers was granted by the customs office of guarantee to the guarantor <strong>and</strong> it is<br />

still valid,<br />

→ scope of validity of individual guarantee with vouchers, i.e. it is valid for declared goods (a<br />

individual guarantee with vouchers may not be issued for high risky goods listed in Annex 28 of<br />

Page 29/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

<strong>Customs</strong> Law Implementing Regulation 2 - see Article 228 para. 3 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ),<br />

→ if the voucher was issued by a guarantor to the principal,<br />

→ validity of access code (PIN), issued by a guarantor to the principal for proving his right to use<br />

this voucher,<br />

→ if the actual total amount of issued <strong>and</strong> still used vouchers does not exceed the maximum amount<br />

of guarantee authorised by the customs office of guarantee,<br />

o on line management of individual guarantee, especially to check:<br />

→ existence of individual guarantee, i.e. the individual guarantee was accepted <strong>and</strong> registered by<br />

the customs office of guarantee <strong>and</strong> it is still valid (was not used),<br />

→ if the individual guarantee was registered for this principal,<br />

→ scope of validity of individual guarantee, i.e. it is valid for declared goods (the individual<br />

guarantee was accepted <strong>and</strong> registered by the customs office of guarantee for certain goods),<br />

→ validity of access code (PIN), issued to the principal for proving his right to use this individual<br />

guarantee.<br />

- Transit module of CDPS (NCTS) shall be able to communicate via common domain with the Guarantee<br />

management system sub-application which is located in different state, where the common transit regime<br />

is used (only for common/community transit regime).<br />

3.1.3.2 Register of guarantee usage<br />

- Where the checks described above in the part 3.1.3.2 of this document successfully passed, the<br />

Guarantee management system sub-application shall:<br />

o register the use of guarantee together with the MRN issued at the customs office of departure <strong>and</strong><br />

with the amount of calculated duties <strong>and</strong> taxes,<br />

o notify electronically the customs office of departure that the usage of guarantee is accepted <strong>and</strong><br />

registered.<br />

- Where the checks described above in the part 3.1.3.2 of this document did not successfully pass, the<br />

Guarantee management system sub-application shall notify electronically the customs office of departure<br />

that the usage of guarantee was not accepted. The customs office of departure having this information<br />

shall not release the declared goods for the transit regime.<br />

3.1.3.3 Writing off the guarantee<br />

- Where the goods have been presented at the customs office of destination the electronic notification is<br />

sent from this office to the customs office of departure. In case that the comprehensive guarantee or the<br />

comprehensive guarantee waiver was used, the customs office of departure based on this information<br />

shall notify that to the customs office of guarantee with the request for credit of a used part of reference<br />

amount.<br />

- Where the transit regime has been discharged (i.e. the moment when the customs office of departure is in<br />

a position to establish, on the basis of a comparison of the data available to this customs office <strong>and</strong> those<br />

available to the customs office of destination, that the regime has ended correctly) the customs office of<br />

departure shall notify that to the customs office of guarantee with the request for release of a used<br />

guarantee.<br />

3.1.4 <strong>Customs</strong> office of departure <strong>Customs</strong> office of transit<br />

3.1.4.1 Anticipated Transit Record<br />

- Where the declared good have been released for transit regime by the customs office of departure, this<br />

office shall notify that to the customs office(s) of transit with electronic message “Anticipated Transit<br />

Page 30/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Record” sent via common domain, according to the Article 45 of Appendix I of the Convention on a<br />

common transit procedure 15 .<br />

- The customs office of transit shall carry out the necessary risk analysis in advance with the Risk analysis<br />

<strong>and</strong> risk management system sub-application on the data of transit declaration received with “Anticipated<br />

Transit Record” message. The decision on control of goods shall be taken when goods are presented at<br />

this customs office.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

transit to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- The results of control shall be registered at this customs office.<br />

- Where the goods released for transit regime are presented at the declared customs office of transit with<br />

the Transit Accompanying Document (TAD) <strong>and</strong> the goods entry to the customs territory through the<br />

customs office of transit, this customs office shall notify that to the customs office of departure with an<br />

electronic message sent via common domain. This message shall contain the customs control results<br />

done at customs office of transit, including the discrepancies, if any have been discovered.<br />

- Where the goods released for transit regime are presented at the different customs office, than originally<br />

declared customs office of transit, with the Transit Accompanying Document (TAD), the new customs<br />

office of transit shall:<br />

o ask for the data at the customs office of departure with an electronic message sent via common<br />

domain,<br />

o carry out the necessary risk analysis with the Risk analysis <strong>and</strong> risk management system subapplication,<br />

when “Anticipated Transit Record” message is delivered,<br />

o decide on the possible control of goods,<br />

o allow to the goods entry to the customs territory through this customs office,<br />

o notify that entry to the customs office of departure with an electronic message sent via common<br />

domain.<br />

3.1.4.2 Transit Accompanying Document<br />

- Where the goods released for transit regime are presented at the declared customs office of transit, the<br />

Transit Accompanying Document (TAD) shall be presented by a carrier.<br />

- The existence of the movement in the transit module of CDPS (NCTS) will be checked by retrieving or<br />

requesting the information from the electronic message “Anticipated Transit Record”. If the transit<br />

declaration doesn’t exist at the customs office of departure, the presented Transit Accompanying<br />

Document will be considered as forged.<br />

- A warning shall be given by the system if the transit operation is already recorded as having entered this<br />

country (of the customs office of transit). However, it has to be noted that two customs offices of transit<br />

in the same country can occur. Office of Entry <strong>and</strong> Office of Exit in case where a movement exits from a<br />

Contracting Party of Convention on a common transit procedure 15 towards a third country.<br />

3.1.4.3 Incidents during the transport<br />

- When transhipment (box 55 on the Transit Accompanying Document) has been established by the<br />

customs authorities during transport operation <strong>and</strong> the entry of goods to the customs territory through the<br />

customs office of transit is allowed, the customs office of transit shall capture this information <strong>and</strong> notify<br />

that to the customs office of departure with an electronic message sent via common domain. This<br />

Page 31/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

message shall contain the customs control results done at customs office of transit, including the<br />

discrepancies, if any have been discovered.<br />

- Where other incidents during transport operation (box 56 on the Transit Accompanying Document) have<br />

been established by the customs authorities, the customs office of transit shall decide:<br />

o to capture this information <strong>and</strong> notify that to the customs office of departure with an electronic<br />

message sent via common domain. This message shall contain the customs control results done at<br />

customs office of transit, including the discrepancies, if any have been discovered, or<br />

o that this data shall not be captured at the customs office of transit.<br />

- In case of diversion <strong>and</strong> binding itinerary, the transit operation is not allowed to cross the frontier, i.e.<br />

must continue its journey to a different customs office of transit without crossing the frontier.<br />

- Where the goods released for transit regime are presented at the declared customs office of transit with<br />

the Transit Accompanying Document (TAD) <strong>and</strong> the entry of goods to the customs territory through the<br />

customs office of transit is not allowed, this customs office shall notify that to the customs office of<br />

departure with an electronic message sent via common domain. This message shall contain the reason:<br />

o for this turn back to the state of the transit operation, or<br />

o for stopping the goods at the frontier.<br />

- Where the entry of goods to the customs territory through the customs office of transit is not allowed, the<br />

customs office of departure shall:<br />

o contact a principal to obtain necessary information,<br />

o take a decision whether the transit regime has to be cancelled or not.<br />

3.1.5 <strong>Customs</strong> office of departure <strong>Customs</strong> office of destination<br />

3.1.5.1 Anticipated Arrival Record<br />

- Where the declared goods have been released for transit regime by the customs office of departure, this<br />

office shall notify that to the customs office of destination with electronic message “Anticipated Arrival<br />

Record” sent<br />

o in case of national transit regime via national domain, according to the Article 246 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 ,<br />

o in case of common transit regime via common domain, according to the Article 45 of Appendix I of<br />

the Convention on a common transit procedure 15 .<br />

- The customs office of destination shall carry out the necessary risk analysis in advance with the Risk<br />

analysis <strong>and</strong> risk management system sub-application on the data of transit declaration received with<br />

“Anticipated Arrival Record” message. The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

destination to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- The results of control shall be registered at this customs office of destination.<br />

- Where the goods released for transit regime are presented at the declared customs office of destination<br />

with the Transit Accompanying Document (TAD), this customs office shall notify that to the customs<br />

office of departure with an electronic message sent via national domain, in case of a national transit<br />

regime, or via common domain, in case of a common transit regime.<br />

Page 32/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Where the goods released for transit regime are presented at the different customs office, than originally<br />

declared customs office of destination, with the Transit Accompanying Document (TAD), the new<br />

customs office of destination shall:<br />

o ask for the data at the customs office of departure with an electronic message,<br />

o carry out the necessary risk analysis with the Risk analysis <strong>and</strong> risk management system subapplication,<br />

when “Anticipated Arrival Record” message is delivered,<br />

o decide on the possible control of goods,<br />

o decide on the end of transit regime,<br />

o notify that ending of transit regime to the customs office of departure with an electronic message<br />

sent via national domain, in case of a national transit regime, or via common domain, in case of a<br />

common transit regime.<br />

3.1.5.2 Transit Accompanying Document<br />

- Where the goods released for transit regime are presented at the declared customs office of destination,<br />

the Transit Accompanying Document (TAD) shall be presented by a carrier.<br />

- The existence of the movement in the transit module of CDPS (NCTS) will be checked by retrieving or<br />

requesting the information from the electronic message “Anticipated Arrival Record”. If the transit<br />

declaration doesn’t exist at the customs office of departure, the presented Transit Accompanying<br />

Document will be considered as forged.<br />

- A warning shall be given by the system if the transit operation is already recorded as:<br />

o having presented to another customs office of destination, or<br />

o having ended at another customs office of destination.<br />

3.1.5.3 Cancellation of transit regime<br />

- When the <strong>Customs</strong> Officer at the customs office of departure accepts the request for cancellation of a<br />

transit regime (i.e. after the decision on release of goods for transit regime), this means that the declared<br />

customs office(s) of transit (for common/Community transit regime) <strong>and</strong> the declared customs office of<br />

destination are already electronically notified on release of goods for transit regime, the cancellation<br />

notification shall be sent to this(these) declared customs office(s).<br />

- When the transit regime (i.e. the decision on release of goods for transit regime) is cancelled then the<br />

already registered guarantee is released, this means that the customs office of guarantee is electronically<br />

notified.<br />

- The declared customs office of transit receives a cancellation notification from the customs office of<br />

departure. The already registered Anticipated Transit Record (ATR) is cancelled.<br />

- The declared customs office of destination receives a cancellation notification from the customs office of<br />

departure. The already registered Anticipated Arrival Record (AAR) is cancelled.<br />

3.1.6 Trade <strong>Customs</strong> office of transit (Common/Community transit)<br />

3.1.6.1 Notification of arrival <strong>and</strong> presentation of goods<br />

- According to the Article 32 of Appendix I of the Convention on a common transit procedure 15 the carrier<br />

shall present the goods released for common transit regime at the customs office of transit with the<br />

Transit Accompanying Document (TAD).<br />

- The carrier may transport the goods via an office of transit other than that mentioned in common transit<br />

declaration, as well as in the Transit Accompanying Document (TAD). That said office shall provide the<br />

customs office of transit originally designated with that information using an electronic message sent via<br />

common domain to the customs office of departure. In case that transit module of CDPS (NCTS) is not<br />

working, that said office shall provide the customs office of transit originally designated with that<br />

Page 33/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

information using the Transit advice note given in Annex A12 of Appendix III of the Convention on a<br />

common transit procedure 15 .<br />

- Notification of arrival of the goods released for common transit regime at the customs office of transit<br />

shall be done with the lodgement of Transit Accompanying Document (TAD) at that customs office.<br />

- The customs office of transit shall register the transit operation <strong>and</strong> lodged Transit Accompanying<br />

Document (TAD) with MRN (Movement Reference Number) given at the customs office of departure.<br />

3.1.6.2 Control of goods<br />

- The customs officer at the customs office of transit takes the appropriate action <strong>and</strong> transit module of<br />

CDPS (NCTS) records the action (presentation of goods <strong>and</strong> TAD). Based on the results of risk analysis<br />

from Risk analysis <strong>and</strong> risk management system sub-application, which was done when “Anticipated<br />

Transit Record” message was delivered, the customs officer shall decide on the possible control of<br />

goods.<br />

- When the customs officer decides on the possible control of goods, he shall notify the carrier that the<br />

consignment has to be controlled prior to the registration of the frontier crossing.<br />

- The carrier of the goods shall inform the customs office of transit about the transhipment occurred. The<br />

customs office of transit where the goods are presented after the transhipment occurred shall capture the<br />

transhipment information (written in box 55 on the Transit Accompanying Document). The objective is<br />

to inform the customs office of departure. In this case the control of goods shall be done.<br />

- The carrier of the goods shall inform the customs office of transit about other incidents occurred during<br />

carriage <strong>and</strong> he shall provide the customs office of transit with official documents related to the incident.<br />

In this case the control of goods shall be done. If there is a problem, then the movement is stopped at this<br />

Office of Transit which then becomes the actual Office of Destination for that movement. If there is no<br />

problem, the <strong>Customs</strong> Officer may, if required, capture this information.<br />

3.1.7 Trade <strong>Customs</strong> office of entry or exit<br />

Only for cases where transit module of CDPS (NCTS) is used for safety <strong>and</strong> security purposes, this means<br />

after the change of customs legislation or after the accession into EU.<br />

3.1.7.1 Entry or exit summary declaration<br />

- Where the declared goods have been released for national transit regime by the customs office of<br />

departure, the carrier is also responsible for lodging the entry or exit summary declaration which is used<br />

for security <strong>and</strong> safety purposes.<br />

- Where the declared goods have been released for common transit regime by the customs office of<br />

departure, the carrier is also responsible for lodging the entry or exit summary declaration which is used<br />

for security <strong>and</strong> safety purposes.<br />

- This responsibility of the carrier can be passed to the principal, who will act for this purpose as a<br />

carrier’s representative. The principal shall mark within his transit declaration, that this declaration is<br />

used also as:<br />

o the entry summary declaration, which is used for security <strong>and</strong> safety purposes at the customs office<br />

of entry being at the same time the customs office of departure for national or common transit<br />

regime,<br />

o the exit summary declaration, which is used for security <strong>and</strong> safety purposes at the customs office of<br />

exit being at the same time the customs office of destination (for national or common transit regime)<br />

or customs office of transit (for common transit regime).<br />

Page 34/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.1.7.2 Risk analysis<br />

- The customs office of entry shall carry out the necessary risk analysis in advance with the Risk analysis<br />

<strong>and</strong> risk management system sub-application on the data of entry summary declaration received within<br />

electronic transit declaration. The decision on control of goods shall be taken when goods are presented<br />

at this customs office.<br />

- The customs office of exit shall carry out the necessary risk analysis in advance with the Risk analysis<br />

<strong>and</strong> risk management system sub-application on the data of exit summary declaration received with<br />

“Anticipated Arrival Record” message or with “Anticipated Transit Record” message. The decision on<br />

control of goods shall be taken when goods are presented at this customs office.<br />

3.1.7.3 Presentation of goods <strong>and</strong> notification of arrival<br />

- The carrier presenting the goods to the customs office of entry or his representative shall notify the<br />

customs authorities of the customs office of entry of the arrival of the means of transport. This<br />

notification of arrival shall contain the particulars necessary for the identification of the entry summary<br />

declarations lodged in respect of all goods carried on that means of transport.<br />

3.1.7.4 Control of goods<br />

- When decision on control of goods is taken, the control protocol shall be issued at that customs office to<br />

be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- When decision on control of goods is taken, the entry or exit summary declaration cannot be changed,<br />

modified, amended or cancelled at this customs office. The results of control shall be registered at this<br />

customs office.<br />

- Based on the customs control, the declared goods shall be allowed to pass through this customs office of<br />

entry or to pass through this customs office of exit or the entry or exit summary declaration can be<br />

modified, changed or cancelled.<br />

3.1.7.5 Registration<br />

- Where the transit declaration (for national or common transit regime) is used as a entry or exit summary<br />

declaration, this entry or exit summary declaration is registered with the same MRN (Movement<br />

Reference Number) as the original transit declaration.<br />

3.1.7.6 Diversion<br />

- The carrier shall be responsible to notify the original customs office of entry about:<br />

o change of customs office of entry declared in the entry summary declaration with the information on<br />

new customs office of entry,<br />

o modification or amendment of entry summary declaration,<br />

o cancellation of entry summary declaration.<br />

- The carrier shall be responsible to notify the original customs office of exit about:<br />

o change of customs office of exit declared in the exit summary declaration with the information on<br />

new customs office of exit,<br />

o modification or amendment of exit summary declaration,<br />

o cancellation of exit summary declaration.<br />

Page 35/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The customs office of entry shall carry out the new risk analysis with the Risk analysis <strong>and</strong> risk<br />

management system sub-application on the data of modified or amended entry summary declaration.<br />

- The customs office of exit shall carry out the new risk analysis with the Risk analysis <strong>and</strong> risk<br />

management system sub-application on the data of exit summary declaration.<br />

3.1.8 Trade <strong>Customs</strong> office of destination<br />

3.1.8.1 Notification of arrival<br />

- In case that the transit declaration was processed electronically at the customs office of departure, the<br />

notification on release of goods for transit regime is sent by the customs office of departure<br />

electronically in the form of message “Anticipated Arrival Record” (AAR) to the declared customs<br />

office of destination.<br />

3.1.8.2 Risk analysis<br />

- The customs office of destination shall carry out the necessary risk analysis in advance with the Risk<br />

analysis management system sub-application on the data of transit declaration received with<br />

“Anticipated Arrival Record” message. The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

3.1.8.3 Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure<br />

- According to the Article 109 of <strong>Customs</strong> Law 1 the principal shall present the goods released for common<br />

transit regime at the customs office of destination with the Transit Accompanying Document (TAD).<br />

- According to the Article 4 para. 1 of Appendix I of the Convention on a common transit procedure 15 the<br />

principal shall present the goods released for common transit regime at the customs office of destination<br />

with the Transit Accompanying Document (TAD).<br />

- The consignee has the same obligation as a principal, which is mentioned above.<br />

- The consignee (or a principal) can notify the presentation of goods to the customs authority, i.e. to the<br />

customs office of destination, in the form of:<br />

o Transit Accompanying Document (paper form),<br />

o transit module of CDPS (NCTS) message (electronic form).<br />

- Electronic notification of presentation of goods sent to the customs authority by a consignee shall be<br />

authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a consignee shall be replaced by e-signature according to the Article 5 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be registered together with the<br />

identification of a consignee in the module for authorisation of e-communication in the Authorisation<br />

sub-application.<br />

- Lodging of electronic notification of presentation of goods to the customs authority is obligatory for<br />

granting the simplified procedure of authorised consignee according to the Article 275 para. 1 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Lodging of electronic notification of presentation of goods to the customs authority is obligatory for<br />

granting the simplified procedure of authorised consignee according to the Article 74a para. 1 of<br />

Appendix I of Convention on a common transit procedure 12 .<br />

- It is assumed that at the time of lodging of notification of presentation of goods to the customs authority,<br />

the goods are already available at the customs office of destination or in some other place called the<br />

‘goods place’ which will be specified to the customs office of destination (the place marked in this<br />

notification) <strong>and</strong> they are ready for ending the transit regime.<br />

Page 36/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The office of destination shall register with the MRN (Movement Reference Number) the presentation of<br />

goods to the customs authority <strong>and</strong> keep the Transit Accompanying Document - TAD.<br />

- When transhipment (box 55 on the Transit Accompanying Document) has been established by the<br />

customs authorities during transport operation, the customs office of destination shall capture this<br />

information <strong>and</strong> notify that to the customs office of departure with an electronic message sent via<br />

national domain, in case of a national transit regime, or via common domain, in case of a common transit<br />

regime. This message shall contain the customs control results done at customs office of destination,<br />

including the discrepancies, if any have been discovered.<br />

- Where other incidents during transport operation (box 56 on the Transit Accompanying Document) have<br />

been established by the customs authorities, the customs office of destination shall capture this<br />

information <strong>and</strong> notify that to the customs office of departure with an electronic message sent via<br />

national domain, in case of a national transit regime, or via common domain, in case of a common transit<br />

regime. This message shall contain the customs control results done at customs office of destination,<br />

including the discrepancies, if any have been discovered.<br />

- The customs office of destination shall take the decision on control of goods using the results of risk<br />

analysis from the Risk analysis <strong>and</strong> risk management system sub-application on the data of customs<br />

declaration received with “Anticipated Arrival Record” message.<br />

- When decision on control of goods which have been presented at the customs office of destination within<br />

the st<strong>and</strong>ard procedure is taken, the notification of this control shall be passed to the consignee.<br />

Authentication of electronic form of this notification of control shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

destination to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

3.1.8.4 Diversion<br />

- The carrier may present the goods at the customs office other than the declared customs office of<br />

destination mentioned in transit declaration, as well as in the Transit Accompanying Document (TAD)<br />

according to:<br />

o Article 239 para. 4 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of national transit regime, or<br />

o Article 34 para. 4 of Appendix I of Convention on a common transit procedure 15 , in case of common<br />

transit regime.<br />

- That new customs office of destination shall notify the customs office of departure <strong>and</strong> ask for the data<br />

of transit declaration using an electronic message sent to the customs office of departure.<br />

- The customs office of departure shall immediately response on this request using an electronic message<br />

sent to the new customs office of destination.<br />

3.1.8.5 Use of simplified procedure of authorised consignee<br />

- Simplified procedure authorised consignee cannot be used with paper declaration for transit regime<br />

according to:<br />

o Article 275 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o Article 74a para. 4 of Appendix I of Convention on a common transit procedure 15 , in case of<br />

common transit regime.<br />

Page 37/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The rules <strong>and</strong> processes described in part 3.1.8.3 of this document are used within the usage of simplified<br />

procedure of authorised consignee.<br />

- It is assumed that at the time of lodging of arrival notification, the goods are still loaded to the sealed<br />

loading compartment of means of transport <strong>and</strong> they are ready for unloading at marked place. This place<br />

is registered <strong>and</strong> authorised within the authorisation of simplified procedure authorised consignee.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure authorised<br />

consignee through the data from modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised place, where goods are available, via code of this place (given in the authorisation),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised country of final consignor or consignee (the list of prohibited countries is given in the<br />

authorisation),<br />

o authorised guarantee, i.e. a comprehensive guarantee shall be used for temporary storage (given in<br />

the authorisation).<br />

- When all the above automated checks passed successfully, the electronic notification shall be accepted<br />

with use of simplified procedure authorised consignee by the customs office of destination. This<br />

acceptance shall be electronically notified to the authorised consignee. Authentication of this message<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

- The authorised consignee shall wait for the decision on control of goods which are still in the loading<br />

compartment of means of transport. The timer is set up in the authorisation of authorised consignee.<br />

- The customs authorities (customs office of destination within the working hours) shall take a decision on<br />

control of goods which have been presented within the simplified procedure authorised consignee within<br />

the time limit (timer for automatic release of goods for unloading) set up in the within the authorisation<br />

of simplified procedure authorised consignee.<br />

- When the decision on control of goods which have been declared within the simplified procedure<br />

authorised consignee is taken, the notification of this control shall be electronically sent to the authorised<br />

consignee. Authentication of this notification of control shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . This<br />

notification shall be sent at the end of the time limit (timer for automatic release of goods for unloading)<br />

set up in the authorisation to give a time to the customs authorities responsible for this control to be<br />

present at the authorised place, where the goods are available, before the notification is sent to the<br />

authorised consignee. At that time the timer for automatic release of goods shall be stopped.<br />

- When the timer for automatic release of goods expired <strong>and</strong> no decision on control of goods was taken,<br />

the goods are automatically released for unloading by the authorised consignee. The decision on release<br />

of goods for unloading together with the data of customs declaration shall be electronically sent to the<br />

authorised consignee at that moment. Authentication of this decision shall be with an e-signature of<br />

customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

- Based on the decision on release of goods for unloading which was electronically sent to the authorised<br />

consignee by the customs office of destination, the authorised consignee shall:<br />

o unseal the loading compartment of means of transport,<br />

o unload the goods from loading compartment of means of transport,<br />

o check the goods on behalf of customs authorities using the electronic data from transit declaration<br />

received from the customs office of destination (Transit Accompanying Document – TAD shall not<br />

be used for this control),<br />

o inform the customs office of destination about the result of control within the time limit given in the<br />

authorisation,<br />

Page 38/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o immediately inform the customs office of destination about the discovered discrepancies <strong>and</strong> wait for<br />

the further instruction from the customs office of destination.<br />

- Where the transit regime has ended the authorised consignee shall return Transit Accompanying<br />

Document – TAD to the customs office of destination within the time limit given in the authorisation.<br />

3.1.9 <strong>Customs</strong> office of destination <strong>Customs</strong> office of departure<br />

3.1.9.1 Presentation of goods at destination (Arrival Advice)<br />

- Where the customs office of destination has received the notification of presentation of goods to the<br />

customs authority (in the form of electronic message or TAD) <strong>and</strong> registered this notification with MRN,<br />

this customs office shall notify the customs office of departure on arrival of goods using the message<br />

“Arrival Advice” according to:<br />

o Article 247 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of national transit regime, or<br />

o Article 46 para. 1 of Appendix I of Convention on a common transit procedure 15 , in case of common<br />

transit regime.<br />

- The message “Arrival Advice” may not be used as proof of the procedure having ended within the<br />

meaning of:<br />

o Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of national transit regime, or<br />

o Article 39 para. 2 of Appendix I of Convention on a common transit procedure 15 , in case of common<br />

transit regime.<br />

3.1.9.2 Control of goods (Control results) <strong>and</strong> ending of transit regime<br />

- According to the Article 106 para. 1 of <strong>Customs</strong> Law 1 the transit regime shall end <strong>and</strong> the obligations of<br />

the principal shall be met when the goods placed under the transit regime <strong>and</strong> the required documents are<br />

produced at the customs office of destination in accordance with the provisions of the procedure in<br />

question. This end of transit regime is registered with the same MRN (Movement Reference Number) as<br />

the original transit declaration.<br />

- The results of control shall be registered at the customs office of destination <strong>and</strong> they shall be forwarded<br />

to the customs office of departure with message “Control results” at the latest on the working day<br />

following the day the goods are presented at the customs office of destination according to:<br />

o Article 247 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of national transit regime, or<br />

o Article 46 para. 2 of Appendix I of Convention on a common transit procedure 15 , in case of common<br />

transit regime.<br />

- The message shall be used as a proof of the procedure having ended within the meaning of:<br />

o Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of national transit regime, or<br />

o Article 39 para. 2 of Appendix I of Convention on a common transit procedure 15 , in case of common<br />

transit regime.<br />

3.1.9.3 Discrepancies<br />

- The customs office of destination or the authorised consignee may discover some discrepancies between<br />

the transit declaration <strong>and</strong> the goods presented to the customs authorities at destination. The<br />

identification of these discrepancies shall be forwarded to the customs office of departure as the results<br />

of control with message “Control results” at the latest on the working day following the day the goods<br />

are presented at the customs office of destination.<br />

- The customs office of destination shall mark in message “Control results” whether this office is waiting<br />

for solving the discrepancies at the customs office of departure or these discrepancies have been solved<br />

at the customs office of destination.<br />

Page 39/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Based on the request for solving the discrepancies the customs office of departure shall:<br />

o take necessary measures for solving the discrepancies, e.g. to contact the principal <strong>and</strong> verify the<br />

details,<br />

o immediately inform the customs office of destination with the results.<br />

3.1.10 Write-off by <strong>Customs</strong> office of departure<br />

3.1.10.1 End of transit procedure confirmed<br />

- The message “Control results” sent from the customs office of destination to the customs office of<br />

departure shall be used as a confirmation of the regime having ended within the meaning of:<br />

o Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of national transit regime, or<br />

o Article 39 para. 2 of Appendix I of Convention on a common transit procedure 15 , in case of common<br />

transit regime.<br />

- According to the Article 239 para. 3 of <strong>Customs</strong> Law Implementing Regulation 2 the customs authority of<br />

destination shall endorse an extra copy or a photocopy of transit declaration or Transit Accompanying<br />

Document – TAD with the following phrase ‘Alternative proof’ to provide evidence of the transit<br />

regime having ended in accordance with Article 242 paragraph (2) of <strong>Customs</strong> Law Implementing<br />

Regulation 2 at the request of the principal.<br />

- According to the Article 106 para. 2 of <strong>Customs</strong> Law 1 the customs office of departure shall discharge the<br />

procedure when it is in a position to establish, on the basis of a comparison of the data available to the<br />

customs office of departure <strong>and</strong> those available to the customs office of destination, that the transit<br />

regime has ended correctly. This discharge of transit regime is registered with the same MRN<br />

(Movement Reference Number) as the original transit declaration.<br />

3.1.10.2 Release of guarantee<br />

- Where the goods have been presented at the customs office of destination the electronic notification is<br />

sent from this office to the customs office of departure. In case that the comprehensive guarantee or the<br />

comprehensive guarantee waiver was used, the customs office of departure based on this information<br />

shall notify that to the customs office of guarantee with the request for credit of a used part of reference<br />

amount.<br />

- Where the transit regime is discharged by the customs office of departure <strong>and</strong> in case that the<br />

comprehensive guarantee or the comprehensive guarantee waiver was used, the customs office of<br />

departure shall notify that to the customs office of guarantee with the request for final release of a used<br />

guarantee.<br />

- Where the transit regime is discharged by the customs office of departure <strong>and</strong> in case that the individual<br />

guarantee was used, the customs office of departure shall notify that to the customs office of guarantee<br />

with the request for release of a used guarantee.<br />

3.1.10.3 Principal notification on discharge of transit regime<br />

- Where the transit regime is discharged by the customs office of departure <strong>and</strong> the transit declaration was<br />

lodged electronically the customs office of departure shall inform electronically the principal or his<br />

representative (a person who lodged the transit declaration) that the transit regime was ended at the<br />

customs office of destination <strong>and</strong> discharged at the customs office of departure. This information shall be<br />

sent to the principal or his representative at that moment. Authentication of this decision shall be with an<br />

e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

3.1.11 Enquiry procedure<br />

Page 40/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.1.11.1 Notification towards Principal<br />

- Where the time allotted for the receipt of the message “Arrival Advice” or of the message “control<br />

result” has expired, the notification <strong>and</strong> enquiry procedure shall start at the customs office of departure.<br />

These time-outs indicate that an enquiry procedure should be started.<br />

- The customs office of departure shall start with the notification to the principal or his representative (a<br />

person who lodged the transit declaration) that the transit regime has not ended within the time period<br />

given in this transit declaration (in the decision on release of goods for transit regime). This information<br />

shall be sent to the principal or his representative at that moment.<br />

- In case that the transit declaration was lodged electronically, this notification <strong>and</strong> the request for<br />

information shall be sent as NCTS electronic message. Authentication of this notification shall be with<br />

an e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

- In case that the transit declaration was lodged in paper form, this notification <strong>and</strong> the request for<br />

information shall be sent in paper form specified by MCA.<br />

- The principal within the time-out shall provide the customs office of departure with further details<br />

related to this transit operation in the form of:<br />

o electronic message, authenticated with an e-signature of principal, or<br />

o paper explanation, or<br />

o oral explanation.<br />

- This time-out period shall be defined by the MCA. This time-out indicates that an enquiry procedure<br />

should be started. It is reset to this value (or a shorter one) when an enquiry is initiated.<br />

3.1.11.2 Enquiry procedure towards declared/actual <strong>Customs</strong> office of destination<br />

- Where the time-out allotted for the receipt of further information from the principal has expired, the<br />

enquiry procedure shall start at the customs office of departure.<br />

- The customs office of departure shall start enquiry procedure with the notification <strong>and</strong> the request for<br />

information to the customs office of destination that the transit regime has not ended within the time<br />

period given in this transit declaration (in the decision on release of goods for transit regime). This<br />

notification <strong>and</strong> the request for information shall be sent as NCTS electronic message to declared/actual<br />

<strong>Customs</strong> office of destination. The actual <strong>Customs</strong> office of destination shall be used based on the<br />

information received from the principal.<br />

- The customs office of destination within the time-out shall provide the customs office of departure with<br />

further details related to this transit operation. These further details shall be sent by customs office of<br />

destination as NCTS electronic message. This time-out period shall be defined by the MCA. This timeout<br />

indicates that an enquiry remainder procedure should be started. It is reset to this value (or a shorter<br />

one) when an enquiry remainder is initiated.<br />

- Where the customs office of departure have not received any further details from the customs office of<br />

destination, the customs office of departure shall start enquiry remainder procedure to the Higher<br />

Authority of a customs office of destination. This enquiry remainder notification <strong>and</strong> the request for<br />

information shall be sent as NCTS electronic message to the Higher Authority of a customs office of<br />

destination.<br />

3.1.11.3 Enquiry procedure towards declared/actual customs office of transit<br />

- The enquiry procedure towards declared/actual customs office of transit is based only on the<br />

"Notification Crossing Frontier" message(s) which was(were) sent from the customs office(s) of transit<br />

as a confirmation that the declared goods have passed this(these) customs office(s).<br />

Page 41/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.1.11.4 Recovery procedure towards a debtor (a principal)<br />

- Where the customs office of departure is not able to discharge the transit procedure, the recovery of<br />

incurred customs debt procedure shall be initiated. The recovery procedure shall start at the customs<br />

office of departure or at another competent customs authority.<br />

- Where the recovery procedure has been initiated by the competent customs authority, that authority shall<br />

send the notification of start of recovery procedure as NCTS electronic message to:<br />

o office of destination,<br />

o office(s) of transit (for common/Community transit regime),<br />

o principal, in case that the transit declaration was lodged electronically.<br />

- In case that the transit declaration was lodged in paper form, this notification of beginning of recovery<br />

procedure shall be sent to the principal in paper form specified by MCA.<br />

- Where the recovery procedure has been initiated by the competent customs authority, that authority shall<br />

send the notification of start of recovery procedure to the guarantor, this notification shall be sent in<br />

paper form specified by MCA.<br />

- Where the recovery procedure has been finished by the competent customs authority, that authority shall<br />

send the notification of closure of recovery procedure as NCTS electronic message to:<br />

o office of destination,<br />

o office(s) of transit (for common/Community transit regime),<br />

o principal, in case that the transit declaration was lodged electronically.<br />

- In case that the transit declaration was lodged in paper form, this notification of closure of recovery<br />

procedure shall be sent to the principal in paper form specified by MCA.<br />

- Where the recovery procedure has been finished by the competent customs authority, that authority shall<br />

send the notification of closure of recovery procedure to the guarantor, this notification shall be sent in<br />

paper form specified by MCA.<br />

3.1.12 NCTS/TIR procedure<br />

The objective of this application in EU (in the pilot phase 2007-2008) is to provide full control of the<br />

European leg of TIR movements <strong>and</strong> to facilitate the termination /discharge of TIR operations within the<br />

Community by replacing the physical return of Voucher No. 2 with the electronic transmission of NCTS<br />

messages. This application will be operational from 1. 1. 2009 in all EU member states.<br />

Same objective should have this NCTS/TIR module in CDPS, this means to provide full control of the<br />

Macedonia leg of TIR movements <strong>and</strong> to facilitate the termination of TIR operations (i.e. discharge of transit<br />

regime) within the Macedonian customs territory by replacing the physical return of Voucher No. 2 with the<br />

electronic transmission of NCTS messages at the national level.<br />

3.1.12.1 NCTS/TIR procedure at <strong>Customs</strong> office of departure<br />

- As it was pointed above in the part 3.1.1.2 of this document the TIR Carnet is a paper based customs<br />

declaration for the transit regime. At present the data of TIR Carnet (paper customs transit declaration)<br />

are keyed in to the customs system by a customs officer at the customs office of departure <strong>and</strong> later on at<br />

the customs office of destination.<br />

- The NCTS/TIR procedure at <strong>Customs</strong> office of departure means that the chosen data of TIR Carnet<br />

(paper customs transit declaration) shall be electronically lodged to the customs office of departure in<br />

parallel with the TIR Carnet (paper customs transit declaration).<br />

- Due to the basic principles of TIR transit procedure (as a chain of transit regimes), it would be<br />

appropriate to develop the possibility of re-usage of the data already filled in the NCTS/TIR system, i.e.<br />

the data sent from customs office of departure to the customs office of destination, which is a new<br />

Page 42/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

customs office of departure. The data can be modified, i.e. some data could be added or some data could<br />

be deleted or amended, by the customs officer at his new customs office of departure based on the<br />

content of TIR Carnet.<br />

- The data elements of the NCTS/TIR declaration shall be introduced <strong>and</strong> they shall be identical with the<br />

data elements of the NCTS/TIR declaration set up at the EU level. The data of the NCTS/TIR declaration<br />

shall not be signed by the principal, i.e. TIR Carnet holder. The lodgement of data elements of the<br />

NCTS/TIR declaration is not necessary to be approved by customs authorities.<br />

- The data elements of the NCTS/TIR declaration shall be processed by CDPS in the same way as the data<br />

of paper transit declaration.<br />

- The paper transit declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number)<br />

by the customs office of departure if all automated checks mentioned above in the part 3.1.1.2 of this<br />

document passed successfully.<br />

- After the acceptance of transit declaration by the customs office of departure the decision on control<br />

shall be taken by a customs officer at the customs office of departure. The Risk analysis <strong>and</strong> risk<br />

management system sub-application shall be used for automated evaluation of possible risks.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

departure to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o principal’s approval of amendment of transit declaration based on the discovered discrepancies,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- In case of NCTS/TIR, the decision on release of goods for transit regime is issued by the customs office<br />

of departure in the form of vouchers No 1 <strong>and</strong> 2 of TIR Carnet (according to Article 105 para. 2 of<br />

<strong>Customs</strong> Law 1 ) which is followed by the Transit Accompanying Document - TAD. Authentication of<br />

this decision shall be with a h<strong>and</strong> written signature <strong>and</strong> a personal customs stamp of a customs officer<br />

from customs office of departure.<br />

- Where the declared goods have been released for transit regime by the customs office of departure, this<br />

office shall notify that to the customs office of destination with electronic message “Anticipated Arrival<br />

Record” sent via national domain, according to the Article 246 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

3.1.12.2 NCTS/TIR procedure at <strong>Customs</strong> office of destination<br />

- The customs office of destination shall carry out the necessary risk analysis in advance with the Risk<br />

analysis <strong>and</strong> risk management system sub-application on the data of transit declaration received with<br />

“Anticipated Arrival Record” message. The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

- Where the customs office of destination has received the notification of presentation of goods to the<br />

customs authority in the form of TIR Carnet <strong>and</strong> TAD <strong>and</strong> registered this notification with MRN, this<br />

customs office shall notify the customs office of departure on arrival of goods using the message<br />

“Arrival Advice” according to Article 247 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 , in case of<br />

national transit regime.<br />

- The message “Arrival Advice” may not be used as proof of the procedure having ended within the<br />

meaning of Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

destination to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

Page 43/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- According to the Article 106 para. 1 of <strong>Customs</strong> Law 1 the transit regime shall end <strong>and</strong> the obligations of<br />

the principal shall be met when the goods placed under the transit regime <strong>and</strong> the required documents are<br />

produced at the customs office of destination in accordance with the provisions of the procedure in<br />

question. This end of transit regime is registered with the same MRN (Movement Reference Number) as<br />

the original transit declaration.<br />

- The results of control shall be registered at the customs office of destination <strong>and</strong> they shall be forwarded<br />

to the customs office of departure with message “Control results” at the latest on the working day<br />

following the day the goods are presented at the customs office of destination according to the Article<br />

247 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Where the goods released for transit regime are presented at the different customs office, than originally<br />

declared customs office of destination, with the TIR Carnet <strong>and</strong> Transit Accompanying Document<br />

(TAD), the new customs office of destination shall:<br />

o ask for the data at the customs office of departure with an electronic message,<br />

o carry out the necessary risk analysis with the Risk analysis <strong>and</strong> risk management system subapplication,<br />

when “Anticipated Arrival Record” message is delivered,<br />

o decide on the possible control of goods,<br />

o decide on the end of transit regime,<br />

o notify that ending of transit regime to the customs office of departure with an electronic message<br />

sent via national domain.<br />

3.1.12.3 Write-off by <strong>Customs</strong> office of departure (NCTS/TIR)<br />

- The message “Control results” sent from the customs office of destination to the customs office of<br />

departure shall be used as a confirmation of the procedure having ended within the meaning of the<br />

Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- According to the Article 106 para. 2 of <strong>Customs</strong> Law 1 the customs office of departure shall discharge the<br />

procedure when it is in a position to establish, on the basis of a comparison of the data available to the<br />

customs office of departure <strong>and</strong> those available to the customs office of destination, that the transit<br />

regime has ended correctly. This discharge of transit regime is registered with the same MRN<br />

(Movement Reference Number) as the original transit declaration.<br />

- Where the transit regime is discharged by the customs office of departure <strong>and</strong> the data of TIR Carnet<br />

(paper transit declaration) was lodged electronically, the customs office of departure shall inform<br />

electronically the principal (TIR Carnet holder) that the transit regime was ended at the customs office of<br />

destination <strong>and</strong> discharged at the customs office of departure. This information shall be sent to the<br />

principal or his representative at that moment. Authentication of this decision shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

3.1.13 Railway procedure<br />

- According to the Article 279 of <strong>Customs</strong> Law Implementing Regulation 2 the executor of the railway<br />

transport operations (this means the Macedonian Railway Company) shall make the records held at their<br />

accounting office(s) available to the dedicated customs authority for purposes of control, which this<br />

dedicated customs authority shall carry out on behalf of the customs office of departure. Same procedure<br />

is used at present within common/Community transit procedure.<br />

Page 44/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The direct electronic communication with the accounting centre of the executor of the railway transport<br />

operations (this means the Macedonian Railway Company) for the purpose of monitoring of transit<br />

operations/regimes by customs authorities shall be established.<br />

- Future development of management of transit regime in the railway transport is under preparation of<br />

European Modernised <strong>Customs</strong> Code <strong>and</strong> its new implementing provisions.<br />

3.1.13.1 Railway procedure at <strong>Customs</strong> office of departure (national transit)<br />

- As it was pointed above in the part 3.1.1.2 of this document the CIM Consignment Note is a paper based<br />

customs declaration for the transit regime. At present the data of CIM Consignment Note (paper customs<br />

transit declaration) are not keyed in to the customs system based on the simplified procedure granted to<br />

the railway transport operations (this means the Macedonian Railway Company) <strong>and</strong> according to the<br />

Article 279 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The modification at <strong>Customs</strong> office of departure means that the chosen data of CIM Consignment Note<br />

(paper customs transit declaration) shall be electronically lodged to the customs office of departure in<br />

parallel with the CIM Consignment Note (paper customs transit declaration).<br />

- The data elements of the transit declaration in the form of CIM Consignment Note shall be introduced.<br />

The data of the transit declaration in the form of CIM Consignment Note shall not be signed by the<br />

principal, i.e. the railway transport operations (Macedonian Railway Company). The lodgement of data<br />

elements of the transit declaration in the form of CIM Consignment Note is not necessary to be approved<br />

by customs authorities.<br />

- The data elements of the transit declaration in the form of CIM Consignment Note shall be processed by<br />

CDPS in the same way as the data of paper transit declaration.<br />

- The paper transit declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number)<br />

by the customs office of departure if all automated checks mentioned above in the part 3.1.1.2 of this<br />

document passed successfully.<br />

- After the acceptance of transit declaration by the customs office of departure the decision on control<br />

shall be taken by a customs officer at the customs office of departure. The Risk analysis <strong>and</strong> risk<br />

management system sub-application shall be used for automated evaluation of possible risks.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

departure to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o principal’s approval of amendment of transit declaration based on the discovered discrepancies,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- In case of transit declaration in the form of CIM Consignment Note, the decision on release of goods for<br />

transit regime is issued by the customs office of departure in the form of CIM Consignment Note<br />

(according to the Articles 277 <strong>and</strong> 278 of <strong>Customs</strong> Law Implementing Regulation 2 ) which is followed by<br />

the Transit Accompanying Document - TAD. Authentication of this decision shall be with a h<strong>and</strong> written<br />

signature <strong>and</strong> a personal customs stamp of a customs officer from customs office of departure.<br />

- Where the declared goods have been released for transit regime by the customs office of departure, this<br />

office shall notify that to the customs office of destination with electronic message “Anticipated Arrival<br />

Record” sent via national domain, according to the Article 246 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

3.1.13.2 Railway procedure at <strong>Customs</strong> office of destination (national transit)<br />

Page 45/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The customs office of destination shall carry out the necessary risk analysis in advance with the Risk<br />

analysis <strong>and</strong> risk management system sub-application on the data of transit declaration received with<br />

“Anticipated Arrival Record” message. The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

- Where the customs office of destination has received the notification of presentation of goods to the<br />

customs authority in the form of CIM Consignment Note <strong>and</strong> TAD <strong>and</strong> registered this notification with<br />

MRN, this customs office shall notify the customs office of departure on arrival of goods using the<br />

message “Arrival Advice” according to Article 247 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

in case of national transit regime.<br />

- The message “Arrival Advice” may not be used as proof of the procedure having ended within the<br />

meaning of Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

destination to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- According to the Article 106 para. 1 of <strong>Customs</strong> Law 1 the transit regime shall end <strong>and</strong> the obligations of<br />

the principal shall be met when the goods placed under the transit regime <strong>and</strong> the required documents are<br />

produced at the customs office of destination in accordance with the provisions of the procedure in<br />

question. This end of transit regime is registered with the same MRN (Movement Reference Number) as<br />

the original transit declaration.<br />

- The results of control shall be registered at the customs office of destination <strong>and</strong> they shall be forwarded<br />

to the customs office of departure with message “Control results” at the latest on the working day<br />

following the day the goods are presented at the customs office of destination according to the Article<br />

247 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Where the goods released for transit regime are presented at the different customs office, than originally<br />

declared customs office of destination, with the CIM Consignment Note <strong>and</strong> Transit Accompanying<br />

Document (TAD), the new customs office of destination shall:<br />

o ask for the data at the customs office of departure with an electronic message,<br />

o carry out the necessary risk analysis with the Risk analysis <strong>and</strong> risk management system subapplication,<br />

when “Anticipated Arrival Record” message is delivered,<br />

o decide on the possible control of goods,<br />

o decide on the end of transit regime,<br />

o notify that ending of transit regime to the customs office of departure with an electronic message<br />

sent via national domain.<br />

3.1.13.3 Write-off by <strong>Customs</strong> office of departure (Railway)<br />

- The message “Control results” sent from the customs office of destination to the customs office of<br />

departure shall be used as a confirmation of the procedure having ended within the meaning of the<br />

Article 242 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- According to the Article 106 para. 2 of <strong>Customs</strong> Law 1 the customs office of departure shall discharge the<br />

procedure when it is in a position to establish, on the basis of a comparison of the data available to the<br />

customs office of departure <strong>and</strong> those available to the customs office of destination, that the transit<br />

regime has ended correctly. This discharge of transit regime is registered with the same MRN<br />

(Movement Reference Number) as the original transit declaration.<br />

Page 46/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Where the transit regime is discharged by the customs office of departure <strong>and</strong> the data of TIR Carnet<br />

(paper transit declaration) was lodged electronically, the customs office of departure shall inform<br />

electronically the principal (Macedonian Railway Company) that the transit regime was ended at the<br />

customs office of destination <strong>and</strong> discharged at the customs office of departure. This information shall be<br />

sent to the principal or his representative at that moment. Authentication of this decision shall be with an<br />

e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

3.2 Export regimes<br />

3.2.1 Trade <strong>Customs</strong> office of export<br />

3.2.1.1 Electronic export declaration<br />

- Lodging of electronic customs declaration is possible according to the Article 71 para. b) <strong>and</strong> Article 89<br />

of <strong>Customs</strong> Law 1 .<br />

- Electronic lodging of customs declaration for export regime by a declarant or his representative shall be<br />

authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a declarant or his representative shall be replaced by e-signature according<br />

to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be registered<br />

together with the identification of a declarant (or his representative) in the module for authorisation of e-<br />

communication in the Authorisation sub-application.<br />

- Lodging of electronic customs declaration for export regime shall be obligatory for granting the<br />

simplified procedure of local clearance in export according to the Articles 169, 200 <strong>and</strong> 201 of <strong>Customs</strong><br />

Law Implementing Regulation 2 .<br />

- It is assumed that at the time of lodging of electronic export declaration, the goods are already loaded to<br />

the loading compartment of means of transport, they are ready to be presented to the customs office of<br />

export <strong>and</strong> they are ready for placing for export regime.<br />

- Automated initial checks of electronic customs declaration shall cover:<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application,<br />

o filling in the data-elements or data-groups (boxes of declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of export licences through the data from licence’s<br />

module of Single window sub-application.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure (if it is used)<br />

through the data from modules of Authorisation sub-application shall cover the authorisation of<br />

simplified procedure local clearance in export regime.<br />

- The electronic export declaration shall be registered with MRN (Movement Reference Number) by the<br />

customs office of export if all above automated checks passed successfully. This registration of customs<br />

declaration with MRN shall be electronically notified to a declarant/exporter or his representative (a<br />

person who lodged the export declaration). Authentication of this notification shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

- If any automatic checks didn’t pass successfully the export declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be electronically notified to a declarant. Authentication<br />

of this notification shall be with an e-signature of customs administration, according to the Article 109<br />

para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . Receiving this information a declarant shall:<br />

Page 47/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o amend his refused export declaration, sign it (with his e-signature) <strong>and</strong> send it (with same Local<br />

Reference Number - LRN) electronically again to the customs office of export, or<br />

o send a new electronic export declaration to the customs office of departure (with new LRN).<br />

3.2.1.2 Paper export declarations<br />

- Lodging of paper customs export declaration is possible in prescribed forms according to Article 72 para.<br />

1 of <strong>Customs</strong> Law 1 :<br />

o in the form of SAD, according to Articles 115 - 117 <strong>and</strong> 407 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ,<br />

o in the other form than SAD based on the authorisation issued by the customs authorities, according<br />

to Article 116 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Data of paper customs export declaration shall be:<br />

o keyed in to the CDPS by a customs officer at the customs office of export, or<br />

o electronically lodged to the customs office of export in parallel with the paper-based customs<br />

export declaration <strong>and</strong> it is not necessary to be approved by customs authorities.<br />

- The customs officer shall have a possibility for temporary storage of unfinished entry of export<br />

declaration. The MCA shall set up the time limit for this temporary storage of unfinished export<br />

declaration.<br />

- It is assumed that at the time of lodging of paper export declaration, the goods are already loaded to the<br />

loading compartment of means of transport, presented to the customs authorities <strong>and</strong> they are ready for<br />

placing for export regime.<br />

- Automated initial checks of data of paper customs export declaration:<br />

o filling in the data-elements or data-groups (boxes of declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls<br />

specified for each type of export declaration).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of export licences via data from licences module of<br />

Single window sub-application.<br />

- The paper export declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number)<br />

by the customs office of export if all above automated checks passed successfully.<br />

- If any automatic checks didn’t pass successfully the export declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified by a customs officer to a declarant (oral or<br />

written notification). Receiving this information a declarant shall:<br />

o amend his refused export declaration <strong>and</strong> lodge it (with same LRN) again to the customs office of<br />

export, or<br />

o lodge a new export declaration to the customs office of export (with new LRN).<br />

3.2.1.3 Oral export declaration<br />

- Lodging of oral export declaration is possible according to Article 71 para. c) <strong>and</strong> Article 89 para. 2) of<br />

<strong>Customs</strong> Law 1 <strong>and</strong> under the conditions given in Articles 133 – 135 <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The data elements of the oral export declaration shall be introduced by MCA. Data of oral export<br />

declaration shall be keyed in to the CDPS by a customs officer at the customs office of export.<br />

- It is assumed that at the time of lodging of oral export declaration, the goods are already presented to the<br />

customs authorities <strong>and</strong> they are ready for placing for export regime.<br />

- Automated initial checks of data of oral export declaration:<br />

Page 48/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o filling in the data-elements or data-groups,<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls<br />

specified for each type of export declaration).<br />

- The oral export declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number)<br />

by the customs office of export if all above automated checks passed successfully.<br />

- If any automatic checks didn’t pass successfully the export declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified by a customs officer to a declarant (oral<br />

notification). Receiving this information a declarant shall:<br />

o amend his refused export declaration <strong>and</strong> lodge it again to the customs office of export, or<br />

o lodge a new export declaration to the customs office of export.<br />

3.2.1.4 Documents to accompany the export declaration<br />

- Necessary documents to accompany the export declaration shall be lodged by a declarant to the office of<br />

export according to the Article 72 para. 2 of <strong>Customs</strong> Law 1 <strong>and</strong> Article 128 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 . The customs office of export may dispense with the presentation of these<br />

documents at the time of completion of the formalities at customs office of export.<br />

- The documents to accompany the export declaration shall be lodged by a declarant to the office of export<br />

in electronic or paper form. The electronic form of documents to accompany the export declaration shall<br />

be determined by the Macedonian customs administration, including the determination of manner of<br />

keeping of the documents that are transmitted by electronic means, according to the Article 131 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The electronic form of documents to accompany the export declaration shall be authenticated with<br />

electronic signature of a declarant. The delivery <strong>and</strong> acceptance of electronic form of documents to<br />

accompany the export declaration shall be electronically notified to a declarant by customs office of<br />

export with information about the acceptance of export declaration. Authentication of this notification<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

- The export declaration shall be accepted by the customs office of export, when the documents to<br />

accompany the export declaration are presented at that customs office with the goods to be released for<br />

the export regime.<br />

- When the simplified procedure local clearance in export regime is used the documents to accompany the<br />

export declaration shall be available for customs at the declarant’s premise.<br />

3.2.1.5 Control of accompanied documents<br />

- The initial automatic control of documents to accompany the export declaration, which were lodged in<br />

electronic form, shall be based on the comparison of type <strong>and</strong> identification number of these documents,<br />

which were provided in the export declaration, <strong>and</strong> the documents sent by a declarant. The passing this<br />

control shall be sufficient for acceptance of a customs export declaration.<br />

- The detailed control of documents to accompany the export declaration, which were lodged in electronic<br />

or paper form, shall be carried out by a customs officer at the customs office of export.<br />

- The result of the detailed control of these electronic documents can be:<br />

o the confirmation of acceptance of customs declaration, in case of electronic lodgement of customs<br />

declaration <strong>and</strong> these documents, or<br />

o the cancellation of acceptance of customs declaration due to invalid documents.<br />

- The result of the detailed control of these paper-based documents can be:<br />

o the acceptance of customs declaration, in case of lodgement of paper-based documents, or<br />

Page 49/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o not-acceptance of customs declaration due to invalid documents.<br />

3.2.1.6 Acceptance, modifications, rectifications <strong>and</strong> deletions of export declarations<br />

- The export declaration shall be accepted by the customs office of export when:<br />

o all above automatic checks passed successfully,<br />

o all documents to accompany the export declaration are lodged by a declarant to that customs office<br />

or the waiver for lodging the documents to accompany the export declaration was granted or the<br />

simplified procedure local clearance in export regime is used,<br />

o the goods are presented to that customs office.<br />

- In case that the export declaration was lodged electronically, this MRN shall be electronically notified to<br />

a declarant. Authentication of this notification shall be with an e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . In case that the<br />

export declaration was not lodged electronically, the acceptance of export declaration with this MRN<br />

shall be notified to a declarant (oral notification) at the customs office of export.<br />

- The registered or accepted export declaration can be changed by a declarant before the decision on a<br />

control of goods is taken. When export declaration was registered or accepted by the customs office of<br />

export, this export declaration can be:<br />

o modified by an electronic message (with MRN <strong>and</strong> same LRN) sent to the customs office of export,<br />

or<br />

o changed or amended by a new export declaration which shall be sent to the customs office of export<br />

(old export declaration shall be cancelled by another electronic message),<br />

o cancelled by a message sent to the customs office of export.<br />

- Any modification or cancellation done by an electronic message shall be confirmed by the customs<br />

office of export with an electronic message. Authentication of this decision shall be with an e-signature<br />

of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

- After the acceptance of export declaration by the customs office of export the request for allocation of<br />

requested export quota (if the export quotas are used), if it was indicated in the customs declaration, shall<br />

be processed by the quotas module of Single window-MK sub-application.<br />

- After the acceptance of export declaration by the customs office of export the decision on control shall<br />

be taken by a customs officer at the customs office of export. The Risk analysis <strong>and</strong> risk management<br />

system sub-application shall be used for automated evaluation of possible risks.<br />

- If CDPS is also used for the purpose of safety <strong>and</strong> security, then full safety <strong>and</strong> security related risk<br />

analysis for all the goods shall be performed additionally within the prescribed time limits (after the<br />

change of national customs legislation or after the accession into EU).<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

export to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o declarant’s approval of amendment of export declaration based on the discovered discrepancies,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- When decision on control of goods is taken, the export declaration cannot be changed, modified,<br />

amended or cancelled at the customs office of export. The results of control shall be registered at this<br />

customs office.<br />

Page 50/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Based on the customs control, the declared goods can be released for export regime or the export<br />

declaration can be modified, changed or cancelled.<br />

3.2.1.7 Cancellation of export declaration<br />

- The cancellation of the export declaration (before the decision on release of goods is taken) shall be<br />

initiated either by a declarant or by the customs office of export (annulment/revocation of export<br />

declaration).<br />

- The cancellation of export declaration by a declarant shall be initiated in:<br />

o electronic form, i.e. by an electronic message sent by a declarant to the customs office of export,<br />

o paper form lodged by a declarant at the customs office of export.<br />

- The registered or accepted export declaration shall be cancelled by an electronic message sent to the<br />

customs office of export before the decision on control of goods is taken or after the customs control.<br />

- When the <strong>Customs</strong> Officer at the customs office of export accepts the request for cancellation of an<br />

export declaration (i.e. before the decision on release of goods for export regime is taken), this means<br />

that the declared customs office of exit has not been electronically notified of the release for export<br />

regime <strong>and</strong> therefore customs office of export shall not inform this customs office about the cancellation.<br />

- The cancellation of export declaration done by an electronic message shall be confirmed by the customs<br />

office of export with an electronic message. Authentication of this decision shall be with an e-signature<br />

of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 . The cancellation initiated in paper form shall be confirmed by the customs office of export<br />

in paper form.<br />

3.2.2 Release of goods for export regime<br />

- The decision on release of goods for export regime can be issued by the customs office of export using<br />

the st<strong>and</strong>ard procedure or simplified procedure of local clearance or simplified procedure of<br />

simplified/incomplete customs declaration. The usage of simplified procedure local clearance is<br />

described bellow – see part 3.2.2.2 of this document. The usage of simplified procedure of<br />

simplified/incomplete customs declaration is described bellow – see parts 3.2.2.3 <strong>and</strong> 3.2.2.4 of this<br />

document.<br />

3.2.2.1 Use of st<strong>and</strong>ard procedure<br />

- In case that the export declaration was lodged electronically <strong>and</strong> the export declaration was registered<br />

with MRN, this MRN is after that used for identification of that export declaration during all next<br />

communication (declarant <strong>and</strong> customs office of export <strong>and</strong> vice versa, customs office of export <strong>and</strong><br />

customs office of exit <strong>and</strong> vice versa).<br />

- In case that the export declaration was lodged electronically, the decision on release of goods for export<br />

regime is issued by the customs office of export electronically <strong>and</strong> it is electronically sent to the<br />

declarant. Authentication of this decision shall be with an e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . At that time the<br />

Export Accompanying Document 20 <strong>and</strong> List of Items 21 (hereinafter called “Export Accompanying<br />

Document”), which shall conform to the specimens in Annexes 45c <strong>and</strong> 45d of Community <strong>Customs</strong><br />

Code Implementing Provisions, 9 shall be:<br />

o printed out by the customs office of export,<br />

20 The new annex to the <strong>Customs</strong> Law Implementing Regulation 2 containing the Export Accompanying Document shall be added.<br />

21 The new annex to the <strong>Customs</strong> Law Implementing Regulation 2 containing the List of Items shall be added.<br />

Page 51/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o verified by a customs officer from the customs office of export with his/her h<strong>and</strong>-written signature<br />

<strong>and</strong> personal customs stamp (a h<strong>and</strong>-written signature <strong>and</strong> personal customs stamp can be replaced<br />

by a code printed in box D of Export Accompanying Document), <strong>and</strong><br />

o issued to the declarant or his representative (person who presented the goods to the customs office of<br />

export).<br />

- In case that the export declaration was lodged electronically, the decision that the goods shall not be<br />

released for export regime is issued by the customs office of export electronically <strong>and</strong> it is electronically<br />

sent to the declarant. Authentication of this decision shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- In case that the export declaration was not lodged electronically, the decision on release of goods for<br />

export regime is issued by the customs office of export in the paper form, i.e. in the form of:<br />

o Export Accompanying Document – EAD, when the export declaration was lodged in the form of<br />

SAD (based on an Article of <strong>Customs</strong> Law Implementing Regulation 2 which shall be amended<br />

accordingly to the Community <strong>Customs</strong> Code Implementing Provisions 9 ),<br />

o Export Accompanying Document – EAD, when the export declaration was lodged in the written<br />

form other then SAD (based on an Article of <strong>Customs</strong> Law Implementing Regulation 2 which shall be<br />

amended accordingly to the Community <strong>Customs</strong> Code Implementing Provisions 9 ),<br />

o Export Accompanying Document – EAD, when the oral export declaration was lodged (see part<br />

3.2.1.3 of this document).<br />

- The decision on release of goods for export regime issued in the paper form (Export Accompanying<br />

Document – EAD) shall be authenticated by the customs officer from customs office of export with his<br />

h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

3.2.2.2 Use of simplified procedure of local clearance<br />

- Simplified procedure of local clearance in export cannot be used with paper or oral declaration for export<br />

regime according to the Articles 169, 200 <strong>and</strong> 201 of <strong>Customs</strong> Law Implementing Regulation 2 . The rules<br />

<strong>and</strong> processes described in part 3.2.1.1 of this document are used within the usage of simplified<br />

procedure of local clearance in export.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of local clearance in<br />

export through the data from modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised place, where goods are available, via code of this place (given in the authorisation),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for presenting the goods at the customs office of exit (given in the authorisation),<br />

o authorised country of final consignee (the list of prohibited countries is given in the authorisation),<br />

o identification of special seals (if they are used), via the serial number of the special seal (given in<br />

the authorisation).<br />

- When the simplified procedure of local clearance in export is used the documents to accompany the<br />

export declaration shall be available for customs at the declarant’s premise. This condition is set up in<br />

the authorisation of simplified procedure of local clearance in export issued by Macedonian customs<br />

authorities.<br />

- When all the above automated checks passed successfully, the electronic export declaration shall be<br />

accepted with MRN (Movement Reference Number) by the customs office of export. This MRN shall be<br />

electronically notified to a declarant. Authentication of this notification shall be with the e-signature of<br />

customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

- A declarant shall not wait for the authorisation for loading of goods to the loading compartment of<br />

means of transport. It is assumed that at the time of lodging of export declaration, the goods are already<br />

Page 52/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

loaded to the loading compartment of means of transport <strong>and</strong> they are ready for placing for export<br />

regime.<br />

- The goods are loaded to the loading compartment of means of transport <strong>and</strong> they are ready for releasing<br />

for export regime at the authorised place when the electronic export declaration is lodged. This place is<br />

registered <strong>and</strong> authorised within the authorisation of simplified procedure of local clearance in export (in<br />

the Authorisation sub-application).<br />

- The customs authorities (customs office of export within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of local clearance in export<br />

within the time limit (timer for automatic release of goods) set up in the within the authorisation of<br />

simplified procedure of local clearance in export (in the Authorisation sub-application).<br />

- When the decision on control of goods which have been declared within the simplified procedure of<br />

local clearance in export is taken, the notification of this control shall be electronically sent to the<br />

declarant or his representative (to a person who lodge the export declaration). Authentication of this<br />

notification of control shall be with an e-signature of customs administration, according to the Article<br />

109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . This notification shall be sent at the end of<br />

the time limit (timer for automatic release of goods) set up in the authorisation (in the Authorisation subapplication)<br />

to give a time to the customs authorities responsible for this control to be present at the<br />

authorised place, where the goods are available, before the notification is sent to the declarant or his<br />

representative (to a person who lodge the export declaration). At that time the timer for automatic release<br />

of goods shall be stopped.<br />

- When the timer for automatic release of goods expired <strong>and</strong> no decision on control of goods was taken,<br />

the goods are automatically released for export regime. The decision on release of goods for export<br />

regime shall be electronically sent to the declarant or his representative at that moment. Authentication<br />

of this decision shall be with an e-signature of customs administration, according to the Article 109 para.<br />

2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- Based on the decision on release of goods for export regime which was electronically sent to the<br />

declarant or his representative by the customs office of export, the declarant shall print out the Export<br />

Accompanying Document – EAD, which will follow the goods to the customs office of exit. The<br />

permission for printing out of EAD by the declarant is given according to the Article of <strong>Customs</strong> Law<br />

Implementing Regulation 2 which shall be amended accordingly to the Community <strong>Customs</strong> Code<br />

Implementing Provisions 9 . The EAD shall be authenticated by the stamp of holder of authorisation of<br />

local clearance in export (a declarant), which could be replaced by the imprint done within the printing<br />

of EAD.<br />

- The export operation can start immediately when the decision on release of goods for export regime is<br />

electronically delivered to the declarant or his representative <strong>and</strong> when the EAD is printed <strong>and</strong><br />

authenticated.<br />

- No supplementary export declaration shall be lodged by the declarant at the customs office of export.<br />

3.2.2.3 Use of simplified procedure of incomplete export declaration<br />

- According to the Article 167 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 the simplified procedure<br />

for incomplete export declaration shall allow the customs authority to accept, only in a duly justified<br />

case, an export declaration which does not contain all the particulars required, or which is not<br />

accompanied by all documents necessary for the customs export regime.<br />

- The minimum data elements of incomplete export declaration shall be introduced <strong>and</strong> it shall be in line<br />

with the Article 197 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The time limit for supplementary lodging of missing data or documents of incomplete export declaration<br />

shall be assigned by the customs office of export. St<strong>and</strong>ard time shall not be longer that 1 month. In dully<br />

justified cases <strong>and</strong> on the request of declarant the customs office of export can prolong this time period.<br />

Page 53/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

That period may not exceed 4 months from the date of acceptance of the declaration, according to the<br />

Article 197 para. 4 <strong>and</strong> Article 172 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The incomplete export declaration can be lodged in:<br />

o electronic form, or<br />

o paper form of SAD document, according to the Articles 169, 200 <strong>and</strong> 201 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The rules <strong>and</strong> processes described in parts 3.2.1.1 <strong>and</strong> 3.2.1.2 of this document are also used within the<br />

usage of simplified procedure of incomplete export declaration.<br />

- The acceptance of incomplete export declaration <strong>and</strong> release of goods for export regime shall be done by<br />

the customs office of export, as well as the acceptance of supplementary lodging of missing data or<br />

documents of incomplete export declaration.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of incomplete<br />

export declaration through the data from modules of Authorisation sub-application shall cover<br />

especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for presenting the goods at the customs office of exit (given in the authorisation),<br />

o authorised time for lodging the supplementary documents or data at the customs office of export<br />

(given in the authorisation),<br />

o authorised country of final consignee (the list of prohibited countries is given in the authorisation),<br />

o identification of special seals (if they are used), via the serial number of the special seal (given in<br />

the authorisation).<br />

- When the simplified procedure of incomplete export declaration is used the documents to accompany the<br />

export declaration shall be lodged together with the incomplete export declaration at the customs office<br />

of export.<br />

- When all the above automated checks passed successfully, the incomplete export declaration shall be<br />

accepted with MRN (Movement Reference Number) by the customs office of export. This MRN shall be<br />

notified to a declarant. Authentication of electronic notification shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- A declarant shall present the declared goods at the customs office of export. The goods are loaded to the<br />

loading compartment of means of transport <strong>and</strong> they are ready for releasing for export regime.<br />

- The decision on release of goods for export using the simplified procedure of incomplete export<br />

declaration is issued by the customs office of export in the form of Export Accompanying Document –<br />

EAD, which will follow the goods to the customs office of exit. The Export Accompanying Document –<br />

EAD shall be authenticated by the customs officer at the customs office of export with his/her h<strong>and</strong>written<br />

signature <strong>and</strong> personal customs stamp (a h<strong>and</strong>-written signature <strong>and</strong> personal customs stamp can<br />

be replaced by a code printed in box D of Export Accompanying Document).<br />

- When the incomplete export declaration was lodged electronically by the declarant, the decision on<br />

release of goods for export using the simplified procedure of incomplete export declaration is also sent<br />

from the customs office of export to the declarant in the form electronic message. Authentication of this<br />

decision shall be with an e-signature of customs administration, according to the Article 109 para. 2 of<br />

the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- The export operation can start immediately when the decision on release of goods for export regime is<br />

delivered to the declarant or his representative <strong>and</strong> when the EAD is printed <strong>and</strong> authenticated.<br />

3.2.2.4 Use of simplified procedure of simplified export declaration<br />

Page 54/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- According to the Article 167 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 the simplified procedure<br />

of simplified export declaration shall allow the customs authority to accept, only in a duly justified case,<br />

an simplified export declaration with subsequent presentation of a supplementary declaration.<br />

- The minimum data elements of simplified export declaration shall be introduced <strong>and</strong> it shall be in line<br />

with the Article 198 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- According to the Articles 198 para. 1 <strong>and</strong> 178 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 the<br />

time limit for lodging of supplementary export declaration shall be assigned by the customs office of<br />

export. The maximum time shall not be longer that 1 month.<br />

- The simplified export declaration can be lodged in:<br />

o paper form of a commercial or administrative document, accompanied by request for the goods to be<br />

placed under the export regime, or<br />

o paper form of incomplete SAD document, according to the Article 198 para. 2 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The rules <strong>and</strong> processes described in parts 3.2.1.1 <strong>and</strong> 3.2.1.2 of this document are also used within the<br />

usage of simplified procedure of simplified export declaration.<br />

- The acceptance of simplified export declaration <strong>and</strong> release of goods for export regime shall be done by<br />

the customs office of export, as well as the acceptance of supplementary export declaration.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of simplified export<br />

declaration through the data from modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for presenting the goods at the customs office of destination (given in the<br />

authorisation),<br />

o authorised time for lodging the supplementary export declaration at the customs office of export<br />

(given in the authorisation),<br />

o authorised country of final consignee (the list of prohibited countries is given in the authorisation),<br />

o identification of special seals (if they are used), via the serial number of the special seal (given in<br />

the authorisation).<br />

- When the simplified procedure of simplified export declaration is used the documents to accompany the<br />

export declaration shall be lodged together with the simplified export declaration at the customs office of<br />

export.<br />

- When all the above automated checks passed successfully, the simplified export declaration shall be<br />

accepted with MRN (Movement Reference Number) by the customs office of export. This MRN shall be<br />

notified to a declarant.<br />

- A declarant shall present the declared goods at the customs office of export. The goods are loaded to the<br />

loading compartment of means of transport <strong>and</strong> they are ready for releasing for export regime.<br />

- The decision on release of goods for export using the simplified procedure of simplified export<br />

declaration is issued by the customs office of export in the form of Export Accompanying Document –<br />

EAD, which will follow the goods to the customs office of exit. The Export Accompanying Document –<br />

EAD shall be authenticated by the customs officer at the customs office of export with his/her h<strong>and</strong>written<br />

signature <strong>and</strong> personal customs stamp (a h<strong>and</strong>-written signature <strong>and</strong> personal customs stamp can<br />

be replaced by a code printed in box D of Export Accompanying Document - EAD).<br />

- The export operation can start immediately when the decision on release of goods for export regime is<br />

delivered to the declarant or his representative <strong>and</strong> when the Export Accompanying Document - EAD is<br />

printed <strong>and</strong> authenticated.<br />

Page 55/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The subsequently presented supplementary export declaration, depending on the case, may have a<br />

general, periodic or recapitulative nature.<br />

- The supplementary declaration lodged within the use of simplified declaration for release of goods for<br />

export regime shall be lodged by the declarant in the form of:<br />

o electronic message (i.e. the electronic supplementary declaration), or<br />

o Single Administrative Document (SAD).<br />

- The decision on final release of the goods for export regime issued in the form of supplementary export<br />

declaration shall be registered with new MRN (Movement Reference Number) by the customs office of<br />

export. This MRN shall be notified to a declarant.<br />

- The decision on final release of goods for export regime shall be issued by the customs office of export:<br />

o electronically <strong>and</strong> it is electronically sent to the declarant with a message, in case of lodging the<br />

electronic supplementary declaration,<br />

o in the form of Single Administrative Document (SAD), in case of paper-based form, <strong>and</strong> it is given<br />

to the declarant.<br />

- In case that the decision on final release of goods for export regime issued electronically, the<br />

authentication of this decision shall be with the e-signature of customs administration, according to the<br />

Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- The decision on final release of goods for export regime issued in the form of Single Administrative<br />

Document (SAD) shall be authenticated by the customs officer from customs office of export with his<br />

h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

- The procedure of release of goods for export regime shall be finished when the exit of goods from the<br />

Macedonian customs territory is confirmed by the customs office of exit.<br />

3.2.2.5 Cancellation of export regime<br />

- The cancellation of the export regime (i.e. the decision on release of goods for export regime) shall be<br />

initiated either by a declarant or by the customs office of export (annulment/revocation of export<br />

declaration).<br />

- The cancellation of export regime by a declarant shall be initiated in:<br />

o electronic form, i.e. by an electronic message sent by a declarant to the customs office of export,<br />

o paper form lodged by a declarant at the customs office of export.<br />

- The export regime, i.e. the decision on release of goods for export regime, shall be cancelled by an<br />

electronic message sent to the customs office of export before the presenting the goods at the customs<br />

office of exit, i.e. before the message that goods have been presented at the customs office of exit is<br />

delivered to the customs office of export.<br />

- The cancellation of export regime initiated by a declarant in electronic form shall be confirmed by the<br />

customs office of export with an electronic message. Authentication of this decision shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

- The cancellation of a export regime initiated by a declarant in written form shall be confirmed by the<br />

customs office of export with the decision issued in written form.<br />

- When the <strong>Customs</strong> Officer at the customs office of export accepts the request for cancellation of a export<br />

operation (i.e. after the decision on release of goods for export regime), this means that the declared<br />

customs office of exit is already electronically notified on release of goods for export regime, the<br />

cancellation notification shall be sent to this declared customs office of exit.<br />

- The declared customs office of exit receives a cancellation notification from the customs office of<br />

export. The already registered Anticipated Arrival Record (AAR) is cancelled.<br />

Page 56/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.2.2.6 Consultation of the status of export declaration<br />

- A customs officer with an appropriate level of authorisation <strong>and</strong> access to export part of CDPS at any<br />

customs office, may request the movement information for a movement with a given MRN, i.e. the<br />

details of export declaration <strong>and</strong> up-dated information about the status of export operation. This includes<br />

the case of an en-route control, if access to the CDPS is available.<br />

- A declarant or his representative with access to web site of Macedonian customs administration may<br />

request the export movement information for a movement with a given MRN. <strong>System</strong> (CDPS) shall<br />

provide him via this web site with up-dated information about the status of export operation, especially<br />

whether:<br />

o export declaration was registered <strong>and</strong> accepted (when <strong>and</strong> where),<br />

o goods were released for export regime (when <strong>and</strong> where),<br />

o goods were presented at the customs office of exit (when <strong>and</strong> where),<br />

o control results were sent from the customs office of exit (when, where <strong>and</strong> result),<br />

o export regime was completed by the customs office of export (i.e. exit confirmation for exported<br />

goods has been sent to a declarant <strong>and</strong> to Macedonian Public Revenue Office which is responsible<br />

for VAT refund.<br />

3.2.3 <strong>Customs</strong> office of export <strong>Customs</strong> office of exit<br />

3.2.3.1 Anticipated Export Record<br />

- Where the declared goods have been released for export regime by the customs office of export, this<br />

office shall notify that to the customs office of exit with electronic message “Anticipated Export Record”<br />

sent via national domain, according to the Article of <strong>Customs</strong> Law Implementing Regulation 2 which<br />

shall be amended accordingly to the Community <strong>Customs</strong> Code Implementing Provisions 9 .<br />

- The customs office of exit shall carry out the necessary risk analysis in advance with the Risk analysis<br />

<strong>and</strong> risk management system sub-application on the data of export declaration received with<br />

“Anticipated Export Record” message. The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

exit to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- The results of control shall be registered at this customs office of exit.<br />

- Where the goods released for export regime are presented at the declared customs office of exit with the<br />

Export Accompanying Document (EAD), this customs office shall notify that to the customs office of<br />

export with an electronic message sent via national domain.<br />

- Where the goods released for export regime are presented at the different customs office, than originally<br />

declared customs office of exit, with the Export Accompanying Document (EAD), the new customs<br />

office of exit shall:<br />

o ask for the data at the customs office of export with an electronic message,<br />

o carry out the necessary risk analysis with the Risk analysis <strong>and</strong> risk management system subapplication,<br />

when “Anticipated Export Record” message is delivered,<br />

o decide on the possible control of goods,<br />

o decide on the completion of export regime,<br />

Page 57/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o notify that completion of export regime to the customs office of export with an electronic message<br />

sent via national domain.<br />

3.2.3.2 Export Accompanying Document<br />

- Where the goods released for export regime are presented at the declared customs office of exit, the<br />

Export Accompanying Document (EAD) shall be presented by a carrier.<br />

- The existence of the export movement in the CDPS will be checked by retrieving or requesting the<br />

information from the electronic message “Anticipated Export Record”. If the export declaration doesn’t<br />

exist at the customs office of export, the presented Export Accompanying Document will be considered<br />

as forged.<br />

- A warning shall be given by the system if the export operation is already recorded as:<br />

o having presented to another customs office of exit, or<br />

o having completed at another customs office of exit.<br />

3.2.3.3 Cancellation of export regime<br />

- When the <strong>Customs</strong> Officer at the customs office of export accepts the request for cancellation of an<br />

export regime (i.e. after the decision on release of goods for export regime), this means that the declared<br />

customs office of exit is already electronically notified on release of goods for export regime, the<br />

cancellation notification shall be sent to this declared customs office.<br />

- The declared customs office of exit receives a cancellation notification from the customs office of<br />

export. The already registered Anticipated Export Record (AER) is cancelled.<br />

3.2.4 Trade <strong>Customs</strong> office of exit<br />

3.2.4.1 Notification of arrival<br />

- In case that the export declaration was processed electronically at the customs office of export, the<br />

notification on release of goods for export regime is sent by the customs office of export electronically in<br />

the form of message “Anticipated Export Record” (501) to the customs office of exit.<br />

- In case that the export declaration was processed electronically at the customs office of export, the<br />

notification on arrival of goods at the customs office of exit is sent by the carrier (or a declarant)<br />

electronically in the form of message “Arrival at exit” (IE507) to the customs office of exit.<br />

3.2.4.2 Risk analysis <strong>and</strong> pre-requisite controls of data<br />

- The customs office of exit shall carry out the necessary risk analysis in advance with the Risk analysis<br />

<strong>and</strong> risk management system sub-application on the data of transit declaration received with message<br />

“Anticipated Export Record” (501). The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

3.2.4.3 Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure<br />

- According to the Article 408 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 the declarant or his<br />

representative (e.g. carrier) shall present the goods released for export regime at the customs office of<br />

exit with the Export Accompanying Document (EAD).<br />

- The carrier (or a declarant) shall notify the presentation of goods to the customs authority, i.e. to the<br />

customs office of exit, in the form of:<br />

o Export Accompanying Document (paper form),<br />

o CDPS message (electronic form) via an exit authority (e.g. exit authority at the airports).<br />

Page 58/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Electronic notification of presentation of goods to the customs office of exit by an exit authority shall be<br />

authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of an exit authority shall be replaced by e-signature according to the Article 5<br />

of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be registered together with the<br />

identification of an exit authority in the module for authorisation of e-communication in the<br />

Authorisation sub-application.<br />

- It is assumed that at the time of lodging of notification of presentation of goods to the customs authority,<br />

the goods are already available at the customs office of exit <strong>and</strong> they are ready for completion of export<br />

regime <strong>and</strong> for leaving the Macedonian customs territory.<br />

- The office of exit shall register with the MRN (Movement Reference Number) the presentation of goods<br />

to the customs authority <strong>and</strong> keep the Export Accompanying Document - EAD.<br />

- The customs office of exit shall take the decision on control of goods using the results of risk analysis<br />

from the Risk analysis <strong>and</strong> risk management system sub-application on the data of customs declaration<br />

received with “Anticipated Export Record” message.<br />

- When decision on control of goods which have been presented at the customs office of exit is taken, the<br />

notification of this control shall be passed to the carrier. Authentication of electronic form of this<br />

notification of control shall be with an e-signature of customs administration, according to the Article<br />

109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

exit to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

3.2.4.4 Diversion<br />

- The carrier may present the goods at the customs office other than the declared customs office of exit<br />

mentioned in export declaration, as well as in the Export Accompanying Document (EAD).<br />

- In case of diversion the carrier shall only present the goods released for export regime <strong>and</strong> the Export<br />

Accompanying Document (EAD) at the new customs office of exit. All other exchange of information<br />

shall be on the new customs office of exit, the customs office of export <strong>and</strong> the declared customs office<br />

of exit.<br />

- That new customs office of exit shall notify the customs office of export <strong>and</strong> ask for the data of export<br />

declaration using an electronic message sent to the customs office of export. The customs office of<br />

export shall immediately response on this request using an electronic message sent to the new customs<br />

office of exit.<br />

3.2.5 Exit authority (airport h<strong>and</strong>ling company) <strong>Customs</strong> of exit<br />

- In case of notification of exit lodged by the Exit authority (i.e. the airport h<strong>and</strong>ling company) at the<br />

customs office of exit the special procedure can/shall be developed. The Exit authority shall<br />

electronically notify to the customs office of exit:<br />

o the presentation of goods at the customs office of exit,<br />

o the exit of goods from the Macedonian customs territory or the Community customs territory.<br />

Page 59/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.2.5.1 Goods movement information<br />

- In case that the export declaration was processed electronically at the customs office of export, the<br />

notification on release of goods for export regime is sent by the customs office of export electronically in<br />

the form of message “Anticipated Export Record” (AER) to the customs office of exit.<br />

3.2.5.2 Risk analysis - pre-requisite controls of data<br />

- The customs office of exit shall carry out the necessary risk analysis in advance with the Risk analysis<br />

<strong>and</strong> risk management system sub-application on the data of transit declaration received with<br />

“Anticipated Export Record” message. The decision on control of goods shall be taken when goods are<br />

presented at this customs office.<br />

3.2.5.3 Presentation of goods<br />

- The carrier (or a declarant) can notify the presentation of goods to the customs authority at the customs<br />

office of exit with CDPS message (electronic form) via an exit authority (e.g. exit authority at the<br />

airports). Electronic notification of presentation of goods to the customs office of exit by an exit<br />

authority shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The h<strong>and</strong> written signature of an exit authority shall be replaced by e-signature according to the Article 5<br />

of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be registered together with the<br />

identification of an exit authority in the module for authorisation of e-communication in the<br />

Authorisation sub-application.<br />

- The rules <strong>and</strong> processes described in part 3.2.4.3 of this document are used within the communication<br />

with exit authority.<br />

- It is assumed that at the time of lodging of arrival notification, the goods are placed on the<br />

authorised/registered place <strong>and</strong> they are ready for loading to the loading compartment of means of<br />

transport (an aircraft) <strong>and</strong> for leaving the Macedonian customs territory. This place is registered <strong>and</strong><br />

authorised within the authorisation of simplified procedure authorised consignee.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of electronic communication with exit<br />

authority through the data from modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised place, where goods are available, via code of this place (given in the authorisation).<br />

- When the above automated checks passed successfully, the electronic notification shall be accepted<br />

within the electronic communication between the exit authority <strong>and</strong> the customs office of exit. This<br />

acceptance shall be electronically notified to the exit authority. Authentication of this message shall be<br />

with an e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

3.2.5.4 Control of goods<br />

- The exit authority shall wait for the decision on control of goods which are placed on the<br />

authorised/registered place <strong>and</strong> they are ready for loading to the loading compartment of means of<br />

transport (an aircraft) <strong>and</strong> for leaving the Macedonian customs territory. The timer is set up in the<br />

authorisation of electronic communication with exit authority (a module of Authorisation subapplication).<br />

- The customs authorities (customs office of exit within the working hours) shall take a decision on control<br />

of goods which have been presented by the exit authority within the time limit (timer for automatic<br />

release of goods for loading) set up in the within the authorisation of electronic communication with exit<br />

authority (a module of Authorisation sub-application).<br />

Page 60/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- When the decision on control of goods which have been released for export regime <strong>and</strong> they have been<br />

presented to the customs office of exit by the exit authority is taken, the notification of this control shall<br />

be electronically sent to the exit authority. Authentication of this notification of control shall be with an<br />

e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 . This notification shall be sent at the end of the time limit (timer for automatic<br />

release of goods for unloading) set up in the authorisation to give a time to the customs authorities<br />

responsible for this control to be present at the authorised place, where the goods are available, before<br />

the notification is sent to the exit authority. At that time the timer for automatic release of goods shall be<br />

stopped.<br />

- When the timer for automatic release of goods expired <strong>and</strong> no decision on control of goods was taken,<br />

the goods are automatically released for loading into the means of transport (an aircraft) by the exit<br />

authority <strong>and</strong> for leaving the Macedonian customs territory. The decision on release of goods for loading<br />

into the means of transport (an aircraft) shall be electronically sent to the exit authority at that moment.<br />

Authentication of this decision shall be with an e-signature of customs administration, according to the<br />

Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- Based on the decision on release of goods for loading into the means of transport (an aircraft) which was<br />

electronically sent to the exit authority by the customs office of exit, the exit authority shall:<br />

o start loading the means of transport (an aircraft),<br />

o check the goods on behalf of customs authorities at customs office of exit using the electronic data<br />

from export declaration received from the customs office of export (Export Accompanying<br />

Document – EAD shall not be used for this control),<br />

o inform the customs office of exit about the result of control within the time limit given in the<br />

authorisation,<br />

o immediately inform the customs office of exit about the discovered discrepancies <strong>and</strong> wait for the<br />

further instruction from the customs office of exit.<br />

3.2.5.5 Notification of exit<br />

- Where the export regime has completed <strong>and</strong> the exported goods left the Macedonian customs territory,<br />

the exit authority shall:<br />

o immediately notify the total exit or, where the case occurs, the partial exit to the customs office of<br />

exit with CDPS message (electronic form) in the time limit given in the authorisation, which shall<br />

be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o return Export Accompanying Document – EAD to the customs office of exit within the time limit<br />

given in the authorisation.<br />

3.2.6 <strong>Customs</strong> office of exit <strong>Customs</strong> office of export<br />

3.2.6.1 Presentation of goods at exit<br />

- Where the customs office of exit has received the notification of presentation of goods to the customs<br />

authority at exit <strong>and</strong> registered this notification with MRN, this customs office shall not notify the<br />

customs office of export on arrival of goods.<br />

- The notification of presentation of goods to the customs authority at exit shall contain the information<br />

about the total or partial intended leave with the given means of transport.<br />

- In case of total leave the Export operation state at the actual customs office of exit shall be set to “Goods<br />

released for immediate leave” totally.<br />

- In case of partial leave the Export operation state at the actual customs office of exit shall be set to<br />

“Goods released for immediate leave” partially.<br />

Page 61/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.2.6.2 Confirmation of Exit <strong>and</strong> Control results<br />

- The results of control shall be registered at the customs office of exit.<br />

- Based on the MRN <strong>and</strong> „Anticipated Export Record“ message <strong>and</strong> on the information on items of exited<br />

goods, the actual exit of the goods from the Macedonian customs territory shall be recorded (date + total<br />

exit or the partial exit + identity of the means of transport) at the customs office of exit.<br />

- If partial exit is recorded, the Export operation state at the actual customs office of exit shall be set to<br />

„Partially exited“.<br />

- If total exit is recorded, the Export operation state at the actual customs office of exit shall be set to<br />

'Exited'.<br />

- For each export operation for which the Export operation state is set to "Exited", the actual customs<br />

office of exit sends an “Exit control result” message to the customs office of export at the latest on the<br />

working day following the day the goods left the Macedonian customs territory.<br />

3.2.6.3 Discrepancies<br />

- The customs office of exit or the exit authority may discover some discrepancies between the export<br />

declaration <strong>and</strong> the goods presented to the customs authorities at exit.<br />

- Where the customs office of exit establishes that part of the goods or all of the goods are missing, it shall<br />

note these discrepancies <strong>and</strong> inform the customs office of export as the results of control with message<br />

“Exit control results”, according to the Article 408 para. 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Where the customs office of exit establishes that there are goods in excess, it shall note these<br />

discrepancies <strong>and</strong> refuse exit to these goods until the export formalities have been completed for all<br />

goods, according to the Article 408 para. 5 of <strong>Customs</strong> Law Implementing Regulation 2 . This means that<br />

for these excessive goods a new export declaration shall be lodged at the customs office of exit having<br />

the role of the customs office of export. After that the customs office of exit shall inform the customs<br />

office of export that all goods left the Macedonian customs territory <strong>and</strong> no discrepancies have been<br />

discovered as the results of control with message “Exit control results”.<br />

- Where the customs office of exit establishes a discrepancy in the nature of the declared goods, it shall<br />

note these discrepancies <strong>and</strong> refuse exit for such goods until the export formalities have been completed<br />

for the real nature of the goods, <strong>and</strong> shall also inform the customs office of export with message “Exit<br />

control results”. The customs office of export shall invalidate the export declaration based on that<br />

information. This means that for these goods a new export declaration shall be lodged at the customs<br />

office of exit having the role of the customs office of export.<br />

- Based on the request for solving the discrepancies the customs office of export shall take necessary<br />

measures for solving the discrepancies:<br />

o to modify the export declaration, in case of missing goods, or<br />

o to invalidate the export declaration, in case of different nature of goods, <strong>and</strong><br />

o to inform the declarant <strong>and</strong> verify the reasons of these discrepancies.<br />

3.2.6.4 Invalidation of export declaration acknowledgement<br />

- Where the export declaration is invalidated by the customs office of export, the electronic notification of<br />

invalidation shall be sent from the customs office of export to the customs office of exit.<br />

- Where the export declaration is modified by the customs office of export after the exit of goods, no<br />

electronic notification of modification shall be sent from the customs office of export to the customs<br />

office of exit.<br />

Page 62/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.2.7 Write-off by <strong>Customs</strong> office of export<br />

3.2.7.1 Exit of exported goods confirmed<br />

- The message “Exit control results” (IE518) sent from the customs office of exit to the customs office of<br />

export shall be used as a confirmation of the export regime having completed within the meaning of<br />

Article of <strong>Customs</strong> Law Implementing Regulation 2 which shall be amended accordingly to the<br />

Community <strong>Customs</strong> Code Implementing Provisions 9 similar like in paper environment according to the<br />

408 para. 6 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- This completion of export regime is registered with the same MRN (Movement Reference Number) as<br />

the original export declaration.<br />

3.2.7.2 Goods not exported<br />

- Where goods released for export do not leave the Macedonian customs territory, the exporter or<br />

declarant shall immediately inform the customs office of export, according to the Article 409 para. 1 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 . This information/notification can be submitted in the form of:<br />

o Export Accompanying Document (EAD) returned to that customs authority (paper form),<br />

o CDPS message (electronic form).<br />

- Where, in the cases referred to in Article 408 para. 6 of <strong>Customs</strong> Law Implementing Regulation 2 , a<br />

change in the transport contract has the effect of terminating inside the Republic of Macedonia a<br />

transport operation which should have finished outside it, the companies or authorities in question may<br />

carry out the amended contract only with the agreement of the customs authority referred to in Article<br />

408 paragraph (2) item a) of this Regulation or, in the case of a transit operation, the customs office of<br />

departure, according to the Article 409 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 . This<br />

information/notification can be submitted in the form of:<br />

o Export Accompanying Document (EAD) returned to that customs authority (paper form),<br />

o CDPS message (electronic form).<br />

- The declarant or the exporter shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 shall send the electronic notification that:<br />

o the goods released for export regime will not leave the Macedonian customs territory,<br />

o the transport contract is going to be changed, or<br />

o the transit declaration is going to be changed.<br />

- The h<strong>and</strong> written signature of the declarant or the exporter shall be replaced by e-signature according to<br />

the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be registered together<br />

with the identification of a consignee in the module for authorisation of e-communication in the<br />

Authorisation sub-application.<br />

3.2.7.3 Exit not confirmed – invalidation of export declaration<br />

- According to the Article 408 para. 7 of <strong>Customs</strong> Law Implementing Regulation 2 the customs office of<br />

export shall verify with the declarant or exporter whether the goods released for export procedure left the<br />

Macedonian customs territory. This verification procedure shall start when the time period given by<br />

Macedonian customs administration which is based on the time limit given by the customs office of<br />

export to the declarant for the exit of goods from the Macedonian customs territory.<br />

- In case that the export declaration was lodged electronically, this verification request shall be<br />

electronically sent by the customs office of export to a declarant or exporter. Authentication of this<br />

notification shall be with an e-signature of customs administration, according to the Article 109 para. 2<br />

of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- In case that the export declaration was not lodged electronically, this verification request shall be printed<br />

by CDPS <strong>and</strong> this paper form shall be sent to a declarant <strong>and</strong> exporter by the customs office of export.<br />

Page 63/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Where the customs office of export did not receive any information or proof from the customs office of<br />

exit or from the declarant or exporter that the goods released for export procedure left the Macedonian<br />

customs territory, this customs office of export shall invalidate the export regime (the decision on release<br />

of goods for export regime).<br />

- Where the export declaration is invalidated by the customs office of export, the electronic notification of<br />

invalidation shall be sent from the customs office of export to:<br />

o the declared customs office of exit,<br />

o the declarant <strong>and</strong> exporter.<br />

- In case that the export declaration was lodged electronically, this decision on invalidation of export<br />

regime shall be electronically sent by the customs office of export to the declarant or the exporter.<br />

Authentication of this notification shall be with an e-signature of customs administration, according to<br />

the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- In case that the export declaration was not lodged electronically, this decision on invalidation of export<br />

regime shall be printed by CDPS <strong>and</strong> this paper form shall be sent to a declarant <strong>and</strong> exporter by the<br />

customs office of export.<br />

3.2.7.4 Notification of exit to declarant <strong>and</strong>/or exporter<br />

- According to the Article of <strong>Customs</strong> Law Implementing Regulation 2 which shall be amended<br />

accordingly to the Community <strong>Customs</strong> Code Implementing Provisions 9 the customs office of export<br />

shall confirm the completion of exit regime to:<br />

o the declarant <strong>and</strong>/or the exporter (in case that he communicates with customs office of export<br />

electronically),<br />

o the national Public revenue office responsible for control of VAT return.<br />

- Authentication of this notification shall be with an e-signature of customs administration, according to<br />

the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

3.2.8 Diversion<br />

3.2.8.1 Export declaration request<br />

- The carrier may present the goods at the customs office other than the declared customs office of exit<br />

mentioned in export declaration, as well as in the Export Accompanying Document (EAD).<br />

- That new customs office of exit shall notify the customs office of export <strong>and</strong> ask for the data of export<br />

declaration using the electronic message “<strong>Declaration</strong> Request Export” (IE502) sent to the customs<br />

office of export.<br />

3.2.8.2 Export Advice Response<br />

- The customs office of export shall without delay (automatic responses) response on this request using the<br />

electronic message “<strong>Declaration</strong> response” (IE503) sent to the new customs office of exit.<br />

3.2.8.3 Diversion Notification<br />

- The customs office of export shall without delay (automatic responses) inform the declared customs<br />

office of exit, which is mentioned in the Export Accompanying Document (EAD) using the electronic<br />

message “Declared office of export not used” (IE524), that the exported goods were presented at another<br />

customs office of exit. The export operation shall be wrote-off at the declared customs office of exit.<br />

Page 64/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.2.9 Split Consignments<br />

3.2.9.1 Exit of goods via one <strong>Customs</strong> office of exit<br />

- Processes described in the parts 3.2.4.1 (Notification of arrival), 3.2.4.2 (Risk analysis <strong>and</strong> pre-requisite<br />

controls of data) <strong>and</strong> 3.2.4.3 (Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure) of this<br />

document shall be used at the customs office of exit, where the consignment of exported goods is split<br />

<strong>and</strong> the separate parts of this consignment are exported via this one customs office.<br />

- Where the consignment of exported goods is split <strong>and</strong> the separate parts of this consignment are exported<br />

via one customs office of exit, this customs office shall be notified by the carrier about the situation.<br />

- The customs office of exit shall use the message “Anticipated Export Record” (IE501) for control of<br />

separate parts of exported consignment which are gradually exported via this customs office. The<br />

customs office of exit shall:<br />

o register the results from these step-by-step controls,<br />

o register the exit of each separate part of the exported consignment.<br />

- When all parts of the exported consignment (all goods) left the Macedonian customs territory the<br />

customs office of exit shall send notification of exit with the results of control to the customs office of<br />

export.<br />

- Processes described in the part 3.2.7 (Write-off by <strong>Customs</strong> office of export) of this document shall be<br />

used.<br />

- Processes described in the part 3.2.6.3 (Discrepancies) of this document shall be used.<br />

3.2.9.2 Exit of goods via more than one <strong>Customs</strong> office of exit (computerised solution)<br />

- Processes described in the parts 3.2.4.1 (Notification of arrival), 3.2.4.2 (Risk analysis <strong>and</strong> pre-requisite<br />

controls of data) <strong>and</strong> 3.2.4.3 (Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure) of this<br />

document shall be used at all declared/actual customs offices of exit where the split separate parts of<br />

consignment of exported goods are presented.<br />

- In case that the export declaration was processed electronically at the customs office of export, the<br />

notification on release of goods for export regime is sent by the customs office of export electronically in<br />

the form of messages “Anticipated Export Record” (501) to all declared customs office of exit.<br />

- Where the consignment of exported goods is split <strong>and</strong> the separate parts of this consignment are exported<br />

via more than one customs office of exit, all these customs offices shall be notified by the carrier about<br />

the situation.<br />

- The customs office of exit shall use the message “Anticipated Export Record” (IE501) for control of<br />

separate part(s) of exported consignment which are gradually exported via this customs office. The<br />

customs office of exit shall:<br />

o register the result(s) from this(these) control(s),<br />

o register the exit of each separate part of the exported consignment.<br />

- When the each part of the exported consignment left the Macedonian customs territory each customs<br />

office of exit shall send notification of exit with the results of control to the customs of export.<br />

- The message “Exit control results” (IE518) sent from the customs office of exit to the customs office of<br />

export shall be used as a confirmation of the export regime having completed for one part of the split<br />

consignment within the meaning of Article of <strong>Customs</strong> Law Implementing Regulation 2 which shall be<br />

amended accordingly to the Community <strong>Customs</strong> Code Implementing Provisions 9 similar like in paper<br />

environment according to the 408 para. 6 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The all messages “Exit control results” (IE518) sent from all customs offices of exit to the customs<br />

office of export shall be used as a confirmation of the export regime having completed for whole<br />

Page 65/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

consignment. When all parts of the exported consignment (all goods) left the Macedonian customs<br />

territory the customs office of export shall write-off the export regime.<br />

- This completion of export regime is registered with the same MRN (Movement Reference Number) as<br />

the original export declaration.<br />

- Processes described in the part 3.2.6.3 (Discrepancies) of this document shall be used.<br />

3.2.9.3 Exit of goods via more than one <strong>Customs</strong> office of exit (paper solution)<br />

- Processes described in the parts 3.2.4.1 (Notification of arrival), 3.2.4.2 (Risk analysis <strong>and</strong> pre-requisite<br />

controls of data) <strong>and</strong> 3.2.4.3 (Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure) of this<br />

document shall be used at first declared/actual customs office of exit where the split separate part of<br />

consignment of exported goods is presented.<br />

- Processes described in the parts 3.2.4.1 (Notification of arrival), 3.2.4.2 (Risk analysis <strong>and</strong> pre-requisite<br />

controls of data) <strong>and</strong> 3.2.4.3 (Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure) of this<br />

document shall be modified due to the fact that all these processes shall be carried out based on Export<br />

Accompanying Document only.<br />

- In case that the export declaration was processed electronically at the customs office of export, the<br />

notification on release of goods for export regime is sent by the customs office of export electronically in<br />

the form of messages “Anticipated Export Record” (501) to first declared customs office of exit.<br />

- Where the consignment of exported goods is split <strong>and</strong> the separate parts of this consignment are exported<br />

via more than one customs office of exit, all these customs offices shall be notified by the carrier about<br />

the situation.<br />

- The first declared/actual customs office of exit shall use the message “Anticipated Export Record”<br />

(IE501) for control of first part of exported consignment which exported via this customs office. Another<br />

actual customs office of exit shall use the Export Accompanying Document for control of next part of<br />

exported consignment which exported via this customs office. Each customs office of exit shall:<br />

o register the result from this control,<br />

o register the exit of each separate part of the exported consignment,<br />

o notify the first declared customs office of export about the control <strong>and</strong> exit of goods.<br />

- When all parts of the exported consignment (all goods) left the Macedonian customs territory the first<br />

customs office of exit shall send notification of exit with the results of control to the customs of export.<br />

- This completion of export regime is registered with the same MRN (Movement Reference Number) as<br />

the original export declaration.<br />

- Processes described in the part 3.2.7 (Write-off by <strong>Customs</strong> office of export) of this document shall be<br />

used.<br />

- Processes described in the part 3.2.6.3 (Discrepancies) of this document shall be used.<br />

3.2.10 Consolidated Consignments<br />

- Processes described in the parts 3.2.4.1 (Notification of arrival), 3.2.4.2 (Risk analysis <strong>and</strong> pre-requisite<br />

controls of data) <strong>and</strong> 3.2.4.3 (Presentation of goods <strong>and</strong> controls with st<strong>and</strong>ard procedure) of this<br />

document shall be used at the customs office of exit, where the consignments of exported goods are<br />

consolidated <strong>and</strong> exported via this customs office.<br />

- Where the consignments of exported goods are consolidated <strong>and</strong> exported via one customs office of exit,<br />

this customs office shall be notified by the carrier about the situation.<br />

Page 66/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The customs office of exit shall use the message “Anticipated Export Record” (IE501) for control of<br />

each exported consignment which consolidated <strong>and</strong> exported via this customs office. The customs office<br />

of exit shall:<br />

o register the result of control for each consignment,<br />

o register the exit of each consignment.<br />

- When consolidated consignment (all goods) left the Macedonian customs territory the customs office of<br />

exit shall send notifications of exit with the results of control for all parts of consolidate consignment to<br />

the customs office(s) of export.<br />

- Processes described in the part 3.2.7 (Write-off by <strong>Customs</strong> office of export) of this document shall be<br />

used.<br />

- Processes described in the part 3.2.6.3 (Discrepancies) of this document shall be used.<br />

3.3 Export control system<br />

- This module of CDPS shall be obligatory after the change of customs legislation or after the accession<br />

into EU for the acceptance <strong>and</strong> processing of exit summary declaration for goods leaving<br />

o Macedonian customs territory (based on the change of national customs legislation which shall be<br />

amended accordingly to the Community <strong>Customs</strong> Code 8 <strong>and</strong> <strong>Customs</strong> Code Implementing<br />

Provisions 9 ), or<br />

o customs territory of the Community (based on the accession of Macedonia into the EU).<br />

- Goods leaving the Macedonian customs territory or the customs territory of the Community, with the<br />

exception of goods carried on means of transport only passing through the territorial waters or the<br />

airspace of the customs territory without a stop within this territory, shall be covered either by a customs<br />

declaration or, where a customs declaration is not required, an exit summary declaration.<br />

3.3.1 Trade <strong>Customs</strong> office of lodgement of EXD<br />

3.3.1.1 Electronic exit summary declaration<br />

- Lodging of electronic exit summary declaration (IE615) is possible according to the Article of <strong>Customs</strong><br />

Law 1 , which shall be amended accordingly to the Community <strong>Customs</strong> Code 8 .<br />

- Electronic lodging of exit summary declaration by a person who brings the goods, or who assumes<br />

responsibility for the carriage of the goods, out of the Macedonian customs territory or the customs<br />

territory of the Community shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a person who brings the goods, or who assumes responsibility for the<br />

carriage of the goods, out of the Macedonian customs territory or the customs territory of the<br />

Community, shall be replaced by e-signature according to the Article 5 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 . The e-signature(s) shall be registered together with the identification of that person in the<br />

module for authorisation of e-communication in the Authorisation sub-application.<br />

- The electronic exit summary declaration (IE615) shall be lodged at the customs office of lodgement or<br />

directly at the customs office of exit within the specified time limit <strong>and</strong> before the goods are brought out<br />

of the Macedonian customs territory or the customs territory of the Community.<br />

- Automated initial checks of electronic exit summary declaration shall cover:<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application,<br />

o filling in the data-elements or data-groups (boxes of exit summary),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

Page 67/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of exit summary declaration<br />

(logical controls).<br />

3.3.1.2 Paper-based exit summary declaration<br />

- The customs office of exit may accept paper-based exit summary declarations in exceptional<br />

circumstances, provided that they apply the same level of risk management as that applied to exit<br />

summary declarations made using a data processing technique according to the Article of <strong>Customs</strong> Law 1 ,<br />

which shall be amended accordingly to the Community <strong>Customs</strong> Code 8 .<br />

- Data of paper-based exit summary declaration shall be:<br />

o keyed in to the CDPS by a customs officer at the customs office of exit, or<br />

o electronically lodged to the customs office of exit in parallel with the paper-based exit summary<br />

declaration <strong>and</strong> it is not necessary to be approved by customs authorities.<br />

- The paper-based exit summary declaration shall be lodged at the customs office of exit within the<br />

specified time limit <strong>and</strong> before the goods are brought out of the Macedonian customs territory or the<br />

customs territory of the Community.<br />

- Automated initial checks of paper-based exit summary declaration shall cover:<br />

o filling in the data-elements or data-groups (boxes of exit summary declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of exit summary declaration<br />

(logical controls).<br />

3.3.1.3 Acceptance, modifications, rectifications <strong>and</strong> deletions of EXD<br />

- The exit summary declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference<br />

Number) by the customs office of lodgement/customs office of exit if all above automated checks passed<br />

successfully.<br />

- If any automatic checks didn’t pass successfully the exit summary declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified by a customs officer to the person, who<br />

lodged the electronic exit summary declaration. Receiving this information the person, who lodged the<br />

exit summary declaration, shall:<br />

o amend his refused exit summary declaration <strong>and</strong> lodge it (with same LRN) again to the customs<br />

office of lodgement/customs office of exit, or<br />

o lodge a new exit summary declaration to the customs office of lodgement/customs office of exit<br />

(with new LRN).<br />

- The registered or accepted exit summary declaration can be changed by a person, who lodged the exit<br />

summary declaration, before the decision on a control of goods is taken. When the exit summary<br />

declaration was registered or accepted by the customs office of lodgement/customs office of exit, this<br />

exit summary declaration can be:<br />

o modified by an electronic message (with MRN <strong>and</strong> same LRN) sent to the customs office of<br />

lodgement/customs office of exit, or<br />

o changed or amended by a new exit summary declaration which shall be sent to the customs office of<br />

lodgement/customs office of exit (old exit summary declaration shall be cancelled by another<br />

electronic message),<br />

o cancelled by a message sent to the customs office of lodgement/customs office of exit.<br />

- Any modification or cancellation done by an electronic message shall be confirmed by the customs<br />

office of lodgement/customs office of exit with an electronic message. Authentication of this decision<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

Page 68/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- After the acceptance of exit summary declaration by the customs office of lodgement/customs office of<br />

exit the decision on control based on full safety <strong>and</strong> security related risk analysis shall be taken by a<br />

customs officer at the customs office of lodgement/customs office of exit. The Risk analysis <strong>and</strong> risk<br />

management system sub-application shall be used for automated evaluation of possible risks.<br />

3.3.2 Trade <strong>Customs</strong> office of exit<br />

3.3.2.1 Risk analysis - pre-requisite controls of data<br />

- In case that the exit summary declaration was processed electronically at the customs office of<br />

lodgement, the customs office of exit:<br />

o shall receive the exit summary declaration with full safety <strong>and</strong> security related risk analysis from<br />

the customs office of lodgement,<br />

o can carry out the own risk analysis in advance based on the data of exit summary declaration.<br />

- In case that the exit summary declaration was processed electronically at the customs office of exit the<br />

full safety <strong>and</strong> security related risk analysis shall be done at that customs office.<br />

3.3.2.2 Notification of arrival<br />

- In case that the exit summary declaration was processed electronically at the customs office of<br />

lodgement, this exit summary declaration <strong>and</strong> the risk analysis result is sent by the customs office of<br />

lodgement electronically in the form of message (IE601) to the declared customs office of exit.<br />

- In case that the exit summary declaration was processed electronically at the customs office of<br />

lodgement/customs office of exit, the notification on arrival of goods at the customs office of exit is sent<br />

by the carrier (or a the person who brings the goods, or who assumes responsibility for the carriage of the<br />

goods, out of the Macedonian customs territory or the customs territory of the Community)<br />

electronically in the form of message “Arrival at exit” (IE507) to the customs office of exit.<br />

3.3.2.3 Presentation of goods<br />

- According to the Article of <strong>Customs</strong> Law 1 , which shall be amended accordingly to the Community<br />

<strong>Customs</strong> Code 8 the person who brings the goods, or who assumes responsibility for the carriage of the<br />

goods, out of the Macedonian customs territory or the customs territory of the Community (i.e. a carrier)<br />

shall present that goods at the customs office of exit with the notification of exit in the form of message<br />

“Arrival at exit” (IE507).<br />

3.3.2.4 Control of goods<br />

- When decision on control of goods which have been presented at the customs office of exit is taken, the<br />

notification of this control shall be passed to the carrier. Authentication of electronic form of this<br />

notification of control shall be with an e-signature of customs administration, according to the Article<br />

109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

exit to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

Page 69/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- When decision on control of goods is taken, the exit summary declaration cannot be changed, modified,<br />

amended or cancelled at the customs office of exit. The results of control shall be registered at this<br />

customs office.<br />

- Based on the customs control, the declared goods can be allowed to leave the Macedonian customs<br />

territory or the customs territory of the Community or the exit summary declaration can be modified,<br />

changed or cancelled.<br />

3.3.2.5 Diversion<br />

- Same procedure as described in part 3.2.4.4 shall be used in case of diversion of movement from<br />

declared customs office of exit to the new one.<br />

3.3.3 Exit authority (airport h<strong>and</strong>ling company) <strong>Customs</strong> of exit<br />

- Same procedure as described in part 3.2.5 shall be used in case of notification of exit lodged by the Exit<br />

authority (i.e. the airport h<strong>and</strong>ling company) at the customs office of exit.<br />

3.4 Import regimes<br />

3.4.1 Trade <strong>Customs</strong> office of lodgement of summary declaration<br />

3.4.1.1 Electronic or paper summary declaration<br />

- Lodging of electronic summary declaration is possible according to the Article 54 para. 1 of <strong>Customs</strong><br />

Law 1 . Electronic lodging of electronic summary declaration by the person, who is identified in the<br />

Article 54 para. 2 of <strong>Customs</strong> Law, 1 shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong><br />

Law Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a person, who is identified in the Article 54 para. 2 of <strong>Customs</strong> Law, 1 shall<br />

be replaced by e-signature according to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 . The e-<br />

signature(s) shall be registered together with the identification of this person in the module for<br />

authorisation of e-communication in the Authorisation sub-application.<br />

- Lodging of paper customs export declaration is possible in prescribed forms according to Article 54 para.<br />

1 of <strong>Customs</strong> Law 1 :<br />

o in the form given by the Article 96 para. 2 <strong>and</strong> the Annex 17 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ,<br />

o in the other paper form than given in the Annex 17 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Data of paper customs export declaration shall be:<br />

o keyed in to the CDPS by a customs officer at the customs office, or<br />

o electronically lodged to the customs office in parallel with the paper-based summary declaration<br />

<strong>and</strong> it is not necessary to be approved by customs authorities.<br />

- It is assumed that at the time of lodging of a summary declaration, the goods are already presented to the<br />

customs office <strong>and</strong> they are ready for granting the status of temporary storage.<br />

- Automated initial checks of summary declaration shall cover:<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application, in case of electronic summary declaration,<br />

o filling in the data-elements or data-groups (boxes of summary declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups,<br />

Page 70/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o check of guarantee through data from Guarantee management system sub-application, which shall<br />

cover the existence, validity, authorisation by a person with access code (PIN), sufficient amount<br />

of guarantee (at least on line management of comprehensive guarantees <strong>and</strong> individual guarantee).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of summary declaration (logical<br />

controls).<br />

- The summary declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number) by<br />

the customs office if all above automated checks passed successfully. This MRN shall be notified to a<br />

person, who lodged the summary declaration. Authentication of electronic notification shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- If any automatic checks didn’t pass successfully the summary declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified to a person, who lodged the summary<br />

declaration. Authentication of electronic notification shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

Receiving this information the person, who is identified in the Article 54 para. 2 of <strong>Customs</strong> Law, 1 shall:<br />

o amend his refused summary declaration <strong>and</strong> lodge it (with same Local Reference Number - LRN)<br />

again to the customs office, or<br />

o lodge a new summary declaration to the customs office (with new LRN).<br />

3.4.1.2 Acceptance, modifications, rectifications <strong>and</strong> deletions of SD<br />

- The summary declaration shall be accepted by the customs office when:<br />

o all above automatic checks passed successfully,<br />

o the goods are presented to that customs office.<br />

- In case that the summary declaration was lodged electronically, this MRN shall be electronically notified<br />

to a person, who lodged this summary declaration. Authentication of this notification shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 . In case that the summary declaration was not lodged electronically, the<br />

acceptance of summary declaration with this MRN shall be notified (oral notification) to a person, who<br />

lodged this summary declaration at the customs office.<br />

- The registered or accepted summary declaration can be changed by a principal before the decision on a<br />

control of goods is taken. When summary declaration was registered or accepted by the customs office,<br />

this summary declaration can be:<br />

o modified by an electronic message (with MRN <strong>and</strong> same LRN) sent to the customs office, or<br />

o changed or amended by a summary declaration which shall be sent to the customs office (old<br />

summary declaration shall be cancelled by another electronic message),<br />

o cancelled by a message sent to the customs office.<br />

- Any modification or cancellation of summary declaration done by an electronic message shall be<br />

confirmed by the customs office with an electronic message. Authentication of this decision shall be with<br />

an e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

- After the acceptance of summary declaration by the customs office the decision on control shall be taken<br />

by a customs officer at the customs office. The Risk analysis <strong>and</strong> risk management system subapplication<br />

shall be used for automated evaluation of possible risks.<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office to<br />

be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

Page 71/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- When decision on control of goods is taken, the summary declaration cannot be changed, modified,<br />

amended or cancelled at the customs office. The results of control shall be registered at this customs<br />

office.<br />

- Based on the customs control, the summary declaration shall be modified, changed or cancelled, if it is<br />

necessary.<br />

- Based on the customs control, the goods declared in the summary declaration shall be released for<br />

temporary storage <strong>and</strong> the lodged/declared guarantee shall be used <strong>and</strong> registered in the Guarantee<br />

management system sub-application.<br />

3.4.1.3 Temporary storage<br />

- The goods presented to a customs authority (customs office) shall, following such presentation, have the<br />

status of goods in temporary storage until such time as they are assigned a customs-approved treatment<br />

or use (e.g. the release for customs procedure), according to the Article 60 of <strong>Customs</strong> Law 1 . According<br />

to the Article 99 of <strong>Customs</strong> Law Implementing Regulation 2 the goods shall be placed in a temporary<br />

storage facility on the basis of the summary declaration.<br />

- Where the place referred to in Article 61 para. 1 of the <strong>Customs</strong> Law 1 has been approved on a permanent<br />

basis for the placing of goods in temporary storage, according to the Article 98 para.1 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 , <strong>and</strong> such place shall be called “temporary storage facility”. The temporary<br />

storage facility shall be registered in the Authorisation sub-application.<br />

3.4.1.4 Release from temporary storage<br />

- The goods with the status of goods in temporary storage shall stay in the temporary storage facility until<br />

such time as they are assigned a customs-approved treatment or use (e.g. the release for customs<br />

procedure).<br />

- The CDPS shall change the status of goods <strong>and</strong> release from temporary storage where a customsapproved<br />

treatment or use is assigned by the customs officer at the customs office. The release of goods<br />

from temporary storage shall be:<br />

o partial release, when to a part of goods declared in one summary declaration has not been assigned<br />

any customs-approved treatment or use,<br />

o total release, when to all goods declared in one summary declaration has been assigned a customsapproved<br />

treatment or use.<br />

- The CDPS shall automatically check the quantity of goods with the status of goods in temporary storage<br />

based on the partial or total release.<br />

3.4.2 Trade <strong>Customs</strong> office of import<br />

3.4.2.1 Electronic or paper-based import declaration<br />

- Lodging of electronic customs declaration is possible according to the Article 71 para. b) <strong>and</strong> Article 89<br />

of <strong>Customs</strong> Law 1 . Electronic lodging of customs declaration for any import regime by a declarant or his<br />

representative shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The h<strong>and</strong> written signature of a declarant or his representative shall be replaced by e-signature according<br />

to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 . The e-signature(s) shall be registered<br />

together with the identification of a declarant (or his representative) in the module for authorisation of e-<br />

communication in the Authorisation sub-application.<br />

Page 72/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Lodging of electronic customs declaration for import regime is obligatory for granting the simplified<br />

procedure of local clearance in<br />

o free circulation regime, according to the Articles 179 - 183 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ,<br />

o customs warehousing regime, according to the Articles 188 - 190 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ,<br />

o inward processing regime, according to the Articles 188 - 190 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ,<br />

o temporary import regime, according to the Articles 188 - 190 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 ,<br />

o processing under the customs control regime, according to the Articles 188 - 190 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure (if it is used)<br />

through the data from modules of Authorisation sub-application shall cover the authorisation of<br />

simplified procedure local clearance for placing of goods under:<br />

o free circulation regime,<br />

o customs warehousing regime,<br />

o inward processing regime,<br />

o temporary import regime,<br />

o processing under the customs control regime.<br />

- Lodging of paper customs import declaration is possible in prescribed forms according to Article 72<br />

para. 1 of <strong>Customs</strong> Law 1 :<br />

o in the form of SAD, according to Articles 115 - 117 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o in the other form than SAD based on the authorisation issued by the customs authorities, according<br />

to Article 116 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- Data of paper customs export declaration shall be:<br />

o keyed in to the CDPS by a customs officer at the customs office of import, or<br />

o electronically lodged to the customs office of import in parallel with the paper-based customs<br />

import declaration <strong>and</strong> it is not necessary to be approved by customs authorities.<br />

- Due to the basic principles of import procedures (as a chain of temporary storage <strong>and</strong> import regimes), it<br />

would be appropriate to develop the possibility of re-usage of the data already filled in the summary<br />

declaration or import system, i.e. the data from summary declaration or a declaration for the regime with<br />

economic impact at the customs office of import should be processed to the further import declaration.<br />

The data can be modified, i.e. some data could be added or some data could be deleted or amended, by<br />

the customs officer at his new customs office of departure based on the content of import declaration.<br />

- The customs officer shall have a possibility for temporary storage of unfinished entry of import<br />

declaration. The MCA shall set up the time limit for this temporary storage of unfinished import<br />

declaration.<br />

- It is assumed that at the time of lodging of import declaration:<br />

o the goods are already ready to be presented to the customs office of import <strong>and</strong> they are ready for<br />

placing for any import regime, or<br />

o the goods will be presented to the customs office of import <strong>and</strong> they will be ready for placing<br />

under any import regime later on based on the authorisation of customs authorities according to the<br />

Article 111 para. 2 <strong>Customs</strong> Law Implementing Regulation 2 . This authorisation shall contain the<br />

time limit for presentation of the goods <strong>and</strong> it shall be registered in the Authorisation subapplication.<br />

- Automated initial checks of import customs declaration shall cover:<br />

Page 73/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application, in case of lodging of import customs declaration,<br />

o filling in the data-elements or data-groups (boxes of declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups (boxes of<br />

declaration).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls).<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of import licences through the data from licence’s<br />

module of Single window sub-application.<br />

- Automated check of guarantee through data from module for guarantees for other then transit regime of<br />

Guarantee management system sub-application shall cover the existence, validity, authorisation by a<br />

declarant with access code (PIN), sufficient amount of guarantee (at least on line management of<br />

comprehensive guarantees <strong>and</strong> individual guarantees).<br />

- The import declaration shall be registered with MRN (Movement Reference Number) by the customs<br />

office of import if all above automated checks passed successfully. In case of electronic import<br />

declaration, this registration of customs declaration with MRN shall be electronically notified to a<br />

declarant. Authentication of this notification shall be with an e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- If any automatic checks didn’t pass successfully the import declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified to a declarant. In case of electronic import<br />

declaration, this information shall be notified electronically. Authentication of this electronic notification<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 . Receiving this information a declarant shall:<br />

o amend his refused import declaration <strong>and</strong> lodge it (with same Local Reference Number - LRN)<br />

again to the customs office of import, or<br />

o lodge a new import declaration to the customs office (with new LRN).<br />

3.4.2.2 Oral import declarations<br />

- Lodging of oral import declaration is possible according to Article 71 para. c) <strong>and</strong> Article 89 para. 2) of<br />

<strong>Customs</strong> Law 1 <strong>and</strong> under the conditions given in Article 132, in case of free circulation regime, <strong>and</strong><br />

Article 136, in case of temporary import regime, of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The data elements of the oral import declaration shall be introduced by MCA. Data of oral import<br />

declaration shall be keyed in to the CDPS by a customs officer at the customs office of import.<br />

- It is assumed that at the time of lodging of oral import declaration, the goods are already presented to the<br />

customs authorities <strong>and</strong> they are ready for placing for free circulation regime or temporary import<br />

regime.<br />

- Automated initial checks of data of oral import declaration:<br />

o filling in the data-elements or data-groups,<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of declaration (logical controls<br />

specified for each type of import declaration).<br />

- The oral import declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference Number)<br />

by the customs office of import if all above automated checks passed successfully.<br />

- If any automatic checks didn’t pass successfully the import declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified by a customs officer to a declarant (oral<br />

notification). Receiving this information a declarant shall:<br />

o amend his refused export declaration <strong>and</strong> lodge it again to the customs office of import, or<br />

o lodge a new import declaration to the customs office of import.<br />

Page 74/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.4.2.3 Documents to accompany the import declaration<br />

- Necessary documents to accompany the import declaration shall be lodged by a declarant to the office of<br />

import according to the Article 72 para. 2 of <strong>Customs</strong> Law 1 <strong>and</strong> Article 125, in case of free circulation<br />

regime, or Article 127, in case of customs regimes with economic impact, of <strong>Customs</strong> Law<br />

Implementing Regulation 2 . The customs office of import may dispense with the presentation of these<br />

documents at the time of completion of the formalities at customs office of import.<br />

- The documents to accompany the import declaration shall be lodged by a declarant to the office of<br />

import in electronic or paper form. The electronic form of documents to accompany the import<br />

declaration shall be determined by the Macedonian customs administration, including the determination<br />

of manner of keeping of the documents that are transmitted by electronic means, according to the Article<br />

131 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The electronic form of documents to accompany the import declaration shall be authenticated with<br />

electronic signature of a declarant. The delivery <strong>and</strong> acceptance of electronic form of documents to<br />

accompany the import declaration shall be electronically notified to a declarant by customs office of<br />

import with information about the acceptance of import declaration. Authentication of this notification<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

- The import declaration shall be accepted by the customs office of import, when the documents to<br />

accompany the import declaration are presented at that customs office with the goods to be released for<br />

the import regime.<br />

- When the simplified procedure local clearance in import regime is used the documents to accompany the<br />

import declaration shall be available for customs at the declarant’s premise.<br />

3.4.2.4 Control of accompanied documents<br />

- The initial automatic control of documents to accompany the import declaration, which were lodged in<br />

electronic form, shall be based on the comparison of type <strong>and</strong> identification number of these documents,<br />

which were provided in the import declaration, <strong>and</strong> the documents sent by a declarant. The passing this<br />

control shall be sufficient for acceptance of a customs import declaration.<br />

- The detailed control of documents to accompany the import declaration, which were lodged in electronic<br />

or paper form, shall be carried out by a customs officer at the customs office of import.<br />

- The result of the detailed control of these electronic documents can be:<br />

o the confirmation of acceptance of customs declaration, in case of electronic lodgement of customs<br />

declaration <strong>and</strong> these documents, or<br />

o the cancellation of acceptance of customs declaration due to invalid documents.<br />

- The result of the detailed control of these paper-based documents can be:<br />

o the acceptance of customs declaration, in case of lodgement of paper-based documents, or<br />

o not-acceptance of customs declaration due to invalid documents.<br />

3.4.2.5 Acceptance, modifications, rectifications <strong>and</strong> deletions of import declarations<br />

- The import declaration shall be accepted by the customs office of import when:<br />

o all above automatic checks passed successfully,<br />

o all documents to accompany the import declaration are lodged by a declarant to that customs office<br />

or the waiver for lodging the documents to accompany the import declaration was granted or the<br />

simplified procedure local clearance in import regime is used,<br />

o the goods are presented to that customs office.<br />

Page 75/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- In case that the import declaration was lodged electronically, this acceptance of customs declaration with<br />

MRN shall be electronically notified to a declarant. Authentication of this notification shall be with an e-<br />

signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 . In case that the import declaration was not lodged electronically, the<br />

acceptance of import declaration with this MRN shall be notified to a declarant (oral notification) at the<br />

customs office of import.<br />

- The registered or accepted import declaration can be changed by a declarant before the decision on a<br />

control of goods is taken. When import declaration was registered or accepted by the customs office of<br />

import, this electronic import declaration can be:<br />

o modified by an electronic message (with MRN <strong>and</strong> same LRN) sent to the customs office of import,<br />

or<br />

o changed or amended by a new import declaration which shall be sent to the customs office of import<br />

(old import declaration shall be cancelled by another electronic message),<br />

o cancelled by a message sent to the customs office of import.<br />

- Any modification or cancellation done by an electronic message shall be confirmed by the customs<br />

office of import with an electronic message. Authentication of this decision shall be with an e-signature<br />

of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 .<br />

- After the acceptance of import declaration by the customs office of import the request for allocation of<br />

requested import quota (in free circulation regime or in drawback system of inward processing regime),<br />

if it was indicated in the customs declaration, shall be processed by the quotas module of Single window-<br />

MK sub-application.<br />

- After the acceptance of import declaration by the customs office of import the decision on control shall<br />

be taken by a customs officer at the customs office of import. The Risk analysis <strong>and</strong> risk management<br />

system sub-application shall be used for automated evaluation of possible risks.<br />

- If CDPS is also used for the purpose of safety <strong>and</strong> security, this means that the import declaration is<br />

lodged at the customs office of entry instead of entry summary declaration, then full safety <strong>and</strong> security<br />

related risk analysis for all the goods shall be performed additionally within the prescribed time limits<br />

(after the change of national customs legislation or after the accession into EU).<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

import to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o declarant’s approval of amendment of import declaration based on the discovered discrepancies,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- When decision on control of goods is taken, the import declaration cannot be changed, modified,<br />

amended or cancelled at the customs office of import. The results of control shall be registered at this<br />

customs office.<br />

- Based on the customs control, the declared goods can be released for import regime or the import<br />

declaration can be modified, changed or cancelled.<br />

3.4.2.6 Cancellation of import declaration<br />

- The cancellation of the import declaration (before the decision on release of goods is taken) shall be<br />

initiated either by a declarant or by the customs office of import (annulment/revocation of import<br />

declaration).<br />

Page 76/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The cancellation of import declaration by a declarant shall be initiated in:<br />

o electronic form, i.e. by an electronic message sent by a declarant to the customs office of import,<br />

o paper form lodged by a declarant at the customs office of import.<br />

- The registered or accepted import declaration shall be cancelled by an electronic message sent to the<br />

customs office of import before the decision on control of goods is taken or after the customs control.<br />

- The cancellation of import declaration done by an electronic message shall be confirmed by the customs<br />

office of import with an electronic message. Authentication of this decision shall be with an e-signature<br />

of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing<br />

Regulation 2 . The cancellation initiated in paper form shall be confirmed by the customs office of import<br />

in paper form.<br />

3.4.3 <strong>Customs</strong> office of import <strong>Customs</strong> office of guarantee<br />

3.4.3.1 Check of the guarantee<br />

- The guarantees shall be checked <strong>and</strong> registered based on data of the accepted import declaration.<br />

- CDPS shall assist in calculation of amount of duties <strong>and</strong> taxes based on of the highest import duties<br />

applicable to goods of the same kind in the Republic of Macedonia, as well as other duties <strong>and</strong> taxes the<br />

customs authorities are authorised to collect in accordance with the provisions regulating such duties <strong>and</strong><br />

taxes, when the Tariff code is used within the import declaration.<br />

- The calculated amount of duties <strong>and</strong> taxes in risk shall be registered in CDPS.<br />

- CDPS with Guarantee management system sub-application shall be able to carry out:<br />

o on line management of comprehensive guarantees, especially to check:<br />

→ existence of comprehensive guarantee, i.e. the comprehensive guarantee was registered by the<br />

customs office of guarantee <strong>and</strong> it is still valid,<br />

→ if the authorisation for comprehensive guarantee was granted to the declarant,<br />

→ validity of access code (PIN), issued to the declarant for proving his right to use this guarantee,<br />

→ if the actual amount of reference amount does not exceed the reference amount of<br />

comprehensive guarantee,<br />

o on line management of individual guarantee, especially to check:<br />

→ existence of individual guarantee, i.e. the individual guarantee was accepted <strong>and</strong> registered by<br />

the customs office of guarantee <strong>and</strong> it is still valid (was not used),<br />

→ if the individual guarantee was registered for this declarant,<br />

→ scope of validity of individual guarantee, i.e. it is valid for declared goods (the individual<br />

guarantee was accepted <strong>and</strong> registered by the customs office of guarantee for certain goods),<br />

→ validity of access code (PIN), issued to the declarant for proving his right to use this individual<br />

guarantee.<br />

- CDPS shall be able to communicate via national domain with the Guarantee management system subapplication.<br />

3.4.3.2 Register of guarantee usage<br />

- Where the checks described above in the part 3.4.2 of this document successfully passed, the Guarantee<br />

management system sub-application shall:<br />

o register the use of guarantee together with the MRN issued at the customs office of import <strong>and</strong> with<br />

the amount of calculated/assessed duties <strong>and</strong> taxes,<br />

o notify electronically the customs office of import that the usage of guarantee is accepted <strong>and</strong><br />

registered.<br />

- Where the checks described above in the part 3.4.2 of this document did not successfully pass, the<br />

Guarantee management system sub-application shall notify electronically the customs office of import<br />

Page 77/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

that the usage of guarantee was not accepted. The customs office of import having this information shall<br />

not release the declared goods for the declared import regime.<br />

3.4.3.3 Writing off the guarantee<br />

- Where for the goods released for free circulation customs regime with one declaration:<br />

o the amount of customs debt has been paid, in case that end-use has not been used, or<br />

o the amount of customs debt has been paid <strong>and</strong> the conditions <strong>and</strong> time limit given for end-use have<br />

been fulfilled,<br />

the customs office of import based on this information shall notify that to the customs office of guarantee<br />

with the request for release of a used guarantee.<br />

- Where for the goods released for a customs regime with economic impact with one declaration:<br />

o this regime has been ended properly, <strong>and</strong><br />

o another customs approved treatment or use has been assigned to these goods,<br />

the customs office of import based on this information shall notify that to the customs office of guarantee<br />

with the request for release of a used guarantee.<br />

3.4.4 Release of goods for import regime of free circulation<br />

- The decision on release of goods for import regime of free circulation can be issued by the customs<br />

office of import using the st<strong>and</strong>ard procedure or simplified procedure of local clearance or simplified<br />

procedure of simplified or incomplete customs declaration. The usage of simplified procedure local<br />

clearance is described bellow – see part 3.4.4.2 of this document. The usage of simplified procedure of<br />

simplified or incomplete customs declaration is described bellow – see parts 3.4.4.3 <strong>and</strong> 3.4.4.4 of this<br />

document.<br />

3.4.4.1 Use of st<strong>and</strong>ard procedure<br />

- In case that the import declaration for release of goods for free circulation was lodged electronically <strong>and</strong><br />

the import declaration was registered with MRN, this MRN is after that used for identification of that<br />

import declaration during all next communication with a declarant.<br />

- The customs officer at the customs office of import shall process the accepted import declaration for<br />

release of goods for free circulation <strong>and</strong> the calculate/assess the amount of customs debt with the CDPS<br />

based on the data of import declaration for release of goods for free circulation <strong>and</strong> with the data from<br />

Tarim (TARIC) sub-application, according to the Article 233 of <strong>Customs</strong> Law 1 .<br />

- Where the customs officer at the customs office of import has any doubts concerning any data from<br />

accepted import declaration or any document accompanying the import declaration, he shall:<br />

o mark these doubts,<br />

o calculate <strong>and</strong> log an additional security (a guarantee) sufficient to cover the difference between the<br />

amount according to the particulars in the declaration <strong>and</strong> the amount which may finally be payable<br />

on the goods, or to calculate the amount of duties to which the goods may ultimately be liable<br />

instead of lodging this security,<br />

o set a time limit for solving these doubts. The CDPS shall monitor this time limit <strong>and</strong> inform the<br />

customs officer on expiration of this time limit.<br />

- This security (a guarantee) shall be registered in the Guarantee management system sub-application.<br />

- According to the Article 84 para. 1 of <strong>Customs</strong> Law 1 , where acceptance of a customs declaration for free<br />

circulation customs regime gives rise to a customs debt, the goods covered by this customs declaration<br />

shall not be released unless the customs debt has been paid or secured.<br />

Page 78/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- In order to release the goods for free circulation, commercial policy measures shall apply, the other<br />

formalities laid down in respect of the importation of goods shall be completed <strong>and</strong> any duties legally<br />

due under customs or other regulations shall be charged, according to the Article 91 of <strong>Customs</strong> Law 1 .<br />

- Where the declarant already paid (in advance payment) the amount of customs debt or he provided the<br />

guarantee for security of assessed amount of customs debt the customs officer shall release the declared<br />

goods for free circulation with the decision issued:<br />

o electronically <strong>and</strong> it is electronically sent to the declarant with a message, in case of lodging the<br />

electronic declaration,<br />

o in the form of Single Administrative Document (SAD) <strong>and</strong> it is given to the declarant, or<br />

o in the form of receipt, which shall correspond to the model given in Annex 23 of <strong>Customs</strong> Law<br />

implementing Regulation, 2 <strong>and</strong> it is given to the declarant.<br />

- The calculated/assessed amount of customs debt shall be registered in Accounting management subapplication,<br />

this means it shall be entered in the customs accounts, according to the Article 234 para. 1 of<br />

<strong>Customs</strong> Law 1 .<br />

- In case that the decision on release of goods for free circulation issued electronically, the authentication<br />

of this decision shall be with an e-signature of customs administration, according to the Article 109 para.<br />

2 of the <strong>Customs</strong> Law implementing Regulation 2 <strong>and</strong> the time of delivery of this decision shall be the<br />

time of delivery of message, automatically sent by the declarant’s system to the CDPS as a confirmation<br />

of delivery of this decision. This time shall be registered in Accounting management sub-application.<br />

- In case that the decision on release of goods for free circulation regime issued in the form of Single<br />

Administrative Document (SAD) or the receipt, the time of delivery of this decision shall be the time of<br />

release of the goods by the customs authority, according to the Article 235 para. 2 of <strong>Customs</strong> Law 1 , <strong>and</strong><br />

it shall be registered in Accounting management sub-application.<br />

- The decision on release of goods for free circulation regime issued in the paper form (i.e. Single<br />

Administrative Document (SAD) or the receipt) shall be authenticated by the customs officer from<br />

customs office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

- The procedure of release of goods for free circulation regime shall be finished when the amount of<br />

customs debt is paid. This payment shall be registered in CDPS <strong>and</strong> in the Accounting management subapplication.<br />

- According to the Article 208 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 , where goods are<br />

released for free circulation at a reduced or zero rate of duty on account of their end-use <strong>and</strong> the<br />

provisions in force require that the goods remain under customs supervision in accordance with Article<br />

95 of the <strong>Customs</strong> Law 1 , a written authorisation for the purposes of end-use customs supervision shall be<br />

necessary. This authorisation shall be registered in the Authorisation sub-application <strong>and</strong> it shall contain<br />

the description of conditions for end-use <strong>and</strong> the time limit for customs supervision.<br />

- Where the import declaration for free circulation customs regime contains the request/notification for<br />

application of end-use treatment, the registration number of this authorisation shall be a part of this<br />

import declaration.<br />

- In case that the import declaration for free circulation customs regime was lodged electronically, the<br />

decision that the goods shall not be released for this regime is issued by the customs office of import<br />

electronically <strong>and</strong> it is electronically sent to the declarant. Authentication of this decision shall be with<br />

an e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- In case that the import declaration for free circulation customs regime was lodged the paper form (i.e.<br />

Single Administrative Document (SAD) or the receipt), the decision that the goods shall not be released<br />

for this regime is issued by the customs office of import in the paper form prescribed by MCA <strong>and</strong> it<br />

shall be sent to the declarant. Authentication of this decision shall be done by the customs officer from<br />

customs office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

Page 79/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.4.4.2 Use of simplified procedure of local clearance<br />

- Simplified procedure of local clearance for release of goods for free circulation customs regime cannot<br />

be used with paper or oral declaration for this regime according to the Articles 179 - 183 of <strong>Customs</strong><br />

Law Implementing Regulation 2 . The rules <strong>and</strong> processes described in part 3.4.4.1 of this document are<br />

used within the usage of simplified procedure of local clearance in for release of goods for free<br />

circulation customs regime.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of local clearance<br />

for release of goods for free circulation customs regime through the data from modules of Authorisation<br />

sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised place, where goods are available, via code of this place (given in the authorisation),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised country of final consignor (the list of prohibited countries is given in the authorisation),<br />

o number of authorised guarantee (GRN) of comprehensive guarantee registered in the Guarantee<br />

management sub-application.<br />

- When the simplified procedure of local clearance for release of goods for free circulation customs<br />

regime is used the documents to accompany the declaration for free circulation customs regime shall be<br />

available for customs at the declarant’s premise. This condition is set up in the authorisation of<br />

simplified procedure of local clearance issued by Macedonian customs authorities.<br />

- When all the above automated checks passed successfully, the electronic declaration for release of goods<br />

for free circulation customs regime shall be accepted with MRN (Movement Reference Number) by the<br />

customs office of import. This MRN shall be electronically notified to a declarant. Authentication of this<br />

notification shall be with an e-signature of customs administration, according to the Article 109 para. 2<br />

of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- It is assumed that at the time of lodging of electronic declaration for release of goods for free circulation<br />

customs regime, the goods are ready for placing for this regime at the authorised place given in this<br />

declaration. This place is registered <strong>and</strong> authorised within the authorisation of simplified procedure of<br />

local clearance for release of goods for free circulation customs regime (in the Authorisation subapplication).<br />

- The customs authorities (customs office of import within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of local clearance for release<br />

of goods for free circulation customs regime within the time limit (timer for automatic release of goods)<br />

set up in the within the authorisation of simplified procedure of local clearance (in the Authorisation subapplication).<br />

- When the decision on control of goods which have been declared within the simplified procedure of<br />

local clearance for release of goods for free circulation customs regime is taken, the notification of this<br />

control shall be electronically sent to the declarant or his representative (to a person who lodge this<br />

declaration). Authentication of this notification of control shall be with the e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . This<br />

notification shall be sent at the end of the time limit (timer for automatic release of goods) set up in the<br />

authorisation (in the Authorisation sub-application) to give a time to the customs authorities responsible<br />

for this control to be present at the authorised place, where the goods are available, before the<br />

notification is sent to the declarant or his representative (to a person who lodge the declaration for free<br />

circulation customs regime). At that time the timer for automatic release of goods shall be stopped.<br />

- When the timer for automatic release of goods expired <strong>and</strong> no decision on control of goods was taken,<br />

the goods are automatically released for free circulation customs regime. The decision on release of<br />

goods for free circulation customs regime shall be electronically sent to the declarant or his<br />

representative at that moment. Authentication of this decision shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

Page 80/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Based on the decision on release of goods for free circulation customs regime which was electronically<br />

sent to the declarant or his representative by the customs office of import, the declarant shall send back<br />

the electronic confirmation of delivery of this decision. This time shall be registered in Accounting<br />

management sub-application. The time of delivery of this decision shall be the time of delivery of<br />

confirmation.<br />

- The import operation with the release of goods for free circulation customs regime shall finish when the<br />

calculated/assessed amount of customs debt is paid, except the case with end-use treatment.<br />

- No supplementary declaration for release of goods for free circulation customs regime shall be lodged by<br />

the declarant at the customs office of import.<br />

3.4.4.3 Use of simplified procedure of incomplete declaration<br />

- According to the Article 167 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 the simplified procedure<br />

of incomplete import declaration for release of goods for free circulation customs regime shall allow the<br />

customs authority to accept, only in a duly justified case, an import declaration for release of goods for<br />

free circulation customs regime which does not contain all the particulars required, or which is not<br />

accompanied by all documents necessary for this import regime.<br />

- The minimum data elements of incomplete import declaration for release of goods for free circulation<br />

customs regime shall be introduced <strong>and</strong> it shall be in line with the Articles 170 – 173 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The time limit for supplementary lodging of missing data or documents of incomplete import declaration<br />

for release of goods for free circulation customs regime shall be assigned by the customs office of<br />

import. St<strong>and</strong>ard time shall not be longer that 1 month, according to the Article 172 para. 1 of <strong>Customs</strong><br />

Law Implementing Regulation 2 . In dully justified cases <strong>and</strong> on the request of declarant the customs<br />

office of export can prolong this time period. That period may not exceed 4 months from the date of<br />

acceptance of the declaration, according to the Article 172 para. 1 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The incomplete import declaration for release of goods for free circulation customs regime can be lodged<br />

in:<br />

o electronic form, or<br />

o paper form of Single Administrative Document (SAD).<br />

- The rules <strong>and</strong> processes described in parts 3.4.4.1 <strong>and</strong> 3.4.4.2 of this document are also used within the<br />

usage of simplified procedure of incomplete import declaration for release of goods for free circulation<br />

customs regime.<br />

- The acceptance of incomplete import declaration for release of goods for free circulation customs regime<br />

<strong>and</strong> release of goods for free circulation customs regime shall be done by the customs office of import,<br />

as well as the acceptance of supplementary lodging of missing data or documents of incomplete import<br />

declaration for release of goods for free circulation customs regime.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of incomplete<br />

import declaration for release of goods for free circulation customs regime through the data from<br />

modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for lodging the supplementary documents or data at the customs office of import<br />

(given in the authorisation),<br />

o authorised country of final consignor (the list of prohibited countries is given in the authorisation),<br />

o number of authorised guarantee (GRN) of comprehensive or individual guarantee registered in the<br />

Guarantee management sub-application.<br />

Page 81/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- When the simplified procedure of incomplete import declaration for release of goods for free circulation<br />

customs regime is used the documents to accompany the import declaration for release of goods for free<br />

circulation customs regime shall be lodged together with the incomplete import declaration for release of<br />

goods for free circulation customs regime at the customs office of import.<br />

- A declarant shall present the declared goods at the customs office of import.<br />

- When all the above automated checks passed successfully, the incomplete import declaration for release<br />

of goods for free circulation customs regime shall be accepted with MRN (Movement Reference<br />

Number) by the customs office of import. This MRN shall be notified to a declarant. Authentication of<br />

electronic notification shall be with an e-signature of customs administration, according to the Article<br />

109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- The customs authorities (customs office of import within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of incomplete import<br />

declaration for release of goods for free circulation customs regime.<br />

- The decision on release of goods for free circulation customs regime using the simplified procedure of<br />

incomplete import declaration for release of goods for free circulation customs regime is taken by a<br />

customs officer at the customs office of import.<br />

- When the incomplete import declaration for release of goods for free circulation customs regime was<br />

lodged electronically by the declarant, the decision on release of goods for free circulation customs<br />

regime using the simplified procedure of incomplete import declaration is also sent from the customs<br />

office of import to the declarant in the form electronic message. Authentication of this decision shall be<br />

with an e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

implementing Regulation 2 .<br />

- Based on the decision on release of goods for free circulation customs regime which was electronically<br />

sent to the declarant or his representative by the customs office of import, the declarant shall send back<br />

the electronic confirmation of delivery of this decision. This time shall be registered in Accounting<br />

management sub-application. The time of delivery of this decision shall be the time of delivery of<br />

confirmation.<br />

- When the incomplete import declaration for release of goods for free circulation customs regime was<br />

lodged by the declarant in the paper form of Single Administrative Document (SAD), the decision on<br />

release of goods for free circulation customs regime using the simplified procedure of incomplete import<br />

declaration shall be also issued in the paper form (i.e. Single Administrative Document (SAD)) <strong>and</strong> it<br />

shall be authenticated by the customs officer from customs office of import with his h<strong>and</strong> written<br />

signature <strong>and</strong> his personal customs stamp. The time of delivery of this decision shall be the time of<br />

release of the goods by the customs authority, according to the Article 235 para. 2 of <strong>Customs</strong> Law 1 , <strong>and</strong><br />

it shall be registered in Accounting management sub-application.<br />

- The customs authorities' acceptance of an incomplete declaration shall not prevent or delay the release of<br />

the goods thus declared, unless other grounds exist for so doing. Without prejudice to the provisions of<br />

Article 162 of <strong>Customs</strong> Law Implementing Regulation 2 , release shall take place in accordance with the<br />

conditions laid down in the Article 173 paragraphs 2 to 5 of <strong>Customs</strong> Law Implementing Regulation 2<br />

<strong>and</strong> the sum payable (the amount of customs debt) shall be immediately entered by customs authorities<br />

in their accounts.<br />

- The import operation with the release of goods for free circulation customs regime shall finish when the<br />

missing information or documents are provided or calculated/assessed amount of customs debt, to which<br />

the goods in question are subject the amount of the security provided in accordance with the provisions<br />

of the Article 257, is paid.<br />

- No supplementary declaration for release of goods for free circulation customs regime shall be lodged by<br />

the declarant at the customs office of import.<br />

3.4.4.4 Use of simplified procedure of simplified declaration<br />

Page 82/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- According to the Article 167 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 the simplified procedure<br />

of simplified import declaration shall allow the customs authority to accept, only in a duly justified case,<br />

an simplified import declaration for release of goods for free circulation customs regime with subsequent<br />

presentation of a supplementary declaration.<br />

- In case of incomplete declaration on a Single Administrative Document (SAD), the minimum data<br />

elements of simplified export declaration shall be introduced, according to the Article 176 para. 2 first<br />

indent of <strong>Customs</strong> Law Implementing Regulation 2 <strong>and</strong> it shall be in line with the Article 170 of <strong>Customs</strong><br />

Law Implementing Regulation 2 .<br />

- According to the Article 178 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 the time limit for<br />

lodging of supplementary import declaration for release of goods for free circulation customs regime<br />

shall be assigned by the customs office of import. The maximum time shall not be longer that 1 month.<br />

- The simplified import declaration for release of goods for free circulation customs regime can be lodged<br />

in:<br />

o paper form of a commercial or administrative document, accompanied by request for the goods to be<br />

placed under the free circulation customs regime, or<br />

o paper form of incomplete SAD document, according to the Article 176 para. 2 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The rules <strong>and</strong> processes described in parts 3.4.4.1 <strong>and</strong> 3.4.4.2 of this document are also used within the<br />

usage of simplified procedure of simplified import declaration for release of goods for free circulation<br />

customs regime.<br />

- The acceptance of simplified import declaration <strong>and</strong> release of goods for release of goods for free<br />

circulation customs regime shall be done by the customs office of import, as well as the acceptance of<br />

supplementary import declaration.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of simplified import<br />

declaration for release of goods for free circulation customs regime through the data from modules of<br />

Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for lodging the supplementary import declaration for release of goods for free<br />

circulation customs regime at the customs office of import (given in the authorisation),<br />

o authorised country of final consignor (the list of prohibited countries is given in the authorisation),<br />

o number of authorised guarantee (GRN) of comprehensive guarantee registered in the Guarantee<br />

management sub-application.<br />

- When the simplified procedure of simplified import declaration is used the documents to accompany the<br />

import declaration for release of goods for free circulation customs regime shall be lodged together with<br />

the simplified import declaration at the customs office of import.<br />

- A declarant shall present the declared goods at the customs office of import.<br />

- When all the above automated checks passed successfully, the simplified import declaration for release<br />

of goods for free circulation customs regime shall be accepted with MRN (Movement Reference<br />

Number) by the customs office of import. This MRN of simplified import declaration shall be notified to<br />

a declarant.<br />

- The customs authorities (customs office of import within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of simplified import<br />

declaration for release of goods for free circulation customs regime.<br />

- The decision on release of goods for free circulation customs regime using the simplified procedure of<br />

simplified import declaration for release of goods for free circulation customs regime is taken by a<br />

customs officer at the customs office of import.<br />

Page 83/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Due to the fact that the simplified import declaration for release of goods for free circulation customs<br />

regime was lodged by the declarant in the paper form, the initial decision on release of goods for free<br />

circulation customs regime using the simplified procedure of simplified import declaration shall be<br />

issued in the form of simplified import declaration <strong>and</strong> it shall be authenticated by the customs officer<br />

from customs office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp. The time<br />

of delivery of this decision shall be the time of release of the goods by the customs authority, according<br />

to the Article 235 para. 2 of <strong>Customs</strong> Law 1 , <strong>and</strong> it shall be registered in CDPS.<br />

- The subsequently presented supplementary declaration, depending on the case, may have a general,<br />

periodic or recapitulative nature.<br />

- The supplementary declaration lodged within the use of simplified declaration for release of goods for<br />

free circulation customs regime shall be lodged by the declarant in the form of:<br />

o electronic message (i.e. the electronic supplementary declaration), or<br />

o Single Administrative Document (SAD).<br />

- The decision on final release of the goods for free circulation issued in the form of supplementary<br />

declaration shall be registered with new MRN (Movement Reference Number) by the customs office of<br />

import. This MRN shall be notified to a declarant.<br />

- The decision on final release of goods for free circulation customs regime shall be issued by the customs<br />

office of import:<br />

o electronically <strong>and</strong> it is electronically sent to the declarant with a message, in case of lodging the<br />

electronic supplementary declaration,<br />

o in the form of Single Administrative Document (SAD), in case of paper-based form, <strong>and</strong> it is given<br />

to the declarant.<br />

- The finally calculated amount of customs debt shall be registered in Accounting management subapplication,<br />

this means it shall be entered in the customs accounts, according to the Article 234 para. 1 of<br />

<strong>Customs</strong> Law 1 .<br />

- In case that the decision on final release of goods for free circulation issued electronically, the<br />

authentication of this decision shall be with the e-signature of customs administration, according to the<br />

Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation, 2 <strong>and</strong> the time of delivery of this<br />

decision shall be the time of delivery of message, automatically sent by the declarant’s system to the<br />

CDPS as a confirmation of delivery of this decision. This time shall be registered in Accounting<br />

management sub-application.<br />

- In case that the decision on final release of goods for free circulation regime issued in the form of Single<br />

Administrative Document (SAD), the time of delivery of this decision shall be the time of release of the<br />

goods by the customs authority, according to the Article 235 para. 2 of <strong>Customs</strong> Law 1 , <strong>and</strong> it shall be<br />

registered in Accounting management sub-application.<br />

- According to the Article 178 para. 2 of <strong>Customs</strong> Law implementing Regulation 2 , the customs authority<br />

may decide not to submit the supplementary declaration when the simplified declaration concerns goods<br />

the value of which does not exceed 800 euros in corresponding denar value <strong>and</strong> the simplified<br />

declaration already contains all the data needed for release into free circulation.<br />

- The decision on final release of goods for free circulation regime issued in the form of Single<br />

Administrative Document (SAD) shall be authenticated by the customs officer from customs office of<br />

import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

- The procedure of release of goods for free circulation regime shall be finished when the amount of<br />

customs debt is paid. This payment shall be registered in CDPS <strong>and</strong> in the Accounting management subapplication.<br />

3.4.4.5 Cancellation of regime<br />

Page 84/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The cancellation of free circulation customs regime (i.e. the decision on release of goods for free<br />

circulation customs regime) shall be initiated either by a declarant or by the customs office of import<br />

(annulment/revocation of import declaration).<br />

- The cancellation of free circulation customs regime by a declarant shall be initiated in:<br />

o electronic form, i.e. by an electronic message sent by a declarant to the customs office of import,<br />

o paper form lodged by a declarant at the customs office of import.<br />

- The cancellation of free circulation customs regime initiated by a declarant in electronic form shall be<br />

confirmed by the customs office of import with an electronic message. Authentication of this decision<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

- The cancellation of free circulation customs regime initiated by a declarant in written form shall be<br />

confirmed by the customs office of import with the decision issued in written form.<br />

3.4.5 Release of goods for import regimes with economic impact<br />

- According to the Article 312 para. 1 of <strong>Customs</strong> Law Implementing Regulation, 2 the application for<br />

authorisation of a import regime with economic impact shall be made in writing using the model set out<br />

in Annex 27 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- According to the Article 312 para.3 of <strong>Customs</strong> Law Implementing Regulation, 2 the application for<br />

authorisation of a import regime with economic impact may be made by making a customs declaration.<br />

- According to the Article 98 of <strong>Customs</strong> Law, 1 the use of any import regime with economic impact shall<br />

be conditional upon authorisation being issued by the customs authority. This authorisation shall be<br />

registered in the Authorisation sub-application in advance, except the authorisation for temporary import<br />

with total relief from customs duty.<br />

- The decision on release of goods for one of import regimes with economic impact can be issued by the<br />

customs office of import using the st<strong>and</strong>ard procedure or simplified procedure of local clearance or<br />

simplified procedure of simplified or incomplete customs declaration. The usage of simplified procedure<br />

local clearance is described bellow – see part 3.4.5.2 of this document. The usage of simplified<br />

procedure of simplified or incomplete customs declaration is described bellow – see parts 3.4.5.3 <strong>and</strong><br />

3.4.5.4 of this document.<br />

3.4.5.1 Use of st<strong>and</strong>ard procedure<br />

- In case that the import declaration for release of goods for one of import regimes with economic impact<br />

was lodged electronically <strong>and</strong> the import declaration was registered with MRN, this MRN is after that<br />

used for identification of that import declaration during all next communication with a declarant.<br />

- The customs officer at the customs office of import shall process the accepted import declaration for<br />

release of goods for one of import regimes with economic impact with the CDPS based on the data of<br />

this import declaration <strong>and</strong> with the data from Tarim (TARIC) sub-application, according to the Article<br />

233 of <strong>Customs</strong> Law 1 .<br />

- Within the processing of this import declaration the customs officer at the customs office of import shall<br />

set up:<br />

o the amount of security, witch has to be guaranteed with the data from Tarim (TARIC) subapplication<br />

(this security (a guarantee) shall be registered in the Guarantee management system subapplication),<br />

o the time limit for the discharge of import regimes with economic impact, except the release of goods<br />

for customs warehousing regime, but in certain cases the time limit for the discharge of customs<br />

warehousing regime may be also set up. The CDPS shall monitor this time limit <strong>and</strong> inform the<br />

customs officer on expiration of this time limit.<br />

Page 85/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Where the customs officer at the customs office of import has any doubts concerning any data from<br />

accepted import declaration or any document accompanying the import declaration, he shall:<br />

o mark these doubts,<br />

o calculate <strong>and</strong> log an additional security (a guarantee) sufficient to cover the difference between the<br />

amount according to the particulars in the declaration <strong>and</strong> the amount which may finally be payable<br />

on the goods,<br />

o set a time limit for solving these doubts. The CDPS shall monitor this time limit <strong>and</strong> inform the<br />

customs officer on expiration of this time limit.<br />

- In order to release the goods for inward processing customs regime - drawback system, the commercial<br />

policy measures shall apply, the other formalities laid down in respect of the importation of goods shall<br />

be completed <strong>and</strong> any duties legally due under customs or other regulations shall be charged, according<br />

to the Article 139 of <strong>Customs</strong> Law 1 .<br />

- The assessed/calculated amount of customs debt in inward processing customs regime - drawback<br />

system shall be registered in Accounting management sub-application, this means it shall be entered in<br />

the customs accounts, according to the Article 234 para. 1 of <strong>Customs</strong> Law 1 .<br />

- Where the declarant already paid (in advance payment) the amount of customs debt or he provided the<br />

guarantee for security of assessed amount of customs debt the customs officer shall release the declared<br />

goods for a import regime with economic impact with the decision issued:<br />

o electronically <strong>and</strong> it is electronically sent to the declarant with a message, in case of lodging the<br />

electronic declaration,<br />

o in the form of Single Administrative Document (SAD) <strong>and</strong> it is given to the declarant.<br />

- In case that the decision on release of goods for a import regime with economic impact issued<br />

electronically, the authentication of this decision shall be with an e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 <strong>and</strong> the time of<br />

delivery of this decision shall be the time of delivery of message, automatically sent by the declarant’s<br />

system to the CDPS as a confirmation of delivery of this decision. This time shall be registered in CDPS.<br />

- In case that the decision on release of goods for a import regime with economic impact issued in the<br />

form of Single Administrative Document (SAD) or the receipt, the time of delivery of this decision shall<br />

be the time of release of the goods by the customs authority, according to the Article 235 para. 2 of<br />

<strong>Customs</strong> Law 1 , <strong>and</strong> it shall be registered in CDPS.<br />

- The decision on release of goods for a import regime with economic impact issued in the paper form (i.e.<br />

Single Administrative Document (SAD)) shall be authenticated by the customs officer from customs<br />

office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

- In case that the import declaration for a import regime with economic impact was lodged electronically,<br />

the decision that the goods shall not be released for this regime is issued by the customs office of import<br />

electronically <strong>and</strong> it is electronically sent to the declarant. Authentication of this decision shall be with<br />

an e-signature of customs administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- In case that the import declaration for a import regime with economic impact was lodged the paper form<br />

(i.e. Single Administrative Document (SAD)), the decision that the goods shall not be released for this<br />

regime is issued by the customs office of import in the paper form prescribed by MCA <strong>and</strong> it shall be<br />

sent to the declarant. Authentication of this decision shall be done by the customs officer from customs<br />

office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

3.4.5.2 Control of goods<br />

- According to the Article 392 para. 2 of <strong>Customs</strong> Law Implementing Regulation, 2 the customs authority<br />

may require records to be kept by holder of authorisation for a import regime with economic impact to<br />

facilitate their control of the arrangements of that customs regime. The records shall contain the<br />

information specified my MCA.<br />

Page 86/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The CDPS shall allow at least to the customs officer from supervising customs office <strong>and</strong> from<br />

discharging customs office, which are specified in the authorisation <strong>and</strong> they are registered in the<br />

Authorisation sub-application, to:<br />

o see the details of declaration released within this authorisation for a import regime with economic<br />

impact (the details of this authorisation shall be available from the Authorisation sub-application),<br />

o carry out the supervision of these arrangements of that customs regime, including the usage of a<br />

control protocol,<br />

o use a rate of yield for purposes of control or discharging of the inward processing regime, according<br />

to the Article 328 para. 1 of <strong>Customs</strong> Law Implementing Regulation, 2<br />

o control of value of the import goods in inward processing regime per holder of authorisation <strong>and</strong> per<br />

calendar year that each ten-digit <strong>Customs</strong> Tariff code listed in the authorisation does not exceed<br />

10000 EUR in corresponding denar value, according to the Article 348 letter b) of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

3.4.5.3 Use of simplified procedure of local clearance<br />

- Simplified procedure of local clearance for release of goods for an import regime with economic impact<br />

cannot be used with paper or oral declaration for this regime according to the Article 192 of <strong>Customs</strong><br />

Law Implementing Regulation 2 . The rules <strong>and</strong> processes described in parts 3.4.5.1 <strong>and</strong> 3.4.5.2 of this<br />

document are used within the usage of simplified procedure of local clearance in for release of goods for<br />

an import regime with economic impact.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of local clearance<br />

for release of goods for an import regime with economic impact through the data from modules of<br />

Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised place, where goods are available, via code of this place (given in the authorisation),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised country of final consignor (the list of prohibited countries is given in the authorisation),<br />

o number of authorised guarantee (GRN) of comprehensive guarantee registered in the Guarantee<br />

management sub-application.<br />

- When the simplified procedure of local clearance for release of goods for an import regime with<br />

economic impact is used the documents to accompany the declaration for a import regime with economic<br />

impact shall be available for customs at the declarant’s premise. This condition is set up in the<br />

authorisation of simplified procedure of local clearance issued by Macedonian customs authorities.<br />

- When all the above automated checks passed successfully, the electronic declaration for release of goods<br />

for an import regime with economic impact shall be accepted with MRN (Movement Reference Number)<br />

by the customs office of import. This MRN shall be electronically notified to a declarant. Authentication<br />

of this notification shall be with an e-signature of customs administration, according to the Article 109<br />

para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- It is assumed that at the time of lodging of electronic declaration for release of goods for an import<br />

regime with economic impact, the goods are ready for placing for this regime at the authorised place<br />

given in this declaration. This place is registered <strong>and</strong> authorised within the authorisation of simplified<br />

procedure of local clearance for release of goods for an import regime with economic impact (in the<br />

Authorisation sub-application).<br />

- The customs authorities (customs office of import within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of local clearance for release<br />

of goods for an import regime with economic impact within the time limit (timer for automatic release of<br />

goods) set up in the within the authorisation of simplified procedure of local clearance (in the<br />

Authorisation sub-application).<br />

Page 87/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- When the decision on control of goods which have been declared within the simplified procedure of<br />

local clearance for release of goods for an import regime with economic impact is taken, the notification<br />

of this control shall be electronically sent to the declarant or his representative (to a person who lodge<br />

this declaration). Authentication of this notification of control shall be with the e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 . This<br />

notification shall be sent at the end of the time limit (timer for automatic release of goods) set up in the<br />

authorisation (in the Authorisation sub-application) to give a time to the customs authorities responsible<br />

for this control to be present at the authorised place, where the goods are available, before the<br />

notification is sent to the declarant or his representative (to a person who lodge the declaration for an<br />

import regime with economic impact). At that time the timer for automatic release of goods shall be<br />

stopped.<br />

- When the timer for automatic release of goods expired <strong>and</strong> no decision on control of goods was taken,<br />

the goods are automatically released for an import regime with economic impact. The decision on release<br />

of goods for an import regime with economic impact shall be electronically sent to the declarant or his<br />

representative at that moment. Authentication of this decision shall be with an e-signature of customs<br />

administration, according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- Based on the decision on release of goods for an import regime with economic impact which was<br />

electronically sent to the declarant or his representative by the customs office of import, the declarant<br />

shall send back the electronic confirmation of delivery of this decision. This time shall be registered in<br />

CDPS. The time of delivery of this decision shall be the time of delivery of confirmation.<br />

- The import operation with the release of goods for an import regime with economic impact shall finish<br />

when the an import regime with economic impact is discharged – see part 3.4.5.10 of this document.<br />

- No supplementary declaration for release of goods for an import regime with economic impact shall be<br />

lodged by the declarant at the customs office of import.<br />

3.4.5.4 Use of simplified procedure of incomplete declaration<br />

- According to the Article 167 para. 1 of <strong>Customs</strong> Law Implementing Regulation 2 the simplified procedure<br />

of incomplete import declaration for release of goods for an import regime with economic impact shall<br />

allow the customs authority to accept, only in a duly justified case, an import declaration for release of<br />

goods for an import regime with economic impact which does not contain all the particulars required, or<br />

which is not accompanied by all documents necessary for this import regime.<br />

- The minimum data elements of incomplete import declaration for release of goods for an import regime<br />

with economic impact shall be introduced <strong>and</strong> it shall be in line with the Articles 184 <strong>and</strong> 191 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The time limit for supplementary lodging of missing data or documents of incomplete import declaration<br />

for release of goods for an import regime with economic impact shall be assigned by the customs office<br />

of import. St<strong>and</strong>ard time shall not be longer that 1 month, according to the Article 172 para. 1 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 . In dully justified cases <strong>and</strong> on the request of declarant the<br />

customs office of export can prolong this time period. That period may not exceed 4 months from the<br />

date of acceptance of the declaration, according to the Article 172 para. 1 (Articles 184 <strong>and</strong> 191) of<br />

<strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The incomplete import declaration for release of goods for an import regime with economic impact can<br />

be lodged in:<br />

o electronic form, or<br />

o paper form of Single Administrative Document (SAD).<br />

- The rules <strong>and</strong> processes described in parts 3.4.5.1 <strong>and</strong> 3.4.5.2 of this document are also used within the<br />

usage of simplified procedure of incomplete import declaration for release of goods for an import regime<br />

with economic impact.<br />

Page 88/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The acceptance of incomplete import declaration for release of goods for an import regime with<br />

economic impact <strong>and</strong> release of goods for an import regime with economic impact shall be done by the<br />

customs office of import, as well as the acceptance of supplementary lodging of missing data or<br />

documents of incomplete import declaration for release of goods for an import regime with economic<br />

impact.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of incomplete<br />

import declaration for release of goods for an import regime with economic impact through the data from<br />

modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is a<br />

VAT number),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for lodging the supplementary documents or data at the customs office of import<br />

(given in the authorisation),<br />

o authorised country of final consignor (the list of prohibited countries is given in the authorisation),<br />

o number of authorised guarantee (GRN) of comprehensive registered in the Guarantee management<br />

sub-application.<br />

- When the simplified procedure of incomplete import declaration for release of goods for an import<br />

regime with economic impact is used, the documents to accompany the import declaration for release of<br />

goods for an import regime with economic impact shall be lodged together with the incomplete import<br />

declaration for release of goods for an import regime with economic impact at the customs office of<br />

import.<br />

- A declarant shall present the declared goods at the customs office of import.<br />

- When all the above automated checks passed successfully, the incomplete import declaration for release<br />

of goods for an import regime with economic impact shall be accepted with MRN (Movement Reference<br />

Number) by the customs office of import. This MRN shall be notified to a declarant. Authentication of<br />

electronic notification shall be with an e-signature of customs administration, according to the Article<br />

109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- The customs authorities (customs office of import within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of incomplete import<br />

declaration for release of goods for free circulation customs regime.<br />

- The decision on release of goods for an import regime with economic impact customs regime using the<br />

simplified procedure of incomplete import declaration for release of goods for an import regime with<br />

economic impact is taken by a customs officer at the customs office of import.<br />

- When the incomplete import declaration for release of goods for an import regime with economic impact<br />

was lodged electronically by the declarant, the decision on release of goods for an import regime with<br />

economic impact using the simplified procedure of incomplete import declaration is also sent from the<br />

customs office of import to the declarant in the form electronic message. Authentication of this decision<br />

shall be with an e-signature of customs administration, according to the Article 109 para. 2 of the<br />

<strong>Customs</strong> Law implementing Regulation 2 .<br />

- Based on the decision on release of goods for an import regime with economic impact, which was<br />

electronically sent to the declarant or his representative by the customs office of import, the declarant<br />

shall send back the electronic confirmation of delivery of this decision. This time shall be registered in<br />

CDPS. The time of delivery of this decision shall be the time of delivery of confirmation.<br />

- When the incomplete import declaration for release of goods for an import regime with economic impact<br />

was lodged by the declarant in the paper form of Single Administrative Document (SAD), the decision<br />

on release of goods for an import regime with economic impact using the simplified procedure of<br />

incomplete import declaration shall be also issued in the paper form (i.e. Single Administrative<br />

Document (SAD)) <strong>and</strong> it shall be authenticated by the customs officer from customs office of import<br />

with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp. The time of delivery of this decision<br />

Page 89/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

shall be the time of release of the goods by the customs authority, according to the Article 235 para. 2 of<br />

<strong>Customs</strong> Law 1 , <strong>and</strong> it shall be registered in CDPS.<br />

- The import operation with the release of goods for an import regime with economic impact shall finish<br />

when the missing information or documents are provided or calculated/assessed amount of customs debt,<br />

to which the goods in question are subject the amount of the security provided in accordance with the<br />

provisions of the Article 257, is paid.<br />

- No supplementary declaration for release of goods for an import regime with economic impact shall be<br />

lodged by the declarant at the customs office of import.<br />

3.4.5.5 Use of simplified procedure of simplified declaration<br />

- According to the Article 167 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 the simplified procedure<br />

of simplified import declaration shall allow the customs authority to accept, only in a duly justified case,<br />

an simplified import declaration for release of goods for an import regime with economic impact with<br />

subsequent presentation of a supplementary declaration.<br />

- In case of incomplete declaration on a Single Administrative Document (SAD), the minimum data<br />

elements of simplified export declaration shall be introduced, according to the Article 192 of <strong>Customs</strong><br />

Law Implementing Regulation 2 <strong>and</strong> it shall be in line with the Article 185 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- According to the Article 192 (Article 178 para. 1) of <strong>Customs</strong> Law Implementing Regulation 2 the time<br />

limit for lodging of supplementary import declaration for release of goods for an import regime with<br />

economic impact (except the customs warehousing regime) shall be assigned by the customs office of<br />

import.<br />

- The simplified import declaration for release of goods for an import regime with economic impact can be<br />

lodged in:<br />

o paper form of a commercial or administrative document, accompanied by request for the goods to be<br />

placed under the free circulation customs regime, or<br />

o paper form of incomplete SAD document, according to the Articles 185 or 192 (Article 176 para. 2)<br />

of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The rules <strong>and</strong> processes described in parts 3.4.5.1 <strong>and</strong> 3.4.5.2 of this document are also used within the<br />

usage of simplified procedure of simplified import declaration for release of goods for an import regime<br />

with economic impact.<br />

- The acceptance of simplified import declaration <strong>and</strong> release of goods for release of goods for an import<br />

regime with economic impact shall be done by the customs office of import, as well as the acceptance of<br />

supplementary import declaration.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation of simplified procedure of simplified import<br />

declaration for release of goods for an import regime with economic impact through the data from<br />

modules of Authorisation sub-application shall cover especially:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is<br />

a VAT number),<br />

o authorised goods, via Tariff number (given in the authorisation),<br />

o authorised time for lodging the supplementary import declaration for release of goods for an<br />

import regime with economic impact at the customs office of import (given in the authorisation),<br />

o authorised country of final consignor (the list of prohibited countries is given in the authorisation),<br />

o number of authorised guarantee (GRN) of comprehensive guarantee registered in the Guarantee<br />

management sub-application.<br />

- When the simplified procedure of simplified import declaration is used the documents to accompany the<br />

import declaration for release of goods for an import regime with economic impact shall be lodged<br />

together with the simplified import declaration at the customs office of import.<br />

Page 90/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- A declarant shall present the declared goods at the customs office of import.<br />

- When all the above automated checks passed successfully, the simplified import declaration for release<br />

of goods for an import regime with economic impact shall be accepted with MRN (Movement Reference<br />

Number) by the customs office of import. This MRN of simplified import declaration shall be notified to<br />

a declarant.<br />

- The customs authorities (customs office of import within the working hours) shall take a decision on<br />

control of goods which have been declared within the simplified procedure of simplified import<br />

declaration for release of goods for an import regime with economic impact.<br />

- The decision on release of goods for free circulation customs regime using the simplified procedure of<br />

simplified import declaration for release of goods for an import regime with economic impact is taken by<br />

a customs officer at the customs office of import.<br />

- Due to the fact that the simplified import declaration for release of goods for an import regime with<br />

economic impact was lodged by the declarant in the paper form, the initial decision on release of goods<br />

for an import regime with economic impact using the simplified procedure of simplified import<br />

declaration shall be issued in the form of simplified import declaration <strong>and</strong> it shall be authenticated by<br />

the customs officer from customs office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal<br />

customs stamp. The time of delivery of this decision shall be the time of release of the goods by the<br />

customs authority, according to the Article 235 para. 2 of <strong>Customs</strong> Law 1 , <strong>and</strong> it shall be registered in<br />

CDPS.<br />

- The subsequently presented supplementary declaration, depending on the case, may have a general,<br />

periodic or recapitulative nature.<br />

- The supplementary declaration lodged within the use of simplified declaration for release of goods for an<br />

import regime with economic impact shall be lodged by the declarant in the form of:<br />

o electronic message (i.e. the electronic supplementary declaration), or<br />

o Single Administrative Document (SAD).<br />

- The decision on final release of the goods for an import regime with economic impact issued in the form<br />

of supplementary declaration shall be registered with new MRN (Movement Reference Number) by the<br />

customs office of import. This MRN shall be notified to a declarant.<br />

- The decision on final release of goods for an import regime with economic impact shall be issued by the<br />

customs office of import:<br />

o electronically <strong>and</strong> it is electronically sent to the declarant with a message, in case of lodging the<br />

electronic supplementary declaration,<br />

o in the form of Single Administrative Document (SAD), in case of paper-based form, <strong>and</strong> it is given<br />

to the declarant.<br />

- In case that the decision on final release of goods for an import regime with economic impact issued<br />

electronically, the authentication of this decision shall be with the e-signature of customs administration,<br />

according to the Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation, 2 <strong>and</strong> the time of<br />

delivery of this decision shall be the time of delivery of message, automatically sent by the declarant’s<br />

system to the CDPS as a confirmation of delivery of this decision. This time shall be registered in CDPS.<br />

- In case that the decision on final release of goods for an import regime with economic impact issued in<br />

the form of Single Administrative Document (SAD), the time of delivery of this decision shall be the<br />

time of release of the goods by the customs authority, according to the Article 235 para. 2 of <strong>Customs</strong><br />

Law 1 , <strong>and</strong> it shall be registered in CDPS.<br />

- According to the Article 192 (Article 178 para. 2) of <strong>Customs</strong> Law implementing Regulation 2 , the<br />

customs authority may decide not to submit the supplementary declaration when the simplified<br />

declaration concerns goods the value of which does not exceed 800 euros in corresponding denar value<br />

<strong>and</strong> the simplified declaration already contains all the data needed for release into an import regime with<br />

economic impact.<br />

Page 91/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The decision on final release of goods for an import regime with economic impact issued in the form of<br />

Single Administrative Document (SAD) shall be authenticated by the customs officer from customs<br />

office of import with his h<strong>and</strong> written signature <strong>and</strong> his personal customs stamp.<br />

3.4.5.6 Cancellation of an import regime with economic impact<br />

- The cancellation of an import regime with economic impact (i.e. the decision on release of goods for an<br />

import regime with economic impact) shall be initiated either by a declarant or by the customs office of<br />

import (annulment/revocation of import declaration).<br />

- The cancellation of an import regime with economic impact by a declarant shall be initiated in:<br />

o electronic form, i.e. by an electronic message sent by a declarant to the customs office of import,<br />

o paper form lodged by a declarant at the customs office of import.<br />

- The cancellation of an import regime with economic impact initiated by a declarant in electronic form<br />

shall be confirmed by the customs office of import with an electronic message. Authentication of this<br />

decision shall be with an e-signature of customs administration, according to the Article 109 para. 2 of<br />

the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- The cancellation of an import regime with economic impact initiated by a declarant in written form shall<br />

be confirmed by the customs office of import with the decision issued in written form.<br />

3.4.5.7 Discharge of import regime with economic impact<br />

- The discharge of a regime with economic impact means the action by which a new permitted customsapproved<br />

treatment or use including, as the case may be, in order to claim repayment of import duties<br />

after inward processing (drawback system), or in order to obtain total or partial relief from import duties<br />

upon release for free circulation after outward processing was assigned the goods or products released<br />

for an import regime with economic impact.<br />

- Automated check of validity <strong>and</strong> conditions of authorisation for an import regime with economic impact<br />

through the data from modules of Authorisation sub-application shall cover the discharge of an import<br />

regime with economic impact. A special attention shall be given to:<br />

o identification of a holder of authorisation, via the Trader Identification Number – TIN (usually it is a<br />

VAT number),<br />

o authorised goods (main <strong>and</strong> secondary compensating products or processed products), via Tariff<br />

number (given in the authorisation),<br />

o the particulars of the declarations entering the import goods under the the import regime with<br />

economic impact (arrangements),<br />

o quantity <strong>and</strong> value of main <strong>and</strong>/or secondary compensating products or processed products with the<br />

rate of yield, in case of inward processing, processing under the customs control or outward<br />

processing, according the Article 328 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o the rate of import duties to which the import goods are liable <strong>and</strong>, where applicable, their customs<br />

value,<br />

o amount <strong>and</strong> payment of compensatory interest, where a customs debt is incurred in respect of<br />

compensating products or import goods under inward processing or temporary importation,<br />

according to the Article 330 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o authorised time for discharge of an import regime with economic impact (given in the authorisation,<br />

if it is used),<br />

o authorised country of final consignee (the list of prohibited countries is given in the authorisation),<br />

o customs office of discharge,<br />

o formalities of transfer of responsibilities between different holders of authorisation (given in the<br />

authorisation, if it is used).<br />

Page 92/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- According to the Article 321 of <strong>Customs</strong> Law Implementing Regulation 2 the customs office other than<br />

the one specified in the authorisation for import regimes with economic impact (i.e. the customs office of<br />

discharge) can accept the customs declaration for discharge the import regime with economic impact<br />

under the condition that the supervising customs office shall be informed. The CDPS shall provide the<br />

supervising customs office with this information.<br />

- According to the Article 332 of <strong>Customs</strong> Law Implementing Regulation, 2 the customs supervising office<br />

using the data from the CDPS <strong>and</strong> Authorisation sub-application shall make out the bill of discharge. The<br />

bill of discharge shall be made in line with the model given in Annex 49 of <strong>Customs</strong> Law Implementing<br />

Regulation. 2<br />

3.5 Import control system<br />

- This module of CDPS shall be obligatory after the change of customs legislation or after the accession<br />

into EU for the acceptance <strong>and</strong> processing of entry summary declaration for goods entering into<br />

o Macedonian customs territory (based on the change of national customs legislation which shall be<br />

amended accordingly to the Community <strong>Customs</strong> Code 8 <strong>and</strong> <strong>Customs</strong> Code Implementing<br />

Provisions 9 ), or<br />

o customs territory of the Community (based on the accession of Macedonia into the EU).<br />

- Goods entering into the Macedonian customs territory or the customs territory of the Community, with<br />

the exception of goods carried on means of transport only passing through the territorial waters or the<br />

airspace of the customs territory without a stop within this territory, shall be covered either by an entry<br />

summary declaration or a customs declaration, where a customs declaration is lodged in advance.<br />

3.5.1 Trade <strong>Customs</strong> office of lodgement of END<br />

3.5.1.1 Electronic entry summary declaration (END)<br />

- Lodging of electronic entry summary declaration (IE315) is possible according to the Article of <strong>Customs</strong><br />

Law 1 , which shall be amended accordingly to the Community <strong>Customs</strong> Code 8 .<br />

- Electronic lodging of entry summary declaration (IE315) by a person who brings the goods, or who<br />

assumes responsibility for the carriage of the goods, into the Macedonian customs territory or the<br />

customs territory of the Community shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong><br />

Law Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a person who brings the goods, or who assumes responsibility for the<br />

carriage of the goods, into the Macedonian customs territory or the customs territory of the Community,<br />

shall be replaced by e-signature according to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

The e-signature(s) shall be registered together with the identification of that person in the module for<br />

authorisation of e-communication in the Authorisation sub-application.<br />

- The electronic entry summary declaration (IE315) shall be lodged at the customs office of lodgement or<br />

directly at the customs office of first entry within the specified time limit <strong>and</strong> before the goods are<br />

brought into the Macedonian customs territory or the customs territory of the Community.<br />

- Automated initial checks of electronic entry summary declaration shall cover:<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application,<br />

o filling in the data-elements or data-groups (boxes of entry summary),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of entry summary declaration<br />

(logical controls).<br />

Page 93/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.5.1.2 Paper-based entry summary declaration<br />

- The customs office of first entry may accept paper-based entry summary declarations in exceptional<br />

circumstances, provided that they apply the same level of risk management as that applied to entry<br />

summary declarations made using a data processing technique according to the Article of <strong>Customs</strong> Law 1 ,<br />

which shall be amended accordingly to the Community <strong>Customs</strong> Code 8 .<br />

- Data of paper-based entry summary declaration shall be:<br />

o keyed in to the CDPS by a customs officer at the customs office of first entry, or<br />

o electronically lodged to the customs office of first entry in parallel with the paper-based entry<br />

summary declaration <strong>and</strong> it is not necessary to be approved by customs authorities.<br />

- The paper-based entry summary declaration shall be lodged at the customs office of first entry within the<br />

specified time limit <strong>and</strong> before the goods are brought into the Macedonian customs territory or the<br />

customs territory of the Community.<br />

- Automated initial checks of paper-based entry summary declaration shall cover:<br />

o filling in the data-elements or data-groups (boxes of entry summary declaration),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements or data-groups.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of entry summary declaration<br />

(logical controls).<br />

3.5.1.3 Acceptance, modifications, rectifications <strong>and</strong> deletions of END<br />

- The entry summary declaration shall be registered <strong>and</strong> accepted with MRN (Movement Reference<br />

Number) by the customs office of lodgement/customs office of first entry if all above automated checks<br />

passed successfully.<br />

- If any automatic checks didn’t pass successfully the entry summary declaration shall be refused <strong>and</strong> this<br />

information with identification of mistake shall be notified by a customs officer to the person, who<br />

lodged the electronic entry summary declaration. Receiving this information the person, who lodged the<br />

entry summary declaration, shall:<br />

o amend his refused entry summary declaration <strong>and</strong> lodge it (with same LRN) again to the customs<br />

office of lodgement/customs office of first entry, or<br />

o lodge a new entry summary declaration to the customs office of lodgement/customs office of first<br />

entry (with new LRN).<br />

- The registered or accepted entry summary declaration can be changed by a person, who lodged the entry<br />

summary declaration, before the decision on a control of goods is taken. When the entry summary<br />

declaration was registered or accepted by the customs office of lodgement/customs office of first entry,<br />

this entry summary declaration can be:<br />

o modified by an electronic message (with MRN <strong>and</strong> same LRN) sent to the customs office of<br />

lodgement/customs office of first entry, or<br />

o changed or amended by a new entry summary declaration which shall be sent to the customs office<br />

of lodgement/customs office of first entry (old entry summary declaration shall be cancelled by<br />

another electronic message),<br />

o cancelled by a message sent to the customs office of lodgement/customs office of first entry.<br />

- Any modification or cancellation done by an electronic message shall be confirmed by the customs<br />

office of lodgement/customs office of first entry with an electronic message. Authentication of this<br />

decision shall be with an e-signature of customs administration, according to the Article 109 para. 2 of<br />

the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- After the acceptance of entry summary declaration by the customs office of lodgement/customs office of<br />

first entry the decision on control based on full safety <strong>and</strong> security related risk analysis shall be taken by<br />

a customs officer at the customs office of lodgement/customs office of first entry. The Risk analysis <strong>and</strong><br />

risk management system sub-application shall be used for automated evaluation of possible risks.<br />

Page 94/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

3.5.2 Trade <strong>Customs</strong> office of first entry<br />

3.5.2.1 Risk analysis - pre-requisite controls<br />

- In case that the entry summary declaration was processed electronically at the customs office of<br />

lodgement, the customs office of first entry:<br />

o shall receive the entry summary declaration with full safety <strong>and</strong> security related risk analysis from<br />

the customs office of lodgement,<br />

o can carry out the own risk analysis in advance based on the data of entry summary declaration.<br />

- In case that the entry summary declaration was processed electronically at the customs office of entry the<br />

full safety <strong>and</strong> security related risk analysis shall be done at that customs office.<br />

- In case that the imported goods temporarily leave the customs territory (Macedonian customs territory or<br />

the EU customs territory) while moving between two points in that territory by air (or see), provided that<br />

the carriage is effected by a direct route <strong>and</strong> by regular air (or shipping) services without a stop outside<br />

the customs territory, the new entry summary declaration shall not be used. The customs office of<br />

subsequent entry shall receive the results of safety <strong>and</strong> security related risk analysis from the customs<br />

office of lodgement.<br />

3.5.2.2 Arrival notification<br />

- Lodging of electronic arrival notification (IE347) is possible according to the Article of <strong>Customs</strong> Law 1 ,<br />

which shall be amended accordingly to the Community <strong>Customs</strong> Code 8 .<br />

- Electronic lodging of arrival notification (IE347) by a person who brings the goods, or who assumes<br />

responsibility for the carriage of the goods, into the Macedonian customs territory or the customs<br />

territory of the Community shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a person who brings the goods, or who assumes responsibility for the<br />

carriage of the goods, into the Macedonian customs territory or the customs territory of the Community,<br />

shall be replaced by e-signature according to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

The e-signature(s) shall be registered together with the identification of that person in the module for<br />

authorisation of e-communication in the Authorisation sub-application.<br />

- The electronic arrival notification (IE347) shall be lodged at the customs office of first entry within the<br />

specified time limit <strong>and</strong> before the goods are brought into the Macedonian customs territory or the<br />

customs territory of the Community.<br />

- Automated initial checks of electronic arrival notification (IE347) shall cover:<br />

o validity of the e-signature via data from module for authorisation of e-communication in the<br />

Authorisation sub-application,<br />

o filling in the data-elements (boxes of arrival notification (IE347)),<br />

o compliance with the rules <strong>and</strong> conditions applied for the data-elements.<br />

- Automated initial checks of validity <strong>and</strong>/or accuracy of some of data of arrival notification (logical<br />

controls).<br />

3.5.2.3 Presentation of goods<br />

- According to the Article of <strong>Customs</strong> Law 1 , which shall be amended accordingly to the Community<br />

<strong>Customs</strong> Code 8 the person who brings the goods, or who assumes responsibility for the carriage of the<br />

goods, into of the Macedonian customs territory or the customs territory of the Community (i.e. a carrier)<br />

Page 95/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

shall present that goods at the customs office of first entry with the notification of arrival in the form of<br />

message (IE347).<br />

- According to the Article of <strong>Customs</strong> Law 1 , which shall be amended accordingly to the Community<br />

<strong>Customs</strong> Code 8 the person who brings the goods, or who assumes responsibility for the carriage of the<br />

goods, into of the Macedonian customs territory or the customs territory of the Community (i.e. a carrier)<br />

shall present that goods at the customs office of subsequent entry with the notification of arrival in the<br />

form of message (IE344).<br />

3.5.2.4 Control of goods<br />

- When decision on control of goods which have been presented at the customs office of first entry is<br />

taken, the notification of this control shall be passed to the carrier. Authentication of electronic form of<br />

this notification of control shall be with an e-signature of customs administration, according to the<br />

Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

first entry to be used by a customs officer responsible for control of goods. This protocol shall contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

- When decision on control of goods is taken, the entry summary declaration cannot be changed, modified,<br />

amended or cancelled at the customs office of first entry. The results of control shall be registered at this<br />

customs office.<br />

- Based on the customs control, the declared goods can be allowed to entry into the Macedonian customs<br />

territory or the customs territory of the Community or the entry summary declaration can be modified,<br />

changed or cancelled.<br />

3.5.2.5 Diversion<br />

- The carrier may present the goods at the customs office other than the declared customs office of first<br />

entry mentioned in entry summary declaration.<br />

- In case of national diversion (the originally declared first customs office of entry <strong>and</strong> actual first customs<br />

office of entry are in the same state), the carrier shall not send the information on diversion to the<br />

originally declared first customs office of entry.<br />

- In case of international diversion (the originally declared first customs office of entry <strong>and</strong> actual first<br />

customs office of entry are not in the same member state), the carrier shall only send the information on<br />

diversion to the originally declared first customs office of entry, when the goods will entry into the<br />

customs territory of Community via another member state than originally declared first customs office of<br />

entry is. It is not necessary to lodge a new entry summary declaration.<br />

- All other exchange of information shall be on the originally declared customs office of entry <strong>and</strong> the new<br />

customs office of entry. The originally declared customs office of entry shall inform the new customs<br />

office of entry about the diversion <strong>and</strong> it shall provide the new customs office of entry with the result of<br />

safety <strong>and</strong> security related risk analysis from the customs office of lodgement/ originally declared<br />

customs office of entry.<br />

3.5.3 Trade <strong>Customs</strong> office of subsequent entry<br />

3.5.3.1 Notification of arrival<br />

Page 96/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The person who brings the goods, or who assumes responsibility for the carriage of the goods, into of the<br />

Macedonian customs territory or the customs territory of the Community (i.e. a carrier) shall present that<br />

goods at the customs office of subsequent entry with the notification of arrival in the form of message<br />

(IE344).<br />

- Lodging of electronic arrival notification (IE344) is possible according to the Article of <strong>Customs</strong> Law 1 ,<br />

which shall be amended accordingly to the Community <strong>Customs</strong> Code 8 .<br />

- Electronic lodging of arrival notification (IE344) by a person who brings the goods, or who assumes<br />

responsibility for the carriage of the goods, into the Macedonian customs territory or the customs<br />

territory of the Community shall be authorised according to the Articles 4 <strong>and</strong> 5 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The h<strong>and</strong> written signature of a person who brings the goods, or who assumes responsibility for the<br />

carriage of the goods, into the Macedonian customs territory or the customs territory of the Community,<br />

shall be replaced by e-signature according to the Article 5 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

The e-signature(s) shall be registered together with the identification of that person in the module for<br />

authorisation of e-communication in the Authorisation sub-application.<br />

3.5.3.2 Pre-requisite controls<br />

- In case that the imported goods temporarily leave the customs territory (Macedonian customs territory or<br />

the EU customs territory) while moving between two points in that territory by air (or see), provided that<br />

the carriage is effected by a direct route <strong>and</strong> by regular air (or shipping) services without a stop outside<br />

the customs territory, the customs office of subsequent entry shall receive only the results of safety <strong>and</strong><br />

security related risk analysis from the customs office of lodgement, if they are any.<br />

- The customs office of subsequent entry may carry out its own risk analysis based on the results of safety<br />

<strong>and</strong> security related risk analysis <strong>and</strong> the copy of entry summary declaration sent electronically from the<br />

customs office of lodgement/customs office of first entry.<br />

3.5.3.3 Presentation of goods<br />

- When decision on control of goods which have been presented at the customs office of subsequent entry<br />

is taken, the notification of this control shall be passed to the carrier. Authentication of electronic form of<br />

this notification of control shall be with an e-signature of customs administration, according to the<br />

Article 109 para. 2 of the <strong>Customs</strong> Law implementing Regulation 2 .<br />

- When decision on control of goods is taken, the control protocol shall be issued at the customs office of<br />

subsequent entry to be used by a customs officer responsible for control of goods. This protocol shall<br />

contain:<br />

o the specification of type <strong>and</strong> all details of control, including the identification of which part of<br />

declared goods or a means of transport shall be controlled,<br />

o the results of customs control,<br />

o discrepancies discovered during the customs control,<br />

o verification of report by a customs officer responsible for control of goods.<br />

3.5.3.4 Diversion<br />

- The person who brings the goods, or who assumes responsibility for the carriage of the goods, into of the<br />

Macedonian customs territory or the customs territory of the Community (i.e. a carrier) shall present that<br />

goods at the customs office of subsequent entry with the notification of arrival in the form of message<br />

(IE344).<br />

- The person who brings the goods, or who assumes responsibility for the carriage of the goods, into of the<br />

Macedonian customs territory or the customs territory of the Community (i.e. a carrier) may present the<br />

Page 97/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

goods at the customs office other than the declared customs office of subsequent entry mentioned in<br />

entry summary declaration.<br />

- In case of diversion, the carrier shall send the arrival notification to the actual customs office of<br />

subsequent entry.<br />

- All other exchange of information shall be on the originally declared customs office of entry <strong>and</strong> the new<br />

customs office of subsequent entry. The originally declared customs office of entry shall provide the new<br />

customs office of subsequent entry with the result of safety <strong>and</strong> security related risk analysis from the<br />

customs office of lodgement/ originally declared customs office of entry.<br />

3.5.4 Process at entry<br />

- The goods are allowed to be assigned to a customs approved treatment or use or to be placed into the<br />

temporary storage warehouse when:<br />

o the decision on NO control of goods is taken, or<br />

o the control of goods finished with the satisfactory result without amending the entry summary<br />

declaration, or<br />

o the control of goods finished with the satisfactory result with amending the entry summary<br />

declaration.<br />

- The processes described in part 3.4 of this document shall be further used.<br />

4 SUB-APPLICATIONS<br />

4.1 Authorisations sub-application<br />

4.1.1 Authorisations in Transit regime<br />

4.1.1.1 Simplified procedure of authorised consignor<br />

- The use of simplified procedure of authorised consignor in national transit regime is granted according to<br />

the Articles 265 - 271 of <strong>Customs</strong> Law Implementing Regulation 2 . The use of simplified procedure of<br />

authorised consignor in common transit regime is granted according to the Article 65 – 71 of Appendix I<br />

of Convention on a common transit procedure.<br />

- The registry of authorisation of simplified procedure of authorised consignor shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of transit declaration,<br />

o whether this authorisation is valid for national transit regime <strong>and</strong>/or common transit regime, which<br />

shall be used for the cross-check of information from box 1 of transit declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 50 of transit<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 50 of transit declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 50 or 54 of transit declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 50 or 54 of transit declaration,<br />

o type of guarantee (comprehensive guarantee or guarantee waiver), which shall be used for the crosscheck<br />

of information from box 52 of transit declaration,<br />

Page 98/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o registration number of used guarantee (guarantee reference number) which is used for national<br />

transit regime <strong>and</strong>/or common transit regime, which shall be used for the cross-check of information<br />

from box 52 of transit declaration,<br />

o restriction of validity of comprehensive guarantee for risky goods, which shall be used for the crosscheck<br />

of information from box 52 of transit declaration,<br />

o list of goods to be released for transit regime by the holder of authorisation (positive <strong>and</strong>/or negative<br />

enumeration), which shall be used for the cross-check of information from box 33 or 31 of transit<br />

declaration,<br />

o maximum declared time limit for presentation of goods at the customs office of destination, which<br />

shall be used for the cross-check of information from box D of transit declaration,<br />

o timer for automatic release of goods for transit regime, which shall be used for automatic release of<br />

goods for transit regime,<br />

o customs office of departure, where this authorisation is valid, <strong>and</strong> the list of authorised locations of<br />

goods within this customs office, or the list of customs offices of departure with their lists of<br />

authorised locations of goods, which shall be used for the cross-check of information from box 44 of<br />

transit declaration,<br />

o list of seals to be used by the holder of authorisation, if it was granted, which shall be used for the<br />

cross-check of information from box D of transit declaration,<br />

o authorisation for exemption regarding prescribed itinerary, if it was granted, which shall be used for<br />

the cross-check of information from box 44 of transit declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of authorised consignors shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.1.2 Simplified procedure of authorised consignee<br />

- The use of simplified procedure of authorised consignee is granted according to the Article 272 - 275 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 . The use of simplified procedure of authorised consignee in<br />

common transit regime is granted according to the Articles 72 -74a of Appendix I of Convention on a<br />

common transit procedure.<br />

- After the implementation of NCTS/TIR modification in transit module of CDPS, the use of simplified<br />

procedure of authorised consignee in national transit regime is granted according to the Article of<br />

<strong>Customs</strong> Law Implementing Regulation 2 which shall be amended accordingly to the Community<br />

<strong>Customs</strong> Code Implementing Provisions 9 .<br />

- The registry of authorisation of simplified procedure of authorised consignee shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

arrival notification,<br />

o whether this authorisation is valid for national transit regime <strong>and</strong>/or common transit regime, which<br />

shall be used for the cross-check of information from the arrival notification,<br />

o holder of authorisation, which shall be used for the cross-check of information from the arrival<br />

notification,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from the arrival notification,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from the arrival notification,<br />

Page 99/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

the arrival notification,<br />

o type of guarantee (comprehensive guarantee) for the temporary storage,<br />

o registration number of used guarantee (guarantee reference number) which is used for the temporary<br />

storage,<br />

o list of goods for which the transit regime to be ended by the holder of authorisation (positive <strong>and</strong>/or<br />

negative enumeration), which shall be used for the cross-check of information from the arrival<br />

notification,<br />

o customs office of destination, where this authorisation is valid, <strong>and</strong> the list of authorised locations of<br />

goods within this customs office, or the list of customs offices of destination with their lists of<br />

authorised locations of goods, which shall be used for the cross-check of information from arrival<br />

notification,<br />

o timer for automatic release of goods for ending of transit regime by the holder of authorisation,<br />

o maximum time limit for sending the control results to the customs office of destination, which shall<br />

be used for the cross-check of communication of holder of authorisation,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of authorised consignees shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.1.3 Simplified procedure of use of special seals<br />

- The use of simplified procedure of use of special seals in national transit regime is granted according to<br />

the Articles 263 of <strong>Customs</strong> Law Implementing Regulation 2 . The use of simplified procedure of use of<br />

special seals in common transit regime is granted according to the Article 63 of Appendix I of<br />

Convention on a common transit procedure.<br />

- The registry of authorisation of simplified procedure of use of special seals shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of transit declaration,<br />

o whether this authorisation is valid for national transit regime <strong>and</strong>/or common transit regime, which<br />

shall be used for the cross-check of information from box 1 of transit declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 50 of transit<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 50 of transit declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 50 or 54 of transit declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 50 or 54 of transit declaration,<br />

o list of seals to be used by the holder of authorisation, if it was granted, which shall be used for the<br />

cross-check of information from box D of transit declaration,<br />

o customs office of departure or the list of customs offices of departure, where this authorisation is<br />

valid,<br />

Page 100/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of use of special seals shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.1.4 Simplified procedure of exemption regarding prescribed itinerary<br />

- The use of simplified procedure of exemption regarding prescribed itinerary in national transit regime is<br />

granted according to the Articles 264 of <strong>Customs</strong> Law Implementing Regulation 2 . The use of simplified<br />

procedure of use of exemption regarding prescribed itinerary in common transit regime is granted<br />

according to the Article 64 of Appendix I of Convention on a common transit procedure.<br />

- The registry of authorisation of simplified procedure of exemption regarding prescribed itinerary shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of transit declaration,<br />

o whether this authorisation is valid for national transit regime <strong>and</strong>/or common transit regime, which<br />

shall be used for the cross-check of information from box 1 of transit declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 50 of transit<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 50 of transit declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 50 or 54 of transit declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 50 or 54 of transit declaration,<br />

o customs office of departure or the list of customs offices of departure, where this authorisation is<br />

valid,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of exemption regarding prescribed itinerary shall be visible at all levels of Macedonian<br />

customs administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent<br />

customs office.<br />

4.1.1.5 Electronic communications in transit<br />

- The electronic communications in transit regime in national transit regime is granted according to the<br />

Articles 71 letter b) <strong>and</strong> 89 para. 1 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 4, 5, 109 para. 2, 129 - 131 of<br />

<strong>Customs</strong> Law Implementing Regulation 2 . The electronic communications in transit regime in common<br />

transit regime is granted according to the Article 3, 11, 17, 43 of Appendix I of Convention on a<br />

common transit procedure.<br />

- The electronic communications in transit regime shall be divided into the following types:<br />

Page 101/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o electronic communication of a principal with the customs office of departure (i.e. lodging of<br />

electronic transit declaration <strong>and</strong> connected messages),<br />

o electronic communication of a principal with the customs office of guarantee regarding a<br />

comprehensive guarantee or a guarantee waiver (e.g. management of PIN (access code) <strong>and</strong> use of<br />

comprehensive guarantee or a guarantee waiver in transit regime),<br />

o electronic communication of guarantor with the customs office of guarantee regarding an individual<br />

guarantee with vouchers <strong>and</strong> an individual guarantee (e.g. management of PIN (access code)),<br />

o electronic communication of an authorised consignee with the customs office of destination (i.e.<br />

ending of transit regime <strong>and</strong> connected messages).<br />

- The basic element for the electronic communication is the registry of e-signatures used by traders. This<br />

registry could be a part of each authorisation for electronic communication, but it is not practical, due to<br />

the fact that the issuing, changing or cancelling of authorisation is a legal act with all consequences,<br />

including the necessary time. Based on that it is more convenient to issue so called Parameters of<br />

electronic communication as a kind of notification, where e-signature(s) used by a trader is(are)<br />

registered. The registration number of concrete Parameters of electronic communication shall be<br />

mentioned in the each authorisation for electronic communication.<br />

- The Parameters of electronic communication can be used for all electronic communication for all<br />

customs regimes <strong>and</strong> it shall contain the following information/conditions to be automatically crosschecked:<br />

o registration number of Parameters of electronic communication, which is mentioned further on in the<br />

authorisation for electronic communication,<br />

o holder of Parameters of electronic communication, which is mentioned further on in the<br />

authorisation for electronic communication <strong>and</strong> which shall be used for the cross-check of<br />

information from box 50 of transit declaration,<br />

o full address of the holder of Parameters of electronic communication, which is mentioned further on<br />

in the authorisation for electronic communication <strong>and</strong> which shall be used for the cross-check of<br />

information from box 50 of transit declaration,<br />

o electronic signature certificate number <strong>and</strong> issuing authority,<br />

o time of validity of each electronic signature certificate (until), which shall be used for the crosscheck<br />

of information from box 50 or 54 of transit declaration,<br />

o cross-link with all authorisations for electronic communication, where this Parameters of electronic<br />

communication is used,<br />

o history of the authorisation.<br />

- The authorisation for electronic communication of a principal with the customs office of departure (i.e.<br />

lodging of electronic transit declaration <strong>and</strong> connected messages) shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 50 of transit<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 50 of transit declaration,<br />

o registration number of Parameters of electronic communication,<br />

o customs office of departure or the list of customs offices of departure, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

Page 102/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The electronic communication of a principal with the customs office of guarantee regarding a<br />

comprehensive guarantee or a guarantee waiver (e.g. management of PIN (access code) <strong>and</strong> use of<br />

comprehensive guarantee or a guarantee waiver in transit regime) shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 50 of transit<br />

declaration,<br />

o full address of the holder of Parameters of electronic communication, which shall be used for the<br />

cross-check of information from box 50 of transit declaration,<br />

o registration number of Parameters of electronic communication,<br />

o customs office of guarantee or the list of customs offices of guarantee, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The electronic communication of guarantor with the customs office of guarantee regarding an individual<br />

guarantee with vouchers <strong>and</strong> an individual guarantee (e.g. management of PIN (access code)) shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 50 of transit<br />

declaration,<br />

o full address of the holder of Parameters of electronic communication, which shall be used for the<br />

cross-check of information from box 50 of transit declaration,<br />

o registration number of Parameters of electronic communication<br />

o customs office of guarantee or the list of customs offices of guarantee, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The electronic communication of an authorised consignee with the customs office of destination (i.e.<br />

ending of transit regime <strong>and</strong> connected messages) shall contain the following information/conditions to<br />

be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from the electronic<br />

message,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from the electronic message,<br />

o registration number of Parameters of electronic communication<br />

o customs office of destination or the list of customs offices of destination, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

Page 103/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

4.1.1.6 Authorisation for representation in transit<br />

- The scope of used of representation in customs regimes is described in the Article 5 of <strong>Customs</strong> Law 1 .<br />

The condition for use of representation in customs regimes are specified in to the Article 5 of <strong>Customs</strong><br />

Law 1 . According to the Article 5 para. 4 of <strong>Customs</strong> Law 1 the customs authority may require the person<br />

stating that he is acting in the name of or on behalf of another person to produce evidence of his powers<br />

to act as representative. To simplify the evidence <strong>and</strong> the control of used representation the module for<br />

evidence of issued <strong>and</strong> lodged documents proving the powers to act as a representative (power of<br />

attorneys) shall be developed.<br />

- The registry of documents proving the powers to act as a representative (power of attorneys) shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of documents proving the powers to act as a representative (power of attorneys),<br />

which shall be used for the cross-check of information from box 50 of transit declaration,<br />

o whether this authorisation is valid for national transit regime <strong>and</strong>/or common transit regime, which<br />

shall be used for the cross-check of information from box 1 of transit declaration,<br />

o person, who is represented, <strong>and</strong> his full address, which shall be used for the cross-check of<br />

information from box 50 of transit declaration,<br />

o person, who represents, <strong>and</strong> his full address, which shall be used for the cross-check of information<br />

from box 50 of transit declaration,<br />

o time of validity of power of attorney (from – until), which shall be used for the cross-check of<br />

information from box 50 or 54 of transit declaration,<br />

o customs office or the list of customs offices, where this authorisation is valid,<br />

o date of actual record of the registry of power of attorney,<br />

o date of annulment of the power of attorney, which shall be used for the cross-check of information<br />

from box 50 or 54 of transit declaration.<br />

4.1.2 Authorisations in Export regimes<br />

4.1.2.1 Simplified procedure of local clearance in export regimes<br />

- The use of simplified procedure of local clearance in export regime is granted according to the Article 88<br />

of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 167, 169, 196, 199 - 204 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The registry of authorisation of simplified procedure of local clearance in export regime shall contain the<br />

following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of export declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of export<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of export declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of transit declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of transit declaration,<br />

o list of goods to be released for export regime by the holder of authorisation (positive <strong>and</strong>/or negative<br />

enumeration), which shall be used for the cross-check of information from box 33 of export<br />

declaration,<br />

o maximum declared time limit for presentation of goods at the customs office of exit, which shall be<br />

used for the cross-check of information from box D of export declaration,<br />

Page 104/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o timer for automatic release of goods for export regime, which shall be used for automatic release of<br />

goods for export regime,<br />

o customs office of export, where this authorisation is valid, <strong>and</strong> the list of authorised locations of<br />

goods within this customs office, or the list of customs offices of export with their lists of authorised<br />

locations of goods, which shall be used for the cross-check of information from box 44 of export<br />

declaration,<br />

o list of seals to be used by the holder of authorisation, if it was granted, which shall be used for the<br />

cross-check of information from box D of export declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations for local clearance in export regime shall be visible at all levels of Macedonian<br />

customs administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent<br />

customs office.<br />

4.1.2.2 Simplified procedure of incomplete declaration in export regimes<br />

- The use of simplified procedure of incomplete declaration in export regime is granted according to the<br />

Article 88 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 167, 169, 196, 197 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- Due to the fact that the simplified procedure of incomplete declaration in export regime shall not be used<br />

for repetitive use as the authorisation for simplified procedure of simplified declaration (Article 198<br />

para. 1 <strong>and</strong> Article 177 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 ) this authorisation shall be<br />

issued on individually without registration or with registration in the Authorisation sub-application.<br />

- The registry of authorisation of simplified procedure of incomplete declaration in export regime shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of transit declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of export<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of export declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of export declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of export declaration,<br />

o list of goods to be released for export regime by the holder of authorisation (positive <strong>and</strong>/or negative<br />

enumeration), which shall be used for the cross-check of information from box 33 or 31 of export<br />

declaration,<br />

o list of missing data elements of export declaration or missing document, which shall to accompany<br />

the export declaration,<br />

o maximum declared time limit for presentation of goods at the customs office of exit, which shall be<br />

used for the cross-check of information from box D of export declaration,<br />

o customs office of export, where this authorisation is valid, or the list of customs offices of export,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

Page 105/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations for simplified procedures of incomplete declaration in export regime shall be visible at<br />

all levels of Macedonian customs administration. The authorisation shall be created, amended <strong>and</strong><br />

cancelled only by a competent customs office.<br />

4.1.2.3 Simplified procedure of simplified declaration in export regimes<br />

- The use of simplified procedure of simplified declaration in export regime is granted according to the<br />

Article 88 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 167 - 169, 196, 198, 204 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The simplified procedure of simplified declaration in export regime shall be granted for repetitive use<br />

according to the Article 198 para. 1 <strong>and</strong> Article 177 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The registry of authorisation of simplified procedure of simplified declaration in export regime shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of export declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of export<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of export declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of export declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of export declaration,<br />

o list of goods to be released for export regime by the holder of authorisation (positive <strong>and</strong>/or negative<br />

enumeration), which shall be used for the cross-check of information from box 33 or 31 of export<br />

declaration,<br />

o list of missing data elements of export declaration or the document, which shall be used instead of<br />

st<strong>and</strong>ard export declaration in the form of SAD,<br />

o maximum time limit for presentation of supplementary declaration for export regime,<br />

o maximum declared time limit for presentation of goods at the customs office of exit, which shall be<br />

used for the cross-check of information from box D of export declaration,<br />

o customs office of export, where this authorisation is valid, or the list of customs offices of export,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations for simplified procedure of simplified declaration in export regime shall be visible at<br />

all levels of Macedonian customs administration. The authorisation shall be created, amended <strong>and</strong><br />

cancelled only by a competent customs office.<br />

4.1.2.4 Use of outward processing regime (authorisation for RwEI)<br />

- The favourable treatment from which certain goods may benefit by reason of outward processing regime<br />

shall be granted according to the Articles 98 – 104, 158 - 173 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 311 -<br />

333, 396 - 403 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

Page 106/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The registry of authorisation of outward processing regime shall at least contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of export declaration for outward processing regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of export<br />

declaration for outward processing regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of export declaration for outward processing regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of export declaration for outward processing regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of export declaration for outward processing regime,<br />

o type of outward-processing relief arrangement (processing system or st<strong>and</strong>ard exchange system),<br />

o list of goods to be released for export regime of outward processing regime by the holder of<br />

authorisation (positive enumeration), which shall be used for the cross-check of information from<br />

boxes 31 <strong>and</strong> 33 of export declaration for outward processing regime,<br />

o description of outward processing operations (processing of goods),<br />

o provisions concerning rates of yield,<br />

o means <strong>and</strong> methods of identification of goods in question <strong>and</strong> of means of customs supervision,<br />

o period within which the goods should be re-imported after the outward processing regime,<br />

o customs office of export, where the goods will be released for inward processing regime,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for import of replacement products within<br />

st<strong>and</strong>ard exchange system,<br />

o whether the simplified procedure of local clearance is used when the goods are released for outward<br />

processing regime, including the time for automatic release of goods for the regime,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of outward processing regime shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.2.5 Electronic communications in export regimes<br />

- The electronic communications in export regime is granted according to the Articles 71 letter b) <strong>and</strong> 89<br />

para. 1 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 4, 5, 109 para. 2, 129 - 131 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The electronic communications in export regime shall be divided into the following types:<br />

o electronic communication of a declarant with the customs office of export (i.e. lodging of electronic<br />

export declaration <strong>and</strong> connected messages),<br />

o electronic communication of an exit authority with the customs office of exit (i.e. ending of export<br />

regime <strong>and</strong> connected messages).<br />

- The basic element for the electronic communication is the registry of e-signatures used by traders. This<br />

registry could be a part of each authorisation for electronic communication, but it is not practical, due to<br />

the fact that the issuing, changing or cancelling of authorisation is a legal act with all consequences,<br />

including the necessary time. Based on that it is more convenient to issue so called Parameters of<br />

Page 107/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

electronic communication as a kind of notification, where e-signature(s) used by a trader is(are)<br />

registered. The registration number of concrete Parameters of electronic communication shall be<br />

mentioned in the each authorisation for electronic communication.<br />

- The Parameters of electronic communication can be used for all electronic communication for all<br />

customs regimes <strong>and</strong> it shall contain the following information/conditions to be automatically crosschecked:<br />

o registration number of Parameters of electronic communication, which is mentioned further on in the<br />

authorisation for electronic communication,<br />

o holder of Parameters of electronic communication, which is mentioned further on in the<br />

authorisation for electronic communication <strong>and</strong> which shall be used for the cross-check of<br />

information from box 14 of export declaration,<br />

o full address of the holder of Parameters of electronic communication, which is mentioned further on<br />

in the authorisation for electronic communication <strong>and</strong> which shall be used for the cross-check of<br />

information from box 14 of export declaration,<br />

o electronic signature certificate number <strong>and</strong> issuing authority,<br />

o time of validity of each electronic signature certificate (until), which shall be used for the crosscheck<br />

of information from box 14 or 54 of export declaration,<br />

o cross-link with all authorisations for electronic communication, where this Parameters of electronic<br />

communication is used,<br />

o history of the authorisation.<br />

- The authorisation for electronic communication of a declarant with the customs office of export (i.e.<br />

lodging of electronic export declaration <strong>and</strong> connected messages) shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of export<br />

declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of export declaration,<br />

o registration number of Parameters of electronic communication,<br />

o customs office of export or the list of customs offices of export, where this authorisation is valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The electronic communication of an exit authority with the customs office of exit (i.e. ending of export<br />

regime <strong>and</strong> connected messages) shall contain the following information/conditions to be automatically<br />

cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from the electronic<br />

message,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from the electronic message,<br />

o registration number of Parameters of electronic communication<br />

o customs office of exit or the list of customs offices of exit, where this authorisation is valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

Page 108/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o history of the authorisation.<br />

4.1.2.6 Authorisation for representation in export<br />

- The scope of used of representation in customs regimes is described in the Article 5 of <strong>Customs</strong> Law 1 .<br />

The condition for use of representation in customs regimes are specified in to the Article 5 of <strong>Customs</strong><br />

Law 1 . According to the Article 5 para. 4 of <strong>Customs</strong> Law 1 the customs authority may require the person<br />

stating that he is acting in the name of or on behalf of another person to produce evidence of his powers<br />

to act as representative. To simplify the evidence <strong>and</strong> the control of used representation the module for<br />

evidence of issued <strong>and</strong> lodged documents proving the powers to act as a representative (power of<br />

attorneys) shall be developed.<br />

- The registry of documents proving the powers to act as a representative (power of attorneys) shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of documents proving the powers to act as a representative (power of attorneys),<br />

which shall be used for the cross-check of information from box 14 of export declaration,<br />

o whether this authorisation is valid for export regime, which shall be used for the cross-check of<br />

information from box 1 of export declaration,<br />

o person, who is represented, <strong>and</strong> his full address, which shall be used for the cross-check of<br />

information from box 14 of export declaration,<br />

o person, who represents, <strong>and</strong> his full address, which shall be used for the cross-check of information<br />

from box 14 of export declaration,<br />

o time of validity of power of attorney (from – until), which shall be used for the cross-check of<br />

information from box 14 or 54 of export declaration,<br />

o customs office or the list of customs offices, where this authorisation is valid,<br />

o date of actual record of the registry of power of attorney,<br />

o date of annulment of the power of attorney, which shall be used for the cross-check of information<br />

from box 14 or 54 of export declaration.<br />

4.1.3 Authorisations in Import regimes<br />

4.1.3.1 Simplified procedure of local clearance in free circulation<br />

- The use of simplified procedure of local clearance in free circulation import regime is granted according<br />

to the Article 88 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 167 – 169, 179 - 183 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The registry of authorisation of simplified procedure of local clearance in free circulation import regime<br />

shall contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of import declaration for free circulation,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration for free circulation,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration for free circulation,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of import declaration for free circulation,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of import declaration for free circulation,<br />

Page 109/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o list of goods to be released for import regime of free circulation by the holder of authorisation<br />

(positive <strong>and</strong>/or negative enumeration), which shall be used for the cross-check of information from<br />

box 33 of import declaration for free circulation,<br />

o maximum time limit for presentation of supplementary declaration at the customs office of import,<br />

o timer for automatic release of goods for import regime of free circulation, which shall be used for<br />

automatic release of goods for import regime of free circulation,<br />

o customs office of import, where this authorisation is valid, <strong>and</strong> the list of authorised locations of<br />

goods within this customs office, or the list of customs offices of import with their lists of authorised<br />

locations of goods, which shall be used for the cross-check of information from box 44 of import<br />

declaration for free circulation,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations for local clearance in import regime of free circulation shall be visible at all levels of<br />

Macedonian customs administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by<br />

a competent customs office.<br />

4.1.3.2 Simplified procedure of incomplete declaration in free circulation<br />

- The use of simplified procedure of incomplete declaration in free circulation import regime is granted<br />

according to the Article 88 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 167, 169 - 175 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- Due to the fact that the simplified procedure of incomplete declaration in free circulation import regime<br />

shall not be used for repetitive use as the authorisation for simplified procedure of simplified declaration<br />

(Article 177 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 ) this authorisation shall be issued on<br />

individually without registration or with registration in the Authorisation sub-application.<br />

- The registry of authorisation of simplified procedure of incomplete declaration in free circulation import<br />

regime shall contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of declaration for free circulation import regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

declaration for free circulation import regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of declaration for free circulation import regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of declaration for free circulation import regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of declaration for free circulation import regime,<br />

o list of goods to be released for free circulation import regime by the holder of authorisation (positive<br />

<strong>and</strong>/or negative enumeration), which shall be used for the cross-check of information from box 33 of<br />

declaration for free circulation import regime,<br />

o list of missing data elements of declaration for free circulation import regime or missing<br />

document(s), which shall to accompany the declaration for free circulation import regime,<br />

Page 110/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o maximum declared time limit for presentation of missing data elements of declaration for free<br />

circulation import regime or missing document(s), which shall to accompany the declaration for free<br />

circulation import regime,<br />

o customs office of import, where this authorisation is valid, or the list of customs offices of import,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations for simplified procedures of incomplete declaration in free circulation import regime<br />

shall be visible at all levels of Macedonian customs administration. The authorisation shall be created,<br />

amended <strong>and</strong> cancelled only by a competent customs office.<br />

4.1.3.3 Simplified procedure of simplified declaration in free circulation<br />

- The use of simplified procedure of simplified declaration in free circulation import regime is granted<br />

according to the Article 88 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 167 - 169, 176 - 178 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The simplified procedure of simplified declaration in free circulation import regime shall be granted for<br />

repetitive use according to the Article 177 para. 2 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The registry of authorisation of simplified procedure of simplified declaration in free circulation import<br />

regime shall contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of declaration for free circulation import regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

declaration for free circulation import regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of declaration for free circulation import regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of declaration for free circulation import regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of declaration for free circulation import regime,<br />

o list of goods to be released for free circulation import regime by the holder of authorisation (positive<br />

<strong>and</strong>/or negative enumeration), which shall be used for the cross-check of information from box 33 of<br />

simplified declaration in free circulation import regime,<br />

o list of missing data elements of declaration for free circulation import regime or the document,<br />

which shall be used instead of st<strong>and</strong>ard declaration in free circulation import regime in the form of<br />

SAD,<br />

o maximum time limit for presentation of supplementary declaration for free circulation import<br />

regime,<br />

o customs office of import, where this authorisation is valid, or the list of customs offices of import,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

Page 111/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations for simplified procedure of simplified declaration in free circulation import regime<br />

shall be visible at all levels of Macedonian customs administration. The authorisation shall be created,<br />

amended <strong>and</strong> cancelled only by a competent customs office.<br />

4.1.3.4 Authorisation of end-use<br />

- The favourable tariff treatment from which certain goods may benefit by reason of end-use shall be<br />

granted according to the Articles 20 <strong>and</strong> 95 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 207 – 215 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 .<br />

- The registry of authorisation of end-use in free circulation import regime shall at least contain the<br />

following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of import declaration for free circulation,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration for free circulation,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration for free circulation,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of import declaration for free circulation,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of import declaration for free circulation,<br />

o list of goods to be released for import regime of free circulation with end-use by the holder of<br />

authorisation (positive enumeration), which shall be used for the cross-check of information from<br />

boxes 31 <strong>and</strong> 33 of import declaration for free circulation,<br />

o description of end-use operations (processing of goods),<br />

o provisions concerning rates of yield,<br />

o means <strong>and</strong> methods of identification of goods in question <strong>and</strong> of means of customs supervision,<br />

o period within which the goods should be assigned the prescribed end-use,<br />

o customs office of import, where the goods will be released for free circulation with end-use,<br />

o customs office of control with the list of authorised locations of goods,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o conditions for transfer of the goods in accordance with Article 212 paragraph (1) of <strong>Customs</strong> Law<br />

Implementing Regulation 2 ,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of end-use in import regime of free circulation shall be visible at all levels of<br />

Macedonian customs administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by<br />

a competent customs office.<br />

4.1.3.5 Use of customs warehousing regime (authorisation for RwEI)<br />

Page 112/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The favourable treatment from which certain goods may benefit by reason of customs warehousing<br />

regime shall be granted according to the Articles 98 – 104, 110 - 127 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles<br />

311 - 344 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The registry of authorisation of inward processing regime shall at least contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of import declaration for customs warehousing regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration for customs warehousing regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration for customs warehousing regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of import declaration for customs warehousing regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of import declaration for customs warehousing regime,<br />

o type of customs warehouse,<br />

o list of goods to be released for import regime of customs warehousing regime by the holder of<br />

authorisation (positive enumeration), which shall be used for the cross-check of information from<br />

boxes 31 <strong>and</strong> 33 of import declaration for customs warehousing regime,<br />

o provisions concerning rates of yield,<br />

o means <strong>and</strong> methods of identification of goods in question <strong>and</strong> of means of customs supervision,<br />

o customs office of import, where the goods will be released for customs warehousing regime,<br />

o customs office of control with the list of authorised locations of goods,<br />

o customs office of discharge, where a customs approved treatment or use will be assigned to the<br />

goods,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o conditions for transfer of the goods in accordance with Articles 322 - 325 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 (transfer shall not be possible where the place of departure or arrival of<br />

the goods is a type B warehouse),<br />

o whether the simplified procedure of local clearance is used when the goods are released for customs<br />

warehousing regime, including the time for automatic release of goods for the regime, according to<br />

the Articles 188 - 190 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of customs warehousing regime shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.3.6 Use of inward processing regime (authorisation for RwEI)<br />

- The favourable treatment from which certain goods may benefit by reason of inward processing regime<br />

shall be granted according to the Articles 98 – 104, 128 - 142 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 311 -<br />

333, 345 - 362 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

Page 113/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The registry of authorisation of inward processing regime shall at least contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of import declaration for inward processing regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration for inward processing regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration for inward processing regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of import declaration for inward processing regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of import declaration for inward processing regime,<br />

o type of inward-processing relief arrangement (system of suspension or drawback system),<br />

o list of goods to be released for import regime of inward processing regime by the holder of<br />

authorisation (positive enumeration), which shall be used for the cross-check of information from<br />

boxes 31 <strong>and</strong> 33 of import declaration for inward processing regime,<br />

o description of inward processing operations (processing of goods),<br />

o provisions concerning rates of yield,<br />

o means <strong>and</strong> methods of identification of goods in question <strong>and</strong> of means of customs supervision,<br />

o period within which the goods should be assigned the prescribed inward processing regime,<br />

o customs office of import, where the goods will be released for inward processing regime,<br />

o customs office of control with the list of authorised locations of goods,<br />

o customs office of discharge, where a customs approved treatment or use will be assigned to the<br />

compensating products (goods),<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o conditions for transfer of the goods in accordance with Articles 322 - 325 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 (transfer shall not be possible where the place of departure or arrival of<br />

the goods is a type B warehouse),<br />

o whether the simplified procedure of local clearance is used when the goods are released for inward<br />

processing regime, including the time for automatic release of goods for the regime, according to the<br />

Article 192 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- The automatic control of value import goods per holder of authorisation <strong>and</strong> per calendar year for each<br />

ten-digit <strong>Customs</strong> Tariff code does not exceed 10 000 EUR in corresponding denar value, according to<br />

the Article 348 letter b) of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- All authorisations of inward processing regime shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.3.7 Use of temporary importation regime (authorisation for RwEI)<br />

Page 114/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The favourable treatment from which certain goods may benefit by reason of temporary importation<br />

regime shall be granted according to the Articles 98 – 104, 150 - 157 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles<br />

311 - 333, 365 - 395 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

- The registry of authorisation of temporary importation regime shall at least contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of import declaration for temporary importation regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration for temporary importation regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration for temporary importation regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of import declaration for temporary importation regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of import declaration for temporary importation regime,<br />

o type of relief from customs duty arrangement <strong>and</strong> the description of temporary importation<br />

operations (total or partial relief),<br />

o list of goods to be released for temporary importation regime by the holder of authorisation (positive<br />

enumeration), which shall be used for the cross-check of information from boxes 31 <strong>and</strong> 33 of<br />

import declaration for temporary importation regime,<br />

o means <strong>and</strong> methods of identification of goods in question <strong>and</strong> of means of customs supervision,<br />

o period within which the goods should be assigned the prescribed temporary importation regime,<br />

o customs office of import, where the goods will be released for temporary importation regime,<br />

o customs office of control with the list of authorised locations of goods,<br />

o customs office of discharge, where a customs approved treatment or use will be assigned to the<br />

goods,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o conditions for transfer of the goods in accordance with Articles 322 - 325 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 (transfer shall not be possible where the place of departure or arrival of<br />

the goods is a type B warehouse),<br />

o whether the simplified procedure of local clearance is used when the goods are released for<br />

temporary importation regime, including the time for automatic release of goods for the regime,<br />

according to the Article 192 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of temporary importation regime shall be visible at all levels of Macedonian customs<br />

administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by a competent customs<br />

office.<br />

4.1.3.8 Use of processing under customs control regime (authorisation for RwEI)<br />

- The favourable treatment from which certain goods may benefit by reason of processing under customs<br />

control regime shall be granted according to the Articles 98 – 104, 143 - 149 of <strong>Customs</strong> Law 1 <strong>and</strong> the<br />

Articles 311 - 333, 365 - 395 of <strong>Customs</strong> Law Implementing Regulation 2 .<br />

Page 115/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The registry of authorisation of processing under customs control regime shall at least contain the<br />

following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of import declaration for processing under customs control regime,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration for processing under customs control regime,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration for processing under customs control regime,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 of import declaration for processing under customs control regime,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 of import declaration for processing under customs control regime,<br />

o list of goods to be released for processing under customs control regime by the holder of<br />

authorisation (positive enumeration), which shall be used for the cross-check of information from<br />

boxes 31 <strong>and</strong> 33 of import declaration for processing under customs control regime,<br />

o means <strong>and</strong> methods of identification of goods in question <strong>and</strong> of means of customs supervision,<br />

o period within which the goods should be assigned the prescribed processing under customs control<br />

regime,<br />

o customs office of import, where the goods will be released for processing under customs control<br />

regime,<br />

o customs office of control with the list of authorised locations of goods,<br />

o customs office of discharge, where a customs approved treatment or use will be assigned to the<br />

goods,<br />

o security to be provided by the holder of authorisation, i.e. type of guarantee (comprehensive<br />

guarantee or individual guarantee), which shall be used for the cross-check of information from box<br />

52 of import declaration,<br />

o conditions for transfer of the goods in accordance with Articles 322 - 325 of <strong>Customs</strong> Law<br />

Implementing Regulation 2 (transfer shall not be possible where the place of departure or arrival of<br />

the goods is a type B warehouse),<br />

o whether the simplified procedure of local clearance is used when the goods are released for<br />

temporary importation regime, including the time for automatic release of goods for the regime,<br />

according to the Article 192 of <strong>Customs</strong> Law Implementing Regulation 2 ,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The regular controls of conditions for granting a particular authorisation shall be registered by this subapplication.<br />

The time limit between these control shall be set up by Macedonian customs administration<br />

<strong>and</strong> it shall be controlled by this sub-application,<br />

- All authorisations of processing under customs control regime shall be visible at all levels of<br />

Macedonian customs administration. The authorisation shall be created, amended <strong>and</strong> cancelled only by<br />

a competent customs office.<br />

4.1.3.9 Electronic communications in import regimes<br />

- The electronic communications in import regime is granted according to the Articles 71 letter b) <strong>and</strong> 89<br />

para. 1 of <strong>Customs</strong> Law 1 <strong>and</strong> the Articles 4, 5, 109 para. 2, 129 - 131 of <strong>Customs</strong> Law Implementing<br />

Regulation 2 .<br />

- The electronic communications in import regime shall be divided into the following types:<br />

o electronic communication of a carrier with the customs office of entry (i.e. lodging of electronic<br />

entry summary declaration <strong>and</strong> connected messages),<br />

Page 116/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o electronic communication of a carrier/declarant with the customs office of entry or import (i.e.<br />

lodging of electronic summary declaration <strong>and</strong> connected messages),<br />

o electronic communication of a declarant with the customs office of import (i.e. lodging of electronic<br />

import declaration <strong>and</strong> connected messages),<br />

o electronic communication of a declarant with the customs office of guarantee regarding a<br />

comprehensive guarantee (e.g. management of PIN (access code) <strong>and</strong> use of comprehensive<br />

guarantee),<br />

o electronic communication of guarantor with the customs office of guarantee regarding an individual<br />

guarantee (e.g. management of PIN (access code)).<br />

- The basic element for the electronic communication is the registry of e-signatures used by traders. This<br />

registry could be a part of each authorisation for electronic communication, but it is not practical, due to<br />

the fact that the issuing, changing or cancelling of authorisation is a legal act with all consequences,<br />

including the necessary time. Based on that it is more convenient to issue so called Parameters of<br />

electronic communication as a kind of notification, where e-signature(s) used by a trader is(are)<br />

registered. The registration number of concrete Parameters of electronic communication shall be<br />

mentioned in the each authorisation for electronic communication.<br />

- The Parameters of electronic communication can be used for all electronic communication for all<br />

customs regimes <strong>and</strong> it shall contain the following information/conditions to be automatically crosschecked:<br />

o registration number of Parameters of electronic communication, which is mentioned further on in the<br />

authorisation for electronic communication,<br />

o holder of Parameters of electronic communication, which is mentioned further on in the<br />

authorisation for electronic communication <strong>and</strong> which shall be used for the cross-check of<br />

information from box 14 of import declaration,<br />

o full address of the holder of Parameters of electronic communication, which is mentioned further on<br />

in the authorisation for electronic communication <strong>and</strong> which shall be used for the cross-check of<br />

information from box 14 of import declaration,<br />

o electronic signature certificate number <strong>and</strong> issuing authority,<br />

o time of validity of each electronic signature certificate (until), which shall be used for the crosscheck<br />

of information from box 14 or 54 of import declaration,<br />

o cross-link with all authorisations for electronic communication, where this Parameters of electronic<br />

communication is used,<br />

o history of the authorisation.<br />

- The authorisation for electronic communication of a declarant with the customs office of import (i.e.<br />

lodging of electronic import declaration <strong>and</strong> connected messages) shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 of import declaration,<br />

o registration number of Parameters of electronic communication,<br />

o customs office of import or the list of customs offices of import, where this authorisation is valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

Page 117/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The electronic communication of a declarant with the customs office of guarantee regarding a<br />

comprehensive guarantee (e.g. management of PIN (access code) <strong>and</strong> use of comprehensive guarantee in<br />

import regime) shall contain the following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration,<br />

o full address of the holder of Parameters of electronic communication, which shall be used for the<br />

cross-check of information from box 14 of import declaration,<br />

o registration number of Parameters of electronic communication<br />

o customs office of guarantee or the list of customs offices of guarantee, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

- The electronic communication of guarantor with the customs office of guarantee regarding an individual<br />

guarantee (e.g. management of PIN (access code)) shall contain the following information/conditions to<br />

be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration,<br />

o full address of the holder of Parameters of electronic communication, which shall be used for the<br />

cross-check of information from box 14 of import declaration,<br />

o registration number of Parameters of electronic communication<br />

o customs office of guarantee or the list of customs offices of guarantee, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

4.1.3.10 Authorisation for representation in import<br />

- The scope of representation in customs regimes is described in the Article 5 of <strong>Customs</strong> Law 1 . The<br />

condition for use of representation in customs regimes are specified in to the Article 5 of <strong>Customs</strong> Law 1 .<br />

According to the Article 5 para. 4 of <strong>Customs</strong> Law 1 the customs authority may require the person stating<br />

that he is acting in the name of or on behalf of another person to produce evidence of his powers to act as<br />

representative. To simplify the evidence <strong>and</strong> the control of used representation the module for evidence<br />

of issued <strong>and</strong> lodged documents proving the powers to act as a representative (power of attorneys) shall<br />

be developed.<br />

- The registry of documents proving the powers to act as a representative (power of attorneys) shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

o registration number of documents proving the powers to act as a representative (power of attorneys),<br />

which shall be used for the cross-check of information from box 14 of export declaration,<br />

o whether this authorisation is valid for import regime, which shall be used for the cross-check of<br />

information from box 1 of export declaration,<br />

o person, who is represented, <strong>and</strong> his full address, which shall be used for the cross-check of<br />

information from box 14 of import declaration,<br />

Page 118/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o person, who represents, <strong>and</strong> his full address, which shall be used for the cross-check of information<br />

from box 14 of import declaration,<br />

o time of validity of power of attorney (from – until), which shall be used for the cross-check of<br />

information from box 14 or 54 of import declaration,<br />

o customs office or the list of customs offices, where this authorisation is valid,<br />

o date of actual record of the registry of power of attorney,<br />

o date of annulment of the power of attorney, which shall be used for the cross-check of information<br />

from box 14 or 54 of import declaration.<br />

4.1.4 Authorised economic operator (AEO)<br />

- According to the Article 6-a of <strong>Customs</strong> Law 1 the Macedonian <strong>Customs</strong> authorities, if necessary<br />

following consultation with other competent authorities, shall grant the status of "authorised economic<br />

operator" (AEO) to any economic operator established in the Macedonian customs territory.<br />

- The status of authorised economic operator shall be granted based on the rules <strong>and</strong> conditions laid down<br />

in the Article 6-a para. 5 of <strong>Customs</strong> Law 1 , without prejudice to customs controls. <strong>Customs</strong> authorities<br />

shall, on the basis of the recognition of the status of authorised economic operator <strong>and</strong> provided that the<br />

requirements relating to a specific type of simplification are fulfilled, authorise the operator to benefit<br />

from that simplification.<br />

- The criteria for granting the status of authorised economic operator are specified in the Article 6-a para.<br />

4 <strong>and</strong> 5 of <strong>Customs</strong> Law 1 .<br />

4.1.4.1 Simplifications<br />

- An authorised economic operator shall benefit from facilitations with regard to simplifications provided<br />

for under the customs rules, according to the Article 6-a para. 2 of <strong>Customs</strong> Law 1 .<br />

- The registry of authorisation of authorised economic operators, who shall benefit from facilitations with<br />

regard to simplifications, shall contain the following information/conditions to be automatically crosschecked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of customs declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 or 50 of<br />

customs declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 or 50 of customs declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 or 50 of customs declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 or 50 of customs declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

4.1.4.2 Security <strong>and</strong> safety<br />

- An authorised economic operator shall benefit from facilitations with regard to customs controls relating<br />

to security <strong>and</strong> safety provided for under the customs rules, according to the Article 6-a para. 2 of<br />

<strong>Customs</strong> Law 1 .<br />

Page 119/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The registry of authorisation of authorised economic operators, who shall benefit from facilitations with<br />

regard to customs controls relating to security <strong>and</strong> safety, shall contain the following<br />

information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of customs declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 or 50 of<br />

customs declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 or 50 of customs declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 or 50 of customs declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 or 50 of customs declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

4.1.4.3 Simplifications <strong>and</strong> Security <strong>and</strong> safety<br />

- An authorised economic operator shall benefit from facilitations with regard to customs controls relating<br />

to security <strong>and</strong> safety <strong>and</strong>/or from simplifications provided for under the customs rules, according to the<br />

Article 6-a para. 2 of <strong>Customs</strong> Law 1 .<br />

- The registry of authorisation of authorised economic operators, who shall benefit from facilitations with<br />

regard to customs controls relating to security <strong>and</strong> safety <strong>and</strong> from simplifications, shall contain the<br />

following information/conditions to be automatically cross-checked:<br />

o registration number of authorisation, which shall be used for the cross-check of information from<br />

box 44 of customs declaration,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 or 50 of<br />

customs declaration,<br />

o full address of the holder of authorisation, which shall be used for the cross-check of information<br />

from box 14 or 50 of customs declaration,<br />

o time of validity of authorisation (from – until), which shall be used for the cross-check of<br />

information from box 54 or 50 of customs declaration,<br />

o date of actual record of the authorisation,<br />

o date of annulment of the authorisation, which shall be used for the cross-check of information from<br />

box 54 or 50 of customs declaration,<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

4.1.4.4 National <strong>and</strong> European AEO database<br />

- Based on the present situation of Macedonian customs legislation, especially <strong>Customs</strong> Law 1 <strong>and</strong><br />

<strong>Customs</strong> Law Implementing Regulation 2 the Macedonian <strong>Customs</strong> Administration shall develop a<br />

national AEO registry, which shall be able to send the national data to the EU Central AEO system <strong>and</strong><br />

to replicate the data from the EU Central AEO system.<br />

- Another solution would be that Macedonian <strong>Customs</strong> Administration could develop a national interface<br />

to EU Central AEO system before the accession of the Republic of Macedonia into the EU.<br />

- The decision on the development of national AEO registry is a national issue since this functionality<br />

could be incorporated in the national transit application or national export control application or national<br />

import control application or in another application.<br />

Page 120/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

4.2 Guarantee management system<br />

- The scope of the Guarantee management system is to register all kind of guarantees issued <strong>and</strong> accepted<br />

as a security of possible customs debt which could arise in transit regime, i.e. in a national transit regime<br />

or a common transit procedure.<br />

- The objective of the Guarantee management system is to provide the Macedonian customs authorities, as<br />

well as traders <strong>and</strong> the guarantors (in certain cases), with the on line:<br />

o control of used guarantees, especially the control of existence, validity, sufficiency of a guarantee<br />

amount or a reference amount of guarantee, etc.,<br />

o monitoring of used guarantee, especially the monitoring of actual amount of reference amount of<br />

comprehensive guarantee or a guarantee waiver, monitoring of usage of guarantee (i.e. when, for<br />

which operation <strong>and</strong> with which amount a guarantee has been used in certain period, etc.).<br />

- The following types guarantees shall be registered the Guarantee management system with the specific<br />

guarantee reference number (GRN):<br />

o guarantees for transit regime (national transit regime or a common transit procedure):<br />

→ cash deposit,<br />

→ individual guarantee in the form of single guarantee undertaking,<br />

→ individual guarantee in the form of guarantee vouchers,<br />

→ comprehensive guarantee,<br />

→ comprehensive guarantee waiver,<br />

o guarantees for other regimes than a transit regime:<br />

→ cash deposit,<br />

→ individual guarantee in the form of single guarantee undertaking,<br />

→ comprehensive guarantee,<br />

o guarantees for the excise movements or the excise warehouses (subject of final confirmation):<br />

→ cash deposit,<br />

→ individual guarantee in the form of single guarantee undertaking,<br />

→ comprehensive guarantee.<br />

4.2.1 Guarantees in transit regime<br />

- The separate registry shall be for the guarantees to be used by a principal for a national transit regime<br />

<strong>and</strong> for a common transit regime.<br />

- Before the day of accession of the Republic of Macedonia into the Convention on a common transit<br />

procedure 15 the part for the registry of guarantees for a common transit procedure shall be activated. On<br />

the day of accession of the Republic of Macedonia into the European Union the part for the registry of<br />

guarantees for a national transit regime shall be deactivated.<br />

4.2.1.1 Guarantee in the form of cash deposit<br />

- The guarantee in the form of cash deposit shall be registered with a guarantee reference number (GRN)<br />

when the amount of guarantee was delivered on a bank account of Macedonian customs administration<br />

<strong>and</strong> it is confirmed by the Accounting management system.<br />

- The amount of guarantee in the form of cash deposit shall be used for:<br />

o only one transit operation <strong>and</strong> after that it will be returned to the principal,<br />

o repetitive use, i.e. for successive transit operations.<br />

- Where the guarantee reference number (GRN) is used by a principal in his transit declaration <strong>and</strong> before<br />

the acceptance of this declaration, at least the following data shall be checked:<br />

Page 121/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o guarantee reference number (GRN),<br />

o principal,<br />

o amount of guarantee,<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for transit regime the guarantee reference number (GRN) of guarantee in<br />

the form of cash deposit shall be blocked for further use.<br />

- Where the guarantee in the form of cash deposit can be used only for one transit operation <strong>and</strong> after that<br />

it will be returned to the principal, this guarantee reference number (GRN) shall not be further used.<br />

- Where the guarantee in the form of cash deposit can be repetitively used for successive transit<br />

operations, this guarantee reference number (GRN) shall be blocked for further used until the discharge<br />

of transit regime. Where this transit regime is discharged by the customs office of departure, the<br />

guarantee reference number (GRN) shall be unblocked <strong>and</strong> it shall be further used.<br />

4.2.1.2 Individual guarantee in the form of single guarantee undertaking<br />

- The individual guarantee in the form of single guarantee undertaking shall be registered with a guarantee<br />

reference number (GRN) when the customs office of guarantee of Macedonian customs administration:<br />

o approves the guarantor to act as a guarantor for transit regime,<br />

o accepts the individual guarantee in the form of single guarantee undertaking.<br />

- The individual guarantee in the form of single guarantee undertaking shall be used for only one transit<br />

operation.<br />

- Only in specific case <strong>and</strong> based on the decision of Macedonian customs administration the individual<br />

guarantee in the form of single guarantee undertaking shall be used for repetitive use, i.e. for successive<br />

transit operations.<br />

- Where the customs office of guarantee of Macedonian customs administration accepts the individual<br />

guarantee in the form of single guarantee undertaking <strong>and</strong> this individual guarantee in the form of single<br />

guarantee undertaking is registered with a guarantee reference number (GRN), the customs office of<br />

guarantee shall issue:<br />

o decision on approval of the guarantor to act as a guarantor for transit regime,<br />

o decision on acceptance of individual guarantee in the form of single guarantee undertaking (GRN),<br />

o access code (PIN) to be used by a principal for authorised use of guarantee.<br />

- Where the guarantee reference number (GRN) is used by a principal in his transit declaration <strong>and</strong> before<br />

the acceptance of this declaration, at least the following data shall be checked:<br />

o guarantee reference number (GRN),<br />

o access code (PIN),<br />

o principal,<br />

o amount of guarantee,<br />

o goods listed in the individual guarantee in the form of single guarantee undertaking,<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for transit regime the guarantee reference number (GRN) of individual<br />

guarantee in the form of single guarantee undertaking shall be blocked for further use.<br />

- Only in specific case <strong>and</strong> based on the decision of Macedonian customs administration where the<br />

individual guarantee in the form of single guarantee undertaking can be repetitively used for successive<br />

transit operations, this guarantee reference number (GRN) shall be blocked for further used until the<br />

discharge of transit regime. Where this transit regime is discharged by the customs office of departure,<br />

the guarantee reference number (GRN) shall be unblocked <strong>and</strong> it shall be further used.<br />

Page 122/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

4.2.1.3 Individual guarantee in the form of guarantee vouchers<br />

- The guarantee undertaking for individual guarantee in the form of guarantee vouchers shall be registered<br />

with a guarantee reference number (GRN) when the customs office of guarantee of Macedonian customs<br />

administration:<br />

o approves the guarantor to act as a guarantor for transit regime,<br />

o accepts the guarantee undertaking for individual guarantee in the form of guarantee vouchers.<br />

- The individual guarantee in the form of guarantee voucher shall be used for only one transit operation.<br />

- Where the customs office of guarantee of Macedonian customs administration accepts the guarantee<br />

undertaking for individual guarantee in the form of guarantee vouchers <strong>and</strong> this guarantee undertaking<br />

for individual guarantee in the form of guarantee vouchers is registered with a guarantee reference<br />

number (GRN), the customs office of guarantee shall issue:<br />

o decision on approval of the guarantor to act as a guarantor for transit regime,<br />

o decision on acceptance of guarantee undertaking for individual guarantee in the form of guarantee<br />

vouchers (GRN),<br />

o structure of guarantee reference number of vouchers issued by a guarantor based on these decisions,<br />

o form/way of notification of access code (PIN) to guarantee reference number of voucher issued by a<br />

guarantor be used by a principal for authorised use of guarantee.<br />

- Where the guarantee reference number (GRN) <strong>and</strong> access code (PIN) are used by a principal in his<br />

transit declaration <strong>and</strong> before the acceptance of this declaration, at least the following data shall be<br />

checked:<br />

o guarantee reference number(s) (GRNs),<br />

o access code(s) (PINs),<br />

o principal,<br />

o amount of guarantee (number of vouchers),<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for transit regime the guarantee reference number (GRN) of guarantee<br />

voucher shall be blocked for further use.<br />

4.2.1.4 Comprehensive guarantee<br />

- The guarantee undertaking for comprehensive guarantee shall be registered with a guarantee reference<br />

number (GRN) when the customs office of guarantee of Macedonian customs administration:<br />

o approves the guarantor to act as a guarantor for transit regime,<br />

o accepts the guarantee undertaking for comprehensive guarantee.<br />

- The comprehensive guarantee shall be used for several transit operations.<br />

- Where the customs office of guarantee of Macedonian customs administration accepts the guarantee<br />

undertaking for comprehensive guarantee <strong>and</strong> this guarantee undertaking for comprehensive guarantee is<br />

registered with a guarantee reference number (GRN), the customs office of guarantee shall issue:<br />

o decision on approval of the guarantor to act as a guarantor for transit regime,<br />

o decision on acceptance of guarantee undertaking for comprehensive guarantee (GRN),<br />

o form/way of notification of changes of access code(s) (PIN) to guarantee reference number to be<br />

used by a principal for authorised use of guarantee.<br />

- Where the guarantee reference number (GRN) <strong>and</strong> access code (PIN) are used by a principal in his<br />

transit declaration <strong>and</strong> before the acceptance of this declaration, at least the following data shall be<br />

checked:<br />

o guarantee reference number(s) (GRNs),<br />

o access code(s) (PINs),<br />

Page 123/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o principal,<br />

o actual amount of reference amount of guarantee,<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for transit regime the amount of possible customs debt (calculated or<br />

estimated at the customs office of departure) shall be debited from the actual amount of reference<br />

amount of comprehensive guarantee.<br />

- Where the actual amount of reference amount of comprehensive guarantee is not sufficient to cover the<br />

possible customs debt (calculated or estimated at the customs office of departure) on declared goods, this<br />

comprehensive guarantee shall be blocked <strong>and</strong> this information shall be sent from the Guarantee<br />

management sub-application:<br />

o to the CDPS to inform the customs officer at the customs office of departure,<br />

o via the CDPS to the principal.<br />

- Where the goods have been presented at the customs office of destination the electronic notification is<br />

sent from this office to the customs office of departure. In case that the comprehensive guarantee was<br />

used, the customs office of departure based on this information shall notify that to the customs office of<br />

guarantee. Based on this information the amount of possible customs debt (calculated or estimated at the<br />

customs office of departure) shall be credited back to the actual amount of reference amount of<br />

comprehensive guarantee.<br />

- Where the transit regime has been discharged (i.e. the moment when the customs office of departure is in<br />

a position to establish, on the basis of a comparison of the data available to this customs office <strong>and</strong> those<br />

available to the customs office of destination, that the regime has ended correctly) the customs office of<br />

departure shall notify that to the customs office of guarantee with the request for release of a used<br />

guarantee.<br />

- At any time the principal shall have a possibility to:<br />

o change the accession code (PIN) of his comprehensive guarantee,<br />

o check the actual amount of reference amount of his comprehensive guarantee.<br />

- At any time the customs office of guarantee shall have a possibility to:<br />

o change the accession code (PIN) of comprehensive guarantee, based on the request of a principal,<br />

o check the actual amount of reference amount of comprehensive guarantee,<br />

o monitor the changes of actual amount of reference amount of comprehensive guarantee.<br />

4.2.1.5 Comprehensive guarantee waiver<br />

- The authorisation for use of comprehensive guarantee waiver shall be registered with a guarantee<br />

reference number (GRN) by the customs office of guarantee of Macedonian customs administration.<br />

- The comprehensive guarantee waiver shall be used for several transit operation.<br />

- Where the customs office of guarantee of Macedonian customs administration authorises the<br />

comprehensive guarantee waiver <strong>and</strong> this comprehensive guarantee waiver is registered with a guarantee<br />

reference number (GRN), the customs office of guarantee shall issue:<br />

o decision on authorisation of the comprehensive guarantee waiver (GRN),<br />

o form/way of notification of changes of access code(s) (PIN) to guarantee reference number to be<br />

used by a principal for authorised use of comprehensive guarantee waiver.<br />

- Where the guarantee reference number (GRN) <strong>and</strong> access code (PIN) are used by a principal in his<br />

transit declaration <strong>and</strong> before the acceptance of this declaration, at least the following data shall be<br />

checked:<br />

o guarantee reference number(s) (GRNs),<br />

o access code(s) (PINs),<br />

Page 124/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o principal,<br />

o actual amount of reference amount of comprehensive guarantee waiver,<br />

o whether the comprehensive guarantee waiver is not blocked.<br />

- Where the goods are released for transit regime the amount of possible customs debt (calculated or<br />

estimated at the customs office of departure) shall be debited from the actual amount of reference<br />

amount of comprehensive guarantee waiver.<br />

- Where the actual amount of reference amount of comprehensive guarantee waiver is not sufficient to<br />

cover the possible customs debt (calculated or estimated at the customs office of departure) on declared<br />

goods, this comprehensive guarantee waiver shall be blocked <strong>and</strong> this information shall be sent from the<br />

Guarantee management sub-application:<br />

o to the CDPS to inform the customs officer at the customs office of departure,<br />

o via the CDPS to the principal.<br />

- Where the goods have been presented at the customs office of destination the electronic notification is<br />

sent from this office to the customs office of departure. In case that the comprehensive guarantee waiver<br />

was used, the customs office of departure based on this information shall notify that to the customs office<br />

of guarantee. Based on this information the amount of possible customs debt (calculated or estimated at<br />

the customs office of departure) shall be credited back to the actual amount of reference amount of<br />

comprehensive guarantee waiver.<br />

- Where the transit regime has been discharged (i.e. the moment when the customs office of departure is in<br />

a position to establish, on the basis of a comparison of the data available to this customs office <strong>and</strong> those<br />

available to the customs office of destination, that the regime has ended correctly) the customs office of<br />

departure shall notify that to the customs office of guarantee with the request for release of a used<br />

guarantee.<br />

- At any time the principal shall have a possibility to:<br />

o change the accession code (PIN) of his comprehensive guarantee waiver,<br />

o check the actual amount of reference amount of his comprehensive guarantee waiver.<br />

- At any time the customs office of guarantee shall have a possibility to:<br />

o change the accession code (PIN) of comprehensive guarantee waiver, based on the request of a<br />

principal,<br />

o check the actual amount of reference amount of comprehensive guarantee waiver,<br />

o monitor the changes of actual amount of reference amount of comprehensive guarantee waiver.<br />

4.2.2 Guarantees in other regimes than transit regime<br />

- The separate registry shall be for the guarantees to be used by a declarant for a import regime <strong>and</strong>/or for<br />

a temporary storage.<br />

4.2.2.1 Guarantee in the form of cash deposit<br />

- The guarantee in the form of cash deposit shall be registered with a guarantee reference number (GRN)<br />

when the amount of guarantee was delivered on a bank account of Macedonian customs administration<br />

<strong>and</strong> it is confirmed by the Accounting management system.<br />

- The amount of guarantee in the form of cash deposit shall be used for:<br />

o only one import operation <strong>and</strong> after that it will be returned to the declarant,<br />

o repetitive use, i.e. for successive import operations.<br />

- Where the guarantee reference number (GRN) is used by a declarant in his import or summary<br />

declaration <strong>and</strong> before the acceptance of this declaration, at least the following data shall be checked:<br />

o guarantee reference number (GRN),<br />

Page 125/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o declarant,<br />

o amount of guarantee,<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for import regime or they are placed into the temporary storage facility the<br />

guarantee reference number (GRN) of guarantee in the form of cash deposit shall be blocked for further<br />

use.<br />

- Where the guarantee in the form of cash deposit can be used only for one import operation <strong>and</strong> after that<br />

it will be returned to the declarant, this guarantee reference number (GRN) shall not be further used.<br />

- Where the guarantee in the form of cash deposit can be repetitively used for successive import<br />

operations, this guarantee reference number (GRN) shall be blocked for further used until the discharge<br />

of import regime. Where this import regime is discharged by the customs office of import, the guarantee<br />

reference number (GRN) shall be unblocked <strong>and</strong> it shall be further used.<br />

4.2.2.2 Individual guarantee in the form of single guarantee undertaking<br />

- The individual guarantee in the form of single guarantee undertaking shall be registered with a guarantee<br />

reference number (GRN) when the customs office of guarantee of Macedonian customs administration:<br />

o approves the guarantor to act as a guarantor for import regime or for temporary storage,<br />

o accepts the individual guarantee in the form of single guarantee undertaking.<br />

- The individual guarantee in the form of single guarantee undertaking shall be used for only one import<br />

operation.<br />

- Where the customs office of guarantee of Macedonian customs administration accepts the individual<br />

guarantee in the form of single guarantee undertaking <strong>and</strong> this individual guarantee in the form of single<br />

guarantee undertaking is registered with a guarantee reference number (GRN), the customs office of<br />

guarantee shall issue:<br />

o decision on approval of the guarantor to act as a guarantor for import regime or for temporary<br />

storage,<br />

o decision on acceptance of individual guarantee in the form of single guarantee undertaking (GRN),<br />

o access code (PIN) to be used by a declarant for authorised use of guarantee.<br />

- Where the guarantee reference number (GRN) is used by a declarant in his import declaration or this<br />

summary declaration <strong>and</strong> before the acceptance of this declaration, at least the following data shall be<br />

checked:<br />

o guarantee reference number (GRN),<br />

o access code (PIN),<br />

o declarant,<br />

o amount of guarantee,<br />

o goods listed in the individual guarantee in the form of single guarantee undertaking,<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for import regime or for temporary storage the guarantee reference number<br />

(GRN) of individual guarantee in the form of single guarantee undertaking shall be blocked for further<br />

use.<br />

4.2.2.3 Comprehensive guarantee<br />

- The guarantee undertaking for comprehensive guarantee shall be registered with a guarantee reference<br />

number (GRN) when the customs office of guarantee of Macedonian customs administration:<br />

o approves the guarantor to act as a guarantor for import regime or for temporary storage,<br />

o accepts the guarantee undertaking for comprehensive guarantee.<br />

Page 126/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The comprehensive guarantee shall be used for several import operations.<br />

- Where the customs office of guarantee of Macedonian customs administration accepts the guarantee<br />

undertaking for comprehensive guarantee <strong>and</strong> this guarantee undertaking for comprehensive guarantee is<br />

registered with a guarantee reference number (GRN), the customs office of guarantee shall issue:<br />

o decision on approval of the guarantor to act as a guarantor for import regime or for temporary<br />

storage,<br />

o decision on acceptance of guarantee undertaking for comprehensive guarantee (GRN),<br />

o form/way of notification of changes of access code(s) (PIN) to guarantee reference number to be<br />

used by a declarant for authorised use of guarantee.<br />

- Where the guarantee reference number (GRN) <strong>and</strong> access code (PIN) are used by a declarant in his<br />

import declaration or his summary declaration <strong>and</strong> before the acceptance of this declaration, at least the<br />

following data shall be checked:<br />

o guarantee reference number(s) (GRNs),<br />

o access code(s) (PINs),<br />

o declarant,<br />

o actual amount of reference amount of guarantee,<br />

o whether the guarantee is not blocked.<br />

- Where the goods are released for import regime or for temporary storage the amount of possible customs<br />

debt (calculated or estimated at the customs office of import) shall be debited from the actual amount of<br />

reference amount of comprehensive guarantee.<br />

- Where the actual amount of reference amount of comprehensive guarantee is not sufficient to cover the<br />

possible customs debt (calculated or estimated at the customs office of import) on declared goods, this<br />

comprehensive guarantee shall be blocked <strong>and</strong> this information shall be sent from the Guarantee<br />

management sub-application:<br />

o to the CDPS to inform the customs officer at the customs office of import,<br />

o via the CDPS to the declarant.<br />

- Where the import regime or the temporary storage has been discharged (i.e. the moment when the<br />

customs office of discharge is in a position to establish, on the basis of a comparison of the data available<br />

to this customs office <strong>and</strong> those available to the customs office of import, that the regime has ended<br />

correctly) the customs office of departure shall notify that to the customs office of guarantee with the<br />

request for release of a used guarantee. Based on this information the amount of possible customs debt<br />

(calculated or estimated at the customs office of import) shall be credited back to the actual amount of<br />

reference amount of comprehensive guarantee.<br />

- At any time the declarant shall have a possibility to:<br />

o change the accession code (PIN) of his comprehensive guarantee,<br />

o check the actual amount of reference amount of his comprehensive guarantee.<br />

- At any time the customs office of guarantee shall have a possibility to:<br />

o change the accession code (PIN) of comprehensive guarantee, based on the request of a declarant,<br />

o check the actual amount of reference amount of comprehensive guarantee,<br />

o monitor the changes of actual amount of reference amount of comprehensive guarantee.<br />

4.2.3 Electronic communication with Office of Guarantee<br />

- The electronic communication of a declarant with the customs office of guarantee regarding a<br />

comprehensive guarantee or individual guarantee in the form of single guarantee undertaking (e.g.<br />

management of PIN (access code) <strong>and</strong> use of comprehensive guarantee or individual guarantee) shall<br />

contain the following information/conditions to be automatically cross-checked:<br />

Page 127/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o registration number of authorisation, which shall be used for the cross-check of information from the<br />

electronic message,<br />

o holder of authorisation, which shall be used for the cross-check of information from box 14 of<br />

import declaration or summary declaration,<br />

o full address of the holder of Parameters of electronic communication, which shall be used for the<br />

cross-check of information from box 14 of import declaration or summary declaration,<br />

o registration number of Parameters of electronic communication,<br />

o customs office of guarantee or the list of customs offices of guarantee, where this authorisation is<br />

valid,<br />

o further information about the holder of authorisation (an ICT contact person <strong>and</strong> a Procedures<br />

contact person),<br />

o full text of the actual wording of authorisation,<br />

o history of the authorisation.<br />

4.3 Risk analysis <strong>and</strong> risk management system<br />

- The principle of customs control is the proper application of customs regulations <strong>and</strong> compliance with<br />

other legal <strong>and</strong> regulatory requirements, with maximum facilitation of international trade <strong>and</strong> travel.<br />

<strong>Customs</strong> controls should therefore be kept to the minimum necessary to meet the main objectives <strong>and</strong><br />

should be carried out on a selective basis using risk management techniques to the greatest extent<br />

possible.<br />

- Application of the principle of customs controls will allow Macedonian customs administrations to:<br />

o focus on high-risk areas <strong>and</strong> therefore ensure more effective use of available resources,<br />

o increase ability to detect offences <strong>and</strong> non-compliant traders <strong>and</strong> travellers,<br />

o offer compliant traders <strong>and</strong> travellers greater facilitation <strong>and</strong><br />

o expedite trade <strong>and</strong> travel.<br />

- The advantage of using information <strong>and</strong> communication technologies for customs control purposes is the<br />

ability to make information easily available to all authorised customs officials. Automation opens up the<br />

possibility of accessing information held on databases maintained by other law enforcement agencies,<br />

such as police records, immigration files, etc. The application of information <strong>and</strong> communication<br />

technologies also allows customs officials to assess various data, such as selectivity criteria, speedily <strong>and</strong><br />

accurately, in order to identify their usefulness <strong>and</strong> helps them to react quickly to changing<br />

circumstances.<br />

- In ensuring compliance with customs regulations, in order to make efficient use of scarce resources,<br />

customs administration must employ selectivity <strong>and</strong> risk assessment techniques. While these techniques<br />

are not necessarily dependent on information technology for their implementation, they cannot really be<br />

applied efficiently <strong>and</strong> consistently without it. In an automated environment the same selectivity <strong>and</strong> risk<br />

assessment principles can be applied to both goods <strong>and</strong> persons.<br />

- This part has be developed in close cooperation with the International Convention on the Simplification<br />

<strong>and</strong> Harmonisation of <strong>Customs</strong> Procedures 16 <strong>and</strong> the Guidelines to International Convention on the<br />

Simplification <strong>and</strong> Harmonisation of <strong>Customs</strong> Procedures 17 .<br />

-<br />

4.3.1 Risk management<br />

- Risk management is fundamental to the effective targeting of consignments for examination. Selectivity<br />

profiles are only as good as the information they contain. Regular review of profiles will tell customs<br />

officials which data elements <strong>and</strong> combinations of data elements have successfully detected noncompliant<br />

declarations. Analysis of the declaration information itself will also afford clues to trends <strong>and</strong><br />

identify potentially high-risk consignments.<br />

Page 128/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- The principal difference between international/national <strong>and</strong> local profiling is that international/national<br />

profiles are m<strong>and</strong>atory for all customs offices whereas local profiles only concern a single customs office<br />

or a small group of offices. However, information from local profiles should be used as part of the<br />

general risk analysis, <strong>and</strong> where appropriate, upgraded to national status. All profiles should be reviewed<br />

on a regular basis. For security purposes, steps should be taken to identify those authorised to change<br />

profiles, at both levels.<br />

4.3.2 Risk management within the customs authorities<br />

4.3.2.1 The context<br />

- Risk management within customs authorities can be strategic, operational or tactical. It should be<br />

remembered that the risk management process can apply across all of these levels.<br />

- Strategic risk management - by studying comprehensive information, <strong>Customs</strong> administrations can<br />

identify areas of risk, sift out those of minor importance, <strong>and</strong> intervene only where experienced <strong>and</strong><br />

practical judgement indicates it is necessary. Risk areas in the <strong>Customs</strong> context can include social issues<br />

(exclusion of drugs, pornography, etc.), import/export prohibitions <strong>and</strong> restrictions (e.g. CITES), public<br />

health, environment, commercial policy measures (e.g. IPR, GSP), quotas, <strong>and</strong> duty <strong>and</strong> tax issues.<br />

- Operational risk management - is the determination of the level of control necessary to deal effectively<br />

with the assessed risk. An example of this is determining the audit controls applied to an importer or<br />

how to deploy limited staff <strong>and</strong> equipment effectively. Using this approach the customs authority moves<br />

from being a "gatekeeper" checking every movement, to checking only selected movements which<br />

demonstrate the greatest risk.<br />

- Tactical risk management - is used by officers at their workplace in dealing with immediate situations.<br />

Using set procedures combined with intelligence, experience <strong>and</strong> skill, they decide which movements<br />

require greater controls.<br />

4.3.2.2 Selectivity, Profiling <strong>and</strong> Targeting<br />

- Selectivity, profiling <strong>and</strong> targeting are integral parts of risk management. Selectivity criteria for dutiable<br />

goods include the history of the importer, exporter, carrier, agent, etc., the origin <strong>and</strong> routing of the<br />

goods, <strong>and</strong> prohibitions or restrictions. Risk indicators are specified selectivity criteria such as: specific<br />

commodity code, country of origin, country whence consigned, licensing indicator, value, trader, level of<br />

compliance, type of means of transport, purpose of the stay in the customs territory, financial<br />

consequences, or financial situation of the trader/person.<br />

- This is the process that will determine whether or not a particular consignment or person needs looking<br />

at more closely. In an automated environment four selectivity filters can be applied, namely<br />

international, national <strong>and</strong> local profiles <strong>and</strong> a r<strong>and</strong>om selection system.<br />

- The system designer should be aware that for building up a set of profiles the system needs to be flexible<br />

<strong>and</strong> capable of h<strong>and</strong>ling not only simple individual data elements but relatively complicated<br />

combinations of data elements as well. Using combinations allows <strong>Customs</strong> authority to fine-tune its<br />

targeting capabilities. Thus, <strong>Customs</strong> authority might, for example, only want to select a particular<br />

commodity if it comes from a particular country <strong>and</strong> not if it comes from any other country. Annex 3 <strong>and</strong><br />

Annex 4 to this document outline the conceptual approach of a selectivity system (see Chapter 8).<br />

- The principal difference between international/national <strong>and</strong> local profiling is that international/national<br />

profiles are m<strong>and</strong>atory for all <strong>Customs</strong> offices whereas local profiles only concern a single <strong>Customs</strong><br />

office or a small group of offices. However, information from local profiles should be used as part of the<br />

general risk analysis, <strong>and</strong> where appropriate, upgraded to national status. All profiles should be reviewed<br />

on a regular basis. For security purposes, steps should be taken to identify those authorised to change<br />

profiles, at both levels. The r<strong>and</strong>om selection system uses an algorithm to select a declaration for further<br />

examination by <strong>Customs</strong>. It is also important for the system to allow for monitoring of the co-ordinated<br />

Page 129/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

interaction between the three levels of selectivity so that the overall target for examinations is not<br />

exceeded.<br />

- The system will also have to be designed to ensure that all the data go through the international/national<br />

profiles but only the declaration data relevant to a specific region or customs office go through the local<br />

profiles for that region or office. Facilities are often included to enable profiles to be switched off<br />

temporarily by authorised managers.<br />

- Risk profiling is the means by which customs authority puts risk management into practice. It replaces<br />

r<strong>and</strong>om examination of documents <strong>and</strong> goods with a planned <strong>and</strong> targeted working method, making<br />

maximum use of <strong>Customs</strong> resources. A risk profile is a document which can be set out in a number of<br />

ways but it should be comprehensive <strong>and</strong> relevant to the traffic throughput in a <strong>Customs</strong> office.<br />

- The risk profile should contain a description of the risk area, an assessment of the risk, the countermeasures<br />

to be taken, an action date, the results <strong>and</strong> an evaluation of the effectiveness of the action<br />

taken. A risk profile can be kept in a binder or on a local computer <strong>and</strong> it should be as accessible as<br />

possible to <strong>Customs</strong> officers. Once established, the profiles along with other information <strong>and</strong> intelligence<br />

will provide a basis for targeting potentially high risk movements of consignments, means of transport,<br />

or travellers.<br />

Quota kind of goods textiles under quota textiles under quota AND/OR<br />

GSP country of origin specific country of origin specific country of origin AND/OR<br />

CITES transport route unusual transport route - unusual transport route AND/OR<br />

Trader principal specific principal specific principal<br />

4.3.2.3 Evaluation <strong>and</strong> review<br />

- To remain effective any system of risk management has to test the assessment of previously identified<br />

risks <strong>and</strong> be flexible enough to reflect newly identified risks. Evaluation of the effectiveness of risk<br />

management should be undertaken regularly at all stages. The success rate is an important criterion for<br />

evaluating the effectiveness of the risk profiles.<br />

- Evaluation <strong>and</strong> review should be carried out by customs authorities through a regular compliance<br />

measurement process. Although the scope <strong>and</strong> methodologies of these reviews differ, their objective is to<br />

identify weaknesses in the control programme <strong>and</strong> to make recommendations for improvement.<br />

- Risk profiles should be reviewed at regular intervals to ensure that they are always up to date, <strong>and</strong> to rid<br />

the system of information that is no longer relevant. It is important also to retain an element of surprise<br />

by carrying out r<strong>and</strong>om checks, because companies that are in regular contact with <strong>Customs</strong> will be<br />

aware of profiling methods or sometimes the profiles themselves.<br />

- These r<strong>and</strong>om checks can also provide a cost effective means of identifying other types of risk <strong>and</strong> of<br />

monitoring or estimating their significance, or any changes in the risk pattern. Review <strong>and</strong> evaluation<br />

within the risk management process should be incorporated into a regular review procedure to measure,<br />

assess <strong>and</strong> evaluate the effectiveness of the overall <strong>Customs</strong> control programme <strong>and</strong> should take into<br />

account the findings of external government audits.<br />

4.3.2.4 Compliance Measurement Areas<br />

- Using the risk management programme, <strong>Customs</strong> should identify the priority areas to focus their<br />

resources. One approach is to consider that in some countries or economic unions, as much as 10% of<br />

the traders account for over 80% of the imports <strong>and</strong> exports. By focusing on the top 5-10% of these<br />

highest volume manufacturers, importers, exporters <strong>and</strong> commodities, <strong>Customs</strong> can ensure that those<br />

which have the most significant impact on the national economy are being reviewed most effectively.<br />

- The areas may include:<br />

Page 130/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

o Documentary issues:<br />

→ Proper tariff classification by traders,<br />

→ Proper valuation by traders,<br />

→ Country of origin.<br />

o Procedural issues :<br />

→ Importation <strong>and</strong> exportation (from the goods declaration through revenue collection),<br />

→ Transit operations,<br />

→ Warehousing, Free Trade Zones, <strong>Processing</strong>.<br />

o Revenue issues :<br />

→ Timely <strong>and</strong> accurate revenue payments,<br />

→ Proper posting of securities.<br />

o Transport issues :<br />

→ Accurate reporting of the quantity of goods,<br />

→ Accurate description of goods on the manifest <strong>and</strong>/or transport document,<br />

→ Accuracy of container quantities <strong>and</strong> identification numbers,<br />

→ Transporter compliance.<br />

o Specific concerns :<br />

→ Compliance by tariff number or range of tariff numbers,<br />

→ Public health <strong>and</strong> safety issues,<br />

→ Intellectual property rights <strong>and</strong> copyright issues,<br />

→ Compliance with trade agreements,<br />

→ Proper country of origin marking on goods,<br />

→ High revenue commodities,<br />

→ Selected traders.<br />

4.3.2.5 Use of information technology for effective implementation of Risk Management<br />

- The use of information technology is an effective tool for risk management. It enables a more rapid<br />

analysis of selectivity criteria than would be possible manually. Automation allows Macedonian customs<br />

administration to establish a national database of information on all transactions <strong>and</strong> movements which<br />

can be updated <strong>and</strong> used for rapid information sharing <strong>and</strong> identification of changing risk areas. It can<br />

also provide a database of all risk profiles which would form the basis for a selectivity module within an<br />

automated clearance system.<br />

- An automated system allows Macedonian customs administration to subject declarations to a series of<br />

selectivity filters to determine which declarations may require further examination. Such a system may<br />

direct claims to different routes.<br />

4.4 Tarim (TARIC)<br />

4.4.1 General conditions of Tarim (TARIC)<br />

- The online customs tariff database, also called the TARIC, is a multilingual database in which are<br />

integrated all measures relating to tariff, commercial <strong>and</strong> agricultural legislation. By integrating <strong>and</strong><br />

coding these measures, the TARIC secures their uniform application by all EU member states <strong>and</strong> gives<br />

all economic operators a clear view of all measures to be undertaken when importing or exporting<br />

goods. It also makes it possible to collect Community-wide statistics for the measures concerned.<br />

- The online customs tariff database which shall be developed for Macedonian customs administration,<br />

also called the Tarim, shall be a multilingual database in which shall be integrated all measures relating<br />

to tariff <strong>and</strong> commercial legislation. By integrating <strong>and</strong> coding these measures, the Tarim shall secure<br />

their uniform application by all Macedonian customs offices <strong>and</strong> gives all economic operators a clear<br />

view of all measures to be undertaken when importing or exporting goods.<br />

Page 131/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

4.4.2 Content of Tarim (TARIC)<br />

- The Tarim (TARIC) shall contain the following main categories of measures:<br />

o Tariff measures:<br />

→ Third country duty rates, as defined in the Combined Nomenclature<br />

→ Suspensions of duties;<br />

→ Tariff quotas; <strong>and</strong><br />

→ Tariff preferences.<br />

o Commercial measures:<br />

→ Antidumping measures; <strong>and</strong><br />

→ Countervailing duties measure.<br />

o Tax-tariff measures:<br />

→ information relating to the rates of VAT; <strong>and</strong><br />

→ information relating to the rates of excises.<br />

o Measures relating to restriction of movements:<br />

→ Import <strong>and</strong> export prohibitions;<br />

→ Import <strong>and</strong> export restrictions; <strong>and</strong><br />

→ Quantitative limits.<br />

o Measures for gathering of statistical data:<br />

→ Import surveillances;<br />

→ Export surveillance.<br />

4.4.3 Information flows<br />

- The following statements define the basic information flows which occur involving the Tarim (TARIC)<br />

system:<br />

o Combine Nomenclature, Quota <strong>and</strong> Suspensions deliver data to the Tarim (TARIC) system for<br />

integration purposes.<br />

o Tariff applications such as Accounting management system sub-application, Binding Tariff<br />

Information, Authorisation sub-application, Risk analysis <strong>and</strong> risk management system,<br />

Suspensions, Quota <strong>and</strong> Surveillance use Tarim (TARIC) as a reference data system in order to<br />

validate nomenclature codes, geographical areas or to retrieve a duty rate expression for a given<br />

nomenclature code.<br />

o All Macedonian customs offices shall receive on a daily basis all stable updates performed in the<br />

Tarim (TARIC) system.<br />

o A daily update file is sent to Data Dissemination <strong>System</strong> (to traders <strong>and</strong> associations).<br />

o Relevant Macedonian ministries (e.g. Ministry of Finances, including Public Revenue Office,<br />

National Bank of the RM, Ministry of Interior, Ministry of Agriculture, Forestry <strong>and</strong> Water Supply,<br />

Ministry of Health, Ministry of Environment <strong>and</strong> Physical Planning, Ministry of transport <strong>and</strong><br />

Communications, Ministry of Culture, Ministry of Economy, Directorate for Radiation Security,<br />

Institute for st<strong>and</strong>ardisation, State Statistical Office) shall receive Tarim (TARIC) data to populate<br />

their local databases.<br />

- Daily transmissions of Tarim (TARIC) data via an electronic network guarantee immediate <strong>and</strong> correct<br />

information for all Macedonian customs offices with the goal of maximising automatic customs<br />

clearance.<br />

- The same information is also disseminated towards third parties such as economic operators, national or<br />

international organisations, <strong>and</strong> trade associations. The Tarim (TARIC) database shall be available<br />

online on the website of Macedonian customs administration.<br />

Page 132/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

4.4.4 Business Process <strong>and</strong> Security Requirements<br />

- Data management = Central administration of Macedonian customs administration shall create <strong>and</strong><br />

maintain the Tarim (TARIC) data.<br />

- Data dissemination = A daily update file is produced <strong>and</strong> made available for all Macedonian customs<br />

offices, Data Dissemination <strong>System</strong> (to traders <strong>and</strong> associations) <strong>and</strong> other Macedonian ministries.<br />

- Data consultation = Other Macedonian ministries <strong>and</strong> applications consult the TARIC data.<br />

- Confidentiality = All parties within both the Central administration of Macedonian customs<br />

administration <strong>and</strong> all Macedonian customs offices must ensure that only legitimate users are able to<br />

gain access to the confidential Tarim (TARIC) data.<br />

4.5 Accounting management system sub-application<br />

4.5.1 General conditions of Accounting management system sub-application<br />

- The revenue collection is one of their primary functions. Therefore the automation of the revenue<br />

accounting process via Accounting management system sub-application is an essential part of any<br />

integrated <strong>Customs</strong> IT system <strong>and</strong> it should be closely connected with CDPS. The Accounting<br />

management system sub-application (revenue accounting system) must:<br />

o account for all duties collected <strong>and</strong> refunded;<br />

o provide a mechanism for the collection <strong>and</strong> refund of duties at the time of clearance;<br />

o provide a mechanism for the deferment of duty payments for a specified period.<br />

- The application of a deferred payments system requires the establishment of a trader registration system.<br />

This controls the guarantees <strong>and</strong> identifies the revenues payable over a specified period of time.<br />

- In the Accounting management system sub-application (revenue accounting system) the following tasks<br />

are ideally suited to the application of IT:<br />

o automated control of duty security, i.e. the communication with the Guarantee management subapplication;<br />

o maintenance of the traders' deferred payment accounts; <strong>and</strong><br />

o production of fast <strong>and</strong> accurate revenue accounts.<br />

- At the time of clearance, duty can be collected by accepting cash, cheques, bank drafts, credit cards <strong>and</strong><br />

debit cards from the declarant <strong>and</strong>/or by using real-time electronic funds transfer payment methods.<br />

- Macedonian <strong>Customs</strong> Authorities must be able to reconcile the actual duties collected with the total<br />

duties calculated by the CDPS (goods declaration system). Typically, the system should record the actual<br />

duty amounts collected for each transaction together with the MRN <strong>and</strong> the means of payment.<br />

Normally, the type of duty (customs duty, VAT, excise, export tax, etc.) with the corresponding amount<br />

is also recorded, thus allowing the Macedonian <strong>Customs</strong> Authorities to determine for each declaration<br />

how much duty is collected for each duty type.<br />

- The acceptance of payment cards means that Macedonian <strong>Customs</strong> Authorities shall install the necessary<br />

technology linking the <strong>Customs</strong> offices to the banking system, in order to validate the details on the card<br />

<strong>and</strong> ensure acceptance of the total duty amounts.<br />

- The application of a deferred payments system differs significantly from the collection of duty at the<br />

time of clearance. Such systems are based on maintaining individual accounting information for each<br />

approved declarant or trader. Normally, a maximum limit on deferred duty is agreed between the trader,<br />

Macedonian <strong>Customs</strong> Authorities <strong>and</strong> the trader’s bank through the issuing of a guarantee. Details of this<br />

amount, together with details of each transaction (MRN - <strong>Customs</strong> declaration number <strong>and</strong> duty<br />

payable), are maintained on a database, which is linked to the traders registration system. With the<br />

implementation of an automated revenue collection system, a national deferred payment system can be<br />

easily administered.<br />

Page 133/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

- Where information is exchanged electronically, the Accounting management system sub-application will<br />

send via the Guarantee management sub-application a response message to the trader indicating that<br />

duties cannot be deferred due to insufficient credit. The trader would normally be able to submit a<br />

request for information concerning the deferred account balance or a statement of the account.<br />

- When the duty becomes payable, the total amounts owed by each approved trader together with their<br />

bank account details (account number, branch sort code, etc.) should be transferred to the relevant bank.<br />

The question of agreement between Macedonian customs authorities <strong>and</strong> the banks on the information<br />

exchange st<strong>and</strong>ard <strong>and</strong> the medium (EDI, Internet, etc.) will need to be addressed. International st<strong>and</strong>ard<br />

messages designed for use in the EDI environment are available for the transmission of payment<br />

information.<br />

5. TECHNICAL REQUIREMENTS<br />

5.1 Introduction of concept <strong>and</strong> architecture<br />

The logical architecture of CDPS is with multiple tiers. It requires no client installation thus<br />

reducing the total cost of ownership. Such architecture works in various application scenarios <strong>and</strong><br />

deployment patterns. Consequently, the same CDPS application can be deployed in different<br />

environments such as production, testing, training <strong>and</strong> conformance testing environments. We<br />

recommend the use of a Centralised data repository. Recommended multi-tier logical architecture<br />

offers the following benefits: Logically organized code; Easier maintenance; Better reuse of code;<br />

Better team development experience; Higher clarity in coding; Manageability <strong>and</strong> maintainability;<br />

Works in various application scenarios <strong>and</strong> deployment patterns; Decoupled Presentation <strong>and</strong><br />

Business Logic facilitating scalability; Separate interface <strong>and</strong> business logic components allowing<br />

manageable <strong>and</strong> maintainable interfaces with external entities; The business logic in the Business<br />

Tier can be wrapped in a number of web services <strong>and</strong> thus made available to external clients;<br />

Addresses security considerations from the start <strong>and</strong> in-depth.<br />

More details on the proposed technical architecture can be found in the document “<strong>Customs</strong> <strong>Declaration</strong><br />

<strong>Processing</strong> <strong>System</strong>: Functional <strong>and</strong> Technical Architecture”.<br />

Requirements related to the Common Domain are of lower priority compared to the requirements related to<br />

the National <strong>and</strong> External Domain. Implementation of the Common Domain requirements can be postponed<br />

until prior to the accession of Macedonia to EU.<br />

5.2 General Technical Requirements<br />

This section provides an overview of the general technical requirements that have to be met by<br />

every software application which is part of CDPS.<br />

5.2.1 Networking Requirements<br />

This chapter provides the networking requirements for the CDPS whether it is developed,<br />

customised or a combination of both.<br />

Number Description<br />

NR-0000 The communication network(s) has to be sized by MCA <strong>and</strong> CDPS vendor to<br />

ensure the communication between HQ <strong>and</strong> BCOs <strong>and</strong> to meet the national<br />

performance requirements.<br />

NR-0001 The connection between the External Domain <strong>and</strong> the CDPS is recommended to<br />

be a direct connection (e.g. through direct line), or to use strong encryption <strong>and</strong><br />

authentication mechanism e.g. VPN through IPSec.<br />

Page 134/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

NR-0002<br />

Description<br />

All Regional <strong>Customs</strong> Offices, Inl<strong>and</strong> <strong>Customs</strong> Office, <strong>and</strong> Border Crossing<br />

Offices must be connected to the Internet via two communication links from two<br />

independent Internet providers<br />

Table 3: General networking requirements<br />

5.2.1.1 Common Domain<br />

Additionally, following requirements have to be satisfied regarding the connection to the Common<br />

Domain.<br />

Number Description<br />

GR-0010 MCA has to be connected to only one operational CCN Gateway in order to<br />

ensure a connection with CCN. It might be possible for MCA to foresee several<br />

operational Gateways for performance reasons. However, only one address<br />

should be used to point to the Gateways.<br />

GR-0020 CSI protocol has to be used for the business-to-business exchange of all<br />

messages.<br />

GR-0030<br />

GR-0040<br />

GR-0050<br />

GR-0060<br />

GR-0080<br />

GR-0090<br />

GR-0100<br />

GR-0110<br />

GR-0120<br />

GR-0130<br />

The hardware for installation of the CCN Gateway has to be provided by the EC.<br />

MCA can provide the national configuration information to the CCN Technical<br />

Centre (CCN/TC) for the generation <strong>and</strong> installation of the CCN Gateway<br />

installation files.<br />

The necessary network infrastructure has to be provided to ensure the<br />

communication between the CCN Gateway <strong>and</strong> the CDPS<br />

The connection between the CCN Gateway <strong>and</strong> the CDPS is recommended to be<br />

a direct connection (e.g. through LAN or direct line), or to use strong<br />

authentication CSI security services in order for the CDPS platform to be<br />

considered as trusted.<br />

When connected to the Common Domain Network, MCA must provide one<br />

network address (IP address) to the CCN Technical Centre (CCN/TC) <strong>and</strong> must<br />

conform to the logical address specification as defined in [A01], [A02], [A03],<br />

<strong>and</strong> [A04].<br />

A National Administration developing an NDCA has to obtain the CSI stack <strong>and</strong><br />

CSI APIs. These can be obtained from CCN/TC.<br />

A Backup ISDN connection to the CCN network, provided by CCN/TC, has to<br />

be available.<br />

A Backup CCN Gateway has to be online <strong>and</strong> connected to the LAN (in order to<br />

receive the replication <strong>and</strong> synchronisation updates of the X.500 Directory) <strong>and</strong><br />

available for manual switching.<br />

Every CCN Gateway has to be configured per MCA’s configuration files.<br />

Every CCN Gateway has to be configured to automatically send daily technical<br />

statistics on the Information Exchanges h<strong>and</strong>led. This has to be in line with the<br />

specifications defined in [A01], [A02], [A03], <strong>and</strong> [A04].<br />

Table 4: Networking requirements for Common Domain<br />

5.2.2 Modes of operation<br />

Information Exchanges can be performed for several reasons, namely for operational purposes, test<br />

purposes or training purposes.<br />

Number<br />

Description<br />

Page 135/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

GR-2000<br />

GR-2010<br />

GR-2020<br />

GR-2030<br />

Description<br />

CDPS has to support the existence of at least four environments:<br />

• One production environment<br />

• One test environment<br />

• One training environment<br />

• One conformance testing environment<br />

The production, test, training, <strong>and</strong> conformance testing environments must be<br />

logically disjoint. It is strongly advised that the production, test, training, <strong>and</strong><br />

conformance testing environments are physically disjoint.<br />

Test application <strong>and</strong> data, training application <strong>and</strong> data, conformance testing<br />

application <strong>and</strong> data, <strong>and</strong> production application <strong>and</strong> data must be separated<br />

from each other.<br />

It has to be possible to switch between the production, testing, training, <strong>and</strong><br />

conformance testing context.<br />

Table 5: General requirements for Operation Modes<br />

5.2.3 Globalisation <strong>and</strong> Localisation<br />

The requirements for globalisation, localisation, regional settings, <strong>and</strong> Unicode support are given in<br />

this section. The character sets <strong>and</strong> the Data Item conventions for e<strong>Customs</strong> systems that are<br />

defined explicitly in [A01], [A02], [A03], <strong>and</strong> [A04] are applicable to CDPS.<br />

Number<br />

GR-3000<br />

GR-3010<br />

GR-3020<br />

Description<br />

<strong>User</strong> interface must be in Macedonian language<br />

CDPS must support date, time, currency <strong>and</strong> number format, <strong>and</strong> other regional<br />

<strong>and</strong> cultural conventions in Republic of Macedonia<br />

CDPS has to support UTF-8 for XML messages.<br />

Table 6: General requirements for Regional Support.<br />

5.2.3.1 Common Domain<br />

Additionally, following requirements have to be satisfied regarding the connection to the Common<br />

Domain.<br />

GR-3030 CDPS has to support only UNOC as the default character set in all data-items<br />

(non-language sensitive text fields <strong>and</strong> numeric fields) in EDIFACT messages.<br />

GR-3040 CDPS has to support UNOC, UNOD or UNOF as the character set in all<br />

language-sensitive text fields in EDIFACT messages or UTF-8 for XML<br />

messages.<br />

GR-3050 CDPS has to be able to convert (transliterate) the character sets of the EDIFACT<br />

messages (namely UNOC, UNOD <strong>and</strong> UNOF) or XML messages (UTF-8) into<br />

the character set(s) used internally in CDPS.<br />

Table 7: Regional Support requirements related to Common Domain.<br />

5.2.4 Fallback <strong>and</strong> availability<br />

5.2.4.1 Overview<br />

There are three methods to increase the availability <strong>and</strong> reliability of CDPS<br />

• Redundant communication lines: In [R17] we suggested that for reliability reasons in the<br />

future all Regional <strong>Customs</strong> Offices, Inl<strong>and</strong> <strong>Customs</strong> Office, <strong>and</strong> Border Crossing Offices are<br />

given broadb<strong>and</strong> access to the Internet via two communication links from two independent<br />

Page 136/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Internet providers. In addition to the existing communication links (optical cables of<br />

Macedonian railway <strong>and</strong> Ministry of Interior Affairs, ADSL by Macedonian Telekom), the<br />

introduction of a second broadb<strong>and</strong> access to the Internet will become even more feasible <strong>and</strong><br />

economically justified with the near-future introduction of the WiMAX broadb<strong>and</strong> service. For<br />

security reasons, every <strong>Customs</strong> Office needs to be connected to the MCA Headquarters <strong>and</strong><br />

thus the central installation of CDPS via a VPN which uses IPSec tunnelling mode. The use of<br />

two independent Internet providers significantly reduces the probability of loss of connection<br />

between COs <strong>and</strong> HQ. Short-period losses of communication links from one Internet provider<br />

shall have no impact on the CDPS operations <strong>and</strong> shall not be noticed by the end users.<br />

Additional costs due to the existence of redundant communication links between COs <strong>and</strong> HQ<br />

will be more than compensated by the increased overall reliability of CDPS, <strong>and</strong> improved user<br />

experience <strong>and</strong> satisfaction. However, this method only affects the communications<br />

infrastructure, but does not add any additional technical or functional requirements for CDPS.<br />

Hence it does not increase the licensing <strong>and</strong> customisation costs for CDPS<br />

• Paper-based fall-back procedures: Fallback <strong>and</strong> recovery procedures must be also foreseen in<br />

order to minimise the period of the CDPS central installation unavailability. For the IT services<br />

which are considered to be time critical, organisational fallback solutions (alias Business<br />

continuity plan) must be defined <strong>and</strong> supported eventually by legislation. In the very rare cases<br />

where both communications links between a BCO <strong>and</strong> HQ are down for a significant period of<br />

time which is long enough to influence the normal operations of a BCO, a paper-based<br />

procedure needs to be at disposal to the customs officers. After the communications links have<br />

been restored, CDPS shall allow the end–users to enter the data from the paper-based procedure.<br />

• Offline working mode: Due to the high-availability requirement for CDPS, in [R17] we<br />

elaborated on the existence of an offline working mode for the BCOs with non-reliable<br />

communication links to the CDPS installation at the MCA HQ. A cut-down version of CDPS<br />

needs to be installed on a local server at each BCO. The local version of CDPS will implement<br />

only the functionality which is absolutely necessary to allow BCOs to continue the normal<br />

operations during the brief periods of lost connection to MCA HQ. In the online mode, the<br />

central server installation of CDPS is used over the Internet. For the off-line mode, a cut-down<br />

local installation of CDPS with Oracle DB personal edition is used. The offline mode can be<br />

used when an Internet access is not available. When in offline mode, CDPS still supports<br />

multiple users (from the same border crossing office). When the connection to the HQ is<br />

restored after a period of lost connection, the local copy of the database needs to synchronise<br />

with the central copy. This is a two-directional merge-type synchronisation. Synchronisation<br />

should be done as soon as possible in order to minimise the number of conflicts. However, data<br />

replication, data synchronisation, shared data ownership between BCOs <strong>and</strong> HQ, <strong>and</strong> the need<br />

for multiple installations of CDPS can significantly increase the development/customisation<br />

costs of CDPS, the maintenance costs of CDPS, <strong>and</strong> the architectural complexity of CDPS.<br />

Taking into account the advantages <strong>and</strong> drawbacks of the above three methods, with the aim to<br />

increase the reliability <strong>and</strong> availability of CDPS it is our recommendation to implement the first two<br />

methods only, namely: Redundant communication lines <strong>and</strong> Paper-based fall-back procedures. It is<br />

estimated that the additional costs for an offline working mode related to software development,<br />

customisation <strong>and</strong> maintenance will significantly outweigh the benefits in the form of increased<br />

availability.<br />

5.2.4.2 Requirements<br />

In order to ensure a proper h<strong>and</strong>ling of messages during downtimes, the necessary precautions have<br />

to be taken.<br />

Page 137/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

AR-0000<br />

AR-0010<br />

AR-0020<br />

AR-0030<br />

AR-0040<br />

AR-0050<br />

AR-0060<br />

AR-0070<br />

AR-0080<br />

AR-0090<br />

AR-0100<br />

AR-0110<br />

AR-0120<br />

Description<br />

In case CDPS fails or is shut down for maintenance, incoming messages must be<br />

queued.<br />

Immediate fallback to manual procedures is required for high-priority messages<br />

during CDPS downtime.<br />

MCA is responsible for providing the availability of the National network<br />

covering redundancy, resilience, recovery <strong>and</strong> performance aspects (according to<br />

the chosen availability level).<br />

It is recommended that a backup machine for the CDPS should be available for<br />

manual switching.<br />

It is recommended that all servers be protected against power failure<br />

(Uninterruptible Power Supply).<br />

CDPS must operate during opening hours of all COs it serves. It must also<br />

operate outside those hours to carry out processes for which no intervention by<br />

<strong>Customs</strong> Officers is required.<br />

The system should support at least 1000 simultaneous active user sessions (the<br />

number is based on the average number of customs officers at work at the same<br />

time <strong>and</strong> one third of the companies involved in the customs declaration<br />

process). It is required that the number of active session can be changed by<br />

means of a configurable parameter.<br />

CDPS data should be backed up daily, weekly <strong>and</strong> monthly. Data backups<br />

should be stored in a separate location at least 30 kms from the CDPS servers.<br />

CDPS must provide the capability for back up <strong>and</strong> recovery of data such that the<br />

back up operation can be either manually initiated by operations support staff or<br />

automatically performed at regular pre-determined basis as specified by the<br />

operation support staff.<br />

Data older than 5 years should be archived in a different database or different<br />

database scheme. MCA should have access to this data through the different<br />

reports included in CDPS.<br />

The system must be deployed on load balanced server architecture. There should<br />

be possibility for shutting down a server for maintenance reasons <strong>and</strong> in the same<br />

time to keep the system fully operational.<br />

The deployment architecture must be designed <strong>and</strong> managed so as to ensure<br />

continuity of service.<br />

Controls must exist to limit the impact of a Denial of Service attack mounted<br />

against any of the system resources.<br />

Table 8: General requirements for fallback <strong>and</strong> availability<br />

5.2.4.2.1Common Domain Specific Requirements<br />

This chapter provides the additional fallback <strong>and</strong> availability requirements for CDPS related to<br />

Common Domain. These requirements will need to be satisfied prior to the accession of Macedonia<br />

to EU.<br />

Number Description<br />

AR-0005 In case CDPS fails or is shut down for maintenance, incoming messages must be<br />

queued. The CCN Gateway must queue the Common Domain messages.<br />

AR-0130 In the event that it is known that an NCA is unavailable, all messages to be sent<br />

to that NCA will be stored on the CCN Gateway of the MCA or in CDPS.<br />

AR-0140 MCA is responsible for defining rules <strong>and</strong> conditions for the message exchange<br />

Page 138/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

Description<br />

between MCA <strong>and</strong> the Traders. This may or may not be supported by a National<br />

SLA.<br />

5.2.5 Security<br />

Table 9: Common Domain specific requirements for fallback <strong>and</strong> availability<br />

5.2.5.1 Overview<br />

5.2.5.1.1<strong>User</strong>s<br />

The users of the system should be divided on two groups – Internal <strong>User</strong>s <strong>and</strong> External <strong>User</strong>s.<br />

The internal users are the customs officers involved in the process of the customs clearance<br />

(National Domain). The internal users will be authenticated in the system by providing username<br />

<strong>and</strong> password. If in the future the internal users need to electronically sign or authorize a document,<br />

then they will need to be issued an electronic certificate. The electronic certificate can be used for<br />

user authentication too.<br />

The external users are the users from the External Domain, namely, declarants which lodge customs<br />

declaration electronically in the system, employees of other government agencies, or applications<br />

from economic operators <strong>and</strong> other government agencies which consume the web services provided<br />

by CDPS. The external users can be authenticated in the system with username <strong>and</strong> password,<br />

electronic certificate or both. It is up to MCA to decide which of afore mentioned approaches will<br />

be implemented in the system. The external user should connect to the system using a secure<br />

protocol e.g. HTTPS.<br />

Additional information for every system user can be kept in the system. At least user’s personal<br />

names <strong>and</strong> contact information should be required by the system for every user profile.<br />

A link should be established in the system between the external users that represent a juridical<br />

person (operator) <strong>and</strong> their respective juridical person (kept in the referential data module).<br />

A link should be established in the system between the internal users <strong>and</strong> their customs office <strong>and</strong><br />

department (also kept in the referential data module).<br />

There should be a possibility for activation / deactivation of a user profile. This will allow system<br />

administrators respectively to allow / forbid given user(s) to access the system.<br />

The usernames should be unique in the system. It should not be possible to have two different users<br />

(system users) with the same username no matter if they belong to the same or different domains.<br />

5.2.5.1.2Access Rights, Roles <strong>and</strong> Security<br />

The system should keep a list of predefined access rights (privileges) of <strong>Customs</strong> officers. For<br />

traders we have a authorisation for e-communication with customs authorities. Every access right<br />

allows the execution of a given operation or usage of a particular resource in the system. The<br />

system should hide the interface elements which lead to an execution of an operation (for example<br />

loading of data, executing a business process, saving data modifications <strong>and</strong> so on) when the user is<br />

not in the possession of the privilege responsible for that particular operation.<br />

The system should support manageable user roles of <strong>Customs</strong> officers. The roles are composed of<br />

access rights. A user with the corresponding access rights (system administrator) can add, delete<br />

<strong>and</strong> modify user roles. One or more roles should be assigned to every user in the system.<br />

The system will authorize a user to execute a given action or use particular data if the user is in a<br />

role that contains the access right defined (responsible) for this particular action or data.<br />

The authorization for the external users to use certain customs regimes or electronic certificates is<br />

decided based on information from the Authorization sub-application. The visibility of user<br />

interface elements <strong>and</strong> the possibility for execution of certain functions could also be realized with<br />

the access rights <strong>and</strong> user roles.<br />

Page 139/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

5.2.5.1.3Authentication <strong>and</strong> Digital Certificates<br />

As explained above, user authentication can be done with (i) username <strong>and</strong> password, <strong>and</strong> (ii)<br />

digital certificates.<br />

For the external domain it is strongly recommended that digital certificates are used for user<br />

authentication.<br />

<strong>User</strong>s from the external domain can use the same digital certificates for digital signatures too.<br />

Digital signatures prove the origin <strong>and</strong> integrity of data, <strong>and</strong> also provide non-repudiation security<br />

service. According to the Macedonian law [R18], digital signatures have the same validity as h<strong>and</strong>written<br />

signatures. Digital certificates need to be issued by a certified Certificates Issuing Authority,<br />

such as Komercijalna Banka AD Skopje, KIBS AD Skopje, AD Makedonski Telekomunikacii,<br />

GlobalSign, Verisign.<br />

Each user must sign a document which contains the public key from his/her digital certificate. Prior<br />

to any data exchange between CDPS <strong>and</strong> any application from the External Domain it is necessary<br />

that MCA <strong>and</strong> the partners from the External Domain exchange the public key from their digital<br />

certificates.<br />

The digital certificate must be stored on a tamper-proof security device from which it cannot be<br />

copied.<br />

5.2.5.2 Requirements<br />

This section highlights the security requirements for CDPS..<br />

Number<br />

SR-0010<br />

SR-0020<br />

SR-0030<br />

Description<br />

MCA must provide <strong>and</strong> guarantee the security of each CDSP module, e.g. by<br />

deploying firewalls.<br />

CDPS has to take the following security policies into account:<br />

• The IT <strong>and</strong> non-IT CDPS resources <strong>and</strong> assets must be protected from<br />

unauthorised access.<br />

• Precautions must be taken to ensure that confidential information is erased<br />

from CDPS applications <strong>and</strong> tools as soon as it is no longer required.<br />

• Controls should be implemented to ensure that information supplied to<br />

CDSP systems <strong>and</strong> tools is accurate <strong>and</strong> consistent with other information<br />

stored elsewhere in CDPS;<br />

• Data that is passed between two processing stages, does so without<br />

alteration, loss, or addition;<br />

• The CDPS architecture must be designed <strong>and</strong> managed so as to ensure<br />

continuity of service;<br />

• Controls must exist to limit the impact of a Denial of Service attack mounted<br />

against any CDPS resources;<br />

• Transit information should be exchanged only between entities that have<br />

been mutually authenticated;<br />

• Information that is exchanged should be protected from unauthorised<br />

disclosure, loss, or alteration.<br />

The requirements of particular importance concern (a) maintaining the<br />

confidentiality of confidential information regarding Trader <strong>and</strong> Guarantor<br />

relationships, (b) user identification <strong>and</strong> authentication information, <strong>and</strong> (c)<br />

information which may facilitate fraud.<br />

The following security policies, deduced from the [A07], are relevant:<br />

• All IT users must be uniquely identifiable;<br />

Page 140/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

SR-0045<br />

SR-0050<br />

SR-0060<br />

SR-0070<br />

Description<br />

• When challenged to do so by CDPS, IT users must confirm their identity;<br />

• Each CDPS workstation within a country should have a unique identity. This<br />

identity should be authenticated before an IT user is invited to complete the<br />

user authentication process;<br />

• Traders who use a DTI interface must first identify <strong>and</strong> authenticate<br />

themselves to CDOS just as <strong>Customs</strong> Officers do. Any new declarations they<br />

present or changes they make to existing ones must be attributable to them;<br />

• Precautions must be taken to ensure that it is not possible to eavesdrop on the<br />

user authentication dialogue between a workstation <strong>and</strong> the server such that<br />

an adversary could use the information to masquerade as an IT user;<br />

• Precautions should be taken to restrict the use of a Direct Trader Input (DTI)<br />

or CDPS workstation to only the person who has logged on;<br />

• Logical access controls should exist to ensure that Traders using DTI<br />

workstations can only access information related to them or their Principals;<br />

• IT users must have completed appropriate training before they are granted<br />

access to any CDPS resource.<br />

• The system should be able to restrict the visibility of registered customs<br />

declarations. The declarations should be visible only to the customs offices<br />

to which they refer. A customs officer can see only the declarations that are<br />

assigned to him/her.<br />

• There should be at least one user in every customs office which has the right<br />

to see all the declarations concerning the office <strong>and</strong> assign them to the other<br />

customs officers in his/her location.<br />

• If necessary a customs office may send a request to see a declaration which<br />

is not originally assigned to that office. The request is sent to the office<br />

where the declaration was originally lodged <strong>and</strong> it contains the MRN<br />

(Movement Reference Number) of the declaration. The declaration will<br />

become visible to the requesting customs office only if the request is<br />

approved by a user with special privileges (coordinator) in the addressed<br />

office (office of lodgment).<br />

• An external user can preview, modify, <strong>and</strong> cancel the declarations that are<br />

lodged from his user account only, or from users that represent the same<br />

operator (juridical person).<br />

If DTI facility is implemented, logical Access Control must be set up so that<br />

<strong>Customs</strong> Officers can logon from a DTI Trader Workstation but with restricted<br />

functionality only.<br />

Access Control Lists must be implemented up to application level in order to<br />

provide to <strong>Customs</strong> Officers read-access to any movement <strong>and</strong> full access to<br />

those movements <strong>and</strong> reference information in accordance with the MCA access<br />

policy for which they are authorised.<br />

The use of magnetic or optic media should be controlled or prevented e.g. by<br />

storing the users’ credentials, <strong>and</strong> by checking them online when such media are<br />

used.<br />

Page 141/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

SR-0080<br />

SR-0090<br />

SR-0100<br />

SR-0105<br />

SR-0110<br />

SR-0120<br />

SR-0130<br />

SR-0200<br />

SR-0210<br />

SR-0220<br />

SR-0230<br />

SR-0240<br />

SR-0270<br />

SR-0280<br />

SR-0300<br />

SR-0310<br />

SR-0320<br />

SR-0330<br />

SR-0340<br />

SR-0350<br />

Description<br />

It must be possible for MCA to define <strong>User</strong> Access Policies according to<br />

functional rules.<br />

All security relevant events must be audited.<br />

The time st<strong>and</strong>ard used for auditing is Greenwich Mean Time.<br />

CDPS must address the requirements to maintain an audit trail of all changes to<br />

data based on user requests. Proper logs should be maintained in a secure<br />

manner for audit of transactions recorded, changes made to data <strong>and</strong> queries<br />

initiated against end-user request with timestamps to enable examination of the<br />

audit trail at a later date. In addition, CDPS must provide the functionality for<br />

secure management <strong>and</strong> access to log files maintained on-line <strong>and</strong> off-line.<br />

Workstations must be capable of being uniquely identified.<br />

A listing (report) must be maintained including all MCA Workstation IP<br />

addresses, their software revision <strong>and</strong> the group they belong to.<br />

A listing (report) should be maintained including all system users, their access<br />

profile, Workstation <strong>and</strong> Workstation group.<br />

A firewall should be put in place between the MCA <strong>and</strong> the public network (e.g.<br />

between the DTI Trader connections <strong>and</strong> the MCA Server).<br />

<strong>User</strong> identification, user authentication, Workstation identification <strong>and</strong> access<br />

control procedures should be implemented between the MCA server <strong>and</strong> the<br />

Workstation components.<br />

The NCA server should terminate the connection of a Workstation after a period<br />

of inactivity defined in a configuration parameter.<br />

It is recommended that only one login shall be necessary for a <strong>User</strong> to access the<br />

different CDPS applications when pertaining to the same access rights.<br />

IT <strong>User</strong>s must be identified (as a minimum) using user names <strong>and</strong> authenticated<br />

using passwords.<br />

The MCA Domain Administrator should be able to configure the events which<br />

need to be audited in the MCA server.<br />

Duplicate CDPS messages, including acknowledgements, should be logged,<br />

brought to the attention of the <strong>System</strong> Administrator <strong>and</strong> discarded.<br />

The files downloaded from Internet must be virus checked.<br />

CDPS must address the requirement for providing multiple levels of access to<br />

system functionality based on roles assigned to both the MCA IT staff <strong>and</strong> endusers<br />

at any point in time. In addition, CDPS must support the functionality to<br />

grant <strong>and</strong> revoke both permissions <strong>and</strong> authorizations to end-users in a secure<br />

traceable environment.<br />

CDPS must address the need for securing <strong>and</strong> safeguarding of data through<br />

logging of ALL modifications to sensitive data<br />

CDPS must provide the functionality for role-based security <strong>and</strong> access to data<br />

<strong>and</strong> system functionality as well as guard against unauthorized use, copying <strong>and</strong><br />

transmission of data maintained in the database.<br />

Role-based security must be an integral part of CDPS <strong>and</strong> must include an<br />

administration component for updating <strong>and</strong> controlling access to individual subsystems<br />

<strong>and</strong> potentially to data within the database.<br />

By addressing the above requirements, CDPS must reduce to the absolute<br />

minimum the need by MCA IT staff to directly access the database tables using<br />

database utilities.<br />

Page 142/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

SR-0360<br />

SR-0370<br />

SR-0380<br />

SR-0390<br />

SR-0370<br />

SR-0380<br />

SR-0390<br />

SR-0395<br />

Description<br />

CDPS shall support the use of digital certificates for user authentication. CDPS<br />

shall keep a copy of the public keys of such digital certificates in its own<br />

repository.<br />

CDPS shall support the creation <strong>and</strong> verification of digital signatures based on<br />

the use of digital certificates.<br />

CDPS shall check the validity of digital certificates:<br />

• Check if the certificate is issued by an authorized Certificates Issuing<br />

Authority.<br />

• Check if the certificate has not expired.<br />

• Check if the certificate has not been revoked.<br />

CDPS shall keep a copy of public keys of expired digital certificates. This will<br />

allow for verification of digital signatures calculated in the past when the digital<br />

certificate was still valid.<br />

The system should lock a user account if 3 consecutive unsuccessful<br />

authentication attempts are made (wrong password was submitted for 3<br />

consecutive times). The user should not be able to log in the system when its<br />

account is locked. The account should be locked for a given period (at least 30<br />

minutes) of time <strong>and</strong> can be unlocked before this period only by user with<br />

special access rights (system administrator). There should be a possibility for<br />

configuring the locking period through a system configuration parameter.<br />

For security reasons user passwords should expire in a given period of time. The<br />

expiration period should be configured through a system configuration<br />

parameter. The user should not be able to log in the system if the password is<br />

expired. The system should prompt the user to change its password if it is<br />

expired. The system should not allow the user to reuse its previous passwords.<br />

<strong>User</strong> passwords shall satisfy minimum complexity requirements. For example,<br />

user passwords should be at least 6 characters long <strong>and</strong> should contain at least<br />

one digit or a non-alphanumeric character.<br />

CDPS must support single sign-on technology through LDAP (Lightweight<br />

Directory Access Protocol) communication with the Active Directory already<br />

implemented within MCA.<br />

Table 10: General security requirements<br />

5.2.5.2.1Common Domain Specific Requirements<br />

This chapter provides the additional security requirements for CDPS related to Common Domain.<br />

These requirements will need to be satisfied prior to the accession of Macedonia to EU. Security<br />

requirements should be implemented as recommended in the [A07]<br />

Number<br />

Description<br />

SR-0400 The “Security Policy Document” [A07] principles must be implemented.<br />

SR-0410 If a National Host is connected to a public network, a firewall should be put in<br />

place.<br />

SR-0420 Strong authentication CSI service should be used for the connection between a<br />

National Host <strong>and</strong> the CCN/CSI Gateway if it occurs through a public network<br />

<strong>and</strong> no firewall is used.<br />

SR-0430 In compliance with the DDNA (i.e. DDCOM, DDNTA, DDNXA, <strong>and</strong> DDNIA)<br />

specifications, all Common Domain messages must be acknowledged by their<br />

corresponding answer message or by an acknowledgement message.<br />

SR-0440 The NDI-WS workstation (internet workstation) must be physically<br />

Page 143/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

Description<br />

disconnected from the NCA network <strong>and</strong> files downloaded from Internet must<br />

be virus checked.<br />

Table 11: Common Domain related security requirements<br />

5.2.6 Other – Supporting Services<br />

Some other actions have to be taken by MCA to ensure the correct operation of CDPS.<br />

Number<br />

UR-000<br />

UR-0010<br />

UR-0020<br />

Description<br />

A National Help Desk infrastructure providing follow-up <strong>and</strong> tracking must be<br />

set up for <strong>Customs</strong> Officers.<br />

CDPS must provide an integrated online context-sensitive ‘Help’ feature. In<br />

addition, the “Help” feature must be designed <strong>and</strong> implemented to allow Subject<br />

Matter Experts to access, edit <strong>and</strong> update the help screens in Macedonian<br />

language <strong>and</strong> relate the help message to applicable business rules so that when<br />

the business rules change, the need to update the relevant help messages can be<br />

easily identified.<br />

All documentation produced to design, develop, deploy, implement <strong>and</strong> support<br />

CDPS forms part of the solution <strong>and</strong> the MCA must have free <strong>and</strong> unfettered<br />

access to it for its own use. This is to allow the MCA to assume responsibility<br />

for making or for outsourcing modification/enhancements to CDPS, thereby<br />

eliminating dependency on external vendors.<br />

Table 12: Other General requirements<br />

5.2.7 Data Warehouse <strong>and</strong> Reporting<br />

This section details the technical <strong>and</strong> functional requirements for the CDPS-related Data Warehouse<br />

that needs to be implemented for MCA. It is desirable that a data warehouse is built as part of the<br />

CDPS.<br />

Number Description<br />

DW-0010 DWS must not affect the response time of the TPS.<br />

DWS has to perform its processors/disks/database tasks associated with querying<br />

<strong>and</strong> reporting on servers/disks/databases not used by the CDPS transaction<br />

processing systems.<br />

DW-0020 DWS should use data models that speed up <strong>and</strong> optimise querying <strong>and</strong> reporting<br />

tasks. It is expected that these data models will be different from the data models<br />

in the CDPS TPS.<br />

DW-0030 DWS shall use server <strong>and</strong> database technologies that speed up processing of<br />

queries <strong>and</strong> reports such as bit-mapped indexing, <strong>and</strong> shall not use database<br />

technologies which are optimised for TPS such as transaction recovery.<br />

DW-0040 DWS shall provide an environment where a relatively small amount of<br />

knowledge of the technical aspects of database technology is required to write<br />

<strong>and</strong> maintain queries <strong>and</strong> reports <strong>and</strong>/or to provide a means to speed up the<br />

writing <strong>and</strong> maintaining of queries <strong>and</strong> reports by MCA’s IT staff.<br />

DW-0050 DWS shall aggregate (e.g. extract, transform, <strong>and</strong> load) data from CDPS, other<br />

MCA’s TPSs, <strong>and</strong> external data sources, <strong>and</strong> shall thus make it easier to query<br />

<strong>and</strong> report from such data on a regular basis.<br />

DW-0060 DWS shall provide a repository for data from a longer time period than can<br />

efficiently be held in a TPS, <strong>and</strong> can allow for execution of queries <strong>and</strong><br />

Page 144/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number Description<br />

generation of reports on historical data. If required for performance reasons, then<br />

older data shall be periodically purged from TPS. For querying <strong>and</strong> reporting,<br />

this purged data <strong>and</strong> the current data shall be stored in the data warehouse where<br />

the requirements for the response time are much more relaxed.<br />

DW-0070 For security reasons, DWS shall prevent users who only need to execute queries<br />

<strong>and</strong> generate reports from having any access to the TPS in CDPS.<br />

DW-0080 Ad-hoc reporting: CDPS must address the functionality for reporting, based on<br />

selection of one or many fields found on any of the <strong>User</strong> Interfaces <strong>and</strong> must<br />

include options for on-line <strong>and</strong> off-line generation of reports. This functionality<br />

must be supported through the use of a versatile Report Writer that can be used<br />

by a non-technical user.<br />

DW-0090 CDPS shall also provide a number of predefined frequently used reports in the<br />

customs domain.<br />

DW-0100 CDPS shall provide the ability to maintain a library of user-defined on-line<br />

(screen-based) <strong>and</strong> batch-printed reports with pre-stored selection parameters<br />

that can be run without change, <strong>and</strong>/or modified as required when running a<br />

report.<br />

DW-0110 Reports will be available in a variety of formats: Portable Data Format (PDF),<br />

Postscript (PS), MS Word, <strong>and</strong> MS Excel at the very least.<br />

DW-0120 If CDPS allows a user to perform a query <strong>and</strong> view the results, then CDPS will<br />

also allow the user to generate a report from the results, <strong>and</strong> to download the<br />

result or the report.<br />

DW-0130 Reports General: CDPS should have the ability to report on all data entered into<br />

the system <strong>and</strong> should be highly flexible <strong>and</strong> user-friendly with the capacity to<br />

restrict access to reports according to user permissions<br />

DW-0140 Use Reports: CDPS should have the ability to display report output on the screen<br />

along with a view of a summary. CDPS should have ability to enter parameter/s<br />

to filter reports on one or more fields/columns together with the capability to sort<br />

reports on one or more fields/columns.<br />

Table 13: Data Warehouse requirements<br />

5.2.8 Technical Architecture<br />

CDPS must address the MCA’s requirement for an n-tier web-enabled application architecture.<br />

With an n-tier architecture, the MCA will have the flexibility it needs to deploy its IT infrastructure<br />

<strong>and</strong> human resources more optimally <strong>and</strong> overcome the limitations of the Client-Server<br />

architecture. Through streamlining <strong>and</strong> consolidating its operations at the central site, the MCA IT<br />

Department will increase its capacity to provide better service to its internal <strong>and</strong> external clientbase.<br />

CDPS must, therefore, address <strong>and</strong> meet the following requirements regarding its technical<br />

architecture.<br />

Number Description<br />

TA-0010 SOA. CDPS must be based on a Service- Oriented Architecture (SOA) to lay the<br />

foundation for the building of a robust, extensible, reusable components-based<br />

application architecture that is easy to maintain <strong>and</strong> support.<br />

TA-0020 n-tier web enabled application. CDPS must be a web enabled n-tier based<br />

application system. CDPS must be highly scalable.<br />

TA-0030 Separation of data logic from process logic. CDPS must address the<br />

requirement of separation of data <strong>and</strong> process logic to ensure reuse of<br />

components <strong>and</strong> consistent application of business rules across processes in<br />

Page 145/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

TA-0040<br />

TA-0050<br />

TA-0060<br />

Description<br />

order to ensure integrity of data <strong>and</strong> consistency in application of business rules.<br />

This should greatly simplify the maintenance of the system as well as increase<br />

MCA’s ability to respond effectively <strong>and</strong> in a timely manner to user initiated<br />

change requests in response to changes in customs law, policies <strong>and</strong> practices.<br />

Physical independence. CDPS must address the need for increasing the reach<br />

<strong>and</strong> range of the application system irrespective of where the system is<br />

physically located so as to permit two way access to/from external financial<br />

institutions, governmental institutions <strong>and</strong> citizens, irrespective of their physical<br />

location.<br />

Modularity <strong>and</strong> flexibility in making enhancement. CDPS must address the<br />

requirement for a components-based modular system design so as to provide the<br />

MCA the capability to enhance the system to keep up with changing rules <strong>and</strong><br />

procedures.<br />

Data consolidation <strong>and</strong> processing. CDPS must ensure that all data is stored in<br />

a database ensuring that there is no redundant data (i.e. normalized database<br />

schema) in order to simplify data access <strong>and</strong> provide a consolidated logical view<br />

of data, regardless of the organization <strong>and</strong> location of the financial information.<br />

As a result, data processing will be more accurate, consistent <strong>and</strong> timely,<br />

avoiding redundancy <strong>and</strong> increasing processing efficiency.<br />

Table 14: Technical Architecture requirements.<br />

5.2.9 Operating Environment<br />

CDPS will operate within the following environment in MCA.<br />

Number Description<br />

OE-0000 Estimated Transaction Volumes: There will be approximately 2000 MCA<br />

users of CDPS. There will be around 1000 MCA users concurrently accessing<br />

CDPS. It is anticipated that over the next few years the number of users could<br />

increase. CDPS usage patterns vary based upon the hour in the day <strong>and</strong> the<br />

month of the year (see Figure 1 <strong>and</strong> Figure 2). The following information<br />

provides some very broad volumetric for peak <strong>and</strong> average processing days:<br />

• Daily CDPS transactions peak at around 2pm to 4pm. During the peak<br />

hour the number of transactions reaches on average 190 SAD transactions<br />

per hour <strong>and</strong> 184 transit transactions per hour.<br />

• The average amount of daily transactions is: 1178 SAD transactions per<br />

day <strong>and</strong> 1420 transit transactions per day.<br />

Note: The above estimates for the transaction volumes are based upon the<br />

historical data available for the period January-July 2008.<br />

OE-0010 Communication Links to BCOs: MCA will use a VPN system to connect the<br />

BCOs to CDPS Servers running at Headquarters. All BCOs shall be connected<br />

with the MCA Headquarters by two Internet links provided by two independent<br />

Internet providers. The speed of these lines will vary, but the slowest lines shall<br />

be at least 256 Kbps.<br />

OE-0020 Server Hardware Platform: Currently, MCA does not have servers which can<br />

be used to run CDPS. CDPS server(s) has to be sized by MCA <strong>and</strong> CDPS<br />

vendor to meet the performance requirements of CDPS. The vendor must<br />

specify the technical requirements for the recommended hardware for the servers<br />

<strong>and</strong> other resources:<br />

• Processors, hard disks, backup devices per server.<br />

Page 146/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

OE-0030<br />

OE-0040<br />

Description<br />

• Connection between servers<br />

• Communications equipment <strong>and</strong> links between servers <strong>and</strong> between<br />

servers <strong>and</strong> workstations (routers, firewalls etc.).<br />

Server Software Platform: The CDPS vendor must also specify the system<br />

software, infrastructure software (RDBMS, applications server, web server) <strong>and</strong><br />

other third-party software required by CDPS. The vendor must propose an<br />

optimal licensing structure for all third-party software required by CDPS.<br />

Workstation hardware <strong>and</strong> software platform: CDPS Workstation(s) has to<br />

be sized by MCA <strong>and</strong> CDPS vendor to meet the national performance<br />

requirements. All MCA workstations shall run on the Windows XP operating<br />

system <strong>and</strong> above. Internet Explorer 7 will be installed on all MCA<br />

Workstations, but CDPS will also have to support Mozilla Firefox 2 <strong>and</strong> above.<br />

Display resolution will be at least 1024 by 768 pixels with 32bit colour quality.<br />

Minimum processor is 1GHz Celeron. Minimum RAM is 512MB. Minimum<br />

free hard disk space is 10GB.<br />

Note: Currently, MCA does not have a st<strong>and</strong>ard operating environment for its<br />

workstations. Workstations’ operating system varies from Windows 98 to<br />

Windows Vista, though Windows XP is the most used OS. CPUs range from P-<br />

II to Pentium Dual Core. RAM memory ranges from 32MB to 1GB. MCA shall<br />

st<strong>and</strong>ardise its operating environment as per the above paragraph.<br />

Table 15: Operating Environment requirements.<br />

200<br />

180<br />

160<br />

140<br />

120<br />

100<br />

80<br />

60<br />

Apr<br />

Feb<br />

Jan<br />

Jul<br />

Jun<br />

Mar<br />

May<br />

40<br />

20<br />

0<br />

0 5 10 15 20<br />

Figure 1: Average number of transit transactions per hour in a day per month<br />

Page 147/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

200<br />

180<br />

160<br />

140<br />

120<br />

100<br />

80<br />

60<br />

Apr<br />

Feb<br />

Jan<br />

Jul<br />

Jun<br />

Mar<br />

May<br />

40<br />

20<br />

0<br />

0 5 10 15 20<br />

Figure 2: Average number of SAD transactions per hour in a day per month<br />

5.2.10 Version management <strong>and</strong> work packages<br />

CDPS needs to support the concept of a “work package”. A work package allows the user to have<br />

work in progress in isolation from the “current” public information. It is a user decision when this<br />

work in progress is made available as public information by applying the work package. Thus, a<br />

user (or a set of users) can prepare work over a longer period without being visible to users not<br />

involved in this work.<br />

A work package provides the required infrastructure to maintain historical versions of business data.<br />

Each work package consolidates a single version of the manipulated business items in the package.<br />

The version applied by the last work package becomes the “current” version for public access while<br />

all other applied versions are maintained in a historical storage area.<br />

Number Description<br />

WP-0000 All manipulations of the business data (inserting, deleting or updating) are done<br />

in the context of a work package. These manipulations only become visible to<br />

non-involved users at the moment the work package is applied. In order to<br />

manipulate business date one must have selected a work package in which this<br />

manipulation will occur. Four main operations on a work package can be<br />

identified:<br />

• Creating a new work package. This introduces a new package that can<br />

initially be used by the creator of the package. The work package is given<br />

a name, is persistently stored in the system <strong>and</strong> can be used in future<br />

operations.<br />

• Selecting an existing work package. In order to manipulate business data a<br />

work package must be selected. A manipulation can be the insertion of a<br />

Page 148/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

Description<br />

new business item, the modification of an existing item or the deletion of<br />

an existing item.<br />

• Applying a work package. Applying a work package means that all<br />

business data modifications are made public. Everybody can see the<br />

content from this moment on. The timestamp <strong>and</strong> the identity used when<br />

the work package is applied is persistently stored. An applied work<br />

package cannot be altered or removed.<br />

• Cancelling a work package. This operation actually removes all business<br />

modifications done in the context of the package together with the package<br />

itself. Cancel is a complementary operation to apply. One can execute a<br />

cancel or an apply operation <strong>and</strong> an applied package cannot be cancelled<br />

<strong>and</strong> vice versa.<br />

Table 16: Work Package requirements.<br />

5.2.11 <strong>User</strong> Interface<br />

CDPS can provide two different kinds of interactive interface. The first is a web interface based on<br />

HyperText Markup Language (HTML) i.e a thin client, <strong>and</strong> Server side processing of HTTP<br />

requests. The second is a thick client with rich graphical user interface, <strong>and</strong> a significant client –side<br />

data processing.<br />

If a web interface is deployed, then the latest version is always used. However, in some cases, a web<br />

interface may be relatively poor <strong>and</strong> its interactivity may be insufficient. Moreover, this kind of<br />

interface often requires a lot of b<strong>and</strong>width since the client, typically a web browser, must interacts<br />

with the server for each user operation. If CDPS uses Web interface, then CDPS must make<br />

extensive use of AJAX.<br />

Using a thick client may have the following benefits<br />

• A more interactive user interface<br />

• Lower b<strong>and</strong>width requirements. The application does not go to the server for each user<br />

interaction;<br />

• In some cases, the application can be used off-line.<br />

The trade-off is that the application <strong>and</strong> all its future releases must be deployed to all client<br />

workstations.<br />

Number Description<br />

UI-0000 There should be consistent on-screen presentation across all software modules<br />

<strong>and</strong> functions<br />

UI-0005 Configurability: CDPS should provide support for its configuration. CCDPS<br />

should provide a configuration tool that will allow users with administrative<br />

privileges to manage the appearance of forms, reports, labels <strong>and</strong> other UI<br />

elements.<br />

UI-0010<br />

UI-0015<br />

UI-0020<br />

UI-0030<br />

Configuration tool should be usable for translation of UI into another language.<br />

CDPS must provide look-up functionality, whereby the system displays<br />

matching data records from which the user may make selections; <strong>and</strong> the ability<br />

to set up <strong>and</strong> perform key word searching.<br />

CDPS must support keyboard shortcuts for navigation <strong>and</strong> functionality. CDPS<br />

must provide the ability to use function/menu ‘hot keys’ to bypass the menu<br />

structure <strong>and</strong> then return to original area the user was in.<br />

CDPS should provide the ability to tailor menus <strong>and</strong> screens to remove options<br />

for specific users or change terminology globally;<br />

Page 149/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

UI-0040<br />

UI-0050<br />

UI-0060<br />

UI-0070<br />

UI-0080<br />

UI-0090<br />

UI-0100<br />

UI-0110<br />

UI-0120<br />

UI-0130<br />

Description<br />

CDPS should provide menu navigation <strong>and</strong> support for pointing devices e.g.<br />

mouse.<br />

Screen presentation must have a consistent look <strong>and</strong> feel across all software<br />

modules <strong>and</strong> functions.<br />

CDPS must provide tool-tip descriptions when scrolling over icons.<br />

CDPS should ensure no loss of user filtering when navigating forward <strong>and</strong><br />

backward.<br />

CDPS should ensure no loss of user entered data when navigating forward <strong>and</strong><br />

backward.<br />

CDPS should ensure no loss of user sorting when navigating forward <strong>and</strong><br />

backward.<br />

CDPS must have the ability, following validation of a fields contents, to place<br />

the cursor in field which failed validation.<br />

CDPS should have the ability to filter data listed on the screen by any column.<br />

CDPS should have the ability to sort data listed on the screen by any column in<br />

ascending/descending order.<br />

Graphical <strong>User</strong> Interface (GUI) should comply with W3C st<strong>and</strong>ards.<br />

5.3 CDPS Requirements<br />

Table 17: <strong>User</strong> Interface requirements.<br />

5.3.1 Introduction<br />

CDPS defines various network domains. These include the External Domain, the National Domain<br />

<strong>and</strong> the Common Domain. The CDPS vision includes the intercommunication with the Common<br />

Domain, other relevant applications from the National Domain <strong>and</strong> the relevant applications from<br />

the External Domain.<br />

The Common Domain consists of a closed secured network called the Common Communications<br />

Network (CCN). It enables the different applications to communicate with one another in a secured<br />

environment. Access to the CCN is achieved through the CCN Gateways using primarily the<br />

Common <strong>System</strong>s Interface (CSI) protocol.<br />

MCA use its own national network for links between its customs offices. MCA is responsible for<br />

the national domain network, including its security.<br />

The external domain consists of the economic operators <strong>and</strong> the government agencies. Larger EOs<br />

have EDI connections, where smaller EOs have other means of communication (often referred to as<br />

Direct Trader Input - DTI). This could be for example an Internet connection.<br />

Following figure illustrates the various domains related to or in use in the CDPS.<br />

Page 150/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Figure 3: Network Domains<br />

This section defines the Infrastructure Communication Channels (ICC) though which the systems<br />

shall exchange information. The definition of ICCs was based on the business requirements for<br />

exchanging information among the systems. These business requirements are expressed through the<br />

“Business Communication Channels” (BCC). Since the interactions among the systems may be lot,<br />

CDPS <strong>System</strong> Integration is presented per system by defining its BCC <strong>and</strong> ICC with the other<br />

systems.<br />

5.3.2 Integration Architecture<br />

In [R16] we proposed the existence of a separate integration tier in the logical architecture of<br />

CDPS. Integration tier is separate from the implementation of the other tiers: integration with<br />

additional software systems from the Common, National or External Domain, <strong>and</strong> removal of<br />

existing integration with software systems will have no implications on the implementations of the<br />

other tiers. For sake of completeness, here we reproduce the diagram from [R16] which gives a<br />

more detailed presentation of the Data Integration Tier.<br />

Page 151/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

External <strong>System</strong>s<br />

Data Integration Tier<br />

Service Interface<br />

Service Interfaces<br />

Integration Service Gateways<br />

Service<br />

Gateways<br />

MQ Series<br />

CCN/CSI<br />

Web<br />

Service<br />

WS Client CCN/CSI<br />

MQ Series<br />

Integration Tier<br />

Data<br />

Aggregation<br />

Data Integration<br />

BC<br />

Integration Connectors<br />

Web<br />

MQ Series<br />

Service<br />

Data Integration<br />

Components<br />

Entity<br />

Translators<br />

Configuration<br />

Components<br />

Data Persistence Tier<br />

Figure 4. Logical architecture – Data Integration Tier.<br />

Though the above diagram of the Integration Tier allows for existence of multiple integration<br />

connectors (MQ Series, Web Service, CCN/CSI) we expect <strong>and</strong> recommend that Web Services<br />

shall be the dominant mechanism for communication between CDPS <strong>and</strong> applications from the<br />

National Domain, <strong>and</strong> the External Domain.<br />

Number Description<br />

IA-0000 CDPs shall have a separate Integration Tier which shall isolate the internal logic<br />

of CDPS from other software applications that CDPS needs to integrate with.<br />

IA-0010 Technical requirements for the SOAP protocol are as follows:<br />

IA-0020<br />

IA-0030<br />

• SOAP version 1.2<br />

• Support for SSL an HTTPS protocols<br />

• Support for WSDL files<br />

All web services, both the ones implemented in CDPS <strong>and</strong> the ones implemented<br />

in applications from the National Domain, External Domain <strong>and</strong> Common<br />

Domain will be described in WSDL.<br />

CDPS should support the use of a business process management (BPM) server<br />

to integrate with applications <strong>and</strong> to automate <strong>and</strong> integrate business processes<br />

within the National Domain, External Domain or with other NCAs. A typical<br />

BPM will support a variety of connectors to communicate with different<br />

software systems in a large enterprise, or across company boundaries.<br />

Connectors to Web Services are provided by all BPM servers.<br />

5.3.3 CDPS modules<br />

5.3.3.1 Transit Control <strong>System</strong> (TCS)<br />

Table 18: Integration Architecture requirements.<br />

Page 152/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

More information on user requirement can be found in §3.1.<br />

5.3.3.1.1Availability Requirements<br />

This section describes the availability requirements for the Transit Control <strong>System</strong> (TCS).<br />

Availability is generally defined as the accessibility of a system resource in a timely manner. It is<br />

referenced as one (out of six) fundamental components of information security. Specifically, this<br />

type of service aims to provide a reasonable degree of assurance that information <strong>and</strong> information<br />

systems will be available when needed i.e. there is no denial of authorised access to network<br />

elements, stored information, information flows, services <strong>and</strong> applications due to events impacting<br />

the network. <strong>System</strong> unavailability may be caused from:<br />

• Software failures, e.g. operating system failure, application error or application<br />

maintenance/update tasks.<br />

• Hardware failures, e.g. disc I/O failure, scheduled system maintenance tasks.<br />

All Information Exchanges (IE) received from any domain will be appropriately held (e.g. queued)<br />

so they are processed once the system returns to available state. TCS should not re-send IEs for<br />

which there has been no reply as a result of unavailability of the receiving system. The re-send<br />

should occur only upon request of the receiving system, or receipt of an exception report.<br />

Availability rate of TCS should be at least 99,0%.<br />

5.3.3.1.2Requirements<br />

TCS shall satisfy all relevant technical requirements from §5.2.<br />

5.3.3.2 Export regimes/Export Control <strong>System</strong> (ECS)<br />

More information on user requirement can be found in §3.2 <strong>and</strong> §3.3.<br />

5.3.3.2.1Availability Requirements<br />

The hosting of CDPS shall assure that the event of failure will not affect the transactions that take<br />

place during this period. All Information Exchanges (IE) received from other applications will be<br />

appropriately held (e.g. queued) so they are processed once the system returns to available state.<br />

Availability rate of a ECS should be at least 99,0%.<br />

5.3.3.2.2Requirements<br />

ECS shall satisfy all relevant technical requirements from §5.2.<br />

5.3.3.3 Import Regime/Import Control <strong>System</strong> (ICS)<br />

More information on user requirement can be found in §3.4 <strong>and</strong> §3.5.<br />

5.3.3.3.1Availability Requirements<br />

The hosting of CDPS shall assure that the event of failure will not affect the transactions that take<br />

place during this period. All Information Exchanges (IE) received from other applications will be<br />

appropriately held (e.g. queued) so they are processed once the system returns to available state.<br />

Availability rate of a ICS should be at least 99,0%.<br />

5.3.3.3.2Requirements<br />

ICS shall satisfy all relevant technical requirements from §5.2.<br />

5.3.3.4 Reference Data Application<br />

The reference data shall be managed in an application which shall be an integral part of the CDPS<br />

application. The maintenance of the reference data in a separate application is prompted by the fact<br />

that such a system will be necessary at the time of the accession of Macedonia to EU (for<br />

exchanging referential data between the Common <strong>and</strong> National domains). Still the Reference Data<br />

Application (RDA) should be considered as a module of CDPS <strong>and</strong> they should be implemented at<br />

the same time. The reference data is a set of different entities. Every entity has a set of attributes<br />

<strong>and</strong> a list of records.<br />

Page 153/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

The RDA is responsible for maintaining <strong>and</strong> distributing to CDPS <strong>and</strong> other applications from the<br />

National Domain all Reference Data <strong>and</strong> is located at MCA’s HQ.<br />

At the time of accession of Macedonia to EU, RDA will be replaced by the CS/RD.<br />

The structure <strong>and</strong> possible values for reference data for the NCTS application published by DG<br />

TAXUD can be seen in annex 6.<br />

The structure <strong>and</strong> possible values for reference data for the AES application published by DG<br />

TAXUD can be seen in annex 7.<br />

The structure <strong>and</strong> possible values for reference data for the AIS application published by DG<br />

TAXUD can be seen in annex 8.<br />

Number<br />

RD-0000<br />

RD-0010<br />

RD-0020<br />

5.3.3.4.1Requirements<br />

Description<br />

Validation: The usage of the reference data in CDPS will give the possibility for<br />

quick <strong>and</strong> less error prone user input. The users shall be able to choose reference<br />

element from a list (the list will display the reference code <strong>and</strong> description) or to<br />

write directly the reference code. Once selected, the reference code <strong>and</strong> the<br />

description shall always be visible on all the data entry <strong>and</strong> enquiry screens.<br />

RDA shall include functionality for:<br />

• Adding new records in entities<br />

• Editing existing records<br />

• Activating/deactivating records: The activation/deactivation of records<br />

(elements) is useful when the usage of an element needs to be<br />

temporarily allowed or disallowed.<br />

Four-eye principle: For all changes to the reference data, RDA will require a<br />

confirmation of the changes by a second (different) user. RDA <strong>and</strong> all clients of<br />

RDA shall use the original version of the record until its modifications are<br />

confirmed, that is, the modifications to a record are not registered <strong>and</strong> are<br />

pending until a confirmation is made.<br />

Table 19: Reference Data requirements.<br />

5.3.3.4.1.1Common Domain<br />

Following requirements should be satisfied at the time of accession of Macedonia into EU.<br />

Number Description<br />

GR-4000 MCA has to maintain its national <strong>Customs</strong> Office List either locally or remotely<br />

through the interactive mode of access to the CS/RD.<br />

GR-4010 MCA has to be able to exchange information with the CS/RD system located at<br />

Central Operations. Hence, MCA shall comply with the defined protocols for<br />

exchanging Common Reference Data <strong>and</strong> COL in [A01], [A02], [A03], <strong>and</strong><br />

[A04].<br />

GR-4020 MCA has to be able to provide the business statistics <strong>and</strong> to submit them<br />

monthly to CS/MIS. Hence, MCA shall comply with the defined protocols for<br />

exchanging business statistics in [A02] <strong>and</strong> [A03].<br />

GR-4030 MCA has to be able to provide information on the national unavailability periods<br />

<strong>and</strong> to submit it to CS/MIS. Hence, MCA shall comply with the defined<br />

protocols for exchanging availability data in [A01], [A02], [A03], <strong>and</strong> [A04].<br />

5.3.3.4.2Availability requirements<br />

Table 20: Reference Data in Common Domain<br />

Page 154/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Since RDA provides essential services <strong>and</strong> data to all CDPS modules, RDA shall be accessible 24<br />

hours per day, 7 days per week.<br />

5.3.4 Integration with Common Domain<br />

More details on the CDPS system integration can be found in Section V e<strong>Customs</strong> <strong>System</strong>s<br />

Integration of R15. Here we give just a brief summary of that section.<br />

There are two types of usage of the Commission (Common Domain/Tariff application) systems by<br />

the national administrations. The national administration can access the Commission systems from<br />

system-to-system, meaning direct communication between server applications without the direct<br />

intervention of an end user. <strong>System</strong>-to-system usage communicates through CCN queues. The<br />

second type of usage is using the HTTP protocol to connect interactive end users to the<br />

Commission systems. In this type of usage, the interactive user has to connect to the CCN network<br />

in order to authenticate himself/herself. Once the user is authenticated, he has to option to continue<br />

using the CCN network or to redirect to a HTTPS connection over the public Internet.<br />

CDPS will exploit the first type of usage: system-to-system. A CCN specific implementation of the<br />

Integration Tier, called CsiBridge, will map between CCN concepts <strong>and</strong> Web service concepts. As a<br />

result, the other layers <strong>and</strong> components within CDPS do not depend on CCN.<br />

5.3.4.1 Transit Control <strong>System</strong> (TCS)<br />

For the definition of the Business Communication Channels, it is assumed that MCA has developed<br />

a national AEO <strong>and</strong>/or EORI system replicating the data from the Central system.<br />

An overview of the Business Communication Channels for NCTS is presented below. A detailed<br />

description of Business Communication Channels for Transit Control <strong>System</strong> (TCS) can be found<br />

in R15.<br />

Figure 5: Overview of Business Communication Channels for Transit Control <strong>System</strong> (TCS)<br />

An overview of the Infrastructure Communication Channels for TCS is presented below. A detailed<br />

description of Infrastructure Communication Channels for Transit Control <strong>System</strong> (TCS) can be<br />

found in R15.<br />

Page 155/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Figure 6: Overview of Infrastructure Communication Channels for<br />

Transit Control <strong>System</strong> (TCS)<br />

5.3.4.2 Automated Export <strong>System</strong>/Export Control <strong>System</strong> (ECS)<br />

An overview of the Business Communication Channels for ECS is presented below:<br />

Figure 7: Overview of Business Communication Channels for Automated Export <strong>System</strong>/Export Control <strong>System</strong> (ECS)<br />

Infrastructure Communication Channels<br />

An overview of the Infrastructure Communication Channels for the ECS is presented below:<br />

Page 156/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Figure 8: Overview of Infrastructure Communication Channels for<br />

Automated Export <strong>System</strong>/Export Control <strong>System</strong> (ECS)<br />

5.3.4.3 Automated Import <strong>System</strong>/Import Control <strong>System</strong> (ICS)<br />

An overview of the Business Communication Channels for ICS is presented below:<br />

Figure 9: Overview of Business Communication Channels for Automated Import <strong>System</strong>/Import Control <strong>System</strong><br />

(ICS).Infrastructure Communication Channels<br />

An overview of the Infrastructure Communication Channels for the ICS is presented below:<br />

Page 157/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Figure 10: Overview of Infrastructure Communication Channels for<br />

Automated Import <strong>System</strong>/Import Control <strong>System</strong> (ICS)<br />

5.3.4.4 Common Domain Conformance Testing Environment<br />

This section will provide the reader with an overview of the Conformance Testing procedure for<br />

intercommunication with the Common Domain.<br />

5.3.4.4.1Conformance Testing of CDPS<br />

TAXUD as part of its CUST/DEV Project defined the process of Conformance Testing for all<br />

applications from the National Domain which aim to connect to the Common Domain.<br />

The objective of Conformance Testing is to demonstrate that the Common Domain interface of the<br />

MCA’s applications conforms technically to the agreed specifications. The proof of this is that<br />

MCA can exchange messages with other NCAs.<br />

The tests however will be limited in scope since they will not test the internal functionality of the<br />

CDPS. They will only test the compliance to the internationally agreed protocol.<br />

The testing of the MCA is organised in “modes”. During the CDPS development cycle, the test<br />

modes are performed in sequence<br />

• Mode-0: Integration Testing<br />

• Mode-1: National Compliance Testing<br />

• Mode-2: Conformance Testing<br />

• Mode-3: International Testing<br />

The diagram below shows the spectrum of each mode.<br />

Page 158/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Figure 11: Testing modes<br />

Section V.II.5 Conformance Testing Environment & CDCA Testing Applications from R15<br />

explains in details the conformance testing for applications from National Domain before they can<br />

be allowed to communicate with the production environment of the Common Domain. Clearly, this<br />

conformance testing applies to CDPS too.<br />

5.3.4.4.2Conformance Testing Requirements<br />

Prior to the accession of Macedonia to EU, CDPS needs to be tested for conformance with the<br />

Common Domain.<br />

Number Description<br />

CT-0000 Common Domain interface of CDPS must conform technically to the agreed<br />

specifications.<br />

CT-0010 CDSP vendor must demonstrate experience or familiarity with the Common<br />

Domain conformance testing.<br />

CT-0020 CDPS architecture must support the fours modes of the Conformance testing. It<br />

must support the testing against the dedicated testing tools St<strong>and</strong>ard Transit Test<br />

Application (STTA) <strong>and</strong> Transit Test Application (TTA).<br />

Table 21: Conformance Testing requirements.<br />

5.3.4.5Connection to Common Domain<br />

This chapter provides the technical requirements for the connection of CDPS to the Common<br />

Domain. These requirements will need to be satisfied prior to the accession of Macedonia to EU.<br />

Number Description<br />

CC-0000 MCA has to develop <strong>and</strong>/or install a CDPS that supports the different elementary<br />

business processes as defined in [R02], [R01] <strong>and</strong> [R03] limited within the scope<br />

of each system as defined in [R09], [R04] <strong>and</strong> [R08] respectively. The necessary<br />

hardware infrastructure has to be provided by MCA.<br />

Page 159/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

CC-0010<br />

CC-0020<br />

CC-0070<br />

CC-0080<br />

CC-0090<br />

CC-0100<br />

Description<br />

MCA has to develop <strong>and</strong>/or install a CDPS that supports the Information<br />

Exchanges as defined in [A01], [A02], [A03], <strong>and</strong> [A04].<br />

All messages sent or received through the Common Domain must be EDIFACT<br />

(for TCS <strong>and</strong> ECS) or XML (for ICS) messages with the exception of the<br />

messages related to Reference Data <strong>and</strong> statistics. The message formatting is<br />

defined in [R09], [R04] <strong>and</strong> [R08].<br />

MCA has to be able to report <strong>and</strong> notify syntactic/non functional errors to the<br />

sender of the Information Exchange. Hence, MCA shall comply with the<br />

Exception H<strong>and</strong>ling as defined in [A01], [A02], [A03], <strong>and</strong> [A04].<br />

MCA shall h<strong>and</strong>le the CCN/CSI ConfirmOnArrival <strong>and</strong> ConfirmOnDelivery<br />

Acknowledgements as they are defined in [A02].<br />

MCA shall log all incoming messages as defined in [A02].<br />

It is the responsibility of MCA to test incoming EDI Trader messages for<br />

authentication, integrity <strong>and</strong> optionally non-repudiation.<br />

Table 22: General requirements for connection to Common Domain.<br />

5.3.5 Integration with National Domain<br />

More information on the applications from the national domain that CDPS needs to integrate with<br />

can be found in the <strong>User</strong> Requirements section of this document<br />

5.3.5.1 Connection to National Domain<br />

This chapter provides the technical requirements for the connection of CDPS with the National<br />

Domain.<br />

Number Description<br />

CN-0000 CDPS has to support the different business processes related to the integration<br />

with the National Domain as defined in the <strong>User</strong> Requirements section of this<br />

document.<br />

CN-0010 MCA has to develop <strong>and</strong>/or install a CDPS that supports the Information<br />

Exchanges <strong>and</strong> Integration Architecture ad defined in §5.3.2.<br />

CN-0020 All messages sent to or received from the National Domain, including the subapplications,<br />

shall be XML messages. It is allowed that CDPS <strong>and</strong> applications<br />

from the National Domain, including the sub-applications, shall have access to<br />

each other’s databases, though this integration approach is not advisable.<br />

CN-0030 CDPS has to be able to report <strong>and</strong> notify syntactic/non functional errors to the<br />

sender of the Information Exchange from the National Domain.<br />

CN-0040 CDPS shall log all incoming messages from the National Domain which are<br />

digitally signed<br />

CN-0050 If the integrity <strong>and</strong> authenticity of a message sent to or received from the<br />

National Domain needs to be protected, then digital signatures <strong>and</strong> digital<br />

certificates shall be used for this purpose. CDPS shall test digitally signed<br />

incoming messages from the National Domain for authentication, integrity <strong>and</strong><br />

optionally non-repudiation.<br />

CN-0060 Reference Data shall be accessed by applications from the National Domain via<br />

Web Services.<br />

CN-0070 CDPS will expose its functionalities to other applications from the National<br />

Domain, including the sub-applications, by means of Web Services.<br />

Other applications from the National Domain, including the sub-applications,<br />

will expose its functionalities to CDPS by means of Web Services.<br />

Page 160/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

CN-0080<br />

Description<br />

<strong>User</strong> name & password, <strong>and</strong> digital certificates are permitted to be used as<br />

authentication mechanisms.<br />

Table 23: General requirements for connection to National Domain.<br />

5.3.6 Integration with External Domain<br />

5.3.6.1 Economic Operators<br />

This section details the functionalities that CDPS shall provide to the Economic Operators:<br />

For small to medium traders a web application shall be provided on the MCA web site offering the<br />

following functionalities:<br />

• Essential: Lodge a declaration electronically (with the digital certificate <strong>and</strong> signatures)<br />

• Essential: Submit the data <strong>and</strong> lodge the manually signed customs declaration<br />

• Desirable: Check the status of the declarations. Check the status of guarantee: comprehensive<br />

guarantee or guarantee waiver.<br />

• Desirable: Unavailability of certain CDPS module due to planned outages e.g. maintenance.<br />

Send notification to all parties.<br />

For large traders <strong>and</strong> Custom Brokers following functionalities will be provided via Web Services.<br />

Traders can build a commercial thick-client application which consumes these web services:<br />

• Essential: Lodge a declaration electronically (with the digital certificate <strong>and</strong> signatures)<br />

• Essential: Submit the data <strong>and</strong> lodge the manually signed customs declaration<br />

• Essential: Provide the reference data for download<br />

• Desirable: Check the status of the declarations. Check the status of guarantee: comprehensive<br />

guarantee or guarantee waiver.<br />

• Desirable: Unavailability of certain CDPS module due to planned outages e.g. maintenance.<br />

Send notification to all parties.<br />

5.3.6.2 Other Government Agencies<br />

As explained in §2.3 Domains of the government agencies, CDPS needs to integrate with<br />

information systems of the government agencies: Ministry of Finances including Public Revenue<br />

Office, National Bank of the RM, Ministry of Interior, Ministry of Agriculture, Forestry <strong>and</strong> Water<br />

Supply, Ministry of Health, Ministry of Environment <strong>and</strong> Physical Planning, Ministry of transport<br />

<strong>and</strong> Communications, Ministry of Culture, Ministry of Economy, Directorate for Radiation<br />

Security, Institute for st<strong>and</strong>ardisation, State Statistical Office, Central Registry Office. Further<br />

details on the functionality that needs to be provided to the information systems of other<br />

government agencies can be found in §2.3.<br />

5.3.6.3 Connection to External Domain<br />

This chapter provides the technical requirements for the connection of CDPS with the External<br />

Domain.<br />

Number Description<br />

CE-0000 CDPS has to support the different business processes related to the integration<br />

with the External Domain as defined in the <strong>User</strong> Requirements section of this<br />

document <strong>and</strong> in §5.3.6.<br />

CE-0010 MCA has to develop <strong>and</strong>/or install a CDPS that supports the Information<br />

Exchanges <strong>and</strong> Integration Architecture ad defined in §5.3.2.<br />

Page 161/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

CE-0020<br />

CE-0030<br />

CE-0040<br />

CE-0050<br />

CE-0060<br />

CE-0070<br />

CE-0080<br />

CE-0090<br />

CE-0100<br />

CE-0110<br />

Description<br />

All messages sent to or received from the External Domain must be XML<br />

messages.<br />

All CDPS internal messages will be of XML format.<br />

CDPS has to be able to report <strong>and</strong> notify syntactic/non functional errors to the<br />

sender of the Information Exchange.<br />

CDPS shall log all incoming messages from the External Domain.<br />

CDPS shall test incoming messages from the External Domain for<br />

authentication, integrity <strong>and</strong> optionally non-repudiation.<br />

Reference Data shall be made available to External Domain via Web Services.<br />

The privacy <strong>and</strong> integrity of all messages sent to or received from the External<br />

Domain must be protected.<br />

The integrity <strong>and</strong> authenticity of all messages sent to or received from the<br />

External Domain must be protected by means of digital signatures <strong>and</strong> digital<br />

certificates.<br />

Web services will be the only technology used by CDPS to expose functionality<br />

for-business to-business integration with the entities (large traders, Custom<br />

Brokers, <strong>and</strong> Government Agencies) from the external domain (see §5.3.2).<br />

Connection to web services will be secured by means of digital certificates. For<br />

Web Services will be secured by means of the communications protocol Web<br />

Services Security.<br />

<strong>User</strong> authentication for connection to the web application <strong>and</strong> web services shall<br />

be done by digital certificates.<br />

Table 24: General requirements for connection to External Domain.<br />

5.3.7 Conformance testing<br />

MCA needs to establish a CDPS conformance testing procedure for all applications from the<br />

National or External domain which aim to connect to CDPS. Conformance testing is a type of<br />

conformance assessment by means of testing. Conformance testing will determine whether an<br />

application from the National or External domain system meets some specified st<strong>and</strong>ard. To aid in<br />

this, many test procedures <strong>and</strong> test setups need to be developed by CDPS vendor. Typically,<br />

conformance testing plan will be written in parallel with specification.<br />

Conformance testing is a type of black box or functional testing. An output from the conformance<br />

testing is a testing log.<br />

Testing log will be then submitted to MCA for further examination, <strong>and</strong> certification of the tested<br />

application. Only after an application is certified to have passed the conformance testing, it can be<br />

connected to the production environment.<br />

As explained in §5.2.2, MCA <strong>and</strong> CDPS must support the existence of a conformance testing<br />

environment.<br />

Number Description<br />

CT-0000<br />

CT-0010<br />

CT-0020<br />

CT-0030<br />

CDPS vendor shall prepare a conformance testing plan.<br />

CDPS shall support the co-existence of conformance testing environment with<br />

the production environment (see §5.2.2).<br />

MCA shall ensure the existence of a conformance testing environment.<br />

Conformance testing shall be conducted by the vendor of the application from<br />

the External Domain or the National Domain. Conformance testing shall<br />

produce a testing log.<br />

An application can be connected to the production environment only after is has<br />

been certified by MCA on basis of the outcomes from the conformance testing.<br />

Page 162/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

CT-0040<br />

CT-0050<br />

Description<br />

<strong>User</strong> credentials (user name & password, digital certificates) will be different for<br />

the production <strong>and</strong> the conformance testing environment. <strong>User</strong> credentials (user<br />

name & password, digital certificates) which are accepted for authentication<br />

purposes in the production environment cannot be accepted in the conformance<br />

testing environment.<br />

It is desirable that the CDPS vendor shall provide a st<strong>and</strong>alone version of CDPS<br />

which can be installed at an external organisation’s premises <strong>and</strong> used for<br />

preliminary conformance testing without connecting to the CDPS conformance<br />

testing environment at MCA.<br />

Table 25: Conformance testing requirements.<br />

5.3.8 Outsourcing of application hosting<br />

Due to the critical nature of CDPS for everyday operations of MCA, the hosting of CDPS<br />

applications needs to be done in a professional manner. It will be very difficult for MCA to find the<br />

appropriate IT professionals that can support <strong>and</strong> maintain the hosting servers 24x7, to provide the<br />

appropriate backup procedures, hosting facilities etc.<br />

Therefore, it is strongly recommended that MCA outsources the hosting of CDPS applications to a<br />

company that specialises in that area.<br />

Similar to the solution adopted at the Croatian <strong>Customs</strong> Administration [R19], if a central servers<br />

hosting facility is built by the Macedonian Government to satisfy the needs of its agencies <strong>and</strong><br />

Ministries, then MCA shall use <strong>and</strong> benefit from such a hosting facility.<br />

The quality of the outsourcing services shall be covered by a Service Level Agreement (SLA).<br />

Following requirements shall be part of the SLA.<br />

Number Description<br />

OS-0000 CDPS availability will be measured on a monthly level. Minimum availability<br />

shall be 99.58% during the first three months of operations, <strong>and</strong> 99,85% after the<br />

third month. Maximum length of failure period during the working hours is 3<br />

hours in the first three months of operations, <strong>and</strong> 1 hour after the third month.<br />

If the achieved monthly availability level is lower than the minimum availability<br />

level, then the monthly support <strong>and</strong> maintenance fee paid to the service provider<br />

will be reduced accordingly.<br />

OS-0010 Service provider must provide a “Backup & Recovery Plan”. This plan <strong>and</strong> its<br />

implementation are needed for improving availability <strong>and</strong> for avoiding loss or<br />

corruption of data in a disaster case. This plan should describe the various<br />

backup alternatives adopted by the service provider: system mirroring, network<br />

duplication, classical backup, etc. For each adopted solution, the service<br />

provider shall define (if relevant): backup hardware, software, facilities <strong>and</strong><br />

media, backup type (full, differential, incremental, etc) <strong>and</strong> schedule, backup<br />

software installation <strong>and</strong> configuration, resources responsible for backup,<br />

backup storage location, recovery procedures in various situations.<br />

OS-0020 Service provider must provide a Disaster Recovery <strong>and</strong> Business Continuity<br />

Plan to support the communication medium or server failure. Servers must be<br />

hosted in a facility satisfying common hazard-resistance (fire, flood, earthquake<br />

etc.) requirement.<br />

OS-0030 Help desk: Service provider must provide a help desk. Response time from the<br />

Help desk shall be shorter than 5 minutes during work hours, <strong>and</strong> shorter than 20<br />

minutes outside of the working hours. During working hours Help desk shall be<br />

available via phone <strong>and</strong> email. Outside of the working hours, Help desk shall be<br />

Page 163/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Number<br />

Description<br />

available via email.<br />

If the achieved response times from the Help desk are higher than the maximum<br />

allowed response times, then the monthly fee paid for the Help Desk will be<br />

reduced accordingly.<br />

Table 26: Outsourcing of application hosting requirements.<br />

6. PHASING/MILESTONES FOR THE CDPS PROJECT<br />

6.2 Introduction of the stages<br />

6.2.1 Phase plan<br />

The project lifecycle consists of the phases described in the following table.<br />

Phase name Number of iterations Duration<br />

Inception 1 20 days<br />

Elaboration 2 160 days<br />

Construction 5 260 days<br />

Transition 2 60 days<br />

Details are can be obtained from Annex 2 of this document (see Chapter 8).<br />

6.2.2 Phase objectives<br />

The table bellow explains every phase.<br />

Phase name<br />

Inception<br />

Elaboration<br />

Description<br />

The inception phase is of significance primarily for new<br />

development efforts, in which there are significant business<br />

<strong>and</strong> requirements risks which must be addressed before the<br />

project can proceed. For projects focused on enhancements to<br />

an existing system, the inception phase is more brief, but is<br />

still focused on ensuring that the project is both worth doing<br />

<strong>and</strong> possible to do. This phase is more oriented to the product<br />

provider because MCA already decided to replace the existing<br />

Asycuda system with a new one. During the phase the product<br />

provider will estimate the risk, calculate its benefits, define<br />

project scope <strong>and</strong> objectives <strong>and</strong> a final decision will be made<br />

for participating in the project. The functional boundaries of<br />

the system are ready <strong>and</strong> will be provide to the product<br />

provider.<br />

During this phase the <strong>User</strong> <strong>and</strong> Technical Requirements, Usecase<br />

Model, <strong>and</strong> Software Architecture documents provided<br />

by “Technical Assistance for Drafting Technical <strong>and</strong> <strong>User</strong><br />

Requirement for the <strong>Customs</strong> Administration” project will be<br />

further elaborated. Every single detail of the system will be<br />

defined <strong>and</strong> the system’s Functional Specification will be<br />

prepared based upon the <strong>User</strong> Requirements document. The<br />

database model <strong>and</strong> source code design model will be<br />

Page 164/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Construction<br />

Transition<br />

prepared. An architectural prototype (or so called Proof of<br />

Concept) will be constructed for testing the feasibility <strong>and</strong><br />

performance of the architecture. <strong>User</strong> interface prototype will<br />

be designed <strong>and</strong> developed.<br />

The goal of the construction phase is on clarifying the<br />

remaining requirements <strong>and</strong> completing the development of<br />

the system based upon the baselined design <strong>and</strong> architecture.<br />

The phase will be divided on different iterations for the<br />

different modules of the CDPS core. If a ready product is<br />

chosen from MCA the iterations in this phase will be<br />

dedicated for customizing, refining <strong>and</strong> remodeling of the<br />

system.<br />

The most significant deliverables from this phase are the<br />

system itself <strong>and</strong> the installation files <strong>and</strong> scripts.<br />

The focus of the Transition Phase is to ensure that software is<br />

available for its end users. The Transition Phase includes<br />

testing the product in preparation for release, <strong>and</strong> making<br />

minor adjustments based on user feedback. At this point in the<br />

lifecycle, user feedback should focus mainly on fine tuning<br />

the product, configuring, installing <strong>and</strong> usability issues. The<br />

training of the users of the systems is also part of the<br />

objectives of the phase.<br />

A final decision for product acceptance will be made at the<br />

end of this phase <strong>and</strong> eventually data migration from the<br />

previous system can take place.<br />

Page 165/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7. USE-CASE MODELS<br />

7.1 Transit use-case model (national transit)<br />

The objective of this chapter is to provide the use-case models for <strong>User</strong> <strong>and</strong> Technical Requirements for the<br />

“<strong>Customs</strong> <strong>Declaration</strong> <strong>Processing</strong> <strong>System</strong>” (CDPS) in following main parts:<br />

• Transit use-case model (national transit),<br />

• Transit use-case model (common/Community transit),<br />

• National export use-case model,<br />

• ECS - AES use-case model,<br />

• National import use-case model,<br />

• ICS - AIS use-case model.<br />

Page 166/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.1 Overview of Transit Core Business<br />

Page 167/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.2 CO1A - Process Departure - Acceptance/Controls<br />

Premises of Trader<br />

at Departure<br />

Office of Departure<br />

E_Principal initiates<br />

movement<br />

(IE15)<br />

R_Principal notified of<br />

rejection<br />

R_MRN<br />

communicated to<br />

Principal<br />

<strong>Declaration</strong> invalid<br />

(IE16)<br />

<strong>Declaration</strong> valid<br />

(IE28)<br />

CO1A0501<br />

Accept<br />

declaration<br />

<strong>Declaration</strong> valid &<br />

Normal Procedure<br />

<strong>Declaration</strong> valid &<br />

Simplified Procedure<br />

E_Principal submits<br />

an amendment<br />

(IE13)<br />

CO1A2100<br />

Evaluate<br />

amendment<br />

request<br />

Amendment accepted &<br />

Simplified Procedure<br />

Awaiting for<br />

automatic release<br />

R_Amendment<br />

rejected by Office of<br />

Departure<br />

R_Amendment<br />

accepted by Office of<br />

Departure<br />

Amendment<br />

invalid (IE05)<br />

Amendment<br />

accepted<br />

(IE04)<br />

To Control<br />

(IE60)<br />

Amendment<br />

accepted &<br />

Normal<br />

procedure<br />

Cancel guarantee<br />

R_Cancellation<br />

of the guarantee<br />

has been asked<br />

CO1A0801<br />

Decide to control<br />

To Control<br />

No<br />

Control<br />

E_<strong>Customs</strong><br />

Officer decide<br />

to control<br />

1<br />

E_Time to<br />

release<br />

CO1A2300<br />

Verify goods<br />

<strong>and</strong>/or supporting<br />

documents at<br />

Trader<br />

R_Principal notified of<br />

a control<br />

Minor revisions<br />

(IE119)<br />

1<br />

CO1A2200<br />

Register control<br />

decision<br />

(IE17) or (IE119)<br />

Minor revisions<br />

R_Principal<br />

notified of minor<br />

discrepancies<br />

CO1A1001<br />

Verify goods<br />

<strong>and</strong>/or supporting<br />

documents<br />

CO1A1002<br />

H<strong>and</strong>le results of a<br />

control<br />

Satisfactory or<br />

minor revisions<br />

& no opposition<br />

CO1A2400<br />

Prepare guarantee<br />

registration<br />

R_Check of the<br />

Guarantees has been<br />

asked<br />

R_Principal notified of<br />

minor discrepancies<br />

R_Goods not released<br />

for Transit<br />

Major<br />

(IE51)<br />

Minor revisions & no Trader advice<br />

<strong>Declaration</strong><br />

awaiting release<br />

request<br />

Minor revisions &<br />

opposition<br />

E_Principal requests<br />

release<br />

E_Release<br />

request timer<br />

Expired<br />

CO1A2000<br />

Put declaration in<br />

idle state<br />

R_Principal notified of<br />

release request<br />

rejection<br />

(IE54)<br />

Invalid<br />

(IE62)<br />

CO1A1600<br />

H<strong>and</strong>le release<br />

request<br />

Minor revisions &<br />

opposition<br />

Minor revisions &<br />

No Opposition<br />

Possible<br />

release<br />

CO1A2500<br />

Take decision<br />

R_Check of the<br />

Guarantees has been<br />

asked<br />

R_Goods not released<br />

for Transit<br />

No release<br />

(IE51)<br />

Page 168/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.3 CO1B - Process Departure – Release<br />

Page 169/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.4 CO02 - Process Arrival at Office of destination<br />

a) Process Arrival – part I<br />

Page 170/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) Process Arrival - part II<br />

Page 171/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

c) Process Arrival - part III<br />

Page 172/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.5 CO04 - H<strong>and</strong>le enquiry<br />

a) H<strong>and</strong>le enquiry - part 1<br />

Page 173/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) H<strong>and</strong>le enquiry - part 2<br />

Premises of the Trader<br />

at Departure<br />

Competent Authority for<br />

Recovery<br />

Office of Destination<br />

Premises of the<br />

Guarantor<br />

1<br />

R_Principal notified<br />

of recovery<br />

procedure<br />

(IE35)<br />

CO041001<br />

Start recovery<br />

procedure<br />

Movement not covered<br />

by a cash guarantee<br />

(IE35)<br />

R_Guarantor<br />

notified of recovery<br />

procedure<br />

Competent Autority of<br />

Country of Departure<br />

Recovery procedure completed<br />

R_Principal notified<br />

of the write-off<br />

(IE45)<br />

CO041200<br />

Write-off movement<br />

Movement not covered<br />

by a cash guarantee<br />

(IE45)<br />

R_Guarantor<br />

notified of the writeoff<br />

R_Movement<br />

written-off<br />

Page 174/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.6 CO06 - Process Cancellation<br />

Page 175/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.1.7 CO08 - Confirm Authorised Consignee<br />

Office of Departure<br />

Office of Destination<br />

E_Principal requests<br />

confirmation of<br />

Authorised Consignee<br />

CO080100<br />

Submit request for<br />

confirmation<br />

(IE111)<br />

CO080200<br />

H<strong>and</strong>le request for<br />

confirmation<br />

CO080300<br />

Display requested<br />

information<br />

(IE112)<br />

R_Principal has<br />

confirmation of<br />

Authorised Consignee<br />

Page 176/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2 Transit use-case model (common/Community transit)<br />

7.2.1 Overview of common/Community Transit Core Business<br />

Page 177/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.2 CO1A - Process Departure - Acceptance/Controls<br />

Page 178/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.3 CO1B - Process Departure – Release<br />

Premises of the Trader<br />

at Departure<br />

E_Guarantee check<br />

results are available<br />

Office of Departure<br />

CO1B1502<br />

Evaluate<br />

guarantee<br />

registration result<br />

Declared Office of<br />

Transit<br />

Declared<br />

Office of<br />

Destination<br />

OLAF<br />

(ATIS)<br />

R_Principal notified of<br />

negative guarantee<br />

result<br />

Guarantee Nok<br />

(IE55)<br />

Guarantee Nok<br />

Guarantee awaiting<br />

for amendment<br />

E_Principal amends<br />

the declaration<br />

guarantee details<br />

R_Principal notified of<br />

the invalidity of the<br />

guarantee details<br />

Not valid<br />

(IE05)<br />

(IE13)<br />

CO1B1900<br />

H<strong>and</strong>le<br />

amendment of the<br />

declaration<br />

guarantee details<br />

Guarantee amendment valid<br />

Guarantee OK<br />

R_Check of the<br />

Guarantees has been<br />

asked<br />

E_Guarantee<br />

amendment<br />

Timer expires<br />

CO1B1101<br />

H<strong>and</strong>le<br />

unsatisfactory<br />

guarantee result<br />

R_Goods not released for<br />

Transit<br />

IE51<br />

IE29<br />

CO1B1301<br />

Issue Transit<br />

Transaction data<br />

IE01<br />

IE11 – Sensitive Goods Notification<br />

R_Goods released for<br />

Transit<br />

IE50<br />

For each declared<br />

Office of Transit<br />

CO1B1400<br />

H<strong>and</strong>le advanced<br />

arrival notification<br />

CO1B1450<br />

Evaluate<br />

advanced arrival<br />

notification<br />

R_Movement may go to<br />

destination<br />

CO1B1700<br />

H<strong>and</strong>le advanced<br />

Transit notification<br />

R_Enquiry initiation<br />

timer started<br />

R_Office of Transit<br />

notified of departure<br />

R_Office of<br />

Destination notified<br />

of departure<br />

R_OLAF notified of<br />

release of transit<br />

for sensitive goods<br />

Page 179/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.4 CO02 - Process Arrival at Office of destination<br />

a) Process Arrival part I<br />

Premises of the Trader<br />

at Destination<br />

Actual Office of Destination<br />

Office of Departure<br />

Declared Office<br />

of Transit<br />

Declared Office of<br />

Destination<br />

Premises of<br />

the<br />

Guarantor<br />

Premises of the<br />

Trader<br />

at Departure<br />

E_Transit consignment<br />

arrives<br />

at destination<br />

(IE07)<br />

R_Presentation rejected<br />

at destination<br />

Presentation invalid<br />

(IE08)<br />

CO020102<br />

Process arrival<br />

notification<br />

Arrival accepted -<br />

Simplified Procedure<br />

(IE06)<br />

Arrival accepted -<br />

Normal Procedure<br />

(IE06)<br />

Arrival accepted -<br />

Normal Procedure<br />

Diversion<br />

(IE02)<br />

Arrival accepted -<br />

Simplified Procedure<br />

Arrival accepted -<br />

Simplified Procedure<br />

3<br />

(IE03)<br />

CO020300<br />

H<strong>and</strong>le AAR<br />

request<br />

Arrival accepted -<br />

Normal Procedure<br />

R_AAR rejected at<br />

destination<br />

AAR rejected<br />

by Ofice of Departure<br />

(IE21)<br />

CO020202<br />

H<strong>and</strong>le AAR<br />

response<br />

Diversion recorded -<br />

Normal Procedure -<br />

Simplified Procedure<br />

(IE06)<br />

CO020701<br />

Store <strong>and</strong> forward<br />

arrival advice<br />

Foreseen route<br />

not followed<br />

(IE24)<br />

Diversion<br />

(IE24)<br />

CO020703<br />

Record diversion<br />

Diversion recorded -<br />

Simplified Procedure<br />

Diversion recorded -<br />

Normal Procedure<br />

Diversion recorded -<br />

Simplified Procedure<br />

Diversion recorded -<br />

Normal Procedure<br />

R_Office of<br />

Departure notified of<br />

arrival (or diversion)<br />

For each<br />

declared Office<br />

of Transit<br />

CO020702<br />

Close frontier<br />

R_Declared Office<br />

of Destination<br />

notified of diversion<br />

2<br />

1<br />

3<br />

R_Credit reference<br />

amount for<br />

guarantee codes 0<br />

<strong>and</strong> 1has been<br />

asked<br />

R_Declared Offices of<br />

Transit notified of arrival<br />

or diversion<br />

Page 180/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) Process Arrival part II<br />

Premises of the Trader<br />

at Destination<br />

R_Goods released<br />

from Transit<br />

Actual Office of Destination<br />

No control & Normal Procedure<br />

(IE25)<br />

1<br />

CO020600<br />

Decide to control<br />

Office of Departure<br />

Declared<br />

Office of<br />

Transit<br />

Declared Office of<br />

Destination<br />

Premises of<br />

the<br />

Guarantor<br />

Premises of the<br />

Trader<br />

at Departure<br />

2<br />

E_Unloading<br />

authorisation<br />

timer expired<br />

Wait for automatic<br />

unloading permission<br />

R_Guarantor<br />

notified of the<br />

responsibility<br />

extension<br />

R_Authorised<br />

Consignee notified of<br />

the unloading<br />

permission<br />

E_Authorised Consignee<br />

sends unloading<br />

information<br />

4<br />

(IE43)<br />

CO021100<br />

Control of the<br />

goods<br />

CO020601<br />

Force unloading<br />

permission<br />

(IE44)<br />

(IE120)<br />

Unloading information invalid<br />

(IE58)<br />

(IE120)<br />

CO021200<br />

Store & analyse<br />

unloading remarks<br />

E_Goods to be<br />

controlled<br />

Completion without<br />

unloading remarks<br />

(IE18 or IE110)<br />

To control<br />

CO021100<br />

Control of the<br />

goods<br />

No control & Normal Procedure<br />

(IE18 or IE110)<br />

CO021801<br />

H<strong>and</strong>le destination<br />

control results<br />

R_Movement<br />

writen-off<br />

No discrepancies<br />

No discrepancies<br />

CO requested<br />

to answer enquiry<br />

(IE59)<br />

Discrepancies<br />

(IE19)<br />

Discrepancies<br />

(IE19)<br />

For each office<br />

requested for<br />

enquiry<br />

CO021803<br />

Cancel enquiry<br />

process<br />

R_Principal<br />

notified of the<br />

responsibility<br />

extension<br />

R_Unloading<br />

information rejected at<br />

destination<br />

R_Authorised<br />

Consignee notified of<br />

the unloading<br />

permission<br />

No completion<br />

&<br />

No control<br />

unloaded goods<br />

(IE43)<br />

Completion without unloading<br />

remarks<br />

(IE25)<br />

R_Goods released<br />

from Transit<br />

Unloading remarks<br />

CO021300<br />

Decide to control<br />

unloaded goods<br />

To control unloaded goods<br />

(IE120)<br />

4<br />

No discrepancies or<br />

no waiting for discrepancies resolution<br />

(IE25)<br />

Completion with<br />

unloading remarks<br />

&<br />

No contorl<br />

CO021500<br />

Record control<br />

results<br />

(IE18 or IE110)<br />

Discrepancies<br />

CO021701<br />

Solve<br />

discrepancies<br />

R_Release of the<br />

guarantee has<br />

been asked<br />

Following enquiry<br />

(IE45)<br />

(IE45)<br />

R_<strong>Customs</strong> Offices<br />

requested for<br />

enquiry notified of<br />

cancellation<br />

Following enquiry<br />

(IE45)<br />

(IE45)<br />

R_Principal<br />

notified of the<br />

write-off<br />

(IE25)<br />

CO021601<br />

Release goods<br />

from Transit<br />

Office of Destination waiting<br />

for resolution<br />

(IE20)<br />

R_Movement<br />

writen-off<br />

R_Guarantor<br />

notified of the<br />

write-off<br />

Page 181/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

c) Process Arrival part III<br />

Page 182/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.5 CO03 - Process movement at Office of Transit<br />

Office of Transit<br />

Office of Departure<br />

E_Movement<br />

arrives at Office of<br />

Transit<br />

CO030100<br />

Capture MRN at<br />

Office of Transit<br />

International diversion (IE114)<br />

ATR-information available<br />

CO030202<br />

Provide ATRinformation<br />

R_Movement<br />

stopped at<br />

frontier<br />

Passage not valid<br />

CO030300<br />

Validate<br />

passage<br />

CO030203<br />

Receive ATRinformation<br />

(IE115)<br />

Diversion binding itinerary<br />

R_Movement<br />

turned back<br />

Passage valid<br />

R_Movement<br />

may cross<br />

frontier<br />

CO030400<br />

Register frontier<br />

crossing<br />

(IE118)<br />

CO030500<br />

H<strong>and</strong>le<br />

NCF-information<br />

at departure<br />

R_Crossing logged<br />

R_NCF-information<br />

h<strong>and</strong>led at departure<br />

Page 183/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.6 CO04 - H<strong>and</strong>le enquiry<br />

a) H<strong>and</strong>le enquiry - part 1<br />

Premises of the Trader<br />

at Departure<br />

Competent Authority of<br />

Country of Departure<br />

Office of Destination<br />

Wait for reception<br />

of the arrival<br />

advice or control<br />

results<br />

E_Time to start<br />

enquiry<br />

Postpone<br />

enquiry<br />

Postpone<br />

enquiry<br />

Postpone<br />

enquiry<br />

CO040100<br />

Check appropriate<br />

to continue with<br />

enquiry<br />

R_Principal<br />

notified to provide<br />

information<br />

Principal located <strong>and</strong><br />

arrival advice not received<br />

(IE102)<br />

Continue enquiry<br />

CO040200<br />

Request<br />

information on nonarrived<br />

movement<br />

E_Principal provides<br />

information<br />

(IE103)<br />

CO040301<br />

Receive<br />

information on nonarrived<br />

movement<br />

Start enquiry<br />

Start enquiry<br />

CO040401<br />

Start enquiry<br />

procedure<br />

For each possible Office of Destination<br />

CO040402<br />

Send enquiry<br />

request<br />

(IE104)<br />

CO040800<br />

Carry out enquiry at<br />

requested Office<br />

CO040801<br />

Carry out enquiry<br />

reminder at<br />

requested Office<br />

Higher Authority<br />

of a <strong>Customs</strong><br />

Office<br />

Wait for<br />

enquiry<br />

response<br />

E_Time allotted<br />

for enquiry<br />

response expired<br />

Able to resume arrival<br />

process<br />

(IE105)<br />

Postpone<br />

CO040500<br />

Check<br />

appropriate to<br />

continue with<br />

enquiry reminder<br />

Continue<br />

CO040600<br />

Send enquiry<br />

reminder<br />

Consignment<br />

not located<br />

(IE106)<br />

R_Arrival<br />

processing<br />

resumed<br />

(IE105)<br />

Consignment<br />

not located<br />

(IE106)<br />

CO040700<br />

Stimulate enquiry<br />

answer<br />

E_Answer<br />

received<br />

CO040900<br />

Process negative<br />

enquiry response<br />

Premises of the<br />

Guarantor<br />

(IE63)<br />

Office of Transit<br />

(IE23)<br />

R_Guarantor<br />

notified of non<br />

discharge<br />

For each<br />

declared Office<br />

of Transit<br />

CO041202<br />

Record Start<br />

Recovery<br />

All expected enquiry<br />

responses received<br />

1<br />

(IE63)<br />

CO041204<br />

Record Recovery<br />

Start<br />

R_Declared Offices of<br />

Transit notified of start<br />

of recovery<br />

R_Declared Office of<br />

Destination notified of<br />

start of Recovery<br />

Page 184/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) H<strong>and</strong>le enquiry - part 2<br />

Premises of the Trader<br />

at Departure<br />

Competent Authority for<br />

Recovery<br />

Office of Destination<br />

Premises of the<br />

Guarantor<br />

1<br />

R_Principal notified<br />

of recovery<br />

procedure<br />

(IE35)<br />

CO041001<br />

Start recovery<br />

procedure<br />

Movement not covered<br />

by a cash guarantee<br />

(IE35)<br />

R_Guarantor<br />

notified of recovery<br />

procedure<br />

Competent Autority of<br />

Country of Departure<br />

Recovery procedure completed<br />

R_Principal notified<br />

of the write-off<br />

(IE45)<br />

CO041200<br />

Write-off movement<br />

Movement not covered<br />

by a cash guarantee<br />

(IE45)<br />

R_Guarantor<br />

notified of the writeoff<br />

R_Movement<br />

written-off<br />

Page 185/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.7 CO06 - Process Cancellation<br />

Page 186/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.8 CO07 - Query Movement Information<br />

Page 187/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.2.9 CO08 - Confirm Authorised Consignee<br />

Office of Departure<br />

Office of Destination<br />

E_Principal requests<br />

confirmation of<br />

Authorised Consignee<br />

CO080100<br />

Submit request for<br />

confirmation<br />

(IE111)<br />

CO080200<br />

H<strong>and</strong>le request for<br />

confirmation<br />

CO080300<br />

Display requested<br />

information<br />

(IE112)<br />

R_Principal has<br />

confirmation of<br />

Authorised Consignee<br />

Page 188/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3 National export use-case model<br />

7.3.1 Overview of Export Core Business<br />

Premises of the Trader<br />

at the point of Export<br />

Office of Export<br />

Office of Exit<br />

E_Exporter/Declarant<br />

initiate export operation<br />

Prepare<br />

consignment &<br />

declaration<br />

Process export<br />

Present goods at<br />

office of exit<br />

Process exit of<br />

goods<br />

R_EAD Accompanying<br />

Document printed<br />

Export operation<br />

finalized<br />

Finalise Export<br />

operation<br />

Page 189/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.2 CO1A - Process Export - Acceptance/Controls at Office of Export<br />

Page 190/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.3 CO1B - Process Export – Release at Office of Export<br />

Page 191/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.4 CO02 - Process Arrival at Actual Office of Exit<br />

a) Process Arrival at Actual Office of Exit - part I<br />

Page 192/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) Process Arrival at Office of Exit - part II<br />

Page 193/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.5 CO03 - Process Exit at Actual Office of Exit<br />

a) Process Exit at Actual Office of Exit - Part I<br />

Manifest<br />

presentation<br />

(IE547)<br />

Page 194/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) Process Exit at Actual Office of Exit - Part II<br />

Page 195/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.6 CO04 - H<strong>and</strong>le Follow-Up<br />

Page 196/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.7 CO06 - Process Cancellation<br />

Page 197/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.3.8 CO07 - Query Export Operation Information<br />

Page 198/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4 ECS - AES use-case model<br />

7.4.1 Overview of Export Core Business<br />

Office of Export<br />

Office of Exit<br />

Premises of the Trader<br />

at the point of Export<br />

E_Exporter/Declarant<br />

initiate export operation<br />

Prepare<br />

consignment &<br />

declaration<br />

Process export<br />

Present goods at<br />

office of exit<br />

Process exit of<br />

goods<br />

R_EAD Accompanying<br />

Document printed<br />

Export operation<br />

finalized<br />

Finalise Export<br />

operation<br />

Page 199/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.2 CO1A - Process Export - Acceptance/Controls at Office of Export<br />

Page 200/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.3 CO1B - Process Export – Release at Office of Export<br />

Premises of the Trader<br />

at Export<br />

Office of Export<br />

Declared office of<br />

Exit<br />

3<br />

CO1B1301<br />

Issue Export<br />

Transaction data<br />

R_Goods released for<br />

Export<br />

(IE529)<br />

(IE501)<br />

CO1B1400<br />

H<strong>and</strong>le anticipated<br />

export record<br />

R_Export movement<br />

may go to Office of<br />

Exit<br />

R_Follow-up timer<br />

started<br />

R_Office of Exit<br />

notified of the<br />

Export movement<br />

Page 201/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.4 CO02 - Process Arrival at Actual Office of Exit<br />

a) Process Arrival at Actual Office of Exit - part I<br />

Page 202/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) Process Arrival at Office of Exit - part II<br />

Premises of the Trader<br />

(carrier)<br />

at Exit<br />

Actual Office of Exit<br />

1<br />

Office of Export<br />

CO020600<br />

Decide to control<br />

To control<br />

(IE592)<br />

To control<br />

(IE561)<br />

CO021100<br />

Control of the<br />

goods<br />

R_Trader notified of a<br />

control<br />

(IE592)<br />

No control<br />

R_Goods not allowed<br />

to exit<br />

Not satisfactory<br />

(IE522)<br />

CO021500<br />

Record control<br />

results<br />

Not satisfactory<br />

(IE518)<br />

CO021801<br />

H<strong>and</strong>le not<br />

satisfactory exit<br />

control results<br />

R_Goods allowed to<br />

immediate leave<br />

Satisfactory<br />

(No or minor discrepancies)<br />

R_Office of Export<br />

notified of<br />

discrepancies<br />

(IE525)<br />

(IE525)<br />

CO021601<br />

Release goods for<br />

exit<br />

R_Goods allowed to<br />

be stored<br />

leaving<br />

stored<br />

3<br />

2<br />

Page 203/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.5 CO03 - Process Exit at Actual Office of Exit<br />

a) Process Exit at Actual Office of Exit - Part I<br />

Manifest<br />

presentation<br />

(IE547)<br />

Page 204/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) Process Exit at Actual Office of Exit - Part II<br />

Local Authority<br />

at Exit<br />

Actual Office of Exit<br />

Office of Export<br />

Premises of<br />

the Trader<br />

at Export<br />

VAT Authority<br />

Excise<br />

Authority<br />

CAP<br />

Authority<br />

Other Authorities<br />

3<br />

R_Exporter notified<br />

R_VAT Authority notified<br />

(IE599)<br />

(IE599)<br />

E_Exit Notification<br />

(IE590)<br />

CO031100<br />

H<strong>and</strong>le exit<br />

notification<br />

(IE518)<br />

CO031200<br />

H<strong>and</strong>le exit<br />

confirmation<br />

(IE599)<br />

R_Excise Authority<br />

notified<br />

(IE599)<br />

R_CAP Authority<br />

notified<br />

(IE599)<br />

R_Exit Confirmed<br />

R_Other Authorities<br />

notified<br />

Page 205/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.6 CO04 - H<strong>and</strong>le Follow-Up<br />

Page 206/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.7 CO06 - Process Cancellation<br />

Page 207/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.8 CO07 - Query Export Operation Information<br />

Page 208/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.9 CO01A (SUM) – Process Exit summary declaration at Office of Lodgement<br />

Page 209/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.10 CO02 (SUM) – Process Arrival at Actual Office of Exit<br />

a) CO02 (SUM) – Process Arrival at Actual Office of Exit Part I<br />

Premises of the Trader<br />

(Carrier) at Exit<br />

Actual Office of Exit<br />

Office of Lodgement<br />

E_consingment<br />

arrives at exit<br />

(IE507)<br />

R_Presentation rejected<br />

at exit<br />

Presentation invalid<br />

(IE508)<br />

CO020102(SUM)<br />

Process arrival<br />

notification<br />

<strong>Declaration</strong> request<br />

(IE502)<br />

Goods presented<br />

at Exit<br />

<strong>Declaration</strong> response<br />

(IE603)<br />

CO020300(SUM)<br />

H<strong>and</strong>le declaration<br />

request (Export)<br />

R_C_EXS_SND rejected<br />

at Exit<br />

C_EXS_SND rejected<br />

by Office of Lodgement<br />

(IE521)<br />

CO020202(SUM)<br />

H<strong>and</strong>le declaration<br />

request<br />

Response (Export)<br />

R_Office of<br />

Lodgement notified<br />

of diversion<br />

Diversion recorded<br />

1<br />

Page 210/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) CO02 (SUM) – Process Arrival at Actual Office of Exit Part II<br />

Premises of the Person<br />

lodging the Exit summary<br />

declaration<br />

or<br />

Premises of the<br />

Representative at Exit<br />

Premises of the Trader<br />

(carrier)<br />

at Exit<br />

Actual Office of Exit<br />

1<br />

E_Person/<br />

Representative submits<br />

an amendment<br />

Amendment<br />

Invalid<br />

(IE605)<br />

(IE613)<br />

CO020500(SUM)<br />

Evaluate<br />

amendment<br />

request<br />

Amendment<br />

accepted<br />

R_Amendment rejected<br />

by Office of Exit<br />

Amendment<br />

accepted<br />

(IE604)<br />

CO020600(SUM)<br />

Decide to control<br />

R_Amendment accepted<br />

by Office of Exit<br />

To control<br />

(IE592)<br />

R_Trader notified of a<br />

control<br />

To control (IE561)<br />

No control<br />

CO021100(SUM)<br />

Control of the<br />

goods<br />

(IE592)<br />

R_Goods not allowed<br />

to exit<br />

Not satisfactory<br />

(IE522)<br />

CO021500(SUM)<br />

Record control<br />

results<br />

No or minor discrepancies<br />

R_Goods allowed to<br />

immediate leave<br />

(IE525)<br />

(IE525)<br />

CO021601(SUM)<br />

Release goods for<br />

exit<br />

R_Goods allowed to<br />

be stored<br />

leaving<br />

stored<br />

3<br />

2<br />

Page 211/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.4.11 CO03 (SUM) – Process Exit at Actual Office of Exit<br />

a) CO03 (SUM) – Process Exit at Actual Office of Exit Part I<br />

Page 212/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

b) CO03 (SUM) – Process Exit at Actual Office of Exit Part II<br />

Page 213/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.5 National import use-case model<br />

7.5.1 Overview of Import Core Business<br />

Premises of the Trader<br />

at the point of Import<br />

Office of Import<br />

Premises of the Trader<br />

at the point of Import<br />

E_Importer initiates<br />

Temporary storage<br />

Prepare<br />

consignment &<br />

Summary<br />

declaration<br />

Process temporary<br />

storage<br />

E_Importer/Declarant<br />

initiates import operation<br />

Process import<br />

Process import<br />

Prepare<br />

consignment &<br />

declaration<br />

R_Temporary storage<br />

finished<br />

E_Declarant provides<br />

guarantee or payment<br />

Wait for payment of<br />

customs debtt<br />

Import operation<br />

finalized<br />

Finalise Import<br />

operation<br />

Page 214/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.5.2 CO1A - Process Import - Acceptance/Controls at Office of Import<br />

Page 215/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.5.3 CO1B - Process Import – Release at Office of Import<br />

Premises of the Trader<br />

at Import<br />

Office of Import<br />

VAT Office<br />

3<br />

CO1B1301<br />

Issue Import<br />

Transaction data<br />

(IE729)<br />

R_Goods released for<br />

Import<br />

R_Import operation<br />

information to Office<br />

VAT<br />

R_Follow-up timer for<br />

payment of customs<br />

debt started<br />

Page 216/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.5.4 CO2 - Process Import – Discharge of Import Regime<br />

Page 217/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.5.5 CO03 - H<strong>and</strong>le Follow-Up<br />

Page 218/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.5.6 CO04 - Process Cancellation<br />

Premises of Trader<br />

at Import<br />

Office of Import<br />

E_Declarant requests a<br />

cancellation<br />

Cancellation request<br />

(IE714)<br />

CO060102<br />

H<strong>and</strong>le cancellation<br />

request<br />

Cancellation Rejected<br />

(IE709)<br />

R_Cancellation refused<br />

by <strong>Customs</strong> Authority<br />

E_<strong>Customs</strong> cancels an<br />

import operation<br />

Cancellation accepted or on<br />

<strong>Customs</strong> initiative<br />

(IE709)<br />

R_Cancellation accepted<br />

or required by <strong>Customs</strong><br />

Authority<br />

Page 219/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6 ICS - AIS use-case model<br />

7.6.1 Overview of ICS-Core Business – ENS lodged at an Office of Lodgement<br />

Page 220/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.2 Overview of ICS-Core Business – ENS lodged at an Office of first Entry<br />

Page 221/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.3 CO1A (SUM) – Process Entry Summary <strong>Declaration</strong> at Office of Lodgement<br />

Page 222/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.4 CO1B (SUM) – Process Entry Summary <strong>Declaration</strong> at Office of first Entry<br />

Premises of the<br />

Person lodging the<br />

ENS<br />

Office of first Entry<br />

For each Office of<br />

subsequent Entry<br />

E_Person lodging the ENS<br />

R_Person lodging the ENS<br />

notified of rejection<br />

IE315<br />

<strong>Declaration</strong> invalid<br />

(IE316)<br />

<strong>Declaration</strong> valid<br />

(IE328)<br />

CO1B0501(SUM)<br />

Validate <strong>and</strong><br />

register ENS<br />

E_ENS <strong>and</strong> common safety<br />

<strong>and</strong> security risk analysis<br />

received at Office<br />

of first Entry<br />

CO1B0510(SUM)<br />

Register<br />

forwarded ENS<br />

R_MRN communicated to<br />

Person lodging the ENS<br />

E_Persond lodging the ENS<br />

submits an amendment<br />

request for the ENS<br />

R_Amendment rejected for<br />

ENS<br />

R_Amendment accepted for<br />

ENS<br />

Amendmend<br />

request<br />

(IE313)<br />

Amendment<br />

Invalid<br />

(IE305)<br />

Amendment<br />

accepted<br />

(IE304)<br />

CO1B0600(SUM)<br />

Validate <strong>and</strong><br />

register<br />

amendment<br />

request<br />

<strong>Declaration</strong> valid<br />

(IE328)<br />

<strong>Declaration</strong> valid<br />

(IE328)<br />

R_Preventive/prohibitive<br />

measures/controls notified to<br />

Person lodging the ENS<br />

Notify preventive/prohibitive<br />

measures/controls (IE351)<br />

CO1B0520(SUM)<br />

Perform common<br />

safety <strong>and</strong> security<br />

risk analysis<br />

Trader at Entry<br />

(Carrier)<br />

R_MRN communicated to<br />

Trader at Entry (Carrier)<br />

R_Prohibitive measures<br />

notified to Trader at Entry<br />

(Carrier)<br />

Notify preventive/prohibitive<br />

measures/controls (IE351)<br />

CO1B0580(SUM)<br />

Forward ENS data<br />

<strong>and</strong> common<br />

safety <strong>and</strong> security<br />

risk analysis<br />

results<br />

Forward ENS data + relevant<br />

common safety <strong>and</strong> security risk<br />

analysis results (IE319)<br />

Trader<br />

Representative<br />

E_Representative submits<br />

an amendment request for<br />

the ENS<br />

Amendmend<br />

request (IE313)<br />

CO1B0525(SUM)<br />

Perform national<br />

risk analysis for<br />

goods to be<br />

unloaded<br />

R_Amendment rejected for<br />

ENS<br />

R_Amendment accepted for<br />

ENS<br />

Amendment<br />

Invalid<br />

(IE305)<br />

Amendment<br />

accepted<br />

(IE304)<br />

CO1B0650(SUM)<br />

Validate <strong>and</strong><br />

register<br />

amendment<br />

request<br />

R_ENS <strong>and</strong> all risk analysis<br />

results available at Office of<br />

first Entry<br />

R_ENS data <strong>and</strong> common<br />

safety <strong>and</strong> security risk<br />

analysis results received<br />

at Office of subsequent<br />

Entry<br />

R_Preventive/prohibitive<br />

measures/controls notified to<br />

Representative<br />

Notify preventive/prohibitive<br />

measures/controls (IE351)<br />

Page 223/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.5 CO1C (SUM) – Process Entry Summary <strong>Declaration</strong> at Office of subsequent Entry<br />

Page 224/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.6 C01D – Process international diversion at Office of first Entry<br />

Premises of the Trader<br />

Notifying diversion<br />

Office of first Entry<br />

(declared)<br />

Actual Office of first Entry<br />

E_Trader notifying diversion<br />

requesting diversion<br />

Diversion request<br />

(IE323)<br />

CO1D0010<br />

Validate <strong>and</strong> register<br />

diversion request at<br />

Office of first Entry<br />

Notify diversion<br />

(IE303)<br />

CO1D0100<br />

Register forwarded<br />

diversion<br />

notification<br />

Diversion request<br />

invalid (IE324)<br />

R_Diversion request rejected<br />

Diversion request<br />

valid (IE325)<br />

R_Risk analysis results<br />

available at Actual Office of<br />

first Entry<br />

R_Diversion registered at<br />

Office of first Entry<br />

R_Diversion request accdepted<br />

Page 225/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.7 CO3A – Presentation at Actual Office of first Entry<br />

Trader at Entry (Carrier)<br />

Actual Office of first Entry<br />

Office of first Entry<br />

(declared)<br />

E_Trader at Entry presenting<br />

goods at Actual Office of first Entry<br />

Arrival notification (IE347)<br />

R_Presentation rejected at Actual<br />

Office of first Entry<br />

Arrival notification invalid<br />

(IE348)<br />

Arrival notification valid<br />

(IE348)<br />

CO3A0102<br />

Process<br />

presentation at<br />

Actual Office of first<br />

Entry<br />

MRN provided – not available;<br />

<strong>Declaration</strong> request Import<br />

(IE302)<br />

ENS response (IE303)<br />

CO3A0300<br />

H<strong>and</strong>le declaration<br />

request Import<br />

R_Presentation registered at<br />

Actual Office of first Entry<br />

ENS provided<br />

Presented item valid<br />

CO3A0400<br />

H<strong>and</strong>le declaration<br />

response Import<br />

MRN provided,<br />

No valid ENS available<br />

(IE349)<br />

CO3A0625<br />

Perform national<br />

risk analysis for<br />

goods to be<br />

unloaded<br />

R_Requested Office notified<br />

of diversion<br />

R_Presented item accepted<br />

at Actual Office of first Entry<br />

Process<br />

CO3C<br />

R_Presented item rejected<br />

at Actual Office of first Entry<br />

ENS not provided<br />

Presented item rejected (IE349)<br />

Page 226/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.8 CO3B – Presentation at Actual Office of subsequent Entry<br />

Page 227/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.9 CO3C– Release for Entry at Actual Office of (first or subsequent) Entry<br />

Premises of the Trader at<br />

Entry (Carrier)<br />

Actual Office of (first or subsequent) Entry<br />

B<br />

(ex process<br />

CO03A)<br />

B<br />

(ex process<br />

CO03B)<br />

CO3C0600<br />

Decide to control<br />

R_Trader at Entry notified of a<br />

control<br />

To control (IE361)<br />

To control<br />

(IE392)<br />

CO3C1100(SUM)<br />

Control of the goods<br />

(IE392)<br />

CO3C1500(SUM)<br />

Record control<br />

results<br />

R_Goods not allowed to be<br />

assigned to a customs<br />

approved treatment or use<br />

Not satisfactory<br />

(IE322)<br />

No control<br />

R_Goods allowed to be<br />

assigned to a customs<br />

approved treatment or use<br />

Satisfactory with amending the ENS data (IE329)<br />

Satisfactory without amending the ENS data (IE330)<br />

No control (IE330)<br />

Satisfactory with or<br />

without amending ENS<br />

R_“Summary declaration“<br />

available to a customs<br />

approved treatment or use<br />

Page 228/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.10 Overview of Import Core Business<br />

Premises of the Trader at<br />

Entry (Carrier)<br />

Actual Office of (first or subsequent) Entry<br />

B<br />

(ex process<br />

CO03A)<br />

B<br />

(ex process<br />

CO03B)<br />

CO3C0600<br />

Decide to control<br />

R_Trader at Entry notified of a<br />

control<br />

To control (IE361)<br />

To control<br />

(IE392)<br />

CO3C1100(SUM)<br />

Control of the goods<br />

(IE392)<br />

CO3C1500(SUM)<br />

Record control<br />

results<br />

R_Goods not allowed to be<br />

assigned to a customs<br />

approved treatment or use<br />

Not satisfactory<br />

(IE322)<br />

No control<br />

R_Goods allowed to be<br />

assigned to a customs<br />

approved treatment or use<br />

Satisfactory with amending the ENS data (IE329)<br />

Satisfactory without amending the ENS data (IE330)<br />

No control (IE330)<br />

Satisfactory with or<br />

without amending ENS<br />

R_“Summary declaration“<br />

available to a customs<br />

approved treatment or use<br />

Page 229/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.11 CO1A - Process Import - Acceptance/Controls at Office of Import<br />

Page 230/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.12 CO1B - Process Import – Release at Office of Import<br />

Page 231/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.13 CO2 - Process Import – Discharge of Import Regime<br />

Page 232/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.14 CO03 - H<strong>and</strong>le Follow-Up<br />

Page 233/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

7.6.15 CO04 - Process Cancellation<br />

Page 234/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

8. ANNEXES<br />

Annex 1 - Domains for communication<br />

National transit regime:<br />

External<br />

Domain<br />

National<br />

Domain<br />

External<br />

Domain<br />

Office of<br />

Departure<br />

Office of<br />

Destination<br />

Principal<br />

Consignee<br />

Central<br />

<strong>System</strong><br />

Domain for<br />

other auth.<br />

Common/Community transit regime:<br />

External<br />

Domain<br />

National<br />

Domain<br />

Common<br />

Domain<br />

National<br />

Domain<br />

External<br />

Domain<br />

Office of<br />

Departure<br />

Office of<br />

Destination<br />

Principal<br />

Consignee<br />

indirect EU <strong>and</strong> EFTA <strong>and</strong><br />

3 rd countries transit<br />

Central<br />

<strong>System</strong><br />

direct EU transit<br />

Central<br />

<strong>System</strong><br />

Transporter<br />

Domain for<br />

other auth.<br />

Office of<br />

Transit<br />

Page 235/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

National export regime:<br />

External<br />

Domain<br />

National<br />

Domain<br />

External<br />

Domain<br />

Office of<br />

Export<br />

Office of<br />

Exit<br />

Exporter<br />

Trader<br />

(transporter)<br />

Central<br />

<strong>System</strong><br />

Domain for<br />

other auth.<br />

ECS - AES:<br />

External<br />

Domain<br />

National<br />

Domain<br />

Common<br />

Domain<br />

National<br />

Domain<br />

External<br />

Domain<br />

Office of<br />

Export<br />

Office of<br />

Exit<br />

Exporter<br />

indirect exportation<br />

Trader<br />

Central<br />

<strong>System</strong><br />

direct exportation<br />

Central<br />

<strong>System</strong><br />

Domain for<br />

other auth.<br />

Page 236/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

National import regime:<br />

External<br />

Domain<br />

National<br />

Domain<br />

External<br />

Domain<br />

Office of<br />

Import<br />

Office of<br />

Control<br />

Trader<br />

(transporter)<br />

Importer<br />

Central<br />

<strong>System</strong><br />

Domain for<br />

other auth.<br />

ICS - AIS:<br />

External<br />

Domain<br />

National<br />

Domain<br />

Common<br />

Domain<br />

National<br />

Domain<br />

External<br />

Domain<br />

Office of<br />

Entry<br />

Office of<br />

Import<br />

Importer<br />

Transporter<br />

indirect importation<br />

Central<br />

<strong>System</strong><br />

direct importation<br />

Central<br />

<strong>System</strong><br />

Office of<br />

Control<br />

Domain for<br />

other auth.<br />

Page 237/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Annex 2 - Stages <strong>and</strong> milestones for CDPS<br />

Page 238/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Annex 3 – Local selectivity process<br />

Page 239/276


DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />

AND USE-CASE MODELS<br />

Ref: PHASE V<br />

Annex 4 – Selectivity profile filter system<br />

Page 240/276


Annex 6<br />

NCTS – Reference Data<br />

Annex 5 – NCTS Reference Data<br />

Page 241/276


Annex 6<br />

NCTS – Reference Data<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

AAR REJECTION REASON CODE n ..2 Code to identify the AAR Rejection Reason in IE03.<br />

Values:<br />

1 = Movement arrived at Destination<br />

2 = Cancelled<br />

3 = MRN unknown<br />

4 = Other reasons<br />

ADDITIONAL INFORMATION ID an ..3 Codes for SPECIAL MENTIONS (Box 44), see Annex 37c Implementing Provisions <strong>and</strong> Annex D2 of<br />

the Convention 'Additional Information/Special Indication Code'<br />

- Common Codes:<br />

DG0 = "Export from ‘XX’ subject to restriction"<br />

Remark: ‘XX’ = 1 EFTA country or ‘EC’<br />

DG1 = "Export from ‘XX’ subject to duties"<br />

Remark: ‘XX’ = 1 EFTA country or ‘EC’<br />

DG2 = EXPORT<br />

Based on Regulation 1875/2006, Annex 30A following common code can be used additionally, if NCTS<br />

is used for safety <strong>and</strong> securitz.<br />

10600 = Negotiable Bill of lading 'to order blank endorsed'<br />

ADDITIONAL INFORMATION RESPONSE<br />

CODE<br />

- Additional Codes can also be defined at national level.<br />

n 2 Values:<br />

10 = Requested Additional information # 1: see following text<br />

11 = Requested Additional information # 1 not available<br />

20 = Requested Additional information # 2: sent as requested<br />

21 = Requested Additional information # 2 not available<br />

30 = Requested Additional Information # 3: sent as requested<br />

31 = Requested Additional information # 3 not available<br />

40 = Requested Additional Information # 4: see following text<br />

41 = Requested Additional information # 4 not available<br />

50 = Requested Additional Information # 5: see following text<br />

51 = Requested Additional information # 5 not available<br />

60 = Requested Additional information # 6: sent as requested<br />

61 = Requested Additional information # 6 not available<br />

ADDRESS TYPE a 1 Used for GUARANTOR ADDRESS<br />

Values:<br />

L = Local address<br />

S = Service address for other states<br />

Page 242/276


Annex 6<br />

NCTS – Reference Data<br />

AGREED LOCATION CODE an ..17 Agreed location of goods – precise indication of the place where the goods can be examined.<br />

To be defined at national level.<br />

AMENDMENT REJECTION MOTIVATION<br />

CODE<br />

n 1 Used to specify the Amendment Rejection Motivation.<br />

To be defined at national level.<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

ATR REJECTION REASON CODE an ..2 Values:<br />

1 = Movement arrived at Destination<br />

2 = Movement entered <strong>and</strong> not yet exit the country<br />

3 = Movement exit from the country<br />

4 = Other reason<br />

5 = MRN unknown<br />

6 = Cancelled<br />

AUTHORISATION ID an ..17 Unique Identifier for AUTHORISATION. To be defined at national level.<br />

AUTHORISED LOCATION OF GOODS an ..17 Authorised location of goods – precise indication of the place where the goods can be examined.<br />

To be defined at national level.<br />

COMMODITY CODE n ..6 The usage of commodity codes up to eight digits is allowed (nationally), however only the first six digits<br />

are sent to destination/transit countries with the AAR/ATR, see Annex 37c Implementing Provisions <strong>and</strong><br />

Annex D2 to Appendix III of the Convention.<br />

CONTROL INDICATOR an 2 Values:<br />

NP = Document/Certificate not presented<br />

DI = Differences (Attribute incorrect)<br />

NE = New entry<br />

OT = Other<br />

CONTROL RESULT CODE an 2 See Transit Manual<br />

Values:<br />

At departure:<br />

A1 = Satisfactory<br />

A2 = Considered satisfactory<br />

A3 = Authorised Consignor<br />

B1 = Not satisfactory<br />

Page 243/276


Annex 6<br />

NCTS – Reference Data<br />

At destination:<br />

A1 = Satisfactory<br />

A2 = Considered satisfactory<br />

A5 = Charges collected<br />

B1 = Not satisfactory<br />

COUNTRY CODE a 2 Code to specify countries (ISO alpha 2 country code’ as specified in ISO – 3166 <strong>and</strong> subsequent updates<br />

(Annex 37 c of the Implementing provisions <strong>and</strong> Annex D2 to Appendix III of the Transit Convention)<br />

COUNTRY REGIME CODE an 3 Type of regime applicable to the countries involved in the Transit procedure.<br />

Values:<br />

EEC Transit-country of the EC *<br />

OTH<br />

Other country<br />

TOC Transit-country not belonging to EC *<br />

[* EC = European Community]<br />

COUNTRY/REGION CODE an ..3 Codes to be defined at national level.<br />

CURRENCY CODE an 3 ISO 4217; Code to identify the currency used in Transit-countries<br />

CUSTOMS OFFICE REFERENCE<br />

NUMBER<br />

an 8 <strong>Customs</strong> Office Reference Number as defined in Annex 37c Implementing Provisions <strong>and</strong> Annex D2 to<br />

Appendix III of the Convention.<br />

CUSTOMS SUB PLACE an ..17 <strong>Customs</strong> sub place<br />

To be defined at national level.<br />

DECLARATION TYPE an ..5 <strong>Declaration</strong> Types:<br />

T- = Mixed T1 <strong>and</strong> T2 goods<br />

T1 = External Community transit<br />

T2 = Internal Community transit<br />

T2F = T2 betw. diff. fiscal territories<br />

T2SM = see T2 + San Marino<br />

DISCREPANCY SOLVED NOTIFICATION<br />

CODE<br />

an ..2 Used to specify whether the discrepancies have been solved at the Office of Departure or not<br />

0 = Discrepancy not solved at OoDep<br />

1 = Discrepancy solved at OoDep<br />

DIVERSION REJECTION CODE n ..2 Used to specify the AAR rejection reason (IE 21).<br />

Values:<br />

Page 244/276


Annex 6<br />

NCTS – Reference Data<br />

4 = Other reasons<br />

DOCUMENT TYPE an 3 Used to specify the produced document/certificates.<br />

For a list of possible values, see Annex 37c Implementing Provisions <strong>and</strong> Annex D2 to Appendix III of<br />

the Convention<br />

Following of the code values shall be marked as 'transport documents' for the purpose of Condition<br />

564/567:<br />

235<br />

271<br />

703<br />

704<br />

705<br />

722<br />

730<br />

740<br />

741<br />

750<br />

760<br />

785<br />

787<br />

952<br />

955<br />

FLAG n 1 Used for attributes that can have a positive either a negative value.<br />

Values:<br />

0 = No<br />

1 = Yes<br />

GEO INFO CODE an ..6 The complete list the General Notes of the "LIST of authorised customs offices for Community<br />

transit/common transit operations", originally provided in the General Notes of the "LIST of authorised<br />

customs offices for Community transit/common transit operations" is currently updated <strong>and</strong> available in<br />

the CS/RD<br />

Some examples:<br />

CN = North Sea Coast DE/CH German-Swiss frontier<br />

GEO-NOMENCLATURE CODE n 3 Used in Country Geo Nomenclature Code as specified in on the nomenclature of countries <strong>and</strong><br />

Page 245/276


Annex 6<br />

NCTS – Reference Data<br />

territories for the external trade statistics of the Community <strong>and</strong> statistics of trade between Member<br />

States<br />

(Currently in Reg. (EC) no 750/2005 (OJ L 236, 19.5.2005, p. 12)<br />

GUARANTEE ACCESS CODE an 4 Four digits used to access an NCTS guarantee; see Section III under Heading 1.1.2.5 'Access Code'.<br />

GUARANTEE MONITORING CODE n 1 Indication on the monitoring type of a guarantee in NCTS.<br />

Values:<br />

1 = Type 1 monitoring: MRN, date<br />

2 = Type 2 monitoring: MRN, date, amount<br />

3 = Type 3 monitoring: MRN, date, amount <strong>and</strong> update account<br />

GUARANTEE REFERENCE NUMBER an 24 Each NCTS guarantee will be referenced by a unique Guarantee Reference Number (GRN) which will<br />

be used for validation in the guarantee management sub system.<br />

GUARANTEE TYPE n 1 Guarantee Types:<br />

0 = Guarantee waiver<br />

1 = Comprehensive Guarantee<br />

2 = Individual Guarantee (by guarantor)<br />

3 = Cash Deposit Guarantee<br />

5= : Guarantee waiver for secured amount up to 500 EURO<br />

4 = Individual guarantee in the form of voucher<br />

6 = Guarantee waived<br />

7 = Not required between OoDep/OoTra<br />

8 = Not required certain public bodies<br />

9 = Individual GUA with multiple usage<br />

A= Guarantee waiver by agreement<br />

INVALID GUARANTEE REASON CODE an ..3 Used to specify the invalid guarantee reason (IE32, IE201)<br />

Possible values:<br />

G01 = Does not exist;<br />

G02 = Guarantee exists, but not valid;<br />

G03 = Access code not valid;<br />

G04 = Principal Guarantee ≠ <strong>Declaration</strong>;<br />

G05 = Individual guarantee voucher already used;<br />

G06 = Use restriction : No suspended goods;<br />

G07 = Use restriction : NO sensitive goods;<br />

G08 = Not valid for Country of Tra/Des;<br />

Page 246/276


Annex 6<br />

NCTS – Reference Data<br />

G09 = Reference/Guarantee amounts NOT sufficient;<br />

G10 = Individual guarantee by Guarantor already used;<br />

G11 = <strong>Customs</strong> Office of Departure/<strong>Customs</strong> Office of Destination does not correspond (Guarantee type<br />

‘2’);<br />

G12 = Declared Commodity code ≠Commodity code in guarantee;<br />

G13 = TIR guarantee not reusable.<br />

INVALIDITY REASON CODE an 3 To be defined at national level (IE37), e.g. Guarantee provisionally blocked.<br />

KIND OF PACKAGES a 2 Kind of packaging in which goods are packed.<br />

For a list of possible codes (UNECE Recommendation No. 21), see Annex 37c Implementing Provisions<br />

<strong>and</strong> Annex D2 of the Convention<br />

LANGUAGE CODE an 2 Language Code (LNG) used to define the language used for declaration purposes <strong>and</strong> for free text<br />

information (ISO Alpha 2 Codification - ISO 639), see Annex 37/c Implementing Provisions <strong>and</strong> Annex<br />

D2 to Appendix III of the Convention .<br />

LOADING PLACE an ..17 The loading place in a Transit declaration where coded, its structure hat to be defined at national level.<br />

LOCAL REFERENCE NUMBER (LRN) an ..22 Local Reference Number nationally defined <strong>and</strong> allocated by the user in agreement with the<br />

customs/competent authorities, to identify each single Transit declaration.<br />

MOVEMENT QUERY REASON CODE an ..3 Codes to be defined<br />

MOVEMENT REFERENCE NUMBER<br />

(MRN)<br />

an 18 Movement Reference Number used to identify each single Transit transaction, see: Annex 45a<br />

Implementing Provisions <strong>and</strong> Annex D4 to Appendix III of the Convention.<br />

PREFIX-SUFFIX LEVEL an 1 Used in CUSTOMS OFFICE LSD (IE30).<br />

Values:<br />

A = Simple office (see box A in <strong>Customs</strong> Office List)<br />

E = Higher authority (see box E in <strong>Customs</strong> Office List)<br />

PREFIX-SUFFIX FLAG n 1 Used in CUSTOMS OFFICE LSD (IE30)<br />

Values:<br />

0 = Prefix-Suffix Name is put BEFORE the Office name<br />

1 = Prefix-Suffix Name is put AFTER the Office name<br />

PREVIOUS DOCUMENT TYPE an ..6 Previous administrative reference types:<br />

T2, T2L, T2F, T2LF, T2CIM, T2TIR, T2ATA<br />

Page 247/276


Annex 6<br />

NCTS – Reference Data<br />

Additional Codes can be defined at national level.<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

QUERY IDENTIFIER n 1 Query on Guarantee Type (IE34).<br />

Values:<br />

1 = Usage only<br />

2 = Exposure only<br />

3 = Usage <strong>and</strong> exposure<br />

4 = General information only (no usage & exposure)<br />

REGION CODE an ..3 Codes to be defined at national level.<br />

REQUESTED<br />

INFORMATION CODE<br />

ADDITIONAL<br />

n 1 Values:<br />

1 = <strong>Detailed</strong> goods description needed<br />

2 = Copy of the Invoice needed<br />

3 = Copy of Manifest or Connoissement or Airway bill needed<br />

4 = Name/Address of the person in charge of the formalities at DEST needed<br />

5 = Following additional informations needed<br />

6 = Following additional documents needed<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

RISK ANALYSIS RESULT CODE an ..5 Some values are defined at Common Domain-level, other values can be<br />

defined at National Domain level.<br />

Values at common domain level will be defined by the Risk Management Framework project.<br />

ROLE an 3 <strong>Customs</strong> Office performing one or more precise role(s) in Transit.<br />

Values:<br />

AUT = Higher Authority<br />

CCD = Central Office – Common Domain<br />

CND = Central Office – National Domain<br />

DEP = Office of Departure<br />

DES = Office of Destination<br />

GUA = Office of Guarantee<br />

Page 248/276


Annex 6<br />

NCTS – Reference Data<br />

REC = Office of Recovery<br />

TRA = Office of Transit<br />

SECURITY N 1 1 = <strong>Declaration</strong> used for safety <strong>and</strong> security purposes<br />

Not present = Not used for safety <strong>and</strong> security purposes<br />

SENSITIVE GOODS CODE n ..2 Additional identifier for sensitive goods.<br />

SPACE_TO ADD n 1 Used in CUSTOMS OFFICE LSD (IE30)<br />

Values:<br />

0 = A space MUST NOT be added between Prefix-Suffix Name <strong>and</strong> <strong>Customs</strong> Office Actual Name<br />

1 = A space MUST be added between Prefix-Suffix Name <strong>and</strong> <strong>Customs</strong> Office Actual Name<br />

SPECIFIC CIRCUMSTANCE INDICATOR a 1 Regulation 1875/2006, Annex 30A.<br />

Possible values for NCTS:<br />

A = Postal <strong>and</strong> express consignments<br />

B = Ship <strong>and</strong> aircraft supplies<br />

C = Road mode of transport<br />

D = Rail mode of transport<br />

E = Authorised economic operators<br />

SPECIFIC NOTES CODE an ..6 Specific Notes Codes are used, when necessary, to define the characteristics of the customs offices to be<br />

registered in the electronic version of the <strong>Customs</strong> Office List (COL).<br />

List of codes available in Annex 9 hereafter.<br />

STATISTICS TYPE an 3 For a list of possible types see Section V under Heading 1.2 ‘Archive Procedures’.<br />

SYSTEM UNAVAILABILITY TYPE a 1 Values:<br />

S = Scheduled Unavailability<br />

U = Unscheduled Unavailability<br />

N = Business service not implemented<br />

TIN<br />

(TRADER IDENTIFICATION NUMBER)<br />

an ..17 The Trader Identification Number shall be defined on national level.<br />

However, the first 2 digits shall consist of the country code.<br />

TRADER IDENTIFICATION NUMBER an ..17 The structure of the Trader Identification Number is defined in each country <strong>and</strong> is taken as it is, without<br />

conversion, into Transit (the TIN can e.g. be a VAT number).<br />

Page 249/276


Annex 6<br />

NCTS – Reference Data<br />

TRAFFIC TYPE an ..3 Type of traffic dealt with in the Transit <strong>Customs</strong> Office.<br />

Values:<br />

P = Sea traffic<br />

V = Rail traffic<br />

R = Road Traffic<br />

AIR = Airport<br />

C = River traffic<br />

N/A = Not Applicable<br />

TRANSIT OPERATION STATE TYPE an ..3 Some values are defined at Common Domain level (see IE32). Other values<br />

can be defined at National Domain level. The transit operation states can be<br />

found in FTTS, Section 2 under Heading 1.10.1 “State Transition Diagram”.<br />

Values at common domain level are:<br />

Departure: A01 Arrived<br />

A02<br />

A03<br />

A04<br />

A05<br />

A06<br />

Cancellation:<br />

B02<br />

Destination:<br />

C02<br />

C03<br />

C04<br />

Page 250/276


Annex 6<br />

NCTS – Reference Data<br />

C06<br />

C07<br />

C08<br />

C10<br />

Transit: D01<br />

D02<br />

D03<br />

D04<br />

D05<br />

D06<br />

D07<br />

D08<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

TRANSPORT CHARGES - METHOD OF<br />

PAYMENT<br />

a 1 Commission Regulation (EC) 1875/2006, Annex 30A.<br />

Common code values for NCTS:<br />

A = Payment in cash<br />

B = Payment by credit card<br />

C = Payment by cheque<br />

D = Other<br />

H = Electronic credit transfer<br />

Y =Account holder with carrier<br />

Z = Not pre-paid<br />

TRANSPORT MODE n ..2 Mode of transport corresponding to the active means of transport; see Annex 38 of the Implementing<br />

Provisions <strong>and</strong> Annex A9 to Appendix III of the Convention .<br />

Page 251/276


Annex 6<br />

NCTS – Reference Data<br />

TYPE OF TRANSPORT CROSSING n ..2 To be defined at national level.<br />

BORDER (BOX 21)<br />

UN DANGEROUS GOODS CODE n 4 Codes from the UNDG (United Nations Dangerous Goods list) shall be used.<br />

The Codes will be integrated in CSRD.<br />

UN/LOCODE a 3 To be defined at national level (within the ECE/TRADE/205, Recommendation 16).<br />

UNIT OF MEASURE a 3 Values:<br />

HTL = hectolitre<br />

KGM = kilogram<br />

PCE = pieces or items<br />

Page 252/276


Annex 7<br />

AES – Reference Data<br />

Annex 6 – AES Reference Data<br />

Page 253/276


Annex 7<br />

AES – Reference Data<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

ADDITIONAL INFORMATION ID an ..5 Codes for SPECIAL MENTIONS (Box 44), see Annex 38 Implementing Provisions.<br />

- Common code values for AES/ECS:<br />

30100 = Simplified exportation (incomplete export declaration)<br />

30200 = Simplified exportation (local clearance)<br />

30300 = Goods destined for exportation — agricultural refunds not applicable<br />

30400 = RET-EXP – Copy 3 to be returned<br />

- Additional Codes can also be defined at national level.<br />

AER REJECTION REASON CODE n ..2 Code to identify the AER rejection reason in IE503.<br />

Common code values:<br />

2 = Cancelled<br />

3 = MRN unknown<br />

4 = Other reasons<br />

5 = Movement already exited<br />

(AGREED) LOCATION CODE an ..17 Agreed location of goods (Box 30) – precise indication of the place where the goods can be examined.<br />

To be defined at national level.<br />

AMENDMENT REJECTION MOTIVATION<br />

CODE<br />

n 1 Used to specify the Amendment Rejection Motivation in IE505 <strong>and</strong> IE605.<br />

To be defined at national level.<br />

ARRIVAL AGREED LOCATION CODE an ..17 Arrival agreed location of goods – used in IE507; precise indication of the place where the goods can be<br />

examined.<br />

To be defined at national level.<br />

AUTHORISED LOCATION OF GOODS an ..17 Authorised location of goods (Box 30) – precise indication of the place where the goods can be<br />

examined.<br />

To be defined at national level.<br />

AUTHORISED STORING LOCATION OF<br />

GOODS<br />

an ..17 Authorised storing location of goods – used in IE507; precise indication of the place where the goods<br />

can be examined.<br />

To be defined at national level.<br />

COMBINED NOMENCLATURE an 8 The full CN code (Box 33.1) based on the Harmonised <strong>System</strong> (HS) is to be used (8 digits).<br />

For Codes see TARIC.<br />

COMMODITY CODE an 22 Commodity Code (Box 33), see Annex 37/38 Implementing Provisions based on the Harmonised <strong>System</strong><br />

(HS) <strong>and</strong> TARIC.<br />

The 22 digit Commodity Code is composed of the following:<br />

Page 254/276


Annex 7<br />

AES – Reference Data<br />

- Combined Nomenclature code (8 digits, Box 33.1)<br />

- TARIC code (2 digits, Box 33.2)<br />

- TARIC first additional code (4 digits, Box 33.3)<br />

- TARIC second additional code (4 digits, Box 33.4)<br />

- National additional code (4 digits, Box 33.5)<br />

The number of digits to be used may vary depending on the Rules specified in FTSS.<br />

COMMUNITY / NATIONAL PROCEDURE an 3 For the list of possible codes see Annex 38 Implementing Provisions (Box 37.2).<br />

Common code values for AES/ECS:<br />

A51<br />

A52<br />

A53<br />

B51<br />

B52<br />

B53<br />

B54<br />

C51<br />

C52<br />

E51<br />

E52<br />

E53<br />

E61<br />

E62<br />

E63<br />

E71<br />

F51<br />

F61<br />

F62<br />

F63<br />

F64<br />

COMPLEMENTARY CODE n 1 For the list of possible values see Annex 38 Implementing Provisions (Box 20.3).<br />

Common code values for AES/ECS:<br />

1 Place situated in the territory of the Member State concerned<br />

2 Place situated in the territory of another Member State<br />

3 Other (place situated outside the Community)<br />

Page 255/276


Annex 7<br />

AES – Reference Data<br />

CONTROL INDICATOR an 2 The Code is used in IE518 (Exit control results) to report 'not satisfactory' control results/discrepancies<br />

from the Office of Exit to the Office of Export. Its use is explained in the DDNA document but not in<br />

FTSS. It gives an indication of the differences detected at the Office of Export <strong>and</strong> the Office of Exit.<br />

Common code values for AES/ECS:<br />

DI = Differences (Attribute incorrect)<br />

NP = Document/Certificate not presented<br />

OR = Original<br />

OT = Other<br />

CONTROL RESULT CODE an 2 Used to record the results of a control of goods either at export or at exit (SAD box D).<br />

Common code values for AES/ECS:<br />

At Office of Export:<br />

A1 = Satisfactory<br />

A2 = Considered satisfactory<br />

A3 = Simplified procedure<br />

B1 = Not satisfactory<br />

At Office of Exit:<br />

A1 = Satisfactory<br />

A2 = Considered satisfactory<br />

A4 = Minor discrepancies<br />

B1 = Not satisfactory<br />

COUNTRY (CODE) a 2 Code to specify countries (ISO alpha-2 country code as specified in ISO – 3166 of 1 January 1996 as<br />

published by Eurostat on a yearly basis).<br />

For the attribute 'Country of export' (box 15 <strong>and</strong> 15a) <strong>and</strong> 'TRADER CONSIGNOR.country code'<br />

the countries of the EU shall be used only.<br />

For the attribute 'country of destination' (box17 <strong>and</strong> 17a), other countries than EU countries shall<br />

be used only.<br />

COUNTRY OF ORIGIN a 2 Box 34a. See 'COUNTRY (CODE)'<br />

COUNTRY OF ROUTING CODE a 2 See 'COUNTRY (CODE)'<br />

CURRENCY CODE a 3 Code to specify currencies (ISO alpha-3 currency code as specified in ISO 4217).<br />

CUSTOMS OFFICE REFERENCE<br />

NUMBER<br />

an 8 <strong>Customs</strong> Office Reference Number as defined in Annex 37c Implementing Provisions.<br />

See also <strong>Customs</strong> Office List (COL).<br />

CUSTOMS SUB PLACE an ..17 <strong>Customs</strong> sub place. To be defined at national level.<br />

DECLARATION TYPE (BOX 1.1) a 2 <strong>Declaration</strong> type codes as defined in Annex 38 Implementing Provisions (Box 1.1).<br />

Page 256/276


Annex 7<br />

AES – Reference Data<br />

Common code values for AES/ECS:<br />

EX = Export (except to EFTA)<br />

EU = Export (to EFTA)<br />

CO = Community goods<br />

DECLARATION TYPE (BOX 1.2) a 1 <strong>Declaration</strong> type codes as defined in Annex 38 Implementing Provisions (Box 1.2).<br />

Common code values for AES/ECS :<br />

A Normal declaration (normal procedure under Article 62 of the Code)<br />

B Incomplete declaration (simplified procedure under Article 76(1)(a) of the Code)<br />

C Simplified declaration (simplified procedure under Article 76(1)(b) of the Code)<br />

D Normal declaration (such as referred to under code A) lodged before the declarant is in a position to<br />

present the goods.<br />

E Incomplete declaration (such as referred to under code B) lodged before the declarant is in a<br />

position to present the goods.<br />

F Simplified declaration (such as referred to under code C) lodged before the declarant is in a position<br />

to present the goods.<br />

X Supplementary declaration under a simplified procedure covered by B<br />

Y Supplementary declaration under a simplified procedure covered by C<br />

Z Supplementary declaration under a simplified procedure under Article 76(1)(c) of the<br />

Code (entry of the goods in the records)<br />

DISPATCH/PRODUCTION REGION an ..2 Code for the dispatch-/production region (Box 34b).<br />

To be defined at national level.<br />

DIVERSION REJECTION CODE n ..2 Used to specify the AER rejection reason (IE521).<br />

Codes D, E <strong>and</strong> F can only be used in the framework of the procedure provided for in Article 201(2) where<br />

customs authorities authorise the lodgement of a declaration before the declarant is in a position to present the<br />

goods.<br />

Common code values for AES/ECS:<br />

4 = Other reasons<br />

11 = Cancelled<br />

12 = MRN unknown<br />

13 = Movement already exited<br />

DOCUMENT TYPE an ..4 Used to specify the produced document/certificates as defined in TARIC (Box 44).<br />

EXPORTOPERATION STATE TYPE an ..3 Some values are defined at Common Domain level, other values can be<br />

defined at National Domain level.<br />

Page 257/276


Annex 7<br />

AES – Reference Data<br />

Values will be documented in the Design Document for National Application.<br />

EXIT REJECTION MOTIVATION CODE an ..2 To be defined at national level<br />

EXPORT_QUERY REASON CODE an ..3 The code is used in IE527.<br />

Common code values for AES/ECS:<br />

10 = Enquiry on Export data<br />

20 = Request for Export Operation State<br />

99 = Other<br />

FLAG n 1 Used for attributes that can have a positive either a negative value.<br />

Code values:<br />

0 = No<br />

1 = Yes<br />

INCOTERM CODE a 3 See also Annex 38 Implementing Provisions (Box 20)<br />

Common code values for AES/ECS:<br />

EXW = Ex works<br />

FCA = Free carrier<br />

FAS = Free alongside ship<br />

FOB = Free on board<br />

CFR = Cost <strong>and</strong> freight<br />

CIF = Cost, insurance <strong>and</strong> freight<br />

CPT = Carriage paid to<br />

CIP = Carriage <strong>and</strong> insurance paid to<br />

DAF = Delivered at frontier<br />

DES = Delivered ex-ship<br />

DEQ = Delivered ex-quay<br />

DDU = Delivered duty unpaid<br />

DDP = Delivered duty paid<br />

XXX = Delivery terms other than those listed<br />

KIND OF PACKAGES a 2 See Annex 38 Implementing Provisions (Box 31). Based on UNECE Recommendation No. 21/Rev. 4 –<br />

May 2002.<br />

LANGUAGE CODE a 2 Language Code (LNG) used to define the language used for declaration purposes <strong>and</strong> for free text<br />

information (ISO Alpha 2 Codification – ISO 639 / 1988), see Annex 37c Implementing Provisions.<br />

Page 258/276


Annex 7<br />

AES – Reference Data<br />

METHOD OF PAYMENT a 1 See also Annex 38 Implementing Provisions (Box 47, last column)<br />

Common code values for AES/ECS:<br />

A = Payment in cash<br />

B = Payment by credit card<br />

C = Payment by cheque<br />

D = Other (e. g. direct debit to agent's cash account)<br />

E = Deferred or postponed payment<br />

F = Deferred payment — customs system<br />

G = Postponed payment — VAT system (Article 23 Sixth VAT Directive)<br />

H = Electronic credit transfer<br />

J = Payment through post office administration (postal consignments) or other public sector or government<br />

department<br />

K = Excise credit or rebate<br />

M = Security, including cash deposit<br />

P = From agent's cash account<br />

R = Guarantee<br />

S = Individual guarantee account<br />

T = From agent's guarantee account<br />

U = From agent's guarantee — st<strong>and</strong>ing authority<br />

V = From agent's guarantee — individual authority<br />

O = Guarantee lodged with Intervention Agency.<br />

MOVEMENT REFERENCE NUMBER<br />

(MRN)<br />

an 18 Movement Reference Number used to identify each single export transaction (See Annex 45a, Chapter II<br />

Implementing Provisions <strong>and</strong> Annex 8 to Appendix A3 of FTSS).<br />

NATIONAL ADDITIONAL CODE an 4 Codes to be defined at national level. See explanation for 'Commodity code', Box 33.5.<br />

NATURE OF TRANSACTION CODE n ..2 See Annex 38 Implementing Provisions (Box 24 Column A <strong>and</strong> B)<br />

Common code values for AES/ECS:<br />

1<br />

2<br />

3<br />

4<br />

5<br />

6<br />

7<br />

8<br />

9<br />

11<br />

12<br />

Page 259/276


Annex 7<br />

AES – Reference Data<br />

13<br />

14<br />

15<br />

21<br />

22<br />

23<br />

31<br />

32<br />

33<br />

34<br />

41<br />

42<br />

43<br />

51<br />

52<br />

53<br />

61<br />

62<br />

PREVIOUS DOCUMENT CATEGORY an 1 The attribute correspond to the first element of Box 40. It shall not be merged any longer with the<br />

previous document type.<br />

Common code values for AES/ECS:<br />

X = Summary declaration<br />

Y = Initial declaration<br />

Z = Previous document<br />

PREVIOUS DOCUMENT TYPE an ..6 The attribute correspond to the second element of Box 40. It shall not include any longer the first<br />

element of Box 40 (see PREVIOUS DOCUMENT CATEGORY):<br />

T2, T2L, T2F, T2LF, T2CIM, T2TIR, T2ATA<br />

AES/ECS Codes for the purpose of EMCS:<br />

Administrative Accompanying Document (EMCS) AAD<br />

Other types of previous documents:<br />

Container list 235<br />

Loading list (delivery note) 270<br />

Packing list 271<br />

Proforma invoice 325<br />

Commercial invoice 380<br />

House waybill 703<br />

Master bill of lading 704<br />

Bill of lading 705<br />

CIM consignment note (rail) 720<br />

Page 260/276


Annex 7<br />

AES – Reference Data<br />

Road list SMGS 722<br />

Road consignment note 730<br />

Air waybill 740<br />

Master air waybill 741<br />

Despatch note (post parcels) 750<br />

Multimodal/combined transport document 760<br />

Cargo manifest 785<br />

Bordereau 787<br />

Community transit <strong>Declaration</strong> — Mixed consignments (T) 820<br />

External Community transit <strong>Declaration</strong> (T1) 821<br />

Internal Community transit <strong>Declaration</strong> (T2) 822<br />

Control copy T5 823<br />

TIR carnet 952<br />

ATA carnet 955<br />

Reference/date of entry of the goods in the records CLE<br />

Information sheet INF3 IF3<br />

Information sheet INF8 IF8<br />

Cargo manifest — simplified procedure MNS<br />

Internal Community transit <strong>Declaration</strong> — Article 340 c, 1)<br />

T2F<br />

T2M T2M<br />

Community goods - Normal declaration (normal procedure under Article 62 of the Code) COA<br />

Community goods - Incomplete declaration (simplified procedure under Article 76(1)(a) of the Code) COB<br />

Community goods - Simplified declaration (simplified procedure under Article 76(1)(b) of the Code) COC<br />

Community goods - Normal declaration (such as referred to under code A) lodged before<br />

the declarant is in a position to present the goods. COD<br />

Community goods - Incomplete declaration (such as referred to under code B) lodged before<br />

the declarant is in a position to present the goods. COE<br />

Community goods - Simplified declaration (such as referred to under code C) lodged before<br />

the declarant is in a position to present the goods. COF<br />

Community goods - Supplementary declaration under a simplified procedure covered by B COX<br />

Community goods - Supplementary declaration under a simplified procedure covered by C COY<br />

Community goods - Supplementary declaration under a simplified procedure<br />

under Article 76(1)(c) of the Code (entry of the goods in the records) COZ<br />

Export (to EFTA) - Normal declaration (normal procedure under Article 62 of the Code) EUA<br />

Export (to EFTA) - Incomplete declaration (simplified procedure under Article 76(1)(a) of the Code) EUB<br />

Export (to EFTA) - Simplified declaration (simplified procedure under Article 76(1)(b) of the Code) EUC<br />

Export (to EFTA) - Normal declaration (such as referred to under code A) lodged before<br />

the declarant is in a position to present the goods. EUD<br />

Export (to EFTA) - Incomplete declaration (such as referred to under code B) lodged before<br />

the declarant is in a position to present the goods. EUE<br />

Export (to EFTA) - Simplified declaration (such as referred to under code C) lodged before<br />

the declarant is in a position to present the goods. EUF<br />

Export (to EFTA) - Supplementary declaration under a simplified procedure covered by B EUX<br />

Page 261/276


Annex 7<br />

AES – Reference Data<br />

Export (to EFTA) - Supplementary declaration under a simplified procedure covered by C EUY<br />

Export (to EFTA) - Supplementary declaration under a simplified procedure<br />

under Article 76(1)(c) of the Code (entry of the goods in the records) EUZ<br />

Export (except to EFTA) - Normal declaration (normal procedure under Article 62 of the Code) EXA<br />

Export (except to EFTA) - Incomplete declaration (simplified procedure<br />

under Article 76(1)(a) of the Code) EXB<br />

Export (except to EFTA) - Simplified declaration (simplified procedure<br />

under Article 76(1)(b) of the Code) EXC<br />

Export (except to EFTA) - Normal declaration (such as referred to under code A) lodged before<br />

the declarant is in a position to present the goods. EXD<br />

Export (except to EFTA) - Incomplete declaration (such as referred to under code B) lodged before<br />

the declarant is in a position to present the goods. EXE<br />

Export (except to EFTA) - Simplified declaration (such as referred to under code C) lodged before<br />

the declarant is in a position to present the goods. EXF<br />

Export (except to EFTA) - Supplementary declaration under a simplified procedure covered by B EUX<br />

Export (except to EFTA) - Supplementary declaration under a simplified procedure covered by C EUY<br />

Export (except to EFTA) - Supplementary declaration under a simplified procedure<br />

under Article 76(1)(c) of the Code (entry of the goods in the records) EUZ<br />

Import - Normal declaration (normal procedure under Article 62 of the Code) IMA<br />

Import - Incomplete declaration (simplified procedure under Article 76(1)(a) of the Code) IMB<br />

Import - Simplified declaration (simplified procedure under Article 76(1)(b) of the Code) IMC<br />

Import - Normal declaration (such as referred to under code A) lodged before<br />

the declarant is in a position to present the goods. IMD<br />

Import - Incomplete declaration (such as referred to under code B) lodged before<br />

the declarant is in a position to present the goods. IME<br />

Import - Simplified declaration (such as referred to under code C) lodged before<br />

the declarant is in a position to present the goods. IMF<br />

Import - Supplementary declaration under a simplified procedure covered by B IMX<br />

Import - Supplementary declaration under a simplified procedure covered by C IMY<br />

Import - Supplementary declaration under a simplified procedure<br />

under Article 76(1)(c) of the Code (entry of the goods in the records) IMZ<br />

Other ZZZ<br />

PROCEDURE REQUESTED N 2 For possible values see Annex 38 Implementing Provisions (Box 37.1, first two-digits)<br />

Common code values for AES/ECS:01<br />

02<br />

07<br />

10<br />

11<br />

21<br />

22<br />

23<br />

Page 262/276


Annex 7<br />

AES – Reference Data<br />

31<br />

40<br />

41<br />

42<br />

43<br />

45<br />

48<br />

49<br />

51<br />

53<br />

61<br />

63<br />

68<br />

71<br />

76<br />

77<br />

78<br />

91<br />

PREVIOUS PROCEDURE n 2 For possible values see Annex 38 Implementing Provisions (Box 37.1, second two-digits)<br />

Common code values for AES/ECS:<br />

00<br />

01<br />

02<br />

07<br />

10<br />

11<br />

21<br />

22<br />

23<br />

31<br />

40<br />

41<br />

42<br />

43<br />

45<br />

48<br />

49<br />

51<br />

53<br />

54<br />

61<br />

Page 263/276


Annex 7<br />

AES – Reference Data<br />

REPRESENTATIVE STATUS CODE n 1 See also Annex 38 Implementing Provisions (Box 14).<br />

Common code values for AES/ECS:1 = Declarant<br />

2 = Representative – direct representation<br />

3 = Representative – indirect representation<br />

63<br />

68<br />

71<br />

76<br />

77<br />

78<br />

91<br />

92<br />

RISK ANALYSIS RESULT CODE an ..5 Some code values will be defined at Common Domain level, other values can<br />

be defined at National Domain level.<br />

Values at common domain level (codes to be used for C-Messages) will be defined by the Risk<br />

Management Framework project.<br />

ROLE an 3 <strong>Customs</strong> Office performing one or more precise role(s).<br />

Following code values of the <strong>Customs</strong> Office List (COL) can be used for AES/ECS:<br />

EXC = Excise<br />

EXP = Office of Export<br />

EXT = Office of Exit<br />

EXL = Office of Lodgement Exit<br />

ETR= Office of Exit for Transit<br />

SPECIFIC CIRCUMSTANCE INDICATOR a 1 Regulation 1875/2006, Annex 30A.<br />

Possible values for AES/ECS:<br />

A = Postal <strong>and</strong> express consignments<br />

B = Ship <strong>and</strong> aircraft supplies<br />

E = Authorised economic operators<br />

STATISTICAL VALUE CURRENCY See 'CURRENCY CODE'<br />

Page 264/276


Annex 7<br />

AES – Reference Data<br />

STORING FLAG n 1 See 'FLAG'<br />

SUMMARY DECLARATION REJECTION<br />

REASON CODE<br />

n ..2 Possible values for AES/ECS:<br />

3 = MRN unknown<br />

4 = Other reasons<br />

SYSTEM UNAVAILABILITY TYPE a 1 Values:<br />

S = Scheduled Unavailability<br />

U = Unscheduled Unavailability<br />

N = Business service not implemented<br />

TARIC CODE an 2 TARIC code, see explanation for 'Commodity code', Box 33.2.<br />

TARIC FIRST ADDITIONAL CODE an 4 TARIC code, see explanation for 'Commodity code', Box 33.3.<br />

TARIC SECOND ADDITIONAL CODE an 4 TARIC code, see explanation for 'Commodity code', Box 33.4.<br />

TIN<br />

(TRADER IDENTIFICATION NUMBER)<br />

an ..17 The Trader Identification Number shall be defined on national level.<br />

However, the first 2 digits shall consist of the country code.<br />

TRAFFIC TYPE an ..3 Type of traffic for which a given <strong>Customs</strong> Office has an appropriate competency. The Codes are part of<br />

the <strong>Customs</strong> Office List (COL).<br />

Values:<br />

P = Sea traffic<br />

V = Rail traffic<br />

R = Road Traffic<br />

AIR = Airport<br />

C = River traffic<br />

PP = Pipeline<br />

N/A = Not Applicable<br />

TRANSPORT CHARGES - METHOD OF<br />

PAYMENT<br />

a 1 Commission Regulation (EC) 1875/2006, Annex 30A.<br />

Common code values for AES/ECS:<br />

A = Payment in cash<br />

B = Payment by credit card<br />

C = Payment by cheque<br />

Page 265/276


Annex 7<br />

AES – Reference Data<br />

TRANSPORT MODE<br />

(TRANSPORT MODE AT DEPARTURE)<br />

(TRANSPORT MODE AT BORDER)<br />

(INLAND TRANSPORT MODE)<br />

D = Other<br />

H = Electronic credit transfer<br />

Y =Account holder with carrier<br />

Z = Not pre-paid<br />

n ..2 See also Annex 38 Implementing Provisions. The 2-digit codes from Annex A9 to Appendix III of the<br />

Transit convention shall not be used for Export operations.<br />

Mode of transport corresponding to the active means of transport (box 25 <strong>and</strong> 26).<br />

Possible values are:<br />

1 = Sea transport<br />

2 = Rail transport<br />

3 = Road transport<br />

4 = Air transport<br />

5 = Postal consignment<br />

7 = Fixed transport installations<br />

8 = Inl<strong>and</strong> waterway transport<br />

9 = Own propulsion<br />

TYPE OF TAX an 3 See also Annex 38 Implementing Provisions (box 47).<br />

Common code values for AES/ECS::<br />

A00 = <strong>Customs</strong> duties on industrial productsA10 = <strong>Customs</strong> duties on agricultural productsA20 =<br />

Additional duties<br />

A30 = Definitive antidumping duties<br />

A35 = Provisional antidumping duties<br />

A40 = Definitive countervailing duties<br />

A45 = Provisional countervailing duties<br />

B00 = VAT<br />

B10 = Compensatory interest (VAT)<br />

B20 = Interest on arrears (VAT)<br />

C00 = Export taxes<br />

C10 = Export taxes on agricultural products<br />

D00 = Interest on arrears<br />

D10 = Compensatory interest (I.e. Inward processing)<br />

E00 = Duties collected on behalf of other countries<br />

TYPE OF TRANSPORT CROSSING n ..2 To be defined at national level (box 21).<br />

BORDER<br />

UN DANGEROUS GOODS CODE n 4 Codes from the UNDG (United Nations Dangerous Goods list) shall be used.<br />

UNIT OF MEASURE a 3 Values:<br />

HTL = hectolitre<br />

KGM = kilogram<br />

PCE = pieces or items<br />

Page 266/276


Annex 7<br />

AES – Reference Data<br />

WAREHOUSE TYPE a 1 See also Annex 38 (box 49) <strong>and</strong> Art. 525 (a1) Implementing Provisions<br />

A = Public <strong>Customs</strong> warehose under responsibility of the warehousekeeper<br />

B = Public <strong>Customs</strong> warehose under responsibility of the depositor<br />

C =Private warehouse, other than D <strong>and</strong> E<br />

D =Private warehouse, where release for free circulation is made by way of the<br />

local clearance procedure <strong>and</strong> may be granted on the basis of the<br />

nature, the customs value <strong>and</strong> the quantity of the goods to be taken<br />

into account at the time of their placing under the arrangements<br />

E = Private warehouse, where the arrangements apply although the goods need not<br />

be stored in a place approved as a customs warehouse<br />

F = Public <strong>Customs</strong> warehouse operated by customs authority<br />

Y = Non-customs warehouse<br />

Z = Free zone or free warehouse;<br />

Page 267/276


Annex 8<br />

AIS – Reference Data<br />

Annex 7 – AIS Reference Data<br />

Page 268/276


Annex 8<br />

AIS – Reference Data<br />

NAME FORMAT LENGTH VALUES + TEXT<br />

ADDITIONAL INFORMATION ID an ..5 Codes for SPECIAL MENTIONS (Box 44), see Regulation 1875/2006, Annex 30A.<br />

- Common Code values for AIS/ICS:<br />

10600 = Negotiable Bill of lading 'to order blank endorsed<br />

- Additional Codes can also be defined at national level.<br />

AEO CERTIFICATE TYPE an 4 Code for the first 4 digits of 'Document Reference (Box 44)' specifying the AEO certificate type:<br />

AEOC = AEO certificate – <strong>Customs</strong> simplifications<br />

AEOF = AEO certificate – Security <strong>and</strong> safety<br />

AEOS = AEO certificate – <strong>Customs</strong> simplifications/security <strong>and</strong> safety<br />

AMENDMENT REJECTION MOTIVATION<br />

CODE<br />

The code will be used in case the TIN will not be available or not known by all involved <strong>Customs</strong><br />

administrations (Pre-EORI) only.<br />

The Code is also used in the AEO system.<br />

n 1 Used to specify the Amendment Rejection Motivation in IE305.<br />

Entry summary declarations:<br />

Since amendment requests can be sent to another Member State than the one to whom the initial<br />

declaration was sent, common codes for AIS/ICS shall be used.<br />

Common Code values for AIS/ICS:<br />

BUSINESS FUNCTIONALITY CODE a 1<br />

1 = Trader not allowed to amend*<br />

2 = Cancelled<br />

3 = MRN unknown<br />

4 = Other reasons<br />

5 = Goods entered already<br />

6 = Goods released for subsequent procedure already<br />

9 = Goods under control<br />

* If the Trader sending the amendment request is neither the Person lodging the summary declaration nor<br />

his Representative)<br />

Is used to identify the unavailability/availability of a given business<br />

functionality in a Member State:<br />

For the purpose of ICS phase 1, following codes are to be added:<br />

O = Accept sending Entry summary declarations to an Office of First Entry in<br />

another<br />

MS<br />

Page 269/276


Annex 8<br />

AIS – Reference Data<br />

P = Accept receiving Entry summary declarations lodged at an Office of<br />

Lodgement in another MS<br />

U = Entry <strong>Processing</strong><br />

V = Lodgement<br />

W = All Functionalities<br />

COMBINED NOMENCLATURE n ..8 Commodity Code (Box 33.1), see Annex 37/38 Implementing Provisions<br />

The 4, 6 or 8 first digits of the Combined Nomenclature Code shall be used, according to the Rules<br />

specified in FTSS.<br />

COUNTRY (CODE) a 2 ISO alpha-2 country codes based on Commission Regulation (EC) No 1833/2006 (yearly updated).<br />

COUNTRY CODE OF OFFICE OF FIRST<br />

ENTRY DECLARED<br />

a 2 ISO alpha-2 country codes based on Commission Regulation (EC) No 1833/2006 (yearly updated).<br />

Only the Country Codes for EU Member States shall be used.<br />

COUNTRY OF ROUTING CODE a 2 See 'COUNTRY (CODE)'<br />

CUSTOMS INTERVENTION CODE an.. 4 Used to specify the type of customs control in case <strong>Customs</strong> decide to intervene.<br />

Following common codes shall be used:<br />

A001 = Goods not to be loaded<br />

P001 = General physical control of goods<br />

D001 = Documentary control<br />

S001 = Seals control<br />

Other nationally defined codes may be used additionally.<br />

CUSTOMS STATUS an.. 5 <strong>Declaration</strong> type used to specify the customs status of goods:<br />

Following code values can be used for AIS/ICS:<br />

C = Goods for which the community status can be demonstrated<br />

F = Goods for which the community status can be demonstrated, consigned to or originating<br />

in a part of the community customs territory where the provisions of directive<br />

77/388/EEC do not apply<br />

N = All other goods<br />

T1 = External Community transit<br />

T2 = Common transit procedure covering Community goods<br />

TD = Goods already placed under transit or carried under inward processing, customs warehouse<br />

or temporary admission procedure<br />

TF = Goods placed under the internal community transit procedure in accordance with Art. 340c (1)<br />

Page 270/276


Annex 8<br />

AIS – Reference Data<br />

X = Community goods to be exported, not under transit<br />

CUSTOMS OFFICE REFERENCE<br />

NUMBER<br />

an 8 <strong>Customs</strong> Office Reference Number as defined in Annex 37c Implementing Provisions.<br />

See also <strong>Customs</strong> Office List (COL)<br />

DOCUMENT TYPE an ..4 Used to specify the produced document/certificates as defined in TARIC (Box 44).<br />

Following of the code values shall be marked as 'transport documents' for the purpose of Condition<br />

564/567:<br />

N235<br />

N271<br />

N703<br />

N704<br />

N705<br />

N714<br />

N722<br />

N730<br />

N740<br />

N741<br />

N750<br />

N760<br />

N785<br />

N787<br />

N952<br />

N955<br />

ENTRY REJECTION MOTIVATION CODE an ..2 To be defined at national level<br />

ERROR TYPE n 2 Indicates the type of (validation) error.<br />

The technical codes will be specified in the Design Document for National<br />

Import Application (DDNIA) <strong>and</strong> in CS/RD.<br />

Page 271/276


Annex 8<br />

AIS – Reference Data<br />

FLAG n 1 Used for attributes that can have a positive either a negative value.<br />

Code values:<br />

0 = No<br />

1 = Yes<br />

IMPORT OPERATION STATE TYPE an ..3 Some values are defined at Common Domain level, other values can be<br />

defined at National Domain level.<br />

Values will be documented in the Design Document for National Import<br />

Application (DDNIA).<br />

INFORMATION TYPE n.. 2 Used to specify the requested or provided type of information:<br />

1 = Common risk analysis results <strong>and</strong> appropriate ENS data<br />

2 = Full ENS including common risk analysis results<br />

ITEM NUMBER REJECTION REASON<br />

CODE<br />

n ..2 Common code values for AIS/ICS:<br />

4 = Other reasons<br />

5 = Item unknown<br />

6 = Item already presented for Entry<br />

7 = Item already arrived at Entry<br />

8 = Item under control<br />

9 = Item released for Entry<br />

KIND OF PACKAGES an 2 See Annex 38 Implementing Provisions (Box 31). Based on UNECE Recommendation No. 21/Rev. 4 –<br />

May 2002.<br />

LANGUAGE CODE / LNG a 2 Language Code (LNG) used to define the language used for declaration purposes <strong>and</strong> for free text<br />

information (ISO Alpha 2 Codification – ISO 639 / 1988), see Annex 37c Implementing Provisions.<br />

MOVEMENT REFERENCE NUMBER<br />

(MRN)<br />

an 18 Movement Reference Number used to identify each single Import transaction.<br />

The Structure of the MRN for Transit is documented in Annex 45a, Chapter II Implementing Provisions<br />

<strong>and</strong> Annex 8 to Appendix A3 of FTSS. The MRN for Export (AES/ECS) is documented in Annex 45c,<br />

Chapter II Implementing Provisions. The same structure shall be used for Import (AIS/ICS).<br />

RISK ANALYSIS RESULT CODE an ..5 The last digit of the an..5 code are introduced <strong>and</strong> managed in the CS/RD only. The other digits will be<br />

allocated <strong>and</strong> managed by the risk applications <strong>and</strong> are not transparent for ICS, ECS <strong>and</strong> NCTS.Last<br />

digit: Following codes shall be used:<br />

A: No load notification to be sent (can be used in ICS only)<br />

Page 272/276


Annex 8<br />

AIS – Reference Data<br />

B: Common risk analysis result for which an immediate action is required at the Office of First Entry<br />

C: Common risk analysis result to be communicated to the Office(s) of Subsequent Entry in other EU<br />

Member States<br />

N: National risk analysis results. ('N' shall also be used in case of national profile r<strong>and</strong>om risk<br />

analysis).<br />

Z: No risk analysis results available<br />

0 (zero): No risk identified<br />

Digit 1-4:<br />

o If the last digit is 'A', 'B' or 'C', then the common codes values defined by<br />

the Risk Management Framework project shall be used;<br />

o If the last digit is 'N', then the code values can be defined at National<br />

Domain level;<br />

o If the last digit is 'Z' or 0 (zero), then the digits 1-4 shall not be used.<br />

ROLE an 3 <strong>Customs</strong> Office performing one or more precise role(s).<br />

Following code values of the <strong>Customs</strong> Office List (COL) can be used for AIS/ICS:<br />

ENL: Office of Lodgement Entry<br />

ENT: Office of (first or subsequent)Entry<br />

SPECIFIC CIRCUMSTANCE INDICATOR a 1 Regulation 1875/2006, Annex 30A.<br />

Possible code values for AISS/ICS:<br />

A = Postal <strong>and</strong> express consignments<br />

C = Road mode of transport<br />

D = Rail mode of transport<br />

E = Authorised economic operators<br />

B = is used for 'Exit summary declarations –ship <strong>and</strong> aircraft supplies' <strong>and</strong> can not be used in AIS/ICS<br />

SUMMARY DECLARATION REJECTION<br />

REASON CODE<br />

n ..2 Possible code values for AIS/ICS:<br />

3 = MRN unknown<br />

4 = Other reasons<br />

6 = Movement already presented for Entry<br />

7 = Movement already arrived at Entry<br />

Page 273/276


Annex 8<br />

AIS – Reference Data<br />

8 = Movement already released for Entry<br />

SYSTEM UNAVAILABILITY TYPE a 1 Code values:<br />

S = Scheduled Unavailability<br />

U = Unscheduled Unavailability<br />

N = Business service not implemented<br />

TIN<br />

(TRADER IDENTIFICATION NUMBER)<br />

an ..17 The Trader Identification Number shall be defined on national level.<br />

However, the first 2 digits shall consist of the country code.<br />

TRAFFIC TYPE an ..3 Type of traffic for which a given <strong>Customs</strong> Office has an appropriate competency. The Codes are used in<br />

the <strong>Customs</strong> Office List (COL).<br />

Code values:<br />

P = Sea traffic<br />

V = Rail traffic<br />

R = Road Traffic<br />

AIR = Airport<br />

C = River traffic<br />

P/P = Pipeline<br />

N/A = Not Applicable<br />

TRANSPORT CHARGES - METHOD OF<br />

PAYMENT<br />

TRANSPORT MODE<br />

(TRANSPORT MODE AT BORDER)<br />

a 1 Commission Regulation (EC) 1875/2006, Annex 30A.<br />

Common code values for AIS/ICS:<br />

A = Payment in cash<br />

B = Payment by credit card<br />

C = Payment by cheque<br />

D = Other<br />

H = Electronic credit transfer<br />

Y =Account holder with carrier<br />

Z = Not pre-paid<br />

n ..2 See also Annex 38 Implementing Provisions. The 2-digit codes from Annex A9 to Appendix III of the<br />

Transit convention shall not be used for Import operations.<br />

Mode of transport corresponding to the active means of transport (box 25 <strong>and</strong> 26).<br />

Possible values are:<br />

1 = Sea transport<br />

2 = Rail transport<br />

3 = Road transport<br />

4 = Air transport<br />

5 = Postal consignment<br />

7 = Fixed transport installations<br />

8 = Inl<strong>and</strong> waterway transport<br />

9 = Own propulsion<br />

Page 274/276


Annex 8<br />

AIS – Reference Data<br />

UN DANGEROUS GOODS CODE an 4 Codes from the UNDG (United Nations Dangerous Goods list) shall be used.<br />

Page 275/276


Annex 8<br />

AIS – Reference Data<br />

Page 276/276

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!