• ansiz@lemmy.world
    link
    fedilink
    English
    arrow-up
    50
    ·
    22 hours ago

    It’s because that explanation isn’t correct. The real deal is you just have entries without a death date, so if you ran a query this get super old ages as a result.

    Note that isn’t a database of payments or even people eligible for them, just a listing of ‘everyone’ with a SSN. There is a separate master death index. In the old days, wild west kind of stuff people would disappear so the death date would never get entered. Modern days every morgue and funeral home has to legally notify SS when someone dies, there is a specific form and major hell to pay if you don’t do it.

    • BakerBagel@midwest.social
      link
      fedilink
      arrow-up
      8
      ·
      20 hours ago

      Social Security numbers were first issued in 1937. You would have need someone to be over 110 in 1937 to have an age over 200. I think that it’s a combination of birthdays entered wrong plus no official death date.

      • ansiz@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        11 hours ago

        I think those are related to survivor benefits. Like an old man marrying a young woman in the 40’s. Like the civil war vets marrying woman in the 20th century. The last civil war widow was getting benefits until she died in 2020. But still the same basic issue.

        But in that case the old man isn’t getting benefits but just is needed as a reference for the person actually getting them.

      • Madison420@lemmy.world
        link
        fedilink
        arrow-up
        16
        arrow-down
        1
        ·
        20 hours ago

        Wouldn’t matter anyway the ss admin automatically stops pay and initiates audit for anything over 115.