summary of resolution amendments · • the resolved that provision updated to amend the...
TRANSCRIPT
1 Adopted Changes at 42nd Passenger Agency Conference – with expedited effectiveness 1 January 2020
SUMMARY OF RESOLUTION AMENDMENTS
42nd Passenger Agency Conference
Changes with expedited effectiveness 1 January 2020 This document aims to provide Agents with a high-level summary of upcoming changes to the Passenger Agency
Conference Resolutions that were adopted at the last Passenger Agency Conference that took place last October 2019 in
Geneva. Agents may refer to the Book of Expedited Resolutions that will provide additional details on the actual changes in
the provisions.
Another edition including the changes adopted for normal effectiveness 1 June 2020 will be issued in conjunction with the
Book of Finally Adopted Resolutions when it becomes available. Finally, Agents will have the complete list of salient aspects
included in the cover page of the next Travel Agent’s Handbook, as usual.
General
• Various resolutions will be rescinded to remove outdated provisions (Resolution 800x, 804f, 824a, 824d, 828, 850b,
862, 866a).
• Editorial amendments and alignment of Resolutions:
– Preamble amended to replace reference of “countries and/or territories” to “markets and regions” (Resolution 800,
812, 818g, 896).
– Correction of reference to interest rate in various Resolutions, as adopted from PAC/40 in 2017 where some areas
in Resolutions were not correctly updated at the time (Resolutions 812, 818g and 832).
– Minor amendments to ensure that the dispute process described within Resolution 812, 818g and 850m are
consistent and provide clear provisions for all parties. There is no change in the process.
Resolution 800a – Application Form For Accreditation as an IATA Passenger Sales Agent
New paragraph to include provisions for the application of Agents dedicated to selling only NDC transactions and do not
have a GDS contract.
Resolution 812 – Passenger Sales Agency Rules
• The RESOLVED that provision updated to amend the re-adoption of Remittance Holding Capacity calculation for PAC
2020. Added provision to ensure that Agents must be provided with a minimum of six months notification before new
calculations may take effect to ensure there is a minimum communication requirement.
• Section 5.5.4, 5.9.3, 5.9.4 will be amended to allow Agents to adjust their Financial Securities which will impact the
Agent’s Remittance Holding Capacity on a relative percentage basis instead of the adjustment being based upon the
difference in amount of the Financial Security provided. This applies to both increases and decreases.
• Section 5.6 increases the minimum Remittance Holding Capacity for Risk Status ‘A’ Agents to change from USD5,000
to USD10,000 to provide more flexibility to Agents.
• Section 6.5.1 is amended to reflect that Monthly Remittance Frequency is effective until 31 December 2019, except for
South Africa, Botswana and Morocco where the effective date is until 30 April 2020.
• Section 6.5.3 is amended so that the Remittance Frequencies and exceptions to Remittance dates adopted by
Conference will be reflected in a new Attachment ‘I’ to Resolution 812 for clarity, instead of having it published on
IATA’s website.
2 Adopted Changes at 42nd Passenger Agency Conference – with expedited effectiveness 1 January 2020
• Section 6.9.4 is amended to include the operations of Indonesia and Pakistan within its provision that governs the
encashment of Agents’ Financial Securities in the event of an Agent default.
• Section 6.10.1.1 is amended to limit Post-Billing Disputes to debit documents against Agents to avoid mistaken usage
as observed in the past two years to a small number of cases where Post-Billing Disputes have been made on credit
documents due to misunderstanding by the users of the functionality.
• Whereas 6.10.1.5 is amended to create further parity for a 7-day extension to be granted to either party of the dispute,
given that a response was provided from the counter party from the 24th day onwards, instead of solely on the 30th
day.
• Attachment ‘B’, New paragraph to include provisions for the application of Agents dedicated to sell only NDC
transactions and do not have a GDS contract).
Resolution 818g – Passenger Sales Agency Rules
• Attachment ‘A’, Section 1.6.2 is amended to reflect that Monthly Remittance Frequency is effective until 31 December
2019 except for Morocco where the effective date is until 30 April 2020.
• Section 1.11.1 is amended to limit Post-Billing Disputes to debit documents against Agents to avoid mistaken usage as
observed in the past two years to a small number of cases where Post-Billing Disputes have been made on credit
documents due to misunderstanding by the users of the functionality.
• Whereas 1.11.1.5 of the Attachment is amended to create further parity for a 7-day extension to be granted to either
party of the dispute, given that a response was provided from the counter party from the 24th day onwards, instead of
solely on the 30th day.
Resolution 824r – Refunds
Section 1 is amended to clarify that Refunds should be conducted against the original Airline and currency that the
transaction was issued in.
Resolution 866 – Definitions of Terms used in Passenger Agency Programme Resolutions
Amendments or inclusion of definitions to introduce concepts required for NDC Sales to be described under PAC
Resolution provisions.
RESOLUTIONS ADOPTED AT THE
FORTY SECOND PASSENGER AGENCY CONFERENCE
IATA Office Geneva, Switerland, 22-24 October 2019
FOR EXPEDITED IMPLEMENTATION
PAC/Reso/680
Paseo de la Castellana 95
28046 Madrid
Spain
M E M O R A N D U M PAC/Reso/680
To: All Members, Passenger Agency Conference
Accredited Representatives
From: Director, FDS Operations, GDC
Date: 30 November 2019
Subject: FORTY SECOND PASSENGER AGENCY CONFERENCE (PAConf/42)
IATA Office, Geneva, Switzerland 22-25 October 2019
ADOPTED RESOLUTIONS FOR EXPEDITED IMPLEMENTATION
1. Attached are the expedited Resolutions adopted at PAConf/42, 22-24 October 2019.
2. Members are requested kindly to file these Resolutions with their respective Government authorities,
where required, and to advise this office of such authorities’ reactions when received.
3. The filing period is 1-31 December 2019 for effectiveness 1 January 2020 (unless otherwise indicated).
4. You are reminded that these Resolutions will be declared effective upon receipt of the required
Government approvals, in accordance with Resolutions 001 and 006.
Juan Antonio Rodriguez
Director – FDS Operations, GDC
Contents
Extract From The Draft Minutes Of The Forty Second Passenger Agency Conference Relating To Expedited
Resolution Amendments............................................................................................................................................................................. 1
Outline Of Contents And Status Of Effectiveness ............................................................................................................................. 9
Resolution 800 - Passenger Sales Agency Rules ............................................................................................................................. 10
Resolution 800a - Application Form For Accreditation As An Iata Passenger Sales Agent .............................................. 11
Resolution 812 - Passenger Sales Agency Rules ............................................................................................................................. 12
Resolution 818g - Passenger Sales Agency Rules ........................................................................................................................... 31
Resolution 824r - Refunds ........................................................................................................................................................................ 35
Resolution 832 - Reporting And Remitting Procedures ................................................................................................................. 36
Resolution 866 - Definitions Of Terms Used In Passenger Agency Programme Resolutions .......................................... 37
Resolution 896 - Alternative Transfer Method Providers & Alternative Transfer Methods [Transparency In
Payments Transition] ................................................................................................................................................................................. 38
Page | 1 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
EXTRACT FROM THE DRAFT MINUTES OF THE FORTY SECOND PASSENGER AGENCY CONFERENCE RELATING TO EXPEDITED RESOLUTION AMENDMENTS
Geneva, Switzerland
22-24 October 2019
ITEM R3 – CORRECTION IN REFERENCE TO COUNTRIES
M/ Mr. Alvarenga explained that this item proposed amending the preambles of Resolutions 800, 812, 818g
and 896 by replacing reference to ‘country’ with the more accurate reference of ‘markets and regions’.
M/ On a formal vote, Conference unanimously adopted the changes to the resolutions as shown at
Attachment ‘A’ to the agenda paper for expedited effectiveness of 1 January 2020.
M/ In addition, PAConf granted a temporary editorial right to the Secretary to similarly update any other
references to ‘country’ or ‘countries’ where necessary to ensure they were reflected correctly throughout
resolutions.
Action: Secretary
ITEM R13 – ENCASHMENT & SETTLEMENT OF BANK GUARANTEE, INSURANCE BOND OR
OTHER FORM OF GUARANTEE – ID AND PK
M/ Mr. Prabaharan reported that this paper concerned proposals by the LCAG-Ps of Indonesia and Pakistan
for those two countries to be included in Section 6.9.4 of Resolution 812 setting out the terms for encashment
of Bank Guarantees, Insurance Bonds or other forms of guarantee. The airlines had unanimously voted in favour
of the proposal which would limit their exposure in terms of default and satisfy those airlines that wished to
pursue stronger risk management practices. The provision was already in place for India and had also applied to
Singapore until the implementation of NewGen ISS when it was agreed that the RHC would be equal to the
Financial Security amount.
M/ On a formal vote, PAConf unanimously adopted the inclusion of Indonesia and Pakistan in Section 6.9.4
of Resolution 812 as shown on page 2 of the agenda paper for expedited effectiveness of 1 January 2020.
ITEM R14 – SUNSET MONTHLY REMITTANCE
ITEM R14.1 – REQUEST TO DEFER THE SUNSETTING OF MONTHLY REMITTANCE FOR BSP
ZA
ITEM R14.2 – REQUEST TO DEFER THE SUNSETTING OF MONTHLY REMITTANCE FOR BSP
BW
M/ Following the status report on item R14 given during the Open Session, the Chairman advised that he
would take items R14.1 and R14.2 together. These concerned specific requests from APJC ZA and APJC BW
for an extension of monthly remittance in their markets until 30 April 2020. The paper from APJC ZA included a
supporting letter received from the National Treasury of South Africa. APJC BW was asking for more time in
order to engage with corporate and government clients on the need to change or improve payment terms on
Page | 2 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
travel related transactions and were also in consultation with local banks seeking the introduction of lodge cards
in the market, which was seen as a vital component in addressing delayed payments by corporate clients. The
Chairman had some sympathy with their predicament and asked PAConf whether there would be a problem in
agreeing to an extension until 30 April 2020 for South Africa and Botswana.
M/ A member was also sympathetic to their request, however it was a little unpredictable and it could be
that, come the end of March, there would be another request to defer further.
M/ The Chairman believed it would be fair to indicate that no further extension would be granted and he
hoped that would be supported by Conference. He planned to take the vote on the basis that no further
extension would be tolerated.
M/ Mr. Herrero thought this was a good opportunity to show that they were listening to the APJCs and it was
important highlight that especially to APJCs that did not want to meet. APJC Spain had had an opportunity to
meet and agree to a plan, or request an extension, but it was not possible to do that if the APJC was not meeting.
M/ With respect to Spain, one of the countries still on monthly remittance, a member asked whether IATA
planned to inform all the agents in the market that monthly remittance would be removed effective 1 January
2020. Mr. Alvarenga confirmed that IATA had already done that and communicated that to the individual agents
that would be impacted. There had also been a conference call to explain what had happened at PAConf last
year and no objections were received from the Agents during the call.
M/ On a formal vote on items R14.1 and R14.2, and on the understanding that there would be no further
extension, PAConf unanimously agreed to extend the sunsetting of monthly remittance in South Africa and
Botswana until 30 April 2020. Unanimously adopted.
ITEM R14.3 – MOROCCO – LETTER FROM APJC CHAIRMAN
M/ Further to the discussion the previous day during the Open Session, Mr. Alvarenga reported that there
had been an overnight exchange of emails with the PAConf delegate from Morocco requesting that the deadline
for the removal of monthly remittance for their market also be delayed to April 2020. In support of their request,
the PAConf representative cited the challenging economic environment, corporate payment delays and issues
with credit card payment among others. The member proposed holding a new APJC meeting in the next few
weeks and was ready to work closely with the travel agents and airlines on an action plan to ensure a smooth
transition to a new remittance frequency. That was the stated position of the carrier for any subsequent vote on
this item.
M/ The Chairman advised that he would take a vote on item R14.3 to postpone the sunsetting of monthly
remittance in Morocco as subsequently amended by the national carrier to request consideration of a 30 April
2020 sunset date, on the understanding that the same provisions as for South Africa and Botswana would apply
in that no further extension or exemption would be granted. On that basis, Conference unanimously approved
extending the deadline for the sunsetting of monthly remittance in Morocco until 30 April 2020.
M/ The Chairman highlighted that after 30 April next year, remittance frequency in 180 countries worldwide,
with the exception of Israel and Tunisia, would be at least fortnightly. He thought that was excellent progress but
asked IATA to see what it could do to move the last two countries also.
M/ Mr. Lugo stated that eliminating monthly remittance in Israel would present a competition law problem
and IATA was trying to introduce variable remittance scheme where airlines and agents could agree bilaterally
and that would satisfy Israeli competition law. It would still require negotiation with the APJC. APJC Israel was a
Page | 3 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
very unique institution and it did not function like other APJCs. He had spoken with the IATA Country Manager
and they would see how it went.
M/ The Chairman asked that this be a formal item on the agenda of the next APJC Israel meeting.
Concluding the discussion on this item, he congratulated PAConf on the action it had taken and thought it was a
good step forward.
Action: Legal/APJC Israel
ITEM R16 – RHC RE-ADOPTION
M/ Ms. Simoes reminded PAConf that the 100% RHC formula had been adopted after significant discussion
with the global travel agent associations. At the time, it was agreed that the formula would be reviewed by this
year’s Conference following a full year of NewGen ISS. In addition to the information in the agenda paper, Ms.
Simoes then presented a few slides with the global RHC results, showing that less than 2% of agents were
reaching their RHC limit on a monthly basis. Less than 4% were reaching 75% of their RHC on a monthly basis
and for the 12 month period October 2018 to September 2019, only 6.7% of agents migrated had reached 100%
of their RHC level. The RHC results were consistent with expectations and demonstrated that the majority of
agents had not been impacted by the RHC to date and suggested that cumulatively, with a +100% growth
threshold, only a small minority of agents would reach their RHC on an annual basis.
M/ When the analysis had been undertaken, it was recognized that NewGen ISS had only been live in a
handful of countries for 12 months. In consultation with PSG, it was proposed to recommend to Conference that
the current +100% RHC formula should be re-adopted for another year pending further analysis. Therefore this
paper was asking Conference to re-adopt the provisions under Resolution 812, Section 5.6 subject to further
analysis of the RHC results in NewGen ISS migrated markets and review of the RHC calculation by Conference in
2020. IATA would also consult with the agent community in a timely manner if there was any intent to change the
calculation.
M/ Ms. Simoes then highlighted that, in doing the initial analysis, the country-specific details for Canada
revealed that the minimum RHC amount for Risk Status A agents, established at the equivalent of USD 5,000, was
too low. PSG had therefore endorsed raising the amount to USD 10,000, which would still limit the airlines’ risk
exposure whilst allowing agents, who in the past had little or no Cash sales, greater flexibility year over year. As
indicated in the agenda paper, that change was being requested for expedited effectiveness.
M/ A member commented that, whilst he did not object to the formula being extended for another year, he
did have difficulty in explaining to agents why there was no difference in the formula for Risk Status A and Risk
Status B agents. He suggested that perhaps consideration could be given to having a different formula for Risk
Status A, B and C agents.
M/ In terms of the agreement to go forward with the same calculation, Ms. Simoes explained that that had
come out of the decision with the global travel agent associations, until they had more experience with a greater
number of countries being live with NewGen ISS for an extended period of time. It was something that could be
considered, but the proposal here simply represented how the consultation had taken place and the outcome of
that consultation.
M/ The Chairman advised that he would take two formal votes. The first vote would be on Attachment A,
pages 1-2, to increase the RHC minimum amount from USD 5,000 to USD 10,000. The second vote was on
Attachment B to readopt the existing RHC formula for a further year.
Page | 4 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
M/ A member agreed that whilst it was correct to say that they needed to look at the formula, they also had
to look at all the elements together. They had put a lot on the travel agents in recent years. He would like to look
at the different components and have them assessed, otherwise they were in danger of only looking at part of
the puzzle. They had not yet found the perfect solution and whilst he did not disagree with the action taken here
today, he thought they were still facing a broader problem that should be looked at by PSG.
M/ The Chairman agreed that the NGI arrangements would need to be monitored constantly to make sure
they had got things right. Mr. Popovich supported the need for further evaluation and suggested that they should
also review their tool set to see if they were using the tools in the right way.
Action: NGI Team
M/ On a formal vote, PAConf unanimously adopted the changes shown at Attachments A and B to the
agenda paper for expedited effectiveness of 1 January 2020. The Chairman commented that it was very likely
that there would be a proposal to revise the formula for next year’s Conference
ITEM R18 – NDC FOR BSP – CHANGES TO APPLICATION FORM
M/ Presenting this item, Mr. Alvarenga explained that with the implementation of NDC, a seller might decide
to have its air transaction issuances fully processed outside the GDS channel, but nonetheless still show an
interest in becoming an IATA Accredited Agent to benefit from the value proposition of participating in a BSP. It
was therefore proposed to amend Resolutions 800a and 812 Attachment B (Application Forms for Accreditation
as an IATA Passenger Sales Agent) to indicate the seller conducted NDC-only transactions with airlines and to
provide IATA with a letter of recommendation from an IATA Member Airline.
M/ On a formal vote, PAConf unanimously adopted the proposed amendments to Resolution 800a and 812
Attachment ‘B’ as shown in the body of the agenda paper for expedited effectiveness of 1 January 2020.
ITEM R20 – SETTLEMENT WITH ORDERS (SWO)
M/ Speaking to this item, Mr. Ruy (Head, SwO Programme) reported that the SwO messaging standard under
Resolution 758 had been unanimously approved by the Passenger Standards Conference (PSC) meaning that
airlines and agents could start using the SwO standard. The objective of this paper was to clarify that Orders
sent by BSP airlines formed part of the agency risk management framework under the Passenger Agency
Programme.
M/ PAConf unanimously endorsed the proposal to amend the definition for ‘BILLING’ in Resolution 866 and
include a new definition for ‘ORDER MANAGEMENT SYSTEM (OMS)’ as shown in the agenda paper for expedited
effectiveness of 1 January 2020.
ITEM R25 – CHANGES IN REMITTANCE DATE – SAUDI ARABIA
M/ Ms. Awwad presented this item from APJC Saudi Arabia. She explained that Saudi Arabia was on four
times a month Remittance Frequency but there were two long holidays a year, Eid and Hajj, where it was proposed
to postpone the remittance dates during those periods to the second working day after the holidays as banks
were naturally very busy immediately after the holidays. The APJC had unanimously endorsed the proposal for
1 January 2020 effectiveness.
M/ The Chairman had difficulty with the proposal as there was no resolution text to go with it and it was
unclear how it was supposed to work. He thought it would be a difficult thing to administer and thought some
Page | 5 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
resolution text would be needed. He asked the national carrier, Ms. Awwad and Mr. Alvarenga to discuss the
matter off the floor to see what could be done.
M/ Later in the meeting, under discussion of item R33, it was agreed that an exception for Saudi Arabia to
accommodate this proposal would be included in the new Attachment ‘I’ being developed as part of Resolution
812.
Action: Secretary
ITEM R27 – DISPUTED AGENCY DEBIT MEMOS
M/ Ms. Manova reported that this item had come about as a result of an issue raised by the GDC highlighting
that the text in Resolution 850m, Section 4.9 was not aligned with the text in Resolution 812, Section 6.6.7 and
Resolution 818g, Attachment ‘A’, Section 1.7.9, giving rise to a number of TAC cases as explained in detail in the
agenda paper. The request was therefore to adopt clarification of the language in Resolutions 812 and 818g to
reflect the intent of Resolution 850m.
M/ On a formal vote, Conference unanimously adopted the proposed resolution changes set out in
Attachment ‘A’ of the agenda paper for expedited effectiveness of 1 January 2020.
ITEM R29 – RESOLUTION 824R – REFUNDS
M/ Mr. Saenz reported that a review by the RET Validation Task Force (RVTF), which was currently working
on the systematic revision of all RET validations application in the IATA DPC system to ensure compliance with
the DISH rules as well as PAC and PSC resolutions, had resulted in two proposals relating to refunds of traffic
documents. The first was that any refund should be affected in the currency in which the document was originally
issued, and the second was to clarify that the traffic document could only be refunded using the same airline
ticketing authority.
M/ On a formal vote, Conference unanimously adopted the proposed resolution changes set out in the body
of the agenda paper for expedited effectiveness of 1 January 2020.
ITEM R33 – INCLUSION OF REPORTING & REMITTANCE EXCEPTIONS IN R812
M/ Ms. Wan reminded PAConf that Resolution 818g Attachment C contained a list of exceptions to
remittance dates submitted by the APJCs to Conference. With the migration to Resolution 812, it had been
decided to upload that information onto the IATA website instead of putting it as an attachment to the resolution
in the Resolutions Manual. Since then, the governance team had realized that the upload was difficult to find and
maintain, and it did not seem like a binding document because it was not part of the resolution. The
recommendation therefore was to put the information back into the resolution as an attachment to Resolution
812 and, for completeness, also to include information on remittance frequencies as well as exceptions, as
shown at Attachment A to the agenda paper. If adopted by Conference, the governance team also requested
editorial rights to include any changes adopted by this Conference into the new Attachment, including the Saudi
Arabia exception discussed earlier under item R25.
M/ The Chairman regarded this as a major change, but believed it would be very beneficial. On a formal vote,
Conference unanimously adopted the proposed changes to Resolution 812, Section 6.5.3.2 as shown in the body
of the agenda paper and the inclusion of a new Attachment ‘I’ to Resolution as shown on pages 1-21 of
Attachment ‘A’, in addition to any editorial amendments to include changes adopted by PAConf/42, for expedited
effectiveness of 1 January 2020.
Page | 6 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
M/ Reminding Conference of discussions under item R25 the previous day, the Chairman ascertained that
there were no further comments and no opposition to going into the Attachment ‘I’ agreed under item R33.
Action: Secretary
ITEM R35 – EDITORIAL CHANGES TO RESOLUTIONS 812, 818G AND 832
M/ Mr. Mula advised that this item was an editorial change to align text in certain resolutions according to
the agency fees tables adopted by PAConf in 2017.
M/ On a formal vote, Conference unanimously adopted the proposed amendments to Resolutions 812,
818g and 832 set out at Attachment ‘A’ of the agenda paper for expedited effectiveness of 1 January 2020.
ITEM R37 – AMENDMENT TO RESOLUTION 812 SECTION 5
M/ Mr. Lugo advised that Revision 2 to R37 dated 22 October 2019, circulated on site, would need to be
rescinded and withdrawn. When a group of member airlines had met after the PSG on Monday there was some
brainstorming on Resolution 812 Section 5 concerning increases and decreases in the RHC as a result of
increases or decreases in the Financial Security. He had advised that the paper would need to be reviewed by
competition law counsel in the major regions. Regretfully, competition law counsel in Australia was currently
travelling but the view of Canadian and EU counsel was that the proposal that the increase in the Remittance
Holding Capacity could not exceed 25% of the FS calculation as per LFC over a rolling 12 month period would
appear to be an arbitrary cap on expanding an agent’s business even though the 25% was a potential risk
mitigation tool. He believed that the proposal might benefit from review in a Legal Working Group and in the
meantime strongly recommended its withdrawal and PAConf should address Revision No. 1 dated 16 October
2019.
M/ The member submitting the item stressed that this issue was a huge concern to airlines and this proposal
aimed at addressing a loophole in the resolution that was a risk for them all. Whilst reluctantly he could agree to
set Revision No. 2 aside and concentrate on Revisions No. 1, it was extremely important for PAConf to endorse
that proposal which would at least afford them some measure of protection.
M/ The Chairman agreed that this was a very important item. It was a shame that Revision No. 2 had to be
put to one side, as he thought that would have been a better way forward.
M/ During discussion, there was consensus that something had to be done but some carriers were
concerned that they were potentially closing one risk but opening up another.
M/ A member asked IATA Legal whether a percentage as proposed in Revision No. 2 was unacceptable or
whether there was any possibility of working around that to find a solution? If it was made clear that the intention
behind the proposal was not really a capping of sales, because an agent could request an increase in their RHC
if they had an increase in sales, but it was just to limit the increase in the RHC because of the Financial Security.
Would it be possible to find a solution or were they stuck with the proposal in Revision No. 1?
M/ Mr. Lugo agreed that there needed to be a solution to the problem. Unfortunately the solution presented
in Revision No. 2 was impacted by antitrust laws and according to IATA’s competition law counsel in Canada and
the EU, it would be arbitrary, restrictive on agents’ expanding their business and would be seen as a collective
boycott by IATA members in violation of antitrust laws. So there were indeed concerns. That being said, the
resolution as drafted did present a risk and some agents had taken advantage. The intention behind the
resolution as drafted was to give agents flexibility. Unfortunately this was not something that could be resolved
easily in a breakout session here and they would need to work very closely with international competition law
Page | 7 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
counsel to try to find a solution that would protect the airlines from unscrupulous agents and not violate
competition law.
M/ The Chairman asked whether it would be more acceptable to have a range of amounts rather than a fixed
percentage however Mr. Lugo advised that that would require more discussion with competition law counsel.
The best way forward would be to have airlines and external counsel discuss the problem. He would be happy to
arrange a joint meeting with a selection of carriers.
M/ The Chairman asked the member submitting this item whether he would feel more comfortable if he
could declare the item defeated on the understanding that within the next fortnight there would be a conference
call with PSG and external legal counsel to address this one topic to try to find a satisfactory solution more on
the lines of Revision No. 2 than Revision No. 1.
M/ The member was reluctant to postpone this because they had an opportunity to discuss it here rather
than on a conference call when, if that failed, they would be in big trouble.
M/ On a formal vote on item R37, Revision No. 1 dated 16 October 2019, no carriers were opposed but 5
carriers abstained by name – AF AI BA KL UA and the proposal was therefore adopted for expedited
effectiveness of 1 January 2020. The carrier submitting the item thanked everyone for their support and asked
whether it would be possible to have an earlier implementation.
M/ The Chairman and Mr. Popovich voiced their thanks to the member for having raised this issue and for
having put forward something that was of benefit for the whole industry. The Chairman advised he would look
into whether it would be possible to have an earlier implementation.
M/ Later in the day, after consultation, the Chairman advised that it would not be possible to implement this
prior to 1 January, however at least they had adopted something. He asked whether there was any interest in
trying to see if the proposal could be improved upon by inserting a range of percentages on the understanding
that any further changes would be implemented by mail vote but still implemented on 1 January 2020?
M/ Mr. Lugo reported that he had a proposal which he would discuss first with competition law counsel and
then come back. The Chairman asked, if it might be possible to come up with something better, Mr. Lugo could
send out an email to PSG and then they could look at arranging a conference call.
Action: Mr. Lugo
M/ The Chairman recollected that during discussion, a member had asked whether it would be possible to
have a list of those agents that had already requested a decrease in their FS amount under Resolution 812,
Section 5, for risk mitigation purposes. Mr. Rodriguez confirmed that the action had been for him and Mr. Lugo
to look at the possibility of providing some of this information. Unfortunately, due to the necessity of dealing with
another item during the break, it had not been possible to discuss this with Mr. Lugo. He asked for a little more
time to look into the matter.
Action: Mr. Rodriguez/Mr. Lugo
ITEM R38 – CHANGING REMITTANCE DATE DUE TO ADMINISTRATIVE HOLIDAY
M/ Ms. Wan introduced this paper from APJC Turkey, explaining that from time to time the Turkish
government would occasionally announce pre and post-weekdays of the religious holiday as an administrative
holiday for the public sector that were not preempted in any published calendar or announced beforehand. This
had been dealt with in the past by going through a lengthy exception process and now the APJC wanted to
Page | 8 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
formalize that arrangement through an exception in resolution, as detailed in the agenda paper. Although the
paper made reference to an exception in Resolution 818g, it would be more appropriate to have it recorded in
the newly-adopted Attachment ‘I’ to Resolution 812.
M/ On a formal vote, PAConf unanimously endorsed the proposal for expedited effectiveness of 1 January
2020.
ITEM R47 – POST-BILLING DISPUTES – PROCESS ENHANCEMENTS
M/ Ms. Manova reminded PAConf of the changes introduced in the post-billing dispute process almost two
years ago and highlighted in particular two aspects that had been identified and brought to the ADM Group for
further analysis. The first was whether the additional 7 days should only be granted upon interaction on the
resolution day, and the second was whether all document types should be available for post-billing dispute.
M/ In addition to the background information set out in the agenda paper, Ms. Manova also provided a
presentation to illustrate the two proposals being put forward. She explained that the first proposal was to
extend the application of the 7 days, from the 24th day onwards. That would not increase the total timeframe for
managing post-billing disputes. The current provisions only allowed for an additional 7 days to be granted if a
comment was provided on the 30th day. However, there were many scenarios where a comment placed even on
the 28th day may not be seen by the other party, so the proposed change took into consideration potential long
weekends and bank holidays.
M/ The second proposal was to disable the possibility of raising a post-billing dispute for Refund
transactions as the post-billing dispute model was being misunderstood and misused by users, causing
duplicate payments in cases where a post-billing dispute was closed in favour of the agent or where no
agreement had been reached between the parties. The ADM Group had undertaken an analysis of all post-billing
dispute examples over the past two years, reviewing such cases in detail and had confirmed that the present
proposal made sense.
M/ On a formal vote, PAConf unanimously adopted the proposals and the changes to resolutions 812 and
818g Attachment A as shown at Attachment A to the agenda paper, for expedited effectiveness of 1 January
2020.
Page | 9 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
OUTLINE OF CONTENTS AND STATUS OF EFFECTIVENESS
Expedited Resolutions adopted at:
Forty Second Passenger Agency Conference (PAConf/42)
22-24 October 2019
Intended Effective Date: 1 January 2020
(unless stated otherwise)
Resolution
Title
PAConf/42
Agenda Item
PAC(556)800 (except USA) Passenger Sales Agency Rules R3
PAC(546)800a (except USA) Application Form For
Accreditation as an IATA
Passenger Sales Agent
R18
PAC(556)812 (except USA) Passenger Sales Agency Rules R3, R13, R14.1,
R14.2, R16, R18,
R25, R27, R33,
R35, R37, R38, R47
PAC(556)818g(except USA) Passenger Sales Agency Rules R3, R14.3, R27,
R35, R47
PAC(556)824r (except USA) Refunds R29
PAC(556)832 (except USA)
(except 818g and 812 countries)
Reporting and Remitting
Procedures
R35
PAC(556)866 (except USA) Definitions of Terms Used in
Passenger Agency Programme
Resolutions
R20
PAC(556)896 (except USA) Alternative Transfer Method
Providers & Alternative Transfer
Methods [Transparency In
Payments Transition]
R3
Resolution 800
Page | 10 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
PASSENGER SALES AGENCY RULES (Amending)
PAC(556)800 (except USA) Expiry: Indefinite
Type: B
Amend Resolution 800 as shown below: This Resolution is applicable in the following countries and/or territories markets and regions:
Afghanistan, Algeria, Angola, Armenia, Belarus, Bhutan, Brunei Darussalam, Burundi, Cape Verde, Christmas
Island, Cocos (Keeling) Islands, Cuba, Comoros, Democratic People's Republic of Korea (DPRK), Democratic
Republic of Congo, Djibouti, Equatorial Guinea, Eritrea, Falkland Islands/Malvinas, Gambia, Guinea, Guinea-
Bissau, Indian Ocean Islands, Islamic Republic of Iran, Iraq, Israel, Laos (Peoples' Democratic Republic), Liberia,
Libya, Madagascar, Maldives, Sao Tome and Principe, Seychelles, Sierra Leone, Somalia, Tajikistan, Timor
Leste, Turkmenistan, and Uzbekistan.
Resolution 800a
Page | 11 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
APPLICATION FORM FOR ACCREDITATION AS AN IATA PASSENGER SALES AGENT (Amending)
PAC(556)800a (except USA) Expiry: Indefinite
Type: B
Amend Resolution 800a as shown below: 8.7 Please indicate the GDS with which you have signed a contract:
In absence of contract with GDS, kindly confirm you carry only NDC transactions with Airlines, and provide IATA
with one (1) letter of recommendation from an IATA Member Airline.
Resolution 812
Page | 12 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
PASSENGER SALES AGENCY RULES (Amending)
PAC(556)812 (except USA) Expiry: Indefinite
Type: B
Amend Resolution 812 as shown below:
This Resolution is applicable in the following countries market and regions:
Area 1: Anguilla, Antigua and Barbuda, Argentina, Aruba, Bahamas, Barbados, Belize, Bermuda, Bolivia, Bonaire,
Brazil, British Virgin Islands, Canada, Cayman Islands, Chile, Colombia, Costa Rica, Curacao, Dominica, Dominican
Republic, Ecuador, El Salvador, French Guyana, Grenada, Guadeloupe, Guatemala, Guyana, Haiti, Honduras,
Jamaica, Martinique, Mexico, Montserrat, Nicaragua, Panama, Paraguay, Peru, Saint Kitts and Nevis, Saint Lucia,
Saint Vincent and the Grenadines, St. Eustatius, St. Maarten (Dutch part), Saba, Suriname, Trinidad and Tobago,
Turks and Caicos Islands, Uruguay, Venezuela.
Area 2: Africa: Botswana, Central/West Africa(1), Egypt, Ethiopia, Ghana, Kenya, Lesotho, Malawi, Mauritius,
Mayotte, Morocco, Mozambique, Namibia, Nigeria, Reunion Island, Rwanda, South Africa, Sudan, Swaziland,
Tanzania, Tunisia, Uganda, Zambia, Zimbabwe.
Area 2: Europe: Albania, Andorra, Austria, Azerbaijan, Belgium, Bosnia & Herzegovina, Bulgaria, Channel Islands,
Croatia, Czech Republic, Denmark, Estonia, Finland, France, Georgia, Germany, Gibraltar, Greece, Greenland,
Hungary, Iceland, Isle of Man, Ireland, Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia
(FYROM), Malta, Moldova, Monaco, Netherlands, Norway, Poland, Portugal, Republic of Cyprus, Romania, Russian
Federation, San Marino, Serbia & Montenegro, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey, Ukraine,
United Kingdom.
Area 2: Middle East: Gulf Area(2), Jordan, Kuwait, Lebanon, Saudi Arabia, Syrian Arab Republic, Yemen.
Area 3: Bangladesh, Cambodia, Chinese Taipei, Hong Kong (SAR), India, Indonesia, Japan, Kazakhstan, Korea,
Kyrgyzstan, Macau (SAR, China), Malaysia, Mongolia, Myanmar, Nepal, Pakistan, People’s Republic of China,
Philippines, Singapore, South West Pacific, Sri Lanka, Thailand, Vietnam.
[…]
RESOLVED that:
1. The provisions of this Resolution are adopted and effective 1 March 2018, except the provisions of sections
6.15 to 6.18, which became effective 1 January 2017.
2. This Resolution will be implemented in a country or group of countries upon notification of the Agency
Administrator in accordance with the provisions of Resolution 846. Notification of the date of implementation
of this Resolution shall be given to all Members by the Agency Administrator with a minimum of 60 days’ notice.
3. The provisions of section 5.6 will be reviewed at the PAC taking place in 2019 2020, and will be subject to re-
adoption. In the event that PAC amends the Remittance Holding Capacity calculation established in Resolution
812 section 5.6, Accredited Agents will be notified of the change, at minimum, six months before the new
calculation takes effect.
Page | 13 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
4. Where this Resolution is implemented in a country or group of countries, Resolution 848 will no longer apply
in that country(ies).
5. Where Resolution 812a is implemented in a country or group of countries at a later date than this Resolution,
any provisions which refer to Resolution 812a will only become effective as of such later date.
[…]
5.5.4. Failure to Provide a Financial Security
5.5.4.1 Where the request relates to an increase in the amount of FS and IATA already holds a Financial Security
for that Agent, failure to provide the increase in the amount of the Financial Security by the deadline will result in
the Agent’s Remittance Holding Capacity being reduced by the same percentage of increase in the Financial
Security requested decreased by the difference between the requested Financial Security amount and the
Financial Security amount already held by IATA.
[…]
5.6 CASH CONDITION–REMITTANCE HOLDING CAPACITY
5.6.1 Risk Status “A” and “B”
5.6.1.1 Subject to sections 5.6.1.4, the Remittance Holding Capacity granted to the Agent having Risk Status
“A” or “B” will be determined by aggregating the amount calculated under the following formula in respect of
the Agent in each applicable country:
Remittance Holding Capacity = Total Days × Total BSP Cash Turnover 3 highest Reporting Periods × 2
Days in Reporting Period × 3
where:
“Total Days” means the number of days from the beginning of the Agent's Reporting Period to the Remittance
Date in respect of that Reporting Period(s) applicable to the Agent in the applicable country;
“Total BSP Cash Turnover 3 highest Reporting Periods” means the total cash turnover of the Agent in the
applicable country over the three highest Reporting Periods of the 12 months prior to the date the Remittance
Holding Capacity is calculated; and
5.6.1.2 For countries with individualised airline Reporting Periods, the Remittance Holding Capacity will be
calculated by aggregating the amounts calculated under the formula in section 5.6.1.1 for each individualised
frequency of Remittance, using the three highest Reporting Periods for each frequency.
5.6.1.3 Subject to the provisions of sections 5.8 and 5.9.3-5.9.5, or a change to the Agent's Risk Status, the
Remittance Holding Capacity calculated under section 5.6.1.1 will apply for a period of 12 months from the date
of calculation.
5.6.1.4 Where an Agent holding Standard Accreditation with Cash Facility is required to provide, in accordance
with applicable Local Financial Criteria, a Financial Security for an amount that is higher than the amount
Page | 14 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
calculated under the formula in section 5.6.1.1 above, the Remittance Holding Capacity granted to the Agent
will be equal to the amount of the Financial Security provided.
5.6.1.5 For the Agent having Risk Status “A”, the Remittance Holding Capacity granted will be not less than the
equivalent of USD 5,000 10,000.
5.6.1.6 For the Agent holding Multi-Country Accreditation, the Remittance Holding Capacity determined under
section 5.6.1.1 will be established, at the Agent's option, in one of the following currencies:
(a) United States Dollar (USD);
(b) Euro (EUR);
(c) Pound Sterling (GBP);
(d) Australian Dollar (AUD);
(e) Singapore Dollar (SGD),
by conversion of each amount to be aggregated under section 5.6.1.1 into the selected currency.
5.6.1.7 In the event that the Remittance Frequency in a market changes and/or an Agent voluntarily elects to
remit on a different frequency, the Agent's Remittance Holding Capacity will be recalculated taking into
consideration the revised Remittance Frequency.
5.6.2 Agent with Risk Status “C”
5.6.2.1 The Remittance Holding Capacity granted to the Agent having Risk Status “C” will be equal to the
amount of the Financial Security provided by the Agent.
5.6.2.2 For the Agent holding Multi-Country Accreditation, the Remittance Holding Capacity will be established,
at the Agent's option, in one of the currencies set out in section 5.6.1.5.
5.6.3 CHINA ONLY The Remittance Holding Capacity granted to the Agent, regardless of its Risk Status, will be
at all times equal to 90% of the total Financial Security amount provided by the Agent.
5.6.4 CHINA ONLY For BSP China Domestic Agents, the Financial Security will be calculated as per provisions
of the Local Financial Security Criteria.
[…]
5.9.3 Reaching or Exceeding the Remittance Holding Capacity
5.9.3.1 If All Amounts Owing are, at any time, equal to or higher than the Remittance Holding Capacity, the Cash
Payment Method will be removed from the Agent, (but other authorized Payment Methods, in accordance with
section 2.1.2.1, will continue to be available), until the Agent has either:
(a) remitted in advance of, or on, the Remittance Date, to reduce All Amounts Owing below its Remittance Holding
Capacity; or
(b) provided an additional Financial Security amount, in which case its Remittance Holding Capacity will be
increased:
(i) subject to section 5.9.3.1(b)(ii), by the same percentage of amount as the additional Financial Security
amount provided; or
Page | 15 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
(ii) in the case of the Agent holding Standard Accreditation with Cash Facility, by such other amount as
determined in accordance with the applicable Local Financial Criteria.
5.9.4 Management of Remittance Holding Capacity Where All Amounts Owing Are Less Than the Remittance
Holding Capacity
5.9.4.1 If All Amounts Owing are, at any time, lower than the Remittance Holding Capacity, the Agent may, subject
to any minimum amount established in the applicable Local Financial Criteria or Multi-Country Financial Criteria,
reduce the amount of the Financial Security provided in accordance with sections 5.5, 5.9.3.1(b) or any other
section of this Resolution, in such case the Remittance Holding Capacity will be decreased:
(a) Subject to section 5.9.4.1(b), by the same percentage of decrease in amount as the reduction of the
Financial Security amount ; or
(b) In the case of the Agent holding Standard Accreditation with Cash Facility, by such other amount as
determined in accordance with the applicable Local Financial Criteria;
provided that All Amounts Owing do not equal or exceed the new Remittance Holding Capacity.
5.9.4.2 Notwithstanding any other provision under this section 5, the Agent may at any time increase its
Remittance Holding Capacity by either:
1. providing IATA with a Financial Security for a higher amount, or,
2. for the Agent with Risk Status ‘A’ in a market with no minimum Financial Security requirement, providing a new
Financial Security.
The Remittance Holding Capacity will be increased:
(a) by the same percentage of amount as the new or additional Financial Security amount provided or
subject to section 5.9.3.1 (b), or,
(b) in the case of the Agent holding Standard Accreditation with Cash Facility, by such other amount as
determined in accordance with the applicable Local Financial Criteria.
[…]
6.12 REMITTANCE OF AMOUNTS DUE
6.12.1 This section 6.12 governs the remittance to IATA of All Amounts Owing by the Agent who is in Payment
Default.
6.12.2 If the Agent who is in Payment Default is able to demonstrate to the satisfaction of IATA prior to the
effective date of termination specified in the Notice of Payment Default issued in accordance with section
6.9.2.1(b) that:
(a) All Amounts Owing, if any, have been remitted to IATA, or
(b) at least 20% of All Amounts Owing have been remitted and a firm schedule for repayment by instalments
within twelve months of the balance plus interest at the official (prime) bank rate plus one two percent has been
agreed between IATA and the Agent; or
(c) an alternative repayment schedule and conditions, initiated by the Agent, have been agreed between the
Agent and IATA on the basis that:
Page | 16 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
(i) the Agent has remitted not less than 20% of All Amounts Owing and can demonstrate to IATA's satisfaction
that it has taken all steps possible to remit at least 50% of All Amounts Owing; and
(ii) a firm schedule for repayment by instalments over an agreed period of no more than twelve months; and
(iii) the repayments will cover the balance plus interest at the official (prime) bank rate plus one two percent or,
in any event, will provide for payment of interest at a rate similar to that set out in Subparagraph 6.12.2(b),
IATA will notify the BSP Airlines accordingly and section 6.11.3.2 will apply in respect of that Notice of Payment
Default.
[…]
6.5 REMITTANCE
6.5.1 The provisions of this section 6.5 govern the general remittance procedures and frequencies for the
remittance of Billings by the Agent.
6.5.1.1 Please note that Monthly Remittance Frequency will be removed effective 31 December 2019 and all
relevant paragraphs in this Manual will be rescinded effective 1 January 2020. APJCs are required to meet and
determine a precise date and plan to transit into a more frequent Remittance Frequency no later than 30 June
2019, with an effectiveness date no later than 31 December 2019.
In the countries where Monthly Remittance Frequency is available it is only effective until 31 December 2019
except that for South Africa, Botswana and Morocco where the effective date is 30 April 2020.
[…]
6.5.3 Frequency of Remittance
6.5.3.1 The Conference will establish the standard Remittance Frequency and, if considered appropriate, any
additional more frequent Remittance Frequencies for Agent remittances in each country. The relevant
Remittance Date will be communicated to all Agents participating in each BSP.
6.5.3.2 IATA will publish the The Remittance Frequencies and any exceptions as adopted by the Conference in
accordance to 6.5.3.1 applicable to each country are reflected in Attachment ‘I’ of this Resolution on its website.
[…]
6.6.7 Disputed Agency Debit Memo
The provisions of this paragraph should be read in conjunction with the provisions concerning ADMs as
provided in Resolution 850m.
Page | 17 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
6.6.7.1 an Agent may for reason dispute an ADM, except for an ADM issued as a means to collect credit card
chargebacks in accordance to Resolution 890 Section 4.7,
6.6.7.2 an Agent shall have a maximum of 15 days in which to review and dispute an ADM prior to its submission
to BSP for inclusion in the Billing,
6.6.7.3 when an ADM is disputed prior to it being submitted to the BSP for processing, it will be recorded as
disputed, and will not be included in the Billing,
6.6.7.4 if an Agent disputes an ADM within the minimum dispute period it shall be suspended from the BSP
process and settlement of the dispute will be for resolution between the Agent and Airline concerned:
(a) in the event an Agent disputes an ADM and, after agreement between the Airline and the Agent, it is
determined that the purpose of that ADM was correct, the Airline will advise the Agent and the BSP accordingly
and the ADM as originally submitted will be processed. All subsequent disputes of such ADM must be dealt with
according to the process as described in this Resolution 812, Section 6.10.
(b) if as a result of an Agent dispute it is determined after agreement between the Airline and the Agent that the
ADM needs adjustment, the Airline will submit to the Agent and the BSP the adjusted ADM, in the form of a new
ADM, in which case only the new ADM shall be processed,
(c) all disputes are to be settled by the Airline within 60 days of receipt. Once the status of the ADM dispute has
been set, notwithstanding if the 60 days have been reached or not, all subsequent disputes of such ADM must
be dealt with according to the process as described in this Resolution 812, Section 6.10,
6.6.7.5 an ADM that has been included in the BSP Billing will be processed for payment. All subsequent
disputes of such ADM, must be dealt with according to the process as described in this Resolution 812,
Section 6.10,
6.6.7.6 If after 60 days of receipt of a disputed ADM by an Airline the dispute has not been settled resolved,
despite consultation between the Airline and the Agent, such ADM will no longer be suspended and will be
withdrawn from the BSP process,
6.6.7.7 Such ADM dispute is now for bilateral resolution between the Airline and the Agent.
6.6.7.8 No more than one ADM must be raised in relation to one original ticket issuance. When more than one
ADM is raised in relation to the same ticket it must be specified that it is for a different adjustment than
previous.
[…]
6.9.4 Encashment of Bank Guarantee, Insurance Bond or Other Form of Guarantee (India, Indonesia and
Pakistan only)
6.9.4.1 In the event that the Agent's BSP bank guarantee, insurance bond or any other form of guarantee, if
applicable is insufficient to provide a full settlement to each of the BSP participating Airlines concerned listed in
Page | 18 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
the Billing which has been subject to the Agent's default, each such BSP Airline shall be provided with a
prorated amount of the bank guarantee, insurance bond or other form of guarantee in proportion to its
percentage share in Billing up to the date when the full amount of the bank guarantee, insurance bond or other
form of guarantee was exceeded. In the event that the Agent has provided a separate bank guarantee,
insurance bond or any other form of guarantee in favour of a specific BSP Airline for Accountable Transactions,
such BSP Airline shall not be entitled to any payment under the Agent's BSP bank guarantee, insurance bond or
other form of guarantee until all outstanding indebtedness of the Agent to other BSP Airlines shall be
discharged. In the event that the Agent owned by a Member, where the Member or Member's parent company
holds greater than 50% of the equity of the Agent or the Agent's parent company, is declared in Default, such
member shall not be entitled to any payment under the Agent's BSP bank guarantee, insurance bond or other
form of guarantee.
[…]
6.10.1 DISPUTES (Except Argentina and Russian Federation)
6.10.1.1 In order to be dealt with through BSP, disputes raised by the Agent must:
(a) be registered with IATA via BSPlink (ASD in China);
(b) relate to a specified amount as part of a Billing;
(c) state a substantive reason for the dispute supported by written evidence of that dispute;
(d) be raised by the Agent within 12 months of the date of the Accountable Transaction;
(e) be added to the daily dispute file.
(f) be unrelated to a chargeback issued by means of an ADM pursuant to Resolution 890 subsection 4.7.
(g) be unrelated to a refund transaction.
6.10.1.2 All validly disputed amounts will continue to form part of the Billing and the Agent must remit the
disputed amount to the BSP on the Remittance Date notwithstanding the existence of the dispute.
6.10.1.3 All disputed amounts paid by the Agent will be held by IATA for a period of 30 days or until the dispute
is resolved, whichever is earlier.
6.10.1.4 For Reported Sales markets, any disputed amount received from the Agent and paid to a BSP Airline
will be deducted from the BSP settlement of that BSP Airline in the following Reporting Period and held for a
period of 30 days or until the dispute is resolved, whichever is earlier.
6.10.1.5 All disputes must be resolved in BSPlink (ASD in China) between the Airline and the Agent within 30
days with a maximum of two responses per party, otherwise the dispute will be for bilateral resolution between
the Airline and the Agent outside of the BSP and IATA will pay the disputed amount held to the Agent or the
Airline as applicable in accordance with section 6.10.7 6.10.1.7. If the Agent or Airline responds to a dispute on
the 30th day any day from day 24th onwards, the Airline or Agent will have an additional 7 days to respond.
[…]
Amend Resolution 812 Attachment ‘B’ as shown below:
7.5 Please indicate the GDS(s) with which you have signed a contract:
Page | 19 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
In absence of contract with GDS, kindly confirm you carry only NDC transactions with Airlines, and provide IATA
with one (1) letter of recommendation from an IATA Member Airline.
Add Attachment ‘I’ to Resolution 812 as shown below:
Operation Frequency Number of days in a
sales period
End of Sales
Period to
Remittance
Date
Note:
Albania Four times per
Month Refer to BSP Calendar 15
Antigua Four times per
Month Refer to BSP Calendar 10
Argentina Weekly 7 10
Aruba Four times per
Month Refer to BSP Calendar 10
Australia Weekly 7 8
Remittances shall be made so
as to reach the Clearing Bank
not later than its close of
business on the 8th day from
the Reporting Date.
Austria Twice per month 15 15
Austria Four times per
Month Refer to BSP Calendar 15
Azerbaijan Four times per
Month Refer to BSP Calendar 10
Bahamas Four times per
Month Refer to BSP Calendar 10
Bahrain Twice per month 15 15
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Bahrain Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Bangladesh Twice per month Refer to BSP Calendar Refer to BSP
Calendar
Barbados Four times per
Month Refer to BSP Calendar 10
Belgium Twice per month 15 7
PAConf/41 adopted that 2
times per month frequency will
be removed effective 1 April
2020.
Belgium Four times per
Month Refer to BSP Calendar 7
Belize Four times per
Month Refer to BSP Calendar 5
Benin Twice per month 15 17
Page | 20 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Bermuda Weekly 7 15
Bolivia (BOB/USD) Four times per
Month Refer to BSP Calendar 5
Bonaire Four times per
Month Refer to BSP Calendar 10
Bosnia and
Herzegovina
Four times per
Month Refer to BSP Calendar 15
Botswana Monthly 30 15
Monthly Remittance Frequency
will be available until 30 April
2020
Botswana Twice per month 15 15
Botswana Four times per
Month Refer to BSP Calendar 7
Brazil 3 Times a Month Refer to BSP Calendar 13
Brazil Four times per
Month Refer to BSP Calendar 10
Bulgaria Four times per
Month Refer to BSP Calendar 10
Burkina Faso Twice per month 15 17
British Virgin
Islands
Four times per
Month Refer to BSP Calendar 10
Cambodia Twice per month Refer to BSP Calendar Refer to BSP
Calendar
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Cameroon Twice per month 15 17
Canada Weekly 7 10
Cayman Islands Four times per
Month Refer to BSP Calendar 10
Chad Twice per month 15 17
Chile (CLP/USD) Weekly 7 5
China Every 3 days 3 5
If the remittance frequency so
established exceeds four times
per month, the remittance date
and settlement date can be
adjusted forward or backward
based on the need of the
market due to the updated
public holidays
Chinese Taipei Four times per
Month Refer to BSP Calendar 8
Colombia Four times per
Month Refer to BSP Calendar 5
Congo Twice per month 15 17
Costa Rica Four times per
Month Refer to BSP Calendar 5
Page | 21 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Croatia Four times per
Month Refer to BSP Calendar 15
Curacao Four times per
Month Refer to BSP Calendar 10
Cyprus Twice per month 15 15
Cyprus Four times per
Month Refer to BSP Calendar 7
Czech Republic Four times per
Month Refer to BSP Calendar 10
Denmark Four times per
Month Refer to BSP Calendar 15
Dominica Four times per
Month Refer to BSP Calendar 10
Dominican Republic Four times per
Month Refer to BSP Calendar 10
Ecuador Four times per
Month Refer to BSP Calendar 10
Egypt Twice per month 15 15
El Salvador Four times per
Month Refer to BSP Calendar 5
Estonia Four times per
Month Refer to BSP Calendar 7
If the Remittance Frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
calendar day from the
Reporting Date.
Ethiopia Twice per month 15 15
Ethiopia Four times per
Month Refer to BSP Calendar 7
Fiji Weekly 7 15
If the remittance frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 15th
day from the Reporting Date.
Finland Four times per
Month Refer to BSP Calendar 15
France Twice per month 15 15
France Four times per
Month Refer to BSP Calendar 15
French Polynesia Weekly 7 15
If the remittance frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 15th
day from the Reporting Date.
Gabon Twice per month 15 17
Page | 22 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Georgia Four times per
Month Refer to BSP Calendar 7
Germany Twice per month 15 15
Germany Four times per
Month Refer to BSP Calendar 15
Germany Daily 1 3
Ghana Twice per month 15 15
Ghana Four times per
Month Refer to BSP Calendar 7
Greece Twice per month 15 16
Greece Four times per
Month 15 16
Grenada Four times per
Month Refer to BSP Calendar 10
Guam Weekly 7 15
Guatemala Four times per
Month Refer to BSP Calendar 5
Guyana (USD/GYD) Four times per
Month Refer to BSP Calendar 10
Haiti (USD/HTG) Four times per
Month Refer to BSP Calendar 10
Honduras Four times per
Month Refer to BSP Calendar 5
Hong Kong Four times per
Month Refer to BSP Calendar 8
Hungary Four times per
Month Refer to BSP Calendar 15
Iceland Four times per
Month Refer to BSP Calendar 15
India Four times per
Month Refer to BSP Calendar 9
Remittances shall be made so
as to reach the Clearing Bank
not later than its close of
business on the 9th calendar
day from the Reporting Date
and the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
If the Clearing Bank is closed
for business on the required
“Remittance Date” then the
Agent shall make the
Remittance so as to reach the
Clearing bank on the first
subsequent day when the
Clearing bank is open for
business.
Four holidays during the year
will not be scheduled as
Remittance dates in the BSP
Remittance Calendar
irrespective of whether or not
Page | 23 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
they are national holidays
when the electronic payment
grid of the Reserve Bank of
India is closed. Those holidays
are as follows: 1. Diwali. (Date
varies each year) 2. Dussehra.
(Date varies each year) 3. Holi.
(Date varies each year) 4.
Christmas. (December 25)
Indonesia
DOMESTIC
Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Indonesia
INTERNATIONAL
Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Ireland Twice per month 15 16
Ireland Four times per
Month Refer to BSP Calendar 8
Italy Twice per month 15 15
MV item A318 adopted by
Conference to introduce twice
per month Remittance
Frequency in Italy effective 1
Jan 2020
Italy Four times per
Month Refer to BSP Calendar 7
Ivory Coast Twice per month 15 17
Jamaica Four times per
Month Refer to BSP Calendar 10
Japan Four times per
Month Refer to BSP Calendar 8
Recurring dates 29 December
through 3 January, considered
as business holidays, must not
have remittance scheduled
during this window.
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
Page | 24 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
close of business on the 8th
calendar day from the
Reporting Date.
Jordan Twice per month 15 15
If the Remittance Frequency so
established is twice monthly,
Remittances shall be made so
as to reach the Clearing Bank
not later than its close of
business on the last day of the
month in respect of Billings
covering the first 15 days of
the month and the 15th day of
the following month, in respect
of Billings covering the period
from the 16th to the last day of
the month; provided that the
method of payment used
assures that the funds are in
the Clearing Bank for good
value on the day of remittance
in time for the settlement to be
made into the BSP Airlines'
account on the date so
established locally
Jordan Four times per
Month Refer to BSP Calendar 7
Kazakhstan Four times per
Month Refer to BSP Calendar 6
Kenya (USD/KES) Twice per month 15 17
Kenya (USD/KES) Four times per
Month Refer to BSP Calendar 7
Korea 6 Times a Month 5 5
Kosovo Four times per
Month Refer to BSP Calendar 15
Kuwait Four times per
Month Refer to BSP Calendar 7
Latvia Four times per
Month Refer to BSP Calendar 7
If the Remittance Frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
calendar day from the
Reporting Date.
Lebanon Twice per month 15 15
Lebanon Four times per
Month Refer to BSP Calendar 7
Page | 25 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Lithuania Four times per
Month Refer to BSP Calendar 7
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
calendar day from the
Reporting Date.
Macau Four times per
Month Refer to BSP Calendar 8
Macedonia Four times per
Month Refer to BSP Calendar 15
Malawi Twice per month 15 15
Malawi Four times per
Month Refer to BSP Calendar 7
Malaysia Weekly 7 10
If the Remittance Frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 10th
day from the Reporting Date.
Mali Twice per month 15 17
Malta Twice per month 15 15
Mauritania Twice per month 15 17
Mauritius Twice per month 15 16
Mexico Four times per
Month Refer to BSP Calendar 10
Micronesia Weekly 7 15
Mongolia Weekly 7 8
Montenegro Four times per
Month Refer to BSP Calendar 15
Montserrat Four times per
Month Refer to BSP Calendar 10
Morocco Monthly 30 16
Monthly Remittance Frequency
will be available until 30 April
2020
Morocco Twice per month 15 16
Mozambique Twice per month 15 15
Mozambique Four times per
Month Refer to BSP Calendar 7
Nepal (USD/NPR) Four times per
Month Refer to BSP Calendar 14
Remittances shall be made so
as to reach the Clearing Bank
no later than its close of
business on the 14th day from
the Reporting Date.
Netherlands Twice per month 15 10
Netherlands Four times per
Month Refer to BSP Calendar 10
Page | 26 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
New Caledonia Weekly 7 15
If the remittance frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 15th
day from the Reporting Date.
New Zealand Weekly 7 6
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on 6th day
from the Billing Distribution
date.
Nicaragua Four times per
Month Refer to BSP Calendar 5
Niger Twice per month 15 17
Nigeria (USD/NGN) Twice per month 15 15
Nigeria (USD/NGN) Four times per
Month Refer to BSP Calendar 7
Norway Four times per
Month Refer to BSP Calendar 15
Oman Twice per month 15 15
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Oman Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Pakistan Twice per month 15 15
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
day from the Reporting Date.
Panama Four times per
Month Refer to BSP Calendar 5
Papua New Guinea Weekly 7 15
If the remittance frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 15th
day from the Reporting Date.
Paraguay(USD/PYG) Four times per
Month Refer to BSP Calendar 10
Page | 27 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Peru Four times per
Month Refer to BSP Calendar 7
Philippines
(USD/PHP)
Four times per
Month Refer to BSP Calendar 7
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
day from the Reporting Date.
Poland Four times per
Month Refer to BSP Calendar 15
Portugal Four times per
Month Refer to BSP Calendar 15
Qatar Twice per month 15 15
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Qatar Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Romania (EUR/RON) Four times per
Month Refer to BSP Calendar 15
Russian Federation Four times per
Month Refer to BSP Calendar 7
Rwanda (USD/RWF) Twice per month 15 17
Rwanda (USD/RWF) Four times per
Month Refer to BSP Calendar 7
Saint Kitts Four times per
Month Refer to BSP Calendar 10
Saint Lucia Four times per
Month Refer to BSP Calendar 10
Saint Marteen
(USD/ANG)
Four times per
Month Refer to BSP Calendar 10
Saint Vincent Four times per
Month Refer to BSP Calendar 10
Samoa Weekly 7 15
If the remittance frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 15th
day from the Reporting Date.
Page | 28 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Saudi Arabia Four times per
Month Refer to BSP Calendar 7
When Remittance date falls on
the working day after Eid and
Hajj holidays, it shall be
postponed to the second
working day after such
holidays.
Senegal Twice per month 15 17
Serbia Four times per
Month Refer to BSP Calendar 15
Singapore Four times per
Month Refer to BSP Calendar 7
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
day from the Reporting Date.
Slovakia Four times per
Month Refer to BSP Calendar 10
Slovenia Four times per
Month Refer to BSP Calendar 15
South Africa Monthly 30 15
Monthly Remittance Frequency
will be available until 30 April
2020
South Africa Twice per month 15 15
South Africa Four times per
Month Refer to BSP Calendar 7
Spain 3 Times a Month 10 10
Sri Lanka Four times per
Month Refer to BSP Calendar 7
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
day from the Reporting Date.
Sudan Four times per
Month Refer to BSP Calendar 7
Suriname
(USD/EUR)
Four times per
Month Refer to BSP Calendar 10
Sweden Four times per
Month Refer to BSP Calendar 15
Switzerland Twice per month 15 15
Switzerland Four times per
Month Refer to BSP Calendar 15
Switzerland Daily 1 3
Tanzania (USD/TZS) Twice per month 15 18
Tanzania (USD/TZS) Four times per
Month Refer to BSP Calendar 10
Page | 29 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
Thailand Four times per
Month Refer to BSP Calendar 7
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
day from the Reporting Date.
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Togo Twice per month 15 17
Tonga Weekly 7 15
If the remittance frequency so
established is four times
monthly, Remittances must be
made so as to reach the
Clearing Bank not later than its
close of business on the 15th
day from the Reporting Date.
Trinidad & Tobago Four times per
Month Refer to BSP Calendar 10
Tunisia Monthly 30 15
Tunisia Twice per month 15 15
Turkey Twice per month 15 16
If Remittance date falls on any
weekday, which is announced
as administrative holiday by
government, the Remittance
date will be postponed to the
first working day after the
administrative holiday
Turks-Caicos Four times per
Month Refer to BSP Calendar 10
Uganda Twice per month 15 15
Uganda Four times per
Month Refer to BSP Calendar 7
Ukraine Four times per
Month Refer to BSP Calendar 7
Ukraine Every 3 days 3 7
United Arab
Emirates Twice per month 15 15
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
United Arab
Emirates
Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
United Kingdom Twice per month 15 15
Page | 30 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
United Kingdom Four times per
Month Refer to BSP Calendar 8
Uruguay Four times per
Month Refer to BSP Calendar 10
Venezuela Four times per
Month Refer to BSP Calendar 10
Vietnam Four times per
Month Refer to BSP Calendar 7
If the remittance frequency so
established is four times
monthly, Remittances shall be
made so as to reach the
Clearing Bank not later than its
close of business on the 7th
day from the Reporting Date.
Zambia (USD/ZMW) Twice per month 15 15
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Zambia (USD) Four times per
Month Refer to BSP Calendar 7
Remittances must be made so
that the method of payment
used assures that the funds
are in the Clearing Bank for
good value on the day of
remittance.
Zimbabwe Four times per
Month Refer to BSP Calendar 7
Resolution 818g
Page | 31 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
PASSENGER SALES AGENCY RULES (Amending)
PAC(556)818g (except USA) Expiry: Indefinite
Type: B
Amend Resolution 818g as shown below: This Resolution is applicable in the following countries market and regions:
Area 1: Anguilla, Antigua and Barbuda, Argentina, Aruba, Bahamas, Barbados, Belize, Bermuda, Bolivia, Bonaire,
Brazil, British Virgin Islands, Canada, Cayman Islands, Chile, Colombia, Costa Rica, Curacao, Dominica,
Dominican Republic, Ecuador, El Salvador, French Guyana, Grenada, Guadeloupe, Guatemala, Guyana, Haiti,
Honduras, Jamaica, Martinique, Mexico, Montserrat, Nicaragua, Panama, Paraguay, Peru, Saint Kitts and Nevis,
Saint Lucia, Saint Vincent and the Grenadines, St. Eustatius, St. Maarten (Dutch part), Saba, Suriname, Trinidad
and Tobago, Turks and Caicos Islands, Uruguay, Venezuela.
Area 2–Africa: Botswana, Central/West Africa(1), Egypt, Ethiopia, Ghana, Kenya, Lesotho, Malawi, Mauritius,
Mayotte, Morocco, Mozambique, Namibia, Nigeria, Reunion Island, Rwanda, South Africa, Sudan, Swaziland,
Tanzania, Tunisia, Uganda, Zambia, Zimbabwe.
Area 2–Europe: Albania, Andorra, Austria, Azerbaijan, Belgium, Bosnia & Herzegovina, Bulgaria, Channel Islands,
Croatia, Czech Republic, Denmark, Estonia, Finland, France, Georgia, Germany, Gibraltar, Greece, Greenland,
Hungary, Iceland, Ireland, Isle of Man, Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia
(FYROM), Malta, Moldova, Monaco, Netherlands, Norway, Poland, Portugal, Republic of Cyprus, Romania,
Russian Federation, San Marino, Serbia & Montenegro, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey,
Ukraine, United Kingdom.
Area 2–Middle East: Gulf Area, Jordan, Kuwait, Lebanon, Saudi Arabia, Syrian Arab Republic, Yemen.
Area 3: Bangladesh, Cambodia, Chinese Taipei, Hong Kong (SAR), India, Indonesia, Japan, Kazakhstan, Korea,
Kyrgyzstan, Macau (SAR, China), Malaysia, Mongolia, Nepal, Pakistan, People's Republic of China, Philippines,
Singapore, South West Pacific, Sri Lanka, Thailand, Vietnam.
[…]
2.2 SETTLEMENT OF AMOUNTS DUE
The provisions of this Paragraph govern the settlement of monies due by an Agent declared in Default.
2.2.1 when an Agent declared in Default is able to demonstrate to the Agency Administrator prior to the
termination date specified in his notice of termination that:
(i) either all outstanding amounts, if any, have been settled, or
(ii) at least 50% of the outstanding amount has been settled and a firm schedule for repayment by instalments
within six months of the balance plus interest at the official (prime) bank rate plus one two percent has been
agreed between the Agency Administrator and the Agent, or
Page | 32 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
(iii) an alternative repayment schedule and conditions have been agreed between the Agent and IATA on the
basis that;
(a) the Agent has remitted not less than 20% of All Amounts Owing and can demonstrate to IATA's satisfaction
that it has taken all steps possible to remit at least 50% of All Amounts Owing; and
(b) a firm schedule for repayment by instalments has been agreed between IATA and the Agent over an agreed
period of no more than 12 months; and
(c) the repayments will cover the balance plus interest at the official (prime) bank rate plus one two percent, or
in any event will provide for payment of interest at a rate similar to that set out in the provisions of Resolution
818g.
2.2.2 an alternative repayment schedule and conditions have been agreed between the Agent and either the
Agency Administrator or IATA, upon unanimous agreement of the BSP Airlines to whom the outstanding
amount is due, a fraction of such amount has been settled and a firm schedule for repayment by instalments
over an agreed period of the balance plus interest at the official (prime) bank rate plus one two percent has
been agreed between the Agency Administrator and the Agent; such alternative repayment schedule shall
extend over no more than 12 months and, in any event, shall provide for payment of interest at a rate similar to
that set out in Subparagraph 2.2.1(ii)
[…]
Amend Resolution 818g Attachment ‘A’ as shown below:
1.6.2 Frequency of Remittance
The Conference will establish the standard frequency of Agents' Remittances under such BSP. The Remittance
Date will be communicated to all Agents participating in each BSP.
Please note that Monthly Remittance Frequency will be removed effective 31 December 2019 and all relevant
paragraphs in this Manual will be rescinded effective 1 January 2020. APJCs are required to meet and
determine a precise date and plan to transit into a more frequent Remittance Frequency no later than 30 June
2019, with an effectiveness date no later than 31 December 2019
With the exception of Tunisia in the countries where Monthly Remittance Frequency is available, it is only
effective until 31 December 2019 and for Morocco it is effective until 30 April 2020
[…]
1.7.9 Disputed Agency Debit Memo
The provisions of this paragraph should be read in conjunction with the provisions concerning ADMs as
provided in Resolution 850m.
1.7.9.1 an Agent may for reason dispute an ADM,
1.7.9.2 an Agent shall have a maximum of 15 days in which to review and dispute an ADM prior to its submission
to BSP for inclusion in the Billing,
Page | 33 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
1.7.9.3 when an ADM is disputed prior to it being submitted to the BSP for processing, it will be recorded as
disputed, and will not be included in the Billing,
1.7.9.4 if an Agent disputes an ADM within the minimum dispute period it shall be suspended from the BSP
process and settlement of the dispute will be for resolution between the Agent and Airline concerned:
1.7.9.4(i) in the event an Agent disputes an ADM and, after agreement between the Airline and the Agent, it is
determined that the purpose of that ADM was correct, the Airline will advise the Agent and the BSP accordingly
and the ADM as originally submitted will be processed. All subsequent disputes of such ADM must be dealt with
according to the process as described in this Resolution 818g, Attachment ‘A’, Section 1.11.
1.7.9.4(ii) if as a result of an Agent dispute it is determined after agreement between the Airline and the Agent
that the ADM needs adjustment, the Airline will submit to the Agent and the BSP the adjusted ADM, in the form
of a new ADM, in which case only the new ADM shall be processed,
1.7.9.4(iii) all disputes are to be settled by the Airline within 60 days of receipt. Once the status of the ADM
dispute has been set, notwithstanding if the 60 days have been reached or not, all subsequent disputes of such
ADM must be dealt with according to the process as described in this Resolution 818g, Attachment ‘A’, Section
1.11.
1.7.9.5 an ADM that has been included in the BSP Billing will be processed for payment. All subsequent
disputes of such ADM must be dealt with according to the process as described in this Resolution 818g,
Attachment ‘A’, Section 1.11,
1.7.9.6 If after 60 days of receipt of a disputed ADM the dispute has not been settled resolved, despite
consultation between the Airline and the Agent, such ADM will no longer be suspended and will be withdrawn
from the BSP process,
1.7.9.7 Such ADM dispute is now for bilateral resolution between the Airline and the Agent.
1.7.9.8 No more than one ADM must be raised in relation to one original ticket issuance. When more than one
ADM is raised in relation to the same ticket it must be specified that it is for a different adjustment than
previous.
[…]
1.11 DISPUTES
1.11.1 Disputes (Except Argentina and Russian Federation)
1.11.1.1 In order to be dealt with through the BSP, disputes raised by the Agent must:
(a) be registered with IATA via BSPlink (ASD in China);
(b) relate to a specified amount as part of a Billing;
(c) state a substantive reason for the dispute supported by written evidence of that dispute;
(d) be raised by the Agent within 12 months of the date of the Accountable Transaction;
(e) be added to the daily dispute file.
(f) be unrelated to a chargeback issued by means of an ADM pursuant to Resolution 890 Subsection 4.7.
(g) be unrelated to a refund transaction.
Page | 34 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
1.11.1.2 All validly disputed amounts will continue to form part of the Billing and the Agent must remit the
disputed amount to the BSP on the Remittance Date notwithstanding the existence of the dispute.
1.11.1.3 All disputed amounts paid by the Agent will be held by IATA for a period of 30 days or until the dispute
is resolved, whichever is earlier.
1.11.1.4 For Reported Sales markets, any disputed amount received from the Agent and paid to a BSP Airline
will be deducted from the BSP settlement of that BSP Airline in the following Reporting Period and held for a
period of 30 days or until the dispute is resolved, whichever is earlier.
1.11.1.5 All disputes must be resolved in BSPlink (ASD in China) between the Airline and the Agent within 30
days with a maximum of two responses per party, otherwise the dispute will be for bilateral resolution between
the Airline and the Agent outside of the BSP and IATA will pay the disputed amount held to the Agent or the
Airline as applicable in accordance with section 1.11.1.7. If the Agent or Airline responds to a dispute on the
30th day any day from day 24th onwards, the Airline or Agent will have an additional 7 days to respond.
1.11.1.6 Each agreement or disagreement with the dispute must be registered by the Airline or the Agent, as
applicable, in BSPlink (ASD in China), and each disagreement must be accompanied by a substantive reason for
the disagreement supported by written evidence.
1.11.1.7 Disputed amounts held by IATA will be paid as follows:
(a) Where the Airline agrees with the dispute raised by the Agent, to the Agent.
(b) Where the Airline disagrees with the dispute, the Airline must state a substantive reason for the
disagreement supported by written evidence. If the Agent agrees with this position, the disputed amount will be
paid to the Airline. Otherwise, the disputed amount will be remitted to the Agent, without prejudice to the right
of the Airline to claim the disputed amount from the Agent outside of the BSP.
(c) Where no response is received from the Airline within 30 days, the dispute is deemed settled in favour of the
Agent and the disputed amount will be paid to the Agent.
Resolution 824r
Page | 35 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
REFUNDS (Amending)
PAC(556)824r (except USA) Expiry: Indefinite
Type: B
Amend Resolution 824r as shown below: Section 1—CONDITIONS
Agents shall only refund Traffic Documents issued by such Agent and must observe the original issuance of a
Traffic Document to establish the conditions for refund. In principle Traffic Documents will be refunded using
the ticketing authority of the same Airline, in the same currency and in the same form of payment it has been
originally issued. When a ticket originally issued by an Agent has been exchanged/reissued by an Airline on
which the Traffic Document was originally issued on, it may subsequently be refunded by the Agent.
1.1 if the amount of refund does not differ from the Traffic Document being refunded, such refunds should be
returned to the same form of payment with which the original Traffic Document was paid. For payments made
by multiple forms of payment, it shall be processed in the same amounts to each respective form of payment.
1.2 if the amount of refund differs from the Traffic Document being refunded, such refunds must be returned
to the same forms of payment with which the Traffic Document being refunded was paid, subject to Airline's
instructions.
Resolution 832
Page | 36 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
REPORTING AND REMITTING PROCEDURES (Amending)
PAC(556)832 (except USA) Expiry: Indefinite
Type: B
(except 818g and 812 countries)
Amend Resolution 832 as shown below: 3.2 SETTLEMENT OF AMOUNTS DUE
The provisions of this Paragraph govern the settlement of monies due by an Agent declared in Default.
3.2.1 when an Agent declared in Default is able to demonstrate to the Agency Administrator prior to the
termination date specified in his notice of termination that:
(i) either all outstanding amounts, if any, have been settled, or
(ii) at least 50% of the outstanding amount has been settled and a firm schedule for repayment by installments
within six months of the balance plus interest at the official (prime) bank rate plus one two percent has been
agreed between the Agency Administrator and the Agent;
(iii) an alternative repayment schedule and conditions have been agreed between the Agent and either the
Agency Administrator or IATA, a fraction of such amount has been settled and a firm schedule for repayment
by instalments over an agreed period of the balance plus interest at the official (prime) bank rate plus one two
percent has been agreed between the Agency Administrator and the Agent; such alternative repayment
schedule shall extend over no more than 12 months;
Resolution 866
Page | 37 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
DEFINITIONS OF TERMS USED IN PASSENGER AGENCY PROGRAMME RESOLUTIONS (Amending)
PAC(556)866 (except USA) Expiry: Indefinite
Type: B
Amend Resolution 866 as shown below: BILLING means a billing to Agents, according to data reported by the Ticketing System Provider or an Order
Management System, incorporating all Accountable Transactions for the Billing Period.
ORDER MANAGEMENT SYSTEM (OMS) – An Airline database and/or application that creates and manages an
Airline’s Orders, tracks delivery of all services found within an Order and communicates to all appropriate
internal and external suppliers, applications and accounting systems of the Airline.
Resolution 896
Page | 38 Filing Period (12-31 December 2019)
Effective/Implementation Date (1 January 2020)
ALTERNATIVE TRANSFER METHOD PROVIDERS & ALTERNATIVE TRANSFER METHODS [TRANSPARENCY IN PAYMENTS TRANSITION]
(Amending)
PAC(556)896 (except USA) Expiry: Indefinite
Type: B
Amend Resolution 896, as shown below: WHEREAS pursuant to Resolution 846, countries markets and regions under Resolution 818g will be
transitioned to Resolution 812 and its affiliated Resolutions upon specific parameters being met;
WHEREAS the Passenger Agency Conference wishes to make a wider variety of Payment Methods available to
Agents as soon as operationally feasible, it is,
RESOLVED that:
1. The below conditions will apply for the enrolment of products with IATA by Alternative Transfer Method
Providers;
2. This Resolution will be implemented in a country or group of countries upon notification by the Agency
Administrator in accordance with the provisions of Resolution 846. Notification of implementation of this
Resolution will be given to all Members by the Agency Administrator;
3. When Resolution 812 and 812a are fully implemented in a country, this resolution will no longer apply.
Notification will be given by the Agency Administrator with a minimum of 30 days’ notice when this is to be
applied.