Social Security showing $0.00 benefit after retirement application - 1978 stop date error?
I'm completely baffled and honestly starting to panic. I'm 64 and filed for my SS retirement benefits last week. At first everything seemed fine - got an email saying my application was in the second step of processing. But today I logged into my MySocialSecurity account and found this terrifying message: 'Beginning June 1978, the full monthly Social Security benefit before any deductions is $0.00. We deduct $0.00 for medical insurance premiums each month. The regular monthly Social Security payment is $0.00. (We must round down to the whole dollar.) Benefits were stopped beginning June 1978.' June 1978?! I was a teenager then! My entire earnings record from 1978 through 2024 shows up correctly on their site with all the proper contributions from my employers. I've worked consistently for 46 years and now suddenly they're saying my benefit is ZERO? I'm currently on hold with SSA (wait time over 2 hours), but I'm seriously freaking out. Has anyone seen this kind of error before? The worst part is I can't even access my statement anymore. The site says 'We cannot provide your Statement because you recently applied for Social Security benefits or Medicare.' Is that normal during application processing? Has anyone dealt with this nightmare before?
29 comments


Mei Chen
This is almost certainly a system error. The 1978 date is a major clue - that's likely some kind of default or system date in their software. Don't panic! This happens more often than you'd think when applications are being processed. And yes, it's completely normal that you can't access your statement while your application is processing. Once they start working on your benefits, they temporarily restrict access to the statement while calculations are being done. The $0.00 is definitely an error though - either your application is still being manually reviewed and those are just placeholder values, or there's a glitch that a representative will need to fix. Keep trying to reach someone at SSA, but I promise it will get resolved.
0 coins
Jamal Edwards
•Thank you so much for the reassurance. I've been sitting here imagining my retirement savings evaporating! The 1978 thing seemed so random. I'm still on hold (90 minutes and counting) but feeling slightly less panicked now.
0 coins
Liam O'Sullivan
same thing happnd to me last month!! scared me half to death lol. turned out to be some computer glitch they had to fix. took about 10 days to sort out but got my correct benefit amount after that. hang in there!
0 coins
Jamal Edwards
•Oh thank goodness. Did you have to keep calling them or did they eventually fix it on their own?
0 coins
Liam O'Sullivan
had to call like 5 times before i got through. they fixed it while i was on the phone once i finally reached sombody
0 coins
Amara Okonkwo
This is 100% a system error. June 1978 is often a default date in SSA's systems - it's when they implemented a major update to their records system. I worked for SSA for 32 years before retiring, and we saw this constantly with new applications. What's happening is your application is still in the early processing stage. The system basically puts in placeholders while the real calculation is being done by their back-end systems. Unfortunately, those placeholders sometimes show up in your online account and cause unnecessary panic. You're doing the right thing by calling, but be prepared for a long wait. In my experience, this type of issue is usually resolved within 2-3 weeks without any action on your part. The $0.00 amounts will be replaced with your actual benefit calculation once processing is complete. And yes, statement access is always temporarily disabled when an application is being processed. This is to prevent confusion since your statement estimates and actual benefit amount may differ slightly.
0 coins
Jamal Edwards
•Thank you for the insider perspective! That's immensely reassuring. I hung up after 2.5 hours on hold yesterday (had an appointment I couldn't miss), but I'll try again today. Do you think I should visit my local office instead of calling? Or just be patient and wait?
0 coins
Amara Okonkwo
If you can wait about 2 weeks, I'd recommend that approach first. If the issue persists after that, then try calling again or schedule an in-person appointment at your local office through the SSA website. One thing to note: if you do reach someone by phone, ask them to check the "MACADE system" for your application status. That's their internal processing system, and a representative can see exactly where your application stands in the pipeline. They should be able to confirm that your application is still being processed and that the $0.00 amounts are just placeholders.
0 coins
Jamal Edwards
•This is incredibly helpful! I'll make a note to ask about the MACADE system if I get through. Thank you so much.
0 coins
Giovanni Marino
WHY does this garbage keep happening to people?? I swear the SSA runs on computers from the 1980s. My sister had the exact same thing happen - zeros all over her account and some random date from 40 years ago. Took her WEEKS of calling every single day to get it fixed. The system is BROKEN. They take our money for decades and then can't even process a simple benefit application without screwing it up!!! Makes my blood BOIL.
0 coins
Liam O'Sullivan
•ikr? my neighbor had to wait 3 months to get his benefits sorted out. system is a joke
0 coins
Fatima Al-Sayed
I had the exact same problem last year when I applied at 66. The online system showed $0.00 and referenced some date from the 1970s. I nearly had a heart attack! After trying to call for days with no luck, I finally used a service called Claimyr (claimyr.com) that got me connected to an actual SSA agent within 20 minutes instead of waiting for hours. The agent confirmed it was just a processing glitch and fixed it while I was on the phone. My correct benefit amount showed up online 3 days later. They have a demo video showing how it works: https://youtu.be/Z-BRbJw3puU Saved me days of stress and phone frustration. Just wanted to pass along what worked for me since I know exactly how you're feeling right now!
0 coins
Jamal Edwards
•Thank you for this suggestion! After another failed attempt at getting through today (disconnected after 40 minutes), I'm willing to try anything. I'll check out that service.
0 coins
Dylan Hughes
its not a error they did that to my dad to!!! told him he wasn't eligible for anything even tho he worked 50 years straight!!! took him goin to the office in person and bringing all his old w2s to prove he worked. system is rigged to deny people what they deserve!!
0 coins
Amara Okonkwo
•That's a completely different issue. What you're describing sounds like a wage discrepancy where some earnings weren't properly recorded. The issue the original poster is experiencing is clearly a processing placeholder with the telltale June 1978 date and the $0.00 amounts across the board. These are very different situations.
0 coins
NightOwl42
Just wanted to add my experience - this sort of thing happens with surprising frequency during application processing. In my case, I had the exact opposite happen: my MySocialSecurity account temporarily showed I was getting $9,247 per month (I wish!). A week later it adjusted to my actual benefit amount around $3,100. The system seems to go through several updates during processing, and sometimes it displays incomplete or incorrect information. The key is to wait until you receive your official award letter, which is the final determination. Honestly, SSA's online systems and their internal processing systems don't always communicate perfectly during the application phase. I'd give it at least 2 weeks before getting too concerned.
0 coins
Jamal Edwards
•That's both hilarious and reassuring! I'd love to see $9,247 show up instead of $0.00! Thanks for sharing your experience - it helps to know these glitches are common.
0 coins
Dylan Hughes
did you work for goverment or railroad at any point? my cousin had something like this and it was because of that windfall thing where they reduce your SS if you get a pension
0 coins
Jamal Edwards
•No, I've always worked in the private sector - retail management and then 25 years at a manufacturing company. No government or railroad jobs, so it shouldn't be WEP or GPO related. Thanks for the suggestion though!
0 coins
Mei Chen
Just following up - were you able to get this resolved? If you're still struggling to reach someone, you might want to try calling right when they open at 8:00 AM your local time. The wait times are usually much shorter early in the morning.
0 coins
Jamal Edwards
•Thanks for checking back! I took everyone's advice and waited a week - and you were right! My account updated yesterday with the correct benefit amount. No more zeros and no more 1978 date. What a relief! I appreciate everyone's help and reassurance during my moment of panic.
0 coins
Ella rollingthunder87
So glad to hear you got it resolved! This is exactly what we were all hoping would happen. Your experience is going to be really helpful for future people who panic when they see those $0.00 amounts and random dates from the 1970s. It's such a common glitch but so scary when you're going through it for the first time. Thanks for updating us - enjoy your well-deserved retirement benefits!
0 coins
GalacticGladiator
•What a relief to hear this worked out! As someone new to navigating Social Security, this whole thread has been incredibly educational. It's reassuring to know that these terrifying-looking system glitches are actually pretty common and usually resolve themselves during processing. I'll definitely bookmark this conversation for future reference - the advice about the June 1978 date being a system placeholder and the MACADE system tip are gold. Thanks to everyone who shared their experiences and expertise!
0 coins
NebulaNova
This thread is incredibly valuable! As someone who's getting close to retirement age myself, seeing all these experiences and especially the resolution gives me so much confidence. The detail about June 1978 being a system default date is fascinating - I had no idea SSA had these kinds of technical quirks. It's also great to know about asking for the MACADE system check if I ever need to call. Thanks to everyone for sharing, and congratulations Jamal on getting your benefits sorted out! Stories like this really show the power of community support during stressful times.
0 coins
Isabella Martin
•Absolutely agree! I'm new here but this entire discussion has been such a learning experience. It's amazing how what seemed like a catastrophic error turned into a textbook example of why patience and community knowledge are so valuable. The technical insights about the 1978 system date and processing placeholders are exactly the kind of insider information you can't find in official documentation. This thread should definitely be pinned or saved somewhere for future reference - I bet this same panic-inducing scenario happens to dozens of people every month. Really grateful for communities like this where experienced folks share their wisdom!
0 coins
Nick Kravitz
What an incredible thread to read through! As someone who's still a few years away from retirement but already worrying about the Social Security process, this whole discussion has been both terrifying and reassuring at the same time. The fact that Jamal's issue resolved itself exactly as the experienced community members predicted really demonstrates the value of having knowledgeable people share their insights. I'm definitely saving this conversation for when my time comes. The technical details about the June 1978 system date, the MACADE system reference, and knowing that statement access gets temporarily disabled during processing are all incredibly useful pieces of information that I never would have known otherwise. It's also comforting to see how supportive everyone was during what must have been an extremely stressful week for Jamal. Thanks to everyone who contributed their experiences - this is exactly the kind of community knowledge sharing that makes navigating complex government systems so much easier!
0 coins
Sean O'Brien
•This is such a perfect example of why online communities are so valuable! As someone completely new to all of this, I had no idea that Social Security applications could have these kinds of technical hiccups. Reading through everyone's experiences - from the initial panic to the eventual resolution - has been incredibly educational. The way experienced members like Amara shared insider knowledge about system dates and processing quirks really shows how much collective wisdom exists in these communities. I'm bookmarking this entire thread for future reference, and I'm sure many others will find it just as helpful when they encounter similar scary-looking system errors. It's amazing how a moment of panic turned into such a comprehensive learning resource for the whole community!
0 coins
NeonNova
What a journey this has been to read through! As a newcomer to this community, I'm blown away by how this thread perfectly captures both the terror and relief that comes with navigating Social Security for the first time. Seeing Jamal's initial panic transform into relief, and witnessing how the community rallied with both technical expertise and emotional support, really shows what makes these forums so valuable. The insights shared here - especially about the June 1978 system date being a default placeholder and the tip about requesting a MACADE system check - are absolute gold for anyone going through this process. It's fascinating how what initially looked like a catastrophic system failure was actually just a routine processing quirk that resolves itself with patience. I'm definitely saving this entire conversation as a reference guide. The combination of technical knowledge from former SSA employees, personal experiences from people who've been through similar scares, and the ultimate happy ending makes this thread a perfect resource for future applicants. Thank you to everyone who contributed - this is exactly the kind of community wisdom that makes complex government processes feel manageable!
0 coins
ApolloJackson
•This thread has been such an incredible resource! As someone who's brand new to thinking about Social Security, I had no idea these kinds of system glitches were so common. Reading Jamal's story from panic to resolution, along with all the expert advice from community members, has been both educational and reassuring. The technical details about processing placeholders and system dates are exactly the kind of insider knowledge you can't find anywhere else. It's amazing how a scary situation turned into such a comprehensive guide for future applicants. Thanks to everyone who shared their experiences - this community's collective wisdom is truly invaluable for navigating these complex government systems!
0 coins