From the testimony of Mariana Lacanfora, Acting Deputy Commissioner for Retirement and Disability Policy, Social Security Administration to a House Ways and Means Committee hearing yesterday on Social Security Number (SSN) usage:
By the way, what does BNC stand for?
Update: I found this in an OIG report: "The BNC is not an alternative identifier. Notices going to the same individual from different notice systems or in different years would display a different BNC." So Social Security is going to use an identifier that will be worthless to anyone other than Social Security. That takes care of the security problem but it increases the calls, that will often go unanswered, from attorney offices trying to figure out who a notice pertains to.
By the way, are there any reported instances where a notice sent out by Social Security that contained an SSN ever actually caused someone a problem? I don't mean someone's fear that somehow, maybe, theoretically there might be a problem but a real, verified, significant problem? I've never heard of such a case. Why is Social Security doing something that will cause real problems in order to deal with an imaginary problem?
We take seriously public concerns related to mailing documents that include the SSN. Therefore, in 2015, we convened an intra-agency workgroup to analyze options for removing the SSN from all agency notices. Based on our review, we concluded the best option would be to replace the SSN with the BNC — the identifier we now use on the Social Security COLA [Cost Of Living Adjustment] notice. The BNC will allow us to identify the notice and respond to inquiries quickly — just as the SSN has. As part of our IT [Information Technology] modernization efforts, we will begin to modernize communications (notices and mailings) in 2018. As we modify notices, or develop new ones, we will put only the BNC on such notices.
In concert with CMS’ [Center for Medicare and Medicaid Services'] efforts to remove the SSN from Medicare Cards, next year we plan to replace the SSN with the BNC on benefit verifications [sic] letters, which account for approximately 11 million notices. We also plan to replace the SSN with the BNC on certain notices to appointed representatives and on Social Security post-entitlement notices, which account for approximately 2.6 million and 28 million notices, respectively.This may be a problem for attorneys who represent Social Security claimants. My firm often has two clients with the same name. When we receive correspondence we use the SSN to determine which client it pertains to. The client doesn't know their BNC. How can we know which client the correspondence pertains to? What if it's an award certificate for a child of a client? That won't even have the client's name on it. We already have a problem with fee payments in this situation. Is someone going to tell us the BNC?
By the way, what does BNC stand for?
Update: I found this in an OIG report: "The BNC is not an alternative identifier. Notices going to the same individual from different notice systems or in different years would display a different BNC." So Social Security is going to use an identifier that will be worthless to anyone other than Social Security. That takes care of the security problem but it increases the calls, that will often go unanswered, from attorney offices trying to figure out who a notice pertains to.
By the way, are there any reported instances where a notice sent out by Social Security that contained an SSN ever actually caused someone a problem? I don't mean someone's fear that somehow, maybe, theoretically there might be a problem but a real, verified, significant problem? I've never heard of such a case. Why is Social Security doing something that will cause real problems in order to deal with an imaginary problem?