IBSPs OUTPUT WORKSHOP - ABTA

IBSPs OUTPUT WORKSHOPMay 2018

IBSPs Migration Team

2

What is IBSPs ?

Is the re‐development of the IATA  Industry Settlement System using the latest technologies with additional improvements in security, speed and automation. 

IBSPs is fully PCI DSS compliant.(Payment Card Industry data Security Standard) 

3

Improvements Global Reference Information maintained once

Same Validation rules across all markets

DPC Automation, less reliance on Supplier

Consistent terminology used

Same Outputs in all markets

Reduced number of outputs

4

IBSPs Functionalities Net Remit Processing including NR5 (DISH Standard).

Variable Commission processing.

Commission Control (Default/Allowable). 

Multiple Remittance Calendars.

Additional Refund Validations.

5

OUTPUTS

6

Why New Output Reports

In May 2013 the ISSWG endorsed a recommendation to enhance the new outputs formats with aims of:

Minimise the number of outputs whilst maximising the content and to provide a set of outputs that can be applied globally across all BSPs

Align to airline current requirements for Electronic Documents (Current reports are based on the paper based documents, OPTATs, ATBs MPDs)

7

Benefits Outputs will use standard nomenclature

Reports provide a user friendly explanatory notes, in the header

Structure of reports has changed for a better display of information

Tax Breakdown is now an optional parameter, at country level, which can reduce the number of pages for billing reports by up to 80%

Statistical outputs based on calendar month and the Date of Issue of the document

8

Regulatory Requirements for Outputs Any report distributed in the BSP subject to regulatory

requirements will be analyzed and, if required, developed.

Contact Migration team by email at ibspseurope@iata.org

9

Third Parties Agreements with external companies that provide

statistical data based on reports produced by the BSP.

Need to contact them to identify what source data they are using.

Contact Migration team at ibspseurope@iata.org

10

OUTPUT NAMING CONVENTION The name of the report is divided into 3 sections The First two letters represent the Class The second two letters represent the recipient type The rest represents the Family to which the output is

associated

FC Financial ControlAG AgentBILLSUM Billing SummaryBILLDET Billing Detail

11

REPORT STRUCTURE The Report structure may contain

two sections, a summary providing grand totals by category followed by transaction details.

The Summary is provided on the first page instead of the last for ease of reference.

Details are grouped by Currency, Category, Scope, Agent (if appropriate) then by Document Type e.g. Issues, Refunds etc., with sub totals and finally by Transaction Code and Document Number.

PAGE HEADER

REPORT HEADER

SUMMARY TOTALS Currency/Country Header

CATEGORY HEADERo SCOPE Header (Conditional)o Billing Class Header

Transaction Detailso Billing Class Footero SCOPE FOOTER (Conditional)

CATEGORY FOOTER (Conditional) Currency/Country Footer (Conditional)

PAGE FOOTER

12

Output Packages

Reports are grouped in packages to facilitate the identification by the recipient. Naming convention does not change.

Packages are created in ZIP format. Reduce the number of reports in the BSPlink inbox.

Two Categories of Reports:

Default: Distributed to all recipients (Airlines, Agents) in the BSP.

Optional: Distributed to specified recipients upon request.

13

Migration Timelines

Region BSP Name Parallel TestProduction Cutover

Status

GDCAustria, Switzerland, Serbia and Montenegro, Czech Republic, Spain, France, United Kingdom, Portugal, Slovenia, Slovakia, Turkey, Kosovo

Sep‐18 Nov‐18 In Planning

14

File Mapping Maestro VS IBSPsType Package Package description Reports Great Britain

FCAGBILLDET R2930 & R2100FCAGBILLSUMFCAGCHARGESFCAGTAXSUMFCAGTAXDET FCAGREMS

MIAGTXNSUMMARY DQAGVALID R9000 & R2100MIAGNRTXN R2100

AGT‐DAILY Agent Daily PCAGDLYSALES

AGT‐BILLING‐HOT Agent Billing HOT FCAGBILLHOT R2150 & R2151AGT‐TRANSACTION Agent Transaction Files MIAGTXNDET R4004AGT‐STATDEST Agent Statistics by Destination MIAGSTATDEST R4098AGT‐STATB Agent Statistics by Transaction Type MIAGSTATB R4099

AGT‐COMPROD Agent Comparative Productivity MIAGCOMPROD R5021AGT‐YTD‐STATS AGT‐YTD‐STATS MIAGSAVI ‐ MIAGFIYR R5035

R2100Default

Optional

AGT‐BILLING Agent Billing

15

Outputs are classified in 5 Classes: RI – Reference Information – the exchange of Reference information with

BSPLink and other Portals, provides changes in participant status DQ - Data Quality - validation errors identified during file loading for all input

files identifying transactions that have been Rejected, Modified or flagged as Warning

PC – Payment Card – the provision of PCI/DSS compliant content to Acquirers and participants

FC - Financial Control - Outputs with the detailed or summary information of the billing transactions, related to the settlement amounts generated for a Carrier

MI - Management Information – related to business intelligent reports and transactions monthly summary reports

16

RI – Reference InformationReference Information is automatically Acquired from External Systems and these provide Participants with the changes that may impact financial processing.

Airline Participation Agent Accreditation Ticketing Authority ETSP association Airports Taxes

17

DQ – Data Quality Data Quality reports will be available for all participants and will

include those transactions that fail validation including DISH requirements.

Three severity levels may be applied to each validation. REJECT – Transaction cannot be processed as the Balance Payable cannot be

accurately calculated MODIFY – based on Airline/Agent Controls e.g. Commission control,

rates/amounts may be changed if they do not meet Airline settings WARNING – has no impact on Financial value

Some Global defaults may be deviated at a BSP or GDS level

18

DATA QUALITY - REJECTErrors are written to database table, and the errors are flagged against the transaction and prevents the transaction from being processed.

Would have resulted in an incorrect Balance Payable Would have resulted in an indeterminate Form of Payment Proscribed by a Regulatory Authority

19

DATA QUALITY - MODIFYErrors that will require certain default processing to adjust the content e.g. Reject to Cash, Change Commission rate etc.

Balance Payable has been modified due to incorrect Commission Balance Payable modified by additional of Pseudo cash in an

unbalanced transaction Balance Payable modified due to invalid Net Remit conditions Split between Standard and Supplementary Commission adjusted Reject to CASH

20

DATA QUALITY - WARNINGErrors which do not require any default processing are written to the database table, may appear on the validation reports but warning does not stop the transaction from being processed.

Invalid Check Digit on Related Ticket Document Invalid Check Digit on In Connection with Document Extraneous content in Reserved space

21

BSP Name

Data Type - Summary

22

Reporting Data

BSP Name

Agent code and Airline code

23

PC – Payment CardPayment Card provides the Invoicing Files to Acquirers and reports to all participants

Payment Card processing will become 7 days per week Resolution 728 governing Payment Cards will be applied Airlines have a number of options in dealing with Payment Card forms of

Payment: Airlines may “Reject” or “Modify” transactions by Payment Card Type or IIN

range that they do not accept. If the transaction is modified, this will appear in the “Modified” section of

the Daily Validation report and in the Airline Non Invoiced report. Where an Airline has no Merchant Agreement a Payment Card Type or IIN

ranges the transaction will also be reported in the Airline Non Invoiced report and the Airline will be responsible for arranging processing by their Banking institution.

24

PC – Payment CardDefault Reports distributed on a Daily Basis:

PCAGDLYSALES – Agent Payment Card Daily Sales. The Payment Card Daily sales report provides an Agent with a list of all processed transactions with a Credit Card form of Payment. Totals are displayed by Card Type and Airline

25

PC – Payment Card - PCAGDLYSALES

26

FC – Financial ControlProvides all the Outputs contributing to the control of Financial activities, these include:

Daily Accountable and Billing HOTs Daily Trial Billings Billing Summary and Detail reports Remittance and Settlement reports Tax Summary and Detail reports Tax on Commission reports

27

Sales Summary and Analysis

28

29

30

Line Layout - 1

The first seven columns identify the

Airline Transaction Code Document Number Issue date Coupon Usage Net Remit Identifier Stat code

31

Line Layout - 2

The next columns identify the

Forms of Payment Transaction Amount FARE Amount (TDAM-

TAXES Taxes Fees Penalties Commissionable Amount

32

Line Layout - 3

The last columns identify the

Standard Commission Rate and Amount

Supplementary Commission Rate and Amount

Tax on Commission Balance Payable

33

IndicatorsThe NR Code column shows that the Transaction is: Net Remit (NR:) The Method used (2) The Calculation applied (E)

The STAT column shows the SCOPE of the transaction: D – Domestic I – International

34

Mixed Forms of Payment

Mixed forms of Payment are represented vertically as few Transactions have multiple forms of Payment. Each FOP has its own entry with the Total shown as an “**”.All values from Fare Amount to Balance Payable will be on the “**” line.

35

Related Ticket/Documents - ISSUE

Related Ticket/Documents may be associated with Issues, Refunds, Debits and Credits.For an “ISSUE” Transaction with an “Exchange” Form of Payment it will be shown below the Ticket/Document to which it is related and display the Ticket/Document number and the Coupons utilised.There is no Transaction value associated with the Exchange but there may be an added collection

36

Related Ticket/Documents - REFUND

When associated with a REFUND it may be a different Document number for an “INDIRECT” refund or the same number for a “DIRECT” refund.Multiple documents may be refunded on an “INDIRECT” refund and these will normally be input via BSPLink

37

Related Ticket/Documents DEBITS/CREDITS

When associated with a DEBIT or CREDIT the Related Ticket/Document Number will represent the original ISSUE or REFUND that has created the necessity to apply an adjustment.

38

FCXXBILLDET – EasyPay

39

FCXXBILLSUM – Summary

40

DETAIL

The “DETAIL” section of this report is the same as the first page summary but by each individual carrier, it simply shows:

ISSUES – Cash and Credit REFUNDS – Cash and Credit MEMOS – Credits and Debits COMMISSION – Standard and Supplementary TAX on COMM – Tax on Commission Standard and Supplementary BALANCE PAYABLE – Remittance Amount

TOTAL TAX column will be added

41

FCXXBILLSUM – EasyPay

42

FCXXBILLSUM – EasyPay

43

MI – Management InformationManagement Information is basically the catch all for all outputs not associated with the five other classes

It includes Daily Transaction Summary and Detail files where Daily HOTs are not required

Billing Period outputs to meet Participant requirements that are not considered essential for Financial Control

Monthly Statistical Reports providing Month and Year to date

44

New Transactional Files

MIxxTXNDET• Document Details• TAX Detail Record

MIxxTXNEXT• Document Details• TAX Details Record• CC Details Record• Related Documents

Record

MIxxTXNMAX• Document Details• TAX Details Record• CC Details Record• Related Documents

Record• Routing Information

Record

45

FC - Remittance and Settlement Reports

46

FC –FCAGREMSUM

47

FC – FCAGREMDET

48

Training Modules

http://www.travelcampus.com/iataclassroom/bspreport/europe.html

User: EuropePassword: sis06

49

For additional information: All queries from markets to be directed through

the Customer Service Portal

Contact Migration Team at ibspseurope@iata.org