<p><div><div><div><div data-show-faces="false" data-height="21" data-width="100" data-layout="button_count" data-send="true" data-href="https://www.r-bloggers.com/latest-uss-proposal-who-would-lose-most/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="https://statgeek.net/2018/03/13/latest-uss-proposal-who-would-lose-most/"> R – Let's Look at the Figures</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<p>Yesterday the UUK/UCU negotiations at ACAS concluded with an <a rel="nofollow" href="https://www.ucu.org.uk/media/9300/Agreement-reached-between-UCU-and-UUK-under-the-auspices-of-ACAS/pdf/UCU_UUK_agreement_at_ACAS_12_March_Final.pdf" target="_blank">agreement</a> document.</p>
<p>In this post I’ll look at the numbers in those proposed interim changes to the Universities Superannuation Scheme, to work out how much money would effectively be lost by USS members at each salary level.</p>
<p>This is inevitably a fairly rough calculation, but its results don’t really demand more precision.  The picture is very clear: the cost of “saving” USS would be felt most by USS members with low or moderate incomes.</p>
<p>The effective marginal rates at which money is lost by members are (as calculated below):</p>
<ul>
<li>4.3% on salary up to £42k</li>
<li>10.7% on salary between £42k and the current USS threshold salary of £55.55k</li>
<li>1.0% (at most) on salary over £55.55k</li>
</ul>
<p>This translates into the following relationship between salary and the percentage of salary lost:</p>
<p><img data-orig-file="https://statgeek.files.wordpress.com/2018/03/lost.png?w=456" data-orig-size="2940,1470" data-medium-file="https://statgeek.files.wordpress.com/2018/03/lost.png?w=456?w=300" data-attachment-id="723" data-image-meta="{" data-image-description="" src="https://statgeek.files.wordpress.com/2018/03/lost.png?w=456" data-permalink="https://statgeek.net/2018/03/13/latest-uss-proposal-who-would-lose-most/lost/" data-large-file="https://statgeek.files.wordpress.com/2018/03/lost.png?w=456?w=450" alt="lost" data-image-title="lost" sizes="(max-width: 450px) 100vw, 450px" data-comments-opened="1" class="wp-image-723" data-recalc-dims="1"></p>
<p>The two “kinks” in that graph reflect the discontinuities in marginal rates, at £42k and at £55.55k.</p>
<p>The long decay to the right continues indefinitely, ultimately approaching an asymptote at 1% lost, i.e., for those with absolutely stratospheric salaries (if such people are actually members of USS, still, that is — though I would guess that many are not).</p>
<p>In the rest of this post I’ll give the details of the calculation that leads to the above numbers and graph.</p>
<p>Just here, though, let me again comment on how <strong>unfair</strong> this “remedy” would be.  The unfairness should be obvious from the above graph: those who are paid most, and would stand to benefit most from being in USS, would contribute least, in percentage terms, in this proposed move towards the future sustainability of USS.  (For a more general view on this unfairness, see also my previous two posts in this “USS” category.)</p>
<h2>The calculation</h2>
<p>It suffices to consider salaries in three distinct bands.  In each salary band, we can calculate how much is lost, per unit of salary.</p>
<p>The following code in <em>R</em> reproduces the graph drawn above.  A brief explanation is then given, beneath the displayed code.</p>
<pre>## This code runs in base R.

## Function to compute the amount that would be lost annually (£k)
## at any given salary level
sacrifice &lt;- function(salary) { # salary in thousands
 old_threshold &lt;- 55.55
 new_threshold &lt;- 42
 s &lt;- salary

## sacrifice arising from income up to the new threshold
 r1 &lt;- min(s, new_threshold) * 
         ((8.7 - 8)/100 + 23 * (1/75 - 1/85))

## sacrifice arising from income between the thresholds
 s2 &lt;- (s > new_threshold) * 
          (min(s, old_threshold) - new_threshold)
 r2 &lt;- s2 * ((8.7 - 8)/100 + (23/75 - (12 + 8.7)/100))

## sacrifice (max) arising from income over the old threshold
 r3 &lt;- (s > old_threshold) * 
         (s - old_threshold) * (13/100 - 12/100)

return(r1 + r2 + r3)
}

## A vector of salary values up to £250k
salaries &lt;- (1:2500) / 10

