@BillM223 & @DawnC --- well, the error seems to have been corrected.
End result - had to reach out to my old company again and get on them for about 3 months.
Each time, they say it is ADP dragging their feet in responding.
- My old company FINALLY got me a number I could call at ADP to see about straightening it out but the person I talked to still stated "they do not talk to employees" only "employers".
- Went back to old company, let them know.
- They, again, FINALLY got me another number to call - this time, I got to talk to a support rep.
- The only problem this time, the systems these Support members had access to did not contain my old company (that has been in existence for over 10 years, working through ADP) in their database.
- They finally managed to find the old company once I gave them my SSN BUT it was only partial info. After talking to their team and supervisor, it turns out, they did NOT have access to all the info they needed to make any changes...
So, went back to old company again - let them know. They told me they were in contact with a better, more responsive ADP rep to help fix this.
They DID FINALLY fix the blasted problem which stemmed from a mistake as it turns out (WHICH I TOLD THEM TO BEGIN WITH).
They and ADP are preparing another W2 for me without the "wages over limit" nonsense. But it would take 4 - 6 weeks...
I still wanted to know what happened to trigger that mistake, and my old company told me, they will come back to me once they get that info from ADP....
- That was March 26 and I'm getting gray hair while waiting, AGAIN....!!! (Could be CoViD related delays, but I do not know....)
Best part is, either the:
- old company FINALLY figured out their mistake OR
- ADP (unlikely) figured out the mistake on their end.
- And I can now get the Social Security Admin to correct my data for that year, that is - ONCE I receive the corrected W2 (for which the old company SHOULD be getting that data to the SSA).
Sorry for the rant (not shouting above, just emphasizing) but I severely dislike the run-around in these kinds of scenarios in which I should not have been the one to keep pushing them to unwillingly fix their mistake.
I also wanted to lay out in a some what detailed manner what happened, in case someone else runs into this kind of error.
- Historical content reference...
Thank you again for attempting to help me out.
Patrick
