Skip to main content

Test Home
You & IATA

Search

You are here: Home » Services » Financial Services » Simplified Interline Settlement » SIS Forums
  • Print this page
  • Share this page

How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

This is a read-only copy of the discussions. To view the original, where you can reply, go here. For info on how to log in, please see the instructions.

Created by Claudia L (Lufthansa) on 2011-03-01 11:16:43 Back to Topics

How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi all.
 
Carriers who are not migrating at the earliest moment will have to reject items that were billed by SIS migrated carriers through SIS via capturing these rejections in IS-Web.
These rejections will be part of the non migrated carrier's revenue accounting system and the invoice that they create in that system as well in order to account for the invoice and its positions.
 
What is the expected procedure of ICH clearance and billing for these rejections? The billed (SIS migrated) carrier should not receive these positions twice / in two invoices nor should they be billed twice via ICH.
 
Please explain how IATA expects this to be handled.
 
Thanks,
Claudia (LH)
Replied by Ashley H on 2011-03-02 09:01:17

Dear Claudia,

 

This is correct: non-migrated carriers must respond to SIS billings (prime, RM, correspondence) via SIS, which means IS-WEB.

 

All SIS transactions, regardless of the reason why they are processed through SIS, are submitted to the respective Clearing House after successful validation.

These transactions may not be reported on the F12 to ICH or the Recap Sheet to ACH.

 

The carrier’s internal process however, will differ from carrier to carrier. This depends also from the “capabilities” of the Revenue Accounting System.

 

There is not “one single way” of doing it. Therefore the SIS Project Team has encouraged the carriers in all presentations to focus on the business processes – not only for the new system but also and in particular if they are non-migrated carriers.

 

Pax and Cargo: SIS is supporting the non-migrated carriers with the “listing in csv format”, which allows the carriers, to download the entered transactions (as a billing carrier) and upload them into their RA systems and/or create a posting file/document out of it.

 

Miscellaneous: a csv download for the line item details is not possible. We are currently evaluating the possibility to provide an IS-XML for the billing carrier.

 

As mentioned above, the solution is different for each carrier.

IATA and the SIS project team expect and encourage the non-migrated carriers to carefully define their business processes.

 

I hope this helps.

Best regards


From: Lufthansa
Posted: Tuesday, March 01, 2011 11:16 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi all.
 
Carriers who are not migrating at the earliest moment will have to reject items that were billed by SIS migrated carriers through SIS via capturing these rejections in IS-Web.
These rejections will be part of the non migrated carrier's revenue accounting system and the invoice that they create in that system as well in order to account for the invoice and its positions.
 
What is the expected procedure of ICH clearance and billing for these rejections? The billed (SIS migrated) carrier should not receive these positions twice / in two invoices nor should they be billed twice via ICH.
 
Please explain how IATA expects this to be handled.
 
Thanks,
Claudia (LH)
Replied by Binbin D (Accounting Centre of Chin) on 2011-03-09 22:59:58
Hi, IATA
 
I'd like to know when will  “listing in csv format”  be able to be downloaded by the billing entity, after Submission Deadline or before it? 
Thanks

From:
Posted: Wednesday, March 02, 2011 9:01 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Dear Claudia,

 

This is correct: non-migrated carriers must respond to SIS billings (prime, RM, correspondence) via SIS, which means IS-WEB.

 

All SIS transactions, regardless of the reason why they are processed through SIS, are submitted to the respective Clearing House after successful validation.

These transactions may not be reported on the F12 to ICH or the Recap Sheet to ACH.

 

The carrier’s internal process however, will differ from carrier to carrier. This depends also from the “capabilities” of the Revenue Accounting System.

 

There is not “one single way” of doing it. Therefore the SIS Project Team has encouraged the carriers in all presentations to focus on the business processes – not only for the new system but also and in particular if they are non-migrated carriers.

 

Pax and Cargo: SIS is supporting the non-migrated carriers with the “listing in csv format”, which allows the carriers, to download the entered transactions (as a billing carrier) and upload them into their RA systems and/or create a posting file/document out of it.

 

Miscellaneous: a csv download for the line item details is not possible. We are currently evaluating the possibility to provide an IS-XML for the billing carrier.

 

As mentioned above, the solution is different for each carrier.

IATA and the SIS project team expect and encourage the non-migrated carriers to carefully define their business processes.

 

I hope this helps.

Best regards


From: Lufthansa
Posted: Tuesday, March 01, 2011 11:16 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi all.
 
Carriers who are not migrating at the earliest moment will have to reject items that were billed by SIS migrated carriers through SIS via capturing these rejections in IS-Web.
These rejections will be part of the non migrated carrier's revenue accounting system and the invoice that they create in that system as well in order to account for the invoice and its positions.
 
What is the expected procedure of ICH clearance and billing for these rejections? The billed (SIS migrated) carrier should not receive these positions twice / in two invoices nor should they be billed twice via ICH.
 
