Message Implementation Guide - FOD Financiën · FOD FIN Belgium and IBM Corporation 2014 MASP.be Message Implementation Guide Advanced Intervention Notification message IE351 Document:

FOD FIN Belgium and IBM Corporation 2014MASP.be

Message Implementation Guide

Advanced Intervention Notification message

IE351

Document: MASP.be_ICS_MIG Advanced Intervention_2.2.odm Date: 25/06/2015Version: 2.2

Owner: FOD FIN AAD&A Status: ReleasedSubject: Message Implementation Guide Advanced Intervention Notification

messagePage 1 of 22


1 Document History

1.1 Document LocationThis is a snapshot of an on-line document. Paper copies are valid only on the day they are printed. Refer to the author if you are in any doubt about the currency of this document.

1.2 Revision History

Date of this revision Date of next revision

25/06/2015 (date)

Revision number

Revision date

Summary of changes Changes marked

00.01 20/05/2008 Initial version created (N)

00.02 21/05/2008 Added sequence diagram, field explications (N)

00.03 27/05/2008 Review Wim Baetens (N)

0.04 03/06/2008 Internal review (N)

0.05 30/07/2008 Update XML mapping section (N)



messagePage 2 of 22


Revision number

Revision date

Summary of changes Changes marked

0.06 21/08/2008 Merged internal reviews (N)

0.07 28/08/2008 Resolved aviation mapping (N)

0.08 10/09/2008 Correct CUSRES Stop segments + cosmetic changes (N)

1.00 10/09/2008 Renamed to version 1.00 (Content unchanged) (N)

1.01 28/01/2009 Added mapping to XML (N)

1.02 24/04/2009 Alignment with DG TAXUD KEL 0.18 (N)

1.10 01/02/2011 Removed obsolete CARGOIMP sectionRemoved support for EDIFACT mappings

(N)

2.0 15/01/2014 Extract content from CSE database(documentary change only)

(N)

2.1 06/05/2014 Alignment with DG TAXUD KEL 0.27 (N)

2.2 25/06/2015 Alignment with DG TAXUD RFC-list 28 (N)

1.3 ApprovalsThis document requires following approvals. Signed approval forms are filed in the Quality section of the PCB.

Name Title

Roger Beeckman Program Manager AAD&A

1.4 DistributionThis document has been distributed to

Name Title

Roger Beeckman Program Manager AAD&A

Wim Baetens ICT-Project manager MASP-ICS (AAD&A)

Bernard Van Acker Lead Architect IBM



messagePage 3 of 22


Contents1 Document History.......................................................................................................................................... 2

1.1 Document Location................................................................................................................................ 21.2 Revision History..................................................................................................................................... 21.3 Approvals............................................................................................................................................... 31.4 Distribution............................................................................................................................................. 3

2 Introduction.................................................................................................................................................... 52.1 Purpose................................................................................................................................................. 52.2 References............................................................................................................................................ 52.3 Acronyms............................................................................................................................................... 6

3 Functional description.................................................................................................................................... 83.1 Purpose................................................................................................................................................. 83.2 Process descriptions.............................................................................................................................. 83.3 Sequence diagram................................................................................................................................. 83.4 Timing constraints.................................................................................................................................. 9

4 Message structure....................................................................................................................................... 104.1 Primary and response message structure...........................................................................................104.2 Technical message structure...............................................................................................................13

5 XML mapping............................................................................................................................................... 146 Applicable rules and conditions.................................................................................................................... 187 Field explanations........................................................................................................................................ 19

FiguresFigure 1: No load notification at the Office of first Entry....................................................................................9



messagePage 4 of 22


2 IntroductionThis chapter identifies the document, describes the contents of the document, and states its purpose.

2.1 PurposeThis Message Implementation Guide for IE351 describes how to implement the message and its related response message(s).1

2.2 ReferencesThis document refers to the following external documents and/or Web sites:

ID Reference Title/URL v

A1 Process definition Taxud: Doc1043-FSS_AIS Addendum-Corrigendum 1-2013 final_main.doc

1.00

A2 Functional message specification Taxud: Doc1043-FSS_AIS Addendum-Corrigendum 1-2013 final_B2_ messages.doc

1.00

A3 Codelists Taxud: DDNIA-Appendix C.pdf 12.20

A4 Design document Taxud: DDNIA-Main Document.doc 12.20

A5 XML mapping Taxud: DDNIA-Appendix R.pdf 12.20

A6 [removed] [removed]



A9 PLDA B2B Functional Documentation http://plda.fgov.be/nl/documentatie#12 1.1

