Download
sis simplified interline settlement technical migration n.
Skip this Video
Loading SlideShow in 5 Seconds..
SIS – Simplified Interline Settlement Technical Migration PowerPoint Presentation
Download Presentation
SIS – Simplified Interline Settlement Technical Migration

SIS – Simplified Interline Settlement Technical Migration

164 Vues Download Presentation
Télécharger la présentation

SIS – Simplified Interline Settlement Technical Migration

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SIS – Simplified Interline SettlementTechnical Migration SIS Awareness Regional Workshop, LIMA March 2011 Adina Minculescu

  2. Agenda • All Carriers - Old IDEC • Old IDEC Migration • Old IDEC Files and Submission Deadlines • Non-migrated Billed Carriers - Old IDEC • Recognition of SIS Down Converted Transactions • Down Converted Transactions – Source Codes • Invoice Header Values and Invoice Numbers • Batch Size • Sampling – Number of Invoices per Period • All Carriers - Migration Impact • Non-migrated Billed Carriers – SIS Impact SIS P3 – Lima Workshop - Technical Migration

  3. Old IDECMigration SIS P3 – Lima Workshop - Technical Migration

  4. non migrated claims ICH F12 Upload / IS-WEB ACH Recap Sheet Settlement Processes ICH F3 remainsACH Settlement Sheet unchanged* ICH ACH “Digital Signature” Company IS-WEB Billed Entity Central Repository Billing Entity IS-WEB IS-XML IS-XML Billing & Invoicing Processes Overall Processes Overall Processes IS-IDEC IS-IDEC Prorate Engine Usage File IS IDEC down converted non migrated Processes at time of Sales ATPCO 1 File = Old IDEC + IS IDEC down converted file Integrated Settlement NFP engine non migrated ATPCO Old IDEC ARC COMPASS™ SIS – Migration Overview * ICH reports include SIS & F12 claim differentiation. ACH: separate reports for SIS and Recap Sheet claims SIS P3 – Lima Workshop - Technical Migration

  5. Hard Cut-over – current IDEC file SIS P3 – Lima Workshop - Technical Migration 5

  6. Old IDEC – Connectivity Testing 2011 Carrier  SIS Connectivity testing to SIS Platform SIS  Carrier Connectivity testing from SIS Platform 13 Jun – 4 Jul 25 Aug Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Timelines subject to changes SIS P3 – Lima Workshop - Technical Migration

  7. Old IDECFiles & Submission Deadlines SIS P3 – Lima Workshop - Technical Migration

  8. Non-migrated Carrier: old IDEC From migrated and non-migrated billing entities Billed Entity Non-migrated ATPCO Old IDEC monthly Non-Migrated Billed Entity • One monthly old IDEC file, with • Old IDEC transactions from non-migrated billing carriers • Down converted IS-transactions (prime source codes) from migrated billing carriers SIS P3 – Lima Workshop - Technical Migration

  9. From non-migrated billing entities Old IDEC monthly From migrated billing entities IS-IDEC / IS-XML weekly Migrated Carrier: old IDEC & IS-File Billed Entity Migrated ATPCO Integrated Settlement Migrated Billed Entity • One old IDEC file, with old IDEC transactions from non-migrated billing carriers (monthly) and • IS-Format file (IS-WEB, IS-IDEC, IS-XML) from migrated billing carriers (weekly) SIS P3 – Lima Workshop - Technical Migration

  10. Old IDEC Old IDEC 25th* of month 15th* of month Old IDEC: Submission Deadlines Billing Entity Billed Entity ATPCO Non-Migrated Billing Carriers • Only ONE submission, around 15th of the month All Billed Carriers • One monthly old IDEC, around 25th of the month * subject to change SIS P3 – Lima Workshop - Technical Migration

  11. Agenda • All Carriers - Old IDEC • Old IDEC Migration • Old IDEC Files and Submission Deadlines • Non-migrated Billed Carriers - Old IDEC • Recognition of SIS Down Converted Transactions • Down Converted Transactions – Source Codes • Invoice Header Values and Invoice Numbers • Batch Size • Sampling – Number of Invoices per Period • All Carriers - Migration Impact • Non-migrated Billed Carriers – SIS Impact SIS P3 – Lima Workshop - Technical Migration

  12. Recognition of SIS Down Converted Transactions SIS P3 – Lima Workshop - Technical Migration

  13. Old IDEC: Recognize SIS transactions From migrated and non-migrated billing entities • SIS will flag the SIS down converted transactions • Invoice Header Record PAXField 15 - Currency conversion indicator field (=9) • All transactions in the flagged invoice come from a migrated billing carrier Billed Entity Non-migrated ATPCO Old IDEC monthly non migrated carrier needs to recognize SIS down converted transactions SIS P3 – Lima Workshop - Technical Migration

  14. Down Converted Transactions -Source Codes SIS P3 – Lima Workshop - Technical Migration

  15. SIS Prime Source Codes  Old IDEC The below Source Codes will be included from IS-Format into Old IDEC: SIS P3 – Lima Workshop - Technical Migration

  16. SIS Prime Source Codes  Old IDEC • Non-migrated billing carriers will still use the current Source Codes(correct or wrong) • Migrated billing carriers will use the new Source Codes Result: Non-migrated billed carriers must recognize both sets of Source Codes SIS P3 – Lima Workshop - Technical Migration

  17. Invoice Header Values & Invoice Numbers SIS P3 – Lima Workshop - Technical Migration

  18. Old IDEC: Invoice Values (from migrated carriers) Integrated Settlement ATPCO • Old IDEC Output: • Prime • Prime • Prime • IS-Format Input: • Prime • Prime • Prime • RM • RM • BM Applies to non-migrated billed carriers only! • Remember: down conversion of prime Source Codes only • Result: missing records in the invoices from migrated billing entities; invoice values not summing up • Note: In case of invoices flagged as SIS transactions: then a difference between invoice values and the sum records always relates to “excluded” non prime transactions IS-IDEC down converted SIS P3 – Lima Workshop - Technical Migration

  19. Old IDEC: Invoice Numbers (ex SIS) • During migration we will have • Old IDEC input and output: 6N mandatory & 8 A/N optional • IS-IDEC input and output: 10 A/N  Old IDEC SIS transaction invoice number could contain alpha codes SIS P3 – Lima Workshop - Technical Migration

  20. Batch Size SIS P3 – Lima Workshop - Technical Migration

  21. Old IDEC: Batch Size (ex SIS) • SIS – Batch size is unlimited (i.e. 99‘999) • Old IDEC – Batch size is 200 • RAM rule to prevent migrated billing carriers to exceed the batch size of 200 • However, no IS Validation Results in: non migrated carriers could receive batch sizes higher than 200 SIS P3 – Lima Workshop - Technical Migration

  22. Sampling –Number of Invoices per Period SIS P3 – Lima Workshop - Technical Migration

  23. Old IDEC – Form A/B: Invoice Numbers • Today old IDEC: • One Invoice Number per billing carrier Form A/B per period • After SIS go-live: • More than one invoice number possible per billing carrier Form A/B per periodSIS will not prevent this • Recommendation to migrated Sampling carriers:Submit only one Form A/B per period, unless agreed differently on a bilateral basis Results in: non migrated carrier must be able to handle this Sampling Members to agree change to RAM B1, Attachment A, Para 4 to allow multiple invoices per period. SIS P3 – Lima Workshop - Technical Migration

  24. Agenda • All Carriers - Old IDEC • Old IDEC Migration • Old IDEC Files and Submission Deadlines • Non-migrated Billed Carriers - Old IDEC • Recognition of SIS Down Converted Transactions • Down Converted Transactions – Source Codes • Invoice Header Values and Invoice Numbers • Batch Size • Sampling – Number of Invoices per Period • All Carriers - Migration Impact • Non-migrated Billed Carriers – SIS Impact SIS P3 – Lima Workshop - Technical Migration

  25. Migrating Passenger: Approach Always first ! SIS P3 – Lima Workshop - Technical Migration Three (3) Certification Processes : Partly – structured approach • Prime Billing Sampling Provisional Invoice (Form A and B) • Any other transactions • Any other transactions Any other transactions: • Rejection Memos • Billing Memos • Credit Memos • Sampling all other formats

  26. Migrating Passenger: Examples SIS P3 – Lima Workshop - Technical Migration Prime Billing & Sampling Provisional Invoice (Form A and B) RM BM, CM, Sampling Form D/E and F, XF OR Prime Billing & Sampling Provisional Invoice (Form A and B) & RM Sampling Form D/E and F, XF BM and CM OR Prime Billing & Sampling all Forms RM BM and CM OR All together

  27. Migrating Cargo: Approach Always first ! SIS P3 – Lima Workshop - Technical Migration Two (2) Certification Processes : Partly – structured approach • Original Billing • Any other transactions • Any other transactions Any other transactions: • Rejection Memos • Billing Memos • Credit Memos

  28. Migrating Miscellaneous: Approach SIS P3 – Lima Workshop - Technical Migration Two (2) Certification Processes : Partly – structured approach • Original Billing Any other transactions: • Rejection Invoices • Invoice based on an “Authority to Bill”

  29. Pre SIS go-live: Basic Member Profile All Carriers: Set up basic SIS Member Profile in IS-WEB • Needed to control old IDEC process • Needed to control IS-WEB access • Needed to validate submissions of migrated carriers SIS P3 – Lima Workshop - Technical Migration

  30. Rejection Values - 1 Context: • 2nd and 3rd RM: the representation of rejection values have changed in SIS showing the total amounts instead of difference amounts Migrated carriers: • After migration, there will still be RMs coming in, for billings performed before migrating • If the rejecting carrier is non-migrated, these RMs come in the „old format“ showing difference amounts Results in: migrated carriers need to handle these cases in their own RA systems SIS P3 – Lima Workshop - Technical Migration

  31. Rejection Values - 2 Non-Migrated carriers: • RMs from non-migrated carriers may be based on the difference value or may be based on the total value (depending on the rejecting carriers internal processes) • RMs from migrated carriers will be based on total valuesWhen you reject this RM, you have to go through IS-Web and use the total concept Results in: • Non-migrated carriers need to handle these cases in their own RA systems (see ISPG, chapter 3.8.) SIS P3 – Lima Workshop - Technical Migration

  32. Agenda • All Carriers - Old IDEC • Old IDEC Migration • Old IDEC Files and Submission Deadlines • Non-migrated Billed Carriers - Old IDEC • Recognition of SIS Down Converted Transactions • Down Converted Transactions – Source Codes • Invoice Header Values and Invoice Numbers • Batch Size • Sampling – Number of Invoices per Period • All Carriers - Migration Approach • Non-migrated Billed Carriers – SIS Impact SIS P3 – Lima Workshop - Technical Migration

  33. Migrated carriers remove paper invoice Migrated Billing Carriers can remove the paper invoice • Migrated billing carriers may remove the paper invoice three (3) months after migration • Bilateral agreements for an earlier or later removal possible • ACH proposes to remove paper immediately • Non-migrated billed carriers have to access IS-WEB in order to receive their invoices (Access IS-WEB, manually search their invoices and supporting documents and print them out on their printer and paper) SIS P3 – Lima Workshop - Technical Migration

  34. Non-Migrated Carriers to respond via SIS Rejections and Correspondence: According to the RAM rules (ref. RAM A10, part 2), if an airline receives a billing or rejection or correspondence that was submitted via SIS, and it wishes to dispute that billing, rejection or correspondence, it has to do so via SIS. This is applicable to all billing categories (Passenger, Cargo, Miscellaneous, and UATP after the respective SIS implementation). As this is not yet made explicit in the RAM for Misc and UATP, the RAM will be revised later this year to include this provision.   As a non-migrated carrier, you will use SIS (IS-WEB) at the latest from September 2011 onwards for Pax and Misc rejections and correspondence! SIS P3 – Lima Workshop - Technical Migration 34 March 2011

  35. Questions? We’d be glad to address all your questions through the SIS Forums, register for an account at: www.iata.org/SISForum Thank you. SIS P3 – Lima Workshop - Technical Migration 35 February 2011