Prince Harry and Meghan Markle made news earlier this year as they announced that they would be stepping down from their roles as ‘senior’ members of the royal family, becoming financially independent and relocating to Canada and now California.
The couple have lost their HRH titles and closed their Sussex Royal social media accounts, moving away from the brand.
‘The Duke and Duchess of Sussex are grateful to Her Majesty and the Royal Family for their ongoing support as they embark on the next chapter of their lives,’ a statement read earlier this year.
And while Harry and Meghan will always remain family members, as of 31 March at midnight, they were announced to no longer represent the Queen.
‘Effective March 31, 2020, no other Royal communications representatives act on behalf of The Duke and Duchess of Sussex, including Palace spokespeople, Household representatives nor Royal sources,’read a statement on behalf of the couple. ‘Going forward, Buckingham Palace will no longer comment/guide on Sussex related enquiries.’
But why 31 March? According to royal insiders, it’s all about finance, with the date marking the end of the financial year.
‘One of the reasons behind the Duke and Duchess of Sussex officially stepping back from their royal duties on this date, is because 31 March marks the end of the financial year for the royal family,’ explained HELLO Online’s royal correspondent Danielle Stacey. ‘Every year, around June, the royal household publishes its annual financial statement, the Sovereign Grant report, for the previous year. Details in the annual reports include the cost of travel, staff and property maintenance. Harry and Meghan have expressed their wishes to work to become financially independent and as they will no longer receive funding from the Sovereign Grant, it makes sense for them to depart on this particular date.’
Well, that’s that.
The post The reason for Prince Harry and Meghan Markle's 31 March resignation date has been revealed appeared first on Marie Claire.
from Marie Claire https://ift.tt/2xJwhGg
0 Comments