A10 PLDA B2B Synthese Documentation http://plda.fgov.be/nl/documentatie#11 1.1


A12 B2B Technical documentation for PLDA http://fiscus.fgov.be/interfdanl/bedrijven/e_diensten/paperless/bestanden/PLDA_B2B_Communication_Technical_Documentation%20-%20v1.1.3.doc

1.1.3


A14 Conditions and Rules Import messages MASP.be_ICS_MIG Conditions and Rules.pdf 2.40

1 If applicable



messagePage 5 of 22

http://plda.fgov.be/nl/documentatie#12

http://fiscus.fgov.be/interfdanl/bedrijven/e_diensten/paperless/bestanden/PLDA_B2B_Communication_Technical_Documentation%20-%20v1.1.3.doc



http://plda.fgov.be/nl/documentatie#11


2.3 Acronyms

Acronym Description

AEO Authorised Economic Operator

AIS Automated Import System

API Application Programming Interface

CC/IP Customs Code and Implementing Provisions

CCN/CSI Common Communications Network / Common Systems Interface

CCN-TC Common Communications Network – Technical Centre

CDCA Centrally Developed Customs Application

COL Customs Office List

CS/MIS Central Services/Management Information System

DDCOM Design Document for Common Operations and Methods

DDNA Design Documentation for National Applications

DDNIA Design Documentation for National Import Applications

DDNTA Design Documentation for National Transit Applications

DDNXA Design Documentation for National Export Applications

DTI Direct Trader Input

EBP Elementary Business Process

ECS Export Control System

EDI Electronic Data Interchange

EDIFACT EDI for Administration, Commerce and Transport

EFTA European Free Trade Association

ENS Entry Summary Declaration

EORI Economic Operator Registration and Identification

FTSS Functional Transit System Specification

ICS Import Control System

IE Information Exchange

IT Information Technology

MS Member State

NA National Administration

NCA National Customs Application

NCTS New Computerised Transit System

NICA National Import Control Application



messagePage 6 of 22


Acronym Description

PAN Pre-Arrival Notification

RD Reference Data

RFC Request for change

RFCL Request for change list

STTA Standard Transit Test Application

TTA Testing Transit Application

TTSS Technical Transit System Specification

XML eXtensible Mark-up Language



messagePage 7 of 22


3 Functional description

3.1 PurposeThe Office of First Entry sends the advanced intervention notification (IE351) to the Trader after collection of risk analysis data from the entry summary declaration. When a certain risk level is detected, traders with AEO-status may be warned in advance that certain goods will be subject to customs control (=preventive measures). For maritime, containerised cargo, the IE351 message functions as a so-callled ‘no-load notification’, and will be sent for the highest risk levels (=prohibitive measures). Such risk are considered high enough to deny access to the EU. However, considering the impact of such a situation, it should be noted that such messages will be sent only in extreme circumstances.

3.2 Process descriptionsThe IE351 message is sent to the trader in the ICS Phase & process PROCESS ENTRY SUMMARY DECLARATION AT OFFICE OF FIRST ENTRY CO1B(SUM).

ICS executes a risk analysis verification using the information coming from the Entry Summary Declaration. Where risk is identified, the competent services of the Customs shall be alerted prior to the sending out of the advanced intervention notification (IE351) and prior to the forwarding of the data to the Offices of subsequent Entry (if any).

Based on the risk analysis, following cases are to be distinguished:

• Last digit of the risk analysis result code = 'A': The Office of first Entry shall send a no load notification (IE351) to the appropriate Traders in order to prevent goods to be loaded at the port of loading. This is an extremely rare case in which a very high risk is identified.

• Last digit of the risk analysis result code = 'B': Common risk for which an immediate action is required at the Office of first Entry is identified;

• Last digit of the risk analysis result code = 'C': Common risk to be communicated to the Office(s) of subsequent Entry in other EU Member States is identified;

• Last digit of the risk analysis result code = 'N' (national risk analysis result): shall not be used.

• Last digit of risk analysis result code = '0' (zero): No risk identified.

The consequence for the trader is that the import movement is stopped.

3.3 Sequence diagramFollowing figure indicates the case where the Advanced Intervention Notification is notified to the business actors concerned after the ENS has been submitted to the Office of first Entry.



messagePage 8 of 22


If the safety and security risk analysis calls for a “No load” decision (risk analysis result code = ‘A’), the Officeof first Entry notifies the involed business actors via an Advanced Intervention Notification (IE351 message). The business actors are the Person Lodging the ENS (who has sent the ENS or an amendment request) andthe Trader at Entry (Carrier).

