I obviously can't know why, but apparently the system allows to keep receiving benefits without the date being present in the database and maybe even claim benefits without the date being present, which is why.
Maybe the data was there initially, but was deleted or lost for technical reasons, for example the date was incomplete, e.g. only the year of birth was known, but not the exact day and then was dropped to null as invalid during some kind of upgrade.
Maybe the data was not possible to enter into the system for technical reasons -- somebody didn't have access, something was down, the next shift was supposed to enter it once the system was back up. Maybe the same, but for process reasons, for example setting the date requires attaching the birth certificate and the birth certificate is lost.
Maybe the data was intended to be entered, but somebody forgot to actually do it, was waiting for birth certificate to be produced, but approved the benefits provisionally.
Maybe the birth certificate was shown to the official, but was of the wrong kind (handwritten extract, foreign document without consular legalization, damaged, illegible or incomplete date), so it was legit enough to start paying benefits but not legit enough to upload to the server. Maybe the date was conflicting with other records somehow. Maybe there was a court decision involved which determined eligibility for benefits but didn't determine exact date of birth.
The key point here -- the system allows for this kind of inconsistency (benefits are being paid, but the date is not present) and relies on a human process to eventually reach a consistent state, but the process failed and nobody really cares to rectify it as long as benefits are being paid.
That's assuming the benefits are actually paid to those people and the organization is not aware of this data issue and not investigating those people for fraud right now.
In an organization big enough there is always this kind of stuff happening (see "seeing like a bank"), which is tolerated as long as statutory task is not compromised.