Please explain how IATA expects this to be handled.
 
Thanks,
Claudia (LH)
Replied by Claudia L (Lufthansa) on 2011-03-10 11:24:06
Hi IATA.
 
In this case we would like to share our thoughts on how to avoid duplicate billing of these rejections. Maybe other carriers can comment on how they plan to handle this.
 
1. SUGGESTED PROCESS:
The RA system should flag inward invoices which are based on a down converted file from IATA (see separate flag in downconverted IDEC which is provided by IATA). In this way you know that all these invoice transactions have originally been billed via SIS.
Whenever you reject a transaction which is billed in such a down converted invoice from IATA, this rejection should get another flag (like “SIS-rejection”) in the RA system.
All rejections with such a flag should be invoiced in a separate invoice at the end of the period.
This special rejection invoice should not be reported to ICH/ACH by the non-migrated billing airline. Neither should it be printed and sent to the migrated billed airline.
The regular invoices are reported to ICH/ACH as usual and printed and sent as usual.
This special rejection invoice is manually captured in IS-Web with all its invoice positions and details, the settlement indicator would be “I, A, M” to initiate settlement via ICH/ACH for this invoice.
The billed migrated carrier would receive the rejections for SIS-billings only once, which is in the invoice captured in IS-Web. The billing via ICH/ACH for these rejections would only be done once based on the invoice captured in IS-Web.
Issues which would be avoided by using this process:
- the rejections on SIS-billings are billed only once via IS-Web, not a second time via the paper invoice
- there are separate invoice numbers for the regular rejections and prime billings and the rejections on SIS-billings
- the billed migrated carrier would not receive the same transaction twice or have to identify the already billed transactions he received via IS-transfer earlier.
2. MINIMUM REQUIREMENTS IN GENERAL
Minimum requirement in case you continue to include the rejections on SIS-billings in your regular paper invoice, while still capturing them in IS-Web:
- make sure the rejections on SIS-billings are only billed via ICH/ACH once
- mark the rejections on SIS-transactions in the paper listing you send to the billed migrated carrier so that he knows that these were transmitted via IS-interface already.
Comments are very welcome.
Thanks
Claudia (LH)
Replied by Ashley H on 2011-03-10 13:00:01

Hi,

 

All output files are available at “Billing Output Generation deadline” which is around 1-2 days after “Submission Deadline”.

 

Best regards


From: Accounting Centre of Chin
Posted: Wednesday, March 09, 2011 10:59 PM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi, IATA
 
I'd like to know when will  “listing in csv format”  be able to be downloaded by the billing entity, after Submission Deadline or before it? 
Thanks

From:
Posted: Wednesday, March 02, 2011 9:01 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Dear Claudia,

 

This is correct: non-migrated carriers must respond to SIS billings (prime, RM, correspondence) via SIS, which means IS-WEB.

 

All SIS transactions, regardless of the reason why they are processed through SIS, are submitted to the respective Clearing House after successful validation.

These transactions may not be reported on the F12 to ICH or the Recap Sheet to ACH.

 

The carrier’s internal process however, will differ from carrier to carrier. This depends also from the “capabilities” of the Revenue Accounting System.

 

There is not “one single way” of doing it. Therefore the SIS Project Team has encouraged the carriers in all presentations to focus on the business processes – not only for the new system but also and in particular if they are non-migrated carriers.

 

Pax and Cargo: SIS is supporting the non-migrated carriers with the “listing in csv format”, which allows the carriers, to download the entered transactions (as a billing carrier) and upload them into their RA systems and/or create a posting file/document out of it.

 

Miscellaneous: a csv download for the line item details is not possible. We are currently evaluating the possibility to provide an IS-XML for the billing carrier.

 

As mentioned above, the solution is different for each carrier.

IATA and the SIS project team expect and encourage the non-migrated carriers to carefully define their business processes.

 

I hope this helps.

Best regards


From: Lufthansa
Posted: Tuesday, March 01, 2011 11:16 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi all.
 
Carriers who are not migrating at the earliest moment will have to reject items that were billed by SIS migrated carriers through SIS via capturing these rejections in IS-Web.
These rejections will be part of the non migrated carrier's revenue accounting system and the invoice that they create in that system as well in order to account for the invoice and its positions.
 
What is the expected procedure of ICH clearance and billing for these rejections? The billed (SIS migrated) carrier should not receive these positions twice / in two invoices nor should they be billed twice via ICH.
 
Please explain how IATA expects this to be handled.
 
Thanks,
Claudia (LH)
Replied by Liz J on 2012-02-24 15:32:06

Dear SIS team;

 As our company (692-PZ) is not migrated yet, we need to clarify the following,

 To reverse billing rejections of companies already migrated, Do we have to do via IS Web or do as always integrated into our file F12 that goes to ICH?

Please clarify this because we have to reject billings from companies already migrated. These Invoices from our partners were originated at SIS.

 Thanks in advance.

