0 | P a g e
e-AWB Handling Guideline
Australia
Version 1.0
Note: The purpose of these guidelines herewith is for general information only.
e-AWB Working Group AUSTRALIA
1 | P a g e
TABLE OF CONTENTS
SECTION SUBJECT PAGE
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 What is e-AWB?
1.2 EDI Agreements
1.3 Types of Shipments in Scope
1.4 How does e-AWB work?
1.5 e-AWB implementation requirements for a Forwarder
2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 The e-AWB Operational Process . . . . . . . . . . . . . . . . . . . . . .9
3.1 The e-AWB Acceptance Process
3.2 Special Handling Code ECC/ECP Process
3.3 Exception Management
4 FWB / XFWB Validation Rules . . . . . . . . . . . . . . . . . . . . . . . .13
4.1 AWB Consignment Details
4.2 FLT : Flight Bookings
4.3 RTG : Routing
4.4 SHP : Shipper Details / CNE: Consignee Details
4.5 AGT : Agent Details
4.6 SSR : Special Service Request
4.7 ACC : Accounting Information
4.8 CVD : Charge Declaration
4.9 RTD : Rate Description
4.10 Nature and Quantity of Goods
4.11 OTH : Other Chargers
4.12 Shipper’s Certification
4.13 Carrier’s Execution
4.14 OSI : Other Service Information
4.15 SPH : Special Handling Codes
4.16 Summary of required FWB Data
5 Recommended Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2 | P a g e
TABLE OF APPENDICES
APPENDIX SUBJECT PAGE
A AU e-AWB Working Group Terms of Reference. . . . . . . . . . 21
B MeA Airline Submission Form Completion Guidelines. . . . . .24
C MeA Completion Guidelines – Freight Forwarders . . . . . . 25
D New MeA Paperless Process for Freight Forwarders . . . . 26
E FWB Error Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
F Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3 | P a g e
Revision History
Version
Date
Updated by
Changes made
1.0
(Original)
1 August 2017
Dylan
Albuquerque
-
4 | P a g e
SECTION 1: Introduction
1.1 What is e-AWB?
The Air Waybill (AWB) is the Contract of Carriage between the “shipper” (e.g.
forwarder) and the “carrier” (airline). It is also called the paper AWB. It is governed
by the IATA Resolution 600a “The Air Waybill”. The “Air Waybill Conditions of
Contract” are printed on the reverse side of the AWB as per IATA Resolution 600b.
The Warsaw Convention of 1929 mandates the paper AWB.
The e-AWB is defined as:
(a) a consignment moving with an electronically-concluded Contract of
Carriage with no accompanying paper air waybill proof of the contract;
and,
(b) No paper AWB transported in the aircraft to destination.
To ship via e-AWB, either a Bilateral Agreement or IATA Multilateral e-AWB
Agreement is required.
1.2 EDI Agreements
5 | P a g e
1.2.1 Bilateral Agreement: Both the Carrier and the Freight Forwarder sign the
IATA Recommended Practice 1670 (RP1670) which covers all locations
where both parties are operating.
1.2.2 Multilateral e-AWB Agreement (MeA): IATA Resolution 672 – Airline and
Freight Forwarder sign the MeA once and for all, and can immediately start
moving e-AWB shipments with their respective partners, provided that both
have mutually “activated” a location where they have operations.
1.3 Types of Shipments in Scope
1.3.1 General Cargo/Consolidations with no accompanying shipping
documents.
1.3.2 Special Cargo (Live Animals/Lithium Batteries) may require the original
declaration and health/quarantine certificates. For such cases, forwarders
may submit and include the original documents inside the document pouch,
and enter the below statement in the OSI or SSR field of the FWB indicating
the cargo as such.
For Live Shipment:
“Shippers Certification for Live Animals attached”
For Lithium Ion Batteries (as an example):
"Lithium ion batteries in compliance with Section II of PI 965"
"Lithium ion batteries in compliance with Section II of PI 966"
"Lithium ion batteries in compliance with Section II of PI 967"
"Lithium metal batteries in compliance with Section II of PI 968"
"Lithium metal batteries in compliance with Section II of PI 969"
"Lithium metal batteries in compliance with Section II of PI 970"
6 | P a g e
The relevant statement(s) may be included within Handling
Information (Box 21) of the AWB which will be sent in the OSI
segment.
1.3.3 Dangerous Goods (DG) Shipments may require the original Declaration for
Dangerous Goods (DGD). For such cases, forwarders may submit and include the
original documents inside the document pouch, and enter the below statement in
the OSI or SSR field of the FWB indicating the cargo as such.
For DG Shipment:
“Dangerous Goods as per attached DGD”; or
“Dangerous Goods as per attached DGD-CAO”
For consolidation containing both DG and Non-DG:
“XX Packages Dangerous Goods as per attached DGD”; or
“XX Packages Dangerous Goods as per attached DGD-CAO”
1.3.4 Direct/Walk-in Shipments will be handled according to each Airlines’ current
individual processes.
1.4 How does e-AWB work?
Both parties (Airline and Forwarder) must have an Electronic Data Interchange
(EDI) Agreement prior to implementing the e-AWB.
Forwarder makes reservations with the Carrier and specify in FWB message
according to agreed procedure between Airline and Forwarder. SHC code
"EAP" or "EAW" is to be indicated in the booking record.
Forwarder sends FWB / XFWB and FHL / XFHL (for consolidations) electronic
messages to either the Cargo Community System (CCS), the airline or the CTO
as dictated by the airline. The receiving party validates the data and transmits
an FNA back to the forwarder if error is found otherwise transmits an FMA back
to the forwarder and send the data to the Cargo Terminal Operator (CTO)
and/or airline, as per CTO & airline standing instructions. This is a critical step
to ensure the eAWB data has been processed by CTO/Airline.
Prior to tendering the shipment to the Carrier, the Forwarder must check for a
FMA or FNA message. This is a critical step to ensure the eAWB data has been
processed by the CTO/Airline and to ensure that the FWB/FHL is captured by
the CTO/Airline to avoid rejection due to nil FWB/FHL data by CTO/Airline
when tendering the shipment.
Forwarder tenders the shipment to the CTO prior to flight departure/cut-off.
7 | P a g e
CTO receives the shipment and undertakes check/weigh as per airline
requirements.
If there is a discrepancy: (Please refer to Refer to 3.3 Exception Management
for courses of action)
. CTO accepts the shipment and sends ““Freight on Hand” or “Freight
Status Update” (FSU/FOH) with the corrected PCS/WGT/VOL to the
airline.
a. CTO requests the Forwarder re-sends the FWB / XFWB with the
corrected information.
b. Once the corrected FWB is received from the Forwarder, CTO sends
the FSU/RCS to the airline and subsequently the airline responses
FSU/RCS to FF/CCS as per agreed process.
Forwarder re-sends the FWB/ XFWB with the corrected information.
If the new information is correct, the CTO (and subsequently the Airline)
responds to the forwarder with the FSU/RCS electronic message, concluding
the Cargo Contract.
1.5 e-AWB Implementation Requirements for a Forwarder
Capability to send out FWB / XFWB and FHL / XFHL messages.
Capability to receive FSU/FOH, “Freight Status Update” / ”Ready for Carriage
Status” (FSU/RCS), FMA (Acknowledgement) and FNA (Rejection) messages
Electronic archival capability of the FWB / XFWB and FSU / RCS messages
(which together constitute the Shipment Record).
Capability to interpret the FNA message and re-send a corrected FWB/FHL to
the Airline/CTO.
8 | P a g e
SECTION 2: Scope
No physical Master Air Waybill (MAWB) or House Manifest (FHL) will be tendered
by the forwarder to any Airline from the origin station of uplift.
The physical MAWB is to be replaced by the electronic message equivalent – the
FWB.
Freight Forwarder (FF) must transmit the FWB / XFWB and FHL / XFHL (for
consolidations) for all shipments to the Airline to lodging-in their cargo at the CTO
acceptance counter. Prior to lodgement, FF is to confirm that airline/CTO has
received the FWB data from the FMA message from the airline, CTO or the CCS.
Airline will adopt the e-AWB Single Process for Forwarders that will cover all cargo
categories and destinations, unless otherwise stated.
For cargo acceptance, FF may continue to tender their document pouch containing
shipping documents (e.g. consol manifest, house AWB, commercial invoices,
packing list, etc.) unless the Airline has implemented e-Freight for the shipment
destination.
To meet customs and regulatory requirements at some destinations, other paper
documents (e.g. health certificates, etc.) shall continue to be tendered at cargo
acceptance, if necessary.
In case the customer (consignee/ shippers) needs paper to satisfy customs/
legal/tax/issuance requirements, FF shall provide a copy of the paper AWB to meet
said local requirements.
EAW and EAP codes should be entered in the FWB / XFWB by the Freight
Forwarder, to indicate if there is pouch containing original shipping documents
accompanying the shipment.
ECC and ECP codes are to be entered in the FWB / XFWB by the CTO or Airline;
ECC to identify an eAWB shipment and ECP to identify if an e-AWB shipment (if
feasible) with a paper air waybill being printed under e-AWB agreement.
9 | P a g e
SECTION 3: The e-AWB Operational Process
3.1 The e-AWB Acceptance Process
Step 1: Freight Forwarder (or their co-loaders) must transmit the electronic AWB (FWB
/ XFWB) and FHL / XFHL (for consolidations) for all shipments, regardless of
destination, and prior to the freight tendered at the acceptance counter.
The FWB and FHL may be sent:
By Freight Forwarder using an in-house computer system
o Directly to Airline system
o Via CCS connection hubs to the Airline system
By Freight Forwarder via the Airline’s e-AWB portal/website
By Freight Forwarder via CCS system’s e-AWB portal/website
10 | P a g e
Forwarder should only transmit an accurate FWB / XFWB and FHL /
XFHL message to the CTO/Airline before tendering their shipment for
cargo acceptance.
Step 2: Airline will receive the FWB/FHL messages from the Forwarder and then
send out an:
FMA to acknowledge receipt of the processed FWB / XFWB; or,
FNA if the FWB / XFWB contains syntax or format errors.
The FMA or FNA will be sent almost instantly after system checks against the
Airline’s list of FWB data validation rules. Forwarder to resolve issues with the
Airline, if any.
Forwarder must obtain the FMA to verify with the airline or CTO that the FWB
has been processed and cargo is clear to be lodged.
Step 3: Forwarder tenders their shipment to the CTO, and may include a pouch
containing documents for carriage to final destination at the point of cargo
acceptance.
Step 4: CTO compares the FWB / XFWB and FHL/XFHL against the actual shipment
tendered.
If there are business data errors, CTO/Airline sends the FNA message to the
Forwarder informing of the errors.
If there are discrepancies, the Carrier system (after receipt of data from their
CTO) will:
Send the FSU/FOH message to the Forwarder informing of the
discrepancies; and,
Produce the Warehouse Receipt, if necessary.
Forwarder to amend and re-send the FWB containing the corrected
information.
Step 5: CTO on behalf of Airline will determine whether the Shipment qualifies as e-
AWB, and act accordingly (please refer to Section 3.2, Special Handling Code
ECC/ECP Process).
Step 6: Once the FWB data matches the actual shipment, the Airline will receive
FSU/RCS from the CTO and send out FSU/RCS to Forwarder to conclude the
contract.
3.2 Special Handling Code ECC/ECP Process
11 | P a g e
Step 1: CTO or the Airline confirms that the Forwarder is authorized to deliver freight
without a paper AWB (as an e-AWB agreement is in place and activated).
Step 2: CTO or the Airline determines whether the Shipment is ECC (e-AWB) or ECP
(paper AWB), taking into account applicable International Convention,
regulatory requirements and network constraints.
For ECP shipments:
For airlines that have adopted to observe the e-AWB Single Process:
o CTO prints the paper AWB pursuant to Resolution 600a, including the
Conditions of Contract, based on the FWB/XFWB sent by the
Forwarder.
o Airline signs the paper AWB on behalf of the Forwarder or prints the
Airline name in capital letters in the paper AWB’s Signature of Issuing
Carrier or its Agent box.
For airlines that have NOT adopted the e-AWB Single Process:
o Forwarder confirms that they have a copy of the AWB paper inside the
pouch, for use at destination for regulatory purposes.
Step 3: CTO/Airline enters or automatically generates the appropriate code in the
Special Handling Code field.
3.3 Exception Management
3.3.1 In case of missing FWB/XFWB prior to freight delivery:
Approach 1: Airline rejects the freight delivery.
Approach 2: Airline informs forwarder to send FWB/XFWB.
Airline informs forwarder of missing FWB and/or FHL message.
FF sends the FWB:
o Within 30 minutes after the advice was given; or
o Before flight closure, whichever comes first
Otherwise, fall back to a paper AWB.
Approach 3: Fall back to a paper AWB.
The above approaches need to be agreed upon between the two parties.
3.3.2 In case of a discrepancy between FWB/XFWB and received cargo:
Approach 1: CTO/Airlines sends FSU/FOH.
CTO/Airlines sends FSU/FOH, informing Forwarder of the
required correction on the FWB data.
12 | P a g e
If forwarder agrees with the required correction:
o Forwarder sends correct FWB
o Airline sends FSU/RCS
If Forwarder does not agree with the required correction:
o If Airline and Forwarder mutually agree on the correct
shipment data, Forwarder sends the corrected FWB, and
Airline sends FSU/RCS.
o Otherwise, fall back to a paper AWB.
Note: If replacement FWB is not sent prior to cut-off, shipment is
offloaded.
Approach 2: Airline sends FSU/RCS with incorrect data and a paper CCA.
Note: This implies incorrect shipment data in the FWB/XFWB. The
CCA details then constitute the contract between forwarder
and airline.
13 | P a g e
SECTION 4: FWB / XFWB Validation Rules
FWB / XFWB message quality is a pre-requisite for e-AWB implementation.
To avoid delays at time of freight presentation, Forwarder must take immediate action to
re-send the amended FWB / XFWB to the CTO/Airline if they received an FNA message.
Forwarder should work with the CCS for verification of data success, and correction of
errors.
For detailed guidelines, Forwarders should carefully note the following information and
contents to convey in their FWB messages to the Carriers:
Terms used are defined as follows:
M
Element is mandatory
O
Element is optional
C
Element is conditional
a
Alphabetic character or letter (A-Z)
n
Numeric character or number (0-9)
m
Alpha-numeric
t
Either a letter, number or another acceptable character
e.g. full stop, dash and space
p
Could include a decimal point
4.1 AWB Consignment Details
AWB Number
t[…12]
12 characters
M
Origin Airport Code
[aaa]
3 characters
M
Destination Airport Code
[aaa]
3 characters
M
Shipment Description Code
[a]
”T”
M
Total Pieces
[nnnn]
4 numeric
M
Weight Code in Kilogram
[a]
“K”
M
Weight
n[…7]
7 numeric
M
Example:
FWB/1
618-37257861AMSBNE/T9K510.0
4.2 FLT: Flight Bookings
Carrier Code
[mm]
2 characters
M
Flight Number
[nnn(n)(a)]
5 characters
M
Day of Month
[nn]
2 characters
M
Example:
618-3725861AMSBNE/T9K510.0
FLT/SQ323/29
4.3 RTG: Routing
Airport Code
[aaa]
3 characters
M
14 | P a g e
Carrier Code
[mm]
2 characters
M
Example:
FLT/SQ323/29
RTG/SINSQ/BNESQ
Only valid IATA codes should be used.
4.4 SHP: Shipper Details / CNE: Consignee Details
Name
t[…35]
35 characters
M
Street Address
t[…35]
35 characters
M
Place
t[…17]
17 characters
M
State/Province
t[…9]
9 characters
O
ISO Country Code
[aa]
2 characters
M
Postal Code
t[…9]
9 characters
M
Contact Identifier
m[…2]
2 characters
O
Contact Number
m[…25]
25 characters
O
Example:
RTG/SINSQ/BNESQ
SHP
/ABC INTL SG PVT LTD
/210 LEVEL – 1 ABC 1A
/SINGAPORE
/SG/238164
CNE
/ABC INTL OF WA INC
/425 ROAD DRIVE
/BRISBANE/QLD
/AU/4000
Forwarders are to ensure that the shipper and consignee names and addresses
which are populated in the FWB (limited by 35 characters) are an exact match with
their shipping details.
Full Shipper/Consignee name without abbreviation is required for those not
exceeding 35 characters. If the Forwarder sends FWB/17, all required address
information is to be included in the first address line, because the CCS will need
to back-translate the data to FWB/16 for sending to carriers/CTO’s that do not
support FWB/17.
Only when the Shipper/Consignee name exceeds 35 characters the Forwarder
may abbreviate the company name.
Only commonly understood abbreviations should be used;
Avoid any ambiguity in understanding the abbreviated addresses; and,
Optimize the use of the 35 characters available.
For Contact Identifier, the only identifiers accepted are FX/TE/TL.
15 | P a g e
Due to customs requirements in many countries, the Postal Code is mandatory.
4.5 AGT: Agent Details
IATA Agent Code
n[…7]
7 characters
M
IATA Agent CASS Code
[nnnn]
4 characters
O
Name
t[…35]
35 characters
M
Issuing Place (Airport Code)
t[…17]
17 characters
M
Example:
AGT//7847311/0811
/XYZ LOGISTICS
/SIN
4.6 SSR: Special Service Request
SSR (x 3 lines)
t[…65]
65 characters
C
Example:
AGT//7847311/0811
/XYZ LOGISTICS
/SIN
SSR /STORE TO -8 DEGREE CELSIUS
Forwarders may input any specific handling information required in this field.
4.7 ACC: Accounting Information
ACC
t[…34]
34 characters
O
Example:
SSR/RCAR-KC/STORE TO -8 DEGREE CELSIUS
ACC/ /SPL RATE 500K
Forwarders may input data indicated at the Accounting Information Box.
Presently, in AU the forwarder provides the CAN as provided by AU Customs
into the ACC/GEN field.
4.8 CVD: Charge Declaration
Currency Code
[aaa]
3 characters
C
P/C (2 fields)
[a]
P(repaid) or C(ollect)
C
Declared value for Carriage
m[…12]
NVD=No Value Declared
C
Declared value for Customs
m[…12]
NCV=No Customs Value
C
Amount of Insurance
t[…11]
XXX=No Value
C
Example:
ACC/GEN/SPL RATE 100K
CVD/SGD//PP/NDV/NCV/XXX
4.9 RTD: Rate Description
AWB Rate Line Number
[nn]
2 characters
M
No of Pcs or Rate Comb Pt
[nnnn]
4 characters
M
Weight Code
[a]
“K”
M
Weight
n[…7]p
7 characters
M
Rate Class Code
[a]
“C” “M” “N” “Q”
M
Commodity Item Number
[nnnn]
4 characters
C
16 | P a g e
Chargeable Weight
n[…7]p
7 characters
M
Rate or Charge
n[…8]p
8 characters
M
Total Charge Amount
n[…12]p
12 characters
M
Example:
CVD/SGD//PP/NDV/NCV/XXX
RTD/1/P30/K510.0/CC/S0315/W510.0/R3.75/T1912.50
When Rate Class Code of “C” is entered, the Commodity Item Number is required.
4.10 Nature and Quantity of Goods
Forwarder must provide accurate, specific and complete “Nature of Quantity of
Goods” information since generic terms are not accepted in most countries.”
Although space available for inputting the handling information in the FWB is 20
characters x 11 lines, “Manifest description of foods” in the Airline Flight Manifest
(FFM) is limited to 15 characters, and the commodity description in the FFM is
extracted from the first 15 characters of the first line of the NG field of the FWB.
As such the Forwarder must provide an accurate and valid commodity description
in the FWB, capped at 15 characters for the first line in the NG field, as this will
have an impact on the FFM message.
For example:
“Aircraft spare parts” inputted in the first line of the NG field of the FWB will be
truncated to 15 characters as “Aircraft spare”, when the FFM is generated.
Following are the Goods Data Identifiers in the FWB:
NG
Goods Description for non-consol cargo
t(…20)
O
NC
Goods Description for Consolidation cargo
t(…20)
O
ND
Dimension
M[…3]n[…
5]-n[…5]-
n[…5]/n[…
4]
C
NV
Volume
n[…9]p
C
NU
ULD information (if any)
Ammmnnn
(n)mm
C
NS
SLAC (if any)
n[…5]p
C
NH
Harmonized Code
m(6…18)
O
NO
Country of Origin of Goods
a2
O
Example:
RTD/1/P30/K510.0/CC/S0315/W510.0/R3.75/T1912.50
/NG/1 AIRCRAFT PARTS
/2/ND//CMT60-80-120/1
/3/NV/MC0.57
Forwarder may input the description of “Goods Description” in either the “NG” or
“NC” data field, and omit phrases such as “Said to Contain” in the first line of the
17 | P a g e
NG field of the FWB. Data for either the Dimension (ND) or Volume (NV) must be
inputted allowing for the determination of the correct volume/chargeable weight of
the shipment.
4.11 OTH: Other Charges
Forwarders may only use the standard IATA’s Other Charge Codes. Following is
a list of the common codes used:
OTHER
CHARGE
CODES
DESCRIPTION
MY
Fuel Surcharge - Due Issuing Carrier
XB
Security (Surcharge/premiums)
CG
Electronic processing or transmission of data for customs purposes
CC
Manual data entry for customs purposes
RA
Dangerous Goods Fee
Example:
OTH/P/MYC262.50/XBC67.50
Note: Individual carriers may have specific requirements for Other Charges
(OTH) information. This should be clarified with the individual carriers.
4.12 Shipper’s Certification
Signature
t[…20]
20 characters
M
Example:
CER/CAPT J.T.KIRK
Forwarder is required to enter the name of the “Shipper or his Agent” in CAPITAL
letters.
4.13 Carrier’s Execution
Issue Date
nnaaann
M
Issue Place or Airport/City
Code
t[…17] or
aaa
M
Signature
t[…20]
20 characters
M
Example:
ISU/25OCT15/AMS
SPEEDAIR SERVICES
Forwarder is required to enter the name of the “Issuing Carrier or its Agent” in
CAPITAL letters. The forwarder should show the issuing staff member’s AU DG
Number (issued by IATA on completion/refresh of DG Acceptance Training) before
the staff’s name, within the ISU segment.
4.14 OSI: Other Service Information
OSI (x 3 lines)
t[…65]
65 characters
M
Example:
18 | P a g e
OSI/DANGEROUS GOODS AS PER ATTACHED SHIPPERS
DECLARATION – 1 PACKAGE
Forwarders may input any other handling information required in this field.
4.15 SPH: Special Handling Codes
SHC (x 9)
[aaa]
3 characters
O
Example:
SPH/ECC/PER
Forwarders must input the correct Special Handling Codes (SPH) as listed in the
IATA TACT Rules manual. A Freight Forwarder is not permitted to include
ECC/ECP codes in the FWB.
The SPHs “ECC” and “ECP” are to be inputted by the Airline only.
4.16 Summary of required FWB data
ELEMENT NAME
LINE
AWB BOX
USE
COMMENTS
AWB Number
1A/1B
M
Origin Airport Code
1
M
Destination Airport Code
11A
M
Flight Bookings
FLT
19A/19B
M
Routing
RTG
11B/11D/11F
M
Agent
AGT
06/07/08
M
Total Pieces
RTD
22A
M
Gross Weight
RTD
22B
M
Weight Code
RTD
22C
M
“K”
Rate Class Details
RTD
22D
M
“C” “M” “N” “Q” “X”
Commodity Item Number
RTD
22E
C
Chargeable Weight
RTD
22F
M
Rate or Charge
RTD
22G
M
Total Charge Amount
RTD
22H
M
Goods Description
NG/NC
22I
C
Cap at 15 characters for the 1st line
Should not contain “Said to contain”
Dimensions/Volume
ND/NV
22I
C
Either should be present
Other Charges
OTH
23
C
Handling Information
SSI/OSI
21
C
Accounting
ACC
10
O
Shipper’s Certification
CER
31
M
Carrier’s Execution
ISU
32C
M
Should include AU number
19 | P a g e
20 | P a g e
SECTION 5: Recommended Practice
Below are the recommended practices to be followed by local stakeholders in the
implementation of the e-AWB process:
Forwarders to provide the correct FWB if possible at all times.
Use the following recommended codes:
MY – Fuel Surcharge Code
XB – Security Surcharge Code
FWB Completion
For loose cargo – need to populate at least one of the following FWB fields:
a. Shipment dimensions
b. Shipment volume weight
For Bulk Unit Programme (BUP) cargo – need to indicate “BUP” in Special
Handling Codes (SPH) field.
Airlines/CTO to provide an FNA/FMA for all FWBs received. FNA messages to
incorporate the MIP error codes as described in Appendix.
FWB’s may only include e-CSDs if the FF is a RACA under the Office of Transport
Security (OTS) legislation (Aviation Transport Security Regulation).
21 | P a g e
Appendix A
e-AWB Australia Working Group
Terms of Reference
1. Objectives
1.1 The e-AWB Australian Working Group (hereinafter referred to as the Support
Group) is established as an action group reporting to the e-AWB Advisory Group.
1.2 The objective of the e-AWB Australian Support Group is to utilize industry
participation to support the overall efforts made by the individual stakeholder to
further increase the e-AWB penetration at Australia.
1.3 The Support Group shall:
1.3.1. Agree on the location deliverables, actions, and plans to jointly support the
e-AWB penetration rate growth in Australia, subject to and practical to the
Australian environment.
1.3.2. Demonstrate that joining the IATA Multilateral e-AWB Agreement will
remove the legal burden of signing multiple bilateral e-AWB agreements
and will help to promote e-AWB adoption in the industry.
1.3.3. Lead by example, to show case the benefits and commitment to implement
a 50% e-AWB penetration in Australia by the end of 2017.
2. Composition
2.1 The Support Group shall consist of 12-15 members (stakeholders) with relevant
knowledge of e-AWB and can be expanded when necessary.
2.2 The Support Group shall ideally include members from the following stakeholder
groups:
o Airlines
o Freight Forwarders
o Ground Handling Agent
o Software / technology providers
2.3 Affiliates of Freight Forwarders and additional airlines may join as Support Group
Members.
2.4 Membership of the Support Group shall reflect a geographical representation as
fairly as possible.
22 | P a g e
2.5 The IATA Cargo Committee members shall appoint their South West Pacific based
staff for their involvement in the e-AWB support group initiative.
2.6 When appropriate, the Support Group shall invite the participation of industry
experts (e.g. Legal, Regulators) at the group meetings from time to time for
consultation purposes.
2.7 Observers from IATA Members, IATA Strategic Partners and industry stakeholders
may be invited to attend the Support Group meetings upon concurrence of IATA
Secretariat.
3. Rules and Procedures
3.1 The Support Group shall be established for duration of twelve (12) months or less
if the penetration rate of e-AWB is above 47% for Australia’s overall statistics
declared effective by IATA prior to the twelve months period.
3.2 Meetings of the Support Group shall be conducted by regular teleconferences or,
when required, face-to-face meetings may be organized upon acceptance of the
majority of the members of Support Group.
3.3 The Support Group shall limit its activity to providing industry support and actions
to drive up the e-AWB penetration in Australia.
3.4 All meetings shall be conducted in accordance with IATA’s Competition Law
Guidelines for IATA Traffic Conferences.
4. Roles and Responsibilities
4.1 The Support Group shall report to the e-AWB Advisory Group.
4.2 Each member of the Support Group shall participate in his or her capacity as a
representative of the industry with required (relevant) knowledge.
4.3 Members of the Support Group shall identify the required and/ or necessary
business information needed to propose recommendations.
4.4 The Support Group shall consult with the relevant industry bodies when needed.
4.5 IATA shall provide the Secretary, who will support and facilitate the meetings of
the Support Group.
4.6 From time to time, IATA may appoint a member of the Support Group as Facilitator
for the teleconferences or the face-to-face meetings.
5. Deliverables
23 | P a g e
5.1 The Support Group shall be responsible to help reach 50% e-AWB penetration.
5.2 Develop a joint industry plan and road map to support the 50% target.
a. Contribute its resource to support the joint plan and road map.
5.3 The Support Group activity shall base on below actions report back to the e-AWB
Advisory Group on following:
(i) Airline’s, Freight Forwarder, GHA’s actions to increase the e-AWB
penetration in Australia:
(ii) Multilateral e-AWB Agreement progress.
(iii) Any issues that may require support and guidance from the e-AWB Advisory
Group.
5.4 Agenda and minutes of the Support Group meetings including additional
documentation shall be made available to all members of the Support Group on
the IATA extranet website of the e-AWB Advisory Group.
* * * * * * * * *
24 | P a g e
Appendix B
MeA Airline Submission Form Completion Guidelines
Airlines need to complete and submit the Airline Submission Form to join the IATA
Multilateral e-AWB Agreement
Type into the grey shaded fields in the Submission Form, then print and sign
In the Submission Form:
Ensure to specify the Designated Contact (section A)
Ensure to specify the Airport locations (section B)
Ensure to enter the Airline Reference and Signatory details (page 4)
For list of Airports, an Excel sheet template is also available; please contact
IATA cargo at cargo@iata.org
Send completed Airline Submission Form to:
IATA Cargo
Attn: Ben Behanan
Manager, e-AWB Standard Multilateral Agreement
International Air Transport Association
33 Route de l’Aéroport
1215 Geneva 15 Airport
Switzerland
Please send a soft copy of the filled-in Submission Form (and filled-in Excel Sheet, if
applicable) by e-mail to IATA Cargo at cargo@iata.org
In case of any questions, please contact IATA Cargo at cargo@iata.org
25 | P a g e
Appendix C
MeA Completion Guidelines – Freight Forwarders
To join the IATA Multilateral e-AWB Agreement, complete and sign the Agreement
and the Submission Form
Type into the grey shaded fields in the Agreement and Submission Form, then print
and sign
In the Agreement, enter the details on Page 1 and Page 12
In the Submission Form:
Send the signed Original Agreement (2 copies) and Submission Form (1 copy) to:
IATA Cargo
Attn: Ben Behanan
Manager, e-AWB Standard Multilateral Agreement
International Air Transport Association
33 Route de l’Aéroport
1215 Geneva 15 Airport
Switzerland
26 | P a g e
Appendix D
New MeA Paperless Process for Freight Forwarders
A new paperless process using e-signatures is now available for freight forwarders to join
the Multilateral e-AWB Agreement. The new process is legally binding, secure, efficient,
and environmentally friendly – removing the need for parties to print, sign and mail paper
documents.
Join in four easy steps:
1. Review the standard Multilateral e-AWB Agreement
2. Complete and submit the Online Joining Form (takes approx. 10-15 minutes)
3. Receive your Agreement by e-mail from IATA Cargo
4. e-sign the Agreement
Next steps: IATA will counter sign the Agreement and you will receive the final signed
PDF by e-mail. Your company will be listed to the IATA Multilateral e-AWB Agreement
and you will receive a joining confirmation message from IATA advising the effective date
and next steps.
Click for more information:
Introduction to paperless process (pdf)
About e-signatures (including demo on how to e-sign)
27 | P a g e
Appendix E
FWB Error Reference
Starting with MIP Strategy v4 and currently in effect, improvement via a new simplified
error code set (short format-XXX99) and error types are redefined as follows:
D – Data error; e.g. invalid or missing data in a specific field
R – Rejected; e.g. message rejected for the reason described in the error definition
S – Syntax error; e.g. the format of the message id invalid resulting in the inability to
use the message and therefore its rejection
The table below explains the meaning of the column headings used.
Column Heading
Description
Error Code
New MIP Error Code
Error Type
D – invalid Data error
R – message Rejected
S – Syntax error
Error Description
Description of the error
Note: all errors shown below applies to FWBs only.
Error
Code/s
Error
Type
Error Description
Accounting Information Errors
ACC00
ACC01
ACC02
D
Invalid or missing accounting information details
- accounting information identifier
- accounting information
Agent Errors
AGT00
AGT01
AGT02
AGT03
AGT04
AGT05
AGT06
D
Invalid or missing agent details
- account number
- IATA cargo agent numeric code
- IATA cargo agent CASS address
- participant identifier
- name
- place
Agent Reference Data Errors
ARD00
ARD01
D
Invalid or missing agent reference data
- file reference
AWB Consignment Detail Errors
AWB00
AWB01
AWB02
D
Invalid or missing AWB consignment details
- airline prefix
- AWB serial number
28 | P a g e
Error
Code/s
Error
Type
Error Description
AWB Consignment Detail Errors (continuation)
AWB03
AWB04
AWB05
AWB06
AWB07
AWB08
AWB09
AWB10
AWB11
AWB12
D
- airport/city code of origin
- airport/city code of destination
- shipment description code
- number of pieces
- weight code
- weight
- volume code
- volume amount
- density indicator (DG)
- density group
AWB13
R
Message rejected - AWB serial number blacklisted
AWB14
R
Message rejected - AWB serial number not allocated to forwarder
CC Charges in Destination Currency Data Errors
CDC00
CDC01
CDC02
CDC03
CDC04
CDC05
D
Invalid or missing CC charges in destination currency details
- destination currency details ISO currency code
- currency conversion rate - rate of exchange
- CC charges in destination currency - charge amount
- charges at destination - charge amount
- total collect charges - charge amount
Shipper’s Certification Errors
CER00
CER01
D
Invalid or missing shippers certification details
- signature
Consignee Errors
CNE00
CNE01
CNE02
CNE03
CNE04
CNE05
CNE06
CNE07
CNE08
CNE09
D
Invalid or missing consignee details
- account number
- name
- street address
- place
- state/province
- ISO country code
- post code
- contact identifier
- contact number
CNE10
S
Syntax error - consignee details – total characters of country code, post code,
contact id and contact number cannot exceed 69
Commission Information Errors
COI00
COI01
COI02
COI03
D
Invalid or missing commission information details
- no commission indication - CASS indicator
- commission amount - CASS settlement factor
- commission percentage - CASS settlement factor
Collect Charge Summary Errors
COL00
COL01
COL02
COL03
COL04
COL05
COL06
COL07
COL08
D
Invalid or missing collect charge summary details
- total weight charge - charge identifier
- total weight charge - charge amount
- valuation charge - charge amount
- taxes - charge amount
- total other charges due agent - charge amount
- total other charges due carrier - charge amount
- charges summary total - charge amount
- charges collect not allowed to this destination
29 | P a g e
Error
Code/s
Error
Type
Error Description
Customs Origin Errors
COR01
D
Invalid or missing customs origin code details
Charge Declaration Errors
CVD00
CVD01
CVD02
CVD03
CVD04
CVD05
CVD06
CVD07
D
Invalid or missing charge declarations details
- ISO currency code
- charge code
- p/c indicator (Weight/Valuation)
- p/c indicator (Other charges)
- declared value for carriage
- value for customs declaration
- value for insurance declaration
Flight Booking Errors
FLT00
FLT01
FLT02
FLT03
D
Invalid or missing flight booking details
- carrier code
- flight number
- day
FWB Errors
FWB01
R
Message rejected - FWB data differs significantly from that contained in the
booking
FWB02
R
Message rejected - FWB routing differs from that contained in the shipment
booking
FWB03
S
Syntax error - SSR+NFY+OSI+COR total character length too long - total
characters cannot exceed 216
Carrier’s Execution Errors
ISU00
ISU01
ISU02
ISU03
ISU04
ISU05
D
Invalid or missing carriers execution details
- day
- month
- year
- place or airport/city code
- signature
Message Errors
MSG01
S
Syntax error - message envelope syntax error
MSG02
S
Syntax error - invalid or no end of message character
MSG03
S
Syntax error - unable to use the (data contained in the message cannot be used
to update the carrier’s system)
MSG04
R
Message rejected - data already created in carrier’s system (too late to be of any
use; message received after the carrier has created the data in its system)
MSG05
R
Message rejected - the originator’s TTY address is not recognized by the carrier
MSG06
R
Message rejected - the originator’s TTY address is recognized but not configured
to accept this message type
MSG07
R
Message rejected - message version number not supported by carrier
Also Notify Errors
NFY00
NFY01
NFY02
NFY03
NFY04
D
Invalid or missing notify details
- name
- street address
- place
- state/province
30 | P a g e
Error
Code/s
Error
Type
Error Description
Also Notify Errors (continuation)
NFY05
NFY06
NFY07
NFY08
D
- ISO country code
- post code
- contact identifier
- contact number
NFY09
S
Syntax error - also notify details - total characters of country code, post code,
contact id and contact number cannot exceed 69
Nominated Handling Party Errors
NOM00
NOM01
NOM02
D
Invalid or missing nominated handling party details
- name
- place
Other Customs Information Errors
OCI00
OCI01
OCI02
OCI03
OCI04
D
Invalid or missing other customs information details
- ISO country code
- information identifier
- customs information identifier
- supplementary customs information
Other Participant Information Errors
OPI00
OPI01
OPI02
OPI03
OPI04
OPI05
OPI06
OPI07
OPI08
D
Invalid or missing other participant information details
- name
- participant office message address - airport/city code
- participant office message address - office function designator
- participant office message address - company designator
- other participant information- file reference
- other participant identification - participant identifier
- other participant identification - participant code
- other participant identification - airport/city code
Other Service Information Errors
OSI01
D
Invalid or missing other service information
Other Charges Errors
OTH00
OTH01
OTH02
OTH03
OTH04
D
Invalid or missing other charge details
- p/c indicator
- other charge code
- entitlement code
- charge amount
Prepaid Charge Summary Errors
PPD00
PPD01
PPD02
PPD03
PPD04
PPD05
PPD06
PPD07
D
Invalid or missing prepaid charge summary details
- total weight charge - charge identifier
- total weight charge - charge amount
- valuation charge - charge amount
- taxes - charge amount
- total other charges due agent - charge amount
- total other charges due carrier - charge amount
- charge summary total - charge amount
Sender Reference Errors
REF00
REF01
REF02
REF03
REF04
D
Invalid or missing sender reference details
- sender office message address - airport/city code
- sender office message address - office function designator
- sender office message address - company designator
- sender office message address - file reference
31 | P a g e
Error
Code/s
Error
Type
Error Description
Sender Reference Errors (continuation)
REF05
REF06
REF07
D
- sender office message address - participant reference
- sender office message address - participant code
- sender office message address - participant airport/city code
Rate Description Errors
RTD00
RTD01
RTD02
RTD03
RTD04
RTD05
RTD06
RTD07
RTD08
RTD09
RTD10
RTD11
RTD12
RTD13
RTD14
RTD15
RTD16
RTD17
RTD18
RTD19
RTD20
D
Invalid or missing rate description details
- AWB rate line number
- AWB column identifier
- number of pieces/rate combination point details
- gross weight details - weight code
- gross weight details - weight
- gross weight details - rate class code
- commodity item number/ULD rate class type/rate class code class rate
- chargeable weigh details - weight
- rate charge details - rate or charge or discount
- total details - charge amount or discount amount
- goods description - goods data identifier
- goods description - nature and quantity of goods
- consolidation - nature and quantity of goods
- dimensions - weight code
- dimensions - weight
- dimensions - measurement unit code or no dims available code
- dimensions - length dimension
- dimensions - width dimension
- dimensions - height dimension
- dimensions - no of pieces
RTD21
S
Syntax error - rate description details - total number of characters of unit code,
length, width, height and no of pieces cannot exceed 20
RTD22
RTD23
RTD24
RTD25
RTD26
RTD27
RTD28
RTD29
RTD30
- volume - volume code
- volume - volume amount
- ULD number - ULD type
- ULD number - ULD serial number
- ULD number - ULD owner code
- shippers load and count - SLAC
- harmonized commodity code
- country of origin of goods - ISO country code
- service code details - service code
Routing Errors
RTG00
RTG01
RTG02
RTG03
RTG04
D
Invalid or missing routing details
- 1st destination/carrier airport city code
- 1st destination/carrier code
- onward destination/carrier airport city code
- onward destination/carrier code
Shipper Errors
SHP00
SHP01
SHP02
SHP03
SHP04
SHP05
SHP06
SHP07
D
Invalid or missing shipper details
- account number
- name
- street address
- place
- state/province
- ISO country code
- post code
32 | P a g e
Error
Code/s
Error
Type
Error Description
Shipper Errors (continuation)
SHP08
SHP09
D
- contact identifier
- contact number
SHP10
S
Syntax error - shipper details - total characters of country code, post code,
contact id and contact number cannot exceed 69
Sales Incentive Information Errors
SII00
SII01
SII02
D
Invalid or missing sales incentive information details
- charge amount
- CASS indicator
Special Handling Details Errors
SPH01
D
Invalid or missing special handling code
Shipper Reference Information Errors
SRI00
SRI01
SRI02
D
Invalid or missing shipment reference information details
- reference number
- supplementary shipment information
Sales Service Request Errors
SSR01
D
Invalid or missing Special Service Request
Free Text Description of Goods Errors
TXT01
D
Invalid or missing free text description of goods details
TXT02
S
Syntax error - free text description of goods details - total characters cannot
exceed 545
33 | P a g e
Appendix F
Definitions
Special Cargo - is defined as where other government agencies (OGA), as well as
Customs Administrations, are involved in the permission to import and export.
Shipment Record – any record of the Cargo Contract preserved by the carrier,
evidenced by means other than an AWB.
Cargo Contract – a term used in the e-AWB Agreement and means a contract between
the forwarder and carrier, for the transportation and settlement of a specific cargo
shipment.
Cargo Receipt –a document which is provided to the forwarder by the carrier
electronically or in paper form, evidencing the Shipment Record as a substitution for
the issuance of an AWB and which permits identification of the shipment that has been
accepted and deemed “Ready for Carriage” (RCS).
Warehouse Receipt – an electronic FSU message or paper document provided to
the shipper by the carrier acknowledging the receipt of the cargo shipment as
“Freight on Hand” (FOH) for carriage by air. At a minimum, the Warehouse Receipt
must have:
The weight and number of pieces of the cargo shipment;
The date, time and place received by the Carrier; and,
Reference the shipment identification number covering the specific cargo
shipment.
34 | P a g e
To the extent is readily available, an indication of the places of departure, destination
and, if applicable, agreed stopping places should also be specified.
EAW – special handling code indicating that there is no document pouch
accompanying the cargo to destination.
EAP – special handling code indicating that there is a document pouch to be tendered
by the freight forwarder, containing original shipping documents which are required by
customs at destination.
ECC – special handling code indicating that there is no paper AWB accompanying the
shipment to the destination; ECC code will be entered by the Airline.
ECP – special handling code indicating that there is a copy of the paper AWB
accompanying the shipment to the destination merely in compliance of local customs
regulations/requirements.
Others –
EAW e-freight Consignment With No Accompanying Paper Documents
ECC Consignment established with an electronically concluded cargo contract
with no accompanying paper air waybill
ECP Consignment established with a paper air waybill contract being printed
under an e-AWB agreement
EDI Electronic Data Interchange
FF Freight Forwarder
FFM Cargo-IMP Airline Flight Manifest Message
FHL Cargo-IMP House Manifest Data Message
FMA Cargo-IMP Acknowledgment Message
FNA Cargo-IMP Rejection (Error) Message
FOH Freight on Hand
FSU Cargo-IMP Status Update Message
FWB Cargo-IMP Air Waybill Data Message
GHA Ground Handling Agent
IATA International Air Transport Association
ND Dimension
NS Volume
RCS Cargo and Documents are Received Ready for Carriage
SPH Special Handling Codes
XFFM Cargo-XML Airline Flight Manifest Message
XFHL Cargo-XML House Manifest Data Message
XFNM Cargo-XML Notification Message
XFSU Cargo-XML Status Update Message
35 | P a g e
XFWB Cargo-XML Air Waybill Data Message
MeA - Multilateral e-AWB Agreement: Electronic Air Waybill Resolution 672
OSI – Other Service Information (segment of the FWB)
SSR – Special Service Request (segment of the FWB)
CCS – Cargo Community System
CTO - Cargo Terminal Operator
PCS – Pieces
WGT – Weight (Actual)
VOL – Volume (Weight)
DG - Dangerous Goods
DGD – Dangerous Goods Declaration
DGD CAO – Dangerous Goods Declaration – Cargo Aircraft Only
MAWB – Master Air Waybill
CCA – Cargo Correction Advice
FLT - Flight Bookings (segment of the FWB)
RTG – Routing (segment of the FWB)
SHP – Shipper Details (segment of the FWB)
FX – Telefax (Contact Identifier)
TE – Telephone (Contact Identifier)
TL – Telex (Contact Identifier)
FWB/16 – FWB Version 16
FWB/17 – FWB Version 17
AGT - Agent Details (segment of the FWB)
SSR – Special Service Request (segment of the FWB)
ACC – Accounting Information (segment of the FWB)
AU - Australia
CAN – Customs Authority Number
CVD – Charge Declaration (segment of the FWB)
RTD – Rate Description (segment of the FWB)
P/C – Prepaid/Collect
NG – Goods Description for non-consol cargo
NC – Goods Description for Consolidation cargo
NV – Volume
OTH – Other Charges (segment of the FWB)
ISU – Carrier’s Execution (segment of the FWB)
BUP – Bulk Unitization Programme, Shipper/Consignee Handled Unit
MIP – Message Improvement Program
RACA - Regulated Air Cargo Agent
OTS - Office of Transport Security
SLAC – Shipper’s Load and Count
