Skip to content
Laird Norton Wealth Management
  • Services
          • Wealth Planning
            • Business Owner
            • Equity Compensation
            • Estate Strategies
            • Philanthropic Giving
            • Tax Strategies
          • Investment Management
            • Tax-Aware Investing
            • Risk Management
            • Alternatives & Private Market
            • Impact Investing
          • Trust Services
            • Beneficiary Services
            • Family Legacy
            • Trust Administration
            • Trust Benefits
            • Understanding Trusts
          • NonProfit Clients
            • Request RFP Participation
  • About
          • About LNWM
            • Fiduciary Financial Advisor
            • How We Help
            • Our Team
            • Corporate Social Responsibility
            • Careers
            • Community
            • Board of Directors
            • FAQs
        • two people in a kayak on water
  • Insights
        • Blog

          Top-of-mind at LNWM and elsewhere.

          Papers

          Expert insights and analysis.

          Videos

          See what we're up to.

          Media

          Our published work and media coverage.

  • Contact
Search Icon
Client Login
mobile-login

Home » Insights » Financial and Business Planning » Social Security Ending In 2023? No. But What Really Happens When The Trust Fund Is Emptied?

statue of liberty

Social Security Ending In 2023? No. But What Really Happens When The Trust Fund Is Emptied?

Independent Media | Financial and Business Planning | September 2, 2020 (September 11, 2020)
This article was written by an independent media source and selected by LNWM for our blog readers. LNWM provides this third-party information for informational purposes only and has not verified the accuracy or completeness of such. In addition, LNWM is endorsing neither the content nor the author of the commentary.

The Social Security Administration’s chief actuary recently reported, in response to a question by Senate Democrats Chuck Schumer, Bernie Sanders, and Ron Wyden, that, if the dedicated payroll taxes to fund Social Security were removed with no replacement income source, the Disability Insurance Trust Fund would be depleted in the middle of 2021 and the Retirement/Survivors’ Trust Fund, in mid-2023.

This is no surprise — though the dates are sooner than my prior back-of-the-envelope calculation in a prior article. It’s fairly obvious that the key is the provision in the hypothetical, as specified by the Democrats, that there would be “no alternative source of revenue to replace the elimination of payroll taxes.” I have said regularly (and again in that article) that I believe there would be a “Social Security fix” — legislation to simply direct general revenues to fill in the cap, whether it’s the 20% gap that has long been expected, or the full obligation in the event that the payroll tax were ended. I’ve further said that I could well see Congress legislating this as a “temporary fix,” over and over again, until the political stars align for a permanent change.

In other words, a headline such as NBC’s “ Terminating payroll tax could end Social Security benefits in 2023, chief actuary warns ” is highly misleading because it lacks that caveat: if there’s no other revenue source.

The notion that Trump would be able to corral enough votes to remove the payroll tax, but would not simultaneously ensure provision for alternative funding is nonsensical. In that respect, the Democrats’ request is simply an attempt to generate more headlines in their favor.

But that nonetheless suggests that there is a real risk that partisan rancor could cause the Trust Fund depletion to lead to a game of chicken, rather than to bipartisan, constructive solutions. So it’s time to address the question: what would actually happen?

The short answer is simple: when the Social Security Trust Fund is depleted, there will remain enough money to pay 80% of promised benefits.

This statistic is cited repeatedly, with the intent, by some, to generate urgency in solving the problem, while others use it to reassure their audience: “don’t worry, even if nothing’s done, the cut won’t really be that bad.”

But how exactly would benefits be cut?

There are, after all, a variety of options one might imagine.

Benefits could be cut in an across-the-board way: cut everything by 20%. Or, to be fairer, benefits could be given a haircut by resetting the maximum benefit at some lower amount. Benefits could be means-tested so that those with the most retirement income from other sources take the hardest hit.

But what does the law actually say? Turns out, the answer is “ nothing .”

Literally.

Here’s the Congressional Research Service’s report, updated just this past July, “Social Security: What Would Happen If the Trust Funds Ran Out?”

“The Social Security Act specifies that benefit payments shall be made only from the trust funds (i.e., only from their accumulated bond holdings). Another law, the Antideficiency Act, prohibits government spending in excess of available funds. Consequently, if the Social Security trust funds become insolvent—that is, if current tax receipts and accumulated assets are not sufficient to pay the benefits to which people are entitled—the law effectively prohibits full Social Security benefits from being paid on time.