## Compute percent of salary that would be lost, at each salary level
sacrifices &lt;- 100 * sapply(salaries, sacrifice) / salaries

## Plot the result
svg(file = &quot;lost.svg&quot;, width = 8, height = 4)
plot(salaries, sacrifices, type = &quot;l&quot;, xlab = &quot;salary (thousands)&quot;, ylab = &quot;percent lost&quot;,
 main = &quot;Percent of salary lost under UUK-UCU agreement 2018-03-12&quot;)
dev.off()</pre>
<h3><strong>Band 1: Salary up to £42k<br>
</strong></h3>
<p>All contributions from this part of salary go to the “defined benefit” part of USS.</p>
<p>The new proposal would see <strong>8.7%</strong> of member’s salary up to £42k going in to this, as opposed to <strong>8.0%</strong> at present.<strong><br>
</strong></p>
<p>The return (i.e., the value of the defined-benefit pension) can readily be calculated using the standard HMRC formula, the one that is used for Annual Allowance and Lifetime Allowance purposes.</p>
<p>Under <em>current USS</em>, the value of this part is <strong>23 times (<em>s</em>/75)</strong>, where <em>s</em> is either £42k or the member’s salary if the salary is less than £42k.</p>
<p>Under <em>yesterday’s proposals</em>, the value of this part would fall to <strong>23 times (<em>s</em>/85).</strong></p>
<p>The amount lost to each member, relating to salary in this first band, is then the sum of the additional contribution made and the amount of pension value lost: that is <em>r1</em> in the above code.</p>
<h3>Band 2:  Salary between £42k and £55.55k</h3>
<p>Now, for salaries greater than £42k, let <em>s2</em> be the smaller of (salary minus £42k) and (£55.55k minus £42k).</p>
<p>Then <em>current USS</em> has members contributing <strong>8% of <em>s2</em></strong> in this part, for a return of <strong>23 times s2/75</strong>.</p>
<p><em>Yesterday’s proposal</em> would change the contribution to <strong>8.7% of <em>s2</em></strong>, for a return of <strong><em>s2</em> times (12% + 8.7%)</strong>.</p>
<p>Again, the amount lost to each member, relating to salary in this second band, is just the sum of the additional contribution made and the amount of pension value lost: that is <em>r2</em> in the above code.</p>
<h3>Band 3: Salary over £55.55k</h3>
<p>The picture here is a bit more complicated, but we can at least calculate an <em>upper bound</em> on the amount lost at any given salary level.</p>
<p>The complication arises because of the optional USS “1% Match” possibility, and because losses at high salaries might need to be discounted to allow for breaching HMRC tax allowances.</p>
<p>But the <em>largest</em> possible loss in this band is incurred by someone who has taken the USS 1% Match, and has no tax-allowance issues; and that is what we calculate here.</p>
<p>The amount lost by such a person would be simply <strong>1% of their salary in excess of £55.55k </strong>(since that’s the value of the lost “Match” contribution from the employer; and the employee’s own contributions still go directly to the employee’s defined-contribution pension pot).  That is the quantity computed as <em>r3</em> in the above code.</p>
<h2>Conclusion</h2>
<p>I have reproduced the full calculation here, with code, because I found the result of the calculation so shocking!  If anyone reading this thinks I have made a mistake in the calculation, please do let me know.</p>
<p>If it <strong>is</strong> correct — and right now I have no reason to suspect otherwise — then I confess I’m alarmed that this is actually being proposed as a potential solution, even as an <em>interim</em> solution for the next 3 years, to the perceived problems with USS.  It shakes my faith in all those who have been involved in negotiating it.  With seemingly intelligent people on both sides of the table, how could they possibly come up with something as bad as this?</p>
<p>© David Firth, March 2018</p>
<p><strong>To cite this entry:</strong><br>
Firth, D (2018). Latest USS proposal: Who would lose most?  Weblog entry at <span>URL</span> <a rel="nofollow" href="https://statgeek.net/2018/03/13/latest-uss-proposal-who-would-lose-most/" target="_blank">https://statgeek.net/2018/03/13/latest-uss-proposal-who-would-lose-most/</a>.</p>
<h3><span>Update, 13 March pm: A tabular view of what’s in the graph</span></h3>
<pre>## Make a table for anyone who wants more detail than the graph
salary &lt;- c(10:55, 55.55, 56:100, 150, 200)
percent_lost &lt;- round(100 * sapply(salary, sacrifice) / salary, 2)
salary &lt;- 1000 * salary
my_table &lt;- data.frame(salary, percent_lost)</pre>
<p>That’s the code for making a little table, showing the same numbers as those in the graph.</p>
<p>Here is the resulting table:</p>
<pre>salary    %
 10000 4.31 -- I started the table at £10k for no good reason
 ...
 41000 4.31
 42000 4.31 -- the proposed new threshold
 43000 4.46
 44000 4.60
 45000 4.73
 46000 4.86
 47000 4.98
 48000 5.10
 49000 5.22
 50000 5.33
 51000 5.43
 52000 5.53
 53000 5.63
 54000 5.72
 55000 5.81
 55550 5.86 -- current USS threshold, highest % of salary lost
 56000 5.82
 57000 5.74
 58000 5.65
 59000 5.57
 60000 5.50
 61000 5.42
 62000 5.35
 63000 5.28
 64000 5.22
 65000 5.15
 66000 5.09
 67000 5.03
 68000 4.97
 69000 4.91
 70000 4.86
 71000 4.80
 72000 4.75
 73000 4.70
 74000 4.65
 75000 4.60
 76000 4.55
 77000 4.51
 78000 4.46
 79000 4.42
 80000 4.37
 81000 4.33
 82000 4.29
 83000 4.25
 84000 4.21
 85000 4.18
 86000 4.14
 87000 4.10
 88000 4.07
 89000 4.03
 90000 4.00
 91000 3.97
 92000 3.93
 93000 3.90
 94000 3.87
 95000 3.84
 96000 3.81
 97000 3.78
 98000 3.75
 99000 3.73
