EDICOM 2001 JAKARTA – 4th October 2001 AFACT IIC Customs EDI Project Siti Aminah Abdullah IIC Chair

EDICOM Jakarta2 Project Goals Ultimate goal of project –Exchange of Customs EDI data for: Trade Facilitation & Expediting Clearance Enforcement Statistics High-level timing goals –Pilot by end 1999 –Live implementation by early 2000

EDICOM Jakarta3 Project Description Exchange of EDI Information between Customs Administrations –Exchange of Export Declaration (CUSDEC) –Selected Information based on need and confidentiality agreements –May extend to other documents and information in the future

EDICOM Jakarta4 Legal Framework AFACT IIC –Authority –Implementation Standards & Guidelines –Project Management Pilot –Bilateral Memorandum of Understanding Live –Bilateral Agreement with Annexes

EDICOM Jakarta5 Technical Overview Standards –Developed and reviewed by the IIC-TWG (Technical Working Group) –EDI Standards using EDIFACT D95B with Asia Region guidelines (RECES) –VAN-to-VAN network over X.400 –WCO D95B Mapping Guide & APEC Code Harmonization Guide

EDICOM Jakarta6 Network Overview X.400 VANVAN Customs Customs

EDICOM Jakarta7 Process Overview Local standard export CUSDEC Regional standard export CUSDEC 1. Map to regional CUSDEC standard 2. Cross-reference from local codes to harmonized codes (using tables) 3. Convert character set, if necessary (using tables where possible) Local standard information Regional standard export CUSDEC 7. Map to local requirements 6. Cross-reference from harmonized codes to local codes (using tables) 5. Convert character set, if necessary (using tables where possible) 4. Transmitted Optional StepsRequired Steps

EDICOM Jakarta8 Process Overview Sending Country –Decides what information may be released to other countries –Maps local CUSDEC into region standard prior to transmission Message Structure Data Elements (group locations and qualifier codes) Language and Character Sets (translate non-ASCII to ASCII for descriptive text-type data elements) Code Set Normalization (tabled cross-reference)

EDICOM Jakarta9 Process Overview Receiving Country –Receives regional-standard export CUSDEC from sending country –Uses message according to local requirements –May re-map message for local standards Message Structure Data Elements (group locations and qualifier codes) Language and Character Sets (translate ASCII to non- ASCII for descriptive text-type data elements) Code Set Normalization (tabled cross-reference)

EDICOM Jakarta10 Unique Referencing Unique Reference Number (URN) is required for identifying consignments EDIFACT Representation WCO Guidelines - WCO UCR Group b1. FOR MORE INFO... UCN Unique Consignment Reference Number I nternationally unique number used by Importers / Exporters to identify the consignment Format = Last digit of calendar year + Country Code + Exporter ID + Exporter Reference RFFUCN 9MY

EDICOM Jakarta11 Current Status Overview of current progress –Standards and guidelines established –Level 2 (VAN-to-VAN) testing in progress or completed –Draft standard MOU and Agreement prepared –MOU and Level 3 (Customs-to-Customs) pilot message exchange between Korea & Malaysia

EDICOM Jakarta12 Current Status Overview of current progress –Other countries intending to participate: Chinese Taipei India Indonesia Islamic republic of Iran Pakistan

EDICOM Jakarta13 Current Status Korea – Malaysia Pilot Exchange: –Bilateral message exchange between Customs Administrations of Korea & Malaysia –MOU signed on –Confidential (for Customs Administrations only) –Two Joint project team (JPT) meetings held to date

EDICOM Jakarta14 Current Status Korea – Malaysia Pilot Exchange: –Pilot exchange began on –Weekly exchange of export consignment declaration information –(export CUSDEC, EDIFACT D97A)

EDICOM Jakarta15 Current Status Korea – Malaysia Pilot Exchange: –Selected subset of 3 harmonised tariff codes each direction for direct shipments: Place of Loading/Discharge and Departure Date Total Weight (in KGM) Reference information (used to build UCI) House B/L (Korea)

EDICOM Jakarta16 Current Status Korea – Malaysia Pilot Exchange: –Selected subset of 3 harmonised tariff codes each direction for direct shipments: Trader registration # + invoice # (Malaysia) Transport details (vessel call sign, voyage number, vessel registration, vessel name) Consignor and consignee name & address Line item information (HS code, goods description, quantity measurements)

EDICOM Jakarta17 Data Exchange Issues Resolved UN/EDIFACT version Code Qualifiers Data formats, lengths and decimal usage Data exchange issues unresolved: –Common UCI to link up import/export data –Unavailability of information (eg. Malaysia House B/L info & Korea party identification and invoice no info) –Localised usage of data (eg. Malaysia vessel ID assigned by local port authority)

EDICOM Jakarta18 Conclusion Successful and reliable exchange of export consignment declaration data No major technical problems encountered Minor problems revolved around non- availability and/or local use of some data elements Clear case of a need for internationally adopted use of a Unique Consignment Identifier (UCI)

Thank You! Any questions and comments?