AndyW2026
Newbie
- Joined
- Feb 7, 2026
- Posts
- 3
Hi everyone,
I’m hoping for a sanity check from the community here.
I’m currently in a deadlock with Qantas Executive Relations regarding what looks like a clear database error in the Partner Earning Tables for Malaysia Airlines (MH), and a lack of update for East Coast -> KUL post the September 1, 2025 enhanced partnership agreement - and I’m trying to decide if I’m banging my head against a wall or if I should push this to VCAT. I'm actually more annoyed at the lack of understanding, escalation and acknowledgement of the issue than the SCs and will likely make Platinum regardless, but of course the extra 120SC will get me there faster!
I recently flew MEL -> KUL -> BKK on Malaysia Airlines in Business Class (Fare class "D") return.
It feels like they are knowingly relying on a database error to under-reward East Coast flyers, and refusing to fix it because "the computer says so." They have also provided no plausible explanation for the significant differences and lack of update for East Coast -> KUL
Am I being silly for pushing this over ~120 Status Credits, or is this a legitimate case for VCAT given they are publishing contradictory value tables for the same product?
Cheers,
I’m hoping for a sanity check from the community here.
I’m currently in a deadlock with Qantas Executive Relations regarding what looks like a clear database error in the Partner Earning Tables for Malaysia Airlines (MH), and a lack of update for East Coast -> KUL post the September 1, 2025 enhanced partnership agreement - and I’m trying to decide if I’m banging my head against a wall or if I should push this to VCAT. I'm actually more annoyed at the lack of understanding, escalation and acknowledgement of the issue than the SCs and will likely make Platinum regardless, but of course the extra 120SC will get me there faster!
I recently flew MEL -> KUL -> BKK on Malaysia Airlines in Business Class (Fare class "D") return.
- I received 60 Status Credits for the MEL -> KUL leg and another 60 for the return KUL -> MEL leg.
- If I had flown PER to KUL or ADL to KUL — on the exact same airline and exact same Fare Class D, I would have earned 100 Status Credits each way.
- Perth/Adelaide (Zone 4): Were correctly updated to the new "Business" rate (jumping from ~50 to 100 SC).
- Melbourne/Sydney (Zone 5): Appear to have been left stranded on the legacy pre-September rates (staying at 60 SC), effectively treating "D" class as Economy/Discount Economy from the East Coast, despite Qantas's own updated table defining "D" as Business post the September 1 changes!
- Note: Qantas does not operate their own metal on this route, so "route protection" differences shouldn't be at play here.
- They refuse to acknowledge the announced changes in the airline earning table on their own website post September 1, and lack of updates to the calculator. They simply point to the calculator and say "The calculator says 60, so it is 60." - and "apologies" for any confusion - with Executive relations attempting to offer me 5000 FF points for the misunderstanding, and to "help me" get to platinum at the end of my membership year if I fell short (I should qualify before then anyway)
- I pointed out that it is illogical for shorter flights (PER-KUL/ADL-KUL) to earn nearly double a longer flight (MEL-KUL) for the same fare class. Their Executive Relations team replied claiming the difference was due to "complex factors, but predominately Fare Class type"—which is patently false, as I was comparing D Class to D Class.
- I went to the Airline Customer Advocate. Qantas responded to them by stating my flights were "not eligible for Status Credits" (factually untrue, as they credited 60) and they refused to engage further.
It feels like they are knowingly relying on a database error to under-reward East Coast flyers, and refusing to fix it because "the computer says so." They have also provided no plausible explanation for the significant differences and lack of update for East Coast -> KUL
Am I being silly for pushing this over ~120 Status Credits, or is this a legitimate case for VCAT given they are publishing contradictory value tables for the same product?
Cheers,