Licha Jara-PZ 692


From:
Posted: 3/2/2011 9:01 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Dear Claudia,

 

This is correct: non-migrated carriers must respond to SIS billings (prime, RM, correspondence) via SIS, which means IS-WEB.

 

All SIS transactions, regardless of the reason why they are processed through SIS, are submitted to the respective Clearing House after successful validation.

These transactions may not be reported on the F12 to ICH or the Recap Sheet to ACH.

 

The carrier’s internal process however, will differ from carrier to carrier. This depends also from the “capabilities” of the Revenue Accounting System.

 

There is not “one single way” of doing it. Therefore the SIS Project Team has encouraged the carriers in all presentations to focus on the business processes – not only for the new system but also and in particular if they are non-migrated carriers.

 

Pax and Cargo: SIS is supporting the non-migrated carriers with the “listing in csv format”, which allows the carriers, to download the entered transactions (as a billing carrier) and upload them into their RA systems and/or create a posting file/document out of it.

 

Miscellaneous: a csv download for the line item details is not possible. We are currently evaluating the possibility to provide an IS-XML for the billing carrier.

 

As mentioned above, the solution is different for each carrier.

IATA and the SIS project team expect and encourage the non-migrated carriers to carefully define their business processes.

 

I hope this helps.

Best regards


From: Lufthansa
Posted: Tuesday, March 01, 2011 11:16 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi all.
 
Carriers who are not migrating at the earliest moment will have to reject items that were billed by SIS migrated carriers through SIS via capturing these rejections in IS-Web.
These rejections will be part of the non migrated carrier's revenue accounting system and the invoice that they create in that system as well in order to account for the invoice and its positions.
 
What is the expected procedure of ICH clearance and billing for these rejections? The billed (SIS migrated) carrier should not receive these positions twice / in two invoices nor should they be billed twice via ICH.
 
Please explain how IATA expects this to be handled.
 
Thanks,
Claudia (LH)
Replied by Ashley H on 2012-02-24 17:01:59

Dear Licha,

 

If you are billed in SIS, you are required to rejection the invoices in SIS (via IS-Web as you are not migrated). Please refer to the SIS Bulletin – March 2011, where this was communicated to the industry.

 

Hope this is clear.

Regards,

Ashley

 

From: JARA Maria Liz
Posted At: February-24-12 3:32 PM
Posted To: SIS Forums - Technical Aspects of Migration
Conversation: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

 

Dear SIS team;

 As our company (692-PZ) is not migrated yet, we need to clarify the following,

 To reverse billing rejections of companies already migrated, Do we have to do via IS Web or do as always integrated into our file F12 that goes to ICH?

Please clarify this because we have to reject billings from companies already migrated. These Invoices from our partners were originated at SIS.

 Thanks in advance.

Licha Jara-PZ 692


From:
Posted: 3/2/2011 9:01 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Dear Claudia,

 

This is correct: non-migrated carriers must respond to SIS billings (prime, RM, correspondence) via SIS, which means IS-WEB.

 

All SIS transactions, regardless of the reason why they are processed through SIS, are submitted to the respective Clearing House after successful validation.

These transactions may not be reported on the F12 to ICH or the Recap Sheet to ACH.

 

The carrier’s internal process however, will differ from carrier to carrier. This depends also from the “capabilities” of the Revenue Accounting System.

 

There is not “one single way” of doing it. Therefore the SIS Project Team has encouraged the carriers in all presentations to focus on the business processes – not only for the new system but also and in particular if they are non-migrated carriers.

 

Pax and Cargo: SIS is supporting the non-migrated carriers with the “listing in csv format”, which allows the carriers, to download the entered transactions (as a billing carrier) and upload them into their RA systems and/or create a posting file/document out of it.

 

Miscellaneous: a csv download for the line item details is not possible. We are currently evaluating the possibility to provide an IS-XML for the billing carrier.

 

As mentioned above, the solution is different for each carrier.

IATA and the SIS project team expect and encourage the non-migrated carriers to carefully define their business processes.

 

I hope this helps.

Best regards


From: Lufthansa
Posted: Tuesday, March 01, 2011 11:16 AM
Subject: How to avoid duplicate billing of rejections between migrated/non-migrated carrier?

Hi all.

 

Carriers who are not migrating at the earliest moment will have to reject items that were billed by SIS migrated carriers through SIS via capturing these rejections in IS-Web.

These rejections will be part of the non migrated carrier's revenue accounting system and the invoice that they create in that system as well in order to account for the invoice and its positions.

 

What is the expected procedure of ICH clearance and billing for these rejections? The billed (SIS migrated) carrier should not receive these positions twice / in two invoices nor should they be billed twice via ICH.

 

Please explain how IATA expects this to be handled.

 

Thanks,
Claudia (LH)

 
ADVERTISEMENT


Additional information

© International Air Transport Association (IATA) 2014. All rights reserved.