This document provides the semantic mapping description of information on the characteristics or attributes of Low Value Consignments (LVC) which parties in the digital commercial value chain across-borders are called upon to handle, compliant to the EU VAT Ecommerce Package as well as the UPU-WCO customs model.<\/p>\n
This document is limited to LVC, the logical definition of an electronic message, which supports the communication of information about postal items with a unique transport unit identifier.<\/p>\n
While different customs processes apply to LVC (goods ? \u20ac150), and consignments exceeding an intrinsic value of > \u20ac150, this technical specification only applies to LVC. Therefore, it applies to the collection of import duties (VAT) and not to customs fees.<\/p>\n
The document defines both EDIFACT directory 00A and XML implementations to bridge in a semantic mapping between UPU M33 ITMATT messages and the EU customs data model and its super-reduced data set, that can be used to convey item-level data for use in customs processing applications.<\/p>\n
The document specifies that the supply of certain attribute values, segments and tags is mandatory (M), whilst the supply of other attributes, segments and tags is specified as optional (O).<\/p>\n
This document separates the financial, the data-elements and the physical flow of low value consignments. Further it defines the use of unique transport identifiers, unique transaction identifiers and the IOSS VAT Identification number.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 4 Data Mapping 4.1 General <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4.2 Simplified procedure for the collection of import duties <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4.3 Mapping the UCC-DA, ANNEX B column H7 Super-Reduced Data set against the UPU-WCO Postal Data model <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4.4 Semantic mapping: WHAT, WHO, HOW, WHY <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Annex A (informative)Illustrative Semantic mapping: Postal Data Elements (CN23, ITMATT, EDIFACT, XML) <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | Annex B (informative)Mapping Semantic messages to Postal and Non-postal environment <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | Annex C (informative)Stakeholders and Information Exchanges based on UN\/EDIFACT C.1 General <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | C.2 Important data elements based on semantic approach C.2.1 General C.2.2 Flow 1: Shipping Notification I – Origin Carrier to Destination Carrier <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | C.2.3 Flow 2: Shipping Notification II – Destination Carrier to Destination Customs <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | C.2.4 Flow 3: Customs Confirmation I – Destination Customs to Destination Carrier <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | C.2.5 Flow 4: Customs Confirmation II – Destination Carrier to Origin Carrier <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | C.2.6 Flow 5: Despatch Information I – Origin Carrier to Destination Carrier <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | C.2.7 Flow 6: Despatch Information II – Destination Carrier to Destination Customs <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | C.2.8 Flow 7: Cross Border Transport Instruction – Origin Carrier to X border Transport Service Provider <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | C.2.9 Flow 8: Consignment Information – X border Transport Service Provider to Destination Customs <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | Annex D (informative)Stakeholder and Information Exchanges based on WCO\/UPU flowchart and messaging model D.1 General <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | D.2 WCO – UPU Flow details D.2.1 General D.2.2 Flow 1: CN23 data <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | D.2.3 Flow 2: CN23 data to border agency D.2.4 Flow 3: Assessment complete \/Referral notification <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | D.2.5 Flow 4: Assessment complete or Referral message to origin post D.2.6 Flow 4+: Message from origin post to destination post after receiving the referral D.2.6.1 General D.2.6.2 RFI message (Request for Information) <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | D.2.6.3 RFS message (Request for Screening) <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | D.2.6.4 DNL message (Do Not Load) D.2.7 Flow 4++: Data transmitted by Destination post to destination customs after referrals D.2.8 Flow 5: Dispatch data from origin to destination post <\/td>\n<\/tr>\n | ||||||
| 85<\/td>\n | D.2.9 Flow 6: Receptacle ID and item ID list to customs D.2.10 Flow 7: Consignment data to airline D.2.11 Flow 8: Manifest from airline to customs <\/td>\n<\/tr>\n | ||||||
| 87<\/td>\n | Annex E (informative)ANNEX B of the UCC-DA, changes for the inclusion of the H7 data set <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Requirements for electronic advanced data (EAD) in postal operations, in particular compliant to security and customs requirements<\/b><\/p>\n |