In case other customs interventions/controls are to be performed, the Office of first Entry may decide to inform the Person Lodging the ENS in advance with the IE351 message if he is an AEO.

The IE351 is not sent in direct reply of a IE315 message (the Entry Summary Declaration sent by the trader) - even though the IE351 is sent after processing of the ENS by the Belgian Customs. Note that the IE351 can also be sent in relation to an amendment request (IE313).

3.4 Timing constraintsProhibitive measures: a “No load” IE351-message should be sent by Customs at the latest 24 hours after theENS has been lodged (in other words: right before loading starts)

Preventive measures: no specific timing constraints, but – if applicable – at the latest before the IE330 (=release for entry)



messagePage 9 of 22

Figure 1: No load notification at the Office of first Entry


4 Message structureThis section shows the structure for the primary and response message(s). The description for applicable rulesand conditions can be found in 6 Applicable rules and conditions.

4.1 Primary and response message structureIE351

MESSAGE

Data item Repetition Optionality Format Code list RC

1x R

Message sender an..35

Message recipient

Date of preparation n6

Time of preparation n4

Priority O a1

Test indicator n1 27 TR9085

Message identification R an..14

Message type an..6 60

Correlation identifier D an..14 TR9181

---HEADER


1x R

Reference number an..22 R891

Document/reference number an..21

Transport mode at border O n..2 18 R134

R826

Nationality D a2 8 C024

R134

Identity of means of transport crossing border O an..27 C017

C514

R134

Total number of items R n..5 R811

Commercial Reference Number O an..70 R134



messagePage 10 of 22


Conveyance reference number D an..35 R134

R843

TR0518

TR0519

Notification date and time R n12 R660

Declaration registration date and time R660

R661

Declaration Submitted Date and Time R660

---GOODS ITEM


999x D C571

Item number R n..5 R810

Commercial Reference Number O an..70 R134

------PRODUCED DOCUMENTS/CERTIFICATES


99x R147

Document type R an..4 13 R136

R809

Document reference an..35

Document reference LNG O a2 12 TR0099

------CONTAINERS


99x R818

Container number R an..17 R809

------(MEANS OF TRANSPORT AT BORDER) IDENTITY


999x O R818

Nationality a2 8

Identity of means of transport crossing border R an..27 C514

R809

Identity of means of transport crossing border LNG O a2 12 TR0099

---(LODGEMENT) CUSTOMS OFFICE






1x R833

Reference number R an8

---(REPRESENTATIVE) TRADER


1x O R895

Name D an..35 C501

Street and number C501

Postal code an..9 C501

City an..35 C501

Country code a2 8 C501

NAD LNG O 12 TR0099

TIN R an..17 R835

---(LODGING SUMMARY DECLARATION) PERSON


1x

Name D an..35 C501



City an..35 C501


NAD LNG O 12 TR0099

TIN R an..17 R837

---(FIRST ENTRY) CUSTOMS OFFICE


1x

Reference number an8

Expected date and time of arrival O n12 R134

R660

R666

---(ENTRY CARRIER) TRADER






1x R895

Name D an..35 C501



City an..35 C501


NAD LNG O 12 TR0099

TIN R an..17 R837

---CUSTOMS INTERVENTION


999x

Item Number concerned O n..5 R888

Customs Intervention code R an..4 108

Customs Intervention text O an..350

Customs Intervention LNG a2 12 TR0099

4.2 Technical message structureThe technical handling of the messages (headers, signature, connectivity) will not change in MASP.be. Therefore all documentation [A9] and [A10] is still relevant.

Specific message headers for sending/receiving messages are described in [A12].





5 XML mappingThe XML mapping is done according to the mapping rules in [A5].

IE351

Data group/item XML Tag

MESSAGE CDxxxA

MESSAGE.Message sender MesSenMES3

MESSAGE.Message recipient MesRecMES6

MESSAGE.Date of preparation DatOfPreMES9

MESSAGE.Time of preparation TimOfPreMES10

MESSAGE.Priority PriMES15

MESSAGE.Test indicator TesIndMES18

MESSAGE.Message identification MesIdeMES19

MESSAGE.Message type MesTypMES20

MESSAGE.Correlation identifier CorIdeMES25

MESSAGE - HEADER HEAHEA

MESSAGE - HEADER.Reference number RefNumHEA4

MESSAGE - HEADER.Document/reference number DocNumHEA5

MESSAGE - HEADER.Transport mode at border TraModAtBorHEA76

