Originally Posted by
b12e
I get that, but the export PDF does contain the "correct actual" state (amount of XP, amount of miles, amount of UXP), so perhaps as a kickstart it should go from "current state" and look back, rather than start from the bottom and work up. There's, realistically speaking, no way for me to "fix" the balance besides manually add an entry with a fake flight number to "correct" the data.
There should also be events to indicated requalifications, so I guess getting the correct qualification period should also be possible automatically without manual intervention (e.g. the below screenshot).
Either way I've been platinum for longer than the PDF export, so getting old data is going to be near impossible (I do have the flights logged in Flighty, but not the XP and miles movements), perhaps the import should only consider "complete" data, in my case 2023 and newer (since the first "XP Counter offset" in the data) - and warn that older data needs to be manually added.
First fix is live: the import now detects XP discrepancies and lets you add a correction to match your official balance. Still working on: auto-detecting qualification periods from requalification events and smarter handling of incomplete historical data.