BSP Data Interchange Specifications Handbook - DISH
DISH is the global data interchange standard implemented by all Billing Settlement Plans (BSPs), to ensure consistency and the exchange of the highest possible quality data between BSPs and GDSs, airlines and other business partners. The DISH provides the passenger travel industry with a set of standard formats to support the reporting of Passenger sales and ticketing data for settlement purposes.
The DISH Handbook constitutes Attachment "A" to the Passenger Services Conference Resolution 750; BSP Data Interchange Specifications.
BSP data interchange standards are jointly agreed, developed and maintained by industry experts (particularly involved in revenue accounting) participating in BSPs and the BSP Data Interchange Specifications Group (BDISG).
DISH Revision 23 (Mandatory)
The PSC has endorsed new business requirements and numerous enhancements to DISH standards included within a new Revision 23 publication, declared effective 01 April 2018.
DISH Revision 23 has been developed to reflect a worldwide data interchange standard to be implemented by all Billing and Settlement Plans (BSPs) ensuring the highest possible quality data is exchanged between BSPs, airlines and strategic partners. View the DISH revision (pdf).
In order to produce Revision 23, major amendments include:
- Addition of 3DS and EMV data elements and records for card transactions
- Transparency in Payments (TIP) requirements for alternative payment methods aligned with PSC Resolution 728 on form of payment codes
- New data elements and RET/HOT records to support Complex Taxes Fees and Charges – Additional Coupon Tax Data
- New data elements and RET/HOT records to support GST related information
- CSI file format defined as a Mandatory layout for card transactions
- Complete revision of Testing/Certification Procedures and RET/HOT Data Quality Assurance in DISH Chapter 4
- Exempted taxes reflected within the TMFA & TMFT data elements
- New Diners/Discover and JCB specifications to the FPTI data element
- Addition of other new data element indicators related to Change of Gauge, Commission Control Adjustment, Arrival Date, Arrival Time, Departure Terminal and Arrival Terminal
- Mandatory/Conditional Status modifications to records and fields in alignment to PSC & Ticketing Resolutions
- Modification of CSI and CSP data elements status anomalies
DISH 23 replaces all previous Revisions and is presented as a mandatory Revision. Testing procedures and scenarios in Chapter 4 are to be followed.
DISH 23 Implementation Downloads
DISH 23 is to be tested and implemented by all BSPs and their business partners as per the following timelines outlined below that will be coordinated by the IATA DISH 23 Project team with all stakeholders.
- By 15 May 2018: All stakeholders to evaluate DISH 23, and advise IATA if any questions/problems with DISH 23 publication and/or the high level implementation dates
- By 01 August 2018: IATA to distribute the DISH 23 Project Plan (zip) including the per-BSP Implementation Schedule
- By 01 March 2019: DISH 23 functionality developments by all stakeholders
- 01 March – 01 July 2019: Testing/implementation for the selected Pilot BSPs
- By 01 December 2019: Global Roll-out, Implementation of all other BSPs
All questions are to be directed to IATA via the dedicated mailbox: firstname.lastname@example.org.
The following documents are to be used to support the DISH 23 Implementation Process:
DISH Revision 22 & Update Bulletins
DISH22 has been implemented in 2015 by all BSPs and their business partners.
DISH Revision 22.2 has been made obsolete.
The PSC has since adopted DISH Revision 22 Update Bulletin 2016/1 with various editorial enhancements and IATA EasyPay requirements with most recently, a new expedited DISH Revision 22 Update Bulletin 2018/1 reflecting the reporting of Transparency in Payment standards made effective 01 March 2018.
The following documents are to be used to support the DISH 22:
DISH Amendment Process
New business requirements and amendments to the DISH are to be forwarded to email@example.com using the DISH Amendment Form (doc). The proposal will be submitted to the next meeting of the BDISG.
Proposed amendments to DISH discussed and agreed at BDISG are endorsed by the PSC for adoption as an IATA standard.
When a new business requirement or an amendment necessitates urgent implementation (e.g.: a change in government regulation) an electronic procedure known as the PSC mail vote is used to expedite the change. This only applies to exceptional urgent items.
All agreed amendments become effective on the date recommended and published in the next Revision of the DISH.
Implementation plans are coordinated by IATA and are driven by the testing procedures outlined in DISH section 4.3.
Key Benefits of DISH
The DISH defines the reporting standards to enable GDSs to report ticket and miscellaneous documents sales made by BSP travel agents to the IATA Data Processing Centers, to enable the Sales data to be provided to airlines and credit card acquirers, and aids Remittance and Settlement.
The Handbook specifies the formats, specifications and data fields used in BSPs for the following DISH files and business functions.
- Agent Reporting (RET); agents reporting via the Global Distribution Systems (GDSs) to the BSP
- Airline Accounting/Sales (HOT); hand off transmission and accounting data file from the BSP
- Credit Sales Invoicing (CSI); transactions produced by the BSP for the card company or airline
- Ticket Inventory Data (TI); allocation of STD numbers to BSPs, ticketing systems and airlines
- Credit Card Settlement Plan (CSP); invoice data from BSPs to the card company, bank, airline or UATP contractor airline
DISH describes the status of availability and identifies the functional use of data elements. It also serves as a development tool for BSP systems and their interfaces with BSP participants.
The DISH contains set testing procedures used for implementation processes and conforms to provisions of the IATA Passenger Services and Agency Conference Resolutions, Ticketing handbook and Airline Coding Directory.
For questions, please contact firstname.lastname@example.org.