“The Social Security Act states that every individual who meets program eligibility requirements is entitled to benefits. Social Security is an entitlement program, which means that the federal government is legally obligated to pay Social Security benefits to all those who are eligible for them as set forth in the statute. If the federal government fails to pay the benefits stipulated by law, beneficiaries could take legal action. Insolvency would not relieve the government of its obligation to provide benefits.

“The Antideficiency Act prohibits government agencies from paying for benefits, goods, or services beyond the limit authorized in law for such payments. The authorized limit in law for Social Security benefits is the balance of the trust fund. The Social Security Act does not stipulate what would happen to benefit payments if the trust funds ran out. As a result, either full benefit checks may be paid on a delayed schedule or reduced benefits would be paid on time.”

But does the Social Security Administration have the authority to made decisions about how to pay out benefits?

To operate within the strict parameters of the law, the administration would be obliged to simply delay benefit payments, creating a backlog that grows . . . and grows . . . and grows — because, however much the original narrative may have been that Social Security deficits are temporary, due to Baby Boomer retirements, that’s not at all the case; we will never again be able to cover Social Security costs through FICA taxes, and the deficit will only get worse over time. This means that retirees would get “full” checks but only 9 or 10 in a year.

Could the Social Security Administration cut benefits, to manage this backlog, so that everyone gets 80% checks paid on time? For further clarity, I checked in with Marc Goldwein, head of policy at the non-partisan Committee for a Responsible Federal Budget, who confirmed that there is no consensus on this point; some experts say “yes,” some say “no.”

What it comes down to then, is this: it may indeed be the case that, come 2035, or 2031 or 2027, Republicans and Democrats will both recognize that they have to sort out their differences so as to not leave Social Security in the lurch. But if they insist on “winning” rather than compromising, the outcome could be quite chaotic indeed.

  • Share:

Sign Up For Navigator

Get our quarterly insights on investments, wealth planning, taxes and trusts.

Site Logo in footer footer logo
facebook Twitter Opens a news tab Linkedin Opens a news tab Youtube Opens a news tab

About

  • Board of Directors
  • Careers
  • Community
  • Contact
  • FAQs
  • Our Team
  • Sign up for Navigator

Services

  • Investment Management
  • Sustainable Investing
  • Tax Strategies
  • Trust Services
  • Understanding Trusts
  • Wealth Planning

Address

  • Laird Norton Wealth Management 801 Second Avenue, Suite 1600
    Seattle, WA 98104
    United States
  • 206.464.5100
  • 800.426.5105
© 2023 Laird Norton Wealth Management. All rights reserved.
Form CRSOpen PDF in a new tab Legal Terms and Conditions Privacy Policy
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to customize your settings.
Cookie SettingsAccept All
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
langsessionLinkedIn sets this cookie to remember a user's language setting.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
_uetsid1 dayBing Ads sets this cookie to engage with a user that has previously visited the website.
_uetvid1 year 24 daysBing Ads sets this cookie to engage with a user that has previously visited the website.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
_hjAbsoluteSessionInProgress30 minutesHotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjFirstSeen30 minutesHotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user.
_hjIncludedInPageviewSample2 minutesHotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit.
_hjIncludedInSessionSample2 minutesHotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit.
_hjTLDTestsessionTo determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails.
_omappvp11 yearsThe _omappvp cookie is set to distinguish new and returning users and is used in conjunction with _omappvs cookie.
_omappvs20 minutesThe _omappvs cookie, used in conjunction with the _omappvp cookies, is used to determine if the visitor has visited the website before, or if it is a new visitor.
calltrk_session_id1 yearThis cookie is set by the Provider CallRail. This cookie is used for storing an unique identifier for a user browser session. It is used for tracking the number of phone calls generate from the website.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_mkto_trk2 yearsThis cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
MUID1 year 24 daysBing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
_ce.gtldsessionNo description
_dc_gtm_UA-41670453-11 minuteNo description
_hjSession_275188330 minutesNo description
_hjSessionUser_27518831 yearNo description
AnalyticsSyncHistory1 monthNo description
BIGipServerab10web-nginx-app_httpssessionNo description
BIGipServerab47web-nginx-app_httpssessionNo description
calltrk_landing1 yearThis is a functionality cookie set by the CallRail. This cookie is used to store the landing page URL. It helps to accurately attribute the visitor source when displaying a tracking phone number.
calltrk_nearest_tld9 years 10 months 8 daysNo description
calltrk_referrer1 yearThis is a functionality cookie set by the CallRail. This cookie is used to store the referring URL. It helps to accurately attribute the visitor source when displaying a tracking phone number.
CookieLawInfoConsent1 yearNo description
li_gc2 yearsNo description
SAVE & ACCEPT
Powered by CookieYes Logo