Electronic Invoice in EDIFACT format

Transcription

1 Electronic Invoice in EDIFACT format Version 3.6 Status: September 1, 2005 EDIFACT Messages Subset AirPlus International Technical Hotline Phone: +49 (0) Fax: +49 (0) JXIL-PDePT-EDI / Status Page 1/46 Manual V 3.6

2 1 Content 1 CONTENT VERSION CONTROL EDIFACT INFORMATION INTRODUCTION IMPORTANCE OF EDIFACT TRANSMISSION PROCEDURE LEGAL ASPECTS SOFTWARE MESSAGES SUBSET OF THE AIRPLUS INTERNATIONAL AIRPLUS SUBSET DEFINITION CONTENT OF THE DATA ELEMENTS SERVICE TYPES STRUCTURE OF THE SUBSET ADDITIONAL DATA MESSAGE CONSTRUCTION CHART OF THE SUBSET (HEADER, LEVEL 1 AND TRAILER) MESSAGE CONSTRUCTION CHART OF THE SUBSET (LEVEL 2) DESCRIPTION OF THE AIRPLUS SUBSETS HEADER SECTION UNA UNB UNH BGM DTM PAI RFF NAD CUX DETAIL SECTION LIN PIA IMD QTY DTM GIN FTX MOA CUX PRI RFF DTM LOC QTY DTM TAX MOA NAD LOC RFF DTM DOC CTA...35 JXIL-PDePT-EDI / Status Page 2/46 Manual V 3.6

3 5.3 TRAILER SECTION UNS CNT MOA RFF TAX MOA UNT UNZ SUBSET SEGMENTS WITH QUALIFYING DATA ELEMENTS MESSAGE HEADER AND TRAILER MESSAGE BODY EXAMPLES HEADER SECTION SERVICE TYPE FLIGHT (FL) SERVICE TYPE RAIL (DB) SERVICE TYPE BAHNONLINE (DO) SERVICE TYPE START-CC (CC) SERVICE TYPE HOTEL (HT) TRAILER SECTION...46 JXIL-PDePT-EDI / Status Page 3/46 Manual V 3.6

4 2 Version control Version 3.6 Complete Overwork of this documentation. Removal of all contents concerning ICP. Version 3.5 Jointment of the documentation for the subsets GSE and BTM. Additions: S. 19 SG 25, PIA Extension for additional data S. 38 SG 50, MOA VAT informations Introduction of new service type Hotel HT (LARS: 540), as well as Transaction Fee TF and Commission Passback CP. Changes: P. 15 SG 0, DTM Due date. P. 16 SG 25, NAD Invoice recipient s address details. P. 18 SG 25, LIN New service type 540 hotel HT in field 1131 on the second LIN level for hotel transactions. P. 19 SG 25, PIA New service type HAT for hotel transactions TF for transaction fee, CP for. In field 7140 (1 st level), domestic identifier for purely domestic transactions in field 1131, CC service code in 7140_02 with qualifier VX in field7143_02. P. 20 SG 25, IMD Hotel reservation number for hotel transactions in field 7008_01, as well as transaction type in field 7008_02 (G V) 2nd level. P. 21 SG 25, QTY Hotel transactions: days invoiced in field 6060 with qualifier DAY in field 6411 and 108 in field 6063, number of participants invoiced with IE in field 6411 and 108 in field 6063 (2nd level) respectively. P. 22 SG 25, DTM Hotel transactions: arrival date with qualifier 178 in field 2005 and departure date with qualifier 189. P. 27 SG 29, RFF Hotel receipt number ACD, CRS reservation number. P. 28 SG 32, LOC hotel service description details (92) in field 3325 and extensive service description details in field 3224 (2nd level). P. 37 SG 48, MOA PLEASE NOTE: Qualifier 125 of MOA segment redefined (net grand total). Version 3.4 Introduction of new service type Bahn-Online (LARS: 511), as well as 0-Invoice Number as a service providers reference for the transaction and a Cutomer Reference Number (LARS: ). Changes: P. 19 SG 25, PIA Service types ET (Executive TeleCard) and TK (Telekom-Chip) are not supported any more. Additionally, Bahn-Online services are indicated with DO. P. 20 SG 25, IMD The service type is now to be found within field 1131 instead of Regarding Bahn-Online transactions, there is information about the booked class in field 7008_02 and a service description in an additional IMD-segment. P. 28 SG 32, LOC Point of departure and destination with Bahn-Online services. P. 29 SG 32, QTY Number of persons travelling (adults and children) with Bahn-Online services. P. 46 SG 34, SG 35 The second SG 34 is coming with two SG 35 in order to submit the 0- Invoice Number and the Customer Reference Number. P. 30 SG 33, TAX Tax rates now in percent (16, 7, 0). JXIL-PDePT-EDI / Status Page 4/46 Manual V 3.6

5 3 EDIFACT information 3.1 Introduction The importance of data exchange on basis of structured data formats has considerably has world-widely increased in the last years. To build modern business relationships and to reduce costs within the organisation data and information flows are required which can be processed electronically. The internationally valid and world-widely consistent standard EDIFACT was developed to meet the requirements for an inter-organisational data exchange. It shows all common kinds of business processes. With this EDI manual we at Lufthansa AirPlus Servicekarten GmbH like to present our EDI offer. Our subset is based on the EDIFACT INVOIC, Version 96.A. This way the use of our documented subsets significantly facilitates the implementation. 3.2 Importance of EDIFACT In the past, several branches have developed industry specific EDI formats. However, they were always just used within one branch of the industry (e. g. VDA - automotive industry). These branch specific EDI applications were advantageous for those being directly involved, but from an economically point of view quite disadvantageous. The result were incompatibilities and doubled efforts. In our times the organisation is seen as a whole. It is not the single working place that is to be improved but much more an entire process to be designed. Saving of time through networking of organisations and the requirement of optimised processes will also have an effect on the handling of customer payments. The requirements for business processes always become more extensive; this means a constraint to make use of all opportunities to rationalise and implement important optimisations within the business field.. For payments this means that invoices and credit notes have to quickly and correctly processed further within the own accounting department without requiring any manual manipulations. These data shall control processes within the organisation and effect on other processes beyond the organisation. 3.3 Transmission procedure An essential condition for the EDIFACT application is the communication carrier. There still are few users who exchange data on tapes or disks but increasingly telecommunication techniques are used. Therefore are several options to build such communication Mailbox and value added services (e. g. IBM IE) These mean advantages by providing different communication protocols, a permanent reception and sending availability, and the opportunity of a better message distribution and collection. AirPlus International provides you with a variety of alternative connection types. This way you may individually choose the preferred transmission type and further use your already existing infrastructure. We exclusively transmit data exchange in the EDIFACT format online. Doing so, the following transmission ways are available: JXIL-PDePT-EDI / Status Page 5/46 Manual V 3.6

6 1) Mailbox / value added services: Data exchange via the X.400 service by the Telekom (You have an MTA), Data exchange via Telebox/400 (You are a UA), Using the IBM Information Exchange (IBM IE), using the General Electric Information Service (GEIS). 2) RVS Host-to-Host transfer 3.4 Legal aspects Signatures within the electronic data exchange with AirPlus are not necessary, for the contractual responsibilities are defined and agreed in separate contracts, the EDI contract and the general agreement. (only in the banking sector an additional electronic authencity mark for the client is required.) The rights and responsibilities between the data exchange partners (receiver/sender) are defined in an EDI contract. In this EDI contract the following issues are determined: Obligations of the electronic invoice Transmission times Conditions for implementing hardware/software modifications Provisions on security and storage Maintenance of confidential and proprietary information Procedure in case of errors Costs of the procedure and the transmission Term of the agreement. A respective EDI general agreement will be provided by the responsible standard institutions. In Germany the development was made by the AWV (Arbeitsgemeinschaft für wirtschaftliche Verwaltung e. V.). AirPlus International uses this general agreement. Business terms and conditions that are normally used should be defined in a separate agreement (general agreement). This way only terms and conditions differing from this need to be transferred. 'Small print' in EDI applications will not be changed. The general agreement between customer and supplier should contain the interface, basics on application and partner in a separate EDI passage. With regard to a data transmission with the AirPlus International this means that general business terms and conditions which have signed on the request for the service card become the basis for the applicable business terms and conditions. Also the tax law needs to be considered: the 14 of the Umsatzsteuergesetz. This means that next to the electronic transmission of the invoice a paper sheet with the VAT contained in the invoice RDT is generated and send to the invoice receiver. The 14 UStG requires a document to accept the VAT. AirPlus International currently provides the VAT protocol parallel to the respective transmissions. Prior to starting the electronic data exchange the customer needs to be informed about the responsible tax office of the supplier, i. e. AirPlus International. 3.5 Software EDI software or an EDI system respectively is necessary for transformation (conversion) of data from in-house systems into the message and syntax structures and again back into the existing in-house system. EDI software packages and EDI systems can be obtained from a variety of companies. Most systems are independent of messages (e. g. invoices, orders, dispatch notes), JXIL-PDePT-EDI / Status Page 6/46 Manual V 3.6

7 independent of format (e. g. EDIFACT, ODETTE, SEDAS, VDA), and version capable, i. e. controlled with tables or a standard database. This means that in case of changes of messages, subsets or versions only the respective assignments (source/target file) need to be adjusted. To avoid the need to change the used applications the format transformation should take place outside of the application. It makes much sense to use a communications computer here. The application makes the message contents available to the EDI system and vice versa. The AirPlus International made the decision to use a communication server. The implemented EDI software meets the above requirements. It works absolutely automatically and partner focused. This way a high quality for transmission can be ensured. JXIL-PDePT-EDI / Status Page 7/46 Manual V 3.6

8 4 Messages subset of the AirPlus International 4.1 AirPlus subset definition The AirPlus subset is an EDIFACT message subset INVOIC, Version 96.A which is based on the AirPlus invoice set (LARS) by AirPlus International. This subset is provided alternatively to the current data media exchange procedure. This subset is used to exchange invoice data between AirPlus and the customer. 4.2 Content of the data elements Basically, the content of the EDIFACT data elements corresponds to the content of the respective LARS fields. However, the quality of the data which are provided is very much characterised by the quality of the data which AirPlus receives from different sources. For the processing of EDIFACT messages normally achieves a significantly higher degree of automation, it is important to take care of specialities of the input data. To meet the EU directives we need to refer all exchange rates to the EURO. With this conversion the exchange rate of the EURO to the sales price will always be shown for each transaction. To facilitate checking the invoice we transmit the fixed notation of the EURO to the selected billing currency in the header of the invoice. Since 1993 we also provide billing data for train transactions which however means some limitation of the data quality. Partial services which belong to a traveller so far have been transmitted as individual transaction (e. g. ticket and reservation). Any reference between the separately quoted transaction cannot be construed in such case. With the introduction of the EURO on the data records of our partner have changed. Therefore we transmit related train services as one single transaction and show the relating partial services (analogue to START CC transactions). Since 2003 train services, which have been booked via internet processed within a separate service type. Beginning with 2004, there will also hotel transactions been processed. 4.3 Service types There are several service types that can be booked via AirPlus International. The content of the data is accordingly manifold. With regard to services which are purchased with the personal AirPlus cards (EuroCard, VISA Card) an automatic service identification is reasonably only possible for flight services. The quality is different when the AirPlus Company Card is used. Here we distinguish four service provider: Flight services Train services Train services online booking START-CC services Car rental Hotels Other services (e. g. card fee) You can identify the specific service type by the code in the PIA/C212_7140. Please note that during the collection information such as e. g. passenger name (NAD/C058_3124), Routing (LOC/C517_3225), ticket number (IMD/C273_7008) or airline (RFF/C506_1154) are required fields only in the area of flight services. There will be empty data elements transmitted, if the input data are not made available by the reservation systems. JXIL-PDePT-EDI / Status Page 8/46 Manual V 3.6

9 4.4 Structure of the subset The AirPlus subset is defined in a three-level hierarchy. The used levels have the following meaning: 1 : 2 : Positions of the invoice. This contains information on the service receiver and details on sales amounts. Description of the performed partial service (e. g. flight service). The structure then looks as follows: Header LIN 1: Positions of the invoice PIA (Fields from the LARS sets 300 & 400) DTM i i i LIN 2:Description of partial service PIA (Fields from the LARS sets 5x0) IMD i i i Trailer By making use of sub-positions it will become necessary to number the occurring LIN segments twice. Therefore the 1082 and C829_1082 counter are run in the data elements. In the data element 1222 the respective level is delivered in a coded manner. The meaning is as follow: In the data element 1082 the counter of the respective 1 st level is carried along. This data element is numbered continually. In the data element C829_1082 is continually numbered within the 2 nd sub-level. This provides the possibility to number the LIN segments as follows (example): LIN 1.0 Pos.1 Flight 1 LIN 2.0 Pos.2 Flight 2 LIN :PO:300+0:0+0' LIN+1++::500+1:0+1' LIN :PO:300+0:0+0' LIN+2++::500+1:0+1' LIN 3.0 Pos.3 CC service 1 LIN+3++S :PO:300+0:0+0' LIN 3.1 Part A LIN+3++::520+1:0+1' LIN 3.2 Part B LIN+3++::520+1:1+1' JXIL-PDePT-EDI / Status Page 9/46 Manual V 3.6

10 4.5 Additional data The AirPlus International has provided the option to allow data being recorded already in the booking system for each booking with an AirPlus card. These data can positively specify your booking within your company. These are data such as personnel number, cost accounting or internal account. Unfortunately, not all services are performed in fully automated systems. That is why it may happen that bookings are input that have no additional data. For these bookings the respective data element is set on the default value '0'. Date fields are set on For we always transmit all additional data fields, we also use this default setting for fields that you do not have used. JXIL-PDePT-EDI / Status Page 10/46 Manual V 3.6

11 4.6 Message construction chart of the subset (header, level 1 and trailer) 0 M 1 UNH 1 0 M 1 BGM 1 0 M 35 DTM 1 0 C 1 PAI 1 1 C 99 RFF 1 2 C 99 NAD 2 7 C 5 CUX 1 25 M 1 LIN C 25 PIA C 35 DTM M 1 MOA C 1 CUX C 10 RFF C 5 DTM M 1 TAX C 1 MOA M 1 NAD C 5 LOC M 1 RFF K 5 DTM M 1 DOC 1 1 UNS M M 1 CTA 2 1 C 10 CNT 2 48 M 1 MOA 4 49 C 1 RFF M 1 50 C 2 TAX 1 MOA 1 M 1 UNT 1 JXIL-PDePT-EDI / Status Page 11/46 Manual V 3.6

12 4.7 Message construction chart of the subset (level 2) 1 25 M 1 LIN C 25 PIA C 10 IMD C 5 MEA C 5 QTY C 25 DTM C 5 GIN C 5 FTX M 1 MOA C 25 PRI C 10 RFF C 5 DTM M 1 LOC C 5 QTY C 5 2 DTM M 1 TAX C 1 MOA M 1 NAD C 5 RFF JXIL-PDePT-EDI / Status Page 12/46 Manual V 3.6

13 5 Description of the AirPlus subsets The description of the AirPlus subsets is shown on the following pages. It was supplemented by the description to the segments UNA, UNB and UNZ. 5.1 Header section UNA UNA Separate default M1 Definition of the separators being used Element Name Status Format UN Format AP Description Values UNA1 Component data element separator M an1 an1 : Colon UNA2 Data element separator M an1 an1 + Plus-sign UNA3 Decimal notation M an1 an1. Decimal Point UNA4 Release character M an1 an1? Question Mark UNA5 Reserved for future use M an1 an1 Space Character UNA6 Segment terminator M an1 an1 Apostrophy The above mentioned separators are conforming to the standard default according to ISO 9735, EN , and DIN Note: The transmission of the UNA segment may be omitted when these standard defaults are used within the transmission file. In case other separators are used the UNA segment has to be transmitted as first segment in the transmission file. UNA:+.? ' UNB UNB Reference data head segment M1 Is used to open, identify and describe a transmission file Element Name Status Format UN Format AP Description Values S001 SYNTAX IDENTIFIER M 0001 Syntax identifier M a4 a4 UNOD 0002 Syntax version number M n1 n1 4 S002 INTERCHANGE SENDER M 0004 Sender identification M an..35 an..35 mutually agreed 0007 Partner identification code qualifier C an..4 an2 ZZ 0008 Address for reverse routing C an..14 S003 INTERCHANGE RECIPIENT M 0010 Recipient identification M an..35 an..35 mutually agreed 0007 Partner identification code qualifier C an..4 an2 ZZ 0014 Routing address C an..14 S004 DATE/TIME OF PREPARATION M 0017 Date M n6 n8 Date at the time of creation 0019 Time M n4 n4 Time at the time of creation 0020 Interchange control reference M an..14 an..14 At the time of creation S005 RECIPIENT'S REFERENCE PASSWORD M 0022 Recipient's reference/password M an Recipient's reference/password qualifier C n Application reference C an..14 an10 LASGINVOIC 0029 Processing priority code C a Acknowledgement request C n Communications agreement identification C an35 an Test indicator C n1 n1 1 = Test UNB+UNOD:4+Sender:ZZ+Receiver:ZZ : LASGINVOIC++++1' Test-Message UNB+UNOD:4+Sender:ZZ+Receiver:ZZ : LASGINVOIC' Live-Message JXIL-PDePT-EDI / Status Page 13/46 Manual V 3.6

14 5.1.3 UNH Segmentgroup 0 UNH Messages head segment M1 Is used to open, identify and describe a transmission file Element Name Status Format UN Format AP Description Values 0062 MESSAGE REFERENCE NUMBER M an1..14 an14 Referenznummer serial S009 MESSAGE IDENTIFIER M 0065 Message type M an1..6 an6 Nachrichtentyp INVOIC 0052 Message version number M an1..3 an14 Versionsnummer D 0054 Message release number M an1..3 an3 Freigabenummer 96A 0051 Controlling agency, coded M an1..3 an2 Verwaltende Organisation UN 0057 Association assigned code C an Code list directory version number C an Message type sub-function identification C an COMMON ACCESS REFERENCE C an1..35 S010 STATUS OF THE TRANSFER C 0070 Sequence of transfers M n First and last transfer C a1..1 S016 MESSAGE SUBSET IDENTIFICATION C 0115 Message subset identification M an Message subset version number C an Message subset release number C an Controlling agency, coded C an1..3 S017 MESSAGE IMPLEMENTATION GUIDELINE C 0121 Message implementation guideline identification M an Message implementation guideline version C an Message implementation guideline release C an Controlling agency, coded C an1..3 S018 SCENARIO IDENTIFICATION C 0127 Scenario identification M an Scenario version number C an Scenario release number C an Controlling agency, coded C an1..3 UNH+213+INVOIC:D:96A:UN' BGM Segmentgroup 0 BGM Beginning of the message M1 Display of the message beginning Element Name Status Format UN Format AP Description Values C002 DOCUMENT/MESSAGE NAME C 1001 Document/message name, coded C an1..3 n3 Invoice type 380 = Invoice (Rechnung) 381 = Credit note (Gutschrift) 1000 Document/message name C an DOCUMENT/MESSAGE NUMBER C an1..35 an..19 Invoice level, Contract number mutually agreed 1225 MESSAGE FUNCTION, CODED C an RESPONSE TYPE, CODED C an1..3 It is mentioned in the data element C002_1001 whether this message is used as an invoice or as a credit note. BGM ' JXIL-PDePT-EDI / Status Page 14/46 Manual V 3.6

15 5.1.5 DTM Segmentgroup 0 DTM Date / Time details M35 Details to way of payment Element Name Status Format UN Format AP Values C507 DATE/TIME/PERIOD M 2005 Date/time/period qualifier M an1..3 n1 "3" = Invoice date "170" = Due date 2380 Date/time/period C an1..35 n Date/time/period format qualifier C an1..3 n3 "102" = YYYYMMDD "203" = YYYYMMDDHHMM Invoice date and due date as shown on invoice. DTM+3: :102' DTM+170: :102' PAI Segmentgroup 0 PAI Payment agreement C1 Details on way of payment Element Name Status Format UN Format AP Values C534 PAYMENT INSTRUCTION DETAILS M 4439 Payment conditions, coded C an Payment guarantee, coded C an Payment means, coded C an1..3 n2 30 = Bank collection 31 = Money tranfer 4435 Payment channel, coded C an1..3 This segment indicates whether the amount is collected by bank collection or whether the customer uses money transfer. PAI+::30' RFF Segmentgroup 1 C99 RFF Reference details M1 Identifying details related to the partner or the business transaction Element Name Status Format UN Format AP Values C506 REFERENCE M 1153 Reference qualifier M an1..3 an2 "IV" = Invoice number 1154 Reference number C an1..35 an..10 Invoice number 1156 Line number C an1..6 an..2 Payment serial number 4000 Reference version number C an1..35 n..3 Invoice repetition number The invoice number together with the billing data are unique. The invoice repetition number supplements the payment/credit note number (0 for the first invoice to a payment/credit note number). For each correction of an JXIL-PDePT-EDI / Status Page 15/46 Manual V 3.6

16 invoice (e. g. new or changed additional data) of an previously created invoice the invoice repetition number is increased by +1. The new invoice automatically replaces all previous ones. The serial number is given when the invoice must have only one value each of a characteristic (BGM\C002_1001) but on one day bookings with different values in this characteristic are invoice. Then the 10 digit payment/credit note number does not change, however this serial number will be placed and increased. RFF+IV: :01:0' NAD Segmentgroup 2 C99 NAD Name and address M1 Details of name, address and function of a partner Element Name Status Format UN Format AP Values 3035 PARTY QUALIFIER M an1..3 an2 "II" = Receipient of the bill "IV" = Sender of the bill C082 PARTY IDENTIFICATION DETAILS C 3039 Party id. identification M an1..35 an..17 EDI partner number Supplier partner number C058 NAME AND ADDRESS C 3124 Name and address line M an Name and address line C an Name and address line C an Name and address line C an Name and address line C an1..35 C080 PARTY NAME C 3036 Party name M an1..35 an..30 Address-Information 1 of the receipient 3036 Party name C an1..35 an..30 Address-Information 2 of the receipient 3036 Party name C an1..35 an..30 Address-Information 3 of the receipient 3036 Party name C an1..35 an..30 Address-Information 4 of the receipient 3036 Party name C an Party name format, coded C an1..3 C059 STREET C 3042 Street and number/p.o. box M an Street and number/p.o. box C an Street and number/p.o. box C an Street and number/p.o. box C an CITY NAME C an1..35 an..30 city of the receipient 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an POSTCODE IDENTIFICATION C an1..9 an..9 post code of the receipient 3207 COUNTRY, CODED C an1..3 This segment group occurs in two different specifications, one comprises the EDI partner number as well as the address of the invoice recipient, the other one is defined as a reference intended for the invoice issuer. NAD+IV:EDI-PARTNER' NAD+II:BILLING-SENDER' JXIL-PDePT-EDI / Status Page 16/46 Manual V 3.6

17 5.1.9 CUX Segment group 7 C5 CUX Currency details M1 Details on the currency used for the business transaction Element Name Status Format UN Format AP Values C504 CURRENCY DETAILS C 6347 Currency details qualifier M an1..3 n1 "1" = Billing currency 6345 Currency, coded C an1..3 n3 Billing Currency 6343 Currency qualifier C an Currency rate base C n1..4 C504 CURRENCY DETAILS C 6347 Currency details qualifier M an1..3 n1 "5" = Base currency 6345 Currency, coded C an1..3 n3 Base currency 6343 Currency qualifier C an Currency rate base C n RATE OF EXCHANGE C n1..12 n..12 Exchange rate 6341 CURRENCY MARKET EXCHANGE, CODED C an1..3 The display of the currencies is numerical and conforms to the currency code ISO Possible values are e. g.: '978' EURO (EUR) 840 US Dollar (USD) To meet the EU directives all exchange rates need to refer to the EURO. Therefore the exchange rate of the EURO against the selected billing currency is given in the data element CUX/5402. CUX+1:840+5: ' JXIL-PDePT-EDI / Status Page 17/46 Manual V 3.6

18 5.2 Detail Section New levels are introduced In the Detail Section. A main level (level 1) and one sub-levels. 1 provides details of the positions as well as the respective amounts. The differentiation is done in the LIN segment by the data element The main level is numbered in the data element is again numbered within the 1 st level with serial numbers in the data element C829_1082. Additionally to the hierarchy levels the data set type of the LARS by which this LIN segment was generated is given in the data element C212_1131. In the following the Detail-Section of the AirPlus Subsets are described by providing the used segments and the used levels LIN Segment group 25 C LIN Position data M1 Details of the basic position data Element Name Status Format UN Format AP LINE ITEM NUMBER C n1..6 n..6 seq. position number seq. position number 1229 ACTION REQUEST/NOTIFICATION, CODED C an1..3 C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an1..35 an..13 Reference number 7143 Item number type, coded C an1..3 an2 "PO" = Order number n3 "300" "5xx" C829 SUB-LINE INFORMATION C 5495 Sub-line indicator, coded C an1..3 n Line item number C n1..6 n..6 0 seq. number 1222 CONFIGURATION LEVEL C n1..2 n CONFIGURATION, CODED C an1..3 Using this segments: 1. : Serial numbering of the positions in the data element In the data element 7140 a AirPlus internal reference number to this transaction is given (Please quote on any requests). Details on the LARS set type from which this segment was generated, can be found in the data element C212_1131. Possible values for this are currently: 300 Position set 2. : Serial numbering of the sub-positions in the data element C829_1082. ). Details on the LARS set type from which this segment was generated, can be found in the data element C212_1131. Possible values for this are currently: 500 Flight set 510 Train set 511 Bahn-Online set 520 START-CC set 530 Car rental set 540 Hotel set 590 "Other sales" set LIN+1++S :PO:300+0:1++0' LIN+1++::500+1:0+1' ( Flight set) JXIL-PDePT-EDI / Status Page 18/46 Manual V 3.6

19 5.2.2 PIA Segment group 25 C PIA Additional product information C25 Details on the commodity code Element Name Status Format UN Format AP PRODUCT ID. FUNCTION QUALIFIER M an1..3 n1 "1"= additional data "1"= additional data C212 ITEM NUMBER IDENTIFICATION M 7140 Item number C an1..35 an..15 Type of sales "ETX" 7143 Item number type, coded C an1..3 an2 "MP" = Identifikation "PD"= Description "190" = Domestic C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an1..35 an..20 Service code of CC 7143 Item number type, coded C an1..3 an2 "VX" = service code C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an1..35 an Item number type, coded C an1..3 an2 C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an1..35 an Item number type, coded C an1..3 an2 C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an1..35 n Item number type, coded C an1..3 an2 Use of this segment: 1. : Detail on type or source of sales. Possible values are: AP AirPlus generated service (e. g. card fees, lounges) AV Car rental CC START-CC CP Commission Passback DB Deutsche Bahn AG DO Bahn-Online FL Flight HT Hotel SO Other sales The source of TF and CP is obvious in field 1131 of the segment LIN and in field 7009 of the segment IMD in level 2. The domestic tag indicates the origin of a service; it can be either exclusively domestic, crossborder or international. A D shall solely represent services originating in the country of the recipient (of these services). In all other cases, this tag is not applicable. 1. example: service type Flight : a flight from FRA to HAJ would be identified by a D, the flight FRA FIU would not be identified at all, therefore the field will be filled with a blank space. 2. example: service type rail : a rail ticket for the route Mainz Cologne would be identified by a D, a rail ticket for the leg Cologne Brussels would again cause the field to be filled up with a blank space. JXIL-PDePT-EDI / Status Page 19/46 Manual V 3.6

20 3. example: travel agency: a flight from FRA to HAJ + TAF would be identified by a D, a flight from Frankfurt to New York + TAF would not be identified at all, therefore the field would be filled with a blank space. 2. : Detail on type of ticket. To identify electronic tickets (ETIX) data element C212_7140 shall be filled with ETX; qualifier PD shall be present in data element C212_7143. For START CC transactions a CC service code will be moved to field C212_7140 and will be qualified by VX in field C212_7143. PIA+1+ETX:PD' 2. level (ETIX ticket) IMD Segment group 25 C IMD Description of the position C10 Supplementary details on the position data Element Name Status Format UN Format AP ITEM DESCRIPTION TYPE, CODED C an1..3 "E" = Description 7081 ITEM CHARACTERISTIC, CODED C an1..3 C273 ITEM DESCRIPTION C 7009 Item description identification C an1..17 Type of sales 7008 Item description C an1..35 Ticketnumber Online order system number Description StartCC document number Rental contract number Hotel reservation number 7008 Item description C an1..35 Booking Class DB-Class 3453 Language, coded C an SURFACE/LAYER INDICATOR, CODED C an1..3 Use of this segment: 1. : Is not used. 2. : Document number The number of the ticket or in case of car rentals the rental contract number are entered into the data element C273_7008[1]. In case of hotel transactions there will be the reservations number of the respective hotel. The type of sales is once more repeated in the data element C273_7009 (cf. PIA segment level 1). If available, the travel class is entered into data element C273_7008[2] or the delivery note number of the service provider is entered into the data element C273_7009. For hotel transactions, the sort of transaction (concerning occasions or guests) will be given. With Bahn-Online services, there is a description in field 7008[1], qualified with E in field 7077 and DO in field Transaction Fees and Commission Passbacks are identified as a service type within C273_7009. The segment can occur up to three times. IMD+++FL::: :C' 2. IMD+++TF::: :C' 2. IMD+++DB:::DB ' 2. (Flight service) (Transaction Fee from flight) (Train ticket) JXIL-PDePT-EDI / Status Page 20/46 Manual V 3.6

21 5.2.4 QTY Segment group 25 C QTY Indication of quantity C5 Details on quantities contained on the positions Element Name Status Format UN Format AP 1 2 C186 QUANTITY DETAILS M 6063 Quantity qualifier M an1..3 n..3 "108" = Invoiced days "49" = Invoiced km "128" = No. of participants "2" = No. of attendands 6060 Quantity M n1..15 n..15 Invoiced days Invoiced km Number of participants 6411 Measure unit qualifier C an1..3 an..3 "DAY" "KTM" "IE" Use of this segment: 1. : Is not used. 2. : Quantity details. This segment occurs up to three times. The occurrence as well as the number depend on the type of sales: Sales types C186_6060 C186_6411 Car rental (AV) 108 = invoiced days 49 = invoiced kilometre DAY KTM Hotel (HT) 108 = invoiced days 2 = attendants DAY IE QTY+108:10:DAY' 2. (invoiced days - AV) JXIL-PDePT-EDI / Status Page 21/46 Manual V 3.6

22 5.2.5 DTM Segment group 25 C DTM Date / Time details C35 Details on customer specific date details and delivery dates Element Name Status Format UN Format AP 1 2 C507 DATE/TIME/PERIOD M 2005 Date/time/period qualifier M an1..3 n..3 "9" = Processing date "136" = Departure date "178" = Arrival date (real) "189" = Departure date (real) 2380 Date/time/period C an1..35 n8 Processing date Departure date Departure date (real) Departure date (real) 2379 Date/time/period format qualifier C an1..3 n3 "102" = YYYYMMDD "102" = YYYYMMDD Use of this segment: 1. : Processing date 2. : Arrival date, departure date or delivery date. This segment occurs up to two times. The differentiation is made by the data element C507_2005. The occurrence depends on the type of sales: Sales type C507_2380 C507_2379 Flight (FL) 136 = Departure date 102 = YYYYMMDD Train (DB) 136 = Departure date 102 = YYYYMMDD Bahn-Online (DO) 136 = Departure date 102 = YYYYMMDD START-CC (CC) 136 = Departure date 102 = YYYYMMDD Hotel (HT) 178 = Arrival date (real) 189 = Departure date (real) 136 = Booking date 102 = YYYYMMDD DTM+9: :102' DTM+136: :102' GIN Segment group 25 C GIN Goods - identification C1000 Details on specific identifaction number Element Name Status Format UN Format AP IDENTITY NUMBER QUALIFIER M an1..3 "BL" = vehicle registration C208 IDENTITY NUMBER RANGE M 7402 Identity number M an1..35 an1 Cartype 7402 Identity number C an1..35 an..30 Brand of car / type C208 IDENTITY NUMBER RANGE C 7402 Identity number M an1..35 an..15 Number plate 7402 Identity number C an1..35 C208 IDENTITY NUMBER RANGE C 7402 Identity number M an Identity number C an1..35 C208 IDENTITY NUMBER RANGE C 7402 Identity number M an Identity number C an1..35 C208 IDENTITY NUMBER RANGE C 7402 Identity number M an Identity number C an1..35 Use of this segment: JXIL-PDePT-EDI / Status Page 22/46 Manual V 3.6

23 1. : Is not used. 2. : Details on the car rented. This segment is only generated for the service type car rental (AV). GIN+BL+C:Compact+M - AB 88' FTX Segment group 25 C FTX Free text C1000 Details on position data that cannot be assigned to any other set Element Name Status Format UN Format AP TEXT SUBJECT QUALIFIER M an1..3 an3 "OSI" = Other information "AAJ" = add. Information 4453 TEXT FUNCTION, CODED C an1..3 C107 TEXT REFERENCE C 4441 Free text, coded M an1..3 C108 TEXT LITERAL C 4440 Free text M an1..70 an..45 Service line 1 Time frame 4440 Free text C an1..70 an..45 Service line Free text C an1..70 an..45 Service line Free text C an Free text C an LANGUAGE, CODED C an1..3 Use of this segment: 1. : Is not used. 2. : Source from Miscellaneous set of the LARS (set type 590). Here are explicitly described those service related sales that cannot be assigned to any other set type. The FTX segment occurs only together with a LIN segment and up to two further RFF segments, but not with other segments used in the subset. FTX+OSI+++service description line 1: service description line 2' JXIL-PDePT-EDI / Status Page 23/46 Manual V 3.6

24 5.2.8 MOA Segment group 26 C5 MOA Amount details M1 Details on the different amounts Element Name Status Format UN Format AP 1 2 C516 MONETARY AMOUNT M 5025 Monetary amount type qualifier M an1..3 an..3 "146" = Sales amount net "14" = Gross amount "67" = Insurance amount "203" = Amount of the position 5004 Monetary amount C n1..18 n..15 Sales amount net Gross amount Insurance amount Amount of the position 6345 Currency, coded C an1..3 n3 Sales currency Billing currency 6343 Currency qualifier C an Status, coded C an1..3 "161" = Fees (Tax) "125" = Net, subject to VAT "204" = Net, not subject to VAT "150" = VAT amount "210" = Debit position "211" = Credit position Fees (Tax) in sales cur. Net, subject to VAT Net, not subject to VAT Vat amount Sales currency Use of this segment: 1. : Amount details. The segments occurs altogether four times. The distinction of the different amounts is made with the data element C516_ : Amount details. The segment occurs up to four times. The occurrence depends on the type of sales or the source of the position: Sales type C516_5025 C516_6345 Flight (FL) 161 Sales currency Train (DB) Bahn-Online (DO) START-CC (CC) Hotel (HT) / 211 Sales currency Sales currency Sales currency Not filled Note: The recipient of the invoice has to be able to deal with the sales currencies, which could possibly occur in transactions of his employees. MOA+146:100.00:978' 1. (Net amount in sakes currency) MOA+14:100.00:978' 1. (Net amount in billing currency) MOA+67:6.20:978' 1. (Insurance amount) MOA+203:106.20: (Amount of the position) MOA+125:2.61:978' 2. (Amount subject to VAT - DB) MOA+204:0:978' 2. (Amount not subject to VAT - DB) JXIL-PDePT-EDI / Status Page 24/46 Manual V 3.6

25 5.2.9 CUX Segment group 26 C5 CUX Currency details C1 Details of the exchange rate valid in this position Element Name Status Format UN Format AP 1 2 C504 CURRENCY DETAILS C 6347 Currency details qualifier M an Currency, coded C an Currency qualifier C an Currency rate base C n1..4 C504 CURRENCY DETAILS C 6347 Currency details qualifier M an Currency, coded C an Currency qualifier C an Currency rate base C n RATE OF EXCHANGE C n1..12 n..9 Exchange rate 6341 CURRENCY MARKET EXCHANGE, CODED C an1..3 Use of this segment: 1. : Detail of exchange rate between sales currency and basis currency. 2. : Is not used. Note: The recipient of the invoice has to be able to deal with the sales currencies, which could possibly occur in transactions of his employees. CUX+++1' JXIL-PDePT-EDI / Status Page 25/46 Manual V 3.6

26 PRI Segment group 28 C25 PRI Price details M1 Details on price information Element Name Status Format UN Format AP 1 2 C509 PRICE INFORMATION C 5125 Price qualifier M an1..3 an..3 Qualifier 5118 Price C n1..15 n..15 Price 5375 Price type, coded C an1..3 an Price type qualifier C an1..3 an Unit price basis C n1..9 n..9 Amounts 6411 Measure unit qualifier C an1..3 an SUB-LINE PRICE CHANGE, CODED C an1..3 an..3 Use of this segment: 1. : Is not used. 2. : The occurrence of this segment depends on the service type. The segment occurs within the service type Car rental (AV) altogether eleven times. The assignment is as follows: PRI+AAA: ' C509_5125 C509_5125 C509_5125 AAA Net rental price Not filled ABD Part payment Not filled AAS Costs for car delivery / collection service Not filled AAT Costs for car return Not filled AI Costs for fuelling Amount litre TEL Costs for car phone Amount units INS Costs for third party insurance Not filled CDW Costs for comprehensive insurance Not filled PDW Costs for passenger insurance Not filled PKT Costs for insurance package Not filled CU Deductible for occurring damages Not filled JXIL-PDePT-EDI / Status Page 26/46 Manual V 3.6

27 RFF Segment group 29 C10 RFF Reference details M1 Identifying details relating to the partner or the business transaction Element Name Status Format UN Format AP 1 2 C506 REFERENCE M 1153 Reference qualifier M an1..3 an..3 "CT" = Contract number "AF" = Airline "AGE" = Agency number "ACD" = add. Reference "AGT" = Service provider "RC" = Routing "DM" = Document number "VN" = Order number "AIM" = Reference 1154 Reference number C an1..35 Card number Airline Agency number add. reference Service provider Routing Document number Order number Reference 1156 Line number C an Reference version number C an1..35 Use of this segment: 1. : Contract number, i. e. the card number which was used to book this position. The segment occurs one time. 2. : Reference details. The segment occurs up to five times. The occurrence depends on the type of sales or the source of the position: Sales type C506_1153 C506_1154 Flight (FL) AF AGE Airline IATA agency number Train (DB) AGT ACD RC Train code (service provider) Train voucher number Train service Bahn-Online (DO) START-CC (CC) AGT ACD RC AGT ACD RC Train code (service provider) Online voucher number Train service CC Code (Service provider) CC voucher number CC service Car rental (AV) AGT Car rental mark Hotel (HT) AGT ACD DM RC AIM Hotel code Hotel voucher number CRS reservations number Grouped service details 1 Grouped service details 2 Other sales (SO) AGT Service provider RFF+CT ' 1. (Card number) RFF+AF:LH' 2. (Airline - FL) RFF+AGE:4711' 2. (IATA agency number - FL) RFF+DM:Voucher Number' 2. (Document number) RFF+VN:12345' 2. (Order number) JXIL-PDePT-EDI / Status Page 27/46 Manual V 3.6

28 DTM Segment group 29 C10 DTM Date / Time details C5 Details on customer specific date details and delivery dates Element Name Status Format UN Format AP 1 2 C507 DATE/TIME/PERIOD M 2005 Date/time/period qualifier M an1..3 n..3 "356" = Sales date "137" = Document date 2380 Date/time/period C an1..35 n8 Sales date Document date 2379 Date/time/period format qualifier C an1..3 n3 "102" = YYYYMMDD "102" = YYYYMMDD Use of this segment: 1. : Sales date. The segment occurs exactly one time. 2. : Document date. The segment occurs up to one time and will only appear the document number (RFF+DM) is part of the RFF segment. DTM+356: :102' 1. (Sales date) LOC Segment group 32 C9999 LOC Location details M1 Details on departure and arrival location and on routing information Element Name Status Format UN Format AP PLACE/LOCATION QUALIFIER M an1..3 n..3 "5" = Departure location "8" = Arrival location "7" = Travel destination "92" = Routing "162" = Agency C517 LOCATION IDENTIFICATION C 3225 Place/location identification C an1..25 an..25 Departure location Arrival location Travel destination Routing Agency "145" = Flight "144" = Train 3224 Place/location C an1..70 Hotel service description 1 C519 RELATED LOCATION ONE IDENTIFICATION C 3223 Related place/location one identification C an Related place/location one C an1..70 C553 RELATED LOCATION TWO IDENTIFICATION C 3233 Related place/location two identification C an Related place/location two C an RELATION, CODED C an1..3 Use of this segment: 1. : Is not used. 2. : Location details. The segment occurs up to two times. The occurrence depends on the type of sales or the source of the position: Sales type 3227 C517_3225 C517_3224 Flight (FL) 5 8 Travel route (start) Travel route (end) JXIL-PDePT-EDI / Status Page 28/46 Manual V 3.6

29 Train (DB) Bahn-Online (DO) 5 8 START-CC (CC) Car rental (AV) 5 7 Service information (Routing) START agency number Travel route (start) Travel route (end) Service information (Routing) START agency number Pick up location Return location START operation location START operation location LOC+5+FRA HAM FRA:145' 2. (Flight route - FL) LOC+8+:145' 2. (Flight route addition - FL) QTY Segment group 32 QTY Quantity details C5 Details on quantities contained in the positions C Element Name Status Format UN Format AP 1 2 C186 QUANTITY DETAILS M 6063 Quantity qualifier M an1..3 n..3 "68" = start quantity "69" = end quantity "114" = passengers 6060 Quantity M n1..15 n..15 KM on pick up KM on return 6411 Measure unit qualifier C an1..3 an..3 "KTM" = Kilometer "IE" = Persons "ZZ" = Children Use of this segment: 1. : Is not used. 2. : Kilometre details. The segment occurs two times but only when the service of a car rental (AV) is concerned DTM Segment group 32 C10 DTM Date / Time details C5 Details on customers specific date details and delivery dates Element Name Status Format UN Format AP 1 2 C507 DATE/TIME/PERIOD M 2005 Date/time/period qualifier M an1..3 "200" = pick up date "201" = pick up time "173" = return date "206" = return time 2380 Date/time/period C an1..35 pick up date delivery date pick up time delivery time 2379 Date/time/period format qualifier C an1..3 "102" = YYYYMMDD "401" = HHMM Use of this segment: 1. : Is not used. 2. : Time and date details. This segment occurs up to four times but only when the services type car rental (AV) is concerned. JXIL-PDePT-EDI / Status Page 29/46 Manual V 3.6

30 TAX Segment group 33 C99 TAX Details on taxes / customs/ fees M1 Details on tax types and rates Element Name Status Format UN Format AP DUTY/TAX/FEE FUNCTION QUALIFIER M an1..3 "1" = Individual "1" = Individual "9" = Information only C241 DUTY/TAX/FEE TYPE C 5153 Duty/tax/fee type, coded C an1..3 "VAT" "VAT" "LOC" = Amount subject to VAT "FRE" = Amount not subject to VAT "ABM" = Deductions with VAT "ABO" = Deductions without VAT 5152 Duty/tax/fee type C an1..35 C533 DUTY/TAX/FEE ACCOUNT DETAIL C 5289 Duty/tax/fee account identification M an1..6 not filled Amount subject to VAT Amount not subject to VAT Deductions with VAT Deductions without VAT 5286 DUTY/TAX/FEE ASSESSMENT BASIS C an1..15 C243 DUTY/TAX/FEE DETAIL C 5279 Duty/tax/fee rate identification C an Duty/tax/fee rate C an1..17 Vat rate Vat rate not filled 5273 Duty/tax/fee rate basis identification C an DUTY/TAX/FEE CATEGORY, CODED C an PARTY TAX IDENTIFICATION NUMBER C an1..20 Use of this segment: 1. : Value added tax rate. If the VAT rate is not known or contains mixed rates, the value is shown. In these cases the tax rates can be found on level 2 or level : Value added tax rate. This rate has specifically to be considered when the data element 5283 is filled with the value "1" and the value is shown on level 1, i. e. this position is a transaction of several partial services with mixed tax rates. If the data element 5283 is filled with the value "9", the amount details refer to other service (subject to vat and not subject to VAT) of the sales type car rental (AV). Only then the data element C533_5286 is filled with a value, but the data element C243_5278 in contrast is not filled (the codes for deductions with ABM or without VAT ABO do not conform the suggestions of the UN but are defined by LSAG for they are not existing.) TAX+1+VAT+++:::16' JXIL-PDePT-EDI / Status Page 30/46 Manual V 3.6

31 MOA Segment group 33 C99 MOA Amount details C1 Details on the different amounts Element Name Status Format UN Format AP 1 2 C516 MONETARY AMOUNT M 5025 Monetary amount type qualifier M an1..3 n3 "150" = Vat amount "120" = decl. VAT for other services "296" = decl. VAT for deductions 5004 Monetary amount C n1..18 n..9 Vat amount Decl. VAT for other services Decl. VAT for deductions 6345 Currency, coded C an1..3 n3 Currency 6343 Currency qualifier C an Status, coded C an1..3 Use of this segment: 1. : Value added tax amount. The segment occurs exactly one time. 2. : Value added tax amount. The segment occurs only if the service is a car rental service (AV). In case the position is not an invoice relevant position (DOC\C002_1001 the 1 has the value 456 or 454), the value added tax amounts here will be shown declaratorily. This is necessary to allow the sum of the single net amounts (PRI segment and TAX segments with qualifier 9 ) to equal the total net amount in the MOA segment of the level 1 (MOA+146). The identification of the declaratory value added tax must not be used to deduct value added tax on inputs. MOA+150:32.25:978' MOA+120:16.25' JXIL-PDePT-EDI / Status Page 31/46 Manual V 3.6