100000 3.70
150000 2.80
200000 2.35 -- possibly there are even some salaries this high?!</pre>
<p> </p>
	<p>
<div>
<div>To <strong>leave a comment</strong> for the author, please follow the link and comment on their blog: <strong><a href="https://statgeek.net/2018/03/13/latest-uss-proposal-who-would-lose-most/"> R – Let's Look at the Figures</a></strong>.</div>
<hr>
<a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers.com</a> offers <strong><a rel="nofollow" href="https://feedburner.google.com/fb/a/mailverify?uri=RBloggers">daily e-mail updates</a></strong> about <a rel="nofollow" href="https://www.r-project.org/" title="The R Project for Statistical Computing">R</a> news and <a rel="nofollow" href="https://www.r-bloggers.com/search/tutorial" title="R tutorials">tutorials</a> on topics such as: <a rel="nofollow" href="https://www.r-bloggers.com/search/data%20science" title="Data science">Data science</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Big%20Data" title="Big Data">Big Data, <a rel="nofollow" href="https://www.r-users.com/" title="R jobs">R jobs</a>, visualization (<a rel="nofollow" href="https://www.r-bloggers.com/search/ggplot2" title="ggplot and ggplot2 tutorials">ggplot2</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/boxplot" title="Boxplots using lattice and ggplot2 tutorials">Boxplots</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/map" title="Maps and gis">maps</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/animation" title="Animation in R">animation</a>), programming (<a rel="nofollow" href="https://www.r-bloggers.com/search/RStudio" title="RStudio IDE for R">RStudio</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/sweave" title="Sweave and literate programming">Sweave</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/LaTeX" title="LaTeX in R">LaTeX</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/SQL" title="SQL and databases">SQL</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/eclipse" title="Eclipse IDE for R">Eclipse</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/git" title="git and github, Version Control System">git</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/hadoop" title="Large data in R using Hadoop">hadoop</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Web+Scraping" title="Web Scraping of google, facebook, yahoo, twitter and more using R">Web Scraping</a>) statistics (<a rel="nofollow" href="https://www.r-bloggers.com/search/regression" title="Regressions and ANOVA analysis tutorials">regression</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/PCA" title="principal component analysis tutorial">PCA</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/time+series" title="Time series">time series</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/trading" title="finance trading">trading</a>) and more...
<img alt="" width="1" src="http://feeds.feedburner.com/~r/RBloggers/~4/neQWQjUAhig" height="1"></a></div>