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

Billing Memo

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 Eun L on 2011-01-04 04:28:03 Back to Topics

Billing Memo

Hello

 

For Billing Memo,

1. Only prime billings are using Billing Memo and BMs rejection should be handled on rejection stage with source code 04. Is that right?

 

2. ISPG said, we can use BM for all type of Passenger Miscellaneous Billing.

In the case of Miscellaneous Billing (M type invoice) for Passenger cases, is BM possible to use?

(We have issued a M type invoice for the passenger code share billings)

 

I still dont clearly know how to use BM except for correspondence cases.

Replied by Ashley H on 2011-01-13 16:33:13
Hi,
 
(1) This is correct - Prime Billings are using BMs and Billin Memo's rejections should be handled on rejection stage with Source Code 04. This is documented in the document of Rules for Source Codes.
 
(2) BM in Pax should be used for non-ticket transactions associated with pax transport. When M type invoice is used for costs actually relating to Pax transport, this could have an effect on the route-revenue recognition.
Best Regards

From:
Posted: Tuesday, January 04, 2011 4:28 AM
Subject: Billing Memo

Hello

 

For Billing Memo,

1. Only prime billings are using Billing Memo and BMs rejection should be handled on rejection stage with source code 04. Is that right?

 

2. ISPG said, we can use BM for all type of Passenger Miscellaneous Billing.

In the case of Miscellaneous Billing (M type invoice) for Passenger cases, is BM possible to use?

(We have issued a M type invoice for the passenger code share billings)

 

I still dont clearly know how to use BM except for correspondence cases.

 
ADVERTISEMENT


Additional information

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