You’re assuming a LOT here.
Many of these software packages weren’t originally written for an international market, and like @doreen says, a lot of what us IT guys are talking about is the idea that there’s a canonical name for a person in a record keeping/governmental way, and then there’s the name they actually use.
We run into it in Anglophone situations all the time as well. Take, for example Charles Doofus III, otherwise known as Trey. His employee paperwork may say “Charles Doofus”, but his email address may be Trey Doofus. Not a problem until the point when you have to try to match those data sets together. You’ve got to be able to definitively tell that Charles and Trey Doofus DOB 9/19/1956 are the same person.
Then it gets more complicated when his son, Charles Doofus IV starts working for the company as a summer intern. Then we’ve got two Charles Doofuses in the system, but one’s Trey Doofus, and the other is Chuck Doofus, and they’re only distinguished by birthday.
And the larger your data set gets, the more likely it is that you may end up with multiple people with the same name and birthday, especially if you’re a national-level enterprise. At my previous job (a national level occupational healthcare provider) we did have multiple names with the same birthdays. Typically they were very common ones- Juan Martinez, or James Smith type names. But they were there- our clinic staff basically had to ask them more identifying information- who do you work for, etc…? In the back of the house, we were kind of screwed if we actually had to match that to anything; there just wasn’t that much to separate Jim Smiths from each other if they had the same birthday.
The reason they did this in the first place is that designers tend to be kind of jealous of data space; if you add an extra field for a mostly unused last name, you increased your database size and complexity and you didn’t actually get anything for it. In 2024, adding a single text field isn’t a big deal, but it was in say… 1994 when a lot of this stuff was being designed.
Not coincidentally, that’s why so many companies used to want SSN; it was a unique identifier for each person that separated EVERY Charles Doofus from each other. Without something like that, IT folks are stuck trying to match on names and birthdates, which is mostly accurate, but still has conflicting stuff like “Charles Doofus” vs. “Charlie Doofus” depending on how Mr. Doofus filled out his form that day for the flu shot or the HR person or the insurance form.