YQ-YR
YQ and YR are surcharges that are filed in the Record S1 in ATPCO. Travelport do not maintain this data it is electronically processed from the sequence data filed by the Airline.
It is essential that any incidents raised relating to this contain the relevant YQ/YR sequence number(s) from ATPCO.
Travelport process YQ/YR service fees based on data received from ATPCO from 2 different records.
- Fuel and Insurance YQ/YR Data (S1) – The S1 record is filed and owned by the marketing carrier.
- Concurrence Record (S2) – The S2 record is filed and owned by the validating or plating carrier.
When a carrier wishes to collect YQ/YR fees for other carriers besides own, they must file an S2 concurrence record indicating which carriers they want (or don’t want) to collect service fees for.
Most of the YQ/YR incidents we receive are due to incorrect filing of the bytes in the Record S1. Below are some examples.
City v Airport
In this example the Airline XX are expecting a lower YQ of EGP483.00 from Sequence # 16000 however we do not match this sequence.
Here is the expected sequence number 16000 which is filed with Location 1 as CITY
HBE is an Airport of ALY so to fix the Airline would need to correct location 1 to “airport” or change “HBE” to city code “ALY”
Here is the updated and correct filing
Which we then match and apply.
YQ/YR is missing from Shopping or the amount is wrong
This is usually when an airline has filed the YQ in their Service Record 1 (S1) with an equipment code for the sector being validated , we cannot validate and apply the YQ since no flights are booked. When we book and FQ the YQ is then assessed and validated. FS (Low Fare shop) always provides the warning -
ADDITIONAL TAXES, SURCHARGES, OR FEES MAY APPLY
Why are Adult & Child YQ pricing different amounts?
If a Carrier has filed S1 record, with fare class restrictions eg fare basis OWFLYPES this will validate with adult. Hence to validate child a sequence needs to be filed with fare basis restriction of OWFLYPES/* . This will match to FBC ending with OWFLYPES/CH which can have any ticketing code appended such as CH25 , IN90 etc.
As per ATPCO apps:-
4.1.17 Fare Basis Code (bytes 212-226) :--
This field specifies the Fare Basis Code. Validation of this field is against the code that appears in the Fare Basis Box on the ticket. If the data in this field matches the code in the Fare Basis Box on the ticket, then processing matches the record (provided a match is also made to all other match fields). If data in this field does not match the code in the Fare Basis Box on the ticket, then processing no matches the record and continues to the next record.
In addition to alphanumeric, the following characters can also be present in bytes 212-226:
Asterisk ('*') An asterisk is a wildcard value that is used to represent any alphanumeric characters in the ticket designator. Up to 2 asterisks are permitted. Edits only permit an Asterisk wildcard in bytes 212-226 when preceded (directly or indirectly) by a Slash. When an asterisk is present, the asterisk may be replaced by any single or string of alphanumeric characters in the ticket designator, including a slash. If the asterisk is preceded by at least one alphanumeric character, it can be but does not have to be replaced. If the asterisk directly follows the slash, it must be replaced.
Example:
Y/* matches Y/CH, Y//CH and Y/ID/CH, but does not match Y