Transcript BS4 Interfaces and Validation

SIS – Simplified Interline Settlement
Integrated Settlement Interfaces and Validation
RA42 Breakout Session
Overview of this Presentation
 Introduction & Scope of Presentation
 Input Formats Overview
 Files (IS-IDEC & IS-XML)
 Web Interface (IS-WEB)
 Validation
 Supporting Documents
 Questions & Answers
SIS – Materials – RA42 Breakout Interfaces & Validation
2
September 2008
IDEC WG Members








Terry Palmer, BA (chair)
Kevin Sams, AA
Gilles Clochette, AF
Raj Bhavnani, EK
Cho YoonHyun, KE
Astrid Schorfheide, LH
Vera Fidalgo, TP
Joe Rochford, VS
 Terry Delaney, IATA
 Gianna Monsch, IATA
SIS – Materials – RA42 Breakout Interfaces & Validation
3
September 2008
IDEC WG Members - RAWG
Representing the Revenue Accounting Working Group:
 Gilles Clochette, AF
SIS – Materials – RA42 Breakout Interfaces & Validation
4
September 2008
WG Meetings
 February – Europe (2 days)
 April – Canada (2 days)
 May – Europe (2 days)
 June – Canada (2 days)
 Additional sub-meetings for File Validation
 3 further conference calls and homework due each
meeting
SIS – Materials – RA42 Breakout Interfaces & Validation
5
September 2008
Interline Settlement - Now
Paper invoices, with coupon listing, coupons, rejects, supporting documents
(monthly)
Settlement sheets –
(weekly)
F3– (weekly)
Billed
Airline
Cargo IDEC File (monthly)
Pax IDEC File (monthly)
prorate
engine
GDSs
BSPs
ACH
ICH
ATPCO
(incl F&F pre IDEC
Validation)
F12 – (weekly)
F1 – net amounts of inv
F2 - summary
Cargo IDEC File (monthly)
Billing
Airline
Pax IDEC File (monthly)
prorate
engine
ARC-Compass
(NFP storage)
AIA F&F
SIS – Materials – RA42 Breakout Interfaces & Validation
Recap sheets - weekly
6
F&F: receives NFP value
All: May receive sales records
September 2008
SIS – General Overview
Integrated Settlement
Settlement Processes
Billed
Airline
IS-IDEC
Overall Processes
IS-XML
ICH
“Digital
Signature”
Company
Billing & Invoicing Processes
Central
Repository
Processes at time of Sales
ARC
COMPASS™
SIS – Materials – RA42 Breakout Interfaces & Validation
IS-WEB
ACH
Overall Processes
IS-WEB
IS-XML
IS-IDEC
Usage
File
Billing
Airline
Prorate
Engine
NFP
engine
7
September 2008
Input Formats
This presentation applies to Passenger, Cargo, and Miscellaneous.
 Files (upload & download)


IS-IDEC
IS-XML
 IS-WEB
 Others – Usage File for Pax
 All contain same fields for a given record type
 Billing carrier can use any format at any time (“input combination”)
 Billing carrier’s choice doesn’t affect billed carrier (“format conversion”)
 Available formats depend on functionality (see other sessions)
SIS – Materials – RA42 Breakout Interfaces & Validation
8
September 2008
File Formats – IS-IDEC
 No longer data exchange file, but rather used to create
an invoice and settlement file
 Similar to IDEC, with enhancements:




Existing fields made mandatory (source codes, etc)
New records added (Rejection Memos, tax breakdowns, etc)
New fields added (for e-billing, additional info, etc)
Unnecessary records / fields removed (batch total records, etc)
 400 byte records (instead of 160 byte)
SIS – Materials – RA42 Breakout Interfaces & Validation
9
September 2008
File Formats – IS-IDEC
 Every carrier will need system enhancements to support
IS-IDEC
 IS-IDEC vs. IS-XML is an IT decision – it is immaterial to
the RA department
 Potential Benefits


Relatively little system development for carriers with a
sophisticated IDEC solution in place already
IS-IDEC format is more efficient (processing, storage, and
internet bandwidth) than IS-XML for a permanent record
structure
SIS – Materials – RA42 Breakout Interfaces & Validation
10
September 2008
File Formats – IS-XML
 New XML format for Integrated Settlement
 Based on IATA Aviation Invoice Standard, developed by
the Airport Invoice Task Force (AITF) and currently used
by IATA InvoiceWorks
 Identical fields and validation requirements to IS-IDEC
SIS – Materials – RA42 Breakout Interfaces & Validation
11
September 2008
File Formats – XML
 Every carrier will need to make system enhancements to
support IS-XML
 IS-IDEC vs. IS-XML is an IT decision – it is immaterial to
the RA department
 Potential Benefits

IS-XML format is more flexible and thus better than IS-IDEC for
non-permanent record structure (like Miscellaneous billings)
SIS – Materials – RA42 Breakout Interfaces & Validation
12
September 2008
IS-WEB Record Structure
 Web-based user interface to create and receive invoices
and records
 Identical fields and validation requirements to IS-IDEC
and IS-XML

Validation in real-time minimizes possibility of later validation
errors
 Download records created via IS-WEB in an excel file
 Not an alternative to a Revenue Accounting system
SIS – Materials – RA42 Breakout Interfaces & Validation
13
September 2008
IS-WEB
 Potential Benefits
 The web interface is hosted by IATA, so no system development
is required by carriers
 Potential Negatives
 More internet bandwidth will be required than file formats, and
the connection will have to be stable
SIS – Materials – RA42 Breakout Interfaces & Validation
14
September 2008
IS-WEB Additional Features
 Same system as for other web-based services
 Audit Trail
 Airline profile updates
 Discussed in other presentations
 View and print invoices in a standard format
 Extensive user access controls (administrator grants
view/edit and upload of supporting documents per user
per area)
SIS – Materials – RA42 Breakout Interfaces & Validation
15
September 2008
Breakdown Records
 Breakdown Records have been added where necessary
to provide for detailed, possibly repeating, data and to
provide for large amounts of text
 E.g., a coupon can have 0 or more tax breakdown
records, each detailing a tax type and amount
 Examples
 Coupon Prime Billing breakdown records:
 Tax, VAT breakdown
 Breakdown records for Rejection, Billing, Credit Memos:
 Reason Breakdown, Coupon Breakdown (with Tax & VAT)
SIS – Materials – RA42 Breakout Interfaces & Validation
16
September 2008
Example Breakdowns (Pax Rejection Memo)
Rejection Memo
(SFI = 21)
Reason Breakdown
= 31)
Reason(SFI
Breakdown
(SFI = 31)
Coupon Breakdown
(SFI
= 32)
Coupon
Breakdown
(SFI
= 32)
Coupon
Breakdown
(SFI = 32)
Tax Breakdown
= 33)
Tax (SFI
Breakdown
(SFI = 33)
Tax Breakdown
VAT Breakdown
= xx)
VAT (SFI
Breakdown
= xx)
VAT (SFI
Breakdown
(SFI = 34)
(SFI = 33)
SIS – Materials – RA42 Breakout Interfaces & Validation
17
September 2008
Validation
SIS – Materials – RA42 Breakout Interfaces & Validation
18
September 2008
Validation
 Validation will be necessary in the Integrated Settlement
environment as quality data is essential:


No paper invoice or “back up” to determine what the electronic
data means
Uploaded data is no longer a data exchange file in support of a
paper invoice, but rather the base for invoicing and settlement
 Some existing fields will continue to be passed through
the system without validation for use on a bilateral basis
SIS – Materials – RA42 Breakout Interfaces & Validation
19
September 2008
Examples of Validation
 Format Rules

Ensures data types (e.g. numeric/alphanumeric), length, etc as defined
 Correct Values

e.g. Settlement method cannot be “ACH” if both airlines are ICH
members
 Mandatory Fields

Source Code, Ticket Issuing Airline, Coupon Number, etc
 Rejection & Correspondence Timeframes and Order Enforced

1st RM  2nd RM  3rd RM  Correspondence
 Mandatory Breakdown Records Are Present

Tax breakdown records are present if coupon tax is populated and the
breakdown record sums match the tax field
SIS – Materials – RA42 Breakout Interfaces & Validation
20
September 2008
Results of Validation
 Timeline
 Will occur within a maximum of 6 hours after submission
 Will also occur after closure if the file was submitted on time (but
failures can’t be fixed in that period)
 Notification of validation results sent to submitting carrier
 Success
 Files go on to next step of IS (e.g. e-invoicing & settlement)
 Failure (options and permissions to be set in profile)
 Invoice or entire file is held until corrected
 Web Correction (IS-WEB interface)
 Delete (then, optionally, resubmit)
SIS – Materials – RA42 Breakout Interfaces & Validation
21
September 2008
Other Features Of File Formats
 20 character “airline’s own use” field (only for Pax)
 Value signs (+/-) where appropriate
SIS – Materials – RA42 Breakout Interfaces & Validation
22
September 2008
Supporting Documents
SIS – Materials – RA42 Breakout Interfaces & Validation
23
September 2008
Supporting Documents
 Supporting documents can be attached to most record
types (including Pax Prime Billings, Cargo,
Miscellaneous)
 Two types of supporting documents:


Electronic Presentation - Supporting document that is digital
but not in a defined and structured format. The document might
be a PDF file or an image that a computer can read but not
extract data from.
E-Electronic Document – Supporting document that is in a
defined and structured format which can be parsed by a
computer. Example formats are IDEC, XML, or CSV.
SIS – Materials – RA42 Breakout Interfaces & Validation
24
September 2008
Supporting Documents – With IS
Integrated Settlement
Settlement Processes
Billed
Airline
TBD
IS-IDEC
Enabling Processes
IS-XML
ICH
“Digital
Signature”
Company
Billing & Invoicing Processes
Central
Repository
Processes at time of Sales
Batch Transfer
e.g. FTP
ARC
COMPASS™
SIS – Materials – RA42 Breakout Interfaces & Validation
IS-WEB
ACH
NFP
engine
25
Enabling Processes
IS-WEB
IS-XML
TBD
Billing
Airline
IS-IDEC
Prorate
Engine
Usage
File
Batch Transfer
e.g. FTP
September 2008
Central Repository & Supporting Docs
 What?
 Any type of supporting document (image, PDF, IS-XML, etc)
 How long?
 As long as the data is operationally required
 When?
 Before or after the associated record is uploaded (with “pending
attachments” flag, which allows for notifications if not uploaded)
 How?
 To be determined in the next phase with the help of the supplier
SIS – Materials – RA42 Breakout Interfaces & Validation
26
September 2008
Uploading Supporting Documents
 Manually Via IS-WEB
 Search for or browse to a billing and upload single documents
 Automatically via a batch upload (to be determined by vendor)
 IS-XML – Multiple supporting documents could be embedded in
the XML format
 Other transfer protocols (e.g. FTP) – Supporting documents
uploaded in a batch format
SIS – Materials – RA42 Breakout Interfaces & Validation
27
September 2008
Uploading Supporting Documents
Potential Issues
 PC-attached single-document scanners very inefficient
 RA system might not have capability to attach scanner
 Matching supporting documents and billings could cause
errors
SIS – Materials – RA42 Breakout Interfaces & Validation
28
September 2008
Uploading Supporting Documents
Potential Solution
1. Batch Header produced (printed from RA system or
created manually)
2. Documents compiled in batches with batch header
3. All documents scanned into one single PDF document
4. IS or software at carrier could split PDF, remove batch
headers, and attach documents to their respective
billings
SIS – Materials – RA42 Breakout Interfaces & Validation
29
September 2008
Thank you.
Email:
[email protected]
SIS Website:
www.iata.org/whatwedo/finance/clearing/sis/index.htm
SIS – Materials – RA42 Breakout Interfaces & Validation
30
September 2008