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 » 2015 Changes to Social Security: Focus Is on “File-and-Suspend”

2015 Changes to Social Security: Focus Is on “File-and-Suspend”

Kristi Mathisen | Financial and Business Planning | January 29, 2016 (February 25, 2020)

Think you have your Social Security strategy figured out? It’s time to take another look. Late in 2015, Congress voted to limit the advantages of “file-and-suspend,” an option used by many Americans to maximize Social Security payouts. If you’re 66 or older now, you have just until April 29, 2016 to lock in all the advantages of the file-and-suspend strategy. Those younger than 66 will also need to review their strategy for collecting benefits in light of recent changes.

In this post, I explain what you need to know and do, depending on your age.

Limiting the Advantages of File-and-Suspend

In effect, Social Security pays people to wait: Say you turned 66 in 2015, but opted to wait until age 70 (2019) to collect what would normally be a $1,000 monthly benefit. That four-year postponement would increase your monthly check to $1,320! You’ll still get a higher payout if you postpone going forward (#1 advantage below), but two related advantages (#2 and #3 below) will go away for most people.
===============================================================================
“File-and-Suspend” Advantages Prior to 2016

People turning 66 (the Full Retirement Age) would file for Social Security and request that their payments be suspended. The advantages:

  • #1: Your benefits would then continue to grow 8% per year (for up to four years).
  • #2: Your family members could begin collecting benefits.
  • #3: You could “unsuspend” any time and get a lump sum of all payments skipped during the suspension.

===================================================================================

THE CHANGES ARE AGE-DEPENDENT

If you’re 66 or older by April 29, 2016, YOU NEED TO ACT FAST!

You have a short window of time – the next three months – to elect to use file-and-suspend in order to retain all three advantages (see box above). After April 29, 2016, suspending your benefits will also suspend all family benefits. Plus, you won’t be able to get a retroactive lump sum payment if you “unsuspend.”

An added twist: former spouses (in a marriage that lasted for at least 10 years) will not be able to collect the 50% divorced-spouse benefit if their ex-spouse suspends. This makes a former spouse vulnerable to his/her ex’s decision to suspend, a nasty surprise for many no doubt.

NOTE: If you’ve already filed for Social Security and opted to file-and-suspend, you’re grandfathered in (pun intended). All the advantages of file-and-suspend will continue for you.

If you’re 62 to 65 years old as of Jan. 1, 2016, take note:

You will still be allowed to file a “restricted application,” when you reach Full Retirement Age (66), IF: (1) You are entitled to Social Security; and (2) You are (or were) married to someone who has filed for Social Security. In this case, you will be able to collect an amount equal to 50% of your spouse’s (or ex-spouse’s) benefit while you suspend your own benefit to keep that growing 8% annually until age 70. NOTE: If your spouse then opts to suspend his/her Social Security after April 29, 2016, your entitlement to the spousal benefit could be cut off.

Some things to keep in mind: If you’re single without dependents, suspending Social Security until age 70 to maximize your payments can make sense. But, if you’re married, and/or have dependents who would collect Social Security based on your benefit, you should review your retirement income strategy to determine how to replace the higher “file-and-suspend” payments you were expecting.

Younger than 62 on Jan. 1, 2016? You may need to revise your plans.

Whether you claim benefits early (starting at age 62) or wait until 66 (Full Retirement Age), once you file you will be paid the highest benefit you’re entitled to, whether that’s a spousal benefit or your own benefit. You won’t be allowed to choose.

You’ll still be able to postpone collecting Social Security to boost your payout by 8% annually for four years. However, unlike those who were 62 by Jan. 1, 2016, (see above) you won’t be able to collect a spousal benefit while letting your own benefit grow. If you had been planning to do this, we can help you determine the next-best option.

  • Share:

Kristi Mathisen

Kristi is Managing Director, Tax & Financial Planning at Laird Norton Wealth Management. An attorney and CPA with more than 25 years of financial-services experience, Kristi writes on the implications of tax issues at the local, state and federal levels.

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