MESSAGE - HEADER.Nationality NatHEA001

MESSAGE - HEADER.Identity of means of transport crossing border IdeOfMeaOfTraCroHEA85

MESSAGE - HEADER.Total number of items TotNumOfIteHEA305

MESSAGE - HEADER.Commercial Reference Number ComRefNumHEA

MESSAGE - HEADER.Conveyance reference number ConRefNumHEA

MESSAGE - HEADER.Notification date and time NotDatTimHEA104





MESSAGE - HEADER.Declaration registration date and time DecRegDatTimHEA115

MESSAGE - HEADER.Declaration Submitted Date and Time DecSubDatTimHEA118

MESSAGE - GOODS ITEM GOOITEGDS

MESSAGE - GOODS ITEM.Item number IteNumGDS7

MESSAGE - GOODS ITEM.Commercial Reference Number ComRefNumGIM1

MESSAGE - GOODS ITEM - PRODUCED DOCUMENTS/CERTIFICATES PRODOCDC2

MESSAGE - GOODS ITEM - PRODUCED DOCUMENTS/CERTIFICATES.Document type DocTypDC21

MESSAGE - GOODS ITEM - PRODUCED DOCUMENTS/CERTIFICATES.Document reference

DocRefDC23

MESSAGE - GOODS ITEM - PRODUCED DOCUMENTS/CERTIFICATES.Document reference LNG

DocRefDCLNG

MESSAGE - GOODS ITEM - CONTAINERS CONNR2

MESSAGE - GOODS ITEM - CONTAINERS.Container number ConNumNR21

MESSAGE - GOODS ITEM - (MEANS OF TRANSPORT AT BORDER) IDENTITY IDEMEATRAGI970

MESSAGE - GOODS ITEM - (MEANS OF TRANSPORT AT BORDER) IDENTITY.Nationality

NatIDEMEATRAGI973

MESSAGE - GOODS ITEM - (MEANS OF TRANSPORT AT BORDER) IDENTITY.Identity of means of transport crossing border

IdeMeaTraGIMEATRA971

MESSAGE - GOODS ITEM - (MEANS OF TRANSPORT AT BORDER) IDENTITY.Identity of means of transport crossing border LNG

IdeMeaTraGIMEATRA972LNG

MESSAGE - (LODGEMENT) CUSTOMS OFFICE CUSOFFLON

MESSAGE - (LODGEMENT) CUSTOMS OFFICE.Reference number RefNumCOL1

MESSAGE - (REPRESENTATIVE) TRADER TRAREP

MESSAGE - (REPRESENTATIVE) TRADER.Name NamTRE1

MESSAGE - (REPRESENTATIVE) TRADER.Street and number StrAndNumTRE1

MESSAGE - (REPRESENTATIVE) TRADER.Postal code PosCodTRE1

MESSAGE - (REPRESENTATIVE) TRADER.City CitTRE1

MESSAGE - (REPRESENTATIVE) TRADER.Country code CouCodTRE1

MESSAGE - (REPRESENTATIVE) TRADER.NAD LNG TRAREPLNG





MESSAGE - (REPRESENTATIVE) TRADER.TIN TINTRE1

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON PERLODSUMDEC

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.Name NamPLD1

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.Street and number StrAndNumPLD1

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.Postal code PosCodPLD1

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.City CitPLD1

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.Country code CouCodPLD1

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.NAD LNG PERLODSUMDECLNG

MESSAGE - (LODGING SUMMARY DECLARATION) PERSON.TIN TINPLD1

MESSAGE - (FIRST ENTRY) CUSTOMS OFFICE CUSOFFFENT730

MESSAGE - (FIRST ENTRY) CUSTOMS OFFICE.Reference number RefNumCUSOFFFENT731

MESSAGE - (FIRST ENTRY) CUSTOMS OFFICE.Expected date and time of arrival ExpDatOfArrFIRENT733

MESSAGE - (ENTRY CARRIER) TRADER TRACARENT601

MESSAGE - (ENTRY CARRIER) TRADER.Name NamTRACARENT604

MESSAGE - (ENTRY CARRIER) TRADER.Street and number StrNumTRACARENT607

MESSAGE - (ENTRY CARRIER) TRADER.Postal code PstCodTRACARENT606

MESSAGE - (ENTRY CARRIER) TRADER.City CtyTRACARENT603

MESSAGE - (ENTRY CARRIER) TRADER.Country code CouCodTRACARENT605

MESSAGE - (ENTRY CARRIER) TRADER.NAD LNG TRACARENT601LNG

MESSAGE - (ENTRY CARRIER) TRADER.TIN TINTRACARENT602

MESSAGE - CUSTOMS INTERVENTION CUSINT632

MESSAGE - CUSTOMS INTERVENTION.Item Number concerned IteNumConCUSINT668

MESSAGE - CUSTOMS INTERVENTION.Customs Intervention code CusIntCodCUSINT665

MESSAGE - CUSTOMS INTERVENTION.Customs Intervention text CusIntTexCUSINT666





MESSAGE - CUSTOMS INTERVENTION.Customs Intervention LNG CusIntTexCUSINT667LNG





6 Applicable rules and conditionsFor the rules/conditions that apply to the messages IE351, refer to [A14]





7 Field explanationsThe explanation of the different fields in the message structure is given in the table below, but only for non-trivial data fields:





Segment/field Description

IMPORT OPERATION

MRN The Movement Reference Number was allocated by the Customs Office upon reception of the original ENS. The MRN of this operation must point to the MRN of the original ENS

LRN The Local Reference Number (LRN) shall be a number/identifier allocated by the sending TRADER for a specific transaction. In this case, the LRN must point to the LRN of the initiating Entry Summary Declaration (ENS)

Declaration registration date and time The 'Declaration registration date and time' is the date and time when the ENS is registered and the MRN is allocated. It corresponds to the 'Declaration registration date and time' communicated in IE328.The time has to be given in the format YYYYMMDDHHMM where: YYYY = YearMM = MonthDD = DayHH = HourMM = Minute

Declaration submitted date and time As this data is in the declaration identified by the MRN, there is no point of copying this again. Therefore, this field is not used.

Total number of items The 'Total number of items' is the total number of goods items declared in the declaration corresponding to the MRN.

As this data is in the declaration identified by the MRN, there is no point of copying this again. Therefore, this field is not used.

Notification date and time Time stamp of the message

Transport mode at border (box 25) Information is present in the ENS ( identified by MRN). Not used.

Nationality Crossing Border (box 21) Iso Alfa II code (box 21/2)

Identity Crossing Border (box 21) Optional field. Not used.

Commercial Reference Number (box 7) Optional field. Not used.

Conveyance reference number Optional field. Not used.

CUSTOMS INTERVENTION

Item Number concerned The item number as presented in the accepted (Entry) summary declaration with the same MRN hasto be entered






Customs Intervention code Used to specify the type of customs control in case Customs decide to intervene.Following common codes shall be used:A001 = Goods not to be loaded P001 = General physical control of goodsD001 = Documentary controlS001 = Seals control

Customs Intervention text Free form text

Customs Intervention _LNG Language identifier of the intervention text

GOODS ITEM If Customs intervention used, this is optional

Item number (Box 32) Optional field. Not used.

Commercial Reference Number (ex box 7) Optional field. Not used.

CONTAINERS Optional Data Group. Not used.

IDENTITY of Means of Transport at Border Optional Data Group. Not used.

PRODUCED DOCUMENTS/CERTIFICATES Optional Data Group. Not used.

CUSTOMS OFFICE of Lodgement Optional Data Group. Not used.

CUSTOMS OFFICE of first Entry

Reference number Reference number

Expected date and time of arrival The data group/attribute shall not be used if the message is sent to the 'Person lodging the ENS'. If the message is sent to the 'Trader at Entry (Carrier)' and if the same data group/attribute is present in the ENS, then it shall be present.The scheduled date/date and time of arrival of the means of transport at the declared first Office of Entry shall be provided. It shall be the local time of the first place of arrival.

For date formatting, see above date fields

PERSON Lodging the summary declaration This is the identification of the trader who has submitted the initial ENS

TIN (Box 14) The EORI Trader Identification number (TIN) shall bedeclared

Name (box 14) Obvious

Street and number (box 14) Obvious

Country (box 14) Obvious

Postcode (box 14) Obvious

City (box 14) Obvious






NAD_LNG Language identifier of the address

TRADER At Entry (Carrier) This is the identification of the trader at entry

TIN (Box 14) The EORI Trader Identification number (TIN) shall bedeclared

Name (box 14) Obvious

Street and number (box 14) Obvious

Country (box 14) Obvious

Postcode (box 14) Obvious

City (box 14) Obvious

NAD_LNG Language identifier of the address

TRADER Representative Optional: This is the identification of the representative of the trader. Not used.




Documents

Message Implementation Guide - FOD Financiën · FOD FIN Belgium and IBM Corporation 2014 MASP.be Message Implementation Guide Advanced Intervention Notification message IE351 Document: