AIRFREIGHT – IMPLEMENTATION GUIDE “CONFIRMATION HANDLING” – version 1.4

/ Federale
Overheidsdienst
FINANCIEN
ALGEMENE ADMINISTRATIE VAN DOUANE EN ACCIJNZEN

Implementation guidelines

-Message “CONFIRMATION HANDLING” - Air freight

Version 1.4

24 JUNI 2015

Message Name: CONFIRMATION HANDLING

Message Version:1.4

Date Released: 24/06/2015

Responsible Agency:Belgian Customs

Message Type:XML

Document Information

Document title / Implementation guidelines - Message “CONFIRMATION HANDLING”
Project Name / ECS
File name
Author / Martine De Doncker
REVISION HISTORY
Rev / Section / Date / Author / Changes
1.0 / All / 01/09/12 / Martine De Doncker / Draft
1.1 / All / 06/11/2012 / Afdeling Ondersteuning automatisering / Corrections
1.2 / All / 22/04/2013 / Pascal DUCHENE / Adaptation for the firms of Koerier
1.3 / All / 09/07/2013 / Pascal DUCHENE / Corrections
1.4 / All / 24/06/2015 / Klara Pasgang / Replace the XSD and sample XML package with a URL

CONTENT

1.Introduction

2.Message “CONFIRMATION HANDLING”

2.1. Technical specifications

2.2.Message specifications

2.3.Functional specifications

2.3.1.Rules

2.3.2.Validation Rules

3.XSD schema

4.Message “Customs response”

5.Example of a ‘CONFIRMATION HANDLING’ message

1.Introduction

This message is sentto the customs authoritiesby the handling company at the moment of the formal acceptanceof the consignment in name of the airline(consignment checked fornumbers, weight....CFRFSU/RCS). This message is sent also to the customs authoritiesby the customs broker at the moment that the consignment has been physically received from the handling company at his location (in this case the consignment is sending back to the broker).

In this message, the handling companyor customs broker informs the customs administration about the arrival of the goods at their storage location.

The customs authoritiesrespondthe handling companyor customs broker with the message ‘CUSTOMS RESPONSE’.

2.Message “CONFIRMATION HANDLING”

2.1. Technical specifications

The used messageformat is of the typeXML. Web services are the only possibility to forwardthe messages.

2.2.Message specifications

MESSAGEMx1

MESSAGE IDENTIFIERMx1

FUNCTIONMx1

HANDLINGMx1

TYPEMx1

IDENTIFICATIONMx1

LOCATIONMx1

(MASTER) WAYBILLMx1

REFERENCEMx1

PACKAGE TYPEMx1

QUANTITYMx1

GROSS MASSMx1

TIME ACCEPTANCEMx1

N° / Field / Form / Content / Rules / XML tag
0 / Message / ConfirmationHandling
1.1 / Message identifier / an..35 / Unique identification of the message / <messageIdentifier>
1.2 / Function / n1 / 9 = first / R1 / <function>
1.3 / Handling / Handling
1.3.1 / Type / an3 / Default code: EOR / type
1.3.2 / Identification / an..17 / EORI number of the handling company or broker who has received the goods / R2
R3 / identification
1.3.3 / Location / an..35 / Location of goods (handling location or broker)
See: / location
1.4 / (Master) waybill
((M)AWB) / MasterWaybill>
1.4.1 / Reference / an..40 / (M)AWB Number / R5 / masterWaybillNumber
1.4.2 / Package type / an2 / ISO code for packages (UNECE Recommendation No. 21) / R6 / packageType
1.4.3 / Quantity / n..6 / Quantity / R7
R8 / quantity
1.4.4 / Gross mass / n..11,3 / Gross mass in KGM / R9 / weight
1..4.5 / Time of acceptance / xs:DateTime / <AcceptanceDate>

2.3.Functional specifications

2.3.1.Rules

R1 = A cancellation message is not allowed.

R2 =The EORI of the handling company or broker must be known by ECS (in the EORI DB).

R3 =The EORI of the handling company or broker must be the same as the EORI of the message “Transfer”.

R5 =The master waybillmust be known in the customs system.

R6 =The kind of packages must be the same as the package type of the master waybill of the message “Transfer”.

R7 =The received quantity should be the same as the quantity of the master waybill of the message “Transfer”.

R8 =IF ‘Package type’ indicates ‘BULK’ (UNECE rec 21 : ‘VQ’, ‘VG’, ‘VL’,‘VY’,’VR’, ‘VS’ or ‘VO’)
THEN the field ‘Quantity’ must be equal to the value 0
ELSE the field ‘Quantity’ must contain always a value greater than 0.

R9 =The received gross mass should be the same as the gross mass of the master waybill of the message “Transfer”.

2.3.2.Validation Rules

Rule / Comment / Error
<function> in (9) / 9 = initial submission / UnknownFunction
handlinghandlingType> in (EOR) / EOR => EORI number as identification / UnknownAgentType
<masterWaybill<mawbPackageType> / The type of package must be conform to UNECE Recommendation No. 21 / UnknownPackageType

3.XSD schema

The relevant XML Schema is ‘ConfirmationHandling.xsd’ and its included XSDs. They can be downloaded as a package from section “Pakket 2 – Functioneel technische specificaties goederenstromen – Berichtspecificaties”, Luchtvracht

4.Message “Customs response”

On all received ‘CONFIRMATION HANDLING’messages the customs system willsendareplyto thehandling companyviathe message ‘Customs response’.

The detail of the message ‘Customs response’ can befoundin the document ‘MIG – Customs response’.

5.Example of a ‘CONFIRMATION HANDLING’ message

The relevant example ‘sample_ConfirmationHandling_01.xml’ is included sample xml. It can be downloaded as a package from section “Pakket 2 – Functioneel technische specificaties goederenstromen – Berichtspecificaties”, Luchtvracht

1