
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>hm treasury &#8211; The Milli Chronicle</title>
	<atom:link href="https://millichronicle.com/tag/hm-treasury/feed" rel="self" type="application/rss+xml" />
	<link>https://millichronicle.com</link>
	<description>Factual Version of a Story</description>
	<lastBuildDate>Tue, 07 Apr 2026 15:20:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://media.millichronicle.com/2018/11/12122950/logo-m-01-150x150.png</url>
	<title>hm treasury &#8211; The Milli Chronicle</title>
	<link>https://millichronicle.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Public Pension Errors in Britain Trigger Long-Term Debt Burdens for Retirees</title>
		<link>https://millichronicle.com/2026/04/64834.html</link>
		
		<dc:creator><![CDATA[NewsDesk MC]]></dc:creator>
		<pubDate>Tue, 07 Apr 2026 15:20:27 +0000</pubDate>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Top Stories]]></category>
		<category><![CDATA[accountability]]></category>
		<category><![CDATA[administrative errors]]></category>
		<category><![CDATA[cabinet office]]></category>
		<category><![CDATA[capita]]></category>
		<category><![CDATA[cheshire]]></category>
		<category><![CDATA[civil service pension]]></category>
		<category><![CDATA[derbyshire]]></category>
		<category><![CDATA[elderly welfare]]></category>
		<category><![CDATA[financial hardship]]></category>
		<category><![CDATA[hm treasury]]></category>
		<category><![CDATA[mycsp]]></category>
		<category><![CDATA[nhs pensions]]></category>
		<category><![CDATA[pension overpayment]]></category>
		<category><![CDATA[pensions ombudsman]]></category>
		<category><![CDATA[policy failure]]></category>
		<category><![CDATA[post office pension]]></category>
		<category><![CDATA[public finance]]></category>
		<category><![CDATA[public sector]]></category>
		<category><![CDATA[retirement crisis]]></category>
		<category><![CDATA[retirement debt]]></category>
		<category><![CDATA[runcorn]]></category>
		<category><![CDATA[social impact]]></category>
		<category><![CDATA[UK economy]]></category>
		<category><![CDATA[uk pensions]]></category>
		<guid isPermaLink="false">https://millichronicle.com/?p=64834</guid>

					<description><![CDATA[“She has been told she will have paid everything she owes when she is 93.” A series of administrative errors]]></description>
										<content:encoded><![CDATA[
<p><em>“She has been told she will have paid everything she owes when she is 93.”</em></p>



<p>A series of administrative errors in Britain’s public sector pension systems is leaving retirees with unexpected debts that, in some cases, will take decades to repay, raising questions about oversight, accountability and the balance between public finance rules and individual hardship.</p>



<p>One such case involves a 66-year-old retired civil servant from Runcorn, Cheshire, who was informed that she had been overpaid £40,000 in pension benefits due to miscalculations by scheme administrators. After accounting for tax already paid on the income, her outstanding liability stands at £32,000. The repayment has significantly reduced her annual income from £19,700 to £12,000.</p>



<p>Initially required to repay £496 per month over five years, she later secured a reduction to £100 per month after raising concerns about affordability. However, the adjustment came with a legal charge placed on her home as security. </p>



<p>Based on the revised terms, she has been told that repayment could extend into her early 90s.Her family says the financial pressure has compounded existing health challenges.</p>



<p> She is currently on medication for depression, with relatives attributing a worsening of her condition to the stress of repayment demands.The case is part of a broader pattern affecting hundreds of pensioners across civil service, healthcare and postal systems. In 2019, MyCSP, which administered the civil service pension scheme on behalf of the UK government, acknowledged that around 2,000 pensioners had been collectively overpaid £2.7 million due to calculation errors. </p>



<p>In several cases, discrepancies went undetected for years, sometimes more than a decade.Despite this, existing regulations require pension administrators to recover overpayments in order to protect public funds. Under HM Treasury guidance, there is no general exemption based on administrative fault. </p>



<p>Recovery is mandatory unless recipients can demonstrate that repayment would cause severe financial hardship.In practice, this creates a tension between fiscal accountability and individual welfare. </p>



<p>Pensioners often receive formal notices informing them of the error, outlining repayment schedules and warning of potential legal action if arrangements are not made within a specified period.In the Runcorn case, the retiree had previously questioned the size of her pension payments in 2021 and again in 2025, but was assured by administrators that the amounts were correct.</p>



<p> Only later was the overpayment identified, leading to the current recovery process.Officials from the Cabinet Office, which oversees the civil service pension scheme, said they apply “stringent guidelines” to ensure public funds are recovered while attempting to minimise the burden on individuals. </p>



<p>They added that repayment plans are designed to be flexible and proportionate to a pensioner’s financial circumstances.However, campaigners and affected individuals argue that the system places disproportionate responsibility on pensioners for errors they did not cause and could not reasonably have identified.</p>



<p>Similar cases have emerged in other public sector schemes. In Derbyshire, a retired NHS worker was informed by the NHS Business Services Authority that he had been overpaid £35,000 due to a miscalculation dating back to 2014. Following his retirement in 2021, his monthly pension income was reduced by £400.</p>



<p>After he challenged the figures, the authority recalculated the debt to £33,000 but maintained its position on recovery. The individual said the financial strain forced him and his spouse to withdraw financial support they had planned to provide for their son’s wedding.</p>



<p>The NHS Business Services Authority acknowledged that multiple opportunities to identify the error had been missed and offered £1,000 as a goodwill payment. It said it remains committed to handling cases sensitively while complying with Treasury rules requiring recovery of overpayments.</p>



<p>Another case involves an 83-year-old former Post Office employee who was told, 16 years after retirement, that she owed £20,000 due to a pension miscalculation. Her monthly income was subsequently reduced by roughly one-third.</p>



<p>Her family says she has spent years seeking clarification from administrators, first from MyCSP and later from Capita, which took over management of the scheme. They describe the process as prolonged and distressing, with limited transparency regarding how the errors occurred.</p>



<p>Disputes over pension overpayments can be referred to the Pensions Ombudsman, an independent body that adjudicates complaints. In some cases, recovery action has been paused pending investigation, offering temporary relief to affected individuals.</p>



<p>The issue highlights broader structural challenges within public pension administration, including legacy systems, complex calculation methods and fragmented oversight across multiple agencies.</p>



<p> While recovery policies aim to safeguard taxpayer funds, the long-term financial and psychological impact on pensioners continues to draw scrutiny.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
