This video explains about the different parts of your benefits and when you can take them. Because the RMPP closed on 6 October 2024 you won’t be building up any more benefits after then. We’ll update the video soon.
1. Your final salary pension: the pension you’ve built up to 31 March 2008. It’s based on the number of years and days you worked up to then, and your current pensionable pay.
2. Your Career Salary Defined Benefit (CSDB): the pension you’ve earned based on your service from 1 April 2008 to 31 March 2018. Each year you earned another ‘block’ of this, and the blocks are revalued over time.
3. Your Cash Balance benefit: the lump sum you’ve earned from 1 April 2018 to 6 October 2024.
This gives you the total amount of pension benefits you’ll get when you retire. If you’re an employee member of the Plan, we’ll show you what these are worth in your benefit illustration each year. You’ll also get a statement from Capita showing the benefits you have in the Royal Mail Statutory Pension Scheme (RMSPS).
Under current legislation, up to 25% (a quarter) of the total value of your benefits can be taken as a tax-free cash sum. For the purpose of this calculation, annual pensions are multiplied by 20, and the Cash Balance fund and other lump sums are taken at face value. The Pensions Service Centre (PSC) pays the benefits due from the RMPP and Capita pays any benefits due from the RMSPS. Although benefits earned to 31 March 2012 are paid from the RMSPS any increase in pre 2012 benefits in excess of statutory increases, attributable to increases in pensionable pay, will be paid by the RMPP.
For a breakdown of your benefits, take a look at your benefit illustration. For more help with your benefit illustration, take a look at some commonly asked questions here.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| _cfuvid | session | Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services |
| cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Analytics" category. |
| cookielawinfo-checkbox-functional | 1 year | The GDPR Cookie Consent plugin sets the cookie to record the user consent for the cookies in the category "Functional". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
| VISITOR_PRIVACY_METADATA | 6 months | YouTube sets this cookie to store the user's cookie consent state for the current domain. |
| wpEmojiSettingsSupports | session | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
| Cookie | Duration | Description |
|---|---|---|
| VISITOR_INFO1_LIVE | 6 months | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| Cookie | Duration | Description |
|---|---|---|
| _ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| _hjSession_* | 1 hour | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
| _hjSessionUser_* | 1 year | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
| vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
| YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| Cookie | Duration | Description |
|---|---|---|
| __Secure-BUCKET | 6 months | Description is currently not available. |
| _dd_s | 15 minutes | No description available. |
| Cookie | Duration | Description |
|---|---|---|
| __Secure-ROLLOUT_TOKEN | 6 months | YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. |
| __Secure-YEC | past | Description is currently not available. |
| __Secure-YNID | 6 months | YouTube cookie used to protect user security and prevent fraud, especially during the login process. |
If you don’t know which section you’re in, contact the Helpline (contact details are at the bottom of the page); or If you recieve an Annual Benefit Illustration the section is noted on the front page.