Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D99B Messages page. Settlement transaction reporting message
0. INTRODUCTIONThis specification provides the definition of the Settlement transaction reporting message (STLRPT) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE1.1. Functional DefinitionA Settlement transaction reporting message is exchanged between participants in the Billing and Settlement Plan (BSP) to report transaction data for processing and account settlement purposes. BSP participants include airlines, agents, Computer Reservations Systems (CRS) and the BSP Centre. 1.2. Field of ApplicationThe Settlement transaction reporting message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. 1.3. PrinciplesA Billing and Settlement Plan (BSP) provides a central system and a global standard for reporting and settling accounts for transactions in the travel, tourism and leisure industry. The Settlement transaction reporting message has two distinct functions: (1) for a Computer Reservation System (CRS) to report agent transactions to the BSP Centre (BSPC); (2) for the BSP Centre (BSPC) to report agent transactions and totals to BSP participating airlines. In the CRS to the BSPC functional message, the data is transmitted on an agent transaction basis. In the BSPC to airline functional message, the data is transmitted on an airline agent basis. Totals of all transactions for an airline by reporting period, agent and transaction type are only transmitted in the BSPC to airline functional message. 2. REFERENCESIATA BSP Data Interchange Specifications Handbook Effective 01 June 1995. See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS3.1. Standard terms and definitionsSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 3.2. Message terms and definitionsIATA BSP Data Interchange Specifications Handbook
4. MESSAGE DEFINITION4.1. Segment ClarificationThis section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements. 0010 UNH, Message headerA service segment starting and uniquely identifying a message. The message type code for the Settlement transaction reporting message is STLRPT. Note: Settlement transaction reporting messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of messageA segment to indicate the type and function of the message. 0030 DTM, Date/time/periodA segment to indicate processing dates and times. 0040 NAD, Name and addressA segment identifying either the reporting agent or the BSP. 0050 Segment Group 1: CUX-EQN-MOAA group of segments occurring in the BSP-to-airline functional message to specify transaction totals of all agents by specified currency. 0060 CUX, CurrenciesA segment to specify the currency for the total amount. 0070 EQN, Number of unitsA segment to specify the number of agents reporting transactions for the specified currency. 0080 MOA, Monetary amountA segment to indicate the transaction totals for the specified currency. 0090 Segment Group 2: DTM-GIS-SG3-SG4A group of segments to specify either the transactions for the reporting period in the CRS-to-BSPC functional message, or the billing analysis transactions and totals in the BSPC-to-airline functional message. 0100 DTM, Date/time/periodA segment to indicate BSP reporting dates. 0110 X GIS, General indicatorA segment to specify indicators relating to the BSP processing of the transactions. 0120 Segment Group 3: CUX-EQN-MOA-QVRA group of segments occurring in the BSP-to-airline functional message to specify the transactions totals for all agents by specified currency for a billing analysis period. 0130 CUX, CurrenciesA segment to specify the currency for the total amount. 0140 EQN, Number of unitsA segment to specify the number of agents reporting transactions for the specified currency. 0150 MOA, Monetary amountA segment to indicate the transaction totals for the specified currency. 0160 QVR, Quantity variancesA segment to indicate monetary variances relating to BSP processing. 0170 Segment Group 4: RFF-LOC-DTM-FTX-SG5-SG6-CNTA group of segments to specify the transaction data for an agent. 0180 RFF, ReferenceA segment identifying the reporting agent. 0190 LOC, Place/location identificationA segment to identify the locale of the agent. 0200 DTM, Date/time/periodA segment to indicate the BSP remittance period ending date. 0210 FTX, Free textA segment to specify free text information relating to the agent transactions. 0220 Segment Group 5: CUX-MOA-QVRA group of segments occurring in the BSP-to-airline functional message to specify transaction totals for the agent. 0230 CUX, CurrenciesA segment to specify the currency for the total amounts. 0240 MOA, Monetary amountA segment to indicate the transaction totals for the specified currency. 0250 QVR, Quantity variancesA segment to indicate monetary variances relating to BSP processing for the agent. 0260 Segment Group 6: BUS-SG7-SG8A group of segments to specify transaction type data. 0270 BUS, Business functionA segment to specify the transaction type. 0280 Segment Group 7: CUX-MOA-QVRA group of segments occurring in the BSP-to-airline functional message to specify transaction type totals of an agent by specified currency. 0290 CUX, CurrenciesA segment to specify the currency for the total amounts. 0300 MOA, Monetary amountA segment to indicate the transaction type totals for the specified currency. 0310 QVR, Quantity variancesA segment to indicate transaction type monetary variances relating to BSP processing for the agent. 0320 Segment Group 8: LIN-DTM-RFF-NAD-LOC-CUX-GIS-IMD-MOA-ALC-FTX-TAX-SG9-SG10-SG11 A group of segments to specify the transaction 0330 LIN, Line itemA segment to specify the transaction. 0340 DTM, Date/time/periodA segment to indicate the date of issue of the transaction. 0350 RFF, ReferenceA segment identifying the reference numbers relating to a transaction. 0360 NAD, Name and addressA segment identifying the agent and passenger involved in the transaction. 0370 LOC, Place/location identificationA segment to identify the location where the transaction took place. 0380 CUX, CurrenciesA segment to indicate the currency relating to the transaction. 0390 X GIS, General indicatorA segment to specify indicators relating to the processing of the transaction. 0400 IMD, Item descriptionA segment to specify the type of transaction, in coded form. 0410 MOA, Monetary amountA segment to indicate transaction monetary amounts. 0420 ALC, Allowance or chargeA segment to indicate the charge. 0430 FTX, Free textA segment to specify free text information relating to the transaction. 0440 TAX, Duty/tax/fee detailsA segment to specify tax and commission amounts. 0450 Segment Group 9: DOC-DTM-FTX-PIA-SEQA group of segments to specify the ticket details. 0460 DOC, Document/message detailsA segment to specify the ticket number. 0470 DTM, Date/time/periodA segment to indicate the date of issue of a refunded ticket. 0480 FTX, Free textA segment to specify free text information relating to the ticket. 0490 PIA, Additional product idA segment to specify the substituted ticket number. 0500 SEQ, Sequence detailsA segment to specify the product delivery sequence number. 0510 Segment Group 10: PAT-MOA-RFF-DTM-AGR-GIS-NAD-FTX-IMD A group of segments to specify the terms of payment 0520 X PAT, Payment terms basisA segment to specify the terms of payment. 0530 MOA, Monetary amountA segment to indicate the monetary amounts associated with the terms of payment. 0540 RFF, ReferenceA segment identifying references relating to the terms of payment. 0550 DTM, Date/time/periodA segment to indicate the dates associated with the terms of payment. 0560 AGR, Agreement identificationA segment to specify the agreement details. 0570 X GIS, General indicatorA segment to indicate payment processing codes. 0580 NAD, Name and addressA segment identifying the client. 0590 FTX, Free textA segment to specify optional free text information. 0600 IMD, Item descriptionA segment to specify the form of payment, in coded form. 0610 Segment Group 11: GIR-IMD-GIN-SG12A group of segments to specify related document details. 0620 GIR, Related identification numbersA segment to specify the related document number. 0630 IMD, Item descriptionA segment to specify the type of related document. 0640 GIN, Goods identity numberA segment to specify stock control numbers. 0650 Segment Group 12: SEQ-FTX-ALC-GIN-RFF-IMD-NAD-TDT-DTM-LOC A group of segments to specify coupon 0660 SEQ, Sequence detailsA segment to specify the coupon delivery sequence. 0670 FTX, Free textA segment to specify print and service provider information in free text format. 0680 ALC, Allowance or chargeA segment to indicate the coupon charge. 0690 GIN, Goods identity numberA segment to specify coupon stock control numbers. 0700 RFF, ReferenceA segment to specify a frequent flyer number. 0710 IMD, Item descriptionA segment to specify services and products relating to the coupon or flight details. 0720 NAD, Name and addressA segment identifying the party to be billed. 0730 TDT, Details of transportA segment identifying the carrier and flight number. 0740 DTM, Date/time/periodA segment to indicate flight departure dates and times, and, coupon validity dates. 0750 LOC, Place/location identificationA segment to specify airports of departure and arrival and to indicate transit stops. 0760 CNT, Control totalA segment to specify the total number of transactions per agent. 0770 UNT, Message trailerA service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message. 4.2. Segment index (Alphabetical sequence by tag)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D99B Messages page. |
![]() |
Site Map | Privacy Policy | Terms of Use | Trademarks |