Regardless of when it eventually posts, anything which departs up to midnight on the 8th counts to your current year. Anything which departs from midnight onwards on the 9th counts to your next year.

@KARFA as always spot on, but not being an expert, and not personally having been in a position of leaving it so tight for a status upgrade/retention, and knowing BA Systems are not always the most reliable, my advice would be:

take a screenshot of your TP’s etc on the app the day before the reset, also of BP’s for the flights before the reset date but due to post afterwards. I’m sure this might make things easier on the likely phone calls / e-comms you might need to involve yourself in if it goes awry. This should hopefully account for even the most difficult potential beaurocrat / system says no you may face, (though my experience has shown vast majority not to be like that)

hope for the best / plan for the worst....?

Although the grace period does exist, the OP’s flight is on 8 July so there is no need to rely on it - hence why I didn’t mention it. Even if the flight does post a week or two after 8th it will still automatically count towards the previous year without any need to rely on the two week grace period.

The grace period is only if you want flight actually flown up to two weeks after 8th to count to the previous year due to status.

I’m interested @KARFA in your experience (and hence my advice to the OP), but in your vast experience, will the BA systems actually recognise it automatically or can they expect a telecon/e-mail follow up to make it stick? I know what my guess would be lol!

It has done correctly every time I have had flights taken right up to the deadline. Flights have posted after 8th, been added to my lifetime total, but the TPs have been immediately zeroed and not added to my new year.

The only question is whether like in the OP’s case it would also recognise the status change if those points were the remaining ones needed to take the member over the threashold for the previous year. On that issue I am not sure, but even if it doesn’t I think a quick call would resolve it. As with normal status updates it may be worth waiting a day or two after the relevant flight actually posts beforehand calling, as status updates do lag 1/2 days behind flight posts.

I am not sure what you are suggesting? Again the OP isn’t needing to use the 2 week grace period as the flight itself is within the relevant membership year.

Thanks @KARFA , this seems to be one of those situations that as a relative novice (but ever grateful for FT flyer advice), this is a situation that stretches the BA system even beyond most FTers experience so I hope the OP will update the “what actually happened” versus “what should have happened”.... IMHO there should be zero need for any manual intervention from the OP to secure his status.... I am glass half empty on this though so predict they may need to speak to a human (or at least follow up with the online systems lol)

Not in my case (includes BA and partner flight) and not in any reports I have ever seen on FT. The points for flights from 8th or before have never incorrectly credited to the new year. The cutoff isn’t messy at all.

If you have an example it would be interesting to see a screenshot.

The flights post with a “transaction date” so the date the flight was taken, and a “posting date” for when they actually hit your account. Anything which has a transaction date of 8th or earlier and posts in the new membership year gets the TPs zeroed out straight away as far as your new TP balance is concerned.

For the instances where the grace period is relied upon a manual intervention is required I imagine you may see the odd mistake. However grace periods are only available anyway for those who haven’t quite reached the threshold to achieve/renew status and do have flights booked within the two week period after 8th which would credit enough points to achieve the threshold

The system works! Let’s hope it does also for the OP!