Aviation Fuel Data Standards Group

Aviation Fuel Data Standards Group

XML Standard for Electronic Fuel Transaction

Version 3.0.0
22 August 2013

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Copyrights

API © 1996
On behalf of AVNET, a joint project of The American Petroleum Institute, The Air Transport Association of
America and The International Air Transport Association. All rights reserved throughout the world.

This document is protected under the copyright laws of the United States and other countries as an unpublished work.
This document contains information that is proprietary and confidential to International Air Transport Association,
which shall not be disclosed outside or duplicated, used, or disclosed in whole or in part for any purpose other than for
evaluation purposes. Any use or disclosure in whole or in part of this information without the express written
permission of International Air Transport Association is prohibited.

© 2005-2007 International Air Transport Association (Unpublished). All rights reserved.

Page 2 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Table of Contents

Document Revision History .................................................................................................................4

Overview ............................................................................................................................................................5
Proposed Electronic Fuel Transaction Standard ..............................................................................................5
Review of Sample Electronic Fuel Transactions...............................................................................................5
Table 1 - Fuel Transaction Standard: changes compared to version 2.0.2 ....................................................6
Table 2 - Proposed Electronic Fuel Transaction Standard Layout ...................................................................7
Currency Conversion: Examples ................................................................................................................26

Page 3 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

DOCUMENT REVISION HISTORY

Revision Record

Version Date Modified Sections / Description
1.0 Draft 9 October 2004
0.0.1 2 December 2004 Laurie Kern (BE) /Initial Draft, based upon Fuel Invoice draft
0.0.2 28 February 2005
0.0.3 28 April 2005 Laurie Kern (BE) changes made per Task Force meeting
Release Candidate (RC) 1.0 5 July 2005
Release Candidate (RC) 1.2 31 October 2005 Laurie Kern (BE) split nodes based upon Contract/Non-Contract payment and
2.0.0 16 December 2005 other changes per task force discussions
2.0.1 15 January 2006 Chaithanya Kadiyala (BE) made changes as per task force discussions and
suggestions.
2.0.2 30 January 2006
Bryan Terry (BE) made changes per Group discussion and suggestions.
3.0.0 26 June 2007
3.0.0 09 August 2007 Bryan Terry (BE) made changes per Group discussion and suggestions.
3.0.0 22 August 2013
Mark Johnson (CGFL) amendment s relating to the structure of the schema
following Miami discussions. Also now references an external file (namespace)
for its enumeration content.
Version formating amended to Mijor, Minor and Revision for easy versioning
control
Amended AircraftMeasurements element under the IPTLine node to optional
(as stated in the documentation)
Added optional field (Remark) to LocalTax and SubTax elements. This allows
additional code information to be passed and ensures consistency with the
Charges element
Documentation amended to include additional payment types “CA” and “CC”
which were originally under the cash portion (now merged into one)
Documentation also updated to reflect changes in codes for the
TicketReferenceValueType field to mirror the invoice schema

Various changes made by the Fuel Data Standards Group.

Error in documentation corrected (lines 266 to 272, level updated)

Update on row 165 till 167 for PADIS

Page 4 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Overview

PURPOSE:

The Aviation Fuel Data Standards Group (the “Group”) is proposing a standardized electronic Fuel
Transaction that can be used by Fuel Suppliers / Into-Plane Service Providers / FBOs to forward Fuel
Transaction information to both fuel suppliers and airlines in the airline industry. The purpose of the proposed
standard is to facilitate a cost effective exchange of data between parties to ensure an accurate
consummation of a buy/sell transaction.

Background:

The Group has created a proposal for a standardized format for electronic Fuel Transactions. An initial
meeting was held with the Group to review the need for a standardized electronic Fuel Transaction format and
to discuss the requirement data elements and layout. Based on the results of this workshop, a standardized
file layout has been proposed. Additional comments received after the conclusion of the meetings have been
incorporated into this document. Other comments and suggestions may be incorporated with future revisions
to the standard.

Proposed Electronic Fuel Transaction Standard

The proposed Electronic Fuel Transaction standard is based on the existing JetA.com standards. The JetA
requirements were reviewed along with anecdotal usage of the EDI standards and comments from the IATA Fuel
XML Task Force to develop the proposed XML standard. The proposal contains the ticket data elements that are
necessary to provide information to the customer for review, attestation and approval of a fuel purchase.

The proposed fuel transaction standard is presented in Table 1 and the XML schema is available in Appendix. The
XML schema may vary in structure as represented in Table 1 due to the use of XML standards in constructing the
schema. Table 1 is constructed as follows:
1. Structure – the major sections of a Electronic Fuel Transaction. The level numbers represent subsets of the

structure. Depending on the nature of the subset, the subset may be repeated to provide additional
information. In addition, a subset may be optional. If a subset is optional, any required element is only
required when the subset is used.
2. Element – the element represents the ticket data element containing a value or information required by the
supplier or customer to process and settle a Electronic Fuel Transaction. Some elements may be required
while others are optional. The values of an element may follow the existing industry standards or specific
requirements by the parties involved.
3. Description – the description provides additional information or clarification of the Element.
4. Repeat – indicates how many times the element or structure can be present at that level in the structure.
5. Element Attributes – describes the attributes of each element: R=required, O=optional, C=Choice,
Type=numeric or alphanumeric, Length=length of element and if numeric what type of number.
6. Value Source – identifies the source of the value or brief description of the value.
7. Notes – additional information on the use of the ticket element.

Review of Sample Electronic Fuel Transactions

Several fuel suppliers agreed to provide samples of their ticket formats representing different types of
Electronic Fuel Transactions. Once these samples are received, the samples will be compared to the
proposed ticket layout to identify if any structural issues are evident with the proposed standard.

Page 5 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Table 1 - Fuel Transaction Standard: changes compared to version 2.0.2

This table highlights the differences between the previous production version 2.0.2 and the new version 3.0.0

ROW ELEMENT NAME NOTES
1 OpenTag Includes optional link to a HTML layout
4 FuelTransactionTransmissionId New required element
14 TicketType Added new value: “D” for delete
71-77 CurrencyConversion New optional element (complex type with subelements)
Replaces the optional element “ExchangeRate” from version 2.0.2
87-93 LocalTaxCurrencyConversion New optional element (complex type with subelements)
Replaces the optional element “ExchangeRate” from version 2.0.2
111-117 SubTaxCurrencyConversion New optional element (complex type with subelements)
Replaces the optional element “ExchangeRate” from version 2.0.2
144 MeterReadingStart Expanded size from 18,4 to 18,6
145 MeterReadingEnd Expanded size from 18,4 to 18,6
146 MeterQuantityDelivered Expanded size from 18,4 to 18,6
148 TotalQuantity Expanded size from 18,4 to 18,6
157 DepartureFuelQuantity Expanded size from 18,4 to 18,6
163 RequiredTankQuantity Expanded size from 18,4 to 18,6
167 TankQuantityDelivered Expanded size from 18,4 to 18,6
171 TotalFuelQuantity Expanded size from 18,4 to 18,6
226-232 CurrencyConversion New optional element (complex type with subelements)
Replaces the optional element “ExchangeRate” from version 2.0.2
242-248 LocalTaxCurrencyConversion New optional element (complex type with subelements)
Replaces the optional element “ExchangeRate” from version 2.0.2
266-272 SubTaxCurrencyConversion New optional element (complex type with subelements)
Replaces the optional element “ExchangeRate” from version 2.0.2
299 MeterReadingStart Expanded size from 18,4 to 18,6
300 MeterReadingEnd Expanded size from 18,4 to 18,6
301 MeterQuantityDelivered Expanded size from 18,4 to 18,6
303 TotalQuantity Expanded size from 18,4 to 18,6
313 TotalFuelQuantity Expanded size from 18,4 to 18,6
316 FuelTransactionTotalFuelQuantity Expanded size from 18,4 to 18,6

Page 6 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Table 2 - Proposed Electronic Fuel Transaction Standard Layout

Note: There are instances in the table where a parent node is qualified as optional but the child elements are qualified as required. This represents that if the
parent node is present, then the child elements, which have been qualified as required need to be present.

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

1 OpenTag <?xml version="1.0" encoding="UTF- Opening tag and optional link to a HTML
8" ?> layout (substitute the actual stylesheet
<?xml-stylesheet type="text/xml" name for “name_of_stylesheet”).
href="name_of_stylesheet.xsl"?> Code directory and base data type are
referenced.

2 0 FuelTransactionTransmission Parent Node for all tickets 1 R
R
3 1 FuelTransactionTransmissionHeader Header information node in the 1 R

transmission R

4 2 FuelTransactionTransmissionId Unique identifier for the file 1 AN 50 This will be referenced in the

transmitted. Acknowledgment message if used.

5 2 FuelTransactionCreationDate** Date of creation of the Transaction file 1 DT Format is of format:

YYYY-MM-DD hh:mm:ss

6 2 FuelTransactionVersion Current Version of the Schema 1R AN 8 Use the current Version of this

document

7 1 FuelTransaction 1- There can be multiple FuelTransaction nodes
48000
but under this node, there is a choice of

IPTContract, IPTOther or BMTicket. (You can

choose only one per FuelTransaction)

8 2 IPTransaction Parent for all into plane transactions 1 C This is the root for IntoPlane Transactions
9 3 Header R
10 4 IntoPlaneCode R only. It is an choice field with BM Transaction
11 4 IntoPlaneName O
12 4 AirportCode 1 R AN 5 Refer to IATA code directory Code List to be developed
Code of Company loading fuel into plane 1 IntoPlane Codes Table R

Name of Company loading fuel into 0-1 AN 25
plane. 1
A 5 Refer to IATA code directory Strictly airport code
Fueler must be associated to a location Section A (Airport Codes)
group that contains this Airport code.

13 4 TicketNumber Delivery Ticket Number 1 R AN 20
Type of Ticket
14 Attribute: 1 R AN 3 Use list of codes: D shall not be used for Canceled tickets or
TicketType
• O = Original when ticket status is Final
(of TicketNumber)
• R = Reissue Cancel means that the ticket may be reissued

• C = Cancel (R) and an invoice will be issued (not for
• D = Delete Delete)

Add others as required

Page 7 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

15 Attribute: Source of ticket 1 R A 1 Codes
TicketSource • M - Manual
Status of ticket 1 • E-Electronic Intended for use related to stock validation
(of TicketNumber)
16 Attribute: Positive or negative depending on 1 R A 1 Codes Required if ticket type was cancel
cancel or reissue P = Pending
TicketStatus F = Final Recommended elements
(of ticket number) Recommended field to create a unique 1 - location code
17 Attribute: ticket identifier O Use list of codes: - supplier code
TicketCancelOperator • P = Positive - date
(of ticket number) Used to reference an earlier ticket. 0-1 • N = Negative - ticket number
18 4 UniqueTicketID** Date from original ticket 0-1 - ticket type
1 O AN 50 A verification of the ticket number should be
19 4 PreviousTicketNumber done against the system.
O AN 20 Required if TicketType = R or C
20 Attribute:
PreviousITPDate R DT

(of OriginalTicket) R DT
21 4 TransactionDate

22 4 Comments For other notes 0-1 O AN 512
23 3 FlightInformation Details of the Flight receiving the 1 R
24 4 AirlineFlightID IntoPlane Transaction 1
25 4 AircraftIdentification Airlines Flight Identification Number 1 R AN 10 AF=Airline Flight Identification XXX if no flight number is available.
26 4 InternationalFlight Aircraft Identification(Tail or Nose) 1 Number
27 4 TicketReferenceValue 0-50
Reference value R AN 10 AR=Aircraft Identification (tail or
nose)

R Boole 1 (Note: Boolean = true/false or
an 1/0)

O AN 50

Page 8 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

28 Attribute: Reference type such as contract 1 R AN 3 Use list of codes: Recommended to use IATA aircraft codes
TicketReferenceValueType number, purchase order number,
equipment number, aircraft number, • AC = Aircraft Type when necessary
(of TicketReferenceValue) flight number, ticket number, next
destination; final destination etc. • AID= Authority
29 4 FlightType issued equipment Reference Table Q (Dimension B)

30 Attribute: • BAT=Batch
FlightServiceType
• BOL=Bill of Lading
(of FlightType)
31 4 ScheduledFlightDate • CID=Company
32 3 PaymentInformation
33 4 PaymentType Issued Equipment ID

• CTN=Contract No.

• D = Delay (enter

reason for delay)

• FDT=Final

Destination

• FO = Flight Origin

• NDT=Next

Destination

• OFD = Origin Flight

Date (YYYY-MM-

DD)

• identification

• PO=Purchase Order

• SO=Sales Order

• TAX=Tax

Create code values if

necessary

0-1 O AN 3 Use list of codes:

• P = Passenger

• C = Cargo

• M = Military

• CH = Charter

• FF = Ferry Flight

• TF = Test Flight

• TR = Training Flight

0-1 O AN 3 Use list of codes:

• AH = Ad-Hoc

• S= Scheduled

Scheduled Date of the Flight (Original) 0-1 O DT
(YYYY-MM-DD)
1 R
Method of Payment 1
R AN 3 Use list of codes: For contract – CN and CO

• CN = Carnet If CO, then CardInformation is Optional, if CN

• CO = Contract Card Information is required

• CC = Credit Card If CA ot CC is used, the Amount received field
must be populated with the value of the sale.
• CA = Cash

Add others as required

Page 9 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
34 4 CardInformation Repeat Req Type Size

0-1 O

35 5 CardName Name on the Card 1 R AN 35 Required when PaymentType=CN or CC
36 5 CardNumber Account Number on the card 1 R AN 20
37 5 CardExpiry Date Card expires (YYYY-MM-DD) 1 R DT Required when PaymentType=CN or CC

38 5 CardSecurityCode Amount of Cash or Card charge 1 O N4 Required when PaymentType=CN or CC
39 5 AmountReceived 1 R N 18,2 Date must be greater than or equal to the
current date of the airport location listed in the
40 Attribute: AirportCode
Currency
(of AmountReceived) Required when PaymentType=CA or CC.
Amount must be positive
41 3 IPTLine
42 4 IPTransactionType 0-1 O AN 3 Refer to IATA code directory Required if PaymentType= CC or CA
43 5 IPTransactionCode Section C (Currency Codes)

44 4 TransactionParties 1R
45 5 Sale 1R

46 6 ReceiverCode 1 R AN 3 Refer to IATA code directory Type of transaction
47 6 ReceiverName Table S (IntoPlaneTransaction
48 6 AccountCustomerNumber Codes)
49 6 SupplierOROwnerCode
50 6 SupplierOROwnerName 1C Use if a sale has been completed as a
51 5 NonSale result of the transaction. Usually as a
result of an IntoPlane transaction, but can
Page 10 of 28 also be used for Bulk Movement. The
Receiver Code will be required in this
instant

Airline Code 1 R AN 4 Refer to IATA code directory Airline Code receiving the IntoPlane

Receiving Party Table U (Receiver Codes) transaction
Who to bill
Company Code 0-1 O AN 50 Airline Name receiving the IntoPlane
Name of Company 1 R AN 20 transaction

1 R AN 5 Refer to IATA code directory Inventory holder’s code.
Table V – Supplier Codes

0-1 O AN 25 Inventory holder’s name.

1C Use if a sale has not been completed as a
result of the transaction. Usually as a
result of an Bulk Movement transaction

Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

52 6 ReceiverCode Airline Code 0-1 O AN 4 Refer to IATA code directory Airline Code receiving the IntoPlane

53 6 ReceiverName Table U (Receiver Codes) transaction

54 6 AccountCustomerNumber Receiving Party 0-1 O AN 50 Airline Name receiving the IntoPlane
55 6 SupplierOROwnerCode Who to bill 0-1 R AN 20 transaction

56 6 SupplierOROwnerName Company Code 1 R AN 5 Refer to IATA code directory Code List to be developed
57 4 MovementInformation Name of Company
Table V – Supplier Codes Inventory holder’s code.
58 Attribute:
Direction 0-1 O AN 25 Inventory holder’s name.
(of MovementInformation)
1R Information containing the movement of
59 5 ProductInformation the fuel product
60 6 ProductID 1 R AN 2 Use list of codes:
• TO Direction of the Movement
61 Attribute: • FR
ProductIDCustoms
1-200 R AN
(of ProductID)
62 Attribute: Identifying number/code of product or 1 R AN 15 Refer to IATA code directory For example: JetA, list to be developed
service 0-1 Section D (Product Codes)
ProductIDQualifier
(of ProductID) Indicates the customs status of fuel. O AN 3 Refer to IATA code directory For example: Bonded
Section P (Customs)
63 6 ProductDescription
Qualifier of product or service 0-1 O AN 4 Use Codes: Description of the product or any notes related
Description of product/service PRDT(Product) to the product.
FEE (Fee)
OTHR(Other)

0-1 O AN 25

64 6 Charges Extra Charges 0-1 O
65 7 Remark allow a further specification of 0-1 O AN 30
the charge where required.
66 7 UnitRate Pricing Unit Rate 1 R N 18,4
67 7 CurrencyCode CurrencyCode 1
68 7 UnitRateType Pricing type use for the unit rate 1 R AN 3 Refer to IATA code directory
Section C (Currency Code)
69 7 UOMFactor UOM Factor used to convert pricing 0-1
70 7 UOM Pricing Unit of Measure 1 R AN 3 Use list of codes:
71 7 CurrencyConversion • P=Percent
0-1 • FF = Flat Fee
Page 11 of 28 • UR = Unit Rate

Add others as required
O N 18,4

R AN 3 Refer to IATA code directory
Section E (UOM)

O Describes how an amount in CurrencyFrom
is converted into an amount in CurrencyTo.

Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

72 8 ConversionMechanism 1R AN 1 Valid values:
• M = Multiply
73 8 CurrencyFrom 1 R • D = Divide
R
74 Attribute: Factor that CurrencyFrom should be 1 AN 3 Use IATA Codes, Section C
FactorFrom multiplied with. R (Currency).
R
(of CurrencyFrom) 1 N9
75 8 CurrencyTo R
Factor that CurrencyTo should be 1 O AN 3 Use IATA Codes, Section C
76 Attribute: multiplied with. R (Currency).
FactorTo
Exchange rate value 1 O N9
(of CurrencyTo)
77 8 ExchangeRate Node listing all the local tax details 0- N 18,6
78 6 LocalTax unboun
Type of Tax such as GST, VAT, Federal ded AN 3 Refer to IATA code directory
79 Attribute: Excise, Custom, Petroleum, 1 Section F (TaxType Code)
LocalTaxType Environmental, Excise, tax exempt etc.
represented by the Invoice Lines 0-1 AN 35
(of LocalTax) Description of tax

80 7 LocalTaxDescription

81 7 LocalTaxCategoryCode Specific Tax codes within a tax type 0-1 O AN 3 Use list of codes: Required for VAT, excise tax;

82 7 LocalTaxLocalJurisdictionTaxBasis Tax basis for local tax jurisdiction • L=Lower Rate
83 7 LocalTaxJurisdictionCodeQualifier Identifies source of the tax jurisdiction
84 7 LocalTaxJurisdictionCode code • H=Higher rate
85 7 LocalTaxRateType Tax jurisdiction code
Indicates how rate is determined • S=Standard rate
86 7 LocalTaxPricingCurrencyCode
87 7 LocalTaxCurrencyConversion Currency (Standard ISO Code) • Z=Zero rated goods

Page 12 of 28 Create additional code values if
necessary

0-1 O AN 2 Use list of codes:

• GR=Gross

• NT=Net

0-1 O AN 10 No List at this time Code List to be developed

0-1 O AN 10 No List at this time All State and local taxes
Code List to be developed
1 R AN 2 Use list of codes:
• P=Percent
• FF = Flat Fee
• UR = Unit Rate

1 R AN 3 Refer to IATA code directory Describes how an amount in CurrencyFrom
0-1 Section C (Currency Code) is converted into an amount in CurrencyTo.

O

Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

88 8 ConversionMechanism 1 R AN 1 Valid values:
• M = Multiply
89 8 CurrencyFrom Factor that CurrencyFrom should be 1 • D = Divide
multiplied with. 1
90 Attribute: R AN 3 Use IATA Codes, Section C
FactorFrom (Currency).

(of CurrencyFrom) R N9
91 8 CurrencyTo
Factor that CurrencyTo should be 1 R AN 3 Use IATA Codes, Section C
92 Attribute: multiplied with. (Currency).
FactorTo
1 R N9
(of CurrencyTo)
93 8 ExchangeRate Exchange rate value 1 R N 18,6
94 7 LocalTaxPricingUOM 0-1
UOM associated with pricing quantity O AN 3 Refer to IATA code directory
and tax rate; Section E (UOM)

95 7 LocalTaxPricingUOMFactor UOM factor used to convert for tax 0-1 O N 18,6
96 7 LocalTaxPricingRate calculation 0-1
97 7 LocalTaxPricingAmount 1 O N 18,6 Can be a flat fee.
98 7 LocalTaxTicketCurrencyCode Tax rate expressed in decimal format 1
used in pricing R N 18,2

Tax represented for the pricing quantity R AN 3 Refer to IATA code directory
and rate Section C (Currency Code)

Currency (Standard ISO Code) for
Invoice Tax

99 7 LocalTaxTicketUOM UOM associated with invoice quantity 0-1 O AN 3 Refer to IATA code directory
and invoice tax rate; Section E (UOM)

100 7 LocalTaxTicketUnitRate Tax rate expressed in decimal format 1 R N 18,6
used for the invoice

101 7 LocalTaxTicketAmount Tax represented for the invoice quantity 1 R N 18,2
102 7 SubTax and rate O
Node additiona1 tax on tax 0- R AN 3 Refer to IATA code directory
103 Attribute: unboun Section F (TaxType Code)
SubTaxType Type of Tax such as GST, VAT, Federal ded O
104 8 Excise, Custom, Petroleum, 1 AN 35
105 8 (of SubTax) Environmental, Excise, tax exempt etc.
represented by the Invoice Lines 0-1
SubTaxDescription Description of tax

SubTaxCategoryCode Specific Tax codes within a tax type 0-1 O AN 3 Use list of codes: Required for VAT, excise tax;

• L=Lower Rate

• H=Higher rate

• S=Standard rate

• Z=Zero rated goods

Create additional code values if

necessary

Page 13 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

106 8 SubTaxJurisdictionTaxBasis Tax basis for local tax jurisdiction 0-1 O AN 2 Use list of codes:
107 8 SubTaxJurisdictionCodeQualifier • GR=Gross
108 8 SubTaxJurisdictionCode Identifies source of the tax jurisdiction 0-1 • NT=Net i.e.: State, Federal, City
109 8 SubTaxRateType code 0-1
O AN 10 No List at this time Code List to be developed
Tax jurisdiction code Code List to be developed
O AN 10 No List at this time
Indicates how rate is determined 1
R AN 2 Use list of codes:
• P=Percent
• FF = Flat Fee
• UR = Unit Rate

110 8 SubTaxPricingCurrencyCode Currency (Standard ISO Code) 1 R AN 3 Refer to IATA code directory
111 8 SubTaxCurrencyConversion 0-1 Section C (Currency Code)
112 9 ConversionMechanism 1
O Describes how an amount in CurrencyFrom
113 9 CurrencyFrom 1 is converted into an amount in CurrencyTo.
114
Attribute: Factor that CurrencyFrom should be 1 R AN 1 Valid values:
115 9 FactorFrom multiplied with. • M = Multiply
116 • D = Divide
(of CurrencyFrom)
117 9 CurrencyTo R AN 3 Use IATA Codes, Section C
118 8 (Currency).
Attribute:
FactorTo R N9

(of CurrencyTo) 1 R AN 3 Use IATA Codes, Section C
ExchangeRate (Currency).
SubTaxPricingUOM Factor that CurrencyTo should be 1
multiplied with. R N9

Exchange rate value 1 R N 18,6
0-1 O AN 3 Refer to IATA code directory
UOM associated with pricing quantity
and tax rate; Section E (UOM)

119 8 SubTaxPricingUOMFactor UOM factor used to convert for tax 0-1 O N 18,6
120 8 SubTaxPricingAmount calculation 1
121 8 SubTaxPricingRate 1 R N 18,2
122 8 SubTaxTicketCurrencyCode Tax represented for the pricing quantity 1
and rate R N 18,6 Can be a flat fee.

Tax rate expressed in decimal format R AN 3 Refer to IATA code directory
used in pricing Section C (Currency Code)

Currency (Standard ISO Code) for O AN 3 Refer to IATA code directory
Invoice Tax Section E (UOM)

123 8 SubTaxTicketUOM UOM associated with invoice quantity 0-1
and invoice tax rate;

Page 14 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

124 8 SubTaxTicketUnitRate Tax rate expressed in decimal format 1 R N 18,6
used for the invoice
R N 18,2
125 8 SubTaxTicketAmount Tax represented for the invoice quantity 1 O AN 25
and rate O AN 25
126 5 Plant 0-1
127 5 StorageLocation 0-1 AN 15 Incase of multiple inventory locations
,guessing this speciofies the storage
128 5 StandNumber Stand/Gate/Bay at which the fuel was 0-1 O source.???
129 5 Equipment delivered R
Parent Element 1- Optional, but highly recommended.
unbou R
130 6 FuelingEquipmentID Used to identify the fueler or dispensing nded R AN 15 Name of code of the equipment used
131 6 FuelingType vehicle ID 1 Only used if fuel type is hydrant
Transport Type AN 3 Use list of codes:
1 • HYD=Hydrant
• REF=Re-Fueler
132 6 PITNumber The hydrant pit number from which the 0-1 O
133 6 Operator fuel was delivered 1 R Add others as required
134 6 AverageFuelTemperature 1 R AN 15
Identification number, code or name of
person who has delivered the fuel AN 50 Name of code of the Operator

135 Attribute: Unit of Measure used for Temperature 1 R AN 3 Use list of codes: Fahrenheit or Celsius temperature
136 6 TUOM 1-2 • C – Celsius measurement
• F - Fahrenheit
(of AverageFuelTemperature)
R
DensityInformation

137 Attribute: Type of Density 1 R AN 3 Use list of codes: Measured or Standard Density
138 7 DensityType Density of Fuel. 1
• MEA – Measured
(of DensityInformation)
• STD - Standard
Density
O N 18,4 Should be between 740 and 860 , 0.74 and

0.86 or 6.175 and 7.177 measured in KG/M3,

KG/LT, or LB/USG respectively.
Must have either density or specific gravity

required.

139 Attribute: Unit of Measure used for Density 1 R AN 3 Refer to IATA code directory
140 7 DensityUOM 1
Section E (UOM)
(of Density)
R N 4,1 Required if Net Quantity Delivered is entered.
Temperature Temperature should be between -47C and
50C or -53F and 122F.

Page 15 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

141 Attribute: Unit of Measure used for Temperature 1 R AN 1 Use list of codes:
TUOM • C = Celsius
142 6 1-10 • F = Fahrenheit
143 (of Temperature) 1
R
144 7 MeterReading
O AN 10
Attribute:
MeterID Starting Meter reading 1 R N 18,6 Must be entered in meter reading ending is
Ending Meter reading 1 entered
(of Meter Reading) 1
MeterReadingStart UOM of Quantity Delivered 1

145 7 MeterReadingEnd R N 18,6 Must be entered in meter reading start is
146 7 MeterQuantityDelivered R N 18,6 entered

Check for difference between meter reading
start and meter reading end.

147 Attribute: R AN 3 Refer to IATA code directory ? correct dimension
MQDUOM Section E (UOM)
148 5
149 (of MeterQuantityDelivered) Sum of all meter quantity 1-3 R N 18,6 Once for gross or once for Net or both
TotalQuantity Identities gross or net quantity 1
150 R AN 2 Use list of codes
Attribute: Unit of Measure 1 • GR=Gross
151 5 TQDFlag • NT=Net
152 6
(of TotalQuantity) R AN 3 Refer to IATA code directory Make sure it covers weight
Section E (UOM)
Attribute:
TQDUOM 1 R
R DT
(of TotalQuantity) Date/Time started, must be less than 1
TransactionTime Date/Time finished 1
(YYYY-MM-DDThh:mm:ss) 0-1
LocalDateTimeStart 0-1
Date/Time started, must be greater than 0-1
153 6 LocalDateTimeFinished Date/Time started R DT “Ticket Date”
(YYYY-MM-DDThh:mm:ss)
154 6 GMTDateTimeStart O DT
Date/Time started, must be less than
155 6 GMTDateTimeFinished Date/Time finished O DT
(YYYY-MM-DDThh:mm:ss)

Date/Time started, must be greater than
Date/Time started
(YYYY-MM-DDThh:mm:ss)

156 4 AircraftMeasurements Amount of fuel in the aircraft 1 O tanks
157 5 R N 18,6
158 DepartureFuelQuantity Unit of Measure 1 R AN 3 Refer to IATA code directory

159 5 Attribute: Amount + / - allowed 0-1 Section E (UOM)
160 DFQUOM 1
If tolerance is a percent or quantity of O N 18,4
(of DepartureFuelQuantity) fuel amount requested R AN 3 Use code list:
TolerenceLevel
• P=Percent
Attribute: • Q=Quantity
TolerenceLevelType
Version 3.0.0
(of TolerenceLevel)

Page 16 of 28

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

161 5 TankMeasurements 1-20 R Use multiple if need to track individual
162 6 AircraftTankID 0-1
163 6 RequiredTankQuantity 0-1 O AN 20

Request from receiver for fuel amount O N 18,6 Covered by PADIS candidate for delition for

next release

Requested from the receiver for fuel amount

164 Attribute: Unit of Measure 1 R AN 3 Refer to IATA code directory Covered by PADIS candidate for delition for
165 6 RTQUOM
Section E (UOM) next release
(of RequiredTankQuantity)
0-1 O N 18,4 Covered by PADIS candidate for delition for
PrefuelTankQuantity

next release.

RTQ= PTQ+TQD

166 Attribute: Unit of Measure 1 R AN 3 Refer to IATA code directory
167 6 PTQUOM Section E (UOM)

(of PrefuelTankQuantity) Measured Quantity delivered. 1 R N 18,6 In case of de-fueling, then quantity will be
Unit of Measure 1 negative.
TankQuantityDelivered

168 Attribute: R AN 3 Refer to IATA code directory
169 3 TQDUOM Section E (UOM)

(of TankQuantityDelivered) 1 R

Summary

170 4 FuelTransactionLineCount Total Line counts for tickets 1 R N 18 Count of the FuelTransactionLine elements for
171 4 TotalFuelQuantity 1 R N 18,6 a FuelTransaction

172 2 BMTransaction Parent for all into plane transactions 1 C This is the root for IntoPlane Transactions
only. It is an choice field with BM
173 3 Header 1 Transaction
174 4 IntoPlaneCode Code of Company loading fuel into plane 1
R

R AN 5 Refer to IATA code directory Code List to be developed

IntoPlane Codes Table Q Recommended starting source is IFQP

codes**

175 4 IntoPlaneName Name of Company loading fuel into 0-1 O AN 25
176 4 AirportCode plane. 1
R A 5 Refer to IATA code directory Strictly airport code
Fueler must be associated to a location Section A (Airport Codes)
group that contains this Airport code.

177 4 TicketNumber Delivery Ticket Number 1 R AN 20

Page 17 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size
Intended for use related to stock validation
178 Attribute: Type of Ticket 1 R AN 3 Use list of codes:
TicketType • O = Original Required if ticket type was cancel
• R = Reissue
(of TicketNumber) • C = Cancel Recommended elements
- location code
179 Attribute: Source of ticket 1 Add others as required - supplier code
180 TicketSource - date
181 Status of ticket 1 R A 1 Codes - ticket number
182 4 (of TicketNumber) • M - Manual - ticket type
Positive or negative depending on 1 • E-Electronic A verification of the ticket number should be
Attribute: cancel or reissue done against the system.
TicketStatus R A 1 Codes Required if TicketType = R or C
(of ticket number) Recommended field to create a unique 1 • P = Pending
ticket identifier • F = Final For contract – CN and CO
Attribute: If CO, then CardInformation is Optional, if CN
TicketCancelOperator O Use list of codes: Card Information is required
(of ticket number) • P = Positive
• N = Negative
UniqueTicketID**
O AN 50

183 4 PreviousTicketNumber Used to reference an earlier ticket. 0-1 O AN 20
Date from original ticket
184 Attribute: 0-1 R DT
185 4 PreviousITPDate For other notes
Method of Payment 1 R DT
(of OriginalTicket) 0-1
1 O AN 512
TransactionDate 1 R
R AN 3 Use list of codes:
186 4 Comments
187 3 PaymentInformation • CN = Carnet
188 4 PaymentType • CO = Contract
Add others as required
189 4 CardInformation 0-1 O

190 5 CardName Name on the Card 1 R AN 35 Required when PaymentType=CN
191 5 CardNumber Account Number on the card 1 R AN 20
192 5 CardExpiry Date Card expires (YYYY-MM-DD) 1 R DT Required when PaymentType=CN

Required when PaymentType=CN .
Date must be greater than or equal to the
current date of the airport location listed in the
AirportCode

193 5 CardSecurityCode 1 O N4

Page 18 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
194 5 AmountReceived Amount of Cash or Card charge Repeat Req Type Size
Required when PaymentType=Cash or Credit
1 R N 18,2 Card. IF Cash, then amount must be positive

195 Attribute: 0-1 O AN 3 Refer to IATA code directory Required if PaymentType= Credit Card or
Currency Section C (Currency Codes) Cash
196 3
197 4 (of AmountReceived) 1R
BMLine 1 R AN

BMTransaction 1 R AN 3 Refer to IATA code directory Type of transaction
Bulk Movement Transaction
198 5 BMTransactionCode Codes (Table T)

199 4 TransactionParties 1C Use if a sale has been completed as a
200 5 Sale result of the transaction. Usually as a
result of an IntoPlane transaction, but can
also be used for Bulk Movement. The
Receiver Code will be required in this
instant

201 6 ReceiverCode Airline Code 1 R AN 4 Refer to IATA code directory Airline Code receiving the IntoPlane

Receiving Party Table U (Receiver Codes) transaction
Who to bill
202 6 ReceiverName Company Code 0-1 O AN 50 Airline Name receiving the IntoPlane
Name of Company 1 R AN 20 transaction
203 6 AccountCustomerNumber
204 6 SupplierOROwnerCode Airline Code 1 R AN 5 Refer to IATA code directory Inventory holder’s code.
Table V – Supplier Codes
205 6 SupplierOROwnerName Receiving Party
206 5 NonSale Who to bill 0-1 O AN 25 Inventory holder’s name.
Company Code
Name of Company 1C Use if a sale has not been completed as a
result of the transaction. Usually as a
result of an Bulk Movement transaction

207 6 ReceiverCode 0-1 O AN 4 Refer to IATA code directory Airline Code receiving the IntoPlane

Table U (Receiver Codes) transaction

208 6 ReceiverName 0-1 O AN 50 Airline Name receiving the IntoPlane
0-1 R AN 20 transaction
209 6 AccountCustomerNumber
210 6 SupplierOROwnerCode 1 R AN 5 Refer to IATA code directory Inventory holder’s code.

211 6 SupplierOROwnerName Table V – Supplier Codes
212 4 MovementInformation
0-1 O AN 25 Inventory holder’s name.

1R Information containing the movement of
the fuel product

Page 19 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

213 Attribute: 1 R AN 2 Use list of codes: Direction of the Movement
214 5 Direction
215 6 • TO
216 (of MovementInformation)
217 ProductInformation • FR

218 6 ProductID 1-200 R

Attribute: Identifying number/code of product or 1 R AN 15 Refer to IATA code directory For example: JetA, list to be developed
ProductIDCustoms service 0-1 Section D (Product Codes)

(of ProductID) Indicates the customs status of fuel. O AN 3 Refer to IATA code directory For example: Bonded
Attribute: Section P (Customs)

ProductIDQualifier Qualifier of product or service 0-1 O AN 4 Use Codes:
(of ProductID) Description of product/service
• PRDT(Product)
ProductDescription
• FEE (Fee)

• OTHR(Other)

0-1 O AN 25 Description of the product or any notes related

to the product.

219 6 Charges Extra Charges 0-1 O
220 7 Remark allow a further specification of 0-1
the charge where required. O AN 30
221 7 UnitRate 1
222 7 CurrencyCode Pricing Unit Rate 1 R N 18,4
CurrencyCode 1
223 7 UnitRateType R AN 3 Refer to IATA code directory
Pricing type use for the unit rate Section C (Currency Code)

224 7 UOMFactor UOM Factor used to convert pricing 0-1 R AN 3 Use list of codes:
225 7 UOM Pricing Unit of Measure 1 • P=Percent
226 7 CurrencyConversion • FF = Flat Fee
0-1 • UR = Unit Rate
227 8 ConversionMechanism
1 Add others as required
O N 18,4
228 8 CurrencyFrom Factor that CurrencyFrom should be 1
229 multiplied with. 1 R AN 3 Refer to IATA code directory
Attribute: Section E (UOM)
230 8 FactorFrom 1
O Describes how an amount in CurrencyFrom
(of CurrencyFrom) is converted into an amount in CurrencyTo.
CurrencyTo
R AN 1 Valid values:
• M = Multiply
• D = Divide

R AN 3 Use IATA Codes, Section C
(Currency).

R N9

R AN 3 Use IATA Codes, Section C
(Currency).

Page 20 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

231 Attribute: Factor that CurrencyTo should be 1 R N9
FactorTo multiplied with. R N 18,6
232 8 O
233 6 (of CurrencyTo) Exchange rate value 1 R AN 3 Refer to IATA code directory
ExchangeRate Section F (TaxType Code)
Node listing all the local tax details 0- O
LocalTax unboun AN 35
Type of Tax such as GST, VAT, Federal ded
234 Attribute: Excise, Custom, Petroleum, 1
235 7 LocalTaxType Environmental, Excise, tax exempt etc.
represented by the Invoice Lines 0-1
(of LocalTax) Description of tax

LocalTaxDescription

236 7 LocalTaxCategoryCode Specific Tax codes within a tax type 0-1 O AN 3 Use list of codes: Required for VAT, excise tax;

• L=Lower Rate

• H=Higher rate

• S=Standard rate

• Z=Zero rated goods
Create additional code values if

necessary

237 7 LocalTaxLocalJurisdictionTaxBasis Tax basis for local tax jurisdiction 0-1 O AN 2 Use list of codes:

• GR=Gross

• NT=Net

238 7 LocalTaxJurisdictionCodeQualifier Identifies source of the tax jurisdiction 0-1 O AN 10 No List at this time Code List to be developed
239 7 LocalTaxJurisdictionCode code 0-1
O AN 10 No List at this time All State and local taxes
Tax jurisdiction code Code List to be developed
R AN 2 Use list of codes:
240 7 LocalTaxRateType Indicates how rate is determined 1 • P=Percent
• FF = Flat Fee
• UR = Unit Rate

241 7 LocalTaxPricingCurrencyCode Currency (Standard ISO Code) 1 R AN 3 Refer to IATA code directory
242 7 LocalTaxCurrencyConversion 0-1 Section C (Currency Code)
243 8 ConversionMechanism 1
O Describes how an amount in CurrencyFrom
244 8 CurrencyFrom Factor that CurrencyFrom should be 1 is converted into an amount in CurrencyTo.
245 multiplied with. 1
Attribute: R AN 1 Valid values:
246 8 FactorFrom • M = Multiply
• D = Divide
(of CurrencyFrom)
CurrencyTo R AN 3 Use IATA Codes, Section C
(Currency).

R N9

Page 21 of 28 1 R AN 3 Use IATA Codes, Section C
(Currency).

Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

247 Attribute: Factor that CurrencyTo should be 1 R N9
FactorTo multiplied with.
248 8 R
249 7 (of CurrencyTo) Exchange rate value 1 O N 18,6
ExchangeRate 0-1 O AN 3 Refer to IATA code directory
UOM associated with pricing quantity O
LocalTaxPricingUOM and tax rate; R Section E (UOM)
R
250 7 LocalTaxPricingUOMFactor UOM factor used to convert for tax 0-1 O N 18,6
251 7 LocalTaxPricingRate calculation 0-1 R
252 7 LocalTaxPricingAmount 1 R N 18,6 Can be a flat fee.
253 7 LocalTaxTicketCurrencyCode Tax rate expressed in decimal format 1 O
used in pricing N 18,2
R
Tax represented for the pricing quantity AN 3 Refer to IATA code directory
and rate O Section C (Currency Code)
O
Currency (Standard ISO Code) for AN 3 Refer to IATA code directory
Invoice Tax Section E (UOM)

254 7 LocalTaxTicketUOM UOM associated with invoice quantity 0-1 N 18,6
and invoice tax rate;

255 7 LocalTaxTicketUnitRate Tax rate expressed in decimal format 1
used for the invoice

256 7 LocalTaxTicketAmount Tax represented for the invoice quantity 1 N 18,2
257 7 SubTax and rate
Node additiona1 tax on tax 0-
258 Attribute: unboun AN 3 Refer to IATA code directory
SubTaxType Type of Tax such as GST, VAT, Federal ded Section F (TaxType Code)
259 8 Excise, Custom, Petroleum, 1
260 8 (of SubTax) Environmental, Excise, tax exempt etc. AN 35
represented by the Invoice Lines 0-1
SubTaxDescription Description of tax
SubTaxCategoryCode
Specific Tax codes within a tax type 0-1 AN 3 Use list of codes: Required for VAT, excise tax;

• L=Lower Rate

• H=Higher rate

• S=Standard rate

• Z=Zero rated goods

Create additional code values if
necessary

261 8 SubTaxJurisdictionTaxBasis Tax basis for local tax jurisdiction 0-1 O AN 2 Use list of codes:
262 8 SubTaxJurisdictionCodeQualifier O
263 8 SubTaxJurisdictionCode O • GR=Gross

• NT=Net

Identifies source of the tax jurisdiction 0-1 AN 10 No List at this time i.e.: State, Federal, City
code 0-1
AN 10 No List at this time Code List to be developed
Tax jurisdiction code Code List to be developed

Page 22 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

264 8 SubTaxRateType Indicates how rate is determined 1 R AN 2 Use list of codes:
• P=Percent
265 8 SubTaxPricingCurrencyCode Currency (Standard ISO Code) 1 • FF = Flat Fee
266 8 SubTaxCurrencyConversion 0-1 • UR = Unit Rate
267 9 ConversionMechanism 1
R AN 3 Refer to IATA code directory
268 9 CurrencyFrom Factor that CurrencyFrom should be 1 Section C (Currency Code)
269 multiplied with. 1
Attribute: O Describes how an amount in CurrencyFrom
270 9 FactorFrom is converted into an amount in CurrencyTo.
271
(of CurrencyFrom) R AN 1 Valid values:
272 9 CurrencyTo • M = Multiply
273 8 • D = Divide
Attribute:
FactorTo R AN 3 Use IATA Codes, Section C
(Currency).
(of CurrencyTo)
ExchangeRate R N9
SubTaxPricingUOM
Factor that CurrencyTo should be 1 R AN 3 Use IATA Codes, Section C
multiplied with. (Currency).

1 R N9

Exchange rate value 1 R N 18,6
0-1 O AN 3 Refer to IATA code directory
UOM associated with pricing quantity
and tax rate; Section E (UOM)
O N 18,6
274 8 SubTaxPricingUOMFactor UOM factor used to convert for tax 0-1 Can be a flat fee.
275 8 SubTaxPricingAmount calculation 1 R N 18,2
276 8 SubTaxPricingRate 1 Incase of multiple inventory locations
277 8 SubTaxTicketCurrencyCode Tax represented for the pricing quantity 1 R N 18,6 ,guessing this speciofies the storage
and rate source.???
R AN 3 Refer to IATA code directory Optional, but highly recommended.
Tax rate expressed in decimal format Section C (Currency Code)
used in pricing
O AN 3 Refer to IATA code directory
Currency (Standard ISO Code) for Section E (UOM)
Invoice Tax
R N 18,6
278 8 SubTaxTicketUOM UOM associated with invoice quantity 0-1
and invoice tax rate; R N 18,2

279 8 SubTaxTicketUnitRate Tax rate expressed in decimal format 1 O AN 25
used for the invoice O AN 25

280 8 SubTaxTicketAmount Tax represented for the invoice quantity 1 O AN 15
and rate
281 5 Plant 0-1 Version 3.0.0
282 5 StorageLocation 0-1

283 5 StandNumber Stand/Gate/Bay at which the fuel was 0-1
delivered
Page 23 of 28

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

284 5 Equipment Parent Element 1- R
unbou
285 6 FuelingEquipmentID Used to identify the fueler or dispensing nded R AN 15 Name of code of the equipment used
286 6 FuelingType vehicle ID 1 R Only used if fuel type is hydrant
Transport Type AN 3 Use list of codes:
1 • HYD=Hydrant
• REF=Re-Fueler
287 6 PITNumber The hydrant pit number from which the 0-1 O
288 6 Operator fuel was delivered 1 R Add others as required
289 6 AverageFuelTemperature 1 R AN 15
Identification number, code or name of
person who has delivered the fuel AN 50 Name or code of the operator

290 Attribute: Unit of Measure used for Temperature 1 R AN 3 Use list of codes: Fahrenheit or Celsius temperature
291 6 TUOM 1-2 • C – Celsius measurement
• F - Fahrenheit
(of AverageFuelTemperature)
R
DensityInformation

292 Attribute: Type of Density 1 R AN 3 Use list of codes: Measured or Standard Density
293 7 DensityType Density of Fuel. 1
• MEA – Measured
(of DensityInformation)
• STD - Standard
Density
O N 18,4 Should be between 740 and 860 , 0.74 and

0.86 or 6.175 and 7.177 measured in KG/M3,

KG/LT, or LB/USG respectively.

Must have either density or specific gravity

required.

294 Attribute: Unit of Measure used for Density 1 R AN 3 Refer to IATA code directory
295 7 DensityUOM
Section E (UOM)
(of Density)
1 R N 4,1 Required if Net Quantity Delivered is entered.
Temperature Unit of Measure used for Temperature 1 Temperature should be between -47C and

50C or -53F and 122F.

296 Attribute: R AN 1 Use list of codes:
TUOM
297 6 • C = Celsius
298 (of Temperature)
• F = Fahrenheit
299 7 MeterReading
1-10 R
Attribute: 1
MeterID O AN 10

(of Meter Reading) Starting Meter reading 1 R N 18,6 Must be entered in meter reading ending is
MeterReadingStart Ending Meter reading 1 R N 18,6 entered

300 7 MeterReadingEnd Version 3.0.0 Must be entered in meter reading start is
entered

Page 24 of 28

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Row Level Structure/Element Description Element Attributes Value Source Notes
Repeat Req Type Size

301 7 MeterQuantityDelivered 1 R N 18,6 Check for difference between meter reading
1 start and meter reading end.

302 Attribute: UOM of Quantity Delivered R AN 3 Refer to IATA code directory ? correct dimension
MQDUOM Section E (UOM)
303 5
304 (of MeterQuantityDelivered) Sum of all meter quantity 1-3 R N 18.6 Once for gross or once for Net or both
TotalQuantity Identities gross or net quantity 1
305 R AN 2 Use list of codes
Attribute: Unit of Measure 1 • GR=Gross
306 5 TQDFlag • NT=Net
307 6
(of TotalQuantity) R AN 3 Refer to IATA code directory Make sure it covers weight
Section E (UOM)
Attribute:
TQDUOM 1 R
R DT
(of TotalQuantity) Date/Time started, must be less than 1
TransactionTime Date/Time finished 1
(YYYY-MM-DDThh:mm:ss) 0-1
LocalDateTimeStart 0-1
Date/Time started, must be greater than 1
308 6 LocalDateTimeFinished Date/Time started R DT “Ticket Date”
(YYYY-MM-DDThh:mm:ss)
309 6 GMTDateTimeStart O DT
Date/Time started, must be less than
310 6 GMTDateTimeFinished Date/Time finished O DT
(YYYY-MM-DDThh:mm:ss)

Date/Time started, must be greater than
Date/Time started
(YYYY-MM-DDThh:mm:ss)

311 3 Summary R

312 4 FuelTransactionLineCount Total Line counts for tickets 1 R N 18 Count of the FuelTransactionLine elements for
313 4 TotalFuelQuantity 1 R N 18,6 a FuelTransaction

314 1 FuelTransactionTransmissionSumma 1 R
315 2 ry 1 R N6
316 2 1 R N 18,6
FuelTransactionMessageCount Count of the number of Electronic Fuel MinValue=1 MaxValue=100,000. This is the
Transactions in the transmission count of the FuelTransaction Nodes.

FuelTransactionTotalFuelQuantity Sum of the fuel quantity of Electronic MinValue=1. this is the count of fuel quantity
Fuel Transactions in the transmission from all the Fuel Transaction nodes

Page 25 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Currency Conversion: Examples

Multi-currency support is one of the main innovations in version 3.0.0 of the Fuel Invoice
Standard. New optional currency conversion elements are provided at various levels:

 CurrencyConversion
 LocalTaxCurrencyConversion
 SubTaxCurrencyConversion

The structure of a CurrencyConversion element is always :
 ConversionMechanism (Multiply or Divide)
 CurrencyFrom with attribute FactorFrom
 CurrencyTo with attribute FactorTo
 ExchangeRate

ConversionMechanism

The most common case is where the ConversionMechanish is Multiply – meaning that the
amount in CurrencyFrom needs to be multiplied by the ExchangeRate to calculate the amount in
CurrencyTo.

Example:

Conversion from EUR to GBP where 1 EUR : 1 GBP = 0.677799
would be modeled as follows:

<CurrencyConversion>
<ConversionMechanism>M</ConversionMechanism>
<CurrencyFrom FactorFrom=”1”>EUR</CurrencyFrom>
<CurrencyTo FactorTo=”1”>GBP</CurrencyTo>
<ExchangeRate>0.677799</ExchangeRate>

</CurrencyConversion>

An ExchangeRate may be used inversely by setting the ConversionMechanism to Divide. In this
case the amount in CurrencyFrom needs to be divided by the ExchangeRate to calculate the
amount in CurrencyTo.

Example:

Conversion from EUR to GBP where 1 GBP : 1 EUR = 1.47536
would be modeled as follows:

<CurrencyConversion>
<ConversionMechanism>D</ConversionMechanism>
<CurrencyFrom FactorFrom=”1”>EUR</CurrencyFrom>
<CurrencyTo FactorTo=”1”>GBP</CurrencyTo>
<ExchangeRate>1.47536</ExchangeRate>

</CurrencyConversion>

Page 26 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

FactorTo and FactorFrom

In some cases, where the value of one currency is very low compared to the other currency, a
multiplication factor may be added.

Example:

Conversion from CLP to USD where 100 CLP : 1 USD = 0.190585
would be modeled as follows:

<CurrencyConversion>
<ConversionMechanism>M</ConversionMechanism>
<CurrencyFrom FactorFrom=”100”>CLP</CurrencyFrom>
<CurrencyTo FactorTo=”1”>USD</CurrencyTo>
<ExchangeRate>0.190585</ExchangeRate>

</CurrencyConversion>

Although less common, a multiplication factor other than 1 could also be provided for the
CurrencyTo.

Example:

Conversion from USD to CLP where 1 USD : 100 CLP = 5.24700
would be modeled as follows:

<CurrencyConversion>
<ConversionMechanism>M</ConversionMechanism>
<CurrencyFrom FactorFrom=”1”>USD</CurrencyFrom>
<CurrencyTo FactorTo=”100”>CLP</CurrencyTo>
<ExchangeRate>5.24700</ExchangeRate>

</CurrencyConversion>

Currency Conversion formulas

To convert an amount in CurrencyFrom to an amount in CurrencyTo, the following rules apply:

If the ConversionMechanism is multiply then use the following formula:

amount in CurrencyTo = (amount in CurrencyFrom / FactorFrom) x (ExchangeRate x FactorTo)

(2) If the ConversionMechanism is divide then use the following formula:

amount in CurrencyTo = (amount in CurrencyFrom / FactorFrom) / (ExchangeRate / FactorTo)

Page 27 of 28 Version 3.0.0

Aviation Fuel Data Standards Group
XML Standard for Electronic Fuel Transactions

Examples of how to use the currency conversion formulas:

Assume that 1 CLP : 1 USD = 0.00190585 and consequently 1 USD : 1 CLP = 524.70

Conversion from CLP to USD where 100 CLP : 1 USD = 0.190585
could be modeled using the Multiply conversion mechanism as follows:

<CurrencyConversion>
<ConversionMechanism>M</ConversionMechanism>
<CurrencyFrom FactorFrom=”100”>CLP</CurrencyFrom>
<CurrencyTo FactorTo=”1”>USD</CurrencyTo>
<ExchangeRate>0.190585</ExchangeRate>

</CurrencyConversion>

To convert 500 CLP to USD:

(500 CLP / 100) x (0.190585 x 1) = 0.95 USD

Conversion from CLP to USD where 1 USD : 100 CLP = 5.24700
could be modeled using the Divide conversion mechanism as follows:

<CurrencyConversion>
<ConversionMechanism>D</ConversionMechanism>
<CurrencyFrom FactorFrom=”100”>CLP</CurrencyFrom>
<CurrencyTo FactorTo=”1”>USD</CurrencyTo>
<ExchangeRate>5,24700</ExchangeRate>

</CurrencyConversion>

To convert 500 CLP to USD:

(500 CLP / 100) / (5.24700 / 1) = 0.95 USD

Page 28 of 28 Version